Database Develop

Voltage Control - control OC/UV for OC kernels.

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
Completely rewritten whole app! Epic 4G FCs gone thanks to theimpaler747
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot

xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
First!!!
I tried it with the Bonsai Rom a couple of days ago and it worked for me. I purchased the extreme and I undervolted straight across the board 250mv and I have no problems so far. I think it all depended if the kernel on the phone is compatible or not.

xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
It made me smile when I saw that you posted. Taking a personal interest and such.
I think you might be getting reports from Syndicate people. Syndicate's Twilight kernel didn't implement sysfs very well. Voltage Control will recognize it but changes can't be made and some clocks aren't read correctly. PimpMyCPU won't read it all.
Genocide kernel, Vision kernel, and Bonsai's kernels all work flawlessly.

Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p

I'm using twilight kernel without any problems but I'm no longer on SFR anymore.
Sent from my SPH-D700 using Tapatalk

xan said:
Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p
Click to expand...
Click to collapse
Yeah, that's not right. My Epic doesn't play nice with Voltage Control but I know better than to rate the app bad. These Epics each have a mind of their own. Some like undervolting, some dont. Some like certain ROMs better. I can run 1400 all day but no undervolting for me
Sent from my SPH-D700 using XDA Premium App

FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing

I have found multiple issues with the Twilight kernel, I love the rom, just Genocide has been a lot more stable AND I never had any issues with Voltage Control. I was wondering if you might incorporate multiple profiles like SetCPU? I had to start looking for a different program when it would constantly lock my phone when trying to use them and then I found Voltage Control, and after the rewrite it just makes it that much easier to use.

This might be good, true.
Multiple profiles seem doable...

xan said:
FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing
Click to expand...
Click to collapse
Happy to have helped out for a great app!

hey all, im running SFR 1.1.1 with its stock twilight kernel.
i use to run genocide, but i think i messed up with the UV features and i started getting a lot of lockups. right now i just run setcpu with 1300/400 and i seem to be ok.
i think i bought the WRONG voltage control app also. i bought voltage control extreme by sulph8.
i would love to get back to 1400/400, but im really unsure what the best course of action is. are there default voltage settings in this app? initially, i'd like to run 1400/400 with all the standard voltage settings to see if my phone acts normally again.

Well, Voltage Control by nitr8 is a unlock key for 'mine' voltage control. For now all money goes to him, he promised to send it to me.
To revert to stock settings -> Chose delete boot settings and reboot.
Viola, you have booted on stock settings!
Then set desired frequency limits and you are done

so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?

Sounds ok

what should i set my governers to?

Well, depends on your experience with kernel, generally:
For battery saving try conservative.
For reasonable performance try interactive/ondemand or smartass.
Some kernels have bad implementation of some governors, which can make them unstable, so you need to test, test, test and observe
From my experience smartass (where implemented) is very smooth.
Stock Samsung Gingerbread kernels came with ondemand (not entirely sure)
Stock Froyo/Eclair was conservative.

useport80 said:
so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?
Click to expand...
Click to collapse
Well, I just flashed it again on Genocide. I am running 1400/200 on demand. I am going to check CPU Spy to see if it performs similar to SetCPU. Curious if on demand still drops below 200 if its set as my minimum like Set did
Sent from my SPH-D700 using XDA Premium App

Voltage Control doesnt use any "hacks" for setting frequencies, it just works with standard implemented sysfs.
The governor is responsible for respecting max/min frequency, its kernel implementation that should keep CPU running within desired freqs.

Can the UI include a CPU temp and aninfo page?
Sent from my armed and operational battle station.

SGS's only thermal monitor is refferred as "battery"...
Info page is somewhat coming, but I have to be sure what and how to put there.

[krn.modules] smartassV2 governor for Galaxy S3 stock Kernel

