Database Users

[HowTo] Tweak your Archos

Hi,
recently i came upon a thread with someone asking :
how to optimize the archos to be quicker ?
As this is propably a question many people might ask (even I still do ) I thought about creating a thread about. This is not just to answer his question but also for all u nerds out there to corrent me - as I might be wrong in some points AND to gather new options to speed up the device. This is what i have learned yet...
Anyway all of the things I list here require root as far as I know. So get your device rooted or abandon the Thread
ALL THINGS IN THIS THREAD ARE WITHOUT WARRENTY - SO IF YOUR DEVICE STARTS MUTATING INTO A DOG HUNTING YOUR ASS FOR NEW FLESH - BE WARNED
Memory Management:
Introduction: HAVING FREE UNUSED MEMORY ON ANDROID HAS (nearly) NO ADVANTAGE (exception having 0 memory also fu**s up the device -> 1. )
All of those methods wont make your device faster in the meaning of really getting faster in speed... as android already has a quite good memory management.
BUT if u get more space in memory your device can keep more of the apps U LIKE in memory (being inactive according to app lifecycle). This will make them get called faster next time u use them and your device will "feel" faster and more responsive.
1. What should work on all roms are the "minfree" settings -> meaning when android really kills apps - depending on free memory (if u don't know what is mean by - search for the "App Lifecycle" of android)
You can try setting those to the values mentioned by sibere (scroll down) or try finding your own settings. There for u can use any app like "AutoKiller Memory Optimizer" just serach "memory optimizer" in the market.
KEEP IN MIND - you may play a bit with those settings - BUT still u should know what u are doing if u use it!
LOW: If u set the values to low the device will kill apps very late keeping much of them in memory this might make you device get slow. If there is too less Memor fo a "new" app or another process just need more memory while running it has to close down other processes before memory can be allocated.
HIGH: If u set em too high u kill most apps instantly - and your device will get problems and might get unstable as far as i understood.
2. Try gettign more "free" memory by disabeling services - as those got the highest priority they wont get killed that fast by the memory management. For checking u might get an app like "TaskManager" wich lists all running processes.
Just check out what takes your memory and disable those u dont need.U can disaable them by using "Titanium Backup" disable app / uninstall em / or just uncheck their autorun by using a programm like "Autorun Manager". Remember if u just disable the autorun they might (re)start later still.
3. Use a low sceen count in your launcher and keep the widget count low. This is related to 2.) as most widgets run a "background service" to update itself / pulling information (e.g. a waether widget getting latest conditions, a calendar widget keeping connection to your calendar app,...) - each widget took at least 8MB memory when i checked with TaskManager - "greater" widgets like "Fancy Widget (sense like clock and weather widget)" sometimes take up to 25MB
4. DONT USE A LIVE WALLPAPER (live wallpapers use MUCH memory most 20MB-40MB - either they get closed down all the time - or they just reside in memory taking the memory u wanted to use for keeping other apps active)
I also noticed that the App Drawer got "much/noticeable" slower in every Laucher I tested while a live wallpaper was active
5. DO NOT USE A TASK KILLER (remeber the introduction!!! - and think about it yourself - if at least 20 ppl ask why - i write this down here )
6. SWAP / COMPCACHE (can be activated through UD config) - this is a really hard question - those methods extend your memory but the memory u gain is MUCH slower then the internal memory. So again u have to decide and try out if it helps u or it doesn't (I used em long time but never realy felt a big advantage of. Compcache even made my device feel slower and i got more FC's most time - also I tried to figure out how the memory management uses this "memory". But i din't find a clear answer yet - as some ppl mentioned that "inactve apps" wont get swapped - need some clear source... Anway in general those 2 should increase Multitasking capability at cost of speed.
7. FUDGESWAP
- noting yet - its GINGERBREAD only - so we have to wait...
FINALY: u have to decide on your own what u really NEED to run "simultaniously" (I personaly rather have less widgets and run background services like growl, eventghost, tasker) but u can count it yourself by checking back with taskmanager and having in mind your archos (GEN8) just has 256MB of internal memory.
CPU Manaagement:
8. (UD) If u got Urukdroid u can try setting your CPU Governor to another value like:
"Interactive" is more reactive than "on demand" (-> SIBERE)
9. Try an OC (OverClocked) Kernel -> get it in the Urukdroid Dev Thread (I wont link any here as u should know what u do and wich u choose!)
BEWARE not all devices can use an OC Kernel (sadly mine can't) but try it out...
10. Try overclocking your device with the Milestone Overclock Utility. This overclock method is based on a module insert. Again this just works with root.
OVERCLOCKING:
Each CPU is different -> each device is different and can handle different maximum speeds - this is related to the former position of the CPU on its waver while production...
So u have to try out what your CPU can handle safely - so it might happen your device will refuse to boot after u flashed a kernel or set some permanen OC values. Keep a BACKUP or reflash old kernel...
In general u normaly can't brick your device by overclocking as the CPU overheats -> safety function of the CPU stops it -> the device resets itself before the CPU get "burned" (hope this also aplies to ARM processors )
Other:
11. The Launcher: I tested out much lauchers already: ADW, ADW EX, VTL, Laucher PRO, Zeam Laucher, GO Laucher - most of them seem to be eaqual in speed and more differ in features (event Laucher PRO is still the fastest on my Wildfire [but development stopped some time ago], GO seemed to be a bit slower imho) - take any of those but avoid taking some over exagerated 3D'ish laucher like Regina, SPB Shell, Claystone...
12. Apps like "AutoKiller Memory Optimizer" have additionaly features to "optimise" the speed,... u might test those out but I didnt notice a difference most time. Still keep in mind - u should know what u are doing
13. Ok - u may want to hit me for that:
It's more a cosmetic thing - but I recently used UOT Kitchen for theming my framework and used the fly-in animations - and they feel much faster then the default animations just try it out... keep a backup of your original framework for reverting.
All the following Tweaks are mentioned by sibere (credits go to him and propably some other people)
echo "1536,2048,4096,6144,8192,10240" > /sys/module/lowmemorykiller/parameters/minfree
(this is related to 1. ; 1MB = 256 => valueas above are 6MB, 8MB, 16MB, 24MB, 32MB, 40MB)
to enable cgroups cpuacct:
mkdir /acct
mount -t cgroups -o cpuacct none /acct
mkdir /acct/uid
to change ioscheduler:
cd /sys/block/mmcblk1/queue
echo "deadline" > scheduler
cd iosched
echo 1 > fifo_batch
These are lost on reboot so if you wanna keep them, add a script to /etc/init.d
Finaly I also have patched the sqlite library. If you want the file, let me know. It boost a lot SQL database writings. See this thread http://forum.xda-developers.com/showthread.php?t=903507
Click to expand...
Click to collapse
Will ask him to comment on "cgroups, ioscheduler, and sqlite" as im not sure if they work with all rom versions / neither how they work exactly.
THANKS Sibere
EDIT:
aditional threads with tweaks
- Supercharger
- http://forum.xda-developers.com/showthread.php?t=1227269
BEWARE I HAVEN'T HAD THE TIME TO CHECK THEM OUT YET AND DIDN'T TEST THEM
SOME OF THEM MIGHT NOT WORK AND PEOPLEARGUE ABOUT THEM (e.g. the "debug.sf.hw =1" is heavily discussed)
IF ANYONE KNOWS MORE ABOUT THOSE OR CAN HELP TESTING IM HAPPY TO LEARN MORE ABOUT

Hi.
For a full reference to cgroups, you may read the cgroups documentation from the kernel.
Basically, it provides process aggregations in the Linux kernel, mainly for resource tracking purposes.
deadline IO scheduler has been used a lot for SSDs and proven to be quite adapted to flash memory.
The minfree settings set here are pretty much optimised by me for the archos. It gives you a good balance between available cache and free ram . Android starts to complain when the free ram drops below 32Mb. with these settings, the OOM task killer will try to maintain a free ram level above 32Mb. You DON'T need a task killer. It will just use precious ram resources and will mess up with the android integrated task killer.
Those settings are reset on boot, so you may add them in a script added to /etc/init.d/ directory.
SQlite optimisation is of great help and I already posted a lot of information about it when I posted the tweaked file. Please refer to this post. (You'll have to look for it, it's somewhere in the dev thread )
Enjoy your optimised archos!

Thanks guys, learning new tips.

Nice! Good tips. Thanks.

Very usefull reading, thanks!

thanks for the tips ! cheers!

Hello, I am JustLoveJoy, I am an up and coming developer, although I work very hard on my phone right now, my gf has gotten an Archos 8 G2 4GB tablet and I have it rooted but it constantly gives me some issues. Finding this thread, I have to ask, can these or any tweaks be applied to her tablet? is there any source code on github or somewhere else? I mainly wish to get her to be able to do her Farmville on it. I'd like to get on to the development boards with a custom rom for it but I need someone with a little experience to point me in the right direction for that. Thanks So much for starting this thread!

hi i just want to try to root my arnova 7g2 bit i don't find a straight 3d on xda. you clan indicate the right street
Inviato dal mio GT-N7000 con Tapatalk 2

did you notice that crow (CM7) for Gen8 was released ?

still nothing for developing for the Archos 8 G2 4GB? If I can get adb shell I would be happy!

Thanks

thinks man
:good:

Thanks for the great post! I still have one of these!

Speed up your i9000 Tips Compilation

Hi everybody!
As i am pretty mad about the slow responsiveness of my i9000, i would like to have everybody to tell the world some tips to help each other in making this phone faster.
My tips:
Use KitKat, Slimrom if possible (SlimKat weekly)
Install mackay kernel, or his bigmem libs.
Use ES Task Manager to remove autorunning apps.
Even like this, i get slowness after a couple of days of use.
What are your tips ? Is it responsive ?
Cheerios!

Ok right now working faster with slimkat latest versión with semaphore Ruth live OC 104% and sd card read ahead at 1024.
Waaay smoother.
I hope it keeps like this a couple of days
Enviado desde mi GameBoy Color

nice to know that :laugh:

Interesting topic :good:
Here's my tips:
ROM: Gamerzrom 4.0, altough I think "Mackay ICS 2014" it's the faster but it lacks some features as quick sms;
Kernel: "Devil4.3_galaxysmtd_20131022" with the following settings: Scheduler: SIO; dynamic fsync: off; governor: ondemand; min freq: 400MHz and max freq: 1000MHz; no OC; deep idle: off; smooth ui: on; sampling rate: 30000; up threshold: 50%; sampling down factor: 4step; eraly demand: off; RAM: 395mb; no zRAM; no swap; no KSM; (most of this settings are the default from gamerzrom)
Other settings: 16bit transparency: on; dithering: color band fix only;
Apps that help: "seeder 2.0" (rng service performance profile: light) and "greenify" (hibernate all apps except launcher and seeder);
Frozed apps with titanium backup: DSPmanager; ES file explorer; videoeditor; terminal emulator; trebuchet;
Launcher: Apex;

Ill try those settings and report back!
Enviado desde mi GameBoy Color

well my phone is lagging as hell too.Maybe ICS is the only solution to our problems?!?
I ve tried many 4.2 ,4.3 and 4.4 roms but after a month of use they all end up lagging even without any extra apps installed.
Can i install ics on top of kitkat or do i need to install gb stock first with odin?

Installing ICS on top of KK will cause bootloop. I think you need to flash GB with Odin (XWJVZ i.e.) then root it with Semaphore or CF-Root kernel. Then finally you can flash any higher Android builds by CWM. I prefer Mackay ICS 1.7. IMO the ROM with best performance. Good luck.
Wysłane z mojego GT-I9000

I don't know what's wrong with either of you people, but my i9000 is on KK 4.4.2 OmniROM Nightlies running alongside Semaphore 3.4.3s with Bigmem enabled (396 MB off and 408 MB on). Everything else is in my signature tab. Also, I've got 42 user apps in my phone (120 odd in total) but still smooth as butter.
Also, in Antutu I score 5400 without OC and 5900 at 110% Live OC.

For Smooth Kitkat on Galaxy i9000. Includes some basics as well.
1. Install Slimkat Weekly
2. Install Minimal Gapps (if required)
3. Remove Unnecessary System Apps with Slimsizer
Browser.apk and Chromebookmarksyncadapter.apk --> replace with lightweight browser eg. Lightning, Puffin or Naked browser
Gmail.apk, Email.apk and Exchange.apk --> Replace with K9Mail (OR keep just Gmail and forward everything from your Exchange Email)
Gallery.apk --> replace with lightweight gallery e.g. Quickpic (Camera still works fine)
Hangouts.apk --> Use normal messaging app
LatinIME.apk and UserDictionaryProvider.apk --> Replace with Swiftkey or Swype
NovaLauncher.apk --> replace with lightweight launcher e.g. Smart Launcher 2 (AND remove all animations from Launcher Settings)
Livewallpaperspicker.apk, phasebeam.apk, phototable.apk, visualizationwallpapers.apk --> Don't need fancy live wallpapers, otherwise get new phone
OTHERS that are safe to delete and you probably don't need (e.g. BasicDreams.apk, CloudPrint2.apk, Dashclock.apk, DSPManager.apk, HTMLViewer.apk, Music.apk, SlimIRC.apk, SoundRecorder.apk)
4. Get rid of animations. Go to Settings --> Developer Options and set 'Window Animation Scale' and 'Transition Animation Scale' to OFF. And set 'Animator Duration Scale' to 0.25x (to prevent the dialer keypad glitch).
5. Install Semaphore Manager from Playstore, then ensure LiveOC is 105%, Ondemand governor, Minimum 105Mhz, Maximum 1050Mhz, NOOP scheduler, and Bigmem is ticked (before reboot you must go to camera and ensure video is on 480p else it will force close on 720p)
6. Install Xposed Installer --> Add Bootmanager (highlight anything that don't have widgets or u don't need notifications from), and Greenify (hibernate anything that don't have widgets and u don't need notifications rom. Also, do not hibernate keyboard)
7. Wifi Advanced Settings --> Untick Scanning Always Available. Also ensure Location is on Battery Saving. Switch OFF Wifi, Bluetooth, and Location when you dont need it.
8. Settings --> Sound --> Untick Vibration on Touch and Touch Sounds (Also do this in your Keyboard Settings)
9. Accounts --> Untick syncing of items you dont need (e.g. Only tick contacts and gmail)
10. Settings --> Advanced Options --> MediaScanner behavior on boot --> Do Not Scan Media
11. Only install/restore apps you use frequently. Other Backup-Uninstall with Titanium Backup and Restore when required.
12. Keep widgets to a minimum
13. Restart your phone daily

Currently put CyanAOSP on an i9000 and it's running great. Overclocking to 1200Mhz seems to cause crashes though.
Switch kernel perhaps?

Currently on CM11 M5 snapshot with Semaphore 3.4.3 kernel, and its buttery smooth so far. M6 snapshot is giving UI crashes
OC Min @ 240 MHz and Max @ 1200 MHz, no crashes. SmartassV2 Governor, Smooth UI on, NOOP Scheduler, bigmems off, Deep Idle off, Touch wake on 30 sec

i ve just formated my phone back to stock 2.3.6 jw7 and root it with cf-root.I just cant believe how much smoother and faster gb is!

You guys should try the OmniROM+Neo Kernel Combination. You'll love it
PFFFFFFFFFFFFFFFFTTT, sent from my i9000

I prefer ICS, too, although it has more bugs than JB or KK...
It is not perfect, but in general useable!

Do not use the phone's features for performance. I think it's entirely relevant to the developer. With the rest of the kernel can handle.
Sorry bad English.

Up! Has anyone still use this phone and with a ROM? So yeah, how is it? Is there any tutorial of it?

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

[ROOT] Advanced Tuning

This thread is for the fortunate subset of 5th Gen Fire devices that are rooted and rocking a custom ROM. It should also work on rooted FireOS (5.3.1 and below) that have both ads and OTA updates blocked.
There have been numerous posts regarding uneven performance while multitasking along with sluggish response after waking the device from a long slumber. Most recognize this is due to excessive swapping associated with limited user addressable RAM. While there are a number of incremental 'tweaks' that can marginally improve this behavior my objective was to realize a more substantial improvement with minimal effort, knob turning and side effects. To date I have realized the benefit (minimal lag; responsiveness approaching devices with twice the RAM; woohoo!) but still working on the automation that will make it largely transparent. Lacking the time to work on the latter I thought it best to toss out the high level config and let others, if interested, work through both validation and implementation details.
As an aside, I have used the same technique on a 2nd gen HD running CM 11 that had been shelved for many months due to the same issues. It now hums along at a respectable pace and is once again a joy to use.
The secret sauce is simple: expand zram space allocation and add a small, secondary swap file in a normally unused location in permanent storage.
Tools (or adb/shell/terminal commands for those with furry chests):
- EX Kernel Manager (EXKM) or other tool/technique that can manage zram parameters (note: I find current builds of Kernel Adiutor too unstable for this work)
- Apps2SD Pro or other tool/technique that can create/manage traditional swap files and swap space priorities
- BusyBox Installer (v1.27.2+) or other tool/technique to insure startup scripts are properly executed
- L Speed (optional) - for ease of implementing a few discretionary performance tweaks
- DiskInfo PRO (optional) - visualize partition utilization
- RAM Truth (optional) - simple app to visualize RAM utilization
Technique (highly abbreviated):
- boot device to rooted ROM; install above tools or equivalents
- use EXKM to resize zram to 128 MB (note: zram must be temporarily disabled)
- use Apps2SD to:
* add a static, 128 MB swap file in the cache partition which remains largely unused with custom ROMs
* important: reassign swap file priorities (button at top right): 0 for the static file; 1 for zram
* increase swappiness to 100 if necessary (EXKM can also be used to set swappiness and other VM parameters)
* verify both swap spaces are enabled via sliders​
Note to geeks: I understand how swappiness, vcache pressure and other virtual memory tunings really work; let's not debate that here. Same with the merits of running a static swap file in combination with zram or the 'dangers' of placing that file in the volatile cache partition. We're talking a hand held device with very modest resources...not the server room with a 99.9x SLA. Yes, zswap would be better. However ...
Optional tweaks:
- use EXKM or L Speed to set LMK parameters to: 24, 32, 40, 48, 56, 64
- use EXKM or L Speed to set write deferral (aka 'laptop mode') to 5 sec
- toggle KSM off/on in L Speed (sets performance enhancing parameters)
- with zram disabled enable zram tweak in L Speed which will establish a 96 MB space along with other optimizations; I find the smaller size ideal for my workflow; YMMV zRAM size can be set with EXKM or another kernel manager.
Challenges:
While the options exist none of the tools noted above can reestablish custom zram space or automatically create a static swap file on boot. I believe this is a kernel issue but have not ruled out interference by Lineage 12.1 which is the ROM I have been testing with. Unfortunately, I lack the time (and quite frankly motivation) to toss Nexus or another ROM on to a spare device to verify the culprit. I might do a bit more testing my my HD 7 which uses a different kernel and ROM. --> Turns out an old version of BusyBox was the culprit; updating to 1.27.2 solved the problem allowing the suggested configuration to be automatically reestablished on reboot. I added my favorite BusyBox installer to the prerequisite tools.
Another issue is the potential for maintaining 'stale' annon pages in zram for a period of time but that's a left field item that probably won't effect most users. A quick fix is occasionally swiping away all apps.
Provide discussion/feedback in this thread. I may or may not respond depending on available time. I love a deep dive (shared above) but once the goal has been reached my interests move elsewhere.
Edit: struck-out references to L Speed after developer/maintainer acknowledged "cooperation" with Kingo Root team (borderline malware).

Quick follow-up: I continue to enjoy benefits noted in the OP with a dual cache configuration. Device remains responsive after waking and typically returns to 'full' performance within a few seconds. I can easily switch between a handful of apps (browser, mail, Play Store, XDA labs, etc) with minimal lag and context preservation; no reloading web pages after switching away. No notable impact on battery life. Really no disadvantages at all - at least with my work flows.
Regardless of tuning one has to keep in mind the modest hardware resources on Fire 7s. Load up a game or two or a couple heavy Amazon/Google apps and things go south pretty quick. That said, responsiveness far better than any stock config, even when the device is clearly overburdened.

Another quick note. Simply adding a classic swap file (suggest 128 GB) to the largely unused cache partition can yield a decent improvement in multi-tasking performance without the complexity of tinkering with zRAM. All steps can be accomplished with the free tool Apps2SD or equivalent. Happy to document if there is sufficient interest.
Note: Be sure to change zRAM swap priority to "1" so it receives preferential treatment over the classic swap file. zRAM will almost always be faster than classic swap but there is only so much if it. The swap file will be used once zRAM is fully utilized (not entirely accurate but generally true).

FWIW - depreciated references to L Speed app in OP after developer acknowledged "cooperation" with Kingo Root team. While nefarious behavior is unlikely there are other options that avoid any potential conflict of interest.

Davey126 said:
...
Technique (highly abbreviated):
- boot device to rooted ROM; install above tools or equivalents
- use EXKM to resize zram to 128 MB (note: zram must be temporarily disabled)
- use Apps2SD to:
* add a static, 128 MB swap file in the cache partition which remains largely unused with custom ROMs
* important: reassign swap file priorities (button at top right): 0 for the static file; 1 for zram
* increase swappiness to 100 if necessary (EXKM can also be used to set swappiness and other VM parameters)
* verify both swap spaces are enabled via sliders
Note to geeks: I understand how swappiness, vcache pressure and other virtual memory e)
Click to expand...
Click to collapse
When you say Cache partition for the swap file are you referring to "/cache" or the second partition for app2sd?

