Database Users

(CM7/MIUI) Screenstate, Governor and Threshold Control Script

Hi Folks,
For those who are interested, I have modified the 90screenstate_scaling script used in Zach's (and now Glitch's) kernel for use with other CM7 compatible kernels. The aim is to create a very simple script that can easily be read, modified and improved upon by non-coders, such as myself.
I have retained only the code that will read the screen state, set the governor appropriately and set the scaling threshold, giving users complete control over the scheduling behavior of their CM compatible kernel.
I am not a coder and all credit goes to FloHimself and zacharius.maladroit for the original content. all I have done is (hopefully) simplify the script and make it easy for non-specialists to read.
If you would like to try it out, copy the script in to /system/etc/init.d and modify the values to your liking. If you are already on Zach's kernel there is nothing new here, as you already have this script.
The script currently includes kernel defaults from Glitch for the smartass governor, from Zach for the conservative and ondemand governors, a few experimental settings, and of course, the ability to modify them yourself.
If you add anything or make any modifications (particularly in relation to your specific usage pattern) you would like to share, please post them and I will update this thread. If you make modifications, comment them appropriately and explain your usage pattern for which the settings work best so that people know if it would work for them.
The experimental conservative settings that I have made (that are currently in use on Glitch kernel) for the screen off state are designed to aggressively keep the frequency very low, almost like a 100mhz frequency cap, while still allowing them to scale up under considerable load. They are (hopefully) ideal for background screen off behaviour such as listening to music, exercise applications or aggressive sync and push/pull email behavior (like in an office).
The experimental smartass settings are designed to test the hypothesis that quick downscaling may cause as many lags as as slow scaling up behavior. The goal is to create a more linearly scaling version of smartass which is slower to upscale or downscale (only a matter of milliseconds difference). These are still under testing.
With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings, which may have battery implication while the screen is on, but they are VERY smooth.

*subscribes*
we could probably make conservative governor more aggressive
with the settings that laststufo used on his kernel but I'm not sure if it would scaled up fast enough if you used e.g. some DSP settings on sound while the screen is off
worth as shot
if I don't forget it - I'll post the settings later

Subscribes too
I like the idea and the simplicity of this. And with Zach's help, also known as "F*ckin scripts master" (almost a private joke ), it can only be great.

I'm a big fan of simple, though as a user of Arch Linux on the desktop I have no choice (BSD style init scripts a boot - beautiful simplicity)!
It's great you lads are watching this! Hopefully the thread will grow in to something, even if it is just an sandbox for users to experiment with the settings they prefer. If nothing else, hopefully you guys get some useful info!

I just added a bit of an experimental version that moves away from the default smartass values.
I am hypothesizing that the very accasional lags in the smartass governor might be related to the governor scaling down too fast, rather than it not scaling up fast enough.
I changed the default down threshold from 40 to 35 and the default up threshold from 60 to 65. Hopefully this will scale up and down a little more linearly and this will make the GUI even smoother. I am still testing this theory at the moment, but thought I might post it (on the first post) if anyone wanted to have a go.

well.heeled.man,
you need to test your conservative settings while the screen is on
they're way too aggressive (at least the up threshold, down threshold may be ok)
also the freq_step at 10% should be at least at 15%
if we compare it with laststufo's kernel (he almost had 100 MHz steps everywhere: 100, 200, 400, 600, 800, 900, 1000 MHz)
so that needs to be compensated to get smoother & similar behavior
I'll take a look & see how the new smartass settings work out
my new conservative settings are:
echo "76" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold # 50 # 76 # 76
echo "30" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold # 35 # 12 # 30 (higher will lead to noticable lags) # 35
echo "15" > /sys/devices/system/cpu/cpufreq/conservative/freq_step # more aggressive ramping up (50)
this currently keeps the cpu between 100-200 MHz while playing MP3s for me (screen off) - mostly 200 afaik right now
but I'll try your conservative settings, too, when I find time - let's see how they are in terms of "smoothness" (I'm sure they're not too usable with the GUI but could be great for background tasks while the screen is off)

Hi Zach, indeed, I would say that the conservative settings are completely unusable with the screen on. I would not recommend these with the screen on.
However, with music (DSP manager too) GPS and Cardio Trainer all running (my cycle home), it seems to work fine (screen off). Every km, Cardio trainer speaks the time taken over the music (two audio streams). With many kernels this becomes slow, or slurred, but sounds perfect with these settings.

