Related
I think I have good news for some of you
There are some hints, that there will be official AOSP support from sony for our devices soon.
For all of you, who don't know: There is a official AOSP project for a few sony devices.
Our problem: Our devices aren't supported (yet?).
But there are good news:
1. The Sony Xperia Developer World github account has forked the rhine-common device tree from FreeXperia/Cyanogenmod. That means they are not uninterested.
2. It gets better: Alin Jerpelea, a member of the Sony Xperia Open Source team and member of FreeXperia, will give a talk about the future of the Sony AOSP support at xda devcon in half a month.
3. And now the best: The github repositority for Sony AOSP kernel recently got a new branch, which is at the same caf tag like our 14.4.A.108 kernel
I am really hoping this becomes truth in near future
Sources:
http://developer.sonymobile.com/201...-mobile-innovation-with-us-at-xdadevcon-2014/
https://github.com/sonyxperiadev/kernel-copyleft/commits/14.4.A.0.xxx
https://github.com/sonyxperiadev/kernel/tree/aosp/LNX.LA.3.5.1-01110-8x74.0
https://github.com/sonyxperiadev/android_device_sony_rhine-common
UPDATE: the latest git commits are proving it, we will get official aosp support
UPDATE: the latest commits prove that z2 and it's variants will also get official aosp(with the same kernel sources as us, congrulations)
That would be great :good:
Does this mean better camera drivers and stuff?
rob rich said:
Does this mean better camera drivers and stuff?
Click to expand...
Click to collapse
Potentially, lets hope so!
CoolDevelopment said:
I think I have good news for some of you
There are some hints, that there will be official AOSP support from sony for our devices soon.
Click to expand...
Click to collapse
First 4.3" high-end device and now official AOSP? Sony, you might just make me a Sony fanboy
Does that mean that it could be possible to flash aosp based roms with locked bootloader? Or am I completely wrong here?
AFAIK the repository for current AOSP devices from sony does not contain camera drivers (and others). So don't expect to much from this news.
vriz27 said:
Does that mean that it could be possible to flash aosp based roms with locked bootloader? Or am I completely wrong here?
Click to expand...
Click to collapse
Unfortunately not
See the latest commits at the git. They are proving the new kernel branch is for sony devices
CoolDevelopment said:
See the latest commits at the git. They are proving the new kernel branch is for sony devices
Click to expand...
Click to collapse
If I'm reading the commits right, and I'd like to think that I am, then we are witnessing the official AOSP bring-up for the rhine-platform!
There's over a thousand lines of new camera code here: https://github.com/sonyxperiadev/kernel/commit/f721c1a0585ab6b9d3eb75a84bc2cf79a7813741
Get excited guys!
Rekoil said:
If I'm reading the commits right, and I'd like to think that I am, then we are witnessing the official AOSP bring-up for the rhine-platform!
There's over a thousand lines of new camera code here: https://github.com/sonyxperiadev/kernel/commit/f721c1a0585ab6b9d3eb75a84bc2cf79a7813741
Get excited guys!
Click to expand...
Click to collapse
That are the same drivers as from the stock kernel, don't expect these commits to increase our camera.
TheQwertiest said:
First 4.3" high-end device and now official AOSP? Sony, you might just make me a Sony fanboy
Click to expand...
Click to collapse
:laugh:
The newest commits are hinting on aosp for z2 aswell
Holy $h13!
How did i not see that before!?
I wasn't interested in devcon all that much. However, now since i know something like official aosp support might be announced there, I can't wait!
SONY GIB UNS AOSP UNTERSTÜTZUNG JETZT!
Sorry, couldn't handle the excitement
Its now official for Z1 and Z2 ! :laugh:
Xperia™ Z2 and Xperia™ Z1 added to AOSP for Xperia on GitHub
And somes good news for our Z1 compact plus other devices :
Xperia Z1 and Z2 added to AOSP for Xperia project; plus unified kernel announced
official ground for AOSP, sweet
I have a question.
Is there any benefits from this for people who has phone with locked bootloader and with -no allowed status? Or i just can congrats people who has unlocked bootloader?
mosespl said:
I have a question.
Is there any benefits from this for people who has phone with locked bootloader and with -no allowed status? Or i just can congrats people who has unlocked bootloader?
Click to expand...
Click to collapse
Only for unlocked bootloaders.
Nice , Tat is a good news.
Thanks for this share. Looking forward for this!
Something it's moving.. https://github.com/sonyxperiadev/device-sony-amami
Hello,
this thread is only for development discussion regarding development of android for msm8974. If you have anything useful, it's the right place, however, it's not for non-dev things.
Current state of cam:
working, though, still low quality. Will be fixed on v6. (and no videocam)
if you wanna have live chat, you can join an IRC
http://webchat.freenode.net/?channels=#freexperia
placeholder
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
SuperLamic said:
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
Click to expand...
Click to collapse
I don't know but I will try in next few days when I get more free time for installing sotck rom
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Click to expand...
Click to collapse
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
rcstar6696 said:
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
Click to expand...
Click to collapse
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
Click to expand...
Click to collapse
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
munjeni said:
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
Click to expand...
Click to collapse
If you read it again you will see that i talk about drm verity not drm keys
Test it if you want we had cm13 booting on 3.4 and it was only possible with display patches audio patches where only needed to fix some small sound issues
Chirayu desai one of the cm maintainer can confirm this.
Selinux is correct this needs to be rewritten and mmap too but i wanted to write it understandable for all guys not only for devs
The other thing about the camera hal is an info from alin but if you say he isnt correct then you will be right :good:
It could be possible that the cam will start without but not with all Features
Do what you want but i'm quite sure that you don't get a fully working cam
rcstar6696 said:
If you read it again you will see that i talk about drm verity not drm keys
Click to expand...
Click to collapse
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality can be noticed. I will definitelly go to 3.10 kernel till after camera gets working
mkdmc said:
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
Click to expand...
Click to collapse
Thats what I thinking now too! Did you tested, whats happening when camera.msm8974.so gets removed, is camera working? I need confirmation on rom 4.6.1.A.236 ! Which I found camera.qcom.so uses chocobal and excal blobs, camera.msm8974.so uses nothing from that.
rcstar6696 said:
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
Click to expand...
Click to collapse
Did you try to grep that file? For example
strings camera.msm8974.so | grep drm
You can see null results about drm
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
Click to expand...
Click to collapse
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
munjeni said:
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality
Click to expand...
Click to collapse
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
You can look into hammerhead source and you see some commits about drm verity too but hammerheads cam libs are not included in the verity
I have castor and sirius
---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------
nailyk said:
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
Click to expand...
Click to collapse
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
rcstar6696 said:
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
Click to expand...
Click to collapse
Where you found that info? Any log about it?
munjeni said:
Where you found that info? Any log about it?
Click to expand...
Click to collapse
Ask alin Jerpelea or chirayu deasi all infos i give too you are from them
For drm verity just use google :/
nailyk said:
screen flickering issue[/URL] it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge
Click to expand...
Click to collapse
I'm oticed frezings and some strange things using that msm8994 display hal, but on my buld I have used codeaurora LA.BR.1.3.6_rb1.3 branch for display, camera and some things in media, I can confirm that display things fly, its soo smoth, video soo smooth, screen power off/on smooth... if you want to try here is it http://munjeni.myiphost.com/mynougat.tar.gz , don't forget to build kernel with script buildkernel.sh since it will install kernel headers from 1.3.3 and will build 1.3.3. kernel too. I have told jerpelea about it but no reaply about LA.BR.1.3.6
rcstar6696 said:
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
Click to expand...
Click to collapse
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
nailyk said:
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
Click to expand...
Click to collapse
Just use nougat and everything from sonyxperiadev instruction page, its kernel 1.3.3 which is very good, extract things from mynougat.rar to android tree, build kernel with script buildkernel.sh (you will need some path modification to it), and the rest like mentioned...
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
Progress is being made many of the bugs are beginning to get fixed
Oreo roms that maybe created:
Lineage 15.1 (highly likely)
Nitrogen Os (by me and @ReversedPosix)
Bugs fixed in oreo generally:
Sound
Rild
Sim card ---->
Fixed By @Quarx2k (Telegram)
Bluetooth ---->
Thanks to these people this is possible @Olivier @ReversedPosix @EnesSastim @Myself5,
XDA:DevDB Information
Test developming, ROM for the Sony Xperia Z5
Contributors
Quantumkk123, QuantumKK123, Zacharias.Maladroit, olivier
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Aosp
Version Information
Status: Alpha/Beta (More things are working now)
Beta Release Date: 2018-05-05
Created 2018-05-10
Last Updated 2018-08-04
@Quantumkk123
you already got the ROM hooked up ?
please upload somewhere & write me a PM so I can take a look at it,
currently busy so kernel has to wait
Atm I think @zacharias.maladroit is reviewing the rom looking to edit the kernel so this rom can work on our phones I think also a few things need to be edited but yeah we might have an unofficial oreo Rom for the z5 and it will be the first
@Quantumkk123 top work! By seeing the features you listed, is this rom based on AOSP but with stock oreo things? :silly:
@zacharias.maladroit take your time. We just want this to work without irritating you guys. Nobody will ask for ETA. :silly: :highfive:
@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.
Quantumkk123 said:
@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.
Click to expand...
Click to collapse
Ok, I got it!
Quantumkk123 said:
@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.
Click to expand...
Click to collapse
At first glance this definitely looks nicer, the issue might be in the details though :silly:
Thanks
zacharias.maladroit said:
At first glance this definitely looks nicer, the issue might be in the details though :silly:
Thanks
Click to expand...
Click to collapse
So @zacharias.maladroit whats happening how much of this rom needs to edited to fully work and how is the kernel doing?
Quantumkk123 said:
So @zacharias.maladroit whats happening how much of this rom needs to edited to fully work and how is the kernel doing?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76479481&postcount=30
&
CONFIG_BT_MSM_SLEEP -> bluetooth driver differences
CONFIG_MSM_DCC => ?
CONFIG_QNS_SYSTEM=y
CONFIG_QUOTA=y
CONFIG_QUOTACTL=y
CONFIG_SDCARD_FS=y
CONFIG_SPLIT_PTLOCK_CPUS=999999
CONFIG_DEBUG_SPINLOCK_BITE_ON_BUG=y
# CONFIG_DEBUG_SPINLOCK_PANIC_ON_BUG is not set
CONFIG_MSM_RTB_SEPARATE_CPUS=y
CONFIG_PROC_PID_CPUSET=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y (quotas)
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_QUOTA_TREE=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MSM_HSL_CONSOLE=y
ours:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CSVT=y
theirs:
# CONFIG_USB_SERIAL is not set
--- /dev/null
+++ b/arch/arm64/configs/diffconfig/suzu_diffconfig
@@ -0,0 +1,7 @@
+CONFIG_MACH_SONY_SUZU=y
+CONFIG_NFC_PN547=y
+CONFIG_QPNP_SMBCHARGER_ID_POLL=y
+CONFIG_TOUCHSCREEN_CLEARPAD=y
+CONFIG_USB_MIRRORLINK=y
+CONFIG_TOUCHSCREEN_CLEARPAD_I2C=y
+CONFIG_TOUCHSCREEN_CLEARPAD_RMI_DEV=y
--- a/arch/arm64/configs/msm8994-perf_defconfig
+++ b/arch/arm64/configs/msm8994-perf_defconfig
@@ -243,13 +243,14 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_USB_USBNET=y
-CONFIG_CNSS=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
-CONFIG_CNSS_MAC_BUG=y
-CONFIG_CLD_LL_CORE=y
CONFIG_ATH_CARDS=y
CONFIG_WIL6210=m
CONFIG_E1000E=y
+CONFIG_CNSS_PCI=y
+CONFIG_CNSS_MAC_BUG=y
+CONFIG_CLD_LL_CORE=y
+CONFIG_BUS_AUTO_SUSPEND=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
diff --git a/arch/arm64/configs/msm-perf_defconfig b/arch/arm64/configs/msm-perf_defconfig
index bfe14733b104..12a8d65cf3cd 100644
--- a/arch/arm64/configs/msm-perf_defconfig
+++ b/arch/arm64/configs/msm-perf_defconfig
@@ -220,7 +220,6 @@ CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
CONFIG_MSM_BT_POWER=y
CONFIG_CFG80211=y
-CONFIG_NL80211_TESTMODE=y
CONFIG_CFG80211_INTERNAL_REGDB=y
CONFIG_RFKILL=y
# CONFIG_NFC_QNCI=y
@@ -270,9 +269,11 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_WCNSS_CORE=y
+CONFIG_CNSS_SDIO=y
CONFIG_WCNSS_CORE_PRONTO=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
CONFIG_WCNSS_REGISTER_DUMP_ON_BITE=y
+CONFIG_CLD_HL_SDIO_CORE=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
@@ -288,8 +289,6 @@ CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI4_DEV=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE=y
CONFIG_SECURE_TOUCH=y
-CONFIG_TOUCHSCREEN_BU21150=y
-CONFIG_INPUT_MT_WRAPPER=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_HBTP_INPUT=y
CONFIG_SENSORS_MPU6050=y
@@ -305,6 +304,7 @@ CONFIG_SENSORS_ISL29044A=y
CONFIG_SENSORS_CAPELLA_CM36283=y
# CONFIG_SERIO_I8042 is not set
# CONFIG_VT is not set
+CONFIG_SERIAL_MSM_HS=y
CONFIG_SERIAL_MSM_SMD=y
CONFIG_DIAG_CHAR=y
CONFIG_HW_RANDOM=y
@@ -611,3 +611,4 @@ CONFIG_SPDM_SCM=y
CONFIG_SECCOMP=y
CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE=y
CONFIG_UID_CPUTIME=y
+CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
Click to expand...
Click to collapse
that'll get you an idea:
kernel-side:
bluetooth might be a problem, we need sdcardfs, our SoC/processor might lack certain parts that are necessary for functions of the ROM (DCC "MSM data capture and compare engine" and others),
binder needs updating,
display driver (?),
matching gpu driver (kernel-side) & adreno blobs (ROM-side)
we might need different kernel modules built for the ROM & subsystems might require rework (see attached list of kernel modules)
ROM-side:
modem needs to be replaced (M-ROM 2.4.8 by nreuge has those files in system/etc/customization/modem ),
ril / qcril might need work
wlan (system/firmware/wlan/bcmdhd) firmware might need to be replaced with ours
system/etc/wifi/wifi_txpower.conf might need modification
system/compatibility_matrix.xml might need changes
where is system/etc/mixer_paths.xml ? => system/vendor/etc/
system/vendor/lib{64}/{egl} adreno related libs need to be checked out - the driver most probably won't work with kernel-side
fingerprint & nfc libraries need to be evaluated [later]
msm_irqbalance, thermal, etc. all crucial subsystems and configurations need to be double and triple-checked before even attempting to put it on the device.
[I got a terrifying moment today while modifying MHL driver and got strange noises out of the phone & speaker - better safe than sorry]
That's only a first (and most likely incomplete) pass through the ROM files
So @zacharias.maladroit I am guessing their is a lot of work to be done well just asking how long will this take is it possible you are able to do all these modification yourself or do you need help from other devs? If you are able how long will It take I can also help out but not today or tomorrow busy with exams lol
Quantumkk123 said:
So @zacharias.maladroit I am guessing their is a lot of work to be done well just asking how long will this take is it possible you are able to do all these modification yourself or do you need help from other devs? If you are able how long will It take I can also help out but not today or tomorrow busy with exams lol
Click to expand...
Click to collapse
No ETA, I'll defer work since I need to focus on personal affairs right now, I can do some random kernel development (or rather: have to since this gives me my occasional "fix") but that's about it ... at least for now
I've pointed out the important points that need work but won't be able to do anything right now since other things need my full attention at the moment
edit:
to answer you question:
yes, help definitely would be appreciated and is required,
I won't do this on my own - since the M-ROM 2.4.8 variant for now is enough that I ask for, I'm mostly focusing on kernel work to get an optimum of performance, stability, security vs. battery runtime,
perhaps @GreyLeshy and additional folks/devs/users like @trax7 have interest in taking a look at this ...
OK welll thanks for all your help we all really appreciate it @zacharias.maladroit hopefully other devs can fix what needs improving as you have thankfully told us and they can fix it and maybe when you have more times on your hands you can fix everything
Great so to all devs out there who own Z5 of course please contribute and help make the first oreo Rom I will make.sure you get pointed out credits if you help Bro @enesstastim and others as well
Quantumkk123 said:
Great so to all devs out there who own Z5 of course please contribute and help make the first oreo Rom I will make.sure you get pointed out credits if you help Bro @enesstastim and others as well
Click to expand...
Click to collapse
We also need to document each and every step and what modifications are necessary so that others can easily reproduce
First and foremost:
what ROM base did you use ?
(MaChao_44) Xperia XP V1.1.5(Android O).zip ¹
or
(MaChao_44) Xperia XP V1.4(Android O).zip ²
?
(I'm guessing the first one but not sure)
https://forum.xda-developers.com/showpost.php?p=76476528&postcount=25 ¹, ²
thanks to @turnout96 for helping out with the download & upload
Version 1.4 @zacharias.maladroit
Quantumkk123 said:
Version 1.4 @zacharias.maladroit
Click to expand...
Click to collapse
Oh good, cause I accidentally compared your mod with that ROM
Only was wondering because a few files were differing that weren't obvious
@zacharias.maladroit oh lol so the changes won't be as different as you thought?
Quantumkk123 said:
@zacharias.maladroit oh lol so the changes won't be as different as you thought?
Click to expand...
Click to collapse
They are just like I wrote before - but just with a few additional files less to worry about
still pretty difficult - this needs quite a few experienced devs to do it (or quite some learning by doing ...)
Would it be possible to use some of the drivers (gpu for example) from roms of other devices?
The OnePlus 2 has the same Snapdragon 810 SoC and there are some Oreo roms available already.
Maybe merging parts of the X and OP2 rom could help?
I dont have any experience modifiying aosp, so if Im worng, just ignore my thoughts.
brothers anyone screenshot this rom thanxxxxxxxx
I decided it might be time to post this kernel as it's starting to take shape. It started life as an Xperiadev unified kernel with some modifications like memutils, it was used by Omnirom that saw a release for the Z1 using kernel 3.10, but had not seen an update since 2016 or so, since that's not something I could live with I decided on Codeaurora-msm-3.10-LA.BR.1.3.7_rb1.9 as a valid subject for purging updates from.
Currently my android-7.1 branch is stuck on the boot logo on Z1 (now led changes color and it reboots, instead of stick on logo before) and finding the issue has taken longer than expected, somewhat due to my relaxed approach this time. The code for supporting all Xperia devices all looks good but I have only Z1 and Z5 to test, for now I've focused on the Z1.
I've forked Xperiadev LA.BR.1.3.3_rb2.14 and testing changes, most surprisingly what i considered a small and important update to the iommu code resulted in a locked kernel, it is certainly not the easily spotted mistake i've been looking for that's at fault with my branch and so this will be my testbed for the code i find functional .
Results thus far:
Xperiadev unified LA.BR.1.3.3_rb2.14 with changes from Codeaurora merge:
https://github.com/threader/kernel , set default to LA.BR.1.3.3_rb2.14
git clone https://github.com/threader/kernel.git
https://github.com/threader/kernel
A speculative merge too far, so far:
git clone https://github.com/threader/android_kernel_sony_msm.git -b android-7.1
https://github.com/threader/android_kernel_sony_msm/tree/android-7.1?files=1
Used for updated qcom device driver code :
git clone git://codeaurora.org/quic/la/kernel/msm-3.10 -b LA.BR.1.3.7_rb1.9 (I also used LA.BR.1.3.7-01310-8976.0 )
threader said:
I decided it might be time to post this kernel as it's starting to take shape. It started life as an omnirom kernel for all Xperia devices, this had not seen an update since 2016 or so, since that's not something I could live with I decided on Codeaurora-msm-3.10-LA.BR.1.3.7_rb1.9 as a valid subject. Currently I'm stuck on the boot logo on Z1 and finding the issue has taken longer than expected, somewhat due to my relaxed approach this time. The code for supporting all Xperia devices all looks good but I have only Z1 and Z5 to test, for now I've focused on the Z1.
I'm working on the android-7.1 branch.
Any ideas?
https://github.com/threader/android_kernel_sony_msm/tree/android-7.1?files=1
Click to expand...
Click to collapse
Don't bother. That is based on Sony's Open Devices Project, which was a good concept but did not provide any sort of usability whatsoever for msm8974 devices. Stick to 3.4.x and forget about unification.
drakonizer said:
Don't bother. That is based on Sony's Open Devices Project, which was a good concept but did not provide any sort of usability whatsoever for msm8974 devices. Stick to 3.4.x and forget about unification.
Click to expand...
Click to collapse
I'm noting difficulties and riddles of #ifndef msm8974 but the omirom 3.10 kernel is not running badly, the camera has issues i noted, and i feel 3.4 has the attention of others.
Regarding the unified project, i started looking at the latest branch for legacy, if i remember correctly the correct branch for legacy is LA.BR.1.3.3_rb2.14, i feel i can compare and move code around with some confidence compared to an older version.
https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BR.1.3.3_rb2.14