Related
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.
This tweak is no longer supported, use Touch Wake instead!
For notebook/netbook computers switching off the screen after a certain timeout is a simple yet effective way of saving battery life and such a feature is integrated into every OS. Android also has a screen timeout feature, however this suspend function also disables the touchscreen controls (and touchkey buttons) and you have to press the power button to re-enable the screen (plus, if you did not disable the lockscreen, you also have to unlock it again).
Since this is kinda annoying I tried to find an app which could disable the screen after a timeout and re-enable it on touch, however I could not find one. After some digging I found out that there is no way with the current Android API to disable the screen without simultaneously disabling the touchscreen controls.
So I took a look at the kernel source and after some trial and error it seems I have found a stable way to implement such a screen off feature.
To enable (disable) the screen dimmer pass 1 (0) to 'enabled' in /sys/class/misc/screendimmer. Pass the delay in ms (this is milliseconds; 1000ms = 1s) to 'delay'. The default state is disabled and a delay of 15000 = 15s.
Changes to the source (based on kernel with BLD 3; apply patches in exactly this order):
http://www.pastie.org/2408247
http://www.pastie.org/2408254
http://www.pastie.org/2408257
http://www.pastie.org/2408259
http://www.pastie.org/2408260
BUGFIX:
I already have the first bug fix for you. The kernel was not compiling anymore without the screen dimmer activated in the .config. Besides that nothing has changed, so if you already have a compiled kernel with the screen dimmer running this will not change anything.
Bug fix: http://www.pastie.org/2408688
BUGFIX #2:
Fixed the auto brightness not working anymore.
Bug fix: http://www.pastie.org/2418667
BUGFIX #3:
The user space access to the framebuffer is closed down before the screen is dimmed which makes sense and took care of one oddity I did notice. Also it should save some more battery.
Bug fix: http://www.pastie.org/2420744
BUG FIX #4:
Patch to avoid race conditions.
Bug fix: http://www.pastie.org/2441551
Get Jonathon Grigg's 'Spark Mod Manager' GUI for controlling Screen Dimmer: http://forum.xda-developers.com/showthread.php?p=17291034
I do not accept donations and since I reached my 50GB limit of free space on SpiderOak, thanks to all of you kind people who got an account using my referral link, I could not ask for more.
Instead if you really want to donate your hard earned money to someone who deserves and needs it, consider donating to the Free Software Foundation at fsf.org: These guys are at the frontline when it comes to keeping Linux free and fighting these greedy bastards who think they are entitled to collect royalties and other fees from Linux users due to some silly patents - and if Linux falls, Android will be next.
This tweak is no longer supported, use Touch Wake instead!
good...thanks!!
You are the GOD ...
Amazing... can't wait one of the kernel dev have this on their kernel. So I can easly flash it.
I already have the first bug fix for you. The kernel was not compiling anymore without the screen dimmer activated in the .config. Besides that nothing has changed, so if you already have a compiled kernel with the screen dimmer running this will not change anything.
Bug fix: http://www.pastie.org/2408688
Nice job, looks like a cool mod.
I'll release it under a experimental version of my kernel enabled by default to see how people like it.
One question, does the screen go off while I'm watching a video such as YouTube?
Sent from my Nexus S using XDA Premium App
Highly Appreciated.
reddv1 said:
Nice job, looks like a cool mod.
I'll release it under a experimental version of my kernel enabled by default to see how people like it.
One question, does the screen go off while I'm watching a video such as YouTube?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, unfortunately the screen always gets dimmed even if the app has the FLAG_KEEP_SCREEN_ON set. I took a look at the kernel source and it seems this flag is not passed on to the kernel and handled only by the Android OS; so the kernel does not know whether currently an app is open which has this flag set. Maybe I can think of something, but most likely this is a limitation which I cannot remove.
This will be amazing.
I have always wanted a way to wake up the phone without reaching over to the power button. I remapped my power button to the soft search key just so I didn't have to reach over to push the power button but it obviously didn't work to wake the phone. This is something I've dreamed of, to just touch the screen or the touch keys and it would wake.
Couple questions:
1) Is it possible that only touching the 4 soft keys will wake the screen (instead of the screen)?
2) How does this affect battery? Is a wake lock held? Does the phone sleep correctly to go into power saving? I'm assuming if the screen is touchable that the phone isn't sleeping and as such, this will be a battery drainer.
Enhanced said:
This will be amazing.
I have always wanted a way to wake up the phone without reaching over to the power button. I remapped my power button to the soft search key just so I didn't have to reach over to push the power button but it obviously didn't work to wake the phone. This is something I've dreamed of, to just touch the screen or the touch keys and it would wake.
Couple questions:
1) Is it possible that only touching the 4 soft keys will wake the screen (instead of the screen)?
2) How does this affect battery? Is a wake lock held? Does the phone sleep correctly to go into power saving? I'm assuming if the screen is touchable that the phone isn't sleeping and as such, this will be a battery drainer.
Click to expand...
Click to collapse
1) Currently the screen is re-enabled both when touching the screen and the touchkeys. I think that makes the most sense. However, one could easily modify the code to limit this to the touchkeys.
2) The phone is not put to sleep, only the screen is disabled. So compared to the normal screen lock this will drain the battery much quicker. This tweak is not intended as a replacement for the stock screen lock, but as an addition. You can set the screen lock to a value like one or two minutes, so it will properly lock the phone for example if put it in your pocket, while having the screen dimmer set to a lower timeout like 15sec, so the screen will be disabled and some battery saved if you just pause for some time for example because you wait for a download to finish or talk to somebody. So, if you use it right, you should save some amount of battery.
I found a bug after running this mod for about a couple hours. The screen would not turn on after leaving the phone for about half an hour. The touchkeys would light up and the when I clicked the volume keys I could hear the volume settings changing.
Sent from my Nexus S using XDA Premium App
Ezekeel said:
1) Currently the screen is re-enabled both when touching the screen and the touchkeys. I think that makes the most sense. However, one could easily modify the code to limit this to the touchkeys.
2) The phone is not put to sleep, only the screen is disabled. So compared to the normal screen lock this will drain the battery much quicker. This tweak is not intended as a replacement for the stock screen lock, but as an addition. You can set the screen lock to a value like one or two minutes, so it will properly lock the phone for example if put it in your pocket, while having the screen dimmer set to a lower timeout like 15sec, so the screen will be disabled and some battery saved if you just pause for some time for example because you wait for a download to finish or talk to somebody. So, if you use it right, you should save some amount of battery.
Click to expand...
Click to collapse
This is exactly what I'm lookin for. i will set 1 minute for screen dimmer and 2 minute for screen lock.
Ezekeel said:
For notebook/netbook computers switching off the screen after a certain timeout is a simple yet effective way of saving battery life and such a feature is integrated into every OS. Android also has a screen timeout feature, however this suspend function also disables the touchscreen controls (and touchkey buttons) and you have to press the power button to re-enable the screen (plus, if you did not disable the lockscreen, you also have to unlock it again).
Since this is kinda annoying I tried to find an app which could disable the screen after a timeout and re-enable it on touch, however I could not find one. After some digging I found out that there is no way with the current Android API to disable the screen without simultaneously disabling the touchscreen controls.
So I took a look at the kernel source and after some trial and error it seems I have found a stable way to implement such a screen off feature.
To enable (disable) the screen dimmer pass 1 (0) to 'enabled' in /sys/class/misc/screendimmer. Pass the delay in ms (this is milliseconds; 1000ms = 1s) to 'delay'. The default state is disabled and a delay of 15000 = 15s.
Changes to the source (based on kernel with BLD 3; apply patches in exactly this order):
http://www.pastie.org/2408247
http://www.pastie.org/2408254
http://www.pastie.org/2408257
http://www.pastie.org/2408259
http://www.pastie.org/2408260
BUGFIX:
I already have the first bug fix for you. The kernel was not compiling anymore without the screen dimmer activated in the .config. Besides that nothing has changed, so if you already have a compiled kernel with the screen dimmer running this will not change anything.
Bug fix: http://www.pastie.org/2408688
wor
I have send Netarchy, reddv1 and mathkid a notice (could not reach morfic) about this update, so they aware of this change. As soon as the new version is implemented I will update the list below. Be patient.
Kernels including these modifications:
none yet
Click to expand...
Click to collapse
it works great in trinity with the cm7 nightlies.. thank you.
I don't understand the instruction. what I have to do?
reddv1 said:
I found a bug after running this mod for about a couple hours. The screen would not turn on after leaving the phone for about half an hour. The touchkeys would light up and the when I clicked the volume keys I could hear the volume settings changing.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Hmm. Yeah, that sounds like a bug. Did any error messages appear in the log? Could you reproduce the error?
simms22 said:
it works great in trinity with the cm7 nightlies.. thank you.
Click to expand...
Click to collapse
Great. If you run into any problems please let me know. I am glad we have such a thorough tester on board.
tonno16 said:
I don't understand the instruction. what I have to do?
Click to expand...
Click to collapse
Wait for the kernel devs to implement this tweak. Then follow their instructions to activate the dimmer; they probably will supply you with some init.d scripts for convenience.
simms22 said:
it works great in trinity with the cm7 nightlies.. thank you.
Click to expand...
Click to collapse
Can I have your kernel please.
Can't hardly wait till u released it for public. I will realy appreciate it.
If I could give a try for your kernel, would please send me by email at [email protected]
Many thx before.
rejanmanis said:
Can I have your kernel please.
Can't hardly wait till u released it for public. I will realy appreciate it.
If I could give a try for your kernel, would please send me by email at [email protected]
Many thx before.
Click to expand...
Click to collapse
Here lucid blue kernel with the screen dimmer: http://goo.gl/nBHir
The screen dimmer is enabled and set at 30 seconds. Post any issue you have here.
Sent from my Nexus S using XDA Premium App
rejanmanis said:
Can I have your kernel please.
Can't hardly wait till u released it for public. I will realy appreciate it.
If I could give a try for your kernel, would please send me by email at [email protected]
Many thx before.
Click to expand...
Click to collapse
it should be out soon, maybe today or tomorrow. you dont want the one im using, its really a raw test kernel.
Found another bug, the auto brightness doesn't work anymore.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Found another bug, the auto brightness doesn't work anymore.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
i can confirm it
reddv1 said:
Here lucid blue kernel with the screen dimmer: http://goo.gl/nBHir
The screen dimmer is enabled and set at 30 seconds. Post any issue you have here.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
grate thx men. i love u
it should be out soon, maybe today or tomorrow. you dont want the one im using, its really a raw test kernel.
Click to expand...
Click to collapse
okay mr simms. i can wait.
THE PROBLEM
To save battery while playing video Tegra intelligently decreases the backlight while increasing color brightness and contrast. Because it monitors on a frame by frame basis the changes are often unnoticable. You basically end up with the same displayed image using less backlight.
Unfortunately it seems to get stuck even after you leave the video and the changes are very noticeable as the changes were specific to the video frame you just left and not your homescreen.
This also may be the cause of some ghosting issues and for some it seems to eliminate any ghosting problems for them.
MANUAL FIX
(will reset at each reboot)
In terminal -
(You may need to type "su" and press enter before entering these commands)
To turn it off
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
To change how aggressive it is (untested)
echo "#" > /sys/devices/tegradc.0/smartdimmer/aggressiveness
Note: battery life while watching videos WILL decrease if you turn it off or decrease the aggresiveness
AUTOMATIC FIX
Trickster Mod
- has the ability to disable PRISM and set it to disable on boot.
N7scripts.rar
- A collection of scripts compiled by hamdir which, in conjunction with Script Manager (available in the market) will allow you to toggle smartdimmer/PRISM on and off at will.
- You can also use script manager to toggle it at boot if you want.
- Also includes a script to disable 3D scaling which may improve 3D gaming performance (untested)
Thanks to hamdir for his pack of scripts and for convincing me to make a new post for these fixes.
I may use this for other sysfs tweaks... mine for now.
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
player911 said:
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Messing with the kernel I haven't had any luck. You could ask Morfic. He might be able to make something happen.
Also prism increase color BRIGHTNESS for the most part (you said saturation). That's why the homescreen ends up looking washed out and bright and not oversaturated when PRISM fails to shut off.
Sent from my Nexus 7 using xda premium
sharp2G said:
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
Click to expand...
Click to collapse
There's no prism file. These tweaks are changing a sysfs value. There's no file. The flashable zip adds an init.d file that runs the manual command at every boot.
In your case CWM is complaining about a file that flashes stock recovery on boot and overwrites CWM. These are completely different things. Let CWM "disable recovery flash" and you'll be good to go.
Sent from my Nexus 7 using xda premium
This is awesome. It definitely needs to be implemented in a ton of ROMs
so does flashing this decrease battery life when watching videos? im confused by op..
awesome post, thx!
yes this fix, completely get rid of the grey levels washout issues!!! and greatly improves the quality of the display, it will cost some battery life, but any boost to this average screen is welcome
now about ghosting it did reduce it a lot but sadly it didn't kill it, i still get the very random occasion of faint LCD ghosting
finally we really need to find out a way to fix the stupid low saturation, in particularly the greens are very low
google....these screen issues, lack of tablet UI and launcher rotation issues, makes want to smash it through the wall
Nice find. Hopefully Google/Nvidia/Asus will fix this in an update.
Thank you very much for this! While I don't own a Nexus 7, I *do* own an Asus TF700T and this problem also exists on it. On the TF700, this "mode" is active all of the time, no matter what you are doing and it is *very* noticeable and distracting, especially when watching videos (but it *is* noticeable everywhere else as well).
Disabling this "Feature" makes the problem go away. At the very least, you can enable/disable as needed now.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
ever since i disabled this gamma destroying feature and my screen keeps getting better and better
starting to fall in love with it really
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
you didn't even enter the command line properly...
Sent from my Nexus 7
sharp2G said:
you didn't even enter the command line properly...
Sent from my Nexus 7
Click to expand...
Click to collapse
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
You do not "run" the "enable" file. You need to do this:
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
or
echo "0" > enable (if you are already in that dir).
That will disable the SMartDimmer "feature". Echoing a "1" will re-enable it. I have not noticed any battery life difference....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
espionage724 said:
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Click to expand...
Click to collapse
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
hamdir said:
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
Click to expand...
Click to collapse
Yes as said in the OP smart dimmer analyzes the video frames and determines whether it can lower the backlight while increasing the color brightness and maintain almost the same image. Lower backlight = better battery life.
Sent from my Nexus 7 using xda premium
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Ravynmagi said:
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Click to expand...
Click to collapse
I agree - I think any battery life reduction will be *very* minor for most people... I certainly haven't noticed any difference...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Does anyone know what the exact stock kernel settings are, and can we set a custom kernel to those EXACT settings?
No matter what tweaks I do, I cannot get any custom kernel (Franco, leankernel, elementalx etc) to be as smooth as the stock kernel. The only reason I like using a custom kernel is to tweak RGB color settings. Aside from that I don't need any other changes.
Essentially I'm looking for the stock kernel with RGB color options. Does this exist?
sn0warmy said:
Does anyone know what the exact stock kernel settings are, and can we set a custom kernel to those EXACT settings?
No matter what tweaks I do, I cannot get any custom kernel (Franco, leankernel, elementalx etc) to be as smooth as the stock kernel. The only reason I like using a custom kernel is to tweak RGB color settings. Aside from that I don't need any other changes.
Essentially I'm looking for the stock kernel with RGB color options. Does this exist?
Click to expand...
Click to collapse
if its a stock kernel, then no. since those options arent in stock. only a custom kernel will include those options. even if its close to stock, its not a stock kernel.
Right. I don't mean it so literally. I don't care if its a custom kernel. I'm just looking for a kernel that has all the stock governor and frequency settings but with RGB color tweaking added.
No matter what I do to a custom kernel, they still stutter and lag significantly more than the stock kernel.
sn0warmy said:
Right. I don't mean it so literally. I don't care if its a custom kernel. I'm just looking for a kernel that has all the stock governor and frequency settings but with RGB color tweaking added.
No matter what I do to a custom kernel, they still stutter and lag significantly more than the stock kernel.
Click to expand...
Click to collapse
set up the custom kernel the same way as you set up the stock kernel. custom kernels change the cpu setting many times, and you dont have to use it in that custom way. you can always set up custom kernels they way you want it, like i do as well. i dont use custom kernels with their default settings, i set them up how i like them.
Yeah, that's really what I'm looking for. By chance, do you know all the stock kernel settings that I would want to change something like leankernel to in order to get the complete stock feel.
I know in another thread you said you use ondemand with sampling_rate set to 15000 and the up_threshold set to 98. This definitely helped but I'm still getting some stuttering, mainly when unlocking the device. Aside from the above settings, what else would you recommend tweaking to get as close to stock as possible?
Thanks for your help!
sn0warmy said:
Yeah, that's really what I'm looking for. By chance, do you know all the stock kernel settings that I would want to change something like leankernel to in order to get the complete stock feel.
I know in another thread you said you use ondemand with sampling_rate set to 15000 and the up_threshold set to 98. This definitely helped but I'm still getting some stuttering, mainly when unlocking the device. Aside from the above settings, what else would you recommend tweaking to get as close to stock as possible?
Thanks for your help!
Click to expand...
Click to collapse
well, stock is set at 2649 max with a 1497mhz for a minimum(not lower), with mpdecision and boost enabled. i believe its also set to have interactive as the governor(but i dont know the stock interactive settings). and what do you mean when unlocking the device? on the lockscreen?
Thanks!
Yeah, it's so strange, with both stock rooted and Pure Shamu, no matter which kernel/settings I use, other than stock, I get this very noticeable stutter on the status bar and nav bar appearing when unlocking the device. It also happens on the first couple times of opening the app drawer after a deep sleep. I've tried everything and can't get it to go away. The only thing that fixes it is the stock kernel. It's baffling me, really.
sn0warmy said:
Thanks!
Yeah, it's so strange, with both stock rooted and Pure Shamu, no matter which kernel/settings I use, other than stock, I get this very noticeable stutter on the status bar and nav bar appearing when unlocking the device. It also happens on the first couple times of opening the app drawer after a deep sleep. I've tried everything and can't get it to go away. The only thing that fixes it is the stock kernel. It's baffling me, really.
Click to expand...
Click to collapse
thats an odd behavior, as i never get a "lag' in the lock screen, or in the app drawer. but i keep my phone at 3033mhz high/300mhz low. even on other settings, thats never happened. do you use the google now launcher?
simms22 said:
thats an odd behavior, as i never get a "lag' in the lock screen, or in the app drawer. but i keep my phone at 3033mhz high/300mhz low. even on other settings, thats never happened. do you use the google now launcher?
Click to expand...
Click to collapse
I use Nova. I tried switching back to Google Now and that didn't solve it. I might give 3033/300 a try and set it to stick to that. You use that setting with ondemand governor and sampling_rate set to 15000 and the up_threshold set to 98?
sn0warmy said:
I use Nova. I tried switching back to Google Now and that didn't solve it. I might give 3033/300 a try and set it to stick to that. You use that setting with ondemand governor and sampling_rate set to 15000 and the up_threshold set to 98?
Click to expand...
Click to collapse
yup. i also disable mpdecision.
with a terminal emulator app..
su(press enter)
stop mpdecision(press enter)
---------- Post added at 03:00 PM ---------- Previous post was at 02:55 PM ----------
also, you might have to play with the voltage for 3033mhz. im a bin 5, and had to raise the voltage at 3033mhz to 1185mV(from thee default 1175) to get it so it wont crash. btw, elementalx kernel only does the 3033mhz
Sounds great. Thanks for all the info. I'll adjust all the settings to your recommendations except I'll keep max at the default 2649 for now to see if that solves the issue. I don't think I'll need to overclock past that to solve the issue (hopefully).
Thanks again.
sn0warmy said:
Sounds great. Thanks for all the info. I'll adjust all the settings to your recommendations except I'll keep max at the default 2649 for now to see if that solves the issue. I don't think I'll need to overclock past that to solve the issue (hopefully).
Thanks again.
Click to expand...
Click to collapse
good luck!
oh, and btw, the oc does very little to reduce battery life. i get about the same battery with or without the oc, about 5.5-7 hours sot, depending what im doing.
Yeah, battery life hasn't been an issue for me on this phone no matter what I change. Love that! :highfive:
sn0warmy said:
Thanks!
Yeah, it's so strange, with both stock rooted and Pure Shamu, no matter which kernel/settings I use, other than stock, I get this very noticeable stutter on the status bar and nav bar appearing when unlocking the device.
Click to expand...
Click to collapse
I get the exact same behavior on any non-stock kernel - which is why I went back to stock. I'm also using Nova.
Sent from my Nexus 6 using Tapatalk
Well, I don't believe it's nova that causes it because I get it with the Google Now launcher/custom kernel as well.
I will say that it's been a few hours with the following settings and I haven't experienced a single stutter. Pretty happy so far.
Lean Kernel (franco will probably work just the same)
Governor: ondemand
min freq - 300
max freq - 2649
sampling_rate - 15000
up_threshold - 98
mpdecision off
sn0warmy said:
Well, I don't believe it's nova that causes it because I get it with the Google Now launcher/custom kernel as well.
I will say that it's been a few hours with the following settings and I haven't experienced a single stutter. Pretty happy so far.
Lean Kernel (franco will probably work just the same)
Governor: ondemand
min freq - 300
max freq - 2649
sampling_rate - 15000
up_threshold - 98
mpdecision off
Click to expand...
Click to collapse
Still on the same setup or have you found something else?
funcrusher said:
Still on the same setup or have you found something else?
Click to expand...
Click to collapse
I should have reported back. I ended up going back to the stock kernel again. Even with those ideal settings I was starting to get the stuttering again. And I even got a few SOD's.
I spent some time reading up on it some more and from what I can tell, pretty much all custom kernels seem to have issues from stuttering, lag, SODs etc. with any given governor. The kernel developers are hard at work to fix this but even Franco and flar have said they still have a lot of work to do before their kernels can be 100% functional and reliable.
I've gone back to the stock kernel and everything is perfect. The only downside for me is that I have no RGB controls so I have to live with the 255,255,255 RGB settings for now. But I'll take that and a 100% fluid phone over bugs.
Cf lumen by chainfire has some colour changing abilities in master mode. Not sure if it helps you.
sn0warmy said:
Does anyone know what the exact stock kernel settings are, and can we set a custom kernel to those EXACT settings?
No matter what tweaks I do, I cannot get any custom kernel (Franco, leankernel, elementalx etc) to be as smooth as the stock kernel. The only reason I like using a custom kernel is to tweak RGB color settings. Aside from that I don't need any other changes.
Essentially I'm looking for the stock kernel with RGB color options. Does this exist?
Click to expand...
Click to collapse
This is exactly what I'm after, I'd pay money for this!! Did you ever find it, still on stock kernel??
Sent from my Nexus 6P using XDA Labs
skiely666 said:
This is exactly what I'm after, I'd pay money for this!! Did you ever find it, still on stock kernel??
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Have you guys tried the kernel by gerard_f?
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Hi there!
For sometime now I want to move to LP but I find too many things that are missing compare to my current KK.
I'm using Lux Auto Brightness on my current device and on LP it caused so problems (fullscreen overlay, presist notification etc..)
I was wondering how is the stock auto brightness of the LP (if it's any different from the current KK) or is there any alternative for LP to the Lux?
Thanks!
I absolutely love the stock brightness settings. You set a desired screen brightness with the slider and it adapts the screen in a way, so that depending on environment light you perceive the screen at the same brightness u initially set. In my opinion it works really, really well.
Dixxhead said:
I absolutely love the stock brightness settings. You set a desired screen brightness with the slider and it adapts the screen in a way, so that depending on environment light you perceive the screen at the same brightness u initially set. In my opinion it works really, really well.
Click to expand...
Click to collapse
What is your opinion about the brightness compare to KK?
I recall seeing some very poor performance form the stock brightness management in sunlight.
Sydrox said:
For sometime now I want to move to LP but I find too many things that are missing compare to my current KK.
I'm using Lux Auto Brightness on my current device and on LP it caused so problems (fullscreen overlay, presist notification etc..)
I was wondering how is the stock auto brightness of the LP (if it's any different from the current KK) or is there any alternative for LP to the Lux?
Click to expand...
Click to collapse
Stock auto-brightness (erm, I mean "adaptive brightness") sucks on Lollipop IMO. It's another example of something that wasn't broken but Google tried to fix it anyway and utterly borked it in the process.
My experience is that it does not "adapt" nearly enough. If I set the slider to the right level in daylight, when I go into a dark room I am blinded. If I set the slider to the right level in a dark room, when I go into sunlight I cannot see the screen. Frankly I cannot see the screen adapting at all. If it is adapting then it's in within a very narrow range. I even did a software repair to see if that would solve it, but it didn't.
I've not used Lux, but I've not heard good things about it in Lollipop and am loathed to install an app to do something that previously was handled fin by the OS. Stock auto-brightness worked very well for me in KK.
pipspeak said:
Stock auto-brightness (erm, I mean "adaptive brightness") sucks on Lollipop IMO. It's another example of something that wasn't broken but Google tried to fix it anyway and utterly borked it in the process.
My experience is that it does not "adapt" nearly enough. If I set the slider to the right level in daylight, when I go into a dark room I am blinded. If I set the slider to the right level in a dark room, when I go into sunlight I cannot see the screen. Frankly I cannot see the screen adapting at all. If it is adapting then it's in within a very narrow range. I even did a software repair to see if that would solve it, but it didn't.
I've not used Lux, but I've not heard good things about it in Lollipop and am loathed to install an app to do something that previously was handled fin by the OS. Stock auto-brightness worked very well for me in KK.
Click to expand...
Click to collapse
Are you sure that you have adaptive brightness enabled at all? I can see it adapt quite clearly on mine.
Sydrox said:
Hi there!
For sometime now I want to move to LP but I find too many things that are missing compare to my current KK.
I'm using Lux Auto Brightness on my current device and on LP it caused so problems (fullscreen overlay, presist notification etc..)
I was wondering how is the stock auto brightness of the LP (if it's any different from the current KK) or is there any alternative for LP to the Lux?
Thanks!
Click to expand...
Click to collapse
I'm using Lux on LP and don't have any issues. The persistent notification can be set so it's only visible in the swiped down notification view, but not perpetually visible in the notification bar (in Lux settings, set notification visibility to lowest priority). What do you mean by "fullscreen overlay?"
camaro322hp said:
I'm using Lux on LP and don't have any issues. The persistent notification can be set so it's only visible in the swiped down notification view, but not perpetually visible in the notification bar (in Lux settings, set notification visibility to lowest priority). What do you mean by "fullscreen overlay?"
Click to expand...
Click to collapse
As I've mentioned, I was unable to click "install" in the APK installtion dialog or click on grant/deny in ther SuperSU window.
Sydrox said:
As I've mentioned, I was unable to click "install" in the APK installtion dialog or click on grant/deny in ther SuperSU window.
Click to expand...
Click to collapse
You need to add Package installer and SuperSU to the sleep list in Lux.
camaro322hp said:
You need to add Package installer and SuperSU to the sleep list in Lux.
Click to expand...
Click to collapse
I just faceplamed myself so hard
I think I found the problem; when battery saver mode is enabled, when it kicks in, it will set your screen brightness to a certain fixed level. But when you charge the phone again and battery saver mode deactivates, it will not automatically re-enable adaptive brightness, so you need to re-enable it manually.
My experience was that kitkat was better on the screen brightness. Lollipop works fine and adapts well, except that in bright sunlight it won't turn up the brightness as much as kitkat did.