rjmxtech said:
When you say Cache partition for the swap file are you referring to "/cache" or the second partition for app2sd?
Click to expand...
Click to collapse
"/cache" partition which resides on faster internal storage. Anything on external storage will be significantly slower due to interface limitations.

@Davey126 it has been about a day or two and I can confirm that by following these instructions it has brought new life into my KFFOWI 5th gen. This paired with some L Speed Tweaks (even though you say not to trust them, I opted to use it for a few performance tweaks) and the Lineage ROM from @ggow makes my user experience on the device quite pleasing.

rjmxtech said:
@Davey126 it has been about a day or two and I can confirm that by following these instructions it has brought new life into my KFFOWI 5th gen. This paired with some L Speed Tweaks (even though you say not to trust them, I opted to use it for a few performance tweaks) and the Lineage ROM from @ggow makes my user experience on the device quite pleasing.
Click to expand...
Click to collapse
Thanks for the feedback.
As for L Speed I don't distrust the current developer/maintainer but no longer feel comfortable providing an implicit endorsement. Who you associate with makes a difference IMHO. Each person needs to make their own call. There is no magic in L Speed; it simply offers a convenient UI to various well publicized system 'tweaks' that can be implemented using other tools/techniques.

Davey126 said:
Optional tweaks:
- use EXKM or L Speed to set LKM parameters to: 24, 32, 40, 48, 56, 64
- use EXKM or L Speed to set write deferral (aka 'laptop mode') to 5 sec
- toggle KSM off/on in L Speed (sets performance enhancing parameters)
- with zram disabled enable zram tweak in L Speed which will establish a 96 MB space along with other optimizations; I find the smaller size ideal for my workflow; YMMV zRAM size can be set with EXKM or another kernel manager.
Click to expand...
Click to collapse
Thanks for the guide, it already seems to have helped a lot with smoothness but I wanted to know how to set these options using EXKM.
I'd never heard of the app before today and I've had a good look through the menus but can't seem to find somewhere to set these values. I'm guessing these are the usage % values used by the CPU governor to jump up and down power states?