well.heeled.man said:
Hi Zach, indeed, I would say that the conservative settings are completely unusable with the screen on. I would not recommend these with the screen on.
However, with music (DSP manager too) GPS and Cardio Trainer all running (my cycle home), it seems to work fine (screen off). Every km, Cardio trainer speaks the time taken over the music (two audio streams). With many kernels this becomes slow, or slurred, but sounds perfect with these settings.
Click to expand...
Click to collapse
awesome !
so it still raises the frequency when needed ?
100 -> 200 (or more)
you checked via e.g. CPU Spy ?
thanks !

Yes, it still goes up when needed (confirmed via CPU Spy), but it needs to be really pushed. It seems like good behaviour in the screen off state.
EDIT: something in the region of a 66%/33% 100/200mhz split at these settings.

I am struggling to confirm that my settings are being applied as I would like in the screen off state. I can read off the values in /sys/devices/system/cpu(/cpu0)/cpufreq/conservative if I manually set conservative in Pimp My CPU with the screen on, but the behaviour seems at odds with the values i.e. not as laggy as one would suspect.

As (a variation of) this script are now used in Glitch's too, I have changed the comments to allow people to very easily see which settings are from kernel devs (which should probably be left alone should you wish to return to their defaults) and experimental settings (which I would suggest you change, if you change any). If you want to use parts of it in Zach's, I would suggest cutting and pasting the experimental part into the appropriate part of Zach's script as overwriting any part of it would remove much of his additional functionality.

This is great guys - thanks for this

With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state, no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings by default. This may have battery implication while the screen is on, but they are VERY smooth.

wrong spot

screenstate_scaling_V49.zip
that's the current version of my screenstate_scaling script that I offer as an option with Neo 17 r7
most of the stuff moved into the S98system_tweak script that now is shipped with the kernel

[KERNEL]05.12.2011 test-kernels [CM7/MIUI] platypus;SECURITY,VOODOO,OC/UV,nodebug,...

