[Kernel] [OC] [QUICKCHARGING] [AOSP PIE] [4.9.221] - SimpleKernel SuZu - Sony Xperia X ROMs, Kernels, Recoveries, & Other D

I'm not responsible for any damage to your device. So be advised.
Kernel Features:
-CPU Overclocked (BIG cores to 2.01GHz (experimental, i should reduce and / or disable it if too many users notify instability in F5122 (that is my personal device));
-AdrenoBoost;
-Slimbus (Audio bridge) Overclocking;
-WCD9335 HiFi selector and tunnings louder audio at kernel side;
-WSA8810 tunnings for better and louder audio in speaker;
-CRC disabled;
-DTS Eagle sound integration;
-300 Hz instead 1 kHz for kernel timer (saves power);
-Boeffla Wakelock blocker;
-Quick charge tweaks (2100mA constant charging for QC 2.0 / 3.0 enabled chargers, drawing about 1,6 Amps from wall PSU);
-Tunned voltage regulators for CPU and GPU enabling High Power Mode;
-Kernel general optimizations;
-WIP: add klapse and kcal;
-Enable 160 MHz clock in crypto engine for faster crypto operations.
Special thanks to:
@stefanhh0 github user (idk what is the nick here, please, pm me and i add it if you want) for keeping a source with newer mainline (i guess) patches;
@franciscofranco for many commits that help us improving performance and saving power;
Sony AOSP team;
And others that maybe i forgot to tag here but all them are in the github code below:
https://github.com/LuizPauloDamaceno/kernel
Inside the zip that you can download below, you will find the initial release. You should flash it by fastboot and them reinstall magisk if you have it. Also, have two xml files that is a complementing of the audio tweaks in android side, enabling CLSH_LOHIFI mode in the audio processor and tunning volumes. From mic to headphones and speakers. The thermanager is the one that you should install it for improved thermal handle with this kernel. Dont worry, things shouldn't fry, but is not my fault if them fry. As another complemention, i've done a "userdata" partition for users who have 64 GB variants, like me. The AOSP is compilled for 32 GB i guess and we have only half of our full capacity. Flashing userdata (obviously, will erase your data partition and you will loose everything like is done in the first AOSP flashes if you dont do a back-up...) you will also have more free space
Kernel: fastboot flash boot boot.img
Userdata: fastboot flash userdata userdata.img
To copy the below files i like to use root explorer app, you can also do by adb. I'm open for suggestion of better apps too
mixer_paths.xml: copy it to /system/vendor/etc/mixer_paths.xml and change permissions to 0644 octal or rw-r-r.
thermanager.xml: copy it to /system/vendor/etc/thermanager.xml and change permissions to 0644 octal or rw-r-r.
The first versions i will not do the automated flashing because are the initial and testing releases, but if my plans goes ok for the next 15 days or in the worst case next month, i can do a twrp flasheable style to make our lives easier. For me, no random reboots, no overheating for normal use and battery stills ok. Report it your experience, i will appreciate to know! =D
https://androidfilehost.com/?fid=4349826312261806431
Hope you all enjoy this, guys!
Luiz

Download link edited.

LuizPauloDamaceno said:
Download link edited.
Click to expand...
Click to collapse
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!

Could this one be used with LineageOS 16 Custom Rom by chippa?

LOLisLIFE said:
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!
Click to expand...
Click to collapse
I've stopped oreo because I didn't see any advantages to me to keep it updating, i do this for fun and based in my use. Now i'm using pie, so, i think is fare to start a Pie project...

justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
I dont know, i dont have sure if could be used because maybe the drivers are different. If the LiOs uses 3.10 kernel then dont, you cant, because the drivers of 4.9 kernel is quite different.

justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.

ParanoidNemo said:
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.
Click to expand...
Click to collapse
Thank you for the test! I will stay in AOSP Pie for a while since i've built mine one following the sony's tutorial for now. Wainting for the results

So, who tested it the first release? Any observations? soon i will post the second release with some improvements.

I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort

Lihxor said:
I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort
Click to expand...
Click to collapse
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...

LuizPauloDamaceno said:
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...
Click to expand...
Click to collapse
Thanks for the answer. Btw, i meant that voice notes are quiet, so their volume is too low to be heard

Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.

LuizPauloDamaceno said:
Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.
Click to expand...
Click to collapse
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?

iH8Ecchi said:
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Been stuck with a lot of work and not tried yet. Will report as soon as I've time to try it.

iH8Ecchi said:
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.

LuizPauloDamaceno said:
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.
Click to expand...
Click to collapse
I did this run a year ago, haven't tested that yet. I've since switched to Lineage GSI (with Sjll's modified 4.9 kernel), and tethering/hotspot works fine.

Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.

adi_adi said:
Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.
Click to expand...
Click to collapse
Have you some random reboot or not with the aosp9 by vknecht?

ParanoidNemo said:
Have you some random reboot or not with the aosp9 by vknecht?
Click to expand...
Click to collapse
Well, random reebots still occur unfortunately, but most on demanding tasks. I'm not an expert, but I don't think this is a kernel issue.

Related

[KERNEL][v500][4.4.2] AIC Kernel [MAY-4-2014]

AIC Kernel​for LG G Pad 8.3 V500​
Compatible with v500 STOCK BASED LG 4.4.2 roms ONLY! The "gamma improvement only" is available for other ROM's in the installer
This was just a private build that seems to have gained some demand to help with the v500 gamma issue. I have been running it the past week and it seems stable enough to share to other v500 users. I'm not a developer, I build and update TWRP for the Nabi tablets, have shared a few windows bat files, have a VB.net app to automate various mods to the Nabi's, and a lot of research of nvflash/APX nand formatting for the Nabi's. My only previous kernel builds were for the HP Touchpad for private use, and my Ubuntu computer. Basically taking what real developers have done and trying to make it work for my own use.
EDIT 5/11/14: I put the gamma improvement fix in just a stock kernel with no other changes, and the changes to CM11 kernel. There are 2 CM kernel version depending on which LG ROM you installed CM over to deal with the dimming issue at boot. Those are available in the new all in one installer.
Disclaimer:
Experimental. Use this at your own risk.
Please Please Please make a full backup of your tablet.
Base:
The starting source is V50020B from LG
Compiled with arm-eabi-4.7
Added features:
Initial
Improved gamma. Using default linear LUT (from 1.8-2.0 to 2.2-2.3 on my screen)
Default overclock from 1.72 to 1.78Ghz (no voltage increase)
Default underclock to 162 Mhz
Sysfs Voltage Table added for undervolting
Allow GPU to manually increase freq from 400Mhz to 487Mhz
Add GPU boost to GPU on demand governor
Add Faux Display interface (gamma control seems broken)
Add NTFS support(untested)
Add SIO Scheduler
Add FIOPS Scheduler
Optimize memcopy, string and square root functions
Add Intelliactive Governor
Download:
BETA: http://nabtabhacks.com/downloads/AICbeta2.zip Very stable but haven't got enough feedback to make it official. See changes here http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Installer for all gamma improvement kernels, tested by numerous members(AIC, stock, and CM) http://nabtabhacks.com/downloads.htm
Installer AIC Kernel: http://nabtabhacks.com/downloads.htm
Uninstaller, returns to stock 20B: http://nabtabhacks.com/downloads.htm
Install:
Reboot to recovery(TWRP)
Make a backup, just do it
Install AIC_kernel_flashable.zip
Wipe caches/dalvik if you see fit
Reboot
Source:
AIC: https://github.com/aicjofs/android_kernel_lge_v500
Stock with gamma only: https://github.com/aicjofs/android_kernel_lge_v500_stock
CM: https://github.com/aicjofs/android_kernel_lge_v500_cm
Credits
I need to give some specific acknowledgement to "oubeichen" for sharing his kernel tree, and sharing of information. Also to id10terror's install script was the easiest to use as a template.
Woohoooo, Finally some gamma correction love. Flashing now
ROM: LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted
Working much smoother with your kernel, thank you for sharing!
Tested it yesterday and it made a subtle but noticeable difference to whiteness and brightness. Thanks again
Sent from my LG-V500 using XDA Free mobile app
Am really eager to try! Thx a million times @op!
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct
Sent from my LG-V500 using XDA Free mobile app
tested with LRS ROM (stock based ) , working perfectly!
many thanks!
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
bloommax said:
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
I have been using the kernel all day and it's working great! Thanks!
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
sleekmason said:
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
Click to expand...
Click to collapse
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
vimesUK said:
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
Click to expand...
Click to collapse
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
Have you looked at the install script I use for the 510? You have the ability to change ramdisk files on the fly using sed (easiest language I could find), by opening the device ramdisk, insert one liner, close ramdisk, combine into boot.IMG.
I have a couple of simple changes for allowing tethering, and values that I couldn't make without it! This part of it may work for you!
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
I kept auto brightness disabled. It does not work well for 4.4.2. You may replicate the brightness issue with the following procedure: 1) reboot the tablet; 2) when adjusting the brightness slider, you will find 0% is very (too) bright, and the entire range is high; 3) after sleeping and waking, the brightness is much dimmer, and the entire range from 0% to 100% is lower in brightness. It seems a procedure during wake modified the range of brightness settings.
Sent from my LG-V500 using Tapatalk
Run with stock kernel 20B. I will test urs by now
Well after having to do a complete reinstall due to another issue, I tried this kernel. Man I've only used it for a few hours but color me highly impressed :good: My gamma is almost perfect and it seems noticeably faster and smoother.
Really great job and thanks.
How is the battery life?
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
In my ignorance I was not aware of what could implicate the brightness values and range on this tablet. Having only just bought it, and upgraded to KK right away, I was not aware of how JB performed, in that respect. Prior to your kernel I was using the Screen Adjuster app as a sort of fix to compensate for the comparative (to my other tablets and phones) lackluster screen performance of the tablet. With the SlimKat ROM I was experiencing, but might have overcome them, some dimming issues which I did not understand.
Since restoring the stock KK backup and using your modified kernel I no longer need the screen adjuster app and things do seem to have improved.