I've FINALLY managed to compile smartassV2 module for SGS3's stock kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The trouble is that the stock kernel does not accept modules...
Every attempt I made ended up with an error about the version of module_layout. I even wrote to Samsung asking for clarification, but I have no reply yet (after about 24 hours).
I will write a post on my blog describing all the investigations; I had to go the hard way and patch /dev/kmem to skip the validation. I've created a small executable which does this.
The good part about it ? It is already included in the .tar.gz below and once executed, it allows any modules to be installed on stock!
I am almost sure that Samsung did not provide the up to date .config file (I am using the Update 1 .tar file) since I had to disable flags in .config to get rid of "unknown symbol" errors. And another proof, the validation errors related to the version of the module_layout symbol.
Thus, the install procedure is a one step longer, patchs3k needs to be executed once, and then any module can be inserted.
Installation procedure:
a) mount your /system in RW mode.
b) create folder /system/xbin/lib
c) copy the contents of the archive to that folder.
d) execute the provided load_smartassV2.sh script (which already does all the steps: calls patchs3k, inserts the module and sets it as current governor).
That's it!
Observations:
a) only for stock kernel.
a1) repeat after me: I will not attempt to run patchs3k if I already flashed a different kernel!
b) load_smartassV2.sh script is made so it is also runnable by Script Manager at boot as super user using the paths in the Install procedure.
c) if you have another way of loading things, you need to figure out how to execute the patchs3k file before inserting the module - I found that the easiest is with the method above.
d) smartassV2 supports lots of configuration options. The only think I made default is the ramp up increment, which is in 500MHz so you don't have to wait forever until the phone gets to max speed. The ramp down I left it at 100MHz increments. All these are configurable and you can echo values in the files found in the list below.
A brief description of each field (but with different values since back then I did it for Sony X10) is found in the Settings part of this post: http://forum.xda-developers.com/showthread.php?t=1212012
Code:
[[email protected]]/sys/devices/system/cpu/cpufreq/smartassV2# ls -1
awake_ideal_freq
debug_mask
down_rate_us
max_cpu_load
min_cpu_load
ramp_down_step
ramp_up_step
sample_rate_jiffies
sleep_ideal_freq
sleep_wakeup_freq
up_rate_us
Download:
Update: download disabled until hotplug issues will be fixed! Please check 4th post below, thanks AndreiLux!
Use it at your own risk!
cpufreq_smartass2_sg3_1.0.tar.gz
Enjoy!

Im really interested in the part regarding the patch to use any module without validation...
Waiting for kernel patch
Sent from my Desire HD using Tapatalk 2

The patchs3k is already bundled in the .tar.gz file above - is this what you meant ?

There's absolutely no point in having smartass on this device, especially on a stock kernel since there is no remaining hotplug logic on it to be used, if that would be even possible. It has major detrimental effects on battery life.
However, we would be interested in what you are doing inside of patchs3k to make it load the module properly and to see if we can use any of that to load Samsung's exFat driver module on custom kernels. Sources please?

viulian said:
The patchs3k is already bundled in the .tar.gz file above - is this what you meant ?
Click to expand...
Click to collapse
AndreiLux said:
There's absolutely no point in having smartass on this device, especially on a stock kernel since there is no remaining hotplug logic on it to be used, if that would be even possible. It has major detrimental effects on battery life.
However, we would be interested in what you are doing inside of patchs3k to make it load the module properly and to see if we can use any of that to load Samsung's exFat driver module on custom kernels. Sources please?
Click to expand...
Click to collapse
That's what i mean
Sources for patchs3k please
Sent from my Desire HD using Tapatalk 2

About the sources - I will create the article these days but I believe it doesn't matter; if you already have control over the custom kernel then you can just make it accept everything and see how things behave.
The trouble with what exFat (which I could also investigate if I have time) is that the CRC checks are thorough and if ANY of the structs used by exFat are different that what the kernel is build with, then there could be big issues with corruption of data and so on. Only Samsung (or sheer luck) could solve this issue. But I did not investigate so these are just assumptions..
@AndreiLux
Then it means I was extremely tired thanks for the explanations with hotplug. I have disabled the download so people won't take it without reading below.
One other thing, the kernel (3.0) like all other kernels has the posibility to create high priority work queues - alloc_workqueue with WQ_HIGHPRI as flag. It means that the work queue that rises the frequency should have higher priority so you don't notice any lag for example.
What I don't like about pegasusq is that it doesn't appear to create high priority work queues. I did not study carefully, but a quick search on the cpufreq_pegasusq.c doesn't show the high priority flag. Maybe the phone one has it ?
They also keep a history of the CPU usage (probably used with hotplugging also).
So I believe the two factors above might contribute to the lag I notice when waking up the phone.
I did notice this weird fact with the cores of the CPU not turning on or off with smartass2 - or remain in the state that pegasusq left them. I was checking test results and it appear to behave normally and have all 4 cores ON during stress test. It was late in the night and I did not check that they are not also shut down.
Maybe I should work on a smartass3 since I can add hotplug logic to smartass - but it is tedious you have to use locks and so on - and I don't have much time.
I think I have more success here with just building ROMs and not digging deep since you just take what everybody does and put a small thanks in a corner then you get all the Thanks and donations.

viulian said:
So I believe the two factors above might contribute to the lag I notice when waking up the phone.
Click to expand...
Click to collapse
The wake up lag is irrelevant to priorities or anything, it's caused by a) if you are referring to the wake up delay then it is because of the kernel is waiting for the modem to wake up which takes an eternity. b) if you are referring to unresponsiveness at the lockscreen, it was due to something in the Wifi drivers.

