OnePlus released the source code of OOS on github. Some nice news.
https://github.com/OnePlusOSS
Hmm, interesting news, thank for info :good:
This is badass!
Great news indeed.
Let's wait for an OPX device tree and vendor blobs
The github page has a 6.0.1 branch only.
Does this mean that this is a build for the oneplus 2 only?
Or does this also mean that devs can now build a 6.0.1 based oxygen os 3 rom for oneplus x as well using this before oneplus themselves do it??
Had a closer look... It just looks like it'll build AOSP... Not O2...
Ivtake the previous post back. This is awesome! We just need to get a device tree working and we can produce an unofficial port!
Now the path clears to custom oxygenOs:highfive:
Also it may mean timely access to sources, if we ever get mm
Unfortunately , I was right earlier... It is not open source O2
@crian RJDTWO is right. Confirmed by Helen yesterday. Can you change the title, please.
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)
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
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
msfrox said:
hay guys
I have to format and update my moms phone it is running CM 13 since I gave it to her. I need a good stable rom to update her phone do you guys have any suggesions
Click to expand...
Click to collapse
Try MOKEE rom (History)...
https://download.mokeedev.com/?device=wt88047
What's the difference between history and release
msfrox said:
What's the difference between history and release
Click to expand...
Click to collapse
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
Nice thanks
History means stablest
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
why alpha? when can we expect a stable build?
shawon11 said:
why alpha? when can we expect a stable build?
Click to expand...
Click to collapse
Sorry bro but this is not my work I am just sharing good TWRP:good:
Azizbagwan said:
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
Click to expand...
Click to collapse
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
robbayani said:
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
Click to expand...
Click to collapse
Project Treble is the Answer
The reason manufacturers have such a hard time pushing out prompt updates is because of all the work that has to go into getting the operating system to communicate with the hardware.
Traditionally, it worked something like this: the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software–technically referred to as vendor implementation—also had to get updated. That’s a lot of work.
So, starting with Android 8.x (Oreo), Google separated the two. That means the Android OS itself can be updated without having to touch the vendor implementation. That, in turn, can be updated by itself if needed.
To put that in full context, before an update can be pushed out to an Android 7.x (or earlier) device, not only does the Android OS code have to be updated, but so does the low-level hardware code, which is generally maintained by the chip maker. So, for example, if Samsung wants to push an update to one of its phones, it has to wait for Qualcomm (or whoever made the chip) to update its code to work with the new Samsung code. That’s a lot of wheels turning at once, and each one is dependent on the other.
With Android 8.x and beyond, it won’t be like this anymore. Since the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
This should dramatically speed up the update process—in theory, at least. Updating devices will still be in the manufacturer’s hands, and since the first Oreo devices outside of the Google-maintained Pixel line are just now rolling out, we haven’t yet had a chance to fully see this in practice. Hopefully, it actually makes a significant change to the speed in which updates are written and pushed out.
Will My Device Benefit from Project Treble?
Now that’s the million dollar question, right? Unfortunately, the answer isn’t so simple (surely you didn’t expect it to be). That said, here are some facts:
If your device never gets updated to Oreo, it will never get Project Treble. No way around that. Sorry.
If your device does get updated to Oreo, it’s still not required to support Treble—that’s up to the manufacturer.
If you buy a new phone that runs Oreo out of the box, it is required to support Treble out of the box.
In short: Treble support on updated systems is still up to the manufacturers, but new Oreo devices will be required to support Treble moving forward.
So, for example, the Pixel 2 already supports Project Treble. The forthcoming Galaxy S9 will also support Treble out of the box. Google also updated the Pixel 1 to support Treble, but it’s unfortunately it looks like Samsung left it out of the Oreo build for the Galaxy S8.
If you’re curious about your own device, Android Police has a running list of all devices that will get Treble support, as well as a which ones will get updated to Oreo without Treble.
Android OS updates have been a constant point of contention for many years now, so it’s good to see Google finally addressing the issue. With any luck, this will put all Android devices closer to parity with Apple in terms of device updates.