Welcome to the Unofficial Benschholds Custom Kernel Profile Sharing Thread for OnePlus 2
Introduction
I've been inspired by the Boeffla Kernel Profile Sharing thread from @v7
Boeffla Profile Sharing Thread
Links
Original Benschholds Kernel Thread
[KERNEL] [OnePlus2] [CM 13] Benschhold Kernel
Credits
@benschhold for his amazing work on the OnePlus 2.
I will refresh the Third Post your Kernel Audiutor profiles with a small description and maybe
the SOT time which you reached with your Profile.
How to Backup and Restore profiles in Synapse.
Backup your Profile
1. Start Synapse and tap on the upper left Corner
2. Go to the Profile Tab
3. Input profile name (Should not have any special characters) and press enter
4. Press check mark at the top
5. Press backup current profile.
6. If the backup was successful you'll get a toast saying so
Restore a profile1. Place profile .tgz file in /sdcard/Synapse/saved_profiles
2. Press restart synapse
3. Go into profile section and select profile you want (can't have any special characters) press the check at the top.
4. Press apply profile
5. Open synapse again and hit the "X" at the top and wait for settings to apply
6. Close synapse and open it again and press the X again
7. Repeat step 7 until the "X" no longer appears
Apply the profile on boot1. Go into settings and check apply on boot
2. Do not reboot for at least 2 minutes or the settings will get reset.
PS: Make sure you have set SeLinux to Permissive.
NOTE : If a profile doesn't setup correctly, Clear synapse data.. Reboot if necessary.
Note 2 : For best results, Reboot and charge till 100% after applying a profile.
How to save Profiles in Kernel Adiutor
Just place the Profiles.json in "/data/data/com.grarak.kerneladiutor/files/"
This is the place where you Profile is saved too.
recently it is impossible to save more than one Profile at the same time in the Profile
Bensch decided to go forward with Kernel Adiutor instead of Synapse.
So feel free to post your profiles for benschs kernel
Kernel Adiutor Profiles.
Daily-Usage Profile
@benschhold Battery Profile
@xdvs23 Daily & Benchmark Profile
Performance Profile
@magnamentis ExtremeScoreProfile
@xdvs23 Daily & Benchmark Profile
Hybrid Profile@[B]ollimi1[/B] Battery & Performance Profile
@Darth
pls bringt it to the right section (general)
and thanks @Xendetor
But where are the profiles?
No one posts his profiles xD
Xendetor said:
No one posts his profiles xD
Click to expand...
Click to collapse
Hi Xendetor,
I want to suggest to rename the thread into "Aduitor 'and' Synapse" profiles because since v1.9 bensch-kernel comes with Aduitor.
It is indeed possible to flash the ukm.zip and using Synapse furthermore as kernel tweaker but I think the most people are too lazy to set up Synapse and disable Aduitor and/or they have problems with Synapse(like me) and prefer to use the build-in Kernel Aduitor.
You could create an area for Aduitor profiles and another for Synapse profiles.
I know @benschhold has create an Auditor profile for better battery usage and other forum members like @magnamentis also posted their profiles in benschholds kernel thread.
I think it would help to ensure that your site will be used from more peoples like now and If you decide to do this, I'll be the first sharing my profile here!!:good:
Okay, today i've no possibilities to change the thread Name, tomorrow i will post the profiles from bensch and magnamantis here.
23.03.2016 *Updated... 2 Profiles in 1 .zip from ollimi1 added
22.03.2016 *Updated... 2 Profiles from Magnamentis and Benschhold added
Xendetor said:
*Updated... 2 Profiles from Magnamentis and Benschhold added
Click to expand...
Click to collapse
Hi Xendetor,:highfive:
nice to see you follow my recommendations. :good:
Here are my profiles for all day usage and with a second high performance benchmark and gaming profile.
- The "all-day-profile" is well balanced to achieve best possible screen on "and" off times, good performance, fast response and best battery.
- The bench/gaming profile is probably self-explanatory and was made to get every single bit of performance from your device.
If you want you can put it into the list of other profiles
(And guys, do not forget to enable "apply on boot" for all sections with modifications and full reboot the device to apply the applied profiles properly! If something goes wrong, disable all "apply on boot" settings, full reboot and start from scratch with modifications.
Although I didn't have any temperature problem with the gaming profile, I recommend to not permanently use it, because of the thermal settings I've made.)
ollimi1 said:
Hi Xendetor,:highfive:
nice to see you follow my recommendations. :good:
Here are my profiles for all day usage and with a second high performance benchmark and gaming profile.
- The "all-day-profile" is well balanced to achieve best possible screen on "and" off times, good performance, fast response and best battery.
- The bench/gaming profile is probably self-explanatory and was made to get every single bit of performance from your device.
If you want you can put it into the list of other profiles
(And guys, do not forget to enable "apply on boot" for all sections with modifications and full reboot the device to apply the applied profiles properly! If something goes wrong, disable all "apply on boot" settings, full reboot and start from scratch with modifications.
Although I didn't have any temperature problem with the gaming profile, I recommend to not permanently use it, because of the thermal settings I've made.)
Click to expand...
Click to collapse
thanks ollimi1 for sharing your profiles. Also the thread is updated.
Xendetor said:
thanks ollimi1 for sharing your profiles. Also the thread is updated.
Click to expand...
Click to collapse
Hello how can i use this profile i tried to put the json file on root/data/data/com.grarak.kernelauditor then files and then go to kernel auditor and then profiles but i says that there is none profiles.
Should i flash by recovery (there is a meta-inf folder)
Ps: i'm on RR with Benschold kernel 2.7
Chris-woods said:
Hello how can i use this profile i tried to put the json file on root/data/data/com.grarak.kernelauditor then files and then go to kernel auditor and then profiles but i says that there is none profiles.
Should i flash by recovery (there is a meta-inf folder)
Ps: i'm on RR with Benschold kernel 2.7
Click to expand...
Click to collapse
I too am having trouble using these profiles. Are we just overwriting the existing profiles.json in files?
Doesnt seem to show up in the profiles section in Kernel Adiutor.
Probably a stupid question but I may as wel ask..
Edit: It works now. you have to enable lord boeffla's core control option for it to show up. idk why but when i enabled that i found the profile
SometimesMonday said:
I too am having trouble using these profiles. Are we just overwriting the existing profiles.json in files?
Doesnt seem to show up in the profiles section in Kernel Adiutor.
Probably a stupid question but I may as wel ask..
Edit: It works now. you have to enable lord boeffla's core control option for it to show up. idk why but when i enabled that i found the profile
Click to expand...
Click to collapse
I don't understand how did you do. Where do I have to put the json file and where can I activate the module on Kernel Auditor
Thanks in advance
Chris-woods said:
I don't understand how did you do. Where do I have to put the json file and where can I activate the module on Kernel Auditor
Thanks in advance
Click to expand...
Click to collapse
You put the json file in data/data/com.grarak.kerneladiutor/files
There should be a profile.json file in there so just copy the one youve downloaded and overwrite the one already there.
there should be a profile section in the kernel adiutor and it should have the profile there, if so just apply the profile.
SometimesMonday said:
You put the json file in data/data/com.grarak.kerneladiutor/files
There should be a profile.json file in there so just copy the one youve downloaded and overwrite the one already there.
there should be a profile section in the kernel adiutor and it should have the profile there, if so just apply the profile.
Click to expand...
Click to collapse
Thanks will try when my battery will be charge at 100%
Its recommended to restart kernel adiutor after replaced profile.json
So, I seem to be having the same problem as @Chris-woods. I've copied the "profiles.json" file into the correct place (Though I don't have a "data/data/com.grarak.kerneladiutor/files," mine is under "Android/data/com.grarak.kerneladiutor/files"), restarted Kernel Adiutor, and nothing is shoing under the "Profile" section. I wanted to try what @SometimesMonday mentioned, but it seems Core Control is already enabled.
I have the same problem, can someone help us, please ?
Okay, i dont have a solution for this, but just try one thing... Installiert es Explorer and uninstall kernel adiutor. After that, es Explorer asks you for delete the kernel adiutor folder. Press Yes.
After that, install the kernel adiutor from the ZIP file from benschs kernel. After that open kernel adiutor and save Any profile. Go to the folder of it and replace the downloaded profile.json with that in the folder and try to load it in the profile tab of kernel adiutor.
Related
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
greenAlgae said:
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
Click to expand...
Click to collapse
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
dmrlook said:
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
Click to expand...
Click to collapse
Well, actually I never try to change the default governor from ondemand before. Partly because I compiled my kernel using official/stock kernel source, so there's only those stock governor options and ondemand seems to be the best option. My phone is SE Xperia Mini Pro / sk17i and currently running Freexperia CM7 rom. The kernel provided has very good performance but seems to cause the battery draining too fast for me, so I compiled a 'stock' kernel to use with it.
After your post above, I tried to add more governor options from freexperia kernel source, recompiled the kernel, edit the init script in ramdisk, and flashed it to my phone.
Here's my result:
- the script in init.d doesn't seems to change the default governor. I don't know exactly why. Other script in init.d seems to run just fine, I can set scaling_min_freq and scaling_max_freq with it. I also check the permission, it's rwxr-x-r-x, but it doesn't seem to be executed at boot.
- in every startup, the rom executes the script in /data/local/userinit.sh too, but setting default governor from that script also doesn't succeed.
- only thing that can change the default governor is adding the line 'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor smartassV2' in 'on boot' section of the init.semc.rc file.
I'm not a developer and i know every rom might be different. So you might need to ask in your rom specific thread, one of the devs might be able to help you there.
Otherwise, you can always set the default governor at boot using app like 'setcpu' or ' No-frills CPU Control'
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
today i was looking for a solution like you and watched this post,finally i could solve the problem.Look at the scripts on /system/etc folder, in my case there was a script located there that changed the governor to ondemand,its name init.qcom.post_boot.sh maybe on your device it has other name.
old thread, i know, but im attempting to root a samsung replenish thats running 2.3.6. can anyone help? nothing is working.
EDIT: LOL. i was thinking "this phone is that old...? this is ridiculous that its running a higher form of gingerbread than my 4 month old phone is......" but i was looking at the join date not the post date, and i thought the thread was 3 years old. LOL
Lemme note here, I deserve no credit, all code and all work was done by Eugene_373 and anyone mentioned below, this is simply a share from the T-MOBILE GALAXY s2 section of XDA, I have fully tested this app and found it to be working wonderfully on my SGH-I777
I love eugene's deving hence the share I hope you all enjoy if this has some way helped you in anyway go over to eugene's profile donate/thank him
App Version:
CPU Sleeper
~Free to all XDA Memebers
~ Must Be Rooted to use App
What is it?
Its a fairly simple App that will put CPU 1/2/3 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1/2/3 back ONLINE.
How does it work?
Since we have Dual & Quad core CPUs, we have a CPU 0 and a CPU 1/2/3, core 0/1/2/3, while the screen is off we really only need to have 1 core active "CPU0", this App will make sure CPU 1/2/3 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
Compatibility?
Works with any Dual Core & Quad Core Devices!
~ICS
~Gingerbread
Battery Saving?
Battery savings all depends on Usage & idle times.
App Download: CPUSleep.apk
Version 1.5 Release Notes:
~ Battery Drain issues 100% Fixed
~ Screen on Lag 100% Fixed
~ SU issues 100% fixed
~ Auto-Start on reboot 100% Fixed
~ Fixed Auto-Start killing Cell Service
~ Su Request on Screen Wake Fixed
~ Debugging enabled for those wanting to check if it's working.
Credits:
Handlerexploit for co-creation of this wonderful App.
Script Version!
Code:
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
[B]CPU Sleeper[/B]
[U]What is it?[/U]
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
[U]How does it work?[/U]
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
[B][COLOR="red"]WARNING! READ THIS![/COLOR][/B]
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
[U][COLOR="Red"]Instructions[/COLOR][/U]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
[I]Version 1: Flashable[/I]
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
[I]Version 2: Script only[/I]
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
[U]Init.d supported kernel:[/U]
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Once done, reboot the system, and it will take effect when your system is finished rebooting.
[U]Script Manager[/U]
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
[U]What do I do if I can't boot after using this?[/U]
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
[B]Downloads[/B]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[URL="http://d-h.st/N1N"]CPU Sleeper script only[/URL]
Quad Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[url=http://www66.zippyshare.com/v/9249467/file.html]cpusleep[/url]
[COLOR="Red"]Download: ClockworkMod Recovery .zip for T989 / I727[/COLOR]
[url=http://www19.zippyshare.com/v/51836824/file.html]CPU_Sleeper.zip[/url]
Thanks to [COLOR="DarkGreen"]pio_masaki[/COLOR] for rewriting the OP
Used this for a day now. Seems to work. Will test some more. Using the app by the way.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
hotplug, sched_mc
I'm running aokp + fluxxi also..is this app any different from hotplug settings or SCHED_MC level settings in xxTweaker?
Krysten17 said:
I'm running aokp + fluxxi also..is this app any different from hotplug settings or SCHED_MC level settings in xxTweaker?
Click to expand...
Click to collapse
Hotplugging and sched_mc are kind of synonymous. The difference is that sched_mc allows you to force a particular pattern of behavior (1 = fill 1 core first, 2 = activate both). This app attempts to force 1 core offline when the screen is off. It's kind of like an extreme version of sched_mc = 1 in that it doesn't allow both cores to be activated. However, I'm not sure if it is capable of preventing the second core from coming online. It may check periodically and subsequently turn it off. I don't think it would have much benefit on our devices; our hotplugging is competent and sufficient. I suppose anything is worth trying though.
looks interesting!
Every now and then i get cpusleep has been granted superuser permissions when the screen is on and im surfing the net or playing a game.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
stevehkim said:
Every now and then i get cpusleep has been granted superuser permissions when the screen is on and im surfing the net or playing a game.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
Click to expand...
Click to collapse
Oh I forgot to update the APK link its been updated download and install the latest version
Sent from my SGH-I777 using Tapatalk 2
Here's the original thread created by the app dev if anyone was wondering:
http://forum.xda-developers.com/showthread.php?t=1745132
Tried it for almost 3 days. Didnt help. No noticeable gains so I uninstalled
just uninstalled it too after seeing no real gain for two days.
Sent from my SGH-I777 using xda app-developers app
Thanks for all who posted. I'm running xxtweaker fluxii aokp . Any advice other than what's listed here for hot plug settings. Thanks
Sent from my SGH-I777 using xda premium
Does it work fine with setcpu ?
Hey guys, this is just a version of @franciscofranco's kernel built with DoubleTap2Wake and Sweep2Wake from Bricked Kernel merged in.
(By downloading and installing the kernel you assume all responsibility for any damage to your device, but I don't post images with the intention of this occurrence and test them to the best of my abilities.)
Download:
r57
boot image - https://sundergaming.com/downloads/hammerhead/franco.Kernel/boot-franco.Kernel-r57-dt2w.img
md5 - 9ba11b4c3f5cd963c69d54bbfd919fe1
zip - https://sundergaming.com/downloads/hammerhead/franco.Kernel/zips/boot-franco.Kernel-r57-dt2w.zip
*Color tweak is integrated since r30, check 2nd post for information on how to enable.
Want a dedicated build for color tweaks because your boot animation isn't pretty enough? Build it yourself. Sources below.
**Test builds posted throughout the thread.
Kernel is for 4.4.1/2 since r19
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in recovery
Sources
Kernel - https://github.com/PhantomGamers/hammerhead
Ramdisk - https://github.com/PhantomGamers/ramdisk_hammerhead
Credits
@franciscofranco for his kernel - http://forum.xda-developers.com/showthread.php?t=2508284
@show-p1984 for the dt2w and s2w additions - http://forum.xda-developers.com/showthread.php?t=2524557
@flar2 for his on-the-fly color tweak, power key touch to wake suspend, and other general dt2w improvements. - http://forum.xda-developers.com/showthread.php?t=2519607
I do accept and appreciate any donations but I urge you to first donate to the amazing developers listed above for their work because my contributions are minimal and without them this kernel variant would not exist.
Franco's original thread for reference only:
franciscofranco said:
Hi all.
Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path.
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in the recovery
Changelog:
http://kernels.franco-lnx.net/Nexus5/4.4/appfiles/changelog.xml
franco.Kernel updater Free apk: http://forum.xda-developers.com/showthread.php?t=1867127
Nexus Display Control Free apk: http://forum.xda-developers.com/showthread.php?t=2424467
Got any questions that you couldn't find after searching?
FAQ: http://forum.xda-developers.com/showthread.php?t=2532422
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Click to expand...
Click to collapse
XDA:DevDB Information
franco.Kernel+DT2W/S2W, a Kernel for the Google Nexus 5
Contributors
PhantomGamers, franciscofranco, show-p1984, flar2
Kernel Special Features:
Version Information
Status: Stable
Created 2014-02-06
Last Updated 2014-02-06
Kernel Settings
Disabled by default. To enable execute the code next to terminal in adb shell or terminal emulator as root.
If you wish for it to be automatically enabled on boot you can create the file named in the boot section.
After creating this file you can still execute the terminal code to enable it immediately or you can just reboot and have the kernel enable it for you.
[DT2W/S2W]
S2W
terminal -
Code:
echo 1 > /sys/android_touch/sweep2wake
boot - Create /sdcard/fkSettings/fks2w
DT2W
terminal -
Code:
echo 1 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2w
Bottom Half Screen DT2W (Only allows you to double tap bottom half to turn screen on, instead of above.)
terminal -
Code:
echo 2 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2wps
S2Sleep
terminal -
Code:
echo 1 > /sys/android_touch/s2w_s2s
boot - Create /sdcard/fkSettings/fks2s
PWRKEY_SUSPEND (Turns off touch to wake when display is turned off with power button, reenables when turned on, useful for long idle periods, unaffected by sweep to sleep)
terminal -
Code:
echo 1 > /sys/module/qpnp_power_on/parameters/pwrkey_suspend
boot - Create /sdcard/fkSettings/fkpwrks
Touch Wake Timeout
terminal -
Code:
echo 15 > /sys/android_touch/wake_timeout
(15 is an example, include the number of minutes you prefer)
boot - Create /sdcard/fkSettings/fkwt with number of minutes to delay timeout (IE: text file with "15" inside)
[COLOR]
*This tweak is experimental and you use it at your own risk.
**Breaks gamma calibration apps.
terminal -
Code:
echo 1 > /sys/module/mdss_dsi/parameters/color_preset
boot - Create /sdcard/fkSettings/fkcolor
[WIDGETS]
*Thanks to @JsChiSurf
http://forum.xda-developers.com/showthread.php?t=2626476
[App]
*Thanks to @casperpas
http://forum.xda-developers.com/showpost.php?p=51682981&postcount=839
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
kashix said:
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
Click to expand...
Click to collapse
Elementalx and Bricked don't have Franco's custom hotplug driver, personally that's the main selling point of his kernel to me.
I don't particularly care for these features anyway though and just used this as a learning experience to build kernels.
(I am currently running this build though to play around with it, haven't noticed a huge difference in battery life myself)
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
This is very tempting to try out.
Thank you!
---------- Post added at 07:57 PM ---------- Previous post was at 07:57 PM ----------
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Flashify seems like it'd do the trick, if original Franco kernels are any indication.
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Yeah Flashify seems like your best bet if you're rooted.
I might try and include zip releases in the future, sorry for the inconvenience.
grumphy said:
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
Click to expand...
Click to collapse
Thanks for the confirmation!
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Nastybutler said:
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Click to expand...
Click to collapse
Yeah that's my plan, I'll most likely keep this going until franco includes his own DT2W feature or unless I run into some technically difficulty.
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Nastybutler said:
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Click to expand...
Click to collapse
The space between the 1 and the > is essential.
PhantomGamers said:
The space between the 1 and the > is essential.
Click to expand...
Click to collapse
Eureka! That was my problem. Thanks! Works a treat.
Gonna give this a whirl
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Also so glad you carried over francos screen calibration too! you rule! And so glad you'll be supporting until (if) franco implements it.
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
tyrellcorpnexus said:
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Click to expand...
Click to collapse
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
tyrellcorpnexus said:
Also so glad you carried over francos screen calibration too! you rule!
Click to expand...
Click to collapse
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
Click to expand...
Click to collapse
I see I see. Thanks again! Hitting that button one time to go to sleep is better than waking every time as well that is for sure!
I'm used to putting my device to sleep with a gesture on Activator with my JB'en iPhone 5. But I still have to wake it using home or lock button so I guess its still needed on that as well..
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
This is too good
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
---------- Post added at 11:47 AM ---------- Previous post was at 11:40 AM ----------
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Click to expand...
Click to collapse
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Nastybutler said:
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
Click to expand...
Click to collapse
Do you have a link to the APK and maybe a screenshot of what it looks like? I'd only be interested in this toggle.
tyrellcorpnexus said:
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Click to expand...
Click to collapse
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
tyrellcorpnexus said:
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
Click to expand...
Click to collapse
Nastybutler said:
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Click to expand...
Click to collapse
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
PhantomGamers said:
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Ah, in that case, that'd be awesome!
No worries, appreciate your work thus far.
This is so great :highfive:
[kernel][v3.5] leanKernel: minimalistic kernel (1/28/16)
leanKernel is not for everyone.
My philosophy is to keep the kernel footprint as small as possible by trimming as much fat as possible, and at the same time keeping it stable, power efficient, and fast. leanKernel is designed to be a drop in replacement for stock kernel, and so it tries not to deviate too far from stock.
You will find that it's lacking some of the bells and whistles of other custom kernels, so if you like features you came to the wrong thread.
Here's a longer post on what leanKernel is about.
Also folks, please read the FAQ before asking questions.
INSTRUCTIONS
If you like to stay as close to stock as possible: 1) Download and flash the normal leanKernel build here (find the latest zip file) in recovery. 2) Reboot and enjoy better performance and battery life (hopefully). That's it! There's no need to flash stock kernel first, or to wipe caches.
If you like to customize, read through the feature list below, the FAQ (post #2), the changelogs, and optionally the entire thread. Then you'll know what to do.
DOWNLOAD (flash in recovery)
v1.x is for Android 5.0, and v2.x is for Android 5.1
main download
mirror (may need to refresh browser to see latest)
PREREQUISITE
Unlocked bootloader, custom recovery installed
Push bullet channel: imoseyon
FEATURES
custom voltage control - use your favorite app
updated to latest 3.10 Linux
interactiveX - screen_off_maxfreq support (default 2.2Ghz)
sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)
latest Linaro gcc 4.9 toolchain (optimized for a15 - thanks to Christopher83)
fat trimmed and various performance tweaks
f2fs support (updated to latest source from Samsung)
force encryption turned off (changed to encryptable)
overclocked to 2.9ghz (experimental - available as a separate build for now)
underclocked to 223mhz (experimental - available as a separate build for now)
Async Fsync
init.d support
cpu-boost control - enable/disable via lkconfig
lkconfig script for customizing leankernel (open terminal app, become superuser, then type "lkconfig" without quotes)
patched mpdecision to prevent changing min/max freq provided as flashable zip (in util directory)
color control (thanks to @savoca)
charging led support
a lot of unnecessary stuff removed from stock kernel
some components updated to Linux 3.18
random generation optimization including e/frandom support
pc/usb charging with boosted current ~300-400mA
some selinux fixes, selinux is enforced by default - staying true to stock (you can easily disable using lkconfig)
SLUB allocator updated to Linux 3.18
wake gesture control from flar2, modified for leankernel (also disabled in-call)
vibe strength control
much of the code is up to date with latest from CodeAurora
(mostly for devs) /sys/module/selinux/parameters/force_audit sysfs node to audit all/hidden selinux denies.
power aware cpu scheduling
faux sound enable/disable by sysfs (and lkconfig)
wakelock control (smb135x, wlan_rx, msm_hsic and sensor_ind)
leanKernel core control script
user option to prevent mpdecision/msm_thermal from changing min/max frequencies: frequency mitigation preventer
supports kexec for multirom
LKCONFIG
You can use lkconfig script to make custom changes to leanKernel (along with popular apps like Kernel Tweaker and Trickstermod). To run lkconfig, open terminal app, "su" (without quotes) to become superuser, enter, and then type "lkconfig" without quotes, then enter.
Code:
[email protected]:/ $ su
[email protected]:/ # lk
leanKernel configurator
---
0) display current settings
1) cpu frequency control
2) wake gesture control
3) wakelock control
4) charging led
5) rgb/picture control (advanced)
6) rgb/picture control (simple)
7) vibe strength
8) power saving mode for cpu scheduler
9) faux sound control
10) selinux mode
11) min/max freq change prevention
21) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit):
CHANGELOG
https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog
Thanks to @guitarshredder87, @Wera750, @akellar, and @grisha1 for testing test builds!
XDA:DevDB Information
Leankernel: Minimalistic Kernel, Kernel for the Nexus 6
Contributors
Imoseyon
Source Code: https://github.com/imoseyon/leanKernel-shamu
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-26
Last Updated 2016-01-31
FAQ
I'm having trouble waking the phone sometimes. Help!
We haven't really figured out exactly what's causing it - but there seems to be evidence that it's not limited just to leanKernel. One thing to try: if your ROM has a feature that prevents accidental wakeups, disable it!
I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?
* Read this post: http://forum.xda-developers.com/showpost.php?p=58135730&postcount=1474
* Short version: This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.. Launch lkconfig, choose core control, and choose one of the options in core control.
Will flashing leankernel decrypt my phone storage?
If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you format data. Once you format you will stay decrypted until you decide to encrypt again (see below). If you're already decrypted, leanKernel will not force encrypt automatically.
What do I do to encrypt again?
There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):
Code:
[email protected]:/ # start encrypt
You will see the phone hot boot and once it comes up you will be encrypted again. Keep in mind that if you want to decrypt again you'll have to wipe.
How do I check the PVS BIN of my cpu?
Code:
[email protected]:/ # cat /proc/cpu/msm_acpu_pvs
The number you get should range between 0 and 15 (inclusive). If you ended up with 15 congratulations. If you ended up with 0, go get it exchanged! Stock frequency/voltage table: http://pastebin.com/ZyGA9Tec
Which kernel control app do you recommend?
When v1.0 gets released it should come with "lkconfig" for tweaking some of the options. Otherwise, I tried Trickster and KernelTweaker, and they both seem to work ok.
What are ondemandX and interactiveX?
ondemandX and interactiveX are very very close to "stock" ondemand and interactive governors, respectively. The only difference is screen_off_maxfreq sysfs support. This means that it gives you the ability to limit phone's max frequency when screen is off. This feature could be effective in reducing battery usage, especially if you have a misbehaving app (or two) that consume cpu cycles while screen is off. The default value is 2265600 - if you change the value to your top speed you're effectively disabling the feature and restoring stock behavior completely. You can use an app like Trickster or Kernel Tweaker to modify screen_off_maxfreq.
HELP! I messed up with lkconfig - how do I go back?
Do not fret. Flash lkconfig_cleaner.zip from the "util" directory.
(If you want to do this manually), reboot the phone into recovery, mount /data, and delete everything in /data/data/leankernel. Once things are back to normal, re-run lkconfig to re-do your settings.
What is cpu-boost?
Read this post: http://forum.xda-developers.com/showpost.php?p=57215289&postcount=535
What is the best RGB setting?
http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620 (old)
http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017 (new)
What is power aware scheduling?
Read this post: http://forum.xda-developers.com/showpost.php?p=58313978&postcount=1651
I missed your kernel when I switched to N5. Glad to have you here
hmm.. a kernel. since its the first one posted here, im trying it out
Hell yeah. Ready to flash
Sent from my AOSP on Shamu using XDA Free mobile app
If I flash this it will decrypt right cool
digweed4me said:
If I flash this it will decrypt right cool
Click to expand...
Click to collapse
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
What app should we use to control? I remember you used to have your app right
holy **** Imoseyon. you made my Thunderbolt usable way back when. so glad to see you developing for the N6 now
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
Flashed it and yes decrypted thanks a lot
IMO!! Good to see ya again man. Can't wait to run your work again.
Appreciate it!
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
You mean lkconfig? Yeah that's coming later (along with a whole lot more).. If you're talking about f2fs, you'd want to use custom recovery but TWRP for shamu doesn't support f2fs yet - i had to do everything manually.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
i am still encrypted, and did not decrypt after flashing. so, all worked as it should.
Can we flash on stock ROM or is a custom ROM required?
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
I'm on a stock ROM.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
AFAIK, there's no way to decrypt without having to wipe unfortunately. Going the other way (unencrypted to encrypted) is super easy though, and no data loss.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
im on rastapop, an aosp based custom rom.
simms22 said:
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
Click to expand...
Click to collapse
Thanks for your quick response. Wipe what tho? Cache, dalvik, and what else? Hope you don't mean all my data.
You don't buy a Mustang for the gas mileage.
Kirisakura-Kernel for the Sony Xperia 1 IV
Hello everyone,
To keep it short: Here is Kirisakura- GKI - Kernel for the Sony Xperia 1 IV aka Nagara. Nagara is the internal codename for this years development platform of Sony Mark IV devices.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
There´s also a cpu-battery saver mode that cuts back the CPU max- freqs, but without the disadvantages like delayed notifications from built into the system user-space power-saving modes.
If that got your curious, I welcome you to continue reading if you´re still interested!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on kernel/common 5.10.149
- compiled with Clang 12.0.5
- CPU-Battery saver to be able to restrict max cpufreqs on the fly, without enabling powersaving modes that might cause missed notifications (see second post)
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- Power saving workingqueues enabled by default
- Change various drivers to use power efficient workingqueues. This compliments EAS in general
- implement LRNG (thanks @arter97, see arter kernel OP for more info )
- Enable support for TTL spoofing
- wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- f2fs improvments for better efficiency
- scheduler improvements
- psi fixes
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img or your magisk patched boot.img in case you want to go back to stock.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Firmware (check the feature list for the current firmware the source is based on). When there´s an OTA update for the Sony Xperia 1 IV it takes Sony a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
If you want to be sure there are no issues, always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder, or attached to the release posts in case AFH is wonky.
https://www.androidfilehost.com/?w=files&flid=335705
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
Android 13
1.0.0 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87711541
1.0.1 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87945391
1.0.3 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-88241223
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Sony for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_GKI_Nagara
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: Safetynet does not pass on my phone since I unlocked the phone, why is this so?
Answer: Google introduced hardware backed attestation recently. Unfortunately the old kernel tricks to still get safetynet passing won´t work. Instead you will have to rely on some magisk modules. Short guide in post #4 below.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from the matching firmware you are on (you can do so by using this tool or similar ones found on XDA and when googling around) and flash via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).
CPU-Frequency Limiting:
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature
Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,6GHZ/1,9GHZ/2,22GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,4GHZ/1,6GHZ/1,8GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,1GHZ/1,1GHZ/1,1GHZ (Little Cluster/Big Cluster/Prime Core)
Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!
Screenshots:
View attachment 5309899View attachment 5309901View attachment 5309903
This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.
How to pass Safetynet after unlocking the bootloader
With the introduction of hardware backed safetynet attestation, passing safetynet has become a lot more complicated.
Some probably remember a while ago, flashing a kernel that forced some flags was enough to pass it. However these days are gone.
Below is a short guide how to pass safetynet on phones that are flagged to use HW attestation (such as the ROG 5).
1. Make sure you´re running latest magisk canary.
2. In Magisk Manager enable both zygisk and deny list.
4. Download the latest Universal Safety Net Fix from @kdrag0n ´s github for zygisk cand flash it in Magisk Manager. Reboot.
5. Profit
Oh, my God! thank you so much for making the IV kernel
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
You are Awesome
tomatoketchup said:
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
Click to expand...
Click to collapse
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
htcmage said:
Oh, my God! thank you so much for making the IV kernel
Click to expand...
Click to collapse
Thaiban said:
You are Awesome
Click to expand...
Click to collapse
Freak07 said:
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
Click to expand...
Click to collapse
excellent <3, I don't need 4K 120fps recording I actually only do 1080p 24 because I like stabilization. so going to flash 64.0.A.8.25 and this kernel after that. million thanks!
It's a small amount, but I donated it, thank you always
htcmage said:
It's a small amount, but I donated it, thank you always
Click to expand...
Click to collapse
Thank you very much! I greatly appreciate it.
Hahaha... Hello my good friend @Freak07. Didn't know you were into Sony as well.
@Freak07 can you port it to xperia pro i ?
Developer, I have a question
If I use my work profile (shelter or island apk) I can't get into the settings menu I get a popup stating that the system UI is shutting down, maybe it's kernel related?
Should I uninstall Uperf before flashing?
Also thanks for this excellent work.
great work!Thx
to those who flashed, how is battery live ?
ist compüatible with latest sony update?
Would be interested to know, if it supports the old android kernels feature to emulate CD and DVD. Its a feature that DriveDroid needs to emulate a bootable DVD drive from an *.ISO hosted from an android device over USB. it was present in my older devices until XZ1 Compact and i was able to boot my pc off from a iso file hosted on my android device. It was much convinient than using silly PXE boot over eth0
No more update ?
Mrxyzl said:
No more update ?
Click to expand...
Click to collapse
OP will update when new Kernel sources are released and he has time. Mentioned in the first post.