@AndreiLux Ok cool the modem interaction worths an additional look then!
BUT I have good news!
cpufreq_smartass2.c will be able to have hotplugging! I did a test module that activates cores and shuts them down and there it works.
In few days I will release the smartass2 with hotplug support for stock kernel.
One thing I saw, the pegasusq does NOT have a high priority work queue to bring the frequency up meaning that other work queues could interfere and actually introduce delays. It also has a complex logic to decide when to bring another core back online and it brings them back one by one.
I would like to have feedback from the community on what should be the bringing up / down behavior for each core for the new smartass2 governor.
I am tempted that upon waking up, to actually bring back all 4 cores at once. It is easier for me, FASTER to be executed (instead of going through heaps of samples to decide if one more core is needed) and is also on the same track with the initial smartass concept, FAST AND QUICK or go slow.
The delicate thing is how to handle shutting down cores. I can make it go back to 1 core and if loaded then bring back all again.
What do you guys think ?
I like this new way in customizing phones design by the community, not by what the rom cooker / kernel builder decides and that's it.

I find it fine and dandy, but the most critical point is why you would want to port such a feature to smartass when you already have pegasus with much more optimal frequency scaling. Also the frequency of which the cores are being hotplugged is incredibly high with runqueue sample rate/times of 50 milliseconds and time of bringing up the cores of only a couple of microseconds, all several orders of magnitudes below usual frequency scaling latencies. We've ported it to the S2 with magnificent results and ditched interactive based governors a long time ago, there is no benefit to it. Exynos is relying on aggressive and optimal DVFS scaling for power efficiency and interactive governors do not suit that too well.
It means that the work queue that rises the frequency should have higher priority so you don't notice any lag for example.
Click to expand...
Click to collapse
This is fine in theory but does it hold up in practice? The S3 is already considered as the smoothest running device running Android or even the smoothest device bar the iPhone.
Not trying to critique your work but I think your approach into improving things here is a bit flawed and viewing it from an odd angle.

