Database Users

[Guide] Minicm7 Guide | Bug Fixed | Review | Extra

This is all guide with bug fixing on minicm7 2.1.X​
Screen Cut:
Only in CWM/CWR
NMEAListener:
I think NMEAListener is GPS
I found that gps.conf is europe settings
since that i have no problem with it
for non-europe residence Here Patch
Compass:
Wait till nAa fix
Video Recording Lag:
did you experience this
use this file Download
Auto Brightness:
use this tutorial
Code:
1. disable auto brightness first in display
2. go to cm settings --> display --> automatic backlight --> choose use custom and allow light decrease
3. tick edit other level
4. set number of levels to 13
5. look at this pic [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874309&stc=1&d=1327627892"]Here[/URL] And [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874311&stc=1&d=1327627892"]Here[/URL]
6. enable auto brightness in settings (not cm)
7. restart
8. enjoy
Android market app won't show up:
clear data on app settings
Just use recommended tweak:
Non-Recommended tweak make ur phone less stable
Recommended:
SuperCharger
Ram Manager / PRO
Juwe Ram's script
Etc...
Non-Recommended
Build.prop tweak
init.d tweak
IPV4/IPV6
Etc...
End of first post continued in 2nd post ​

Guide for Minicm7​
Notice ADW launcher Lag use this settings:
Code:
1) Screen Preferences - Desktop scrolling speed - set to something low-ish like 150-200, default settings are just plain moronic here. Desktop overshoot should be fine at 30 or 40.
2) Drawer Settings - Horizontal Drawer definite on (this is far superior to the scrolling drawer if you have more than a few apps, and feels much smoother).
3) Drawer Settings - Zoom effect speed - 400 is a decent setting, default was way too high.
4) Drawer Settings - Columns/Rows - 4x4 is a nice setting for portrait, if you don't like a crammed screen.
5) System Preferences - Wallpaper Hack - check this. If you have issues, change wallpapers to something of a sane size.
6) System Preferences - Use Screen Cache - check this.
7) System Preferences - Scrollable Widget support - you should start with this unchecked. Only check it if you have issues with some
Make ur phone fast without tweaks?
here my perfomance settings
Go to CyanogenMod Settings --> perfomance settings
Code:
1.) Set compcache ram usage to 18%
2.) Enable use jit
3.) Disable Surface Dithering (optional)
4.) Enable 16bit transparency
5.) Enable Allow purging of assets
6.) VM heap size 48mb
7.)
SDcard cache size 1024kb Class 1,2
SDcard cache size 2048kb Class 3,4
SDcard cache size 3072kb Class 4,5,6,7,8
SDcard cache size 4096kb Class 9,10
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 245mhz
3.) Max Cpu frequency 691mhz+ (optional)
4.) Set on Boot
Make minicm7 more battery save?
here my battery save settings
Note: this settings overwrite "Make ur phone fast without tweaks"
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 19mhz
3.) Undervolt
4.) Set on Boot
final step: Delete Unused App
Extra Section​​
Coming Soon
End Of My Post ​

LtHuNTer_StepheN said:
Don't use any tweaks:
tweaks make your phone fast but less stable
and don't use xloud and mobile bravia
they are fake
Click to expand...
Click to collapse
+1 10char..

I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469

hixvolnutt said:
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
Click to expand...
Click to collapse
For Perfomance it's better set 48mb
this help app memory management
this heap size is usefull for HD games
Oh i forgot
i will edit it
for that tweak is already tested
what i say is
Code:
build.prop tweak
mobile bravia engine
and useless tweak
for that tweak it may increase stability
i will edit so people understand

Post Updated
Thanks

Is there any way to fix compass?the compass is somehow inverse

for auto brightness setting, how many level are you using? Ultra brightness enable or not?

Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk

Post Updated

LtHuNTer_StepheN said:
Post Updated
Click to expand...
Click to collapse
Oops, i'm still using nAa 08...maybe because of that...0_x
Sent from my E15i using Tapatalk

bayumahendra24 said:
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
i think screen cut happen with smartass v2

D E V I L said:
i think screen cut happen with smartass v2
Click to expand...
Click to collapse
Flash the new nAa-08b kerner. This fix the problem

Hi!! I have just one question. The tethering wifi always disconnects when screen turns off. I tried wi-fi settings, advanced, never sleep but does not work. Do you have other solutions? Thanks

still score highly!!!
plus avent updated kernel and rarely get screen cuts!!
so id say great rom plus kernel!!

flegga92 said:
Flash the new nAa-08b kerner. This fix the problem
Click to expand...
Click to collapse
Still using nAa 08 (havent change kernel because what i see on the changelog, the difference between nAa 08 and 08b only the screen cuts fix) with:
- Cpu freq 19-600mhz
- smartassv2 on
- undervolt on
- bootanimation enabled
No more screen cuts since my prev post.
Screen cuts SOMETIMES only appear when i'm in cwm req...thats good enough for me..

For the video lag fix,does it work with other rom which have the same problem?flash with xrec or cwm?

Hello to everyone and excuse me if my question is probably going to be dumb (for sure it's an OT so please forgive me about that) but I'm quite clueless about the issue I'm experiencing and I hope to find an advice here.
I own and X10 mini with MiniCM 2.1.6 and 2.6.29.6-nAa-08 kernel. Everyhing's fine, really a great piece of work that has put new life into my beloved X10 Mini but I'm experiencing the 'screen cut' issue that's discussed here too: it happens only with some apps (Labyrinth for example) but it happens and I'd like to get rid of this.
I don't know if it could be an issue related to the apps not being designed for Gingerbread but I don't think so because I expect something different should this be the case.
I've read that the kernel nAa-08b is intended to solve this issue but it seems (maybe I'm wrong) that it isn't suitable for my X10 mini (I've made some digging around and the latest kernel version for my mini seems the one that I've already installed while the 08b seems to be intended for the X8). I'm sure that the reply is already around here but I couldn't succeed in finding it though I've read a lot (really a lot!) of posts here and there, especially on the official thread:
http://forum.xda-developers.com/showthread.php?t=1068553
where unfortunately I couldn't post because I'm a new member with less than ten posts. Some advices? Thanks anyway!

very good guide
thanks you very mach!

post updated
sorry im busy lately

[CWM] Skeleton zips for system and user apps & build.prop optimization