NeuromancerInc said:
Thanks for the guide, it already seems to have helped a lot with smoothness but I wanted to know how to set these options using EXKM.
I'd never heard of the app before today and I've had a good look through the menus but can't seem to find somewhere to set these values. I'm guessing these are the usage % values used by the CPU governor to jump up and down power states?
Click to expand...
Click to collapse
No, governor tunning is a different beast not addressed in the OP (although I do that on some higher end devices).
With regard to EXKM:
- LMK values can be set under memory -> low memory killer
- KSM toggle can also be found in the memory section
- it appears laptop mode can not be set in EXKM (not that important)
As an alternative to laptop mode you can twiddle 'dirty ratio' and 'dirty background ratio' in EXKM. Suggest setting to 30 and 15, respectfully.
Edit: you may also want to take a peek at Kernel Adiutor (correct spelling). While I find it a bit flaky it exposes more controls vs EKKM and costs less too.

Davey126 said:
No, governor tunning is a different beast not addressed in the OP (although I do that on some higher end devices).
With regard to EXKM:
- LMK values can be set under memory -> low memory killer
- KSM toggle can also be found in the memory section
- it appears laptop mode can not be set in EXKM (not that important)
As an alternative to laptop mode you can twiddle 'dirty ratio' and 'dirty background ratio' in EXKM. Suggest setting to 30 and 15, respectfully.
Edit: you may also want to take a peek at Kernel Adiutor (correct spelling). While I find it a bit flaky it exposes more controls vs EKKM and costs less too.
Click to expand...
Click to collapse
Ah, LMK, not LKM. Thanks again.
Also, just a small suggestion but wouldn't it be better to remove the references to L-Speed and leave an edit message at the bottom rather than having the red, striked through text in the middle?