I'M A SUPPORTER OF BRINGING OFFICIAL ICS TO THE VIBRANT AND OTHER GALAXY S DEVICES!
> CLICK HERE FOR MORE INFORMATION <​
Click to expand...
Click to collapse
CAPTIVATE edition of the Platypus Revolutions kernel
This Project is inactive/low activity for a longer period of time
Kernel
CM7 & MIUI only
NEO series
(since May 24th '11)
Do you want to discuss on this kernel, get the news on the current state of development, or test kernels even fresher than fresh ?
connect via webchat from your browser:
http://webchat.quakenet.org/
and join #platypus-kernel
(recommended)
Fire up your IRC client, and join via client
the server (for now is) : irc.quakenet.org
port : 6667
Channel : #platypus-kernel​
(thanks to Tk for the layout idea )
before you ask for any ETAs:
The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!
---------------------------------------------------------------------------------------
First step before install & kernel switch:
Always have this cleaning script on your internal SD card ready
If you're
- switching kernels,
- have issues with auto-rotation,
- the cam,
- bootloops
- want to remove init script
- recover from a failed overclock attempt
please give either:
- lippol94's updated cleaning script (apply via CWM recovery): http://www.multiupload.com/XFH1GCK4MB
or
- WiwiPouPou's SYSTEM CLEANER SCRIPT (also apply via CWM recovery): (http://forum.xda-developers.com/showpost.php?p=14805606&postcount=21739)
a try
the kernel already applies some cleaning steps during install but sometimes that's not enough ...
---------------------------------------------------------------------------------------
Introduction:
Hi guys,
this is my first modded kernel for the SGS (CM7/MIUI only)
I first needed to test it to make sure that it'll be stable & boot at the first place
so far it's very fast & responsive & smooth
This thread shall serve as the center for my testing kernels (stability & functionality-wise)
DISCLAIMER: the kernel (binary) and driver modules are provided as is. If problems occcur they most probably are from upstream and can be fixed with the newest version. Since I'm doing this in my free spare time as a hobby (quenching my thirst for tweaks & performance) updates will occur irregularly as time permits and I see fit (most probably when new features & bugfixes arrive). YOU are responsible for the actions that you take (such as over- or underclocking), etc. You agree that I can not be held liable for any potential damage that arises from your actions in combination with or the usage of this kernel and other related parts.
Kudos:
* Google, Andy Rubin & the whole Android crew
* Linus Torvalds & the kernel hackers for upstream Linux
* cyanogen & all the devs out there hacking on this
* Supercurio for enriching our media experience of this smartphone
* codeworkx, coolya, guiper, atinm - the whole teamhacksung|cmsgsteam crew and all other hackers working on CM7
* laststufo, hardcore, nikademus, existz and all the other kernel hackers on the SGS forum
* zen-kernel team for inspiration to create a kernel, too
* all other contributors (devs, users, etc.) who make this possible
The purpose of these kernels is extensive stability testing addressing the following sticking points:
- overall stability & functioning of the kernel and phone
- call drops, missed calls, etc.
- lags (suggestions for improvements are welcome)
- auto-rotation, sensors, etc.
- Voodoo Control Plus [any crashes ? compatibility problems ?]
- working on CM7 or MIUI ?
- scheduler, sound, video synchronisation & lags: Tap Tap Revenge 4 (especially at the beginning of songs)
- scheduler, sound, video synchronisation and any other issues: doodle dash (while shooting & sound activated)
- proper pmem memory layout & settings: proper functioning of Google Googles
for those who love SAUCE (Source):
old source:
ALL MY SAUCE for QUORRA KernalZ ^^
new source:
android_kernel_samsung_aries
(fork and 1:1 update to upstream kernel source - changes in different branches)
(latest changes sometimes might not be in [yet] but in the whole repo everything should be available)
current UV & OC stable values:
Recommended apps for OC/UV:
- Pimp my CPU (also available here on XDA for those who don't have a credit card, etc.)
- Xan's VoltageControl
on stability testing:
http://forum.xda-developers.com/showpost.php?p=13255871&postcount=5
(start with "Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?")
the following OC/UV values are only applicable for kernels with the old OC/UV implementation (max. 1.3 GHz)
my current UV (undervolt) stable Values :
old OC/UV implementation (morfic, bilboa1/kang, TheEscapist):
1300000 0 (haven't tested 1.3 GHz much yet)
1200000 -25
1000000 -50
800000 -75
600000 -100
400000 -100
200000 -125
100000 -150
edit:
1200000 -50
1000000 -75
800000 -75
600000 -225
400000 -125
200000 -150
100000 -175
thanks jetcz !
new OC/UV implementation (morfic, bilboa1/kang, TheEscapist - Tk-Glitch):
Tk-Glitch said:
Note that these UV settings will be unstable on many devices. It's only informative.
1600 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1440 MHz - 1.475v / -75mv
1400 MHz - 1.450v / -75mv
1300 MHz - 1.400v / -75mv
1200 MHz - 1.350v / -75mv
1000 MHz - 1.250v / -50mv - If you have stability issues, try to let this one by default.
800 MHz - 1.200v / -75mv
400 MHz - 1.050v / -100mv
200 MHz - 0.950v / -150mv
100 MHz - 0.950v / -200mv - (can be very different between two devices)
More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.
Considering all phones will respond differently to OC/UV, to tweak the values to suit your device will be required.
By default, no overclock/undervolt is applied. You'll need to use one of the tools below to adjust the frequencies and voltages.
Note : Never ever use SetCPU with this kernel. You could encounter many stability problems like random reboots or bootloops.
Click to expand...
Click to collapse
3D performance and games:
recommended apps:
[root] Chainfire3D

1st backup post (kernels)
Kernels:
kernels are listed in descending order
older -> newer (newest at the bottom - for now)
officially declared new stable kernels will be up soon !
for now please go to the IRC channel (1st post to get the newest test-builds)
NEO 17 -r12 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=17339783&postcount=21
NEO 17 -r18 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=18268518&postcount=132
NEO 18-update1 codename: funky fish
NEO XX.1-update1 codename: mighty rhino
http://forum.xda-developers.com/showpost.php?p=19999998&postcount=192
ALL USERS MUST UPDATE (this fixes yet another potential data loss trigger)

2nd backup post (Changelogs)
Changelog list:
obsolete right now

3rd backup post (modems list)
modems:
Description:
Modems play a crucial role in how much battery drains in standy.
e.g. if you have a good signal area and the modem still has high
"Time without a signal" indicator under Cell standby you still will get bad standby time
make sure you have little to no "Time without a signal" in Cell standby
there also somewhat seems to be a connection between "Time without a signal" and high "Android OS" number in battery use (!)
Following modems are only compatible with new radio (modem) partition layout:
radio-cm-7-GalaxyS-JVP-signed.zip (4.29 MB)
md5sum: fb38dbf82daf0720fd2328f5f649013e radio-cm-7-GalaxyS-JVP-signed.zip
For more modems & bootloaders please go to siky_dude's Modem Thread:
[CM7/MIUI][28.08.11] Modems + Bootloaders(MD5)
[SGS / i9000 Thread so some frequencies might be missing, e.g. 850 MHz]
for more modems please refer to a modem thread in the Captivate Forums section

4th backup post (results)
Results & FAQ/Documentation
Results:
(04/27/2011) Results for platypus-kernel_20110427_18_quorra_r1:
- broken auto-rotation & sensors for some [insert ROM (CM7 ? MIUI ?)]
- stable
(05/03/2011) Results for CM7_SGS_platypus-kernel_20110503_17_quorra-r4_exp
- high battery drain, either due to kernel config or optimization flags, fixed with >= quorra r5 (2nd update)
FAQ / Documentation
@bootloop / boot post victims ^^
Hi guys,
could you please try to replace the existing kernel on your MIUI or CM7 nightly CWM-Package with my kernel, modules and its scripts ?
then install that updated package (with the new kernel, modules and scripts)
after that all should work
the bootloops seem to be an issue with bml_over_mtd (broken sectors on the SSD on your phone)
I'll investigate this and see if anything needs to be rewritten and/or updated in that regard
Thanks !
Overclocking / Undervolting:
Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?
A: start with -50 mV (delta from default value) other values probably are too low
my testing includes:
- Angry Birds Rio (several missions)
- Gun Bros (for some time)
- mp3 playback, (flac playback - optional)
- surfing the web via browser, opening up bit.ly links from cmsgsteam twitter feed
- watching youtube video
- watching video via rockplayer lite or mobo video player
- running benchmarks (Smartbench 2011, quadrant standard, an3dbenchXL, anTutuBench)
- Labyrinth Lite (for gravity sensor), auto-rotation (also for sensor)
when 1 GHz (1,2 or 1,3) is OK - go lower with undervolt value (e.g. -75 mV)
after it gets un-stable - go back to last known stable value
then you can limit max frequency to lower one, e.g. 800 MHz
and repeat testing for that frequency
for more info: checkout shaolin95's Mini Overclocking Guide:
Link: http://forum.xda-developers.com/showthread.php?p=12910471#post12910471
LED Support FAQ
Q: Do LED notification require an app, such as BLN, etc ?
A: No. It uses Android's and Cyanogen settings, other apps are not required, although some that are designed for regular LEDs may work.
Q: How to I turn off LED notifications, scheduled or/and complete turn off?
A: Use Cyanogen's Quiet Hours feature (settings>cyanogen>sound>quiet hours) and check "Dim the LEDs during quiet hours" (in reality it will turn them off on the SGS). If you schedule a complete day, then LED notifications will be off all the time.
Q: How do I setup per app, find other LED settings etc?
A: Settings>cyanogen>interface>LED notifications
Q: What to do with LED color settings?
A: We have only one color, so that doesn't work. Use Green as default setting. Some non-bright colors turn off notification, as it's the equivalent as diming LEDs (note that on real LEDs if you dim them too much they look like off too anyway, the difference is that it's gradual. On the SGS the LEDs can be only on or off, not gradual)
Q: How can I troubleshot my system, I can use ADB but...
A: adb logcat | grep lights (on linux) will show you Android requests to turn LED on or off. "status" tells you what we decide will be interpreted as "turn LED on" (1= on, 0 = off)
adb shell cat /proc/kmsg for live view (or adb shell dmesg if you're using adb after the issues occurs - careful the backlog is limited in size so don't be too slow)
notify_led_on and notify_led_off are requests to the kernel to turn LED on or off.
touch key write/read errors (cypress) are non-fatal failures to ask the touch key to do something (eg lit up the LED), when the hardware goes crazy or there's a logical error in the code (can be both)
touch key recovery routine or "stopped responding" are either hardware errors, either a logical error where the driver would try to write something the touchkey doesnt understand. in some occasion lock&unlock fix those as a work around, of course a permanent fix is required
Voodoo Color settings:
Q: I don't have that nice ice-ish white color on my screen anymore - you suck !
Q: my screen looks like someone pissed on the screen - you suck !
(sorry for the language ^^)
A: I love you too ^^
download Voodoo Control or Voodoo Control Plus
Screen RGB multipliers:
- Red: 321*
- Green: 321*
- Blue: 429*
Screen v1 gamma hack:
- use Alt. settings
- or if you prefer others - use: "Reset to 2.3.3 defaults", "Punchy settings" (punchy could lead to a great screen while locking the screen and having "screen off" animation disabled)
other recommended settings:
Also a lil tip for people who use voodoo color!
1 )Color Profiles: Voodoo Profile V1
2 ) Screen v1 gamma hack :
- 50 red
- 53 green
- 44 blue
3 ) SRB multipliers:
Red ="2300875360"
Green ="2300875360"
Blue ="2709919680"
With those adjustment, black colors are BLACK and white colors are WHITE. Everyone should try this.
Click to expand...
Click to collapse
SGS CM7 nightlies wiki
http://sgscm7nightlies.pbworks.com/w/page/41483487/FrontPage
Android OS bug, :
(thanks to ceriko ! and his awesome guide for DarkyROM 10.1)
If your battery drains very fast and your battery stats mentions Android OS above 10%, often between 40 and 60%, sometimes more, this is the best to do as far as I know:
- Remove the 2/3 system files as per the beginning part of this guideguide about batterie issues.
- Install WatchDog and open (I set it to "moderate", then I close it, that's all), this app will warn you whenever an app or a process miss-behaves by draining the battery excessively. It will not fix it but just flag it and you will see a notification.
- Reboot usually stops the drain for a while until it naturally comes back, so reboot whenever you see Android OS above 10% and rising or after you see WatchDog mentioning "Suspend" process using too much battery (the suspend process hanging is the Android OS bug).
- Some apps trigger it, most common are Gameloft games (blame Samsung, not the games/apps). No need to use apps or games for this drain to happen, it also happens straight after boot once phone has been fully charged.
This bug can not be fixed by anyone but Samsung. Some never see it, some will experience it everyday no matters what they do... It's just annoying and unfair but that's the same on all Gingerbread releases by Samsung (JVK, JVB, JVO, JVH). Apparently even the SGS2 has this...
screenstate scaling aka my governor won't change after screen locked:
So what is this all about ?
it's an init script that is put in to /system/etc/init.d
and switches between the configured governors in the script
depending on whether the screen is on (AWAKE_GOVERNOR) or off (SLEEP_GOVERNOR)
in most cases your phone is off - in that case it would be good to use a governor which doesn't fire up the cpu frequency too fast since you don't need it (no GUI, smooth scrolling, etc. needed while the screen is off - lol),
so conservative governor is set
when using the phone (screen on) it really depends on what you want to do: e.g. latency & smoothness is crucial: try smartass2, smartass, ondemand;
you're mainly browsing & reading stuff: try ondemandb, conservative (the screen is already burning enough battery so you don't need another component burning yet more)
only use one governor at a time
e.g.
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
that means lines with "#" are commented out and not used by the script
e.g.
# AWAKE_GOVERNOR
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
also would work (intentionally not filled in any governors)

@all:
Neo 17 r10 is available on IRC !
Changelog said:
NEO 17 (r10 - codename Butterfly) changelog [SGS/Telus, Captivate, Vibrant]
Changes (from r9 - 2nd testbuild):
• bumped RAM up to 348 MB (everything should still work, incl. Youtube HD recording)
• ported over smartass2 governor (super-smooth & battery-efficient, hopefully no issues anymore with getting stuck on high frequencies - unless due to system & broken apps)
• back to cm7 vanilla/stock yaffs2 driver - let's see if this fixes the discouraged random resets for few people (loss of contacts, apps gone, etc.)
Click to expand...
Click to collapse

Wow! New thread finally!
I'm testing with the Neo 17 R10 Kernel now.
Thanks!

Woohoo!
Sent from the frozen tundra known as Canada.

Spectacular. Gave it a shot from r7 and loving it since. Looking forward to future updates.
And about time for your own thread!
Sent from my I897 using Tapatalk

Thanks for the awesome kernels, they always work great, and I always look forward to the progression of this kernel. Thanks again for all your hard work, you are very talented.
Sent from my I897 using XDA App

I'm loving it as well, I don't oc much, maybe uv a little, and I do like the vc. Great work.
Sent from the frozen tundra known as Canada.

Thanks zach, r11 + smartassV2 is really super-smooth! You are doing an amazing job.
No problems so far, I got my last SOD on r9.

So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App

buresh.kevin said:
So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.

the new platypus 17r11 is superfast, my CAPPY felt great with it
thanks Zach
hope the color issue soon to be fix since i like to customize the color temp

Fate-Silver said:
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.
Click to expand...
Click to collapse
Did you have this problem as well?? ha! I found the V51 Script, I think!
I tried to change awake governor but it's not showing in Pimp my Cpu. I rebooted, tried deleting & installing it again but no luck.
I edited the script with text editor from Root Explorer, put # infront of ondemandb, and took # from smartass2. Rebooted but pimp my cpu is showing ondemandb.

hi. can you flash this using the orange cwm that comes with cm7?

yuhenyo said:
hi. can you flash this using the orange cwm that comes with cm7?
Click to expand...
Click to collapse
Yes you can.
Sent from my I897 using Tapatalk

simple man said:
Yes you can.
Sent from my I897 using Tapatalk
Click to expand...
Click to collapse
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?

yuhenyo said:
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?
Click to expand...
Click to collapse
http://webchat.quakenet.org/
The instructions are in the O.P., but you'll need to login, download the file, extract the unpack_me.zip pick the kernel of your choice, download the kernel cleaning script 1st page this thread,flash it, then your kernel, then the screen state script.
Sent from my I897 using Tapatalk

[DISCUSSION THREAD] Fluxi XX Kernel ICS, Non-development/settings/battery life etc

OK as Fluxi XX kernel is becoming more and more popular it seems a perfect time to split the chit chat going on in the Development thread.
Please use this thread for all your non-development chat and sharing settings, battery life screenshots etc. If you're unsure about where to post your questions then please post them here and you'll get lots of other users who are willing to help you.
The original German forum for myfluxi can be found here: http://www.android-hilfe.de/kernel-fuer-samsung-galaxy-s2/236546-aosp-aokp-kernel-04-05-12-fluxi-xx-kernel-ics-xxtweaker-app-xxtouch-recovery.html
The new development thread is here: [AOSP/AOKP-KERNEL] Fluxi XX Kernel ICS [wakelock and drain-free slide2wake for SGS2]
Downloads for latest version:
Kernel CWM download: fluxi-kernel-sgs2-XX.03_s2w_b3.zip
xxTweaker apk download: fluxi-xxTweaker-0.4.0_beta1.apk
Slide to wake is currently beta and enabled by default but to disable it do the following in ADB, terminal emulator or a script (if you can get it working):
echo "0" > /sys/devices/virtual/sec/sec_touchscreen/tsp_slide2wake
If you're going to post bugs please do not just post "My phone is slow", "xxTweaker is not working". Remember if you have issues you need to help myfluxi/others help you so post logs to help diagnose your issue. Here's how to get the logs using xxTweaker:
1) Open xxTweaker
2) Scroll down to xxTweaker option (last in list)
3) Scroll down to "DEBUG AND REPAIR" section
4) Select "Debug system logfiles"
5) This will place a file in /sdcard/xxTweaker/logs
6) Attach this file to your post detailing exactly what's happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to post as much detail as you can along with your attached logs describing the issue you have and if possible how to reproduce it something along the lines of:
Issue experienced: e.g. SOD, freeze, lockscreen unresponsive, slow mo bug etc
What were you doing: Brief explanation of what you were doing when it happened (not applicable to SOD)
Your setup: Are you running stock settings, overclock/underclock/undervolting, governor/scheduler etc
Can it be reproduced: Is it consistent or was it a one-off and if it can how?
If you're new to the kernel then this is the best place to ask any of your Fluxi related questions.
If you have any ideas about how to improve this thread then please post your ideas or if you have any useful how-to's etc related to using the kernel/xxTweaker app then also post these and I can quote your posts in the 2nd post.
Thanks for helping keep the development thread on topic.