http://forum.xda-developers.com/showthread.php?p=24233846
Just download the attached zip file according to your need, add apps.. flash.. enjoy.. Tested with cwm 5.0.2.7 touch..
********************************************************************************************************************************************************
Editing build.prop.
Even though some of the things are well known for us, some of them are new for me..So im jus posting it.
1.Force launcher into memory
Property
ro.HOME_APP_ADJ = 1
Function
This will force the Default launcher into memory. But your device should be having enough free memory, otherwise you will meet lags and performance will be reduced severely. Use a light weight launcher for this.
Values
0 : Turns off the feature. Frees up memory.
1: Keeps the default launcher in memory .Will have highest priority and Android auto kills it only when it’s really necessary.
2.Improving Camera Image quality
Property
ro.media.enc.jpeg.quality=100
Function
This will force the camera application to use 100% quality setting when saving camera images as JPEG
Values
1-100 : with 1 as the worst quality and 100 as the best quality.
3.Increase resolution of panorama image
Property
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
Function
This will force the panorama mode in the camera app to save the image at a higher resolution. This may not be supported by all phones. And since it is an Android 4.0 feature , you will need that android version as well.
Values
defres: Provide the full panorama image resolution.Consisting of all images.
frameres: Provide the resolution of each frame of panorama.
4.Improve performance in video playback and streaming
Property
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=true
Function
Android uses the media framework named “Stagefright” from Froyo ( Android 2.2 ) onwards. While Stagefright is more open and simple, it is sometimes buggy compared to the previously used OpenCore framework. However, Google has greatly improved its stability. These values might affect the stability of playback in some devices, if it is ruining your experience , then revert to the original values.
5.Improve touch responsiveness through Hardware Rendering
Property
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
Function
This will force the system to use GPU for rendering each 2D frame in applications. Since android uses frame by frame rendering of the screen normally, this will offload the rendering to GPU by a huge amount and will make the user experience smoother.
Values
debug.composition.type values : GPU / CPU . GPU will make use of the graphic chip on your device for rendering each frame.
6.Disable Error Profiler
Property
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Function
These commands enable or disable the error profiler in the android. For most android users, there is no use in having error profiling . however , some applications might make use of this for generating error reports.
Values
0 :Enable the feature. Better to delete the property if you don’t want to disable it.
1: Disables the feature.
7.Modify WiFi network scanning time.
Property
wifi.supplicant_scan_interval=180
Function
This command will be already present in all build.prop files. This controls the number of seconds the device waits before scanning for WiFi networks.
Values
Default value is 180 . It is in seconds . You can increase the value if you want to save more battery and doesn’t use WiFi extensively. Or else , you can decrease it , if you are dropping your WiFi signal often.
8.Disable logcat – Android Logger
Property
logcat.live=disable
Function
This command controls the Android Logcat file generation. This file is mainly used for debugging. Expensive disk reads/writes can be reduced by disabling Android logcat.
Values
disable / enable
9.Improve Voice Call clarity
Property
ro.ril.enable.amr.wideband=1
Function
This command controls the AMR audio codec’s property.AMR codec is used for voice calls.
Values
1 or 0 .
10.Disable Extended JNI Checks
Property
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
Function
“JNI does very little error checking. Errors usually result in a crash. Android also offers a mode called CheckJNI, where the JavaVM and JNIEnv function table pointers are switched to tables of functions that do an extended series of checks before calling the standard implementation.” . That’s the definition from Android developers documentation. While disabling this may cause some data loss when the application crashes, most applications ,which are popular, have been thoroughly checked and hence will be using precious CPU time for extended checks . Save that time by disabling this.
Values
0 / 1 : disable / enable .
11.Disable Android Device Check In.
Property
ro.config.nocheckin=1
Function
Every Android device checks in at the Google Servers when an internet connection is found, this helps Google in tracking the number of installations and the statistics of different android versions. This can be disabled to save for saving traffic and some CPU time, due to the frequent polling for checking internet connection.
Values
1/0 for disabling and enabling , respectively.
12.Increase Voice Call Audio Adjustment Steps.
Property
ro.config.vc_call_steps=20
Function
By Default, android offers seven audio levels for calls. This can be altered through this command , if you want to fine adjust the volume of your voice calls. This won’t increase the volume if it’s already low. But you can manage it by more precisely.
Values
Number of steps as integers. 7-20 is recommended. 7 is the default.
Editing Build.Prop
For editing build.prop, your device should be rooted. That’s the first requirement.
It is at /system/
If you have Root Explorer / ES File Explorer installed on your device you can edit from the device itself. More easier method is to get he application named build.prop Editor . It can be used to change the values and add new fields.

works only in cm10 based roms.

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Of course

doesn't CM10 Rom for O1 include this? U posted it separately so thought might be working with CM9 or CM7

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Then what is the point?
Sent from my LG-P500

This tread should be named as:[APP][CM10] messaging app with quick reply, popup notifications
Sent from my LG-P500 using xda premium

It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:

carrthee89 said:
It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:
Click to expand...
Click to collapse
I think we have this
Sent from my LG-P500 using Tapatalk 2

Bump.Now the thread is usefull
Sent from my LG-P500 using xda premium

Updated with build.prop optimizations

** Avoid Focus Stuttering in Low Light for "SCEF02" Users **

** Avoid Focus Stuttering in Low Light for "SCEF02" Users **​
Hello guys, i'm too one of the SCEF02 users who suffered from low-light focusing for over a year now
we all tried everything we could, like using SIEG02 firmware that would give away our focusing-flash and video light
or setting exposure to -4 and creating a dark video!
i always knew this trick would work but we hadn't this option in stock video recorder or lgcamera app
the answer is lowering the ISO!
i have found a software from market that u can set iso for video recording, its called: "CameraPro (Camera X)" (not free but it worth it)
in v2.27 of this software the hd & full-hd video recording of GSII is fixed and now we can use it as our primary video recording software
in iso 100 and 200 u would Never have Low-Light Stuttering and its not dark while recording its just a bit draker even less than setting exposure from 0 to -1
i tested it last night and i've got Smooth video and Quick focusing like filming in day!
all u have to do is to install and open the software & :
1. go to settings (first tab)
2. find this option: "Show unsupported controls" (now u have control over ISO)
3. go to video tab (8th tab) and in "video profile" and select "720p 1280x720"
4. scroll down and select "Enable video expert mode"
5. set other parameters as you like, audio channels, audio bitrate, video bitrate and many more
6. click back and in main screen select settings icon to change ISO
7. set it to "200"
It's Done! now u are ready to capture non-stuttering videos in low-light
any question about software or sharing your ideas are welcome
Hope u enjoy it...

KINGTATu said:
** Avoid Focus Stuttering in Low Light for "SCEF02" Users **​
Hello guys, i'm too one of the SCEF02 users who suffered from low-light focusing for over a year now
we all tried everything we could, like using SIEG02 firmware that would give away our focusing-flash and video light
or setting exposure to -4 and creating a dark video!
i always knew this trick would work but we hadn't this option in stock video recorder or lgcamera app
the answer is lowering the ISO!
i have found a software from market that u can set iso for video recording, its called: "CameraPro (Camera X)" (not free but it worth it)
in v2.27 of this software the hd & full-hd video recording of GSII is fixed and now we can use it as our primary video recording software
in iso 100 and 200 u would Never have Low-Light Stuttering and its not dark while recording its just a bit draker even less than setting exposure from 0 to -1
i tested it last night and i've got Smooth video and Quick focusing like filming in day!
all u have to do is to install and open the software & :
1. go to settings (first tab)
2. find this option: "Show unsupported controls" (now u have control over ISO)
3. go to video tab (8th tab) and in "video profile" and select "720p 1280x720"
4. scroll down and select "Enable video expert mode"
5. set other parameters as you like, audio channels, audio bitrate, video bitrate and many more
6. click back and in main screen select settings icon to change ISO
7. set it to "200"
It's Done! now u are ready to capture non-stuttering videos in low-light
any question about software or sharing your ideas are welcome
Hope u enjoy it...
Click to expand...
Click to collapse
thanks KINGTATu

Thank you for the detailed guide. I will definately try it and report back.
Which rom are you on Btw?
Sent from my GT-I9100 using Tapatalk 2

_Sofos_ said:
Thank you for the details guide. I will definately try it and report back.
Which rom are you on Btw?
@re-2007 deleted the link before you get banned
Click to expand...
Click to collapse
i'm on stock XWLPX with Siyah v4.1.5
yeah, remove that link it's not allowed, thanks

ISO values comparison:
Recording Speed: 100>200~1250~Movie>>400>>>800
Recording Lightness: 800>400>1250>200~Movie>>100
Auto mode is unpredictable

It is indeed much better than lgcamera but stuttering is still there every now and then mate.
At least for me.. It's a curse
Sent from my GT-I9100 using Tapatalk 2

for me no stuttering at all........ again great thanks to KINGTATu
i'm on stock IML74K.JHLP9 stock kerne 3.0.15l
4.0.3

Will try with stock rom cause I'm with cm10 atm
Sent from my GT-I9100 using Tapatalk 2

This method is well known for months... and is not true solution for SCEF02 problems. You can minimize shuttering effects but on the end you get darker video. So you decrease video quality on your own changing one issue for another.
There was no, is no and will be not any real solution for this problem except full camera module change.
Brutal life.

Burgscheinkerkdeiktraast said:
This method is well known for months... and is not true solution for SCEF02 problems. You can minimize shuttering effects but on the end you get darker video. So you decrease video quality on your own changing one issue for another.
There was no, is no and will be not any real solution for this problem except full camera module change.
Brutal life.
Click to expand...
Click to collapse
v2.27 is out for few days now and just this version is compatible with GSII, how u used it before?! there's any other software that capable of changing ISO during videos?
u tried this urself? it wont get any darker its even brighter than setting exposure to -1
try then post ur comment

KINGTATu said:
v2.27 is out for few days now and just this version is compatible with GSII, how u used it before?! there's any other software that capable of changing ISO during videos?
u tried this urself? it wont get any darker its even brighter than setting exposure to -1
try then post ur comment
Click to expand...
Click to collapse
can you show any movie - the best test conditions would be night and outdoor street lamps. I am curious how it works with fixed ISO.

bartekaki said:
can you show any movie - the best test conditions would be night and outdoor street lamps. I am curious how it works with fixed ISO.
Click to expand...
Click to collapse
it's day time here and my internet upload speed is kinda crappy! but i will upload some short videos till tomorrow's night

Burgscheinkerkdeiktraast said:
This method is well known for months... and is not true solution for SCEF02 problems. You can minimize shuttering effects but on the end you get darker video. So you decrease video quality on your own changing one issue for another.
There was no, is no and will be not any real solution for this problem except full camera module change.
Brutal life.
Click to expand...
Click to collapse
Try it by your self it is true solution :good:
NO darker video AT ALL thanksss :laugh:

KINGTATu said:
v2.27 is out for few days now and just this version is compatible with GSII, how u used it before?! there's any other software that capable of changing ISO during videos?
u tried this urself? it wont get any darker its even brighter than setting exposure to -1
try then post ur comment
Click to expand...
Click to collapse
So is it darker than 0 setting or not because if it is then it is not solution. It is just walkaround, changing one thing (issue) for another.
Yes I had tested this app before I replaced module to OMEF01 and videos were choppy (2.20 IIRC).
lgCamera can change ISO too, worth to try.

i'm using lgcamera since i bought my phone! changing ISO on lgcamera is not effective, worth a try!!
-------------------------------------------------------------------------------------------------------------------------------------------------
Here r the videos from my device, i had to resize it to nHD
Edit: CameraPro video is darker because i forgot to change exposure from -1 to 0 (it's -.5 btw)

Hi KINGTAtu:
first of all, thanks for sharing your experience with all of us.
I have some questions about this software:
I got the version 2.27 that you mentioned in your post and when I went to "Video profile" in the menu I only have 2 choices: "low quality" or "high quality", but you said that you could select 720 p 1280X720.
How is that possible? Do I need to go to another place in the menu?
In addition, I saw that when I selected video, it says "Video (Test)". Is this your case also?
In the video section of the settings, it also says that the video section is a beta version.
So far, I was using lgcamera with ISO set to 200 and it is working great, but obviously when I read your post I was curious about this software.
However, I realized that in lg camera if I touch to focus before I start recording, the program does it very quickly and show me a green square meaning that it focused well. On the other side with CameraPro, it focuses not so quickly and the result is always a red square, so I am not sure if it is working properly.
Thanks again for your comments, and regards.
Jorge

joromano said:
Hi KINGTAtu:
first of all, thanks for sharing your experience with all of us.
I have some questions about this software:
I got the version 2.27 that you mentioned in your post and when I went to "Video profile" in the menu I only have 2 choices: "low quality" or "high quality", but you said that you could select 720 p 1280X720.
How is that possible? Do I need to go to another place in the menu?
In addition, I saw that when I selected video, it says "Video (Test)". Is this your case also?
In the video section of the settings, it also says that the video section is a beta version.
So far, I was using lgcamera with ISO set to 200 and it is working great, but obviously when I read your post I was curious about this software.
However, I realized that in lg camera if I touch to focus before I start recording, the program does it very quickly and show me a green square meaning that it focused well. On the other side with CameraPro, it focuses not so quickly and the result is always a red square, so I am not sure if it is working properly.
Thanks again for your comments, and regards.
Jorge
Click to expand...
Click to collapse
that's odd! u should have 1080p 720p 480p ... and the two low and high quality
i couldnt understand what u mean by "Video (Test)"
yeah the video recording section is still in beta but now its ready for GSII
u dont need to touch to focus before starting to record, why u do that? it always focuses before start

How do i know what camera module that i have?

digitallysick said:
How do i know what camera module that i have?
Click to expand...
Click to collapse
CHECK YOUR CAMERA MODULE FIRMWARE
type in a dialer *#34971539#

EPIC POST IS EPIC
Thanks a lot man for sharing this with us .!

My "Perfect" Build v1.0 - Guide (Custom Kernel, tune, zips, apks, libs, sound, vids)

My "Perfect" Build v1.0 - Guide (Custom Kernel, tune, zips, apks, libs, sound, vids)
Below you will find a detailed plan on how to get the absolute most out of your Moto G 2015. I've spent countless hours testing and tuning -- coming up with the setup shown here. Its unbelievably fast and effective, with top tier battery life, and an amazing and unmatched sound system.
Requirements (all downloads listed here are found on XDA, along with their threads for support and security verification)
*Flashables* (All found on XDA)
-CM13 Based Rom (I prefer crDroid, but also CM13 Official Nightly, and Temeseks CM13)
-G-Apps Pico 6.0 (latest version. you can install higher levels of gapps if you so desire, but pico will work just fine)
-Inazuma R3 Kernel
-Optimus R6 Kernel
-PDB-ABS Tweaks v5.0 (init.d Scripts, build props, etc)
-Project Skynet Genesys TX6
-PMB SQlite3 Engine Database v5.1
-FeraDroid Engine v0.20 Beta 3 (*optional)
-Xtreme Music v7.03
-Divine Beats Dolby Atmos v5.0
-Bravia v4 and X-Reality Engine 13-16mp
*APKS* (All found either XDA or Play)
-Selinux Mode Changer (on XDA)
-Kernel Aduitor - Modded Version (on XDA - Formerly known as Singularity)
-Busy Box Pro 1.24.1-Stericson (on XDA)
-System App Remover (Google Play)
-Terminal Emulator (Google Play)
Click to expand...
Click to collapse
I would recommend that you start entirely fresh -- full wipe, then clean install the rom/kernel/and zips.
...Lets Begin!!
Initial Setup:
-Download all the required apk programs and flashable zips, as well as the latest versions of a CM13 stable ROM (I prefer CrDroid for all out speed and stability)
-Wipe (or factory reset), then clean install in this order:
a)xxxxx CM13 Stable Rom
b)Open gApps 6.0 Pico
c)Inazuma R3 Kernel
d)Optimus R6 (NOT R7!!)
e)Project Skynet Genesys TX6
f)FeraDroid Engine v0.20 Beta 3
g)PMB SQlite3 Engine Database v5.1
h)PDB-ABS Tweaks v5.0
i)Xtreme Music v7.03
j)Divine Beats Dolby Atmos v5.0
*THERE IS A MAX of 10 ZIPS in the QUEUE. After you flash the initial 10, you can flash this next one.*
k)Bravia Engine v4 and X-Reality Engine Port
It will take about 5 minutes to flash all the zips listed above, but trust me... its worth it!
-Once all zips are flashed, wipe cache/davlik, then reboot.
-Run through setup, unchecking every single option along the way.
-Once loaded to the home screen, be sure to make your SD Card portable or permanent. (I prefer portable)
Initial Tweaks/Settings
-Enable Developer Options
1)2d gpu rendering
2)animation scaled down to lowest setting
3)advanced reboot menu
4)root enable and adb
-"MORE" (below wifi and data)
6)Emergency Broadcasts ALL OFF
-Sound
1)Vibrate on Touch OFF
2)Intensity 0%
-Display
1)low brightness level
2)adaptive OFF
3)Ambient OFF
4)Live Display OFF
5)Double Tap ON
6)Sleep 30 seconds
7)Wake up on plug OFF
8)Daydream OFF
9)Battery Light OFF
-Security
1)Unknown Sources
-System Profiles OFF
-Privacy
1)Block private
2)Block unknown calls/messages
-Location
1)OFF
2)Scanning OFF
Click to expand...
Click to collapse
Install all APKs from the download list:
-Fully Install BusyBox Pro 1.24.1 from within the program.
-System App Remover (all of these are optional, but here is my personal list. 50mb, and increased battery/performance)
**audio fx, basic daydreams, black hole, bluetooth extensions, BT midi service, browser, bubbles, calculator, calendar and storage, call log backup, cLock, CM wallpapers, CM Actions, android backupconfirm, android shared storage backup, android wallpaper cropper, email, exchange services, fm radio, google backup transport, google calendar sync, holo spiral, html viewer, live lock screen service, live wallpaper picker, location services, market feedback agent, omni switch, phase beam, photo screen savers, photophase, print spooler, proxy handler, screencast, setup wizard, terminal, themes, themes provider, user dictionary, vpn dialogs.**
-Selinux Mode Changer: Set to Permissive
-Kernel Aduitor - Modded
Click to expand...
Click to collapse
After installing Kernel Aduitor, here are the settings that will provide you with the perfect balance of battery life and performance.
Again.... (Very Important Settings)
-CPU:
-1401/200mhz MaxMin
-Conservative Governor (50 Down, 85 up, 15 feq step, everything else untouched)
-Schedule Work Queues on Awake CPU's - ON
-CPU Boost 0ms
-Sync Threshold Disabled
-Input interval 0ms
-Disable ALL core's input touch boost
-HotPlug:
-Intelliplug ON
-Conservative Profile (May use Balanced as an alternative)
-Touch Boost OFF
-Hysteresis 8-10 (May use 14-16 when used with Balanced Profile)
-Threshold Value 1000
-CPU Off-Screen Max - 400 (if unused while screen off.), otherwise, use 533-800mhz if you plan on listening to music while the screen off. 400mhz will cause skipping and major lag for this purpose.
-Thermal:
-Core Control ON
-VDD OFF
-Temp Throttle OFF
-GPU:
-465/200mhz if gaming. Otherwise 310/100.
-MSM Adreno Governor
-Adreno Idler ON
--60, 10, 10 for battery favoring
--35, 20, 5 for balanced
--25, 25, 3 for performance
-Screen:
-Color Profile CUSTOM
-Red 235, Green 240, Blue 255
-Min RGB 35
-Sat Intensity 80
-Hue 0
-Screen Value 130
-Contrast - 120
-Automatic High Brightness OFF
-High brightness OFF
-Battery:
-Power Suspend Mode HYBRID (Userspace for extreme battery)
-Suspend State 0 (When using Userspace, try 1 or 2 depending on your need for battery life)
-IO Scheduler:
-Internal- 2048kb read ahead
-Option 1 and 2 (*sioplus or deadline*)
-scheduler tunables (option 1-sioplus, for super fast reads and single task use): asycn read 400, write 4000, fifo batch 32, sync read 200, write 2000, writes starved 2 (option 2-deadline, for benchmarking performance (read 200, write 2000, fifo 32, front merge 1, read 300, write 6000, starved 2
-Option 3 and 4 (tripndroid and bfq) -- for everyday, well rounded performance. Excellent playback of HD videos, extremely fast USB transfer, very effective multitasker.
-External: 512kb read ahead
--TripnDroid or BFQ
-Rotational Storage ON
-Random Entropy ON from rotational storage
-I/O Stats OFF
-RQ Affinity 1 (You may try 2 if you aren't multitasking, 1 is more balanced between performance and multitasking, while 0 is for when performance is less needed, but effeciency and error free work is required)
LMK:
-Adaptive LMK ON
-15, 20, 35, 60, 95, 140mb
Virtual Memory (VERY IMPORTANT for performance, hence I will give ranges instead of exact figures. Depending on what you use your phone for, these settings can be drastically different. The ones I use are for all out performance, low lag, and moderate multitasking)
-Dirty Ratio: 75-95
-Dirty Background: 40-60
-Dirty Expire 500-750cs
-Dirty Writeback 5000-7500cs
-OverCommit 80-100%
-Swappiness 5-25
-VFS Pressure - 20-40
-Laptop Mode ON
-Min Free 4096
-Extra Free 8192
-zRam 300-350 (Stock is 510mb. I feel that a small ramdisk is just as effecient, while freeing up a few hundred mb for more traditional purposes.)
-WakeLocks:
-wlan_rx, wlan_cntrl, and wlan OFF
-Entropy:
-64 (128 optional) Read
-128 (256 optional) Write
-Misc:
-SELinux Permissive
-TCP Algorithm CUBIC
-Vib Strength 0%
-Logging OFF
-Dynamic F-Sync ON
-OTHER:
-Check "APPLY DURING BOOT" to every section of Kernel Aduitor's App
Click to expand...
Click to collapse
Next:
-Install Terminal Emulator, and open it.
-type "su" at the command prompt, then enter
-type "ABS" (all capital!) then enter.
-You will now see a basic text menu.
-Select #1. This will check your system to make sure its ready to move forward with the tweaks.
-Back on the main menu, select option 2
-Run the following scripts: (Run individually, then return to previous menu)
--#2PDB-Booster,
--#3 PDB Junk Cleaner
--#5 PDB-BuildProp Tweaks, then run each of the following tweaks:
2- Image quality
3- GPU Rendering
5- Increase Scrolling Speed
7- Touch Smoothness
9- Internet Speed Extender
11- Fix App FC's
13- Faster boot
14- Signal Strength Extender
15- HPSA Internet Tweaks
16- Flag Tuner
17- Voice Quality Extender
19- Faster Streaming
20- Liquid Smooth UI
21- 60 Frames Per Second Enable
-Next, return to main menu, and choose #6 PDB-Profiler
-Select your primary need. I use multitasking.
-#7 Ad Blocker Enable
-#8 Internet Speed Tweaker
-#11 SqLite Optimizer
-#12 and #13 should already be activated, but if not, do so now.
-#14 SD Card Speed Tweaker
-Return to Main Menu once again and choose #4
--REBOOT DEVICE--
Click to expand...
Click to collapse
After reboot, enter the Terminal Emulator once again:
Type "su" then enter
Then type "menu" (all lower case) and enter,
After the menu appears, perform command #1 - Checks. It should return all Ok's. If not, please visit the Skynet Genesys Thread for help.
Next, run command #3, and set the mode to balanced for everyday use, battery for low performance/good battery backup, and gaming for extreme performance with less regard for battery life. After completing this step, run command #4.
On this menu, run the following commands:
#1 Xtreme Renices (Places urgent priority on principle processes)****optional*** some ROMs have difficulty with this. Heating issues possible.
#3 Scaling + (lower power use and performance during deepsleep)
#4 WiFi Sleep (allows quicker dormancy of the wifi during inactivity)
#6 KSM (Memory Mergining, Same Page Merging of data used by multiple processes)
**#7 Google Killer (*OPTIONAL* Kills Google appls for battery life extension)
#8 Touch Screen Tweak (Improves responsiveness and reactivity of the touch screen. *OPTIONAL* If the earlier ABS build prop tweak did the trick, then you can skip this one. However, if it didn't give you the results you were looking for, I'd recommend trying this one.)
#9 Netboost - Some additional internet boosting tweaks
#10 Assertive Display - An advanced display manager for Qualcomm Hardware. Its a night/day difference for those who haven't used it before. It takes ambient and live display to a whole new level. Giving you clarity and depth in practically ANY light conditions.
Click to expand...
Click to collapse
With that all said and done.
Its been a pleasure, researching all of the tweaks and tunes available. I'm sure that those who are more experienced than me have came up with better ideas, but for this hillbilly from kentucky... its the best I can do! I love this phone, and the performance it offers for budget pricing!
Sorry its so long, and probably difficult to understand. But I hope you appreciate the work I put into it. There's a few revisions I plan on making to increase battery life, with the help of xposed, greenify, amplify, wakelock tuning, etc. And I didn't really get around to talking about the sound lib and progs we installed. I can assure you, there's nothing placebo about viper4android 2.4.01, dolby atmos, xtreme music, and about a dozen or so libraries that are log proveable as working. The bravia v4 Xreality engine.... I just started using it, and haven't had time to really test it out... but it *should* give us an increase in graphic quality, especially in regards to pictures and videos. In the coming days I'll be adding a new section to further increase audio, productivity, graphics, and battery life. But for now..... this is what ya get! REMEMBER THOUGH..... SELinux MUST BE SET TO PERMISSIVE for Xtreme Music Libs to work correctly. You'll be grateful that you did!
Thank you for reading, and I hope you get as much out of it all as I did.
Have a great weekend guys! and gals!

Feel free to cherry pick, add, remove, tweak, etc. No negative talk. If you don't like my work, do your own build. But if you have something constructive to say, questions to ask, or thoughts to add.... I'd be super grateful, and pleased to read them! My goal is to get the smoothest, fastest, and longest lasting battery as possible... . blended into one neat package.

I'll have to try this when I have time. Thanks for the extensive list of tweaks and addons!

@bubbyj
Thanks mate, looks good.
Would be good that you add the links for each item we have to download.

CPU frequency doesn't go down stays at 1,4 GHz heats up my phone..

Do we have to install Inazuma AND Optimus kernels or choose one?

HelpMeruth said:
CPU frequency doesn't go down stays at 1,4 GHz heats up my phone..
Click to expand...
Click to collapse
I put the wrong entropy levels in. It should be 64-128 read and 128-256 write. That cleared it up on my end. Otherwise check your CPU settings. Down threshold 50-60, up 80-85, step 12-16, conservative gov, conservative hotplug profile, intelliplug active, touch disabled in all locations. Sync disabled. Boost 0ms. If this fails, post screenshots of kernel auditor, each section. We will correct the problem for you.
-------
Yes, the inazuma provides a few options that optimus r6 and r7 don't. And vice versa. And because optimys uses any kernel, it simply overlays its settings on top of the existing one.
R7 has 1401 oc, but loses the intelliplug hotplug. It also loses adreno idler. And has a r6 few unique features added compared to inazuma r3. So by installing r3, then dirty flashing optimus r6, you get a hybrid kernel that offers the best of both. You get all freqs from 200 to 1401, with an added 300mhz state. You get intelliplug hotplugging. You get GPU oc and under clock of 100mhz for extreme battery savings and retain the adreno idler. You get all of optimus optimizations and updates, as well as all the governors and schedulers combined. Its really an awesome kernel that results in crossbreeding the two.

Edited the original post. Made extreme renices optional, fixed entropy causing CPU loading (now 64/128 or 128/256, whichever works best for your usage). Also removed battery optimize from ABS tweaks. It works well, but may cause lags.

It works fine without skynet and abs but the moment i flash any of those two the cpu jumps ans stays at 1,4 ghz

Where do you get R6? I can't find a link only for r7
Envoyé de mon MotoG3 en utilisant Tapatalk

vinz244 said:
Where do you get R6? I can't find a link only for r7
Envoyé de mon MotoG3 en utilisant Tapatalk
Click to expand...
Click to collapse
https://basketbuild.com/filedl/devs?dev=Flashhhh&dl=Flashhhh/Optimus/Optimus-R6-Osprey.zip
here

U can use ApkPure no need gapps anymore

Any update on the kernel setup?

Can someone just send me direct links to the correct version of each flashable files I need to download? I've tried doing this myself multiple times, but once it flashes the "audio enhancer" files it starts to say "unable to mount /data" and "unable to mount /storage" in the TWRP log, and when I reboot into the device, it takes a few minutes to "optimze apps" then it just sends me to the Cyanogenmod boot screen and it stays there. I really shouldn't be asking you guys for something like this but I've had to, multiple times, wipe my data and I'm just getting a bit frustrated since I really want to try this build. Thanks in advance.

OMG man, you give me another mobile with this tutorial, thank you very much mate!!!

Jushten said:
Can someone just send me direct links to the correct version of each flashable files I need to download? I've tried doing this myself multiple times, but once it flashes the "audio enhancer" files it starts to say "unable to mount /data" and "unable to mount /storage" in the TWRP log, and when I reboot into the device, it takes a few minutes to "optimze apps" then it just sends me to the Cyanogenmod boot screen and it stays there. I really shouldn't be asking you guys for something like this but I've had to, multiple times, wipe my data and I'm just getting a bit frustrated since I really want to try this build. Thanks in advance.
Click to expand...
Click to collapse
Same thing here , i still not found any way to get all the files flashed :/

Jushten said:
Can someone just send me direct links to the correct version of each flashable files I need to download? I've tried doing this myself multiple times, but once it flashes the "audio enhancer" files it starts to say "unable to mount /data" and "unable to mount /storage" in the TWRP log, and when I reboot into the device, it takes a few minutes to "optimze apps" then it just sends me to the Cyanogenmod boot screen and it stays there. I really shouldn't be asking you guys for something like this but I've had to, multiple times, wipe my data and I'm just getting a bit frustrated since I really want to try this build. Thanks in advance.
Click to expand...
Click to collapse
Check bellow
---------- Post added at 10:08 PM ---------- Previous post was at 10:08 PM ----------
FrancyelZelling said:
Same thing here , i still not found any way to get all the files flashed :/
Click to expand...
Click to collapse
Here is the list, all of then worker in my phone, but the names that he gaves is a bit different so be careful
NOTE:
I flashed the crDroid (04-22-2016) and it make a bootloop, I tried the AICP too, same problem, the only one which worked was the Nexus Experience 10.2. If you wanna try, the link is below.
Main Post:
*Nexus Experience: http://forum.xda-developers.com/2015-moto-g/development/rom-nxrom-nexus-experience-mm-6-0-1-t3347772
*G-Apps Pico 6.0 :http://opengapps.org/
*Inazuma R3 Kernel: http://forum.xda-developers.com/2015-moto-g/orig-development/kernel-inazuma-t3320323
*Optimus R8 Kernel:http://forum.xda-developers.com/2015-moto-g/orig-development/kernel-optimus-kernel-r1-t3300877
*PDB-ABS Tweaks v5.0 : http://forum.xda-developers.com/android/software-hacking/tweak-arkaynine-boost-script-v3-0-t3120404
*Project Skynet Genesys TX6: http://forum.xda-developers.com/android/software-hacking/android-l-booster-1-soon-t3030796
*PMB SQlite3 Engine Database v5.1: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443
*FeraDroid Engine v0.20 Beta 3:http://forum.xda-developers.com/and...beta-feradroid-engine-v0-19-ultimate-t3284421
*Xtreme Music v7.03: http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
*Divine Beats Dolby Atmos v5.0: http://forum.xda-developers.com/android/software/app-divinebeats-sound-master-phone-sony-t3274355
*Bravia v4 and X-Reality Engine 13-16mp: http://forum.xda-developers.com/and...recompeliren-bravia-engine-x-reality-t3141461
Download link:
*Nexus Experience: http://nxrom.us/motog3.html
*G-Apps Pico 6.0 ARM/6.0/PICO)
*Inazuma R3 Kernel: https://www.androidfilehost.com/?fid=24459283995305053
*Optimus R6 Kernel: https://basketbuild.com/filedl/devs?dev=Flashhhh&dl=Flashhhh/Optimus/Optimus-R6-Osprey.zip
*PDB-ABS Tweaks v5.0 :https://www.androidfilehost.com/?fid=24385658843824596
*Project Skynet Genesys TX6: https://www.androidfilehost.com/?fid=24499762635998635
*PMB SQlite3 Engine Database v5.1(will start automatically ):http://forum.xda-developers.com/attachment.php?attachmentid=3440756&d=1439715903
*FeraDroid Engine v0.20 Beta 3(will start automatically ):http://forum.xda-developers.com/attachment.php?attachmentid=3696184&d=1458938908
*Xtreme Music v7.03: https://www.androidfilehost.com/?fid=24499762636007047
*Divine Beats Dolby Atmos v5.0: https://userscloud.com/ppg965q9d4q7
*Bravia v4 and X-Reality Engine 13-16mp(The second Option): https://drive.google.com/folderview...leEc4MUVXWTdwQnFqV2kxRDcyblBpNXhELThEMGdvWmc#

The problem with skynet is the jump in entropy settings to like 2048 or so, that automatically occurs on some phones. This causes the cpu to lock in at 1.4ghz and pretty much stay there, and loading at 60-80%. I'm going to be offering a brand new build based around the AOSP roms that are popping up everywhere. I'm currently testing it thoroughly. Expect a new thread with a smoother, faster, snappier, and cooler running phone based around this new platform -- probably by the end of the week.
It will include an entropy fix with it. My current settings are 1536 and 256 (read-write) and it does great!
And just one more thing --- along with the new build I'll be offering, I'm also working on an intense battery build. I understand fully that not everyone is interested in squeezing out every last bit of performance and instead desire a usable phone that lasts much longer between charges. I've been working on it off and on for about 3-4 weeks now and have found some amazing tweaks and mods that'll accomplish that goal. The hardest part for me, is being an all out performance nut --- I lose interest in increasing battery life once the performance aspect starts to suffer. With that said, I'm going to be putting my wants to the side and focus much more on the community.

MAJOR UPDATE INFO:
It has came to my attention in the last week or so, that the latest builds of MM --- CM13 based --- DO NOT WORK WITH THE INAZUMA R3 and Optimus R6!! It will bootloop indefinetly. Only versions of CM based roms from prior to about 4/10/2016 will work with it. I've read about it on a few other threads, and tested it myself. It DOES NOT work. It appears to be a problem with the Inazuma R3 Kernel (you can view the thread to see a few people saying the kernel bootloops on the latest versions). The developer is apparently aware and is working on a fix.
As far as the 'unable to mount' /data issue, this occurs now and then with flashables. For me, the fix is to reboot twrp back into the recovery. Don't reboot system. Just reboot recovery, then continue to add your selections. The one that does it most often is the PMB SqLite3 database 5.1 --- and thats about 99% of the time. Hence, I install it at the very last.
I want to apologize for the problems that people have been having, many were my fault and I take responsibility for that. Luckily, everything is fixable and you can always return to your previous setup without issue.
AOSP Version 1.0 will be released by Friday evening.
CM13 version 2.0 will be released shortly after, with fixes to all the issues that have been brought up on here. Thank you again for point the problems out, and giving this a try. See you guys soon!

Check this tool >> http://forum.xda-developers.com/moto-g/orig-development/mod-maxopt-battery-saver-tuner-t2955539/ it does miracles to the battery life and multitasking, before flashing put your phone on airplane mode and do a nandroid backup

[Kernel][3.4.113] Chrono Kernel R5.10

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.
*/
Features:
Universal kernel for JB, KK, LP and MM-based ROMs
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.10.y based releases
r5.7.x (LK 3.4.y based releases)
Installation:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Compatibility:
I only add those ROMs that are confirmed to work by me or someone else:
Stock 4.1.2 ROM
LineageOS 11
CyanogenMod 13
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, 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/master
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R5.7.1
Stable Release Date: 1974-11-11
Beta Release Date: 1974-11-11
Created 2018-03-09
Last Updated 2018-04-16

Changelogs and features
Changelog
R5.9.1
Resolved (hopefully) deepsleep issues *
Fixed touchkey not working issue **
* tested in about 24 hours so far with ~6 hours of deep sleep on UltimateROM 6.0.1 without any issues with wakelocks.
** It seems that in r5.9 was introduced a bug - touch keys weren't working (at least, on 6.0.1) after device wake up.
R5.9
Bring up all the latest CK code from Codina kernel
Fix a severe performance issue on r5.8.2 build
BLN is finally FIXED! *
* Apparently, issues with BLN were related to Janice touchkey driver that was putting the device to sleep (when the display is off) regardless of a BLN wakelock usage. Reverting this behavior seemed to enable BLN to work.
R5.8.2
In-kernel vibrator fix for Android 6.0+
R5.8.1
PowerHAL fixes for 4.4.4
Experimental fix for CPU governor issue on 4.4.4
LCDCLK: revert to TeamCanjica kernel implementation
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)
(old changelog)
R5.7.1
Initial build for janice (kernel sources based on LineageOS 15.1 kernel for Codina)
Fixed bluetooth issue on 4.1.2
Squash-reverted GPU-related code logic from CPU governor Dynamic
J4FS module code cleanup
Reverted forcing minimum CPU freq to 800 MHz
Enabled CONFIG_CPUSETS (required by Android 6.0.x+ ROMs to function properly)
Kernel Tweaks:
(GPU/CPU undervolting and related tweaks)
Undervolting the CPU/GPU will bring battery savings but possible instability.
1) to undervolt CPU use ChronoKernel app or via init.d scripts:
Code:
echo *cpufreq* varm=xx > /sys/kernel/liveopp/arm_summary
for example, following sets voltage varm=0x10 for 200 MHz:
Code:
echo 200000 varm=0x10 > /sys/kernel/liveopp/arm_summary
or
Code:
echo 200000 varm-=10 > /sys/kernel/liveopp/arm_summary
(default varm voltage for 200 MHz is 0x1a but, code above sets 0x1a - 0xa(10) = 0x10 )
2) to undervolt GPU use init.d script:
Code:
echo x vape=yy > /sys/kernel/mali/mali_dvfs_config
Example:
Code:
echo 2 vape=0x1c > /sys/kernel/mali/mali_dvfs_config
"2" stands for DVFS idx (look at mali_boost_high/mali_boost_low).
To prevent overriding of such settings by ChronoKernel app, add line to your init.d script after GPU undervolting
Code:
chmod 444 /sys/kernel/mali/mali_dvfs_config
Don't change voltage of both GPU/CPU at the same time - otherwise if you'll get reboot if won't know what it caused. The same is for different frequencies - if you'll change voltage of too many steps you won't know which frequency caused reboot. It's not easy process, though, following method simplifies it: https://github.com/mkaluza/i9070_kernel_CoCore-E/wiki/Undervolting-janice .
3) Custom LiveOPP table.
By default some LiveOPP steps such as 100, 200, 500 ... MHz aren't used. You can re-enable those by following way:
Code:
echo 200000 enable=1 > /sys/kernel/liveopp/arm_summary
Or use CK app instead. Don't enable it unless it uses the same voltage as 400 MHz. The same is for the rest frequencies - until some of them uses same voltage, no point to enable steps with lower freq. I've added 100 MHz just to further make some tests with it once again. It can't use lower varm than 200 MHz - that's why it's disabled by default. Furthermore, not all phones well keep undervoltage, that's why 100-400 MHz steps uses same stock voltage varm=0x1a.
UPD. thanks to @borkins for this nice editor LiveOPP ARM steps: http://forum.xda-developers.com/showpost.php?p=60311291&postcount=2921
(CPU freq management tweaks)
CPU freq. limiter for screen OFF, adjust it via:
Code:
SYSFS=/sys/kernel/cpufreq/cpufreq_limits_on_suspend
echo min=100000 > $SYSFS
echo max=400000 > $SYSFS
echo on > $SYSFS
Too low frequency may cause freezes after wakeup and sound scrathes. If you use Dynamic govermor, it make no sense to use cpufreq limiter, because Dynamic already takes care about CPUfreq usage optimization. For more, read wiki.
Input boost
This feature has been originally written by zwliew.
Not all governors support input boost. Supported governors: ondemand, interactive, conservative, ZenX, lionheart and some others. Dynamic governor has its own boost interface.
Default boost frequency is 400 MHz.
Code:
echo 450000 > /sys/kernel/cpufreq/input_boost_freq # echo '0' to disable
echo 35 /sys/kernel/cpufreq/input_boost_ms
(BackLight Notification)
To configure time intervals of BLN blinking type(bln_ondelay stands for time of blink and bln_offdelay - delay between two blinks):
Code:
echo bln_ondelay=500 > /sys/kernel/bln/blink_mode
echo bln_offdelay=6000 > /sys/kernel/bln/blink_mode
Make sure BLN enabled:
Code:
echo 1 > /sys/class/misc/backlightnotification/enabled
# to enable bln_wakelock.
echo on > /sys/kernel/bln/bln_wakelock
Use /sys/devices/virtual/misc/backlightnotification/blink_mode to changes modes.
Blink modes:
0 = no blinking
1 = blink backlight only
2 = blink backlight + rear cam flash
3 = blink rear cam flash only
(Module autoload)
Now there is a simple way to load modules at boot. Just move needed modules to /system/lib/modules/autoload and reboot device(or execute /etc/init.d/00autoload)
(DDR overclock)
This feature has been developed by me and allows you to improve DDR and GPU performance. Please note, that DDR OC might work unstable and cause filesystem corruption. Though, DDR clock of 975 MHz has been highly tested and should work fairly stable on most devices.
Overclocking DDR over 975 MHz is highly NOT recommended, especially in case if you not sure that you can deal with possible consequences.
How to OC DDR:
1) by using
this script .
2) by using Terminal Emulator(in example below 975 MHz):
Code:
echo 0x5017f > /sys/kernel/liveopp/pllddr_oc_on_suspend
This setting will be applied right after disabling screen.
(Minimum APE/DDR OPP on screen on)
This feature has been developed by me and allows to set minimum APE/DDR OPP states which are used when screen is ON. APE controls many systems such as an image, video, audio system etc. DDR OPP determines performance of DDR. Default values are APE50 and DDR50. Lower states(APE25/DDR25) reduces power consumption, but may cause graphical glitches like screen blinking or filling it by vertical grey lines. If you don't have mentioned effects, it's recommended to use APE25/DDR25:
Code:
echo ddropp=25 > /sys/devices/pri_lcd_ws2401.0/mcde_screenon_opp
echo apeopp=25 > /sys/devices/pri_lcd_ws2401.0/mcde_screenon_opp
* if you don't have folder /sys/devices/pri_lcd_ws2401.0, use /sys/devices/pri_lcd_s6d27a1 instead.
(Screen refresh rate)
This feature has been developed by cocafe and modified by me. Lower lcdclk frequency cause less power usage, but too low values makes system unusable.
Following command allows to change screen refresh rate:
Code:
echo x > /sys/kernel/mcde/lcdclk
use
Code:
cat /sys/kernel/mcde/lcdclk
to see supported lcdclk modes. Default mode is 60 Hz which is recommended in most typical cases. If you've screen tearings, blinking etc. change resresh rate mode to "60+ Hz":
Code:
echo 0 > /sys/kernel/mcde/lcdclk
(ABB charger tweaks)
added tweakable interfaces for termination current. To adjust it type(just an example):
Code:
echo 90 > /sys/kernel/abb-chargalg/termination_curr_1st
echo 70 > /sys/kernel/abb-chargalg/termination_curr_2nd
curr_2nd should be less or same as curr_1st. Lower values prolongs battery lifetime, but also slows battery charging.
Default values are curr_1st == curr_2nd == 150 mA. Please note, too low values maybe aren't usable.
(Dynamic FSync)
This feature has been developed by Faux123 and allows to dynamically manage the synchronous writes performed on file system (FSync).
It uses asynchronous writes when the screen is on, instead of synchronous writes, to have better performance and a slightly lower battery drain, while when the screen is off the synchronous writes are re-enabled to flush all the outstanding writes and prevent possible data loss.
How to enable/disable the Dynamic FSync (default enabled):
1) By downloading and using Trickster MOD
2) By directly editing the file /sys/kernel/dyn_fsync/Dyn_fsync_active and setting 1 to enable the dynamic fsync, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic fsync feature
Code:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
- Or run this command to re-enable the dynamic fsync feature
Code:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Click to expand...
Click to collapse
(Software CRCs)
Disabling software CRCs gives you a slight bump(10-30% is what they say) of MMC performance, at the cost of a possibility of your Ace 2 freezing randomly.
Code:
echo 0 > /sys/module/mmc_core/parameters/use_spi_crc
Click to expand...
Click to collapse
(Dynamic dirty page writebacks)
This feature has been developed by Christopher83 and allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off.
It is based on a commit of Francisco Franco, but instead of using hard coded values and of disabling at all the dirty page writebacks while the screen is on (possibility of data loss).
By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
How to customize the dynamic dirty page writebacks feature (default disabled):
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
1) By directly editing one of the file written above inside /proc/sys/vm and setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic dirty page writebacks feature
Code:
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
- Or run this command to re-enable the dynamic dirty page writebacks feature
Code:
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
- Run this command to set customize the two intervals (30 seconds while the screen is on, 10 seconds when the screen is off)
Code:
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs
(Tweak app)
ChronoKernel settings
Thanks mars_army for this app!
Bug reports:
after experiencing a random reboot, type in terminal:
Code:
su
cat /proc/last_kmsg > /storage/sdcard0/last_kmsg.txt
report it in the thread and attach the last_kmsg.txt

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.