NeuromancerInc said:
Ah, LMK, not LKM. Thanks again.
Also, just a small suggestion but wouldn't it be better to remove the references to L-Speed and leave an edit message at the bottom rather than having the red, striked through text in the middle?
Click to expand...
Click to collapse
Thanks for noting LKM/LMK typo in OP - fixed that.
I will likely clean-up the OP at some point as there are other refinements (eg: tweaking dirty ratios) that may prove beneficial to a larger community.

Davey126 said:
Thanks for noting LKM/LMK typo in OP - fixed that.
I will likely clean-up the OP at some point as there are other refinements (eg: tweaking dirty ratios) that may prove beneficial to a larger community.
Click to expand...
Click to collapse
I was wondering what differences need to be made for a 7th gen hd 10. I know this guide is written for a 5th gen (1gig RAM, 8 gig drive), but I have a 7th Gen (2gig RAM, 32GIG drive) with 2gig zram (priority 1) and 4 gig swap on the /data partition (priority 2). What would be the best LMK values? Also, is it ok to have the swap on /data vs /cache (my /cache only has 400mb)?
Thanks for any help!
edit: in the OP, it says to set laptop mode using L-speed, and then L-speed is crossed out (I understood why), but no alternative is listed for doing this. I just wanted to add that you can use kernel adiutor to change laptop mode. It's on virtual memory settings.

