Kang kernel
By Sjll
Notice: Beware of bricking device!
This a new kernel for stock 10. It's aim to optimize the kernel and provide better user experience.
I had cherry-picked some commits from other SDM845 devices like M i8 and Oneplus 6T. So it's a fusion kernel, though I don't know whether these commits could improve our performance.
I share the source codes, so you could tweak the kernel by yourself. Ok, don't forget to share your work with us.
Download: Github
Note:
1. For XZ2, boot.img already included Magisk.
2 Internal problem is normal, ignore it.
CAF Version: LA.UM.8.3.r1-07600-sdm845.0.
Linux Version:4.9.206-r25-rel
Recommand to use EX kernel Manager
Feature:
1. GPU OC to 835 Mhz.
2. Thanks: Hide unlocked state from @j4nn
3. Qcacld wlan driver.
4. Remove useless drivers.
5. zram to lz4.
6. Increase priority of RT thread.
7. AVB flag removed.
8. WireGuard support.
9. Disabled some logs in kernel.
10. Newer CAF buff and Linux version.
11. Cpufreq and drm drivers optimization.
12. Schedutil optimization.
13. Energy model improved.
14. New I/O governor (Maple & Zen)
15. Blu_schedutil CPU governor( More Powersave ) Need to enable manually
16. IOsched optimization.
17. DTS eagle driver.
18. KLAPSE Color manager. Need EX kernel Manager
19. boeffla_wl_blocker supported.
20. adrenoboost supported, disable it by default.
21. etc..
How to flash:
HTML:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Vbmeta.img see Attach Files
If there is a dtbo.img, then:
HTML:
fastboot flash dtbo dtbo.img
I provide a new thermal configuration, see Attach Files, download it and replacing the same file in vendor/etc. You will get the full performance of SDM845.
Source code: Github
ROM OS Version: 10.0
ROM Kernel: Linux 4.9
Contributors
Sjll
Created 2020-02-26
FIRST! Muahahaha
Thank you like always.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Is it possible to port it on aosp10/los17 with osmosis anykernel?
thanks! can I flash on xz2 compact h8314?
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
It's the stock kernel
Completely incompatible with the SODP project
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
No, this kernel is only for stock, not SODP.
nikkdib said:
thanks! can I flash on xz2 compact h8314?
Click to expand...
Click to collapse
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Faruk.ErdaL said:
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
Click to expand...
Click to collapse
Thanks, if there is any bugs, feedback to me please. I will try to solve it.
Sjll said:
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
Click to expand...
Click to collapse
Yay
Nice, I wanted to look into TWRP at weekend
You could try to set
ro.debuggable=1
ro.adb.secure=0
Or build an -eng TWRP.
Sjll said:
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Click to expand...
Click to collapse
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
nikkdib said:
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
Click to expand...
Click to collapse
Done, try it and feedback, thanks.
Sjll said:
Done, try it and feedback, thanks.
Click to expand...
Click to collapse
i need to patch with magisk manager first if i want root yes?
nikkdib said:
i need to patch with magisk manager first if i want root yes?
Click to expand...
Click to collapse
Yes, you can. It should work fine with Magisk.
Sjll said:
Yes, you can. It should work fine with Magisk.
Click to expand...
Click to collapse
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
nikkdib said:
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
Click to expand...
Click to collapse
Done, try V1.5 please.
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
After first crash files in /sys/fs/pstore giving you the crash reason
MartinX3 said:
After first crash files in /sys/fs/pstore giving you the crash reason
Click to expand...
Click to collapse
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Faruk.ErdaL said:
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Click to expand...
Click to collapse
After crash go into Fastboot mode and flash the working kernel back (with magisk)
Then the device boots and you get the files
Just don't boot one time too much or the pstore will be wiped.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
For XZ2, it already included Magisk. Internal problem is normal, just ignore it. All works fine for me.
Provide your phone type please.
Related
A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30
Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse
Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)
Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I
Thanks, I hope you don't forget dsds variant.
It is a pleasure to have SunKernel in LineageOS.
Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.
Flashing lineage and kernel, looking forward to try it
Thanks for upload
s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install
zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.
L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks
zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse
Introduction
NOTE:
Hello everyone, this is my first kernel for the Moto G4 Plus. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Here are the major features of the kernel (feel free to explore Github)
Update to date with the latest Linux upstream version (3.10.108-EOL)
Westwood as the default congestion algorithm with many more to choose from
Several subsystems converted to use power efficient workqueues
Compiled with Google's arm-eabi 4.9 toolchain
Audio control from flar2
Downloads
Oreo 8.0 : https://sourceforge.net/projects/babyfish-kernel/files/athene/oreo_caf/
Nougat 7.1 : https://sourceforge.net/projects/babyfish-kernel/files/athene/nougat_caf/
Nougat 7.0 Stock :https://sourceforge.net/projects/babyfish-kernel/files/athene/stock_nougat/
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is unified for Moto G4 and the Plus variant so everything should be working fine.
Install the latest adb and fastboot: https://developer.android.com/studio/releases/platform-tools.html#download
Grab the boot image from the download links above
Method 1:
Using adb and fastboot
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Reboot and profit!
Method 2: TWRP
Keep the bootimage on your phone's storage and boot to TWRP.
Install > Select Install Image > Choose the image > Boot partition > Reboot
Changelog
28 November 2017
Oreo-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Nougat-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Stock N:
Code:
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (if you want a specific mention, please let me know)
All of you guys for viewing the thread
Thiago Neves @lcrd512 and Abhijeet Bohra.
Kernel source links.
8.0.0 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/oreo_caf
7.1 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/nougat_caf
7.0 Stock :
If you like my work, buy me an Appy Fizz or whatever you like
https://www.paypal.me/tywinlannister7 :good:
XDA:DevDB Information
Reviver Kernel, Kernel for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: https://github.com/tywinlannister7/android_kernel_motorola_msm8952
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-28
Last Updated 2018-12-10
Screenshots
Some Screenshots
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing. ?
tywinlannister7 said:
Some Screenshots
Click to expand...
Click to collapse
Which ROM is this?
Ayan Uchiha Choudhury said:
Which ROM is this?
Click to expand...
Click to collapse
DU 12 oreo
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Thanks for the new addition in the family.
I hope this will be the favorite member of the family:laugh:
Where is the love for stock user?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
There is a link for stock rom in the op though?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
Stock version won't be released any sooner. I don't have the time for it right now and compilation process of stock kernel is a bit different than CAF kernels. Maybe before the second week of January.
briatide said:
There is a link for stock rom in the op though?
Click to expand...
Click to collapse
Empty as of now
ganeshkmr21 said:
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Click to expand...
Click to collapse
IDK I don't have the time, we already have so many ROMs available. Creating a new ROM will be adding it to the huge list already available, from AOSP to LineageOS to Dirty Unicorns. I would rather work on optimizing what we have. Quality > Quantity.
jyoti.id said:
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing.
Click to expand...
Click to collapse
Yes. 7.1 version for all N custom ROMs and 8.0 for all the O custom ROMs
DU 12 oreo
Blueman1990 said:
DU 12 oreo
Click to expand...
Click to collapse
about DU 12 oreo where can i get it ?
many thanks
i love new system
Does not boot on LOS15. Can anyone else confirm? Cant do logs cause my data port on my phone is broken. It sits on the boot screen like its loading but never fully boots.
Thank you bro!! finally an oreo kernel!
Where I can get DU 12?
Does this have color management?
And which kennel manager should i use with this?
Thanks
harshal2234 said:
Where I can get DU 12?
Click to expand...
Click to collapse
Its not out yet I guess
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Ashishliterally said:
Does this have color management?
And which kennel manager should i use with this?
Thanks
Click to expand...
Click to collapse
Bro its just a 2 page thread. At least read. That question has been answered, in the OP!
Can't I get the unofficial build?
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Same for me. On LOS 14.1, XT1643
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
I don't think so. If magisk is installed/flashed once, then no need of flashing ever again until you freshly install the rom. (AFAIK)
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
Same happened with me I was on Invicta os 8.0
I will be posting my kernel builds here for convenience.
Pre-requisite
Unlocked bootloader with TWRP Recovery installed.
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works
Features
- Stock based kernel with DT2W enabled.
- Forced encryption disabled.
- Passes Safetynet out of the box.
- Fully working camera (Pie kernel-no DRM fix needed for camera).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Flash zip in recovery (don't just extract boot.img as zip has system files to enable DT2W)
Kernel Sources
https://developer.sony.com/develop/open-devices/downloads/open-source-archives
Note. Kernel is compiled as per stock. DT2W is enabled in the DTB, the same parameters as used by the Loire platform.
Downloads
G8141_DT2W-41-kernel.zip
G8142_DT2W-41-kernel.zip
Kernel Requests.
Post the kernel.sin and I will patch it and add it to the OP.
Kernel Requests: View attachment kernel-G8142-205.zip thx !
oneheart said:
Kernel Requests: View attachment 4522264 thx !
Click to expand...
Click to collapse
Added, thanks. Please test and report back (I only own G8141).
shoey63 said:
Added, thanks. Please test and report back (I only own G8141).
Click to expand...
Click to collapse
if i need flash the drmpatch.zip ？
oneheart said:
if i need flash the drmpatch.zip ？
Click to expand...
Click to collapse
Yes, it's required.
it work on G8412 ， thx ！
How can I update to 205 without losing my data?
SilverGamer_YT said:
How can I update to 205 without losing my data?
Click to expand...
Click to collapse
Flash only system.sin - nothing else. Then boot to recovery and flash drmpatch.zip, kernel.zip and then Magisk if you need it.
Reboot and you are done.
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
karrouma said:
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
Click to expand...
Click to collapse
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
shoey63 said:
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
Click to expand...
Click to collapse
Thank you for you work.
One guy tell me to flash CE1 firmware
I will trt
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Castiglionais said:
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Click to expand...
Click to collapse
For tweaking and double tap to wake - Androplus. For the stability of stock - mine.
shoey63 said:
I will be posting my kernel repacks here for convenience.
Pre-requisite
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works.
Features
- Pure stock kernel with only ramdisk changes to enable DRM fix plus solve SafetNet and Magisk issues.
- Passes Safetynet out of the box.
- Fully working camera (No green Pic's).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Downloads
drmpatch.zip
G8141-205
G8142-205dual
Click to expand...
Click to collapse
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
YasuHamed said:
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
Click to expand...
Click to collapse
Not quite OK. You also need to patch init.environ.rc as per this post https://forum.xda-developers.com/showpost.php?p=74310718&postcount=43
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You could try this one. It is from M-ROM v1.5, a Chinese rom.
I would flash the kernel.zip again, then the SuperSU.zip then the drmpatch.zip and wipe cache and dalvik and see how you go.
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You must try this version this is created for xperia phones:https://forum.xda-developers.com/attachment.php?attachmentid=4164510&d=1496008012
help
I can not understand the order in which I have to do things
Should I unlock the bootloader and then?
I must install the recovery by adb or first the kernel
I come from samsung and the difficulty here is greater and there is much less information, if someone could help me I would appreciate it. I have the latest version of oreo the .205
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest [clean] ROM for our device, benchmarks coming soon .
Click to expand...
Click to collapse
Features
Google's exclusive features for Pixel devices (except Music Ticker and Call Screening)
Lawnchair launcher
Spoofed stock device to pass SN
Widevine L3
Faster encryption device-wide
Daydream VR
Fast, optimised Zest Kernel
EAS
Markup screenshot editing
Google Sound Picker
Google Wallpapers
Digital Wellbeing
Optimised GPU rendering for Pie
Custom Clang and GCC toolchains for building - optimised LLVM with PGO, and GCC 9.1
OpenGApps pico included
GCam HDR+ support
Click to expand...
Click to collapse
Installation instructions
* Go download https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-yoshino.
* Unzip the download to get an .img file.
* Install fastboot (drivers for this can be gotten from Google directly), drivers for flashmode for Windows can be gotten from newflasher.
* Enter your command prompt or terminal whatever and fastboot flash oem THEFILEYOUEXTRACTED.img.
* Find a decent TWRP and flash it.
* Download the ROM for your device. They are all in this folder https://jenkins.cosmic-os.org/job/zfsodp-core/ws/lastbuild so click the one for your codename (eg. G8141 is single sim maple and G8142 is dual sim maple).
* Flash it in TWRP and wipe internal storage and format data (the option that has red text and makes you type yes).
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my Jenkins job.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Sony group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @kholk for his kernel advise
* @Sultanxda for his kernel advise
* @deletescape for Lawnchair
XDA:DevDB Information
Zest-flavoured SODP, ROM for the Sony Xperia XZ Premium
Contributors
LazerL0rd, The entire SODP team
Source Code: https://github.com/ZfSODP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Sony OSS OEM binaries
Based On: SODP
Version Information
Status: Beta
Beta Release Date: 2019-07-06
Created 2019-07-06
Last Updated 2019-08-10
Reserved
Reserved
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
del
Can I flash the kernel through twrp, then flash the zip?
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Give it a week or so mate, lazerl0rd is studying/having exams for a while.
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Any screenshot of the performance?
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
still on logo android !/
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Moarten said:
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too.
Laplacetor said:
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
Click to expand...
Click to collapse
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too. ROM isn't on my website and never was .
wolfmanstr said:
Can I flash the kernel through twrp, then flash the zip?
Click to expand...
Click to collapse
Don't use my stock kernel with this.
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
It performs better, battery is decent now (after a load of changes). We now (as of today) have a Power HAL (libperfmgr) which supports DT2W on supported devices too. I may or may not update it to version 1.3.
SilverGamer_YT said:
Any screenshot of the performance?
Click to expand...
Click to collapse
No, it's EAS and you could test it out.
tronganhha29 said:
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
CRNO said:
still on logo android !/
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now.
Sjll said:
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now. EAS seems stable, here. The bugs we have aren't really EAS related.
undefine said:
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least. I changed up the thermal driver so it should be good now. Btw those thermal modules in Magisk won't change a thing as I use sultan's thermal framework now - not RQBalance stuff. DPI has an option on setup under "vision", choose what you like. I added GCam instead, it's gonna be better quality than Sony's crappy cam app. Ancient app logos aren't gonna be updated, these are ASOP packages - instead I'm replacing them with Google packages. Also I made everything Squircle shaped too. Device-wide dark mode will be coming soon, needs some kanging [with original authorship] from Q. Phone application should be de-google-ified -> you can turn off the spam filter and install any Dialer you want. I'm not dealing with darkening AOSP's package so that's why I'm using Googles. Google can get your data if Play Services is installed anyways. Option to switch resolution and frame rate on the go -> idk why SODP removed that.
Astoras said:
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
Click to expand...
Click to collapse
For Android kernels, you can't just chuck a module in. But I'll add it to the kernel config for ya.
CRNO said:
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Click to expand...
Click to collapse
Already done. And - "I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least."
Project treble for Xperia X Performance
Based on Sony Open Devices
If you end up with a HARD BRICK. Nobody can help you.
Features:
1. Gcam Support
2. Higher performance than SODP default.
Stable Version:
V4.2
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
Required files:
V1.0~V5.1: Link With:SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_tone.img
TWRP: Link
OEM: Link
Sony offcial link
How to flash:
Read README.txt in the zip file please.
GSI:
I tested Descendant.
Different GSI have different compatibility with our treble blob, try more GSI, you will solve all the issues you met.
Gcam:
Gcam must work with Google play services.
I prefer releases from ARNOVA8G2,(Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk)
Download: Link
Enable this settings under fix
•Raw Format to Raw10
•Viewfinder Format to YUV_420_888
If you want to set Raw Format to Raw Sensor
Please enable: Buffer Fix to Fix viewfinder lags.
Update and known BUG:
V5.1:
1. Optimize EAS, more stable.
2. Support dual sim cards.
V5.0:
1. Stable EAS support.
2. I/O speed up.
V4.2:
I forget what's the updates.
V4.1:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back.
3. F2FS support for cache(Qnovo) and userdata partitions.
V4.0:
1. Performance and stability improve.
2. A lot of Fixes of SODP.
V3.1:
1.Update: Performance improve.
V3.0:
1.Update: EAS supported.
TWRP V2.0:
1.Update: Fix userdata can't be read.
V2.0:
1.Update: Performance improve.
V1.0:
1.BUG: Not found.
Source
Sources Code
XDA:DevDB Information
Treble, ROM for the Sony Xperia X Performance
Contributors
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2019-07-11
Last Updated 2019-08-23
Hello,
thank you for your hard work.
Do I understand correctly that you've user 9.0.0_r10 branch of local_manifests when you built it?
Or did you actually checked out the latest one (i.e., 9.0.0_r44)?
hn40cn said:
Hello,
thank you for your hard work.
Do I understand correctly that you've user 9.0.0_r10 branch of local_manifests when you built it?
Or did you actually checked out the latest one (i.e., 9.0.0_r44)?
Click to expand...
Click to collapse
Based on lastest 9.0.0_r44.
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Sjll Back at treble in Xperia x again!
Performance edition this time
thaneekl said:
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Click to expand...
Click to collapse
You need to try different GSI, some GSI don't suit for our treble build.
I tested Pixel Experience.
I will try sim card. I noticed there is IMEI in about phone, so I think sim card should works fine.
thaneekl said:
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Click to expand...
Click to collapse
After I tested, on some GSI sim works, it's not related with our treble build. Please try this GSI.
https://github.com/Descendant/InOps...tZero/Descendant_ThreeDotZero_arm64_aonly.zip
Homepage:
https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
2.0 stable
Havoc-OS 2019-07-12
So far so good. stable so far. But overheat is no joke.
edit:20/7/2019 Heat issued solved. I use this to tame down Snapdragon820. That's just cpu profile so it's will work on any device anyway.
Download the APK, install and grant root permission. No need to flash the zip file. I select Balanced >> Ghostpepper profile.
Omnirom Unofficial 15-07-2019
Best of the best. Not even had heat issues. Is that black magic?
3.1
Now It's work perfectly on my F8132. Thanks a lot.
edit: Yeah It's works. But have issues about random reboot while launching random app or perform random action. Might be rom or overheat isssue. Descendant 3.1.1
edit2: on 3.1
Sjll said:
You need to try different GSI, some GSI don't suit for our treble build.
I tested Pixel Experience.
I will try sim card. I noticed there is IMEI in about phone, so I think sim card should works fine.
Click to expand...
Click to collapse
Any bug on pixel experience gsi? Sorry for my bad english. And thanks for your hard work
Ralvindo said:
Any bug on pixel experience gsi? Sorry for my bad english. And thanks for your hard work
Click to expand...
Click to collapse
So....i dont own an xperia x performance BUT a normal xperia x
And on there the only Problem is that there is an annoying message at Boot
But except that everything is fine
Some random said:
So....i dont own an xperia x performance BUT a normal xperia x
And on there the only Problem is that there is an annoying message at Boot
But except that everything is fine
Click to expand...
Click to collapse
Ok i'll try and give a review here ?
Ralvindo said:
Ok i'll try and give a review here ?
Click to expand...
Click to collapse
:good:
I've got bootloop on latest version.
thaneekl said:
I've got bootloop on latest version.
Click to expand...
Click to collapse
Could you please test the new boot.img with old vendor.img and new vendor.img with old boot.img ?
I need to find the reason.
Sjll said:
Could you please test the new boot.img with old vendor.img and new vendor.img with old boot.img ?
I need to find the reason.
Click to expand...
Click to collapse
It's boot now. Maybe the issues is on my side since my device refuse to boot on any kernel even patched stock kernel at the time
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
thaneekl said:
It's boot now. Maybe the issues is on my side since my device refuse to boot on any kernel even patched stock kernel at the time
Click to expand...
Click to collapse
OK.
plombir0032 said:
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
Click to expand...
Click to collapse
I written "need test". It works on XZP.
plombir0032 said:
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
Click to expand...
Click to collapse
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
Why i can't change the minimum frequency in kernel aduitor? Cores always at high frequency, minimum not applied.
SO-04H
hi
is this work on so-04h docomo ?