@ChronoMonochrome
I tested "chrono_kernel_r5.7.1-test-40-g169a68f4f29d-janice.zip" on Lineage OS 11.
Result: I have the same hiccups in the youtube video like before.
I think that you can revert the LCDCLK frequency to the default 60 Hz value, because I didn't notice any significant difference.
And I had an isolated crash while I was navigating in settings.
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone, Naked Browser, Titanium Backup, Fx File Explorer, Gmail, Google News & Weather, MX Player.
I hope that these logs can help you.

isaak said:
@ChronoMonochrome
I tested "chrono_kernel_r5.7.1-test-40-g169a68f4f29d-janice.zip".
Result: I have the same hiccups in the youtube video like before.
I think that you can revert the LCDCLK frequency to the default 60 Hz value, because I didn't notice any significant difference.
And I had an isolated crash while I was navigating in settings.
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone.
I hope that these logs can help you.
Click to expand...
Click to collapse
Thanks for the report! Unfortunately, the last_kmsg log appears to be taken from MaxiCM kernel, so the crash isn't captured here. In the meantime I'll install some of those apps to test how it goes under increased memory pressure. Was /proc/meminfo log taken before or after reboot? It would be useful to check this sysfs interface when the phone is encountering laggs (if it does), but after reboot this info won't help. About lowmemorykiller changes: were apps running faster / slower? So far Youtube playback is the only issue or phone laggs too?