This is quoted from the other thread to help readers: (Thanks to xator91 for writing it)
xator91 said:
FAQ
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep.
Q: I have setted below maximum Suspend 500 MHz, 800 MHz is also used as the step. Why is this so?
A: "The device" wakes ALWAYS at 800MHz and goes to sleep as well, regardless of which settings are made. The hardware selected 800Mhz to ensure stable operation - change by software impossible.
Q: I need the "intermediate steps", ex. 300 or 700MHz, the CPU frequency table is not. Can I change this?
A: In theory: Nope! In practice: The option of individual frequency steps is a nice gimmick but virtually unnecessary as intelligent as governor select ondemand, conservative, or the interactive dynamic frequency target. The driver provides the steps of the governor decides. Future versions of the SoC Exynos therefore also use 100MHz steps.
Q: The xxTweaker remembers any settings, what is going on?
A: If only some Tweaker settings are not applied, I made a mistake (because I forgot to add them). If no settings are applied, there is something wrong with the permissions. Either missing from the root and the tweaker or directory /data/data/net.fluxi.xxTweaker/shared_prefs chmod'ed is wrong. The latter does the installer script at startup, if you like, it can also manually delete them.
Q: When is the superuser request every action, you can turn that off?
A: Simply update the su binary file: app drawer/superuser/Preferences/ "Press to check for updates" / Important "update anyway" / "Allow"
Q: I can not download, I just get a file "download.php".
A: The Android browser does not understand the PHP script on the server. Either 1 Rename the file and provided with the correct extension, eg "download.zip" or try another browser (Opera, Chrome) or use the PC.
Q: When the device wakes up from sleep or change the lighting conditions, the display is usually too bright / dark. It then takes a few long seconds to realize it, how bright it really is and then it adjusts the brightness. Is there a fix?
A: Yes and no. First, this is completely independent of the kernel. Basically, this is a source CM9/Open Source/Samsung-****ing-and-hold-consorts-important-things-to-lock problem. The HAL is the light sensor from Samsung is not documented and can not read CM reasonable values​​. Use the open-source sensor HAL (xxTweaker | System | Exynos sensor HAL) and the CM settings for automatic brightness (CM | System Settings | Display | Automatic Brightness | Step Customize | Editing levels). However, there is the possibility that thereafter the compass haywire.
Q: Help, BLN works in applications X and Y but not Z!
A: The poor kernel is innocent. BLN is as follows: The Android app generates a notification event, it triggers the liblight module, which writes to the sysfs kernel, liblight kernel module and have to rely on the information from the user space, so the ROM. In other words, from the perspective of the kernel, either always or not working.
Click to expand...
Click to collapse

