Related
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
Hello,
So now we have the Z2 sources, Z2 Pro should come soon as-well, it would be great to start building ourselves a nice CM13 or RR. Sadly I am fully booked for the 2 next weeks and as it's my first CM build (despite I builded some ASOP already), it's going to take me a long time. So the goal of this thread is just to regroup and share the files so we can get ASAP to something stable.
Do we have the sources from the chinese CM13 Z2 Pro build ?
Thanks all !
I would love to contribute, but i'm a bit busy, too. It would be nice if someone could create a git for this project following the rules from cyanogenmod, to get this Phone an official release some time soon.
How To Port CyanogenMod Android To Your Own Device
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Hey, I am fully Intrested in bringing up CyanogenMod for it, but.. Kernel Sources arr bad or something? I am trying to compile with aarch-arm64-androideabi- (gcc4.9) its like failing to build in signal.c
Sorry for my excitement.But i am quiet depressed that more than 2 to 3 months have been passed but their is no nougat ROM for our device.
If someone has idea whether the making is under processing or yet to be start.please let me know.
Thanx.
i guess kernal source is released by xiaomi, very soon we should be able to see some developments on nougat roms for our devices.
At least a month, I think.
Only when you see msm8937 nougat caf kernel source here -> Android releases (QAEP.release) - XWiki
https://wiki.codeaurora.org/xwiki/bin/QAEP/release
hafeez90 said:
Only when you see msm8937 nougat caf kernel source here -> Android releases (QAEP.release) - XWiki
https://wiki.codeaurora.org/xwiki/bin/QAEP/release
Click to expand...
Click to collapse
Thanx for the nice info.I'll keep checking it regularly.
It's hard to pin down the Android codename in advance thanks to Google's notorious trolling. Remember Key Lime Pie and Milkshake? This time, everyone's first guess turned out to be the right one. Google has named Android 8.0 "Oreo" after the cookies produced by Nabisco.
Most Android names are generic treats like Marshmallow and Nougat. However, this is not the first time Google has worked with a company to use a name brand. KitKat was a surprise announcement in 2013. The agreement between Google and Nestle/Hershey includes some cool limited edition KitKat candy bars, too. It is unclear if there will be similar Android-themed Oreo packaging, but Google must have some manner of agreement allowing it to use the Oreo trademark. The statue does at least look a bit more daring than other recent bugdroid mascots.
There's not much new to report on the features in Oreo—we've been playing with the developer preview for months, after all. You can expect picture-in-picture support for apps, autofill apps, faster boot times, and those god-awful new emoji. Oreo is being rolled out to AOSP today, and updates for the Pixels and recent Nexus devices are in final testing now. You can expect the OTA soon on those devices.
Google has just announced that Android 8.0 Oreo will be uploaded to the Android open Source Project today, and that updates to the newest version of the platform are currently being tested by carriers for the Google Pixel, Nexus 5X, and Nexus 6P. Google says these updates will begin rolling out in phases "soon," along with updates for the Pixel C and Nexus Player.
Google has not clarified when factory images or OTA files will be available for devices at this time.
As a reminder, Android Oreo brings a number of new features to the table, including notification dots, enhanced speed, a brand-new set of emoji , more aggressive battery life management, and [finally] OS-level autofill.
Source : Google, AndroidPolice
Android 8.1 is the next version of the OS, Google app reveals..
Android 8.0 Oreo has only been out for a couple of weeks at this point, and hasn't actually made it to every single supported Nexus and Pixel device out there yet. Not to mention how long it's going to take for it to land on any other phone or tablet.
Even so, maybe you'd like to know what the next version of the OS will be? It's Android 8.1, by the way. This has been revealed by a teardown of the latest iteration of the beta Google app. The SDK used internally by the company to build said app outright says so.
As for the name, it makes most sense for Google to keep using Oreo - it would be a shame to switch from such a well recognized brand so soon, and it's also how it did things last year with 7.0 and 7.1 both being Nougat. If you're wondering when 8.1 will hit, remember that in 2016 Android 7.1 debuted with the Pixels only a couple of months or so after 7.0 updates started going out. So we assume that this year the second-gen Pixels will be the first devices to launch running Android 8.1, when they land in October.
Source : - Google, GSMARENA
Google announces Android 8.1 developer preview, final release planned for December
Google launched the new Pixel phones with Android 8.0, which is what last year's Pixel's have been running since the update. A new version of Oreo is on the way, though, and you can try it right now. Google has launched a developer preview for Android 8.1. As usual, it's supported on recent Google devices and can be installed in two ways.
The system images are available for download now, but that requires an unlocked bootloader. The beta program with automatic OTA updates will be available as well. You can sign up now, but it looks like the switch hasn't been thrown to push out the OTAs just yet. If you want to get on the dev preview, it's compatible with the following devices. The OTA files are available for sideloading, though.
Nexus 5X
Nexus 6P
Pixel C
Pixel
Pixel XL
Pixel 2
Pixel 2 XL
The Android 8.1 preview runs from today until the OS is released, which Google expects to happen in December. Installing the preview should not affect your data, but you never know. Running a developer preview does come with some risk, so make sure you've got your data backed up. Leaving the beta program will result in a device reset as well.
Google has a developer-oriented changelog up. Here's what you can expect in the new version.
Neural networks API: The Neural Networks API (NNAPI) provides apps with hardware acceleration for on-device machine learning operations. The API supports on- device model creation, compilation, and execution.
Notifications: Apps can now only make a notification alert sound once per second. Alert sounds that exceed this rate aren't queued and are lost. This change doesn't affect other aspects of notification behavior and notification messages still post as expected.
Improved targeting for low-RAM devices
Autofill framework updates: custom descriptions that the Android System shows in the autofill save UI, specify a Validator object that your app can use to decide if the Android System should show the autofill save UI, and more.
EditText updates
Programmatic Safe Browsing actions: Devs can control whether an app reports known threats to Safe Browsing, and have the app automatically perform a particular action—such as going back to safety—each time it encounters a URL that Safe Browsing classifies as a known threat.
Video thumbnail extractor: The MediaMetadataRetriever class has a new method, getScaledFrameAtTime(), that finds a frame near a given time position and returns a bitmap with the same aspect ratio as the source frame, but scaled to fit into a rectangle of given width and height.
Shared memory API: Android 8.1 (API level 27) introduces a new SharedMemory class. This class allows you to create, map, and manage anonymous shared memory that can be used by multiple processes or apps.
WallpaperColors API: Adds support for managing wallpaper colors. This feature lets you create a WallpaperColors object from a bitmap, a drawable, or by using the first three most visually representative colors. You can also retrieve details of the first three noticeable colors of a wallpaper.
Fingerprint updates
Source - AndroidPolice, Google
DISCLAIMER
Code:
[LIST]
[*]Your warranty is now void.
[*]I am not responsible for bricked devices, dead SD cards,
[*]thermonuclear war, or you getting fired because the alarm app failed.
[*]before flashing it! YOU are choosing to make these modifications, and if
[*]you point the finger at me for messing up your device, I will laugh at you.
[/LIST]
List of Android 8.0 / 8.1 Oreo Based Beta / Alpha Rom's
Osprey
1. [ROM]AospExtended ROM V5.2 [OSPREY]
2. [ROM][osprey] Unofficial LineageOS 15.0 by Alberto97
3. [ALPHA] AOSP 8.0.0 r17 [UltraDevs] [OSPREY] [5 OCT Patch]
4. [ROM]crDroid Android 4.0 [OSPREY] [UNOFFICIAL]
5. [ROM]Xenon HD [OSPREY] [UNOFFICIAL]
6. [UNOFFICIAL][OREO]XPerience 12.0.0
7. [ROM][OSPREY]OFFICIAL]Pixel Experience [AOSP]
8. [ROM][osprey] The Android Open Source Project
9.[ROM]CosmicOS 3.0 Chronus for Osprey[UNOFFICIAL]
10.[Osprey][8.0.0][Unofficial] Ground Zero ROMs || Validus [Beta][GZOSP]
11.[Osprey][VoLTE][AOSCP]CypherOS-5.1[UNOFFICIAL]
12.[ROM]LineageOS 15.1 [OSPREY/MERLIN] [UNOFFICIAL]
13.[ROM][Osprey]ResurrectionRemix v6.0.0[UnOfficial]
Merlin
1. AospExtended 5.2 for Moto G Turbo/Merlin!! By Innfinite4evr
2.[ROM][Merlin]ResurrectionRemix v6.0.0[UnOfficial]
3.[ROM][8.0.0] crDroid Android 4.0 [OSPREY/MERLIN] [UNOFFICIAL] By althafvly
4.[ROM][Merlin]OFFICIAL]Pixel Experience [AOSP]
Official OpenGapps for Oreo 8.1 has been released but still it's in Betahttp://opengapps.org/
TWRP
Osprey
[TWRP][osprey] TWRP for Moto G 2015
Merlin
[TWRP][merlin] TWRP for Moto G Turbo
Reviews For the Android 8 / 8.1 Based Alpha Rom's
LOS 15 Osprey Alpha Build
Battery Review - https://forum.xda-developers.com/showpost.php?p=73793250&postcount=381
In - Depth Review - https://forum.xda-developers.com/showpost.php?p=73928613&postcount=499
AospExtended ROM V5.0 [OSPREY] Alpha build
General Review - https://forum.xda-developers.com/showpost.php?p=74008848&postcount=37
In - Depth Review - https://forum.xda-developers.com/showpost.php?p=74097172&postcount=140
AOSP 8.0.0 r17 [UltraDevs] [OSPREY] Alpha build
General Review - https://forum.xda-developers.com/showpost.php?p=74107538&postcount=24
The Android Open Source Project 8.0
General Review - https://forum.xda-developers.com/showpost.php?p=74622199&postcount=32
Battery Review - https://forum.xda-developers.com/showpost.php?p=74640229&postcount=40
[Osprey][8.0.0][Unofficial] Ground Zero ROMs || Validus [Beta][GZOSP]
General Review - https://forum.xda-developers.com/showpost.php?p=74691620&postcount=12
Battery Review - https://forum.xda-developers.com/showpost.php?p=74692903&postcount=13
[ROM][8.1.0_r1] Pixel Experience [AOSP][OSPREY][UNOFFICIAL]
General Review - https://forum.xda-developers.com/showpost.php?p=74845271&postcount=47
rahul9999 said:
Initial manifest for official Lineage 15.0 has been Created today,
So they have started working on this
Source : - Initial manifest for Lineage 15.0
Click to expand...
Click to collapse
That's pretty cool. My guess is that the first Oreo ROM for our osprey is going to be Lineage OS 15.0.
This time arround, Lineage should be the first one, since there is no fiasco like Nougat's two major releases at once (7.0 and 7.1.1). Remember how people used to get CyanogenMod 14.0 internal sources and put them into Nougat 7.0 ROMs for the osprey? Back then I used to love BeanStalk because it was pretty much the most stable Nougat ROM for my osprey. There was a bug with video recording but I was ready to trade new features for video recording.
nicolasmart said:
That's pretty cool. My guess is that the first Oreo ROM for our osprey is going to be Lineage OS 15.0.
This time arround, Lineage should be the first one, since there is no fiasco like Nougat's two major releases at once (7.0 and 7.1.1). Remember how people used to get CyanogenMod 14.0 internal sources and put them into Nougat 7.0 ROMs for the osprey? Back then I used to love BeanStalk because it was pretty much the most stable Nougat ROM for my osprey. There was a bug with video recording but I was ready to trade new features for video recording.
Click to expand...
Click to collapse
I cant wait man. I need my cookie fix.
rahul9999 said:
Initial manifest for official Lineage 15.0 has been Created today,
So they have started working on this
Source : - Initial manifest for Lineage 15.0
Click to expand...
Click to collapse
I'm not a fan of Lineage. I think I'll stick with CAF rom. It's the best I've ever flashed and the longest I've stayed with a rom.
melp57 said:
I'm not a fan of Lineage. I think I'll stick with CAF rom. It's the best I've ever flashed and the longest I've stayed with a rom.
Click to expand...
Click to collapse
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
With the support of Great Developers we should surely get Android Oreo for our device.. Also a CAF Based Rom but it will take a time as usual... Not sure how much time take for PA..
As i can see a work for Lineage 15 is going on very well & i think this would be our first Oreo ROM..
RijuSarkar13 said:
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
Click to expand...
Click to collapse
I've tried aospa but I don't really like it. It's not that stable for me on osprey, the Qualcomm camera doesn't work and I needed another camera app, PACKAGE INSTALLER WAS MISSING!!! I WASN'T ABLE TO INSTALL APKs, even through recovery. I needed to re-install it to make package installer work. Also, it's not that customizable. Not that Default Lineage is but after installing substratum, everything is perfect.
Sticking with LOS 14.1 + Open Gapps + Kali Nethunter until Lineage 15 gets released.
nicolasmart said:
I've tried aospa but I don't really like it. It's not that stable for me on osprey, the Qualcomm camera doesn't work and I needed another camera app, PACKAGE INSTALLER WAS MISSING!!! I WASN'T ABLE TO INSTALL APKs, even through recovery. I needed to re-install it to make package installer work. Also, it's not that customizable. Not that Default Lineage is but after installing substratum, everything is perfect.
Sticking with LOS 14.1 + Open Gapps + Kali Nethunter until Lineage 15 gets released.
Click to expand...
Click to collapse
I launched so many apps with package installer...that's not roms fault...for example I installed nova Google companion from apkmirror and few other apps..not a single problem...Qualcomm camera got better in 7.2.3...though Moto z camera is always better...it has not much customisation and that is it's uniqueness...I always feel I am using a stock Moto so much improved ROM...I just love the aospa...
RijuSarkar13 said:
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
Click to expand...
Click to collapse
The CAF rom is updated.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
rahul9999 said:
With the support of Great Developers we should surely get Android Oreo for our device.. Also a CAF Based Rom but it will take a time as usual... Not sure how much time take for PA..
As i can see a work for Lineage 15 is going on very well & i think this would be our first Oreo ROM..
Click to expand...
Click to collapse
Can't thank our Osprey Dev enough! This device is 2 yrs old and still going strong.
melp57 said:
The CAF rom is updated.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
Can't thank our Osprey Dev enough! This device is 2 yrs old and still going strong.
Click to expand...
Click to collapse
Yes.. All credits goes to Great Dev Like @Alberto97 @ishubhamsingh @ Arcadee & Many more
melp57 said:
The CAF rom is updated..
Click to expand...
Click to collapse
which one is updated? cosmic os?
RijuSarkar13 said:
which one is updated? cosmic os?
Click to expand...
Click to collapse
Sorry, pa
...
Guy's... Thread Subject edited Related to Android Oreo development.. So instead of spamming any other active threads you can post here...
Also please bear in mind Don't ask for ETA for any Android Oreo ROM... It's against XDA Rules..
Our official Lineage Os maintainer @Alberto97 successfully booted Lineage Os 15 ROM on our device while testing..
So guys be patient development is going great & as per this source we will surely get official Lineage Os 15 ROM based on Android 8 Oreo
Poll added related to which Android Oreo Based Rom your waiting for..
rahul9999 said:
Our official Lineage Os maintainer @Alberto97 successfully booted Lineage Os 15 ROM on our device while testing..
So guys be patient development is going great & as per this source we will surely get official Lineage Os 15 ROM based on Android 8 Oreo
Click to expand...
Click to collapse
Love to get my hands on what he flashed!
EDIT: nice poll!
edit: lots of threads out there saying how to flash oreo on any phone, but the fine print says only nexi and pixili.
edit: seems like Lineage by the end of this year which is fantastic. I assume both 14.1 and 15.0 will be running side by side for quite a while.
edit: Added to my sig to help folks fine it.
edit: @rahul9999 you might put in your sig... that's a very easy way to advertise it w/o breaking xda rules or going off track!!! and when was your English ever bad!
KrisM22 said:
Love to get my hands on what he flashed!
EDIT: nice poll!
edit: lots of threads out there saying how to flash oreo on any phone, but the fine print says only nexi and pixili.
edit: seems like Lineage by the end of this year which is fantastic. I assume both 14.1 and 15.0 will be running side by side for quite a while.
edit: Added to my sig to help folks fine it.
edit: @rahul9999 you might put in your sig... that's a very easy way to advertise it w/o breaking xda rules or going off track!!! and when was your English ever bad!
Click to expand...
Click to collapse
Hehe thanks dude... will add this in my Sign sure
I Also want get my hands on what he flashed.. but we have to wait as stable build might take a time to develop... Soon LoS 15
GZOSP - AIO
Ground Zero Open Source Project
What it is
- GZOSP is our 8.0 base we use for other projects, e.g. Validus
Not much features will be added, only basics and aosp patches will be merged.
It's open source and buildable for anyone, builds from it already started popping up, so we decided to allow it
and to avoid the constant pm's with build questions we decided to create this thread, so maybe people will
help each other some.
Isn't that a novel idea :fingers-crossed:
What is this thread
- The place for: questions about GZOSP, GZOSP builds, GZOSP unofficial builds, GZOSP build questions,
GZOSP issue reports, GZOSP requests, GZOSP anything...
We will not be creating device threads for GZOSP ourselves since it is our base for Validus, for now.
-(Maintainers and unofficial builders are allowed to do whatever they want with GZOSP builds however).-
But since some people like that pure aosp feeling, we will post builds when things get added/updated in here now.
No plans for Tesla & Tipsy yet, but since those were born out of boredom at the end of a Validus Android cycle
anything can happen when we get bored again
- If reporting issues state what device since this is an AIO thread
- When asking for help in build issues, link your trees on github, paste errors on hastebin, give as much info as you can...
Look at some of our devices first for build errors & stuff
Build command= make gzosp -jx
Gerrit code review: https://review.gzospgzr.com
Project GitHub: https://github.com/GZOSP
Devices: https://github.com/GZOSP-Devices
I will reserve a few posts here to fill with links to builds
That's all for now, this will probably be edited later
XDA:DevDB Information
GZOSP, ROM for the Ground Zero ROMs
Contributors
martinusbe, Char_G, scoobyjenkins
Source Code: https://github.com/GZOSP
ROM OS Version: 8.x Oreo
Based On: AOSP 8.0/CAF
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-24
Created 2017-09-26
Last Updated 2018-10-28
Reserved
Public builds by GzR maintainers
oneplus2: https://www.androidfilehost.com/?fid=673791459329055441 updated 10/22 by @hardwareadictos
oneplus3: https://www.androidfilehost.com/?w=files&flid=217699 link to upload folder
oneplus5: https://www.androidfilehost.com/?w=files&flid=218203 link to upload folder
Flo: https://www.androidfilehost.com/?fid=745849072291680731
Moto G4/G4+ https://www.androidfilehost.com/?fid=673791459329056982 by @oadam11 build Oct 29
Moto potter: https://www.androidfilehost.com/?fid=745849072291677971 by @GtrCraft
surnia: https://androidfilehost.com/?fid=817906626617940895 by @spires
Unofficial builds
Bullhead by @sparx can be found here https://forum.xda-developers.com/showpost.php?p=74268779&postcount=333
* unofficial builds are welcome
Reserved
That was fast tho. Nice job.
Go Go Go
Third ) I have never got the first comment, but now I got third
Yupiii Marty [emoji847][emoji847][emoji847]
Enviado desde mi ONE A2003 mediante Tapatalk
ROM OS version 7.x? Nougat[emoji849]isn't it supposed to be 8.0 Oreo?![emoji54][emoji848]
Sent from my ONEPLUS A3003 using Tapatalk
---------- Post added at 07:20 AM ---------- Previous post was at 07:19 AM ----------
Ali.G said:
ROM OS version 7.x? Nougat[emoji849]isn't it supposed to be 8.0 Oreo?![emoji54][emoji848]
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Sorry I just read it...
Sent from my ONEPLUS A3003 using Tapatalk
Still with microg, then its perfect
Can we get "Game do not disturb mode" in future updates please like the latest oxygen update
Sent from my ONEPLUS A3003 using Tapatalk
Ali.G said:
Can we get "Game do not disturb mode" in future updates please like the latest oxygen update View attachment 4283729
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
If that get's added, it will be in Validus
OK I really like the ROM, but I can't get mobile data to work on it. I have tried different firmwares, OB21 and 24, different kernels and everything I can think of, but it doesn't work. I have t mobile US. I have tried it with every build released. Thanks for the ROM tho
Edit:removed the quote. Sorry
michel sedgh said:
OK I really like the ROM, but I can't get mobile data to work on it. I have tried different firmwares, OB21 and 24, different kernels and everything I can think of, but it doesn't work. I have t mobile US. I have tried it with every build released. Thanks for the ROM tho
Edit:removed the quote. Sorry
Click to expand...
Click to collapse
i suppose you are talking about oneplus3
I flashed several builds all with working data, and none of the testers have reported issues with it
i have no idea
martinusbe said:
i suppose you are talking about oneplus3
I flashed several builds all with working data, and none of the testers have reported issues with it
i have no idea
Click to expand...
Click to collapse
Yes oneplus 3. Thanks anyways...
Anyone else having issues waking the phone ( ie tap power to shut screen off or wait for screen to time out then when attempting to wake it the compacitive buttons will light up but screen remians off? Woke up this morning to my alarm as usual and couldn't **** it off cuz screen (ui) was black and had to hard reboot. tried with SuperSu and magisk. Clean flash 24 build microgapps from fraps129 i dont think it was present in 1st build but last two im having this problem could it be my subs theme causing it? Tried a few always Oreo options Thanks
partridge79 said:
Anyone else having issues waking the phone ( ie tap power to shut screen off or wait for screen to time out then when attempting to wake it the compacitive buttons will light up but screen remians off? Woke up this morning to my alarm as usual and couldn't **** it off cuz screen (ui) was black and had to hard reboot. tried with SuperSu and magisk. Clean flash 24 build microgapps from fraps129 i dont think it was present in 1st build but last two im having this problem could it be my subs theme causing it? Tried a few always Oreo options Thanks
Click to expand...
Click to collapse
Since we are still waiting for Oreo commits from the substratum team, always try without a theme first
martinusbe said:
Since we are still waiting for Oreo commits from the substratum team, always try without a theme first
Click to expand...
Click to collapse
Thx basically what im asking is that behavior something that a theme could cause. As the only other mod ive made is enabled soft keys via build.prop
OP3 build 25/9
For a better fingerprint recognize we have to wait for op to release thier Oreo build am I right?
Anyone is using the always on ambient display? Would love to use it but I'm afraid about a burn in
Oh, look, a nice shiny new thread! Thank you! @martinusbe
@martinusbe is burn in protection active? I saw the screen for op5 that kernel was 4.x, will op3 have also 4.x kernel?