ChronoMonochrome said:
Thanks for the report! Unfortunately, the last_kmsg log appears to be taken from MaxiCM kernel, so the crash isn't captured here. In the meantime I'll install some of those apps to test how it goes under increased memory pressure. Was /proc/meminfo log taken before or after reboot? It would be useful to check this sysfs interface when the phone is encountering laggs (if it does), but after reboot this info won't help. About lowmemorykiller changes: were apps running faster / slower? So far Youtube playback is the only issue or phone laggs too?
Click to expand...
Click to collapse
/proc/meminfo log was taken before the reboot. Youtube playback is not the only issue. I can just say that the best way to reproduce a crash or a slowdown is switching from an app to another as quick as possible and/or try a cleaning with CCleaner. Ah, in that list I forgot some apps, so I've updated my previous post.

So far I've tested as much as possible on stock 4.1.2 rom and everything is working fine.
-Bluetooth is definitely fixed, working like a charm.
-CRC, FSYNC and other tweaks give me no issue at all and work good.
-Tested a bit of undervolting, firstly cpu, then gpu, and DDR OC, and here too, no problems.
-Really great the supension min and max cpufreq, tested it with some init.d scripts.
Overall stability and responsiveness of the system is impressive, really positive, you really made a big surprise
These instead are the few things I noticed not working, I think the first two are really not a major problem at all and maybe I am messing with something:
1. I have noticed that trying to set governor by init.d script doesn't seem to take effect and at boot completed I find performance setted as governor:
busybox echo dynamic > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
Click to expand...
Click to collapse
Running then the script manually set dynamic as governor correctly.
(SOLVED WITH A BUSYBOX CHMOD COMMAND BEFORE EVERY PARAMETER SET)
2. I tryed using exfat support, loaded fuse.ko and exfat.ko modules on boot, then used the same binary from cocafe twrp kernel I was using fine (and here I think there is the issue) with this command:
exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard;
Click to expand...
Click to collapse
Sdcard isn't recognized and android is asking to format it as usual.
3. I guess should be the number one: Recovery doesn't seem to work, tryed many times, also removing battery first, but I can't enter in recovery. Next time I flash kernel I will do it manually from terminal, or Universal Kernel Flash app
EDIT1:
I found that the path where lcd parameters are located would be:
/sys/kernel/s6e63m0/panel/lcd_clk
Click to expand...
Click to collapse
instead of:
/sys/kernel/mcde/lcdclk
Click to expand...
Click to collapse
EDIT2:
Seems like deepsleep is broken, because in my situation phone doesn't enter in deepsleep mode and having a look at /d/supsend_stats and d/suspend directory confirm my issue.
I found at first strange the absence of /d/cpuidle directory and so the deepest_state configuration file, like something is missing here.
EDIT3:
I think I found another last issue, BLN is not working, but I think could be again something to do with files and folder structure, for example I can't find:
/sys/class/misc/backlightnotification/enabled
Click to expand...
Click to collapse
Again, this is still something not so important tough
EDIT4:
I was experiencing before issues with phone calls, making phone app freezing and signal loss, going to "no service" mode. Had to flash backup kernel for now, tomorrow as I get some time again I will provide logs

