A replacement for SONY's STAMINA MODE. Also a SMARTER GUIDE.
YOU DON'T NEED TO BLOCK WAKELOCKS, USE BATTERY SAVERS, XPOSED, AMPLIFY, etc.
Recommended for:
CM Based ROMS/Custom kernel users/Wifi users.
For those who want high SoT.:angel:
I am not going ask you for a beer or a cup of coffee, only read this guide and thanks me later. [emoji14]
(Recommended) CLEAN FLASH only ROM first, then proceed.
This guide is divided into 2 parts
Moto G 2014 Index of Threads. Thanks @Mister Magister (Easy to search all roms for G 2014).
1. CM based roms.
2. Stock based roms.
KERNELS -
Halogen - Battery/ Balanced/ Performance.
Spirit - Performance.
Optimus - Balanced.
decipher_simple - More battery/Balanced.[I prefer this]
BLOATWARE REMOVAL.
CM Based: Use ES Explorer. Grant SU permission (Root Explorer). Migrate to root.
OR use the Debloat Script. Supports all devices.
In SYSTEM/APP, delete these folders:
Basic Dreams, Browser, CellBroadcastReceiver, CM File Manager, Dash Clock, Eleven, Email, Exchange2, Galaxy4, HoloSpiralWallpaper, LiveWallpapers, LiveWallpaperPicker, NoiseField, PhaseBeam, PhotoPhase, PhotoTable, VisualizationWallpapers, WAPPush/WhisperPush.
Reboot the phone immediately.
BLOATWARE REMOVAL ZIP ADDED: Flash it through TWRP immediatedly after clean flashing the ROM. It will also clear the dalvik.
Now flash Minimal/Pico GAPPS for first time and kernel. (I prefer DECIPHER KERNELL- His own-my.zip recommended)
This kernel is simple one without useless tweaks and hence recommended for more juice saving!
Also flash L SPEED MOD @Paget96. Really working like a charm!! High savings!
YOU CAN UNDERCLOCK WITH L MOD INSTALLED! IT'S TOTALLY LAG FREE!
Stock Based: Rooted
Delete LIVE WALLPAPERS the same way. You can use Juice Defender Ultimate (Don't grant it SU permission).
FOR STOCK, ONE HAS TO USE XPOSED FOR AMPLIFY AND POWERNAP. There are too many wakelocks.
Basic Settings(Common for both)
Settings:
1. Wifi > Advanced - Scanning always available - OFF, Keep wifi on during sleep - Never.
2. Mobile networks: 2G (Wifi users).
3. Display - Sleep - 30 seconds, Daydream - Off.
4. Sound&Notifications - Other sounds - All OFF (your choice).
5. Battery : Turn on bat. saver - NEVER.
6. Location - OFF.
7. Keyboard - Popup, Sound, Vibrate - OFF.
8. Lockscreen -Display Music Visualizer - OFF.
9. Developer Options - Window, Transition animation scale - 0x (or 0.2x) and Animation Duration Scale - 0.2x
These settings should be tuned according to your needs.
If you wish keep AMBIENT DISPLAY to OFF and DOUBLE TAP TO SLEEP on nav bar.
For RESURRECTION ROM or any other cm based rom -
Don't use BATTERY BAR, SLIM RECENTS/ OMNI SWITCH, SLIM PIE, CLEAR ALL BUTTON, SUPERUSER INDICATOR, RR LOGO.
Keep it clean. Default animations.
Now the interesting part, TWEAKS
Recommended Apps - Drive Link below.
1. Kernel Adiutor.
2. SetCPU.
3. Greenify.
4. SDMaid Pro.
Start with
SET CPU;
Install the app, open it, grant SU permission.
Go to PROFILES tab, add a new profile.
My PROFILES BACKUP given in DRIVE LINK. Place it in root of internal storage and restore from SET CPU. {Updated}
Use min freq of kernels flashed! Either 96MHz or 300Mhz.
1. Turn this profile on when - Screen Off.
CPU Governor: On Demand
Min: 96Mhz Max: 600MHz
Priority: 100, EXCLUSIVE
2. Add a new profile - Battery Saver.
Turn profile on when - Battery 5%
CPU Governor: zzmove
Min: 96MHz Max: 787MHz
Notificaton: Persistent, Battery.
Priority: 99, EXCLUSIVE.
3. Again a new profile
Turn profile on when - Any of these are true. ( in it, add your CAMERA apps)
CPU Governor: Interactive.
Min: 96MHz Max: 1190MHz
Priority: 97, EXCLUSIVE.
4. New one
Turn profile on when - Screen ON.
CPU Govenor: zzmove (2).
Min: 96MHz Max: 1190MHz
Priority: 96, NOT EXCLUSIVE.
Below this priority you can add per app profiles as per your wish.
GRANT SU permission to SET PROFILES (UID)
KERNEL ADIUTOR
Settings for HALOGEN KERNEL, DECIPHER_SIMPLE (Do this after setting up SET CPU)
Open app,
CPU -
Min: 96MHz Max: 1190MHz
CPU Governor: Don't change. It will be as per SET CPU.
Multicore Power Saving: Enabled (Not Aggressive).
CPU Boost -Interval (Both) to 40ms.
Input Boost Freq: 787MHz
CPU Hotplug
Intelliplug -OFF.
MSMHotplug -OFF.
Alucard Hotplug -ON.
You can use INTELLIPLUG Balanced/ Eco Conservative/ Strict(1 core) Halogen too.
GPU
Max: 320MHz (if you are not a gamer or else 450)
Governor: Simple_OnDemand. (Gaming - Performance or msm-adreno_tz)
Save this profile. Allow the phone to rest for 15 mins.
Change the governor to IMPULSE and save another profile for performance. Use widget for applying.
Note - CPU Governors in SET CPU and Kernel Adiutor should match. Don't change the CPU Governor from Kernel Adiutor. Do it from Set CPU Profiles. Also you need to apply the profile after reboot.
GREENIFY - Root Mode.
Add all apps except Set Cpu, Kernel adiutor.
.
Don't use Xposed. It runs everytime you start module app., after all you are using custom rom.
Google Backup off, and all tracking services of GOOGLE PLAY SERVICES should be off.[emoji14]
No wakelock blocks. Auto Sync OFF after syncing - This does more saving.
With above tricks, I have achieved 0% percent drain. ( At night too.), 6hrs SoT :fingers-crossed:
If your phone reboots on unlocking, it means you have something wrong. Then change Set CPU SCREEN OFF profile governor to zzmove.
Code:
[U]CPU Governor Tunables[/U]-
* currently available profiles by ZaneZam and Yank555:
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (1)'def' -> Default -> will set governor defaults -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (2)'ybat -> Yank Battery -> a very good battery/performance balanced setting -
* - DEV-NOTE: highly recommended! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (3)'ybatext'-> Yank Battery Extreme -> like yank battery but focus on battery saving -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (4)'zzbat' -> ZaneZam Battery -> a more 'harsh' setting strictly focused on battery saving -
* - DEV-NOTE: might give some lags! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (5)'zzbatp' -> ZaneZam Battery Plus -> NEW! reworked 'faster' battery setting -
* - DEV-NOTE: recommended too!:) -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (6)'zzopt' -> ZaneZam Optimized -> balanced setting with no focus in any direction -
* - DEV-NOTE: relict from back in the days, even though some people still like it! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (7)'zzmod' -> ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (8)'zzperf' -> ZaneZam Performance -> all you can get from zzmoove in terms of performance but still has the fast -
* - down scaling/hotplugging behaving -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (9)'zzinz' -> ZaneZam InZane -> NEW! based on performance with new insane scaling active. a new experience! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (10)'zzgame' -> ZaneZam Gaming -> NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay -
* ------------------------------------------------------------------------------------------------------------------------------------------
* profile_number 0 means that you can tune the tunables according to your own liking. ;)
Thanks to zakee94. :good:
SDMaid Pro
Check all boxes in Corpse finder settings, and scan and remove all corpse. ( LEFTOVER Dalvik of removed bloatware).
For Stock Based roms/ Stock rooted: Use STELLAR Kernel
zzmove is preconfigured in all kernels above.
If you face lag using zzmove post in here.
RECOMMENDED APPS:
These are best apps
MUSIC PLAYER - Phonograph.
CAMERA - Open Camera. (Better than CM Camera)
NOTE MAKING - Google KEEP.
FILE EXPLORER - ES Explorer.
INSTALLER- Easy Installer.
CLOCK- Timely.
CALENDAR - Sunrise.
Disable this apps: Clock, Google App, Google Calendar Sync, Google Partner Setup, Market Feedback Agent, OTA (if you wish), PICO tts, Print Spooler.
Force Stop this apps at night: Calendar , Calendar Storage, Google Contacts Sync, Google Play Store, Key Chain, Location Services, Themes Provider. (For 0% drain also switch to FLIGHT MODE at night)
Use PICO GAPPS.
No BETTER BATTERY STATS, WAKELOCK DETECTOR, AMPLIFY, and BATTERY SAVERS.
Power Cycle - Charge from 5% to 100% and 10 min more to 100. Give up using phone while charging.
Thanks to all Devs for their support to G 2014. @zakee94 @-decipher-
Next time if anyone says that G 2014 has got 2070mAh battery only. Just reply them that " Since Motorola is grandtechy company they have certain quotas to maintain device ergonomics, so there's odd numbered 2070mAh battery!"
Any SUGGESTIONS will be appreciated. Hit thanks.
Thanks @Azmat Roomi for suggestion of L Speed Mod.
Link to DRIVE.
For OTHERS PHONES you can use the profiling and settings, set cpu.
HIT THANKS and ANSWER THE POLL if YOU have LIKED the THREAD!
Latest screenshot - 8hrs SoT:highfive:
ROM: cm-12.1-20151102-NIGHTLY-titan.zip
KERNEL: Decipher's Drive - [151101]my.zip
No Battery Savers, Xposed, Wakelock Blocker, L Speed Mod etc.
Only GREENIFIED some GCM apps, not all apps. This works. You shouldn't FORCE STOP apps unless they aren't responding. Reloading them takes more battery and memory. Only force stop apps with GCM and the ones you don't use.
Drain was 0% - Since it was 3%, the CPU governor was POWERSAVE. It may be 2-3% at night.
Attached- New SET CPU profiles backup - In the Drive.
Code:
[B]Kernel Adiutor Settings[/B]:
[B]CPU[/B] :
Min - 300MHz.
Max - 1190MHz.
[B]CPU Hotplug[/B] :
MPDecision - Max Cores - 2.
[B]GPU[/B] :
Max - 200MHz.
Governor - simple_ondemand.
[B]Virtual Memory[/B] :
dirty ratio - 70 .
dirty background ratio - 9.
dirty expire centisecs - 350.
dirty writeback centisecs - 500.
min free kbytes - 2857.
over commit ratio - 50.
swapiness - 90.
vfs cache pressure - 130.
[B]TCP Congestion Algorithm[/B] : westwood.
I don't know about the settings. I tried certain combinations and got good results.
Default zzmove profile was 8 - zzperf.
All other settings were at default.
DISABLE PER-APP PROFILES in BATTERY SETTINGS. Recommended.
Minimize HEAVY APPS before screen goes off - If you face lag while unlocking the phone with set cpu profiles screen-off active.
Nice guide and awesome battery life. Thank's for sharing.
-decipher- said:
Nice guide and awesome battery life. Thank's for sharing.
Click to expand...
Click to collapse
Very Nice Guide.I normally use to get 3-4hrs SOT.But after following this guide i am now easily getting 5-6hrs SOT.Guys give it a try it works like charm.
Azmat Roomi said:
Very Nice Guide.I normally use to get 3-4hrs SOT.But after following this guide i am now easily getting 5-6hrs SOT.Guys give it a try it works like charm.
Click to expand...
Click to collapse
Thanks for the review.:highfive:
@Abhishek Bhagwat Alucard seems to keep only one core active the whole time. What do you think about using MSM Hotplug instead?
Also ZZMOVE is a little bit sluggish for me, do you recommend any other governor for screen on?
godoy.rafa said:
@Abhishek Bhagwat Alucard seems to keep only one core active the whole time. What do you think about using MSM Hotplug instead?
Click to expand...
Click to collapse
One core is economy.
Also it delivers smooth performance with zzmove if you have followed the guide as above.
You can try INTELLIPLUG with STRICT profile since it uses 1 core.
Abhishek Bhagwat said:
One core is enough. Smooth performance on zzmove profile 2.
MSM Hotplug in Halogen R7 plugs 4 cores . Could be a bug. So I use Alucard!
Click to expand...
Click to collapse
This is what happens in my device:
Hotplugs:
- Intelliplug plugs only 2 cores, not more os less than that, so I don't use it
- Alucard only plugs one core, and it makes apps like Facebook to become very slow
- MSM Hotplug plugs 1, 2, 3 or 4 cores depending on my usage, and it seems to be the best hotplug in my case
Governor
- ZZMOVE gives my device a very slow response, seems like I am using a much older device, and apps become slow as well
- INTERACTIVE might use more CPU, but makes the device very smooth, fast and responsive. I understand that it might use more battery
@godoy.rafa
The above GUIDE is to give smoothest performance while using ZZMOVE.
In my device -
- Intelliplug plugs
1 Core - Strict , 2 Cores - Eco Conservative/Eco Performance, 3 Cores - Tri, 4Cores - Balanced.
-MSM Hotplug
Variable plugs, mostly 2,3,4 cores.
-Alucard
1 Core.
Try IMPULSE instead of zzmove or interactive. But I won't guarantee BATTERY SAVINGS on it.
Two questions: how do I disable Google backup and Google Play Services' tracking stuff services?
Also, I plan to install Resurrection Remix. The animations which should be kept as default are the ones you change at developer settings?
One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?
theserpent said:
One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?
Click to expand...
Click to collapse
Take the backup of es file explorer apk to your sd card.After flashing cm based rom you will get cm file manager just install es file explorer through it and remove bloatware:good:
josfr4ncisco said:
Two questions: how do I disable Google backup and Google Play Services' tracking stuff services?
Also, I plan to install Resurrection Remix. The animations which should be kept as default are the ones you change at developer settings?
Click to expand...
Click to collapse
1. Pause all ACTIVITIES in Google Play Services App.
Ex. Web History, Youtube History, etc.
2. Settings/Backup and Restore - Untick Backup.
Note: This will delete all the backups except that of CONTACTS, KEEP, etc.
3. All animations should be default at DURATION SCALE of 0.2x.
theserpent said:
One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?
Click to expand...
Click to collapse
Right answer by @azmat!
Awesome guide bro
Cheers
Thanks for the review!
Did it work for you? @Vatsal
Abhishek Bhagwat said:
Thanks for the review!
Did it work for you? @Vatsal
Click to expand...
Click to collapse
Yes bro it did quiet a lot
Why is this thread closed? It was a
Nice guide...
ishubhamsingh said:
Why is this thread closed? It was a
Nice guide...
Click to expand...
Click to collapse
No feedbacks [emoji28]
Abhishek Bhagwat said:
No feedbacks [emoji28]
Click to expand...
Click to collapse
Dont expect feedbacks on huge basis. But ppl do follow this guide.
Guys share ur feedback on regular basis in order to keep thread alive and people wil have solutions for problems in their battery life
Sent from my Moto G 2014 using XDA Free mobile app
Custom kernel for Samsung Galaxy S Advance
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hi there!
Because of numerous issues found in 3.4.113 kernel, I'm temporarily moving to development on 3.0.101 base.
What is difference between chrono kernel (CK) and CK refresh build? CK was mostly tested on MM-based ROMs, but appeared not to work stably on Android 4.4.x. Aim of this build is to properly enable support for older ROMs (like kitkat), and when done, merge these changes to 3.4.113 kernel.
This build is based upon chrono kernel r4.1 build, so to avoid versions confusion, I'm creating a separate topic.
Features:
CPU, GPU and DDR OC support
more governors and I/O schedulers
Lite kernel - some kernel features moved as modules
F2FS support
ABB-charger tweaks
many others features and tweaks...
Credits:
@dh.harald and @hafidzduddin for contribution on U8500 platform sources
@ Team Canjica for a base for this kernel
@ Nova Fusion for F2FS implementation
@zwliew for contribution on TC kernel
@cocafe for LiveOPP, GPU OC, abbamp and abb-charger tweaks and many cool patches which I've used from his kernel
@faux123 for dynamic Fsync implementation
@Christopher83 for dynamic management of dirty page writebacks implementation
@KINGbabasula for contribution on TC kernel sources
@boype for SIOPlus tweaks and OndemandPlus governor
@Adi_Pat for abbamp, kernel tweaks
@PolishVodka for initramfs scripts for 4.2.x and 5.0.x
@Rox for help in fixing initramfs scripts for 4.1.2
@ace2nutzer for optimization CPU OC and for whatever scripts which I have used in my kernel
@Meticulus for BLN, Sweep2wake and Doubletap2wake
@mkaluza for huge LiveOPP/Mali improvements and Dynamic governor
@yanpol199 for help with F2FS support in TWRP
@ all users who tests this kernel and directs the development along the right path
@ all those users, who I forgot to mention (PM me if so)
Team Win for TWRP recovery
Samsung for opening kernel source
Linus Torvalds for Linux sources
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source Code:
LK 3.0.y based releases
Installation:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Notice: this kernel is not compatible with NovathorSettings app, be sure to remove it before installing a kernel!
Download:
FTP
XDA:DevDB Information
Chrono Kernel Refresh, Kernel for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, cocafe, faux123, zwliew, mkaluza, Meticulus, KINGbabasula, ace2nutzer, TeamCanjica
Source Code: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/refresh-3.0.101
Kernel Special Features:
Version Information
Status: Testing
Stable Release Date: 1974-11-11
Beta Release Date: 1974-11-11
Created 2018-03-22
Last Updated 2018-03-23
Changelogs
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs)
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.
R4.6
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
R4.1
Initial build for janice (kernel sources based on Chrono Kernel r4.1)
LiveOPP: updated to r5.7.1 kernel version
Exfat: test fixes for Stock 4.1.2 ROM (not tested)
Enabled CONFIG_STE_TRACE_MODEM (test fix for Stock ROM incoming / outgoing calls)
Kexec: added janice support
Misc
Storages switch
By default, this kernel comes with internal and external storages switched. You can revert this behavior, by changing the line
Code:
use_swap=1
to
Code:
use_swap=0
in file /ramdisk/fstab_specs.txt and flashing the kernel package. This setting will remain until you format /ramdisk partition.
Thank you Chrono again.
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
The nice thing is I find multitasking working far better, phone seems to be more responsive in situations where more apps are running at the same time, this is very good to me!.
Another big point is installation went fine and recovery is working perfectly, so problems with possible bootloops are solved (and after some more usage I will go further to your more updated roms )
If there is something more to provide you, test or informations missing, please ask me Chrono
I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
-If I set 1000 Mhz as maximum clock of the dynamic governor, the phone becomes slower and a bit hot on the back.
Multitasking is severely affected by that clock. Multitasking is more stable at 800 Mhz, despite it's still slow.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
In my attachment there is a meminfo that I took while the phone was under load.
If it isn't enough, I attached a full logcat. There are some errors and crashes.
@Pdevo, @isaak, thanks for testing!
I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
Click to expand...
Click to collapse
Probably I've rushed things, or sort of. I had a hard time trying to find a considerably stable kernel 3.0.101 base (this one appeared to work stably, though not best, in terms of the performance). Nevertheless, the multitasking should already be better (at least better than in r5.7.1, as in this one LowMemoryKiller appeared not to work at all). I'm updating the sources to a new kernel base, r4.6 which should be even better in multitasking term.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
Click to expand...
Click to collapse
Should be fixed in upcoming release.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
Click to expand...
Click to collapse
It's a bug in CM11 ramdisk, I've took another one from Codina, and now this issue should be resolved as well.
Pdevo said:
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
Click to expand...
Click to collapse
I'm afraid that exfat driver built in the kernel is not compatible with this userspace mount.exfat-fuse utility. I won't be able to fix it, until I find a time to return to stock & rebuild either mount.exfat-fuse or kernel driver in order to make them compatible each with other.
As for the deepsleep issue, I can say that at least 4.4.4 is not affected by this bug. Try making sure that no apps are preventing deep sleep (Better battery stats or Wakelock detector can help in that).
New build r4.6 is up!
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
ChronoMonochrome said:
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
Click to expand...
Click to collapse
Tested on Lineage Os 11 without CCleaner.
After flashing this new kernel I had to force a Media scan with Fx File Explorer (that detected over 300 changed files) because the phone was really slow. That was sufficient to speed up the multitasking that now it's much better than previous 4.1 build.
Additional observations:
- Do you think it's possible to improve Media scanner reactivity via kernel?
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!
isaak said:
- Do you think it's possible to improve Media scanner reactivity via kernel?
Click to expand...
Click to collapse
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
Click to expand...
Click to collapse
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
Click to expand...
Click to collapse
Ok, I'll consider of tuning CPU governor in order to provide more battery friendly setup. I was afraid that the battery usage might be too high, but that was a necessary evil, I guess. In the meantime, as a temporary workaround, the maximum CPU frequency can even be lowered to 800 MHz, it should be still fast enough.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!
Click to expand...
Click to collapse
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
ChronoMonochrome said:
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
Click to expand...
Click to collapse
Nevermind.
ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
Click to expand...
Click to collapse
I'd like to revert the behavior, so I would appreciate If you could provide the same instructions here and in the other kernel thread..
ChronoMonochrome said:
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
I would suggest deadline, noop, sioplus, zen (plus the existent FIOPS).
ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
Personally I really appreciate and find useful the external sdcard storage as primary one, should be the default behaviour for me, it makes sense and also I never liked to have some files on one unit and some files on another one (download, pictures, recordings on extsdcard, apps folders, screens, other apps downloads etc on internal), I really like the idea of sdcard as main, like the old times of galaxy mini
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
I will test this build and especially the deepsleep issues, to see if there are apps causing phone not to sleep, the problem is I didn't add any app, just using the same enviroment that with cocore was going to deepsleep. I will report soon, anyway, good job chrono, keep it up
Pdevo said:
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
Click to expand...
Click to collapse
Yes, FIOPS is good. I just think that having 2 or 3 additional schedulers to select would be better for different uses.
In my previous post I replaced sioplus with zen, according to the conclusions of this guide. There is an useful (up to date) list of recommended IO schedulers, ordered for everyday usage, battery life, heavy multitasking, etc.
New build r4.6.1 is up!
Hey guys and sorry for having to wait that long for a new releases!
I'm still working on 3.4.x kernel - no great news here, but at least I've found a more less stable sources base, so the only what needed now, is a time to bring up some stability fixes and feature changes.
For now releasing a 3.0.101 kernel with some minor changes:
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.
ChronoMonochrome said:
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage
Click to expand...
Click to collapse
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.
For me the minimum freq was correctly 400 mhz as expected, as always running on stock 4.1.2.
After two days of use I can say you are following the right path.
This time I wanted to remove every possible source of doubts and I went for a clean installation, so doing a complete reset and flashing your kernel, of course after the temporary one. I still have the phone not going to deepsleep and the call issues (basically it is impossible to do and receive phone calls on stock rom).
A part from these I can say I didn't noticed any other issue at all, finding memory management a little improved compared to previous release and battery life still good, considering the phone isn't going to sleep mode.
I think this will continue to improve and soon all these glitches will just be gone away, thank you so much chrono also hoping to settle for a bit on your ultimateROM, only waiting for the vibration working, because that is basically the only notification for me
isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.
Click to expand...
Click to collapse
1) Isn't an issue here, the showed CPU frequency is 200 MHz, but the actual CPU pll clock set at 400 MHz. Might be confusing, but yet that is better for a battery life.
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?
ChronoMonochrome said:
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
Click to expand...
Click to collapse
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
Click to expand...
Click to collapse
Honestly I don't know how to disable perf profiles. If it's a simple thing to do (like a command or two to execute), please tell me how to do it because it's enough for me, otherwise I'd like to try the third way and see.
ChronoMonochrome said:
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
Click to expand...
Click to collapse
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
Click to expand...
Click to collapse
Yes, "Set on boot" options are correctly set for both Processor and I/O Scheduler.
And I keep "Enable per-app profiles" option turned off.
@ChronoMonochrome
UPDATE 1: It occurs only randomly and with particular combinations. The best way to reproduce is to set these, one at a time:
1) Zenx as governor, min. 200 max 800, Noops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Fiops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Sioplus scheduler. Reboot.
After the first, the second or the third reboot, some of these values you've set will change spontaneously on their own.
UPDATE 2: I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, it's ok now, but I've noticed that this value is not kept after a reboot.
Do you need a specific log?
In case please write me any command and I'll give you the output.
isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs: .....
Click to expand...
Click to collapse
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
ChronoMonochrome said:
....
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?
Click to expand...
Click to collapse
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:
ace2nutzer said:
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:
Click to expand...
Click to collapse
Sorry for so late response, I had to take a break in a development because suddenly got sick with a flu (I'm fine now, btw) :silly:
I think I've found a temporary solution to this bug, take a look if you're interested:
https://github.com/ChronoMonochrome...mmit/bd0dcce403633543f1bf11e5f8b476a3e88322cb
New build is up!
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs) *
Hey there! I've been testing 6.0.1 / 7.1.2 ROMs and I've recently got some issues with camera on 3.4.x kernel build, so I've decided to release a new refresh build (based on 3.0.101 sources).
I've rebased the most of recent changes to CM14.1 branch in order to support these ROMs (so if you're using older ROMs like stock 4.1.2 then better to use previous release cause some patches might be missing here).
Just downloaded the latest version of franco kernel manager 6.1. Im a total noob in terms of using this tool, so I've been looking for a guide or a tutorial that can assist in using it. Also what is the method of flashing the franco kernel from this tool? Where can I download the franco kernel.zip? I have been looking all over, cant seem to find it. Plz help
Im currently on RR Rom latest version 8.6.3. Im looking for a setting to enhance battery life and overall performance of the Phone.
rigerp said:
Just downloaded the latest version of franco kernel manager 6.1. Im a total noob in terms of using this tool, so I've been looking for a guide or a tutorial that can assist in using it. Also what is the method of flashing the franco kernel from this tool? Where can I download the franco kernel.zip? I have been looking all over, cant seem to find it. Plz help
Im currently on RR Rom latest version 8.6.3. Im looking for a setting to enhance battery life and overall performance of the Phone.
Click to expand...
Click to collapse
Hey there
What I did to get Franco kernel was flash it during my first time rooting (so it was a clean flash, as the phone had be factory reset). Once you're in TWRP, you flash Franco kernel and then magisk. This is one way to do it. I can't advise you to flash a new kernel without clean flash because I personally didn't do it and I don't know if issues will come from that. If you can do it, my personal advice is to just do a clean flash. You know the drill, wipe system data and that stuff > flash ROM > Kernel > Magisk, and done
As for where you can get the zip, there is a thread here in the OP5 XDA forum on ROMs and Kernels I think and that's where franco posted the kernels. He's got a website too linked in the same post
HOWEVER, he hasn't updated them since last year, and I don't think they have support for Android 10, only 9
As for settings, well, in my own experience, you won't get any noticeable boost in battery life or performance without doing some drastic change.
If you want better battery life, you can decrease the maximum CPU frequency, change the governor to Conservative or Powersave, disable some cores, or all of those at once, but they WILL degrade performance, sometimes you won't notice but then you'll try to load a heavy webpage on Chrome and then you'll REALLY notice it.
The inverse is also true. To increase performance you change the governor to performance; usually the CPU frequency is set to its maximum by default, and the cores are all enabled anyway so you don't have to change anything. BUT, keeping the governor in Performance will also keep the CPU clocks at its maximum, and that's going to drain your battery like CRAZY, plus it'll overheat it. Usually there is no practical need for this setting, but I use it to play games on Dolphin emulator since thats when I can actually make use of that performance.
A better alternative is to keep the governor on Interactive, which will scale up CPU clocks depending on the load (if doing light stuff, low clocks. Heavy stuff > high clocks). Otherwise, Conservative does the same thing but takes longer to use higher clocks, so battery is saved.
Always use 1 governor for all cores. Do NOT use multiple governors (example: powersave for big cores, performance for little cores) because that will cause instability issues
Also, if you make any changes, you gotta tap the toggle on it, which will say something like "stay on boot: true". Otherwise, if you for instance change your governor to Performance, and then reboot, all your changes will reset to Default
Personally I just keep my governor in Conservative and roll with the defaults.
Hope that helps ya
sorry for digging but I was loooking for solution..
just make a backup of present kernel (tuned with FKM) and then flash it from backup menu
I was trying flash with twrp, magisk, 'set on boot' at first and many other things but it was so simple, it's there all the time