Moved from the other thread:
Screenshots:
Settings:
System
I/O - Noop
CPUIdle Mode - AFTR or LPA
SCHED_MC - Disabled
Display
Brightness -5
Movement Hysteresis 2
Touch Preset - Gingerbread
CPU
100-900Mhz
CPU Voltages
900 - 1025
800 - 1000
700 - 1000
600 - 950
500 - 950
400 - 925
300 - 900
200 - 875
100 - 850
Max Suspend 500Mhz
Min Suspend 200Mhz
Governor
Conservative
Governor Settings:
Ram3n Tweaks from here:http://forum.xda-developers.com/showthread.php?t=1691129
Hotplug
Up - 90
Down 30
Dynamic Hotplug
Bus Frequency
30 Up
23 Down
Voltage Table: 1050,950,950
GPU
67Mhz - 825
100Mhz - 875
200Mhz - 950
BLN & LED
Both Off
Modem
LPX
Apps Used:
Opera
Texts messages
Wi-Fi
Boid
Friendcaster
Market
Other Apps too...

Much better this way

superleeds27 said:
Moved from the other thread:
Screenshots:
Settings:
System
I/O - Noop
CPUIdle Mode - AFTR or LPA
SCHED_MC - Disabled
Display
Brightness -5
Movement Hysteresis 2
Touch Preset - Gingerbread
CPU
100-900Mhz
CPU Voltages
900 - 1025
800 - 1000
700 - 1000
600 - 950
500 - 950
400 - 925
300 - 900
200 - 875
100 - 850
Governor
Conservative
Governor Settings:
Ram3n Tweaks from here:http://forum.xda-developers.com/showthread.php?t=1691129
Hotplug
Up - 90
Down 30
Dynamic Hotplug
Bus Frequency
30 Up
23 Down
Voltage Table: 1050,950,950
GPU
67Mhz - 825
100Mhz - 875
200Mhz - 950
BLN & LED - Both Off
Modem: LPX
Apps Used:
Opera
Texts messages
Wi-Fi
Boid
Friendcaster
Market
Other Apps too...
Click to expand...
Click to collapse
Which rrom are you using? Also which kernel version? Also is that with stock battery or extended?
Sent from my GT-I9100 using Tapatalk 2