Pdevo said:
So far I've tested as much as possible on stock 4.1.2 rom and everything is working fine.
-Bluetooth is definitely fixed, working like a charm.
-CRC, FSYNC and other tweaks give me no issue at all and work good.
-Tested a bit of undervolting, firstly cpu, then gpu, and DDR OC, and here too, no problems.
-Really great the supension min and max cpufreq, tested it with some init.d scripts.
Overall stability and responsiveness of the system is impressive, really positive, you really made a big surprise
Click to expand...
Click to collapse
Thanks for a review!
2. I tryed using exfat support, loaded fuse.ko and exfat.ko modules on boot, then used the same binary from cocafe twrp kernel I was using fine (and here I think there is the issue) with this command:
Sdcard isn't recognized and android is asking to format it as usual.
Click to expand...
Click to collapse
Honestly I didn't test exfat for a long time. These issues might come due to the filesystem driver updates. Anyway I need to test things myself before I'll have clues on how to fix it.
3. I guess should be the number one: Recovery doesn't seem to work, tryed many times, also removing battery first, but I can't enter in recovery. Next time I flash kernel I will do it manually from terminal, or Universal Kernel Flash app
Click to expand...
Click to collapse
Are you sure you have followed the installation guide to flash the kernel? Especially, using TWRP is required to flash a kernel (other recoveries aren't tested and can be a cause for a bugs) I was returning to a stock for a short time to test if bluetooth works and recovery was working for me when I was returning to UltimateROM 6.0.1 afterwards.
Don't use manual flashing or UKF app to flash the kernel! The installation method is quite complicated (compared to installation of other kernels), so a full and proper installation is only possible if you flash it from recovery.
EDIT1:
I found that the path where lcd parameters are located would be:
instead of:
Click to expand...
Click to collapse
I have moved the interface to match the implementation of LCDCLK management on codina.
EDIT2:
Seems like deepsleep is broken, because in my situation phone doesn't enter in deepsleep mode and having a look at /d/supsend_stats and d/suspend directory confirm my issue.
I found at first strange the absence of /d/cpuidle directory and so the deepest_state configuration file, like something is missing here.
Click to expand...
Click to collapse
This is entirely possible due to deepsleep driver changes in a kernel. I never tested if it works on stock, I guess I'll have to return to stock once again.
EDIT3:
I think I found another last issue, BLN is not working, but I think could be again something to do with files and folder structure, for example I can't find:
Again, this is still something not so important tough
Click to expand...
Click to collapse
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?

Yes sir, I flashed your kernel exactly from twrp, coming from cocore refresh24, I referred to UKF or terminal emulator to say I would use that method now that I can't enter recovery mode, but I never use these ways at all, always from recovery, because I know that kernel come with scripts and other files that without recovery wouldn't be installed
Tomorrow I will do further testing

ChronoMonochrome said:
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?
Click to expand...
Click to collapse
As far as I know no dev on Janice introduced BLN, but I don't see any reason why it shouldn't be technically possible if it works on Ace II.
Please don't give up on this unless you're sure at 100%.
@cocafe had it on his todo list, but at the end he didn't implement it for unknown reasons. I asked to him but he never explained it.

ChronoMonochrome said:
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?
Click to expand...
Click to collapse
Until now, BLN never been working or supported on custom and stock roms, as said by @isaak, the reason behing that I think is properly known by developers such as cocafe.
Yesterday I made a little try using the commands you point in the thread, a little go, but in fact is not working. Would be a cool feature, but nothing so important at all for me, at least for now
UPDATE:
I flashed again the kernel, starting from freshly downloaded zip, and I got an infinite bootloop trying to get to recovery, the only way to go back working was flashing stock rom with odin.
I can now safely say there is an issue with recovery using the stock rom.
UPDATE 19:30
I took two logs, one for incoming call and one for outgoing call, reproducing the issue I was referring in previous post.
In the first case, incoming call, notification appear but scrolling to accept call make phone unusable and I could just shutdown it to solve the situation.
In the second case, outgoing call, after I start the call the phone app isn't responding, I see the notification widget but tapping on every possible button, to terminate call or enter in dialog, doesn't work and phone is very unstable until a sort of a timeout is running out and call stop itself.

Hi @ everyone!
Because of th numerous issues found with the current release, I'm starting to work on a fresh kernel sources (3.0.101), almost from scratch. My primary focus for now will be a multitasking, that is the main issue with the current release. Because of yet unknown root cause of the issue it could take a while to reveal it, but I hope to release a new build these days (and after playing with some kernel configuration find out more appropriate one for a multitasking). Stay tuned!

For sure we stay tuned!, thank you so much for the efforts and take all the time you need Chrono

isaak said:
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone, Naked Browser, Titanium Backup, Fx File Explorer, Gmail, Google News & Weather, MX Player.
I hope that these logs can help you.
Click to expand...
Click to collapse
I have set up all these apps about 10-12 days ago. I should say, removing CCleaner seemed to help a lot to increase the phone performance. It's doing a lot of background CPU and I/O work, making the phone almost unusable on r5.7.1 and severely affects performance on r4.1 / r4.6.

ChronoMonochrome said:
I have set up all these apps about 10-12 days ago. I should say, removing CCleaner seemed to help a lot to increase the phone performance. It's doing a lot of background CPU and I/O work, making the phone almost unusable on r5.7.1 and severely affects performance on r4.1 / r4.6.
Click to expand...
Click to collapse
The new CCleaner version is on the heavy side, so I had to freeze some background services with My Android Tools app. Anyway I've just uninstalled it definitively.

New build r5.8 is up!
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)