Excellent constructive feedback! Thank you,
Let me explain my point of view:
1. First, there are many users that do not feel comfortable putting a custom kernel on the phone. Personally, I do not trust custom kernels even if they come with source code. Theoretically is correct to have the open; but I save a lot of time customizing what I trust (Samsung's stock kernel) than checking all the patches of custom kernels to start trusting them. And is not about privacy and so on, but I need the phone to work and I can't really tell if the custom kernel won't decide to play tricks when I mostly need it to work. So I stick with defaults and try to customize here and there.
2. Second, I have no idea how pegasusq compares with smartass2 unless I see them running - also, since I do debugging and so on, the phone uses different frequencies (mostly plugged and running stuff) and so I can't say if pegasusq matches the time_in_state pattern that smartass2 shows. Too early to tell.
And if it can be done why not ? It gives me more experience, it gives people alternatives. Plus, S3 is better than 4s, for sure, but what about the next phones appearing in the next half of year ?
This is just warm up for me to the phone, I have other ideas to dig and hopefully something will come up out of them (at least until the new big market killer comes around and we all jump ship to that one )

Any progress on this

None as it doesn't support multicore correctly...
Sent from my GT-I9300 using xda app-developers app

That was what he was trying to accomplish.andreilux and Simone gave him some new pointers.that's why I ask.

I had no time to take care of it but I am curious to do at least a bare metal version that will wake up with all 4 core at once instead of one by one which I believe pegasus does.
With the default one, the phone is sluggish for half a second when unlocking - I can see it because the launcher struggles for a bit.
But is true, smartass doesn't support cores activation/deactivation.

[KERNEL][AOSP | 4.2.2][DUAL-BOOT] Greenblob 1.1.1 LTS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits to codeworkx for the base aosp kernel!
Features:
More shedulers
row I/O scheduler
sio I/O scheduler
vr I/O scheduler
More governors
cpufreq_smartass2
cpufreq_lagfree
cpufreq_pegasusq
cpufreq_lazy
cpufreq_lulzactive
cpufreq_minmax
cpufreq_abyssplug
cpufreq_wheatley
cpufreq_scary
cpufreq_HYPER
Updated to linux kernel 3.1.0 -rc1
Dualboot support
Brightness adjustments for darker screen settings (good in low light conditions)
Synced with latest codeworkx fixes
Undervolting support
USB fastcharge support
Cleaned up arm source
Compiled with hard float instead of soft float
Greenblob 1.1.72 LTS (Changelog):
Added added row I/O scheduler
Added added sio I/O scheduler
Added added vr I/O scheduler
Upgraded from 3.0.72 to 3.1 -rc1
500 commits FTW! Happy changelogging on git
Greenblob 1.1.1 LTS (Changelog):
Updated kernel from 3.0.36 to 3.0.72 (We´re now on latest linux 3.0.x releases)
Updated ~700 commits (20 Github pages lool). Those are from 3.0.36 to 3.0.72
Hopefully working now on latest cm nightly (working here on my chameleon os)
Go for changelog on github!
Greenblob 1.1 LTS (Changelog):
Fixed auto reboot in recovery
Fixed rebooting during backup in recovery
Fixed some governor stuff
Updated dualboot
Greenblob 1.0 LTS (Changelog):
Added governors
Added 'long-time-support'
DevPrev 6.3 (Changelog):
Added usb fastcharge
Added undervolting support
Default cpu speed at 300mhz
Synced latest changes from cm repo
DevPrev 6.0 (Changelog):
fixed cpu staying at 600mhz
added DualBoot support (Credits to chuandinh for the method. Its the same as Galaxy Note 2 uses)
All dualboot related questions please visit the dualboot thread!!
DevPrev 5.2 (Changelog):
restart after quitting coding kernel
adjusted gamma values for smartphone usage in dark light
wifi driver update
mhard float instead of msoft float
cpu frequency change based on screen on/off
touchkey timeout 2 seconds
cleaned up arm source
TWRP for now - I was just trying something, will revert to cwm soon
Important:
There are no other features than mentioned in the changelog. I restarted the kernel and I think I wont add OC etc. This kernel is not ready yet but damn stable and fast. No need to oc anything (my opinion).
For brightness (gamma) adjustment: You will notice a heavy brightness drop between lowest and lowest +1 step brightness. The one before the lowest was the lowest brightness that comes with normal cm kernel. I will make a better transition between the last two steps within the next update.
DevPrev 5 (Changelog):
Now compatible with cm10.1
Some bugfixes
New control app now on google play!
DevPrev 2 (Changelog):
Updated to latest codeworkx sources
Added undervolting support
Added usb fast charge mode support
Readded 1.2Ghz slot
Greenblob kernel control:
This is the official app to control all features of Greenblob kernel (for now available on Galaxy S2G, visit XDA for infos).
But most features can also be used on any other device! (Ok, not any but for a big number).
You can:
- Change status of tweaks
- Cpu OC
- GPU OC
- Change voltage
Installation:
As usual: Flash the flashable .zip in cwm. Only working on aosp jellybean roms!
Download:
Download here

FAQ:
How do i change voltage?
Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.
Do i need to wipe dalvik/cache?
In general there's no need, but it doesn't hurt so if you have time go ahead. Posted Image I don't wipe.
What's the variable on the GPU OC?
The kernels GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. Greenblob kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.
My phone doesn't seem to be deep-sleeping, what gives?
(assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.
I'm having unusual battery drain - help!
First of all, our i9100g (AS every Smartphone ^^) has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.
I'm having unusual battery drain while screen is off, or phone is sleeping - help!
First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.
I'm having unusual battery drain while phone is in deep-sleep - help!
First make sure you are absolutely positive that deep sleep is working (read the previous question).
While on my kernel *and* connected to Wifi, you shouldn't drain more than 2% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 3-6% per hour, depending on signal strength.
tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
tip 3: http://checkthis.com/d87t
If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.
What is SmartReflex?
SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
My stable and experimental builds will have SR Class 1.5 enabled by default.
You can disable SR via sysfs
How do I use Variable GPU OC?
You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
307Mhz (stock) is set default by the kernel.
Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
for 384MHz: oc gpu 1
for 512Mhz: oc gpu 2
FAQ partly taken from leankernel! I changed the important parts for us! Thanks to them! http://forum.xda-developers.com/showthread.php?t=1790675​

An app for variable gpu oc is already in progress! For now please read the FAQ​

Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G

Such a Fast Releas

iXanza said:
Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thanks ^^ I changed it
And I also changed the battery life expectation
Sent from my GT-I9100G using xda app-developers app

Thanks for sharing，that works great.

any chance to get this kernel for stock rom..?
Sent from my GT-I9100G

+100 for the awesome Kernel !
Sent from my GT-I9100G using Tapatalk 2

First of all, WELCOME BACK FUSS.. Back with bang I can say. New Kernel and it's more powerful, efficient and features. WOW. You Rock. Thank you fuss :beer:
Sent from my GT-I9100G using Tapatalk 2

Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2

ottomatteseo said:
Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2
Click to expand...
Click to collapse
Yes
Sent from my GT-I9100G

iXanza said:
Yes
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thnx
Sent from my GT-I9100G using Tapatalk 2

hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)

IloveXDA512 said:
hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)
Click to expand...
Click to collapse
Flash GreenBlob through CWM
Sent from my GT-I9100G using Tapatalk 2

My phone freezed in the instance i got to the menu. Now it boot loops when i has reached the lockscreen. What should i do now?

I've just installed it. I see in recovery version is now 6.0.1.9 is it still using blob crap for android? Thanks
Sent from my GT-I9100G using xda premium

kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P

cesco73 said:
kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P
Click to expand...
Click to collapse
Sorry thats FUSS not sky
Sent from my GT-I9100G using Tapatalk 2

im sorry to said that, but im still having the reverting back of the freqency....
any idea? ><??