[KERNEL][v500]CM12.1] mani.Kernel v28 (17.08.15)

thanks to
@sleekmason for his tutorial
@franciscofranco for his sources and hotplug algorithm
@oubeichen for msm_kcal_ctrl port
Features:
-franco hotplug algorithm
-custom thermal throtteling
-cpu: interactive
-uv: table exposed
-faux123 gamma control
-various fixes and optimizations
changelog:
v28: 17.08.2015
-updated to newest changes
-removed synapse (flash it yourself)
-governor is conservative now
-reverted some changes to hotplug
-scheduler: noop
-updated toolchain
-livebump instead of loki
-official CM only
how to change hotplug values
the values are located in
Code:
/sys/class/misc/mako_hotplug_control/
there you have
cpufreq_unplug_limit
Code:
if frequency is higher than this cores wont be offlined for a period
max_load_counter
Code:
maximal samples counted to offline cores (higher values = longer time to offline core)
high_load_counter
Code:
- info missing yet -
load_threshold
Code:
threshold to online a core
min_time_cpu_online
Code:
minimum time a core stays online
timer
Code:
samples per second (1 = 10 samples; higher values = less samples)
brightness
If you experience brightness issues it is because you are using base 4.2.2
to avoid issues flash 4.4.2 base
you can find a flashable zip here:
http://forum.xda-developers.com/showthread.php?t=2762526
reboot or crash?
send me last_kmsg
BACKUP BOOT AND SYSTEM FIRST!
Download !!!OFFICIAL CM ONLY!!!: https://www.androidfilehost.com/?fid=24052804347795577
XDA:DevDB Information
mani.Kernel, Kernel for the LG G Pad 8.3
Contributors
ckret
Source Code: https://github.com/drbeat/kernel_lge_v500
Kernel Special Features: franco hotplug, UV table, gamma adjustment, custom thermal throtteling
Version Information
Status: Stable
Created 2015-01-23
Last Updated 2015-08-17
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Rapepini said:
Is this for AOSP?
Inviato dal mio LG-V500 utilizzando Tapatalk
Click to expand...
Click to collapse
yes its for aosp
Cool, a new kernel ! Small question before I make the jump : what do you mean, generic touchboost not working ? Is this an issue for everyday use ?
Generic touchboost is a generic driver for boosting up the CPU in touch
Franco has this in his kernels but i couldnt make it work
So i implementend the touchboost in the existing lge touch driver
Shouldnt be an issue for usage since i am using this kernel myself as daily driver
Working great so far. Using on vanir ROM. Thanks!
How far have u overclocked it. And how does it perform
zombieryder said:
How far have u overclocked it. And how does it perform
Click to expand...
Click to collapse
Didnt overclock it
Never said i did
They pad has a quadcore with 4x1.7 GHz
No need for oc
I tried running this on the following ROM:
[ROM][v500][KK][4.4.4][LINARO/SABERMOD] AOKP [WEEKLY BUILDS][20140705]
The first issue I ran into was that the screen brightness was locked at the highest level. I have read that you need to have the 4.4.2 base when running these 4.4.4 ROMs in order for screen brightness to work. It looked to me like installing this kernel upgraded to the 4.4.4 base, which would explain why that became broken.
Is it therefore safe to assume that this kernel is only for ROMs running the 4.4.4 base and not the 4.4.2 base?
Thanks
Well, no problem with autobrightness for me, and I have switched to 4.2.2 base to avoid the dim screen at startup. Been running it for the biggest part of the day, and found no real issue for now. Good work.
As for what doesn't seem to work, I was thrilled to see the gamma option in trickster mod, and thought I would be able to calibrate my screen correcly for the first time. Sadly, it seems the changes are registered (Trickster mod says they are saved allright), but there is no evolution whatsoever : the screen stays the same (and believe me, I have tried the most extreme settings to be sure I would notice the subtlest of changes).
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
ckret said:
i dont know about the bases
i think i have the 4.2.2 base but i am not sure
and currently gamma is not working. i am looking into that, but it seems quite hard
Click to expand...
Click to collapse
Well at least, the option shows up in trickster mod, so I guess you're not so far from it. Anyway, your kernel seems to run very well. Thanks!
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Cal-123 said:
For sure opened the brightness...in fact ALL the way & no way to lower more.
Also, I lost sound.(Not for sure now about that one) All else fine, but NO gama control, and no 'on demand' - only 'interactive & 2 others'...
So giving it up for now, but thank you for the compiling & I'm sure you'll get it right next time!
Click to expand...
Click to collapse
i am aware of the brightness problem
gamma control not yet given, since i cant find the gamma address
interactive is optimized so its selected as default in this kernel
v3 feels alot smoother
dont know if there are any issues with cabc enabled
you gotta try out and report me
Running v3 on Mahdi. Smooth so far. Will report back in a few days.
Sent from my LG-V500 using Tapatalk
I was testing v3 and brightness value is fixed and wont change for me. I'm using CM11 M8.
wind0zer said:
I was testing v3 and brightness is fixed and wont change for me. I'm using CM11 M8.
Click to expand...
Click to collapse
The brightness seems to be *the* big issue with all the kernel builds. But when mentioned to other kernel builders or porters, they don't understand the 'why' of the need for more brightness. I feel the same way...I would like to be running at 40% brightness and see everything OK, but just so I could possibly save some battery 'time'. But frankly I really don't know why - 5 or more hours is long enough in one day on a tablet for me. Seems to be enough for Oubeichen, who I think is a fine kernel analyzer or porter.
What I would like to see is what Oubeichen put into this kernel found here and which I'm running but is v3.4.xxx (can't remember! and am on a computer now):
http://forum.xda-developers.com/showpost.php?p=54153699&postcount=196
Even though this is early version kernel, I'm running it with no problems - it has about 7 or 8 Processor settings such as Progressive, Conservative...etc. and several I/O's such as Noop and all the others that are not shown on the later 3.4.0 kernels. Nice settings to have to play around with IMO.
As aicjofs said brightness is a BASE issue
If you run the kernel on the 4.4.2 base you will have no Problem
I can compile it for your 4.2.2 base but i dont just geht why you dont upgrade
Having 1000000 options isnt as good as having optimized options
If you want to know what the issue is you have to look jnto the AIC thread. He stated the difference for autobrightness on the bases
i have added a sys interface so ppl with 4.2.2 base can also use this kernel
just read first post

