Hello guys,
i am looking for some custom rom for my x910 leeco.
Could i use maybe lineage os, z2 for that?
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
ThE_MarD said:
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
Click to expand...
Click to collapse
any update ?
Cateye said:
any update ?
Click to expand...
Click to collapse
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Keep working please. We count on you.
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
xaakx said:
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
Click to expand...
Click to collapse
Heyyo, can you please get me logcat from the start of the device booting? I've tried importing all 18 max_plus dts/dtsi files I saw in the kernel but that still didn't get it to boot.
https://github.com/LineageOsMaxPlus...mmit/7eb4dbf827bba4e05de2a802b6fc2b05741b04b9
Here's so far everything I've tried to do
https://github.com/LineageOsMaxPlus
I've been thinking of upgrading my nearly 2 year old x910 since I've been stuck on this hacked chinese rom version of android 6.0.1 (Kernel version 3.18.20 from April 29, 2016). Apps are starting to crash or drain battery, etc
Is there anything I can do? I know X910 was some sort of engineering sample run and never mass sold. I was lucky enough to find one on aliexpress for about $280 2 years ago. Been a great phone but Android 6 is killin me now.
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
ThE_MarD said:
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
Click to expand...
Click to collapse
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
xaakx said:
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
Click to expand...
Click to collapse
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
https://youtu.be/TYfFmDjOQnk
Hello sir
A noob here with x910
Please tell us that should we hope for a stable custom rom on this device like we have on le max 2?
Heyyo @King Ibsd , I am still trying to work on it! :good:
I do have unified builds with X2 working, so that part is good to go! Just need to resolve this panel issue hmm...
I forgot to mention this earlier... But if you're really interested in trying experimental max_plus unified with X2 builds? The last few builds I've posted in the X2 thread are unified with max_plus... But be warned, it has serious video lag as noted in that YouTube link up above.
There is a chance your max_plus has a blank devinfo block which isn't good as we check that for many things on custom ROMs.
If yours is blank? Please flash this via TWRP to correct it to max_plus.
https://drive.google.com/file/d/0B7RnSWm3LBorZ1NzNmtrcmNlV1ZzZ3U0WFdWQnF4bXB0Sm80/view?usp=drivesdk
Hmm, I think the signed graphics firmware I was given for max_plus is REALLY out of date and could be the reason for the video lag...
Can someone here please link me the latest version of EUI ROM that works for max_plus?
ThE_MarD said:
Can someone here please link me the latest version of EUI ROM that works for max_plus?
Click to expand...
Click to collapse
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Palm Trees said:
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Click to expand...
Click to collapse
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
ThE_MarD said:
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
Click to expand...
Click to collapse
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Palm Trees said:
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Click to expand...
Click to collapse
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
ThE_MarD said:
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
Click to expand...
Click to collapse
I collected the x900(乐视_X900)/x900+ (乐视_X900加)/Le Max fastboot images (all models are msm8994 "Snapdragon 810"). So I do believe LeEco was lazy when they created the msm8996 phones. As far as I can tell, LeEco was the first company (or one of the first) to use msm8996. So they might have said "Yeah well, let's move from msm8994 to msm8996 without changing stuff" in the NON-HLOS.bin.
If you want to compare the NON-HLOS.bin from the msm8994 phones with the other NON-HLOS.bin files from the msm8996 phones here are the links and descriptions:
1523500103_MAX1_X900 CN FN CEXCNFN5902803208S 5.9.028S //latest fw release (not fastboot images)
Source: http://bug.letv.com/cn/download/phone/32
Direct DL-link: http://ota.scloud.lfengmobile.com/ota/1523500103_MAX1_X900-CN-FN-CEXCNFN5902803208S-5.9.028S.zip
ro.letv.release.version=5.9.028S
ro.product.letv_model=Letv X900+
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-01-01
ro.build.date=Tue Mar 20 20:00:44 CST 2018
ro.product.model=X900
ro.product.brand=Letv
ro.product.name=max1
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.date=Tue Mar 20 20:31:41 CST 2018
ro.bootimage.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/test-keys
Geekbuying posted the Indian firmware. The .zip file and general description are incorrectly tagged. Nevertheless, it is in fact the Indian Le Max firmware for msm8994 based on Android L 5.0.2.
LETV X900 LE MAX PRO Snapdragon 820 Quad Core Android 5.1 Smartphone Firmware
Should be tagged something like this LeTV X900 5.5.014S 5.0.2
Source: http://blog.geekbuying.com/2017/08/...ore-android-5-1-smartphone-firmware-20170818/
DL-link:http://www.mediafire.com/file/h8276...oid+5.1+Smartphone+Firmware+-5.5.014S-5.0.zip (Password: geekbuying.com)
# begin build properties
ro.letv.product.info=Max1_r1148.5-5.0.2-userdebug_CHN-OPEN-Dev
ro.letv.release.branch=x1_stable_011_20160125
ro.letv.release.version=5.5.014S
ro.build.date=Sun May 22 03:29:13 CST 2016
ro.product.model=Le Max
ro.product.name=LeMax_WW
ro.product.device=max1_in
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_WW/max1_in:5.0.2/CHXOSOP5501405221S/154:user/release-keys
The Chinese firmware below is pretty much comparable except for a few differences in system.img (some apps are included/excluded). Unpacking the boot.img did show comparable ramdisks.
乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
Source:http://url88.cn/Jk9eBy
Direct DL-link:http://rom.url88.cn/{3705256}_乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
ro.letv.release.version=5.5.009S
ro.product.model=X900+
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Source:http://url88.cn/1a9Cpmr
Direct DL-link:http://rom.url88.cn/{3704883}_乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ro.letv.release.version=5.5.009S
ro.product.model=X900
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ThE_MarD said:
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
Video lag for the twrp is completely gone after adding few additional lines that were missing from maxplus device trees as compared to similar dsi panels of Max 2 in your test rom. Following are the additional lines for my device panel mdss_dsi_sharp_qhd_dualdsi_cmd from MSM 8996 v3 + PMI8994 LE_X2_NA-DVT1.1 which looks similar to my device tree dvt3.
qcom,mdss-mdp-transfer-time-us = <0x2710>;
qcom,ulps-enabled;
qcom,config-select = <0x2c>;
config0 {
qcom,split-mode = "pingpong-split";
linux,phandle = <0x2c>;
phandle = <0x2c>;
I couldnt add last two lines for phandle nodes as they are found else where as well. The most important line that fixed the lag of twrp is qcom,config-select = <0x2c> which looks specific to my device. I tried to boot the rom after flashing modified boot without those last two lines for phandle nodes, but the phone screen goes blank while booting. Interestingly, config select and phandle node values are same for pingpong split modes and they are in the range of 0x2a to 0x2f . Once you incorporate these lines with the appropriate pingpong split mode, hopefully the rom should work without any lag as well. Looking forward to next build soon....
Click to expand...
Click to collapse
Related
So FIXED on CM based Nougat roms: only change the media.msm8956hw=1 to 0 in the build prop.
Tested with Lineage, Xenon, NitrogenOS. I think when it's enabled the VR playing quality wrong.
This method wont working on MIUI, because 0 is the default value.
How to fix on MIUI 9.5: post
Hi members! Redmi Note 3 Pro QA
So a simple question and remark. I'm using Var's VR Video Player. This is one of the best optimized player at the moment for all VR formats. Tested a lot of players, the quality as the same with others, so the next problem is not an app problem.
VR video quality is very good in the older MIUI v7.1.x.x and 7.2.x.x roms (not tested all MIUI roms) and Krexus (build 3) rom.
Tried on other roms (I think in all roms), and the quality is not as good, not as sharp the picture. Blurred the edges and the lines not as sharp. All other roms, new MIUI's, all CM base and AOSP roms this happening. Tried to change some encoding options in the build.prop, like in Krexus rom, but not helped.
In Krexus the quality looks like when we disabling hardware encoding in the player app in the newest CM roms. Very good picture, looks like in PC. (but on this rom the hw encoding working).
Yesterday tried the lastest MIUI 8 MM rom, the quality as in other CM-s, but the seeking (stepping?) is very fast, at the moment playing. Not buffering 3-4 sec and not stopped the playing like in other CM and AOSP based roms.
I contact with the Var's player devs and finally we came to the conclusion, it's a rom bug.
Anyone experienced this? Or if playing VR anyone could to check Krexus rom? I don't think it's a simple value problem in some files in the rom, maybe a codecs problem?
So the 2 problem what need to eliminating:
- Hardware decoding quality improve, like in the Krexus rom
- Seeking improvement, like in the lastest MIUI 8 MM dev rom.
If I don't know about this quality problem I would not even notice, but always when trying in new roms I'm goes back to Krexus.
I'm not a dev, so only the testing, and this is in above, what I could to do. If you have an idea and it's not comlicated I'm trying, testing the metode in newer CM rom if this will help a bit.
UPDATE:
Made a screenshot on the systems (check the hills and the licence plate on the car):
Left: CM13 / Right: Krexus old
[url=https://postimg.org/image/o0byvant9/]
[/URL]
Logcat
Yesterday I checked 9+ roms.
Working this Krexus (the oldest build 3, in the new similar the problem). TheStrix CM14 build and a really old MIUI rom.
Not working: All CM13 and AOSP builds and similar modded roms, like Resurrection, Slim, Nexus Exp, Qualcomm AOSP, Exodus, Santhosh CM, Orion, DU, Temasek, iZi etc. On iZi the gyro not working in the app.
Any solution devs? Thanks.
Rom's which working good for VR, sharp image etc.
[ROM][CAF][23/10] halogenOS 7 for Redmi Note 3 [0.5-beta] - used the 0.5 beta release
[30/10/2016]CyanogenMod 14.0/14.1 for Xiaomi Redmi Note 3 - used the 30/10/2016 release
[ROM][LAYERS][KENZO] Krexus-CAF 6.0.1 (MMB29M) used the build3 (20160626) release
[CAF][1/16] [UNOFFICIAL] [halogenOS 7.0] [Kenzo] [VOLTE] by @rocknegi (first release - 2017/01/15)
On Androiddevs @Santhosh M ALL RR Nougat release (latest: 2017/01/17) !!
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
superboy123 said:
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
Click to expand...
Click to collapse
Only some older MIUI builds working good with this higher quality. That's why I tested the roms. On the picture is visible the difference (two system, cropped and merged the two screenshot) and from now it's not a brain trick. I'm using VR more than one year, making and editing videos, so have a difference with that.
If check the original channel VR official videos, on SBS 180 and SOS 180 videos have this issue with HEVC, but also see the differences on H264 . If only check youtube and simple 360 video the quality is very similar. So it's a codec problem I think. Btw thanks if you could help with the logs, which cause this affects thanks again
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Looking more into this, keep this update cause i just bough xiami VR, and i'm interested to know wich rom is better etc, Using umang unofficial cm13
superboy123 said:
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Click to expand...
Click to collapse
I suggest compare with Krexus build 3, as the same, older base.
Yes, I feel huge difference between krexus build 3 and CM13. looks like gpu does not render vr graphic well.
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
KreAch3R said:
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
Click to expand...
Click to collapse
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Steve1207 said:
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Click to expand...
Click to collapse
I took a look at the logcats. What I found was, that both cm13 and krexus-wrong build (the ones that don't work) use this driver:
10-09 15:57:32.843 I/Adreno (1223): QUALCOMM build : 2d489f5, I74772a33ad
10-09 15:57:32.843 I/Adreno (1223): Build Date : 08/04/16
10-09 15:57:32.843 I/Adreno (1223): OpenGL ES Shader Compiler Version: XE031.07.00.00
10-09 15:57:32.843 I/Adreno (1223): Local Branch : mybranch21158950
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : quic/LA.BR.1.3.4_rb1.17
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : NONE
10-09 15:57:32.843 I/Adreno (1223): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
While the only working krexus build uses this driver:
10-09 15:48:34.033 I/Adreno (9424): QUALCOMM build : 4ad80b1, Ibc10b8cc61
10-09 15:48:34.033 I/Adreno (9424): Build Date : 04/14/16
10-09 15:48:34.033 I/Adreno (9424): OpenGL ES Shader Compiler Version: XE031.06.00.02
10-09 15:48:34.033 I/Adreno (9424): Local Branch : mybranch19231206
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : quic/LA.BR.1.3.3_rb2.15
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : NONE
10-09 15:48:34.033 I/Adreno (9424): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
The changelog seems to agree with me, as you the dates make me assume that this commit is included in the broken build.
So maybe, what you can do is, try to grab all adreno libs from the working krexus, put them into another ROM and see if they work
I gave up for today. Made a flashable pack with the old libs, but dosn't work or when booting with other rom don't change the quality. But I'm trying again tomorrow, now search and read about this libs. Thanks your help @KreAch3R, I think helped a lot for the Kenzo developers with this, maybe someone fix this!
I just stopped using VR!
After trying MIUI and Krexus, CM's VR quality is so bad that I refuse to use VR glass.
UP
Hey all! Any news on this? I'm on miui 8 and was thinking about moving to cm based but now you guys are changing my mind.. I dont wanna lose vr for this, even though I dislike miui. Well, lets hope someone fix it. What about asking in their specific rom thread?
What about that krexus version that has good quality? Does it has any bug? Its safe for daily use?
Vr is not that popular so almost no one cares about development. Lets hope draydream changes that!
Steve1207 said:
UP
Click to expand...
Click to collapse
Hey bro does it fixed by that old adreno blobs? im in Miui 8 MM global beta does Miui 8 MM have also quality issues???
Not any news guys. I'll test the CM14 builds today, now looks like it's pretty stable as I read the threads.
Nice! Please report back to us any news. I moved to RR cm13 rom yesterday and did a little testing with my vr box 2, I actualy saw some improvement, in Miui 8 there was a lot of distortion, it's gone now, the quality still not good, haven't tested with old miui to tell the difference. What I noted is that performance is not that good in games anymore, there was some problems with fps, do you guys know what caused that ? I'm on raidon 3.9 kernel, default settings.
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
V-incent said:
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
Click to expand...
Click to collapse
Yep, I was having a bad experience in miui and a terrible one in cm, but I just figured some way to improve, those chinese vrs are a pain, there is no documentation, the solution is to create your own QR Code. It's actualy pretty simple, here is the link https://vr.google.com/cardboard/viewerprofilegenerator/
Send the link through a qr viewer or copy the address into the phone, now your pc and phone are connected, put ur phone in vr and test those configurations. That fixed most problems for me today.
PS: google web ou mention is the qr generator ? It always ask for ppi. There was one qr that I tried one time that bugged my youtube too in VR. Best option isto create your own.
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Very Nice.!!! :fingers-crossed:
nathanchance said:
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Click to expand...
Click to collapse
Thanks for everything Sir.
You really are techno-Jesus, here to teach the ways of kernel perfection. I love your work, dedication, and care for your kernel users. Flash4lyfe.
Yes, please flame me for being a fanboy. You can never show enough appreciation for our beloved xda developers (especially the ones that don't treat users like ****).
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
AndroidGX said:
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
Click to expand...
Click to collapse
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
nathanchance said:
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
Click to expand...
Click to collapse
No worries
Thanks, it works like a charm now (currently trying my kernel on .116), again good job :highfive:
Cheers'
4.4.117 has been merged in.
4.4.118 has been merged in (conflict notes).
4.4.119 and OOS 5.0.4 have been merged in.
4.4.120 has been merged in (conflict notes).
thanks for making this, trying to build lineage and I keep getting the following error:
Code:
drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
Use an out folder.
mkdir out
make O=out mata_defconfig
make O=out -j$(nproc --all)
Click to expand...
Click to collapse
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
aeppacher said:
thanks for making this, trying to build lineage and I keep getting the following error:
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
Click to expand...
Click to collapse
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It booted perfectly, thanks so much! I would use the thanks button but it doesn't seem to be working :/
4.4.121 has been merged in.
I will have a new tree based on the 8.1 sources out tonight.
Sent from my Google Pixel 2 XL using XDA Labs
I have added a new branch for the 8.1 beta source; I will continue to update both 8.0 and 8.1 until 8.1 goes stable.
https://github.com/android-linux-stable/op5/commits/oneplus/QC8998_O_8.1
4.4.122 has been merged in.
4.4.123 has been merged in.
Linux Kernel 4.9 for Moto G5
As you guys already know, our Moto G5 has an ancient linux kernel (3.18.x) which is now EOL (end of life) from support from actual Linux Foundation. It's pretty much stuck there with no probable updates to it (can use the android 3.18 for updates, but I think that's pretty much soon to be deprecated).
I have been working on this kernel since the past one year and finally managed to boot it on our Cedric!
WARNING: THIS KERNEL IS STILL ALPHA AND MOST OF THE BUGS HAVE STILL NOT BEEN FIXED.
I just wanted to share this kernel with the community!
What works:
Boots
Display
Touch
Storage
Charger
Battery Indication
Bugs:
Pretty much every basic thing
RIL (Calls, mobile data, etc.)
Vibrations (Weird and too strong)
Camera
Flashlight
Only Oreo boots so far.
Want to try for yourself?
Click Here to download link LineageOS 15.1 with Linux Kernel 4.9
Huge Thanks to @wiktorek140 for helping me out with bugs and congratulations to him for booting 4.9 on Montana
Leave a thanks if you like my work!
Buy me a Cup of Coffee or Beer here
XDA:DevDB Information
Linux Kernel 4.9, Kernel for the Moto G5
Contributors
m_vaisakh, wiktorek140
Source Code: [url]https://github.com/mvaisakh/msm-4.9[/URL]
Kernel Special Features: Linux Kernel 4.9.x
Version Information
Status: Alpha
Created 2020-03-30
Last Updated 2020-03-30
Reserved
You can find screenshots here:
https://m.imgur.com/a/OWEhM3b
NOTE: The screenshots are from 2 different builds and hence the difference in kernel version.
Cheers!
Update:
I've been working to fix display and audio on for us.
You can check the progress in my kernel repository. I hope to fix it soon!
Nice! Simply nice. This will hopefully get more attention :good:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
m_vaisakh said:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
Click to expand...
Click to collapse
Ig edit the op then :angel:
nift4 said:
Ig edit the op then :angel:
Click to expand...
Click to collapse
Updated OP.
m_vaisakh said:
Updated OP.
Click to expand...
Click to collapse
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
devvikram said:
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
Click to expand...
Click to collapse
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
m_vaisakh said:
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
Click to expand...
Click to collapse
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
devvikram said:
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
Click to expand...
Click to collapse
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
m_vaisakh said:
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
Click to expand...
Click to collapse
thanks alot
I overtook the development and got a few quite nice results. Current bug list:
Boots -
Bt -
Wifi -
Camera -
Vibration -
Gps -
Audio -
Ril - (no call audio)
Fp -
Light Sensors -
Accelerometer -
Proximity -
Gyro -
Mic -
Usb Tethering -
MTP & ADB -
Headphones -
Offline Charging -
Flashlight -
SD Card -
FM Radio -
Issues:
Rebooting to recovery boots to system.
Random reboots.
(that is on Android 10)
my source is at https://github.com/n4experiments/
and thanks to wiktorek140 and his 4.9 montana port because without him I would never be able to get so far
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
Kirisakura-Kernel for the Asus Zenfone 9
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila", while the Zenfone 8 bore the title "Sake".
This year seems to make a change however. The Zenfone 9´s internal codename is "DaVinci".
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
As far as we, @tbalden and me, are aware and as far as we know this project, alongside CleanSlate kernel for the Zenfone 9, marks the first release of a source compiled custom QGKI 2.0 kernel as a standalone flashable zip and project here on XDA.
The introduction of GKI and QCOMs adaptation QGKI means unfortunately that building a monolithic kernel becomes harder and harder. This results in the "kernel" itself no longer just sitting in one partition or the zImage, but it´s spread across different partitions (no longer being monolithic) now. Since there´s no requirment to keep monolithic builds working as in the past, it´s no longer possible to compile the source as is (without applying major rewrites, tricks or hacks) in the monolithic fashion on 5.10 kernels. The same was true for the Pixel 6/Pro.
That means the "kernel" project you´re seeing here needs to be compiled in a build environment to achieve the GKI/QGKI way. Since only Google releases the full build environment alongside the kernel sources itself in a proper fashion with git history, it became very complicated and seemingly impossible to do this on the Zenfone 9 at first glance. A big thanks at this place to Asus. From all the sources of SD8 Gen 1 QGKI devices published, the Asus Source is the most complete. A big thanks to Asus for publishing the sources on time and complete! Also for listening to us if the source is not complete and something is missing.
With excellent teamwork and a lot of hardwork, @tbalden and me managed to compile the Zenfone 9 kernel in QGKI 2.0 fashion after a lot of failed attempts and misery. It´s been a pleasure to work with him over the years here on XDA.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
If that got your curious, I welcome you to continue reading if you´re still interested!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. Starting with 5.4 kernel ( SD 888 ) CFI and SCS were enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
I put the explanations and links in hide tags here.
Spoiler: Documentation Control-Flow-Integrity (CFI) / Shadow Call Stacj (SCS)
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.
Another security feature is Shadow Call Stack (SCS).
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above got you curious, have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Read more about the Release-Model following this link.
This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
Starting with the Initial Message , the following reply and a good summarizing statement.
Quick explanation of QCOM-Upstream. CLO-git is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 8+ Gen1 that´s built into the different SKUs of the Zenfone 9.
The kernel-bases available on QCOMs git, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 13 and intended to be used on the latest Asus Stock-Firmware
- compiled with Clang 16.0.2 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 5.10.181
- upstreamed QCOM base for the Snapdragon SD8+ Gen1 (qcoms internal codename "cape")
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- include important fixes/improvements from kernel/common
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- implement ramoops for easier logs in case of kernel panics
- implement LRNG (see arter kernel OP for more info )
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or Kernel Flasher (free open source solution, get it here)
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
- EAS implementation patched up to latest CAF state
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
- vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.10 default, keep for documentation)
- improve suspend/resume from audio driver (caf-upstream for audio-kernel)
- enable suspend_skip_sync to save power during suspend/resume
- speed up face unlock
- reduce camera launch time
GPU related features:
- GPU driver updated to latest CAF-State
File System related features:
- f2fs improvements
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 9 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.
- add option to force 240hz touch sample rate
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- includes new bbr
- Enable support for TTL spoofing
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
- Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
- enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)
Other features:
- clean up asus drivers and fix a few warnings in kernel log
- enlarge dmesg size to ease debugging
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img, vendor_boot.img, vendor_dlkm.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware via payload extractor)
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 9 receives an OTA update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
Always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip in your favorite kernel app (I personally use Kernel Flasher by @capntrips as it´s free OSS) or TWRP once available.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
AFH is currently down. Please check release posts for attached files.
https://www.androidfilehost.com/?w=files&flid=335947
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87544785
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87641829
1.1.3 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87761015
Android 13
2.0.0
[Kernel][09.12.2022][Android 13] Kirisakura 2.0.0_T for Asus Zenfone 9 aka "DaVinci"
Kirisakura-Kernel for the Asus Zenfone 9 Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago...
forum.xda-developers.com
2.0.6 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87945357
2.0.12 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88194923
2.0.18 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88332217
2.0.19 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88360955
2.0.21 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88384057
2.0.24 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88600875
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Asus for the development device, giving me the opportunity to create this project! This device is absolutely stunning!
@osm0sis for all his work, including the ak3 installer!
@capntrips for his relentless work on several projects, including kernel flasher!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_DaVinci_AI2202/
For necessary changes to other repos, besides the main kernel tree please check tbaldens github, we did the bringup together:
tbalden - Repositories
engineer. Started github with kernel for HTCDoubleshot, migrating version in 2011. kernel follows kernel, patching intuitive new features into CleanSlate line. - tbalden
github.com
F.A.Q:
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img from the matching factory image provided on googles download page.
If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.
Flash those images via fastboot/fastbootd and you will be back on stock kernel.
boot.img, dtbo.img and vendor_boot.img are to be flashed in regular fastboot.
vendor_dlkm.img is to be flashed in fastbootd (you can get to this with "fastboot reboot fastboot" when you´re in regular fastboot)
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
taken from pixel 6 soon to be adjusted
AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
this one too
and this one as well
Woohoo! Rock'n'roll! ^__^
Update to 1.1.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Freak07 said:
Update to 1.1.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Click to expand...
Click to collapse
Hello sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Update to 1.1.1
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2050.2050.29.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.29
- other improvements and tweaks please check github
Download:
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Lossani said:
Hello sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Click to expand...
Click to collapse
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Freak07 said:
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Click to expand...
Click to collapse
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Lossani said:
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Click to expand...
Click to collapse
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts/methods we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can flash any modified vendor_dlkm.
Be aware, disabling the flags triggers an inevitable wipe.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Freak07 said:
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can modify vendor_dlkm.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Click to expand...
Click to collapse
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Lossani said:
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Click to expand...
Click to collapse
check the scripts I just sent you. the vendor_dlkm and vendor_boot from the environment don´t work on the device.
The thing is, asus just uses the kernel environment to precompile zImage,all the modules, dtb and dtbo, then transfer those to their complete build environment and those get includes into the images that end up in the firmware. The zImage they´re using on the device is actually not the one compiled in the build environment, but the GKI kernel uploaded by google. That´s why abi is so important. You´re not supposed to flash the ones produced by the build environment.
Check the scripts how repacking both of those works. If everything is right, that will get you to boot.
the zImage you can get from ASUS_AI2202-32.2030.2030.26-kernel-src/kernel_platform/out/msm-waipio-waipio-gki/dist
Update to 1.1.3
Hey guys and girls,
Here´s the next update. Linux-Stable up to 5.10.149, which also fixed the CVEs discussed here and here.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.34
- merge latest kernel/common
- linux-stable to 5.10.149
- includes a few fixed CVEs
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Update to 2.0.0
Hey guys and girls,
Here´s the next update with source for A13 stable merged. (not much changes, hence the fast release)
Update to A13 stable before flashing this.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 33.0804.2060.65
- merge latest kernel/common
- linux-stable to 5.10.157
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Update to 2.0.6
Hey guys and girls,
Here´s the next update. That´s a bigger one. I´ll explain a few things below in more detail.
The link to the latest firmware can be found following this link.
Monolithic kernel build
Thanks to @arter97 it´s now possible to build the 5.10 qcom kernel now as a monolithic kernel, not needing to build as a GKI style kernel.
To explain it simple: The problem is QCOM/Google are no longer required to test if drivers are loading in the correct order and or test compilation of a monolithic kernel at all.
The gki style kernel has 100s of drivers build as external kernel modules, instead of directly into the zImage.
Having a monolithic build eases development a bit, but won´t directly make an impact to the user.
If you´re interested check my github, it contains the commits. and be sure to drop @arter97 a few thanks somewhere!
Introduction of Lazy RCU
Usually I´m not stating remarks about a change improving battery life notably. But this is one of the few kernel changes that really does make a noticeable difference.
This kernel has the entire(!) RCU subsystem updated to latest linux 6.0 kernel state. This also allowed for Lazy RCU to be merged into the kernel, which should result in power-savings while the device is lightly-loaded or idling (which is basically the case all the time a smartphone isn´t being interacted with (nothing touching the screen and no other workload such as video editing is done).
If you´re interested in details check the slides, which are also linked in the article mentioned/linked above.
A very simplified explanation: RCU functionality can be called 1000s of times a second, batching RCU calls can save power by not calling as often.
Please keep in mind, those are kernel changes and battery life will not be improved magically by huge amounts, but there´s definitely an improvments.
Sony Scheduler Improvements
Import some scheduler changes around Walt from Sony Xperia 1 IV. This improves jitter by a significant amount.
More changes in the changelog below:
Changelog:
- merge latest kernel/common lts branch
- linux-stable to 5.10.160
- merge latest qcom upstream to main branch
- bump clang to latest prebuilt from google 16.0.2
- lazy rcu backported
- scheduler improvements from Sony Xperia 1 IV
- remove wlan rx wakelock as it´s unnecssary
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
luki2411 said:
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
Click to expand...
Click to collapse
hi everybody. this is a very voluminous work, but still, if you decide, I am ready to take an active part in testing.
Hi Freak Will you port this kernel to ROG Phone 6 ?