[APP][2.2+] ~=~ Lumos v1.3.1 ~=~ (Automatic Brightness Manager)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More control.
More battery.
More comfort.​
Lumos is fully customizable automatic backlight level manager. We focus on minimal CPU usage and maximum battery saving while maintaining great backlight change smoothness and responsiveness.
Lumos, holding true to its legacy, combines the best from all available auto-backlight solutions in a simple to use package and adds many extras for your tweaking needs.
Features:
- extremely low CPU usage
- NO battery or CPU overhead (drain) unless you actively use your device's display
- simple yet powerful configuration GUI with easy step-by-step calibration process
- many options that let you change every aspect of how your backlight works
- program exceptions to set different backlight for any application
- relative excaptions allow you to amplify/attenuate the automatic backlight for specific applications
- custom backlight profiles
- extensive in-app context help
- great customer support with an issue/request tracking system
- button and keyboard backlight support, including smooth backlight if rooted and supported by HW
Requirements:
- android 2.2 or newer
- a light sensor
- managable display brightness (in display options)
- you may need root access to control button/keyboard lights
Compatibility:
- pretty much every HTC device out there
- most Samsung devices
- possibly others if manufacturer adheres to android driver model
If you have any problems, comments or suggestions, please leave a message here or PM (with proper subject name) or in the bug tracker at http://elite-force.eu
Screenshots:
YouTube presentation:
Get it here:
Lumos
Lumos. The smart auto-backlight manager your battery will thank you for.
~ NIKER

Changelog:
v1.31:
- added smooth button mode support for some HTC One series kernels
- added ability to force buttons on/off as exception
v1.3:
- fixed buttons sometimes staying on when sleeping in root mode
- fixed crash when canceling exception
- added Czech translation
- marked as compatible with Android 2.2
- sample queue is wiped on wakeup for quicker re-adjustment to new light level
- increased reliability of root commands
- experimental more reliable button off on sleep (root modes)
v1.2:
MAJOR CORE CHANGES, CLEAN REINSTALL RECOMMENDED
- reworked sample queue and calculations to allow for intermediate values, resulting in more smoothness in precise mode
- decoupled sample queue and update queue length (update is now performed after every sample if needed)
- above results in lower average latency and allows for longer sample intervals (less CPU usage, more smoothness)
- above also makes larger sample queues viable as means to smoothen out sensor fluctuations
- added ability to apply user min/max as dynamic range for all calculations (compresses CalBrightness into user range instead of capping)
- Lumos will try to use root access to bulletproof itself if you disable ongoing notification icon
- fixed crash after increasing sample queue size
- tweaked the graphs of built-in profiles to better accommodate dynamic range compression
- added backlight fix for HTC One series phones to prevent button flickering (you need to switch the mode manually)
- allowed broader range for sensor sampling rate and sample queue
- showing average latency instead of worst case in settings to get more realistic numbers
- fixed bugs in relative exceptions
- installed app list is now sorted by name
- other minor bugfixes
! your sampling rates, queue size and animation length settings will be reset after update
! new option Compress Dynamic Range will default to ON

great job

Just purchased this nik3r to say thanks for your work on the Elite kernel for the One X+.
I tend to use 50%, 65% or 85% brightness depending on the lighting, so this'll allow me to finetune the screen backlight levels to my liking & hopefully save a bit of battery in the process.
One small issue on AOKP 4.1.2 for the One X+ though is that the button backlight doesn't ramp up & down along with the screen brightness.
I was under the impression that it is mean to?
Or is this feature only supported under Sense roms on the One X+?

For One X+ you need to use root mode to get reliable on/off and stock-based ROMs don't support smooth levels, unfortunatelly.
Maybe AOSP ROMs will add the support, because I doubt it is a hardware limitation but rather driver issue.

nik3r said:
For One X+ you need to use root mode to get reliable on/off and stock-based ROMs don't support smooth levels, unfortunatelly.
Maybe AOSP ROMs will add the support, because I doubt it is a hardware limitation but rather driver issue.
Click to expand...
Click to collapse
Ah ok. Thanks for the quick reply.

some feedback from me:
this app is awesome! it does exactly what it should and the calibration process makes it very simple to set it up to the values i prefer for autobrightness. there's no need anymore to create/flash mods to reduce autobrightness settings.
i also have some suggestions for future versions:
some more explanations on settings (at least for the core section), profiles and app exceptions since not everything there is self explanatory.
but as this does not affect basic functionality of this app, i'd give 5 stars for this one. i recommend it to everyone who wants to improve battery life by easily setting his own values for brightness levels!

Just purchased this app.I have never buy an app from google play before, it is my first time
Also i want to say thanks for eilite kernel for my hox+ I really appreciate your work nik3r.
Best regards.

New version
New version of Lumos v1.2
is released and will appear on the Play Store shortly.
In the meantime I added a changelog to the second post and it is pretty extensive
Hope you enjoy the update as much as I enjoyed making it!
~ NIKER

Thanks
Thanks
this good software

Let me just say based on my experience that Lumos app in terms of battery and functionality is a very great app! It does exactly what I expect from an quality Automatic brightness manager. Did I mention that Lumos supports apps exception too? Just Perfect!
Developer support is also superb! I've been using Lux since it was free and also purchased the paid app but uninstalled it when Lumos came out and never looked back again.
:good::good::good:

Re: [APP][2.2+] ~=~ Lumos v1.2 ~=~ (Automatic Brightness Manager)
I tried to get this app but Google play said it was not compatible.
Any idea why my HTC legend would be an incompatible device?
Edit: It's got version 2.2 & rooted
Sent from my HTC Legend using xda app-developers app

