Database Users

[Q] ROMs using JustArchi's optimizations

Hello
I was wondering if there are any Nexus 4 ROMs using JustArchi's optimizations (link). I did my best to compile OmniROM with these fixes, but I am not very experienced with Android development.

+1 to this post

Looks like our devices are too fast to use these "insignificant" compiler optimizations
I'll give my 5 cents these days to try compiling it..
Cheers

+1 for this thread.. I asked just the same thing in the general Q&A thread and nobody answered.. I'd like to see CM, ParanoidAndroid...etc.. built with ArchiDroids optimizations..

Like to see that too!
I've been searching for a rom with f2fs support + JustArchi's optimizations. Can be possible?

I created a topic earlier here
opssemnik said:
i can tell from personal experiences, its mostly placebo, tried archi´s rom on my gs3, and aside from the fact that the google camera dosent crash after first shot(witch occors on alot of roms ,even official cm, again on my s3), the rom is same speed, if not less than official cm. (on my s3 i9300)
Click to expand...
Click to collapse
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?

joefso said:
I created a topic earlier here
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
Click to expand...
Click to collapse
yeah i saw those,luck for them, thats why best rom threads are not allowed on xda, people get different results on their devices ,i plan to compile aosp with those just to test on the n4, but i doubt i will :/

No one is going to try this anytime soon.
The code is no where near perfect and it sets up an environment where there is a lot of room for errors which will result in VERY bugy, glitchy, crashing Roms.
The code is really sloppy and so far only JustArchi is the only one that has successfully used this in a ROM with out error.
There is still a lot of going back and forth in whether this really works since android isn't 90% thumb
All this is good for is benchmark scores. Just like F2Fs its all placebo in real world performance.
With a quadcore 2 gig phone... You're not missing much.
Legecy devices will benefit in the least from this.
Sent from my SM-T217S using Tapatalk

First build is ready!
It is mako-userdebug.
I used Linaro toolchain(JustArchi's link) and JustArchi "JustArchi's ArchiDroid Optimizations V3" - https://github.com/JustArchi/android_build/commit/d8cc50d2472e497b431b5652516c9248ad7f3947
It is without Gapps (so PA Gapps must be used).
Build Env :
Debian GNU/Linux testing (with make downgraded from 4.xx because AOSP lunch require this).
AOSPA soruces 4.4.2_r1 used for the build.
No ART patches! ART will fail if you try using it.
Will test this today on my phone, and if successfully boot, I'll post a link for the ROM.
p.s : From back these days, where people find that AMD64 arch is here, Linux builds started to optimize the speed of your GNU/Linux for your specific CPU (Gentoo for example, or Debian GNU/Linux moved from i386 to i686 and after that to AMD64). Well, the tests and builds performance charfs finished with this : improvement of the speed was was something like 0.6/0.9% ... So in the real world reality do not expect much from this!
Regards ...
Edit:1
Boot failed
Next time, I'll enable the proprietary drivers in the build.
Currently new build is running with enabled prop drives settings like:
Source:http://nosemaj.org/howto-build-android-nexus-4
To use these proprietary files, comment out this line in device/lge/mako/full_mako.mk:
#PRODUCT_RESTRICT_VENDOR_FILES := true
Cheers!

[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1]

This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21

Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128

Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.

Reserved

Reserved

Thanks, working great on CM12.

Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.

Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?

Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.

Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom

Thanks, I will use your kernel on my chagallwifi SlimLP builds

Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks

SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though

deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe

diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.

meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective

diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.

meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated

diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.

meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025

[DEV-ONLY][Z1-Z3][3.10 kernel][MSM8974/SD800-1] Custom ROM development

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...

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.

Regarding Android 10 on the HP Touchpad

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!