awaisuk said:
Which rrom are you using? Also which kernel version? Also is that with stock battery or extended?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
See my Sig. Extended Battery too

superleeds27 said:
See my Sig. Extended Battery too
Click to expand...
Click to collapse
Really off topic: what's your theme? Heheheeh.

marcellocord said:
Really off topic: what's your theme? Heheheeh.
Click to expand...
Click to collapse
Flow Theme for AOKP/CM9. Available on the Play Store

Guys, not sure if this is the right thread but.. I've got a 46-minute wakelock with the latest kernel.. Anyone know what to do to get rid of this?
Attached logs..

My phone doesen't sleep very well..
The screen is off during the night but the phone is active and i lost about 10% battery..why?
Sent from my GT-I9100 using Tapatalk 2

Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
---------- Post added at 02:52 PM ---------- Previous post was at 02:21 PM ----------
francesco.cordella said:
My phone doesen't sleep very well..
The screen is off during the night but the phone is active and i lost about 10% battery..why?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Post your BBS.. Then we may have some clue of whats going on..

Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2

francesco.cordella said:
Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Keep in mind that wifi also consumes some battery I wouldn't let my phone on while i'm sleeping. At least I would kill the open apps and turn off wifi.

Sent from my GT-I9100 using Tapatalk 2

LogeshMenon said:
Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
---------- Post added at 02:52 PM ---------- Previous post was at 02:21 PM ----------
Post your BBS.. Then we may have some clue of whats going on..
Click to expand...
Click to collapse
Well SlimICS is CM9 with cherry picked bits of AOKP. Saying that though. I still got better battery life with the proper CM9