ChronoMonochrome said:
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)
Click to expand...
Click to collapse
I tried 5.8.5 and I have still issues with LineageOS 11:
1) 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, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
2) There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline.
- There is still a bug with max clock value of Dynamic governor (I can reproduce it with ZenX governor too). I set it to 800 MHz, I go back to the settings screen, then I return to the Performance -> Processor section to check if the 800 MHz value is maintained. But the UI automatically restored the max clock to 1000 MHz without my consent.
For your information, these issues occur only randomly and with particular combinations. So, if you can't reproduce them, the best way 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.
"Set on boot" options are correctly set for both Processor and I/O Scheduler.
And I keep "Enable per-app profiles" option turned off.
3) On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
PS: I would appreciate if you could update the installation steps in this thread with the same steps of the refresh topic:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip

isaak said:
I tried 5.8.5 and I have still issues with LineageOS 11:
1) 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, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
Click to expand...
Click to collapse
Sorry, I thought I've reverted this change. Can you confirm that setting old LCDCLK freq fixes issue? As a temporary solution you can use init.d script to set the appropriate LCDCLK freq index.
2) There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline
Click to expand...
Click to collapse
Can confirm now. I have a guess for that, for now the solution as follows:
remove /ramdisk/modules/autoload/sioplus-iosched.ko, reboot. I have to test this a bit more time to be sure 100%, but so far I couldn't reproduce an issue after removing this module (no other CPUfreq governor or I/O scheduler must be loaded as well).
- There is still a bug with max clock value of Dynamic governor (I can reproduce it with ZenX governor too). I set it to 800 MHz, I go back to the settings screen, then I return to the Performance -> Processor section to check if the 800 MHz value is maintained. But the UI automatically restored the max clock to 1000 MHz without my consent.
Click to expand...
Click to collapse
It's not a bug, but rather intended behavior - due to PowerHAL changes implemented, CPUfreq can only be changed via script (see /ramdisk/perf.sh). I've previously asked if anyone would prefer to adjust CPUfreq usual way, In this case I can just remove the corresponding lines from the PowerHal script. This will make PowerHAL settings a bit more useless, but will gave easier control over CPUfreq.
3) On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
Click to expand...
Click to collapse
The script actually works, though you're right, it works buggy and everytime shows the default profile (you can set, e.g. Powersave profile and check min/max CPU freq, to check if it actually works).
PS: I would appreciate if you could update the installation steps in this thread with the same steps of the refresh topic:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Click to expand...
Click to collapse
Done!