mistermojorizin said:
I was wondering what differences need to be made for a 7th gen hd 10. I know this guide is written for a 5th gen (1gig RAM, 8 gig drive), but I have a 7th Gen (2gig RAM, 32GIG drive) with 2gig zram (priority 1) and 4 gig swap on the /data partition (priority 2). What would be the best LMK values? Also, is it ok to have the swap on /data vs /cache (my /cache only has 400mb)?
Thanks for any help!
edit: in the OP, it says to set laptop mode using L-speed, and then L-speed is crossed out (I understood why), but no alternative is listed for doing this. I just wanted to add that you can use kernel adiutor to change laptop mode. It's on virtual memory settings.
Click to expand...
Click to collapse
It appears you have priorities reversed. Higher values receive preference. The magnitude of the difference is irrelevant. zRAM is considerably faster than eMMC based storage; the latter should only be used when zRAM is exhausted or momentarily unavailable for whatever reason.
The container sizes also seem excessive. 2 GB of zRAM effectively leaves no uncompressed memory on a HD 10 which is highly inefficient. I wouldn't go over ¼ available RAM or ~½ GB. Toss in a 500 MB of eMMC based (overflow) swap file and you're good to go. If you regularly use more than 1 GB of swap on a relatively low end Android device then something else is amiss.
I am aware Kernel Adiutor can set laptop mode but did not want to introduce another tool into the mix...especially one that has demonstrated inconsistent behavior. FWIW - recent testing suggests 1-2 sec may be a better choice vs the 5 sec mentioned in the OP as the latter may trigger lockouts during sustained writes (eg: large file download on a fast connection). I currently use 1 sec and happy with the results. I will likely update the OP with this info once satisfied that the benefit is worth the effort.
All things being equal I see no reason to change LMK values suggested in the OP. Especially given the availability of zRAM and swap.