LogeshMenon said:
Currently running SlimICS + Fluxi .2 beta9, will i get a better battery life and performance using CM9 + Fluxi .2 beta9??
Any input??
Superleeds, what do ya reckon??
Click to expand...
Click to collapse
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too. I personally leave everything stock clock and voltage wise and just use my phone as I see fit. Remember the less you monitor and worry about the battery the better it will be Battery life should never choose your ROM, whether or not it's useful to you and what you like should
francesco.cordella said:
Must be an entire cycle wakelock?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It's never best practice to judge battery life on the first cycle, just use it, drain it, charge it, then after a few days try monitoring your battery to see what it's doing, but if it's lasting you a day then shouldn't be a problem, or have I just not got as high expectations as everyone else?

superleeds27 said:
Well SlimICS is CM9 with cherry picked bits of AOKP. Saying that though. I still got better battery life with the proper CM9
Click to expand...
Click to collapse
Slight correction it's not CM9 it's AOSP from Google sources with cherry picks from CM9 and AOKP

AvRS said:
Slight correction it's not CM9 it's AOSP from Google sources with cherry picks from CM9 and AOKP
Click to expand...
Click to collapse
There's only two types of ROMs: Samsung Stock and CM9. Every other ROM is a modified ROM from those two. Well, there's b2g also, but no one uses it.