Sorry Lumos needs 2.3 or better

Re: [APP][2.2+] ~=~ Lumos v1.2 ~=~ (Automatic Brightness Manager)
nik3r said:
Sorry Lumos needs 2.3 or better
Click to expand...
Click to collapse
I think that the thread title and description needs changing then as it says 2.2+
Sent from my HTC Legend using xda app-developers app

New version
New version of Lumos v1.3.1 will appear on the Play Store shortly.
It now fully supports smooth button backlight management on some newer One X and X+ custom kernels like EliteKernel and Blade kernel.
Also you can for example set the buttons backlight to be off for your video player using an exception.
Enjoy

Brilliant Application, actually this is one is truly worked for me. I absolutely love this awesome app.
One small request though, I do live in tropical country at times when I take out mobile in direct sunlight the app takes some time to auto adjust the brightness, It is is important for me to see caller or message immediately, can this speed-ed up ? or how about when phone is turned on in direct sunlight the screen turns to max brightness then auto adjusting to optimum value so that I can see the calls/messages from.

The thing is, once the call window appears, no app can change brightness until the call ends (at least on htc). The control is returned to android and there is no workaround i know of. I'll take a second look later in case something changed in 4.2.
If you turn the display on, the sensor sample queue is wiped so the change should be almost immediate. But the call turns it on in your pocket and then returns control to android.
Maybe you could try to add an exception for the phone app and force the display high, but I don't think that will work either.
And thanks for the review
Sent from my X+ powered by ARHD & EliteKernel

nik3r said:
The thing is, once the call window appears, no app can change brightness until the call ends (at least on htc). The control is returned to android and there is no workaround i know of. I'll take a second look later in case something changed in 4.2.
If you turn the display on, the sensor sample queue is wiped so the change should be almost immediate. But the call turns it on in your pocket and then returns control to android.
Maybe you could try to add an exception for the phone app and force the display high, but I don't think that will work either.
And thanks for the review
Sent from my X+ powered by ARHD & EliteKernel
Click to expand...
Click to collapse
Thank you nik3r for detailed reply. I do understand now. Anyway I don't mind it as this app really works well. I think many are not aware of this app and how about releasing trial version on Google Play. It is just a suggestion though, thanks for your time!

nagendraps said:
Thank you nik3r for detailed reply. I do understand now. Anyway I don't mind it as this app really works well. I think many are not aware of this app and how about releasing trial version on Google Play. It is just a suggestion though, thanks for your time!
Click to expand...
Click to collapse
yes
given the price range, atrial version would be apprciated
Envoyé depuis mon Transformer TF101 avec Tapatalk

Still working great and my sole auto brightness app. nik3r one request, can you make app launch quicker in 4.2.2.
It usually takes long time to open in 4.2.2 (Vanilla RootBox ROM)
thanks

[KERNEL] TUNED, LOS14/15/16(Android7/8/9) for S5 [22/ago/18] faster and lighter