isaak said:
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, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
ChronoMonochrome said:
Sorry, I thought I've reverted this change. Can you confirm that setting old LCDCLK freq fixes issue? As a temporary solution you can use init.d script to set the appropriate LCDCLK freq index.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, I can confirm that setting old LCDCLK freq fixed the flicker issue for my screen. I think it would be better to set it as default in the next release.
isaak said:
There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline
etc etc....
ChronoMonochrome said:
Can confirm now. I have a guess for that, for now the solution as follows:
remove /ramdisk/modules/autoload/sioplus-iosched.ko, reboot. I have to test this a bit more time to be sure 100%, but so far I couldn't reproduce an issue after removing this module (no other CPUfreq governor or I/O scheduler must be loaded as well).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I tried your steps, unfortunately they didn't work for me.
ChronoMonochrome said:
It's not a bug, but rather intended behavior - due to PowerHAL changes implemented, CPUfreq can only be changed via script (see /ramdisk/perf.sh). I've previously asked if anyone would prefer to adjust CPUfreq usual way, In this case I can just remove the corresponding lines from the PowerHal script. This will make PowerHAL settings a bit more useless, but will gave easier control over CPUfreq.
Click to expand...
Click to collapse
Personally I would prefer more control over CPUfreq. Could you list the main advantages to limit CPUfreq changes only via script? Is it a sort of auto-optimization? This point is not clear to me. If you think that any change to this mechanism would affect negatively the battery life, then don't change anything.
isaak said:
On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
ChronoMonochrome said:
The script actually works, though you're right, it works buggy and everytime shows the default profile (you can set, e.g. Powersave profile and check min/max CPU freq, to check if it actually works).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I tried Powersave and Performance profiles, in both cases the maximum freq varies between 400 MHz and 1000 MHz, rarely reaching 800 MHz. Minimum freq is always 200 MHz and it doesn't change visually like the maximum freq. Balanced profile is always shown visually after a reboot.

isaak said:
Personally I would prefer more control over CPUfreq. Could you list the main advantages to limit CPUfreq changes only via script? Is it a sort of auto-optimization? This point is not clear to me. If you think that any change to this mechanism would affect negatively the battery life, then don't change anything.
Click to expand...
Click to collapse
Because of some CPUfreq scaling tunables were changed (in the case of Dynamic governor), it makes sense to implement a PowerHAL profiles, which would limit / restore the max CPUfreq. But I think I've found a solution - I will make it possible to change CPUfreq for a Balanced profile.
I tried Powersave and Performance profiles, in both cases the maximum freq varies between 400 MHz and 1000 MHz, rarely reaching 800 MHz. Minimum freq is always 200 MHz and it doesn't change visually like the maximum freq. Balanced profile is always shown visually after a reboot.
Click to expand...
Click to collapse
Ok, I found some logical errors in the script, should be fixed in upcoming release.