Share Yor ROM+Kernels setup here

Hi there, this is the thread to share your rom and kernels setup and if also some mod that you use in your rome such as audio mod. Might be helpful for and the other users to try. Maybe some of you using MiUI Rom either chinese or global or xiaomi.eu or other MiUI based rom and maybe some of you using CM13 and aosp based rom.
Here is also some link for the kernels:
---------------------------------------------
Guyver Kernel
http://forum.xda-developers.com/redmi-note-3/how-to/kernel-test-guyver-kernel-t3494521
Radon Kernel
http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884
Agni Kernel
http://forum.xda-developers.com/red...nel-24-09-2016-agni-puremiui-mm-v1-4-t3468042
http://forum.xda-developers.com/red...ernel-25-09-2016-agni-purecm-mm-v1-6-t3469874
http://forum.xda-developers.com/red...kernel-02-10-2016-agni-purecm-n-v1-7-t3472640
ElementalX
http://forum.xda-developers.com/red...nel-elementalx-rn3-0-01-miui-android-t3455859
Neon Kernel
http://forum.xda-developers.com/redmi-note-3/development/kernel-neon-kernel-t3439667
Blaze Kernel
http://forum.xda-developers.com/redmi-note-3/development/kernel-blaze-kernel-1-t3424981/page152
------------------------------------------------------------------------------------------------------------------------
Some users like more battery backup on their device, some users like more performance on their device. So, which one is yours?
Share.... :highfive: Also it might be helpful if you share your kernel settings. Screenshot would be great :highfive:
My ultimate Kenzo-combo is:
1. Unofficial CM13 by Umang and DiamondBond. Why this over official CM13? Because I don't have to mess with all the camera fixes, everything is included by default. Plus as a bonus I get lightning-fast boot times and slightly quicker apps installation;
2. Radon V3.0.1 aka the most versatile, feature-rich and stable kernel for this device;
3. GovTuner 3.6 with the Balanced profile. The phone runs super-smooth while giving me solid 7-8 hours of actual use. Sure, I could go with more conservative settings and easily get 10-12 hours of SoT, but watching the phone stutter and lag is not for me.
4. Various little mods and adjustments, like the Goodix patch, build.prop tweaks ( disabling Camera2 API and bringing the LCD density down to 420 ), removing SoundFX libraries, heavily debloating the ROM and cleaning up some more system stuff like libraries and ringtones.
Overall this combo gives me the perfect day-to-day usage with no bullstuff, no crashes, no weird glitches and bugs. Everything is consistent, clean, smooth and stable.
CM14.1 can't come soon enough.
01_april said:
3. GovTuner 3.6 with the Balanced profile. The phone runs super-smooth while giving me solid 7-8 hours of actual use. Sure, I could go with more conservative settings and easily get 10-12 hours of SoT, but watching the phone stutter and lag is not for me.
4. Various little mods and adjustments, like the Goodix patch, build.prop tweaks ( disabling Camera2 API and bringing the LCD density down to 420 ), removing SoundFX libraries, heavily debloating the ROM and cleaning up some more system stuff like libraries and ringtones.
Overall this combo gives me the perfect day-to-day usage with no bullstuff, no crashes, no weird glitches and bugs. Everything is consistent, clean, smooth and stable.
CM14.1 can't come soon enough.
Click to expand...
Click to collapse
Wow, that is a lot work to do. Does the Gov Tuner same like L Speed And HEBF mod?
khairul H said:
Wow, that is a lot work to do. Does the Gov Tuner same like L Speed And HEBF mod?
Click to expand...
Click to collapse
Unfortunately, I haven't used either of those mods, so I can't compare.
But after installing GovTuner I noticed a signifcant increase in smoothness and fluidity with no real decrease in battery life / SoT.
01_april said:
4. Various little mods and adjustments, like the Goodix patch, build.prop tweaks ( disabling Camera2 API and bringing the LCD density down to 420 ), removing SoundFX libraries, heavily debloating the ROM and cleaning up some more system stuff like libraries and ringtones.
Click to expand...
Click to collapse
Can you explain how it improves? for example disabling Camera2 API? I use Denoisecamera (from this forum) but some options FC.. but the pictures are actually nice in my opinion... Would like to have a full working camera with at least a close enough quality to this app
Barnir said:
Can you explain how it improves? for example disabling Camera2 API? I use Denoisecamera (from this forum) but some options FC.. but the pictures are actually nice in my opinion... Would like to have a full working camera with at least a close enough quality to this app
Click to expand...
Click to collapse
It doesn't improve picture quailty, it improves the speed and responsiveness of the camera app. I don't care about picture quailty at all because I'm a student, so 99% of the pictures I take are textbooks, whiteboards and so on. I don't need any manual controls and denoise features for that. So, it improves the experience for me personally by making taking pictures faster and simpler.
01_april said:
It doesn't improve picture quailty, it improves the speed and responsiveness of the camera app. I don't care about picture quailty at all because I'm a student, so 99% of the pictures I take are textbooks, whiteboards and so on. I don't need any manual controls and denoise features for that. So, it improves the experience for me personally by making taking pictures faster and simpler.
Click to expand...
Click to collapse
I see, but would you use any other app for the purposes i said? i dont even know now how to unnistall that Camera because it is a flashable zip
I'm using AOSCP 7.1 and Agni Kernel 3.2 and i really like this combo
Another great combo is TeslaN 7.0 and Agni kernel
01_april said:
Unfortunately, I haven't used either of those mods, so I can't compare.
But after installing GovTuner I noticed a signifcant increase in smoothness and fluidity with no real decrease in battery life / SoT.
Click to expand...
Click to collapse
What about your Kernel settings? Governor? I/O scheduler, etc?
MurdererFight said:
I'm using AOSCP 7.1 and Agni Kernel 3.2 and i really like this combo
Another great combo is TeslaN 7.0 and Agni kernel
Click to expand...
Click to collapse
What about your Kernel settings? Governor? I/O scheduler, etc?
AICP + Agni with ondemand and noop + xposed with greenify Amplify and power nap 11-12 hour of screen
I use official CM13 + Guyver Kernel.
I prefer to have a better battery backup (2days) but not in lieu of a great decrease in performance. The phone doesn't shutter or lag, smooth and I get about 10h SOT
mehrshad.shafaghi said:
I use official CM13 + Guyver Kernel.
I prefer to have a better battery backup (2days) but not in lieu of a great decrease in performance. The phone doesn't shutter or lag, smooth and I get about 10h SOT
Click to expand...
Click to collapse
What about your kernel settings? do you keep it default or you tune a little bit? 10h seems interesting.
Barnir said:
I see, but would you use any other app for the purposes i said? i dont even know now how to unnistall that Camera because it is a flashable zip
Click to expand...
Click to collapse
Snapdragon Camera and Manual Camera come to mind, you can easily Google both of those.
khairul H said:
What about your Kernel settings? Governor? I/O scheduler, etc?
Click to expand...
Click to collapse
CPU governor - Interactive, GPU governor - Simple Ondemand with Adreno Idler turned off, I/O scheduler - Zen, forced FastCharge, speaker boost of +18, vibration level of 67%, disabled Fsync, TCP agorithm set to Cubic, Low Memory Killer set to Very Light, plus some color-calibration ( personal preference ).
######MINE KENZO CONFIGURATION###### ROM: - GLOBE MIUI dev 6.11.3- smiui.net
KERNEL -STOCK SMIUI
XPOSED
VIPER4ANDROID FX
HEBF TWEAKS
MIX THEME
MIUI TWEAKS BY SOLARWAREZ (THANKS FOR HIS AWESOME XMIUI APP
SOTS: -10H
OTHER ONES
1.RR 5.7.4
RADON
XPOSED
VIPER
Camlin3 said:
######MINE KENZO CONFIGURATION###### ROM: - GLOBE MIUI dev 6.11.3- smiui.net
KERNEL -STOCK SMIUI
XPOSED
VIPER4ANDROID FX
HEBF TWEAKS
MIX THEME
MIUI TWEAKS BY SOLARWAREZ (THANKS FOR HIS AWESOME XMIUI APP
SOTS: -10H
OTHER ONES
1.RR 5.7.4
RADON
XPOSED
VIPER
Click to expand...
Click to collapse
I am using Official TWRP 3.0.2-2 and I have officially unlocked my device, can I flash smiui rom with my recovery or should I have to install some other recovery? and I want to keep my recovery so I should check don't overwrite recovery while building my smiui rom?
Thank you,
Rescuremix 5.7.3 (MM) + radon kenzo 2.9.5 is great battery life+Better camera,,,
No bugs!!
Sorry my bad english
NX 10.4 + Radon 3.0.1 + amplify,greenify,powernap
Get around 11h SOT , 85k antutu 2GB model
And totally customisable with kernel adiutor
redminote3 said:
NX 10.4 + Radon 3.0.1 + amplify,greenify,powernap
Get around 11h SOT , 85k antutu 2GB model
And totally customisable with kernel adiutor
Click to expand...
Click to collapse
Stats dont work on m stable stock with onl greentif & gotuner. How to get stats in powernap?
Use BetterBatteryStats

[Recommendations] Stable daily driver ROM for Mi 5

Hey guys, recently my father got tired of ****ty MIUI and wanted something better for his Mi 5. Since it's not my phone, I cannot test various ROMs and kernels by clean flashing them.
I just need one ROM that I can switch to on his phone from MIUI.
It needs to be 100% stable (he is sick of bugs), needs to have great calling and bluetooth connection, and great battery life.
Please let me know if such ROM exists for Mi 5, and which one is it
(Do you guys face any issues with bluetooth speakers or taking calls via bluetooth in car?)
You can start with jdcteam's aosp. Has been really solid for me.
arnavbatra said:
Hey guys, recently my father got tired of ****ty MIUI and wanted something better for his Mi 5. Since it's not my phone, I cannot test various ROMs and kernels by clean flashing them.
I just need one ROM that I can switch to on his phone from MIUI.
It needs to be 100% stable (he is sick of bugs), needs to have great calling and bluetooth connection, and great battery life.
Please let me know if such ROM exists for Mi 5, and which one is it
(Do you guys face any issues with bluetooth speakers or taking calls via bluetooth in car?)
Click to expand...
Click to collapse
I've been using LineageOS with 0 problems so far. But it does take some time to set it up that way. For instance, you need to flash the MIUI camera to improve camera performance, and under display calibration adjust the RGB values to 90% to prevent image retention (a problem on MIUI too).
I can confirm that Bluetooth works fine, calling is clear and battery life is good but not better/worse than MIUI. I haven't tried taking calls over a car's Bluetooth.
You should also check out the Xiaomi.eu weekly MIUI 9 builds as they usually fix what Xiaomi broke in their MIUI builds and are actually supported by Xiaomi.
Mr.201 said:
You can start with jdcteam's aosp. Has been really solid for me.
Click to expand...
Click to collapse
xdadevet said:
I've been using LineageOS with 0 problems so far. But it does take some time to set it up that way. For instance, you need to flash the MIUI camera to improve camera performance, and under display calibration adjust the RGB values to 90% to prevent image retention (a problem on MIUI too).
.
Click to expand...
Click to collapse
Thank you for the recommendations guys. Are you using the stock kernel or any custom kernel like BB kernel, Nagatobimaru etc?
What is your opinion about AOSPA and RR ?
AOSP Extended all the way. Using it from past 3 months.
arnavbatra said:
Thank you for the recommendations guys. Are you using the stock kernel or any custom kernel like BB kernel, Nagatobimaru etc?
What is your opinion about AOSPA and RR ?
Click to expand...
Click to collapse
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
xdadevet said:
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
Click to expand...
Click to collapse
What do you mean by the image retention issue? And what have you calibrated? As far as I understand, you have just tweaked the RGB values of the screen. Can you tell me your values? I think the same thing can be done via Kernel Adiutor if you are on a kernel that supports KCAL. AFAIK, stock LOS kernel doesn't have it but most ROMs and all custom kernels have it.
What about AOSP by JDC team, it appears very stable with EAS?
xdadevet said:
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
Click to expand...
Click to collapse
Does this problem have anything in common to the top edge of phone bleeding? Isnt that hardware's fault?
RootNightmareX said:
Does this problem have anything in common to the top edge of phone bleeding? Isnt that hardware's fault?
Click to expand...
Click to collapse
Yes, it's the same problem - I am unaware whether this is a software or hardware problem, but you can correct it 100% with software. It looks like lightbleed right around the border of the phone and you can see ghosting of previus apps around the corners (especially on a grey background). It's easy to fix in LineageOS, but I've had trouble in every other ROM I tried so far.
xdadevet said:
Yes, it's the same problem - I am unaware whether this is a software or hardware problem, but you can correct it 100% with software. It looks like lightbleed right around the border of the phone and you can see ghosting of previus apps around the corners (especially on a grey background). It's easy to fix in LineageOS, but I've had trouble in every other ROM I tried so far.
Click to expand...
Click to collapse
Its not ghosting its more like a radiant, something like a glow that increase and decrase...
..
arnavbatra said:
What do you mean by the image retention issue? And what have you calibrated? As far as I understand, you have just tweaked the RGB values of the screen. Can you tell me your values? I think the same thing can be done via Kernel Adiutor if you are on a kernel that supports KCAL. AFAIK, stock LOS kernel doesn't have it but most ROMs and all custom kernels have it.
What about AOSP by JDC team, it appears very stable with EAS?
Click to expand...
Click to collapse
It looks light an orange tinted lightbleed right around the borders of the display and some ghosting of previous apps are overlayed on the current app (especially visible on grey backgrounds). Check the attached image to see what mean, and this is only about 50% of how bad it can get if you don't adjust for it.
Yes I just tweaked the RGB values to 90% (anything more and you can still notice the effect).
I tried using Kernel Adiutor to fix this problem to no avail, using different ROM and kernel combinations. I never checked if the kernel supports KCAL specifically though.
It's been too long since I used JDC's ROM, but if I remember correctly it was stable and fast but lacked essential features at the time (music playback controls, lockscreen torch, display calibration settings). Their Oreo ROM is far ahead of Lineage 15 in in terms of stability though, not that it's DD ready.
xdadevet said:
It looks light an orange tinted lightbleed right around the borders of the display and some ghosting of previous apps are overlayed on the current app (especially visible on grey backgrounds). Check the attached image to see what mean, and this is only about 50% of how bad it can get if you don't adjust for it.
Yes I just tweaked the RGB values to 90% (anything more and you can still notice the effect)
Click to expand...
Click to collapse
Woah thanks for sharing this man, I didn't know about this, can you please share the screenshot of the settings you have made?
I have the same issue and I can't decide which ROM to flash. MIUI 8 is too laggy, MIUI 9 is faster but all apps crash randomly. I will unlock my phone tomorrow (after the stupid 72 hours waiting period) and I am hoping that this discussion will help us decide. Most probably it will be a choice between Xiaomi.eu or LOS.
arnavbatra said:
Woah thanks for sharing this man, I didn't know about this, can you please share the screenshot of the settings you have made?
Click to expand...
Click to collapse
Sure, no problem. You can find these Settings under Settings > Display > Live Display > Colour Calibration
Xpme said:
I have the same issue and I can't decide which ROM to flash. MIUI 8 is too laggy, MIUI 9 is faster but all apps crash randomly. I will unlock my phone tomorrow (after the stupid 72 hours waiting period) and I am hoping that this discussion will help us decide. Most probably it will be a choice between Xiaomi.eu or LOS.
Click to expand...
Click to collapse
As someone who recently used both Xiaomi.eu and LOS14.1 I might be able to clear that up.
Xiaomi.eu MIUI9 build is almost identical to MIUI 8. There are a few minor tweaks to the UI such as the task switcher which is now more immersive and the new icon pack. Settings are now more bundled together and ROM/System info is graphically displayed. Split screen multitasking seems to be the only new feature. I haven't experienced a single app crash, but the system animation speed was set way to fast by default and transition animations show tearing each time you switch apps. In short, it's fast but not smooth.
I switched back to LOS quite quickly. The only feature MIUI has that LOS doesn't is Dual Apps, and since I don't use that the choice was very simple. LOS is much smoother and faster, with minimal features on top of AOSP. I enjoy the additions, it doesn't feel bloated or barebones.
If you are going to use LOS, I recommend doing the following:
-If you have a 32GB Mi5, flash the LOS stock freq kernel
-Set the display calibration as per my previous posts
-Activate touch home button, always on fingerprint unlock
-Install Magisk
-Flash MIUI camera Magisk module + OISprop-Magisk
-Flash iYTBP Magisk module
-Flash unified hosts Adblock Magisk module (make sure to select systemless hosts in Magisk settings)
-Install Google camera HDR+
-Use Nova (paid) or Lawnchair (free) as the launcher
That should get you going and solve most if not all annoyances coming from MIUI. You'd be amazed with the quality of Google Camera HDR+! Just check the attached samples (they are all compressed due to Xda but you'll get the point).
xdadevet said:
As someone who recently used both Xiaomi.eu and LOS14.1 I might be able to clear that up.
Xiaomi.eu MIUI9 build is almost identical to MIUI 8. There are a few minor tweaks to the UI such as the task switcher which is now more immersive and the new icon pack. Settings are now more bundled together and ROM/System info is graphically displayed. Split screen multitasking seems to be the only new feature. I haven't experienced a single app crash, but the system animation speed was set way to fast by default and transition animations show tearing each time you switch apps. In short, it's fast but not smooth.
I switched back to LOS quite quickly. The only feature MIUI has that LOS doesn't is Dual Apps, and since I don't use that the choice was very simple. LOS is much smoother and faster, with minimal features on top of AOSP. I enjoy the additions, it doesn't feel bloated or barebones.
If you are going to use LOS, I recommend doing the following:
-If you have a 32GB Mi5, flash the LOS stock freq kernel
-Set the display calibration as per my previous posts
-Activate touch home button, always on fingerprint unlock
-Install Magisk
-Flash MIUI camera Magisk module + OISprop-Magisk
-Flash iYTBP Magisk module
-Flash unified hosts Adblock Magisk module (make sure to select systemless hosts in Magisk settings)
-Install Google camera HDR+
-Use Nova (paid) or Lawnchair (free) as the launcher
That should get you going and solve most if not all annoyances coming from MIUI. You'd be amazed with the quality of Google Camera HDR+! Just check the attached samples (they are all compressed due to Xda but you'll get the point).
Click to expand...
Click to collapse
Wow! that was very informative. Thanks a lot man :good: . And yes, I get the point about the photo samples are amazing.
I have the 32 GB version and I already purchased Nova Launcher and use no matter what. I will have to find the addons you mentioned as I have no idea what they do. It's the first time I install a custom ROM on my MI 5. One final question, do you have any thoughts on AOSP Extended?
@xdadevet
Hi, where is OISprop module ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
Xpme said:
Wow! that was very informative. Thanks a lot man :good: . And yes, I get the point about the photo samples are amazing.
I have the 32 GB version and I already purchased Nova Launcher and use no matter what. I will have to find the addons you mentioned as I have no idea what they do. It's the first time I install a custom ROM on my MI 5. One final question, do you have any thoughts on AOSP Extended?
Click to expand...
Click to collapse
I can add all the files you need to a dropbox folder and share the link if that would be easier? I find that the Mi5 is super easy to modify, you shouldn't worry too much. I'll add the firmware you need and GAPPS if that would help you transition.
Yes, AEX is a great ROM with many features. Most Devs seem to be on it (going by their discussions). I haven't found a way to fix my LCD issues on AEX yet, which is the main reason for not using it currently.
rafix96 said:
@xdadevet
Hi, where is OISprop module ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
Click to expand...
Click to collapse
You need to run the apk after you flashed the magisk module and rebooted your phone to calibrate the OIS.