Thanks for these instructions, Davey126!
I just tried this process on my 5th Gen Fire 7" which I recently installed with the LineageOS ROM. I was not familiar with the EX Kernel Manager and Apps2D Pro tools, but it was reasonably clear how to make the settings changes you recommend.
I added the 128Mb swap under /cache and increased the zram swap to 128Mb, setting it to priority 1. Maybe it's my imagination but my device does seem a lot snappier when switching between running applications, and better at returning to previously displayed data in applications instead of reloading pages.
Cheers!

Matrey_Moxley said:
Thanks for these instructions, Davey126!
I just tried this process on my 5th Gen Fire 7" which I recently installed with the LineageOS ROM. I was not familiar with the EX Kernel Manager and Apps2D Pro tools, but it was reasonably clear how to make the settings changes you recommend.
I added the 128Mb swap under /cache and increased the zram swap to 128Mb, setting it to priority 1. Maybe it's my imagination but my device does seem a lot snappier when switching between running applications, and better at returning to previously displayed data in applications instead of reloading pages.
Cheers!
Click to expand...
Click to collapse
Thanks for sharing first impressions. Time will tell if the benefits are durable; certainly have been for me with no adverse side-effects.
Another suggestion to reduce wake lag: install Greenify (or similar tool) and add commonly used apps to the action list even if not flagged as background abusers (you may need to override Greenify's sensible defaults via the gear icon). This prevents multiple apps from becoming simultaneously 'active' on wake which is a huge contributor to lag on lower end devices with limited resources (CPU and RAM). Hibernated apps will launch when needed with minimal delay and NO loss of context. Works a treat.
Be sure to add your favoriate browser, mail, messaging and social media apps to the hibernation list as all like to 'check in' after a long slumber.
Although Greenify can auto-hibernate apps on most devices (works best with Xposed Framework) I use an automated approach that invokes Greenify's widget when the screen goes off. There's still some momentary lag on wake but the device remains responsive which is a huge improvement.

Hi Davey126,
thx for the guide, it seems to work awesome.
However, i have the one problem thats the settings in EXKM regarding to "zRAM Size", "dirty ratio" and "dirty background ratio" are lost after rebooting the device. Is there a way to make the settings reboot proof? Interestingly for the "LKM" settings there is an option "Apply at bootime", which does the trick for me, but only for the LKM options.
Kind regards,
Stephan

IronMan1977777 said:
Hi Davey126,
thx for the guide, it seems to work awesome.
However, i have the one problem thats the settings in EXKM regarding to "zRAM Size", "dirty ratio" and "dirty background ratio" are lost after rebooting the device. Is there a way to make the settings reboot proof? Interestingly for the "LKM" settings there is an option "Apply at bootime", which does the trick for me, but only for the LKM options.
Kind regards,
Stephan
Click to expand...
Click to collapse
Likely BusyBox is missing or outdated. Try installing this (I use the pro version).

Davey126 said:
Likely BusyBox is missing or outdated. Try installing this (I use the pro version).
Click to expand...
Click to collapse
Ok. I bought BusyBox Pro and updated to Version 1.28.1-Stericson. Still all settings in EXKM besides LMK get lost after rebooting the device ...

IronMan1977777 said:
Ok. I bought BusyBox Pro and updated to Version 1.28.1-Stericson. Still all settings in EXKM besides LMK get lost after rebooting the device ...
Click to expand...
Click to collapse
- verify BusyBox is property installed w/no conflicting builds
- uninstall/reinstall EXKM
- test if behavior can be duplicated with another (free) kernel manager like KA

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