Related
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
Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)
This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..
You can find us on https://lineage.microg.org
XDA:DevDB Information
LineageOS for microG, ROM for all devices (see above for details)
Contributors
Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
Source Code: https://github.com/lineageos4microg
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-11-06
Last Updated 2020-08-28
Would like to have build for Nexus 9 aka flounder
Awesome start! Good luck with that! Cheers! :fingers-crossed:
Is this the thread mentioned in the FAQ where one can request builds for other devices supported by LineageOS?
If so, I'd love to see a build for the LG G5 (aka h850), which is currently the only high-end device by a known manufacturer with a removable battery and high repairability (8/10 from Ifixit).
It's fully supported by LineageOS (https://wiki.lineageos.org/devices/h850) and I'd be willing to report any possible problems and help debug it if necessary.
Thanks in advance and awesome project!
Can you please add support for LG G4 (H815) as well?
The LineageOS for microG OTA infrastructure is based on https://github.com/julianxhokaxhiu/LineageOTA?
I'm mounting my own infrastructure and I want to know how to build it. Thanks.
Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
Simon94 said:
Current device list which will be built tomorrow:
Code:
a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
Click to expand...
Click to collapse
Please, include piccolo!
DaniPhii said:
Please, include piccolo!
Click to expand...
Click to collapse
Done!
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
sandeep_7 said:
@Simon94 does it supports substratum ? and thanks for the modded lineage .
Click to expand...
Click to collapse
Same feature-set as LineageOS. If LOS supports substratum, we are supporting this aswell.
Silver_Defender said:
Microg.me is a really wonderful project , I have been using it for 3 days, but there are some things that annoy me. In particular, is it really necessary to implement it in every single build ?? I use an application with the same signature, so at each ota it is replaced by the fakestore and that's annoying . Also one ota per day is pretty excessive I think, especially for daily usage. Why not release an update at the same time as the official lineage ?
Please excuse me if the answers to my questions are obvious, I'm a bit new on microg.
Click to expand...
Click to collapse
Unfortunately we wont remove FakeStore since our goal is to provide a Google free ROM with a fully working ecosystem which requires having FakeStore installed. Sorry for that. What you could do is to write a script for OTA survival / - or removal and put it in the /system/addon.d directory. But we're not going to support this in any way.
Otherwise we can invite you to not use Play Store, but a replacement like Yalp Store.
We like to build as often as we can. Its up to you and your free choice. If you dont want to update on a daily basis, just dont do it
Best, Simon
MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
..
https://lineage.microg.org/#faq said:
Can you add support for my device? It is not supported by LineageOS though...
No, I'm sorry.
Click to expand...
Click to collapse
MaStErB_1984 said:
Would it be possible to built a pac which could be used for an unofficial LOS-Release to install it e.g. via twrp? I would to love to test the microg-package onto my satsuki (E6833) Sony Xperia Z5 Premium Dual
Click to expand...
Click to collapse
There are several methods to get microg. Maybe you should start reading there https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
My preferred method have been nanomod patcher and shadow53's zip.
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
Shashank Varma said:
I can't find my device in the download section!! Yu yunique (jalebi). As the site says that all the devices with official linegae os support will get this rom?? Pls provide for my device jalebi. Thanks in advance.
Click to expand...
Click to collapse
Added in next build.
Simon94 said:
Added in next build.
Click to expand...
Click to collapse
Thank you!! Waiting for it
Hey there! I have an old first-gen Moto X as my main android device (ghost) and I'd love to take advantage of your awesome project! I tried to get the docker image up and running myself, but I keep getting random DNS failures in docker, which seem to get silently passed, which results in the build claiming to be successful, yet no builds show up in my "zips" folder when it completes. Only thing that I think needs changed from the default is the lineageOS branch (cm-13.0). Would it be too much trouble to add 'ghost' to your list of builds?
Thank you,
neutral
Can you add support for taoshan (Sony Xperia L)?
Has LOS support.
Thanks!
Moto g5 cedric?
Code:
#include <std_disclaimer.h>
/*
* 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. Please
* do some research if you have any concerns about features included in it
* 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.
*
*/
What is Project Treble
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition.
About
Weijianism did not build any verdor image of new version because he does not own this device. Although I am not familiar with android source and android build, I am very happy to learn it so that we natrium owners can use project treble.
So I message to Weijianism to know how to do it and have learnt it for a few weeks. Now I am trying to build vendors. Cause I still know a few about it, It is really very hard for me to solve problems in myself. So if you have any advice, please tell me or push you code in github. THANK YOU!
What is NOT WORKING
Camera
Let's test it together.
Download
ALPHA 0815 (boot.img + vendor.img)
How to
1. wipe everything using TWRP
2. flash boot.img + vendor.img
3. flash system.img
4. reboot to system
Sources
Kernel for msm8996 (lineage-15.1)
Configuration for natrium (lineage-15.1)
Configuration for msm8996 (lineage-15.1) (Minor patches)
Proprietary vendor (lineage-15.1) (Minor patches, forked from Weijianism , credits MZO)
XDA: DevDB Information
Project Treble for Mi 5s Plus
Contributors
Justin_hill
Weijianism
Thanks to
LineageOS
Mi 5s Plus devs
@Weijianism
ROM OS Version: 8.x Oreo
Rom Kernel: Linux 3.x
Version Information
Status: Testing
Created: 2018-08-13
Last Updated: 2018-08-16
Anyone try ?
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
1. bootloop problem solved when using rr gsi. (code from hacker1024)
2. bluetooth service stoped problem solved.
QuiseShampe said:
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Click to expand...
Click to collapse
The camera's problem seems very hard, I will try to use GCam later. Now I do have no idea about how to solve it.
You may help me solve it if you like!
pote2639 said:
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
Click to expand...
Click to collapse
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
justin_hill said:
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
Click to expand...
Click to collapse
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
pote2639 said:
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
justin_hill said:
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
Click to expand...
Click to collapse
I guess I'll wait for android p stable sgsi build then.
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
rhp_engcoy said:
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
Click to expand...
Click to collapse
Hope for me get a new natrium and I'll do for capricorn and natrium too.
Ofc, as justin did for natrium already, I'm gonna just ship it on my custom ROMs projects, not separated things like capricorn should get it too.
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
theOriginalSuperl2 said:
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
Click to expand...
Click to collapse
Yeah, your code have inspired me a lot when I saw your repositories.
Maybe I fixed the bluetooth problem when I add back the libbtnv.so to /vendor/lib/ since it was deleted in this commit.
For the camera problem, I don't know how vendor module relates to kernel. But I will try it afterwards.
Actually I almost know nothing about lineage source code, system build skills and things like this. If you can help, it will be grateful!
any news on the development?
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
About treble support I can tell that I'm gonna include in my ROMs, and maybe I'll give some vendor zips too, if @justin_hill doesn't care about that.
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
Sorry, I am trying to do something about Treble for Android Pie, But there are still several problems unsolved. Cause I'm not familiar with those code, so maybe I can't solve it by myself. It will be so grateful if anyone can contribute to it.
So we will expect @Hlcpereira WORK, Thank you so much!
Hey, is the camera problem solved?
It can't be booting on any sgsi so what should i
do
Hello
For the past couple (weeks) I've been trying to compile Android 10 for tenderloin using the Android 9 sources but it's not going so well. First thing I ran into multiple sepolicy errors and I feel as if I fixed them in inappropriate ways but the errors went away. Other errors regarding camera and audio and such, that are regarding that tenderloin no longer uses the legacy audio format. Made me confused because I used the device sources form Evervolv and DIrty unicorns and if i'm correct they built it exactly the same way they uploaded it. After these errors were wrapped up, I got a error at zipping the rom that it could not zip due to failure of being able to read build.prop. This made me believe that the sources are not correctly formatted. If anyone can help me find a manifest, I can build for all you guys. Please keep tenderloin alive!
Now, I did something and I'm getting plenty of perl errors. Maybe I'm just very unlucky. I'm gonna attempt to reinstall on a fresh drive on my server.
If its anyone's concern, I was building lineage 17.1. I noticed for example, Lineage's "qcom-device" repo was shaped completely differently than Evervolvs qcom-device repo.
This led me to thought that Android 10 is going to be extremely difficult because of all the upstream dev changes that was pushed to Q. If any of you would like, I could probably push out March patches Pie rom because over there I'm mostly safe of complying with the source.
My manifest shape
DirtyUnicorn's device-tree
DirtyUnicorn's device-tree-common
DirtyUnicorn's htc-msm8960-kernel
Evervolv's vendor
And dirty unicorn's atheros wlan driver
I have been changing up the device tree so much, it almost looks ridiculous . From what I heard lots of properties on the device tree haven't been touched for years. Maybe tomorrow I can try Evervolv's Q rom. If you guys can help me build up my manifest, we can push out a fully working Q rom for tenderloin. And it would be just in time when Android 11 comes out. Thank you everyone!
I wish that I could offer any help, but I never tried to compile any Android ROM or for the HP_TP.
To my knowledge the only users that I know that could offer some insight on the process would be:
@flintman
@elginsk8r
Also the LuneOS project could offer some help:
https://pivotce.com/tag/luneos/
If Android Q(10) can not be ported to the HP_TP, then at least P(9) is a good ROM to keep updating that could provide many years of App support.
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
djared704 said:
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
Click to expand...
Click to collapse
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
HP_TOUCHPAD said:
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
Click to expand...
Click to collapse
When I look at the tenderloin source, the script to gather the camera driver is disabled. Camera isnt a huge deal though because its only 1.3 MP. However we use the MSM 8960 kernel from HTC and that is the one m7,, but the one m7 is a SD 600 device so it loses sense. I was gonna get some help with one of my kernel developer buddies to dev a kernel for android 10 for tenderloin. If you see the one m7 has Lineage 17.1 available and even though it doesnt have same chipset, if im correct both chipsets went off of the same assembly line process. Lineage 17.1 for the one m7 also packages it as a "uimage" which is what we use. I believe this was only a very small select of devices. Yeah about that ive been getting so many complaints during build about "mkimage" which should've been a prebuilt tool in the lineage source. Don't know why they removed it, or if our developers added it in by their selves, etc. Anyways I fixed that error by just "allowing" mkimage in one of the permission files in my environment. But yeah i went as far as the build packaging the ROM and it complaining it cannot read build.prop. Note the build.props are generated by the environment , not the source (even though the device data is gathered by the source, its not what im talking about). I even go to the directory it was complaining about and it was all there. One of my friends suggested a permission error. I changed permissions to 777 (rw to all users) and it would still output that error. By that point I trashed my build meaning I may of done something wrong early on. I will let someone else continue building 10 but I will continue building 9 with latest patches.
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
HP_TOUCHPAD said:
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
Click to expand...
Click to collapse
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
djared704 said:
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
Click to expand...
Click to collapse
I have only recompile the Kernel and all of them work, but the correct branch must be use. I can not say about building a ROM, never done it.
But Evervovs Pie by elginsk8r works very well and stable as it uses the same kernel, but the framework is different. I guess elginsk8r will be the only that can guide you on the right direction or flintman.
Have fun learning, it takes a lot of TIME!