[KERNEL]Savagezen's Angler Kernel[Dec 2018][Pie][Oreo][Linaro][Clang][3.10.108]

This is the first project I've shared on XDA, though I've maintained it for personal use for a while and posted some prior incarnations on Google+. Hope you enjoy it!
Features:
December 2018 security patch
open source: kernel, anykernel
forked from Franco Kernel
merged Linux Stable 3.10.108
Compiled with Linaro 4.9 and CopperheadOS's Hardened Clang
I/O Schedulers: noop (default), cfq, deadline, fiops, row, zen, maple, sioplus
TCP algorithms: Bic, Cubic, Htcp, Hybla, Vegas, veno, Westwood (default), Reno
FK Features: disabled verified boot flag for Android Pay (root still breaks), support for FKUpdater performance profiles, support for FKUpdater App (not verified as I don't use the app myself), KCAL tweaks in init script.
Reduced wifi wakelocks and wakelock period
Removed possible bluetooth memory leak
KCAL color control support
KCAL brought to Linux guidelines
Spectrum Profile Support: dozens of profiles from around the web included in source code
Touchboost disabled in spectrum profile
Filesystem Support: F2FS, vFAT, EXT4, NTFS
MSM hotplug driver (disabled by default, but toggle included in source code)
Fingerprint boost from Electron Kernel
Wireguard support
Power Efficient Workqueues
State Notifier
Tickless System / Idle
Gentle Fair Sleepers
Hima hotplug driver (see 2018-09 release notes)
Wake Gestures (partial, see 2018-09 release notes)
Many security / hardening features from CopperheadOS (see 2018-12 release notes)
Downloads:
Oreo, 8.1 (Stable / Final): angler-kernel-20181221.zip
Pie, 9.0 (Testing Builds): pie-testing-aosip-20190130.zip, pie-testing-statixos-20190130.zip
Installation:
Boot to TWRP, backup (boot, system, data)
Wipe Dalvik / ART Cache and Cache
Flash the kernel.zip
Wipe Dalvik / ART Cache and Cache
Reboot and enjoy
Note: Sometimes rebooting directly from TWRP results in a boot freeze at the Google splash screen. Just power off and boot up again.
Battery Life / Performance Tests:
Spectrum: Battery: Total Drain: 6.8%/h, Sleep Drain: 4.96%/h, 11% SOT, 17.8 Hour Test (tested version - kernel 20180728, battery v1.3 profile)
Spectrum: Balance: Total Drain: 9.7%/h, Sleep Drain: 6.6%/h, 12% SOT, 19 Hour Test (tested version - kernel 20180728, balance v1.2 profile)
Older Version: June 2018
Thanks:
@osm0sis / AnyKernel2
@nathanchance / Flash Kernel and many guides
@franciscofranco / Franco Kernel
@frap129 / Electron Kernel
@flar2 / ElementalX Kernel
@Adi Shakthi / God's Kernel
@zx2c4 / Wireguard
@phantom146
PS: I'm on Telegram now too!
Profile: @savagezen
Discussion for this kernel: @sz_kernel_angler
Want to stay even more up to date?
Install the IFTTT app
Get notifications for testing releases - Applet Link
Get notifications for source code releases - Applet Link
Changelog:
v20181221 Release Notes
v20181124 Release Notes
v20180910 Release Notes
v20180808 Release Notes
v20180728b - fixed spaces in localversion resulting in kernel name not showing in Settings app.
v20180728 Release Notes
Bugs:
Boot Loop / Freeze on Android 9.0 Oreo.
FAQ:
Need Help / Want to Help? Join the my Telegram Channel: @sz_kernel_angler
Is this kernel compatible with Android Pie (9.0)? It should work out of the box, however several users have reported boot freezes / loops on Pie. I haven't had a chance to test it fully in Pie and am still on Oreo myself. If you run into issues, try running with SELinux as permissive or reach out on Telegram.
Nice, gonna give this a run. Kudos for adding detailed instructions on your site.
Nice, was hoping for new kernel a long time
I would like to suggest the "Hima Hotplug" for your kernel, it is so fluid and great on battery life (experience from sphinx kernel for bullhead)
Pump Ac7i0n said:
Nice, gonna give this a run. Kudos for adding detailed instructions on your site.
Click to expand...
Click to collapse
You're welcome. It is as much for me to remember how to do stuff in the future with other devices as anything else. Glad others can benefit from it as well.
eurochild said:
Nice, was hoping for new kernel a long time
I would like to suggest the "Hima Hotplug" for your kernel, it is so fluid and great on battery life (experience from sphinx kernel for bullhead)
Click to expand...
Click to collapse
Thanks for the suggestion. Browsing source code now...
savagezen said:
You're welcome. It is as much for me to remember how to do stuff in the future with other devices as anything else. Glad others can benefit from it as well.
Thanks for the suggestion. Browsing source code now...
Click to expand...
Click to collapse
just wanted to say solid first public kernel. super smooth
Thank you for the new kernel,so far so good
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
aureljared said:
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
Click to expand...
Click to collapse
I see the same under about phone.
aureljared said:
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
Click to expand...
Click to collapse
Lawlrus said:
I see the same under about phone.
Click to expand...
Click to collapse
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
eurochild said:
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
Click to expand...
Click to collapse
Yeah I agree, it is, by no means, a deal-breaker. I just wanted to point it out for newcomers because I sure had a grand time panicking over whether or not the installation went through.
Currently using this kernel with ABC rom, so far the best kernel ever, very smooth and good heat output
aureljared said:
Yeah I agree, it is, by no means, a deal-breaker. I just wanted to point it out for newcomers because I sure had a grand time panicking over whether or not the installation went through.
Click to expand...
Click to collapse
eurochild said:
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
Click to expand...
Click to collapse
This does work on AOSiP. Stock ROM (and maybe others) it does not appear after tapping on "Kernel Version" in settings. As noted, third party apps like EX Kernel Manager and Kernel Auditor seem to display the kernel version correctly.
There are, in fact, spaces in LOCALVERSION in the config file. I'll add this under bugs in the second post and update when it's fixed.
PS: Glad you guys are enjoying it and to hear it runs smooth and cool! Usage stats for the 'battery' spectrum profile are in the updated OP. Testing the 'balance' profile now.
UPDATE 8/1: The 'kernel version' issues has been fixed. Notation is in second post and download link has been updated in OP.
This kernel kicks ass! Seriously, great work. One of my major complaints with the 6P was its over heating and then thermal throttling. I just didn't play certain games because of it. Now, after flashing this kernel it runs smooth and cool and games work again. Unreal. Truly love the way the phone works now. Not bad for battery life either but it's not my primary any more.
galakanokis said:
This kernel kicks ass! Seriously, great work. One of my major complaints with the 6P was its over heating and then thermal throttling. I just didn't play certain games because of it. Now, after flashing this kernel it runs smooth and cool and games work again. Unreal. Truly love the way the phone works now. Not bad for battery life either but it's not my primary any more.
Click to expand...
Click to collapse
Good to hear! Did you use the Gaming spectrum profile? I'm don't use my phone for games so I didn't test that outside of synthetic benchmarks. Also, the Battery spectrum profile should give pretty good battery life as it's very conservative.
Spoiler: I'm working on maybe adding the chill or relaxed governors to test as well.
No profiles, just default settings. I usually run a week or two on default before I mess around just so I can tell the difference in the tweaks.
I might play around but this phone is just for messing about now, picked up the Essential on the Prime deal and quite like it so the 6P is not a daily driver.
Gotcha. FYI the balanced profile is enabled by default.
savagezen said:
Gotcha. FYI the balanced profile is enabled by default.
Click to expand...
Click to collapse
Do you happen to have the link somewhere?
dirtyreturn said:
Do you happen to have the link somewhere?
Click to expand...
Click to collapse
All the profiles are in my AnyKernel repo on GitHub. There are a total of 30 profiles from around the web even though the Spectrum App only uses those numbered 0, 1, 2, and 3. I include my built kernel zImage-dtb in the AnyKernel repo so that you can clone it yourself and apply a different profile "manually" if you like. Just change the number in ramdisk/init.spectrum.sh, zip it up, and flash it.
Code:
if [ ! -f /data/property/persist.spectrum.profile ]; then
setprop persist.spectrum.profile 0 # change this number
fi
Note, if you use this method, and later select a profile from the Spectrum App, the Spectrum App choice will override the initial one, including after reboot -- because it applies the settings once the user space is reached.
@savagezen thanks! Also, kernel link?? I must be missing it.. Is it in the OP?
Sent from my PH-1 using Tapatalk

Categories

Resources