This is a Kernel, based on Lord Boeffla's Kernel, "boeffla-kernel-4.1-CM14.1-g900f", which is based on LineageOS Kernel, which is based on AOSP (google) Kernel, which is based on Linux Kernel.
It should be installed via Recovery (TWRP or CWM) over any other LOS 14/15 ROM/kernel, just like boeffla kernel. It doesn't need any tweaking with any app. Install it and use it.
BUT you can use "boeffla config app" if you like tweaking. You will receive a Warning about "mpdecision", just ignore it.
It has:
- a different "low memory killer" algorithm
- zcache is disabled for really freeing memory that was used for caching files (when needed) instead of compressing it
- a different default cpu hotplugger. Every other kernel (even LOS/stock) relies on Qualcomm's MPDecision, I wrote my own, *****es
- Tuned governor (it's the default). It's basically the Interactive but with a lot of tuning.
- many compiler optimizations not found on boeffla or LOS
- many unused code simply REMOVED to free memory and CPU. People just add more stuff, I like to remove
- TV tuners removed from code. wtf...
- many unstable governors and i/o schedulers removed
Note that even though 2GB of RAM isn't too little, if you have too many memory-hungry apps, performance will always suffer; Most apps are started(loaded up to RAM) right after booting; There are ways to prevent this auto-start but I can't remember now..
Overall your phone will be snappier, and less battery hungry
XDA:DevDB Information
tuned, Kernel for the Samsung Galaxy S5
Contributors
fbs, lord boeffla, haggertk
Source Code: https://github.com/bemerguy/tuned-kernel-LOS-s5
Kernel Special Features: lighter, optimization-focused
Version Information
Status: Stable
Stable Release Date: 2018-08-22
Created 2017-10-08
Last Updated 2018-11-01

DOWNLOADS:
KTMonitor = an app that will show your cpus clocks in real time, in a overlay window. simple, fast, no ads.
If you only see the first cpu (CPU0), you'll have to change kernel selinux mode to Permissive instead of Strict. Boeffla config app can do it.
"tuned kernel" builds will show up here, from older to newer
klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
klteduos - SM-G900FD, SM-G900MD
kltedv - SM-G900I, SM-G900P
kltekor - SM-G900K, SM-G900L, SM-G900S
los14 = cm14 = android 7
los15 = cm15 = android 8

Reserved
220818:
-hstcp as tcp congestion control
090818:
-and zram disabled again
-compiled with the leanest toolchain type
-undervolt back on, I guess
-lowmemorykiller from xiaomi's stock kernel
-read ahead disabled completely
-more unused kernel parts removed
-more compiler optimization
280618:
-zram enabled again, now with lz4 that should have been used since forever but wasn't
-some kernel fixes from around the net. should be even faster
"tuned" governor tweaked a bit, and it's profiles too (for those who still uses boeffla app to tweak things)
210618:
-LOS 15.x build
-268mhz as default min speed and 2.6ghz as default max speed
-can't figure out why swap is being used A LOT even with swappiness=5, making battery life miserable, so zram disabled again
-"tuned" governor as default. It's a "interactive" with bugs fixed and tweaked
-"zen" scheduler as default, with some bugs fixed. it's fast, simple, almost like noop+deadline+row mixed
230418:
-latest boeffla-based
-wifi tweaked
-zram (swap) is back
-other compiler flags not enabled before
280218:
-beta22 based
-lmk faster than before while screen is on. slower than before when screen is off
-interactuned governor will save some cpu while screen is off
160218:
-now compiling with linaro 8.0
-"interactive" governor renamed to "interactuned" to get rid of conflicting values
-"interactuned" profiles updated on boeffla app (standard, performance, battery, battery extreme)
-tuned hotplugger tweaked a bit
110218:
-lmk will search, compare apps' scores, and kill them in groups. the stock lmk and the "less aggressive" lmk from build 020218 were killing one app at a time
-put tuned hotplugger to run more often when display is on. the cpu cost is minimal as it is extremely simple
-tweaked compiler flags again to not make code large
020218:
-boeffla's beta21 based
-less aggressive lmk again
-tweaked compiler flags
-tweaked interactive governor
-tweaked tuned hotplugger
301217:
-more aggressive lmk
-less aggressive tuned hotplugger
-tweaked the default interactive values in ramdisk (via anykernel), as they are modified by it on boot
-tweaked also the boeffla app interactive profiles
-performance governor will really drain your battery now, but it will be even faster (max cpu clock, all cpus on if using tuned hotplugger)
-compiling with O2 but with some O3 flags. it seems to be faster than 211217
211217:
-beta20 from boeffla
201217:
-tweaked some filesystem stuff
-it seems tuned hotplug was being ramdonly disabled, fixed
-changed how tuned hotplug enables/disables cpus:
it was based on the number of processes needing cpu. But the system itself didn't count as "processes", so I changed it to look at the cores frequencies instead. The cpu governors itself has a lot of code just to measure how busy the cpus are before raising or lowering frequencies, I think it's faster/lighter to just use that info instead of calculating again or in another way.. In practice: cpu0 at max frequency will turn on cpu1 and so on. Any cpu on lowest frequency for some time will turn it off. I don't really know if this will be better or worse than the code before(151217)​
151217:
-beta19 from boeffla
071217:
-beta18 from boeffla kernel
-zram/swap fully disabled. The slowdowns are unacceptable. It seems we will always get a huge performance/battery hit with any kind of swap. For now I think it's better to let the "low memory killer" do its thing than swapping. Remember: Killing an app will instantly free RAM with zero CPU usage. Swapping means a lot of CPU usage, and (as swapping occurs in RAM), only 40-50% of ram will be freed.
011217:
-beta17 from boeffla kernel
-tweaked tuned hotplugger a bit. changing from mpdecision to tuned on config won't bug the lower frequency
-swapping should be faster
271117:
-hotplugers "mpdecision" and "optimized mpd" working again. zzmoove hotplugers removed (the governor itself was removed long ago)
"interactive" profiles changed a bit: "performance" will have more performance, and "battery" will really save more battery
-zram compression (swap) may be even faster now
-compiler toolchain updated to gcc-linaro-7.2.1-2017.11
-processor scheduler using logarithmic scaling
-"tuned" hotplugger logic was changed a bit. it will turn on/off cpus based only on average load, but will obey the "order" and may turn all on if the load is suddenly high. it may also use less cpu to compute
-"interactive" governor may also use less cpu

So it's safe to say that this kernel could just be flashed over beta12 , i would like to test it and see the difference at work .
Also , Thank you for the work you put into this.

I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management. I'm curious if what you have done here will work even better. Keep up the good work.
Sent from my kltespr using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KazuDante said:
So it's safe to say that this kernel could just be flashed over beta12 , i would like to test it and see the difference at work .
Also , Thank you for the work you put into this.
Click to expand...
Click to collapse
yes

The~Skater~187 said:
I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management. I'm curious if what you have done here will work even better. Keep up the good work.
Click to expand...
Click to collapse
Thanks. I think it would. This "ALMK" is a new feature that only made more obvious what was already broken. I was already trying to get rid or modify LMK when it was integrated to our LOS kernel.
You could, *at least*, drain less battery by installing this mod. If you have time, please compare before and after.. I think it does use less cpu and the phone won't "gag" when it needs more memory (like when opening a new app)

64MB for empty applications? That is TOO low. The default is 180MB. This way, lmk would/should only kill anything when all the system has only ~64MB to cache files.
The memory lmk really counts is not the real "free" ram, it's the "cached" ram. Our "free" ram is almost always ~44MB..
the Linux kernel will use available memory for disk caching, unless it's required by a running program.
This is considered good; say you have 4 GB RAM, and your programs are using only 1 GB. The other 3 GB are going to waste. Despite the "feel-good" impression from knowing you're only using 25% of your memory, the counterpart is that the other 75% is going unused. So the kernel uses that for caching files which significantly improves performance. It's automatic; unlike older operating systems you don't need to decide how much to devote to disk cache, or manually configure it.
"The Linux disk cache is very unobtrusive. It uses spare memory to greatly increase disk access speeds, and without taking any memory away from applications. A fully used store of ram on Linux is efficient hardware use, not a warning sign."
Click to expand...
Click to collapse

fbs said:
Thanks. I think it would. This "ALMK" is a new feature that only made more obvious what was already broken. I was already trying to get rid or modify LMK when it was integrated to our LOS kernel.
You could, *at least*, drain less battery by installing this mod. If you have time, please compare before and after.. I think it does use less cpu and the phone won't "gag" when it needs more memory (like when opening a new app)
Click to expand...
Click to collapse
From what I'm seeing this is working great. Free Ram seems to be holding steady between 700 and 800 MB.
Would you mind if I implement this into a test version of my kernel? I would like to see if it has any ill effects with the added features I have in mine.
Sent from my kltespr using Tapatalk

The~Skater~187 said:
From what I'm seeing this is working great. Free Ram seems to be holding steady between 700 and 800 MB.
Would you mind if I implement this into a test version of my kernel? I would like to see if it has any ill effects with the added features I have in mine.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Of course! Let's try to make things better for our S5... !!!

fbs said:
Of course! Let's try to make things better for our S5... !!!
Click to expand...
Click to collapse
Awesome. I added you modified lmk.c to my source, compiling now. I will keep you posted on my findings. Thank you again!
Sent from my kltespr using Tapatalk

im loving where this is going so far.....heck if even in the future this could also be loaded on the 8.0 then our s5 still have a long way to go life wise.
awsome colab guys.:highfive:
and on top of that the official xposed is now out for Nougat , this is a good day.

The~Skater~187 said:
I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management.
Click to expand...
Click to collapse
VERY interesting! For me deactivating ALMK in Kernel Adiutor didn't help so far. But I didn't test this brand new kernel yet - just the older version based on boeffla kernel beta11. This new thread is one the most helpful of the last 3 month! Thank you so much, @fbs!

VERY good news! I have subjected your current kernel to a heavy stress test. Made a Nandroid backup triggered by SManager in the background. Half of the time (about 12 minutes) I chatted on WhatsApp and was surfing with Chrome while the backup was running in the background. This *never* had been working before without any issues. Afterwards I synchronized the 5 GB backup with my NAS via FolderSync in the background. This also worked perfect! In addition, there were no slowdowns or lags at work. Everything ran (and runs) absolutely fluently. At the first glance I'd say it's the far best kernel I ever used on my S5!

I've added another version, with ZCACHE disabled. It may speed up things when accessing files and may solve some bugs. (whispering: I think it was badly implemented, no one uses it anymore..). If anyone is interested in comparing the performance of both versions, including battery usage.. feel free to post!!

fbs said:
I've added another version, with ZCACHE disabled. It may speed up things when accessing files and may solve some bugs.
Click to expand...
Click to collapse
I will gladly give it a try. But I am truly more than satisfied with the current version! It runs smoothly and reliably. I couldn't detect any bugs. The most important thing is that we also get a beta13 and beta14 and so on...

The no zcache version seems pretty damn smooth so far. I haven't really stressed tested yet, but I'm not getting lockups and lag spikes as I was with normal one.
Please keep up the good work.
Battery life is outstanding but I did just drop a brand new battery from Anker this weekend. So. . . .
Sent from my SM-G900T using Tapatalk

PorchSong said:
The no zcache version seems pretty damn smooth so far.
Click to expand...
Click to collapse
I believe the whole thing is also strongly related to the swappiness-value. My swappiness is set to 30 and I can't see any advantages or disadvantages, whether zcache is switched on or off.

Can i using for RR rom ?

wayan_billie said:
Can i using for RR rom ?
Click to expand...
Click to collapse
Yes you can.