AvRS said:
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too. I personally leave everything stock clock and voltage wise and just use my phone as I see fit. Remember the less you monitor and worry about the battery the better it will be Battery life should never choose your ROM, whether or not it's useful to you and what you like should
Click to expand...
Click to collapse
I find it strange that the battery life I get on CM9, i have never achieved on any other ROM.
SlimICS
Several AOKP Rom's
When I've used the Roms I've always used Fluxi and the same kernel settings, plus, given it chance to settle too.
CM9 for some reason seems to consume less battery when the screen is on!

AvRS said:
Personally I think ROM choice has less to do with it and the apps you've got and accounts sync'd etc are where you will save battery. If you freeze/remove anything you don't use then you'll do better and obviously using UC/UV etc will help a tiny bit too......
Click to expand...
Click to collapse
Bro, I've freezed about a total of 18 system apps from slim, extreme UV, UC 100 ~ 800, tweaked governor settings, gpu max step is 160, gpu UV more extreme than superleeds, only absolutely necessary apps, only inverted apps, and full black settings, no fancy color themes, autostart disabled of some services, sync only required apps and tons of other cherry picked tweaks, and i never get past 13 hours, and with screen of 2 hours. Anymore tweaks, and i rather sell off my S2 and get a nokia 3310..
The only thing i may be off the battery saving method is i'm using floating image live wallpaper, as i like to see my wife and daughters photo on my screen.. And even made sure that floating image does not misbehave, process usage and wakelock by FI, is very minimal.
My aim, is to have a minimal of 20 hours with screen usage of 4 hours.:fingers-crossed::fingers-crossed:
This is due to me sometimes being on the road and especially when i'm out on the boat fishing (hobby) for a few days...
I have no qualms when i'm in office or at home, i'm in front of my laptop almost 90% of my wake time.

[GUIDE][ROOTED][FRIENDLY] Battery Guide - CM Based/Stock Based ROMs.

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

[Kernel][3.0.101] Chrono Kernel Refresh R4.6.2

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).