Database Users

[KERNEL][ICS/AOSP] Electron Kernel [-O3][SM~4.9.3]

Just gonna keep this short for you guys. This device is pretty old, and really there isnt much development going on. I dont have the time to work on a lollipop port, nor do I really care enough to try. That being said, I've mixed NUK3RN3L and StarKissed into one kernel, and have added a **** ton of optimizations. The full changes can be seen in my source code HERE. Lets squeeze what optimizations we can out!
Code:
ifdef USE
export DISCLAIMER="Use at your own risk, I'm not responsible for any mishaps or damage"
else
export YOUR_LOSS="You're missing out!"
endif
Major Changes(simplified for non devs):
Improved Memory Managment
Improved Overall performance
Updated from GCC-4.4 to SM-4.9.3(Toolchain)
Download: BasketBuild
Thanks to:
Santod
TwistedUmbrella
Paul Beeler
And more!
XDA:DevDB Information
Electron Kernel for HTC Thunderbolt, Kernel for the HTC Thunderbolt
Contributors
frap129, frap129, santod, TwistedUmbrella
Source Code: http://github.com/frap129/Electron_kernel_mecha
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 1
Created 2014-12-30
Last Updated 2014-12-29

Reserved

I'm glad I glanced at the forum today! Thank you for this.
Question, what should the Kernel version read if it is successfully installed?
Mine says 3.0.16-nuk3rn3l [email protected] #3 PREEMPT
Is that correct?

nichikari said:
I'm glad I glanced at the forum today! Thank you for this.
Question, what should the Kernel version read if it is successfully installed?
Mine says 3.0.16-nuk3rn3l [email protected] #3 PREEMPT
Is that correct?
Click to expand...
Click to collapse
Well, no. But mine hasnt changed either despite it being correctly flashed. Im pretty sure its just a problem with the ROM not detecting the change in kernel. You can download trickster mod or a similar app to check from there.

frap129 said:
Well, no. But mine hasnt changed either despite it being correctly flashed. Im pretty sure its just a problem with the ROM not detecting the change in kernel. You can download trickster mod or a similar app to check from there.
Click to expand...
Click to collapse
I downloaded Trickster and it says the kernel is "Linux version 3.0.16nuk3l ([email protected]) (gcc version 4.4.3 (GCC) ) #3 PREEMPT Fri Jul 12"
Is that what it should say or something else? What does your's say?
Edit: I just reflashed the kernel. Same reading on Trickster. I'm beginning to think that it might be the ROM not displaying the kernel name. I'm running NuSenseRom Reborn 6.0. I THINK I noticed a difference but it might just be a placebo effect. Hahah.

I think it did take. My battery charged in 1/2 the time it normally takes.

happy new year 2015
hmm..what feature on this kernel?
thanks you for post new stuff here btw

Just discovered that WiFi is broken. Says "error" in main settings menu after attempting to turn on the service.

Discussion : Android 8.1 Oreo Related Development

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 Beta​http://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

No official Android 8.0 (Oreo) for the Z5 family

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

Requesting developers for lineageOS 15

Hello developers I am just requesting for lineageOS 15. I am new to to xda.sorry if I asked in wrong way.

No need to request.. Even Nougat is not fully free of bugs. Moreover, there're no marshmallow roms with volte support. Time is just passing by.

A lot of old phones do get 8.0 update,but what's wrong with ours .....!!!
Well is it that we lack people who develop the things ...no offense just curious ..!!
Apologies if I was bit cocky ..
---------- Post added at 05:53 PM ---------- Previous post was at 05:50 PM ----------
I mean even lemax 2 and lepro 3 got the Oreo versions

Ok.. ,
Firstly Our Device Use SD 652 Which rare..
We hard to find drivers for it so it pretty much harder to make lineage 15 to works
Le 3 Pro are similar to OnePlus 3 which is lucky
@codeworkx will work for los 15 after 6 months maybe

Oh..!!!my bad its okay sir,now i get it

DarknessKiller said:
Ok.. ,
Firstly Our Device Use SD 652 Which rare..
We hard to find drivers for it so it pretty much harder to make lineage 15 to works
Le 3 Pro are similar to OnePlus 3 which is lucky
@codeworkx will work for los 15 after 6 months maybe
Click to expand...
Click to collapse
xiaomi mi max (helium) use SD652 too. and it has oreo rom now.can it [email protected] link:lineageos15https://forum.xda-developers.com/mi-max/development/rom-lineageos-15-t3682311
AOSP8.0:https://forum.xda-developers.com/mi-max/development/rom-aosp-nitrogen-t3671282

one03 said:
xiaomi mi max (helium) use SD652 too. and it has oreo rom now.can it [email protected] link:lineageos15https://forum.xda-developers.com/mi-max/development/rom-lineageos-15-t3682311
AOSP8.0:https://forum.xda-developers.com/mi-max/development/rom-aosp-nitrogen-t3671282
Click to expand...
Click to collapse
No.. the issue is camera and fp might not work

DarknessKiller said:
No.. the issue is camera and fp might not work
Click to expand...
Click to collapse
may it is not a big problem.we can use the third party app instead .we just want to exprience oreo though it is not stable.please don't give up us

one03 said:
may it is not a big problem.we can use third party app instead .we just want to exprience oreo though it is not stable.please don't give up us
Click to expand...
Click to collapse
No.. Camera will be totally not usable.. EVEN FP

DarknessKiller said:
No.. Camera will be totally not usable.. EVEN FP
Click to expand...
Click to collapse
OK..i get it.thanks for your reply

Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0

cute_prince said:
Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0
Click to expand...
Click to collapse
Wow, amazing! Thanks!!!
If compiled, device will boot?

thiagox said:
Wow, amazing! Thanks!!!
If compiled, device will boot?
Click to expand...
Click to collapse
No, dont compile now. As I mentioned, device tree needs a lot of patches before it can boot. I am working on it.

cute_prince said:
No, dont compile now. As I mentioned, device tree needs a lot of patches before it can boot. I am working on it.
Click to expand...
Click to collapse
Anyway that's a great news , thanks for giving your time for Le 2

cute_prince said:
Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0
Click to expand...
Click to collapse
Thanks for working on le2

cute_prince said:
Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0
Click to expand...
Click to collapse
You rule!

cute_prince said:
Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0
Click to expand...
Click to collapse
Fantastic! Will see if i can contribute anything.

cute_prince said:
Hi, I have already started developing LOS 15 for Le 2. Just finished patching proprietary blobs to work with Oreo. Kernel changes have also been made. Device tree needs a lot of work to be done. Those who wanna contribute may send pull request to my git.
kernel: https://github.com/cuteprince/android_kernel_leeco_msm8976/tree/lineage-15.0
device: https://github.com/cuteprince/android_device_leeco_s2/tree/lineage-15.0
vendor: https://github.com/cuteprince/android_vendor_leeco_s2/tree/lineage-15.0
Click to expand...
Click to collapse
Hii Sir,
Please Check PM..
Let me know if you want to test LOS15 builds..
Feel free to massage me

@cute_prince it seems @Rk585 is also working on lineage os 15 for s2, maybe you guys can collaborate?

abhifx said:
@cute_prince it seems @Rk585 is also working on lineage os 15 for s2, maybe you guys can collaborate?
Click to expand...
Click to collapse
Nahh he gave up
And @RisbabhRao Are Busy on his studies

Bake AOSP Pie for Xperia XZ?

Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.

I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^

Awesome!
I'm eager to hear about your endeavors in this!

L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant

L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.

@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule

Here is the screenshot I mentioned in my previous post.
I forgot to include it ...

Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?

I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first

31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!

I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.

Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331

Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing

Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait

Xperia z1 has carbon Android pie and gapps link
This may help you.

Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.

No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning

Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.

Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?

I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.