Related
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)
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
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
Source: https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Got nearly 2 years of updates, but not quite.
On a related note, official XZ1 Compact website is up. I'm thinking about getting one for my wife to replace her Z5C, UFS sounds delicious.
The list of devices in the blog is not final and it is possible that we will see Oreo on our device.
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
cyberwytch said:
I was wondering about this myself. Are the stock blobs sdk version specific, so in order to make a custom Oreo rom a stock Oreo ftf is needed first? Or should the nougat blobs potentially be used in an Oreo firmware? Same with hardware drivers that are unique to our device, like WiFi?
Click to expand...
Click to collapse
From memory, as long as the source is configured right it should be fine (Wifi drivers shouldn't be changing as its still the same hardware, same for screen and all) - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
nzzane said:
From memory, as long as the source is configured right it should be fine - Carbonrom and Lineage source are currently being updated to Oreo, along with some of the sony files being configured for it so hopes are high.
Click to expand...
Click to collapse
Awesome sauce! I love your Lineage 14, can't wait to see what's next!
nzzane said:
Even though stock will not support Oreo, Custom firmwares will usually always outlast stock
(Lineage and Carbon are using stock blobs on the Z5 Lineup so custom roms are nearly the same quality, if not better, then stock anyway)
Click to expand...
Click to collapse
That's awesome news, I'll add "official" to the thread title for clarification.
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
I'm currently doing something similar for my laptop running Server 2016, and am slowly making it run like a Desktop OS, by enabling all the other stuff left out that I can find
---------- Post added at 16:25 ---------- Previous post was at 16:21 ----------
nzzane said:
...
Click to expand...
Click to collapse
which linux kernel is LOS running?
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18,
Click to expand...
Click to collapse
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
NeoBeum said:
on github somewhere,
actually, ask and tag greyleshy, he was the one that asked about final kernel for us, and I found the convo somewhere trying to get Bluetooth junk sorted
there might be some msm8994 thing that sony needs but cant use for oreo or something. I dont know
Click to expand...
Click to collapse
Hmm, 'k; thanks. I'll do some more digging. But if true this would flatly contradict Google's own public statements (though I realize it's not like this would be a first for that kind of thing).
-- Nathan
NeoBeum said:
They said it was because Qualcomm aren't great at after market support.
so we couldn't get 3.18, but, what would be interesting to do would be to make some interface to act like a middle man.
Click to expand...
Click to collapse
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
NeoBeum said:
which linux kernel is LOS running?
Click to expand...
Click to collapse
3.10, CAF kernel
nlra said:
Where was this said, and why would we need 3.18 for the Z5 family?
A lot of the reporting being done on this has been bad (whatever happened to reading comprehension, especially in reporters??). According to the source being cited, only SoCs produced prior to 2017 (which the Snapdragon 810 is) AND that are being launched in new devices (which the Z5 series is NOT) are required to run on 3.18. Existing devices already designed and sold before the launch of Oreo (which, having launched in 2015, I think the Z5 family would qualify as) "can continue to use their original base kernel version if desired."
-- Nathan
Click to expand...
Click to collapse
correct,
actually 4.4 kernel, it's only needed for newer SoCs
so we can go on with 3.10 kernel for now but we need to wait for (potential) CAF changes
GreyLeshy said:
Android Oreo supports Kernel 3.10, but need to patch the kernel (example: patch 1, patch 2).
It would be nice if msm8994 supported kernel 3.18 or 4.4, but it is not.
Apparently QCOM has not provided drivers for 3.18+ and therefore CodeAurora kernel was not released because of compatibility issues.
Click to expand...
Click to collapse
well, there's still Linux mainline / vanilla upstream support for msm8994 since 4.10 kernel in a very rough state with terminal only (AOSP)
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
yeah I basically read it as qualcomm have bad after market support
zacharias.maladroit said:
and there's the (close to complete) bringup of msm8994 on 3.18 kernel sauce: https://github.com/sonyxperiadev/kernel/pull/972 (for AOSP)
Click to expand...
Click to collapse
I might have something interesting to build then and I can stop lounging around
any news for official aosp 8.0 release for z5?
Enviado desde mi SGP712 mediante Tapatalk
while traversing the gerrit of Lineageos I observed updates of old versions and even cyanogenmod, while we have the obligation to upgrade to the next version with the update tool, is there a way to stay on a old version and take advantage of new features without fully compiling android