Database Info

[KERNEL] Undervolt driver for the stock HTC kernel for EVO 4G and others (2.6.32.15)

This kernel module allows you to run any stock HTC Froyo kernel with lowered CPU voltages. Reducing voltage decreases power consumption by the CPU, thus lowering heat and increasing battery life.
INSTALL:
You need root or an unrestricted recovery image (e.g ClockworkMod) to install this. The default settings decrease voltage by 75-100 mV which seems stable on my device (HTC Desire) and is reported to be fine on the EVO. Just download the attached file and select it from recovery or ROM Manager.
I've built "update.zip" files for the EVO 4G with Linux kernel versions 2.6.32.15-g746f4f0, 2.6.32.15-ge2fb08e, and 2.6.32.15-g59b9e50. You can check your kernel version in Settings->About phone->Software information.
Other HTC devices running Froyo are supported. If you have a different device, please give me the full version number and I can add an update.zip for it.
Full details and source are in the original thread in the Desire forum:
[KERNEL] Undervolt driver for the stock HTC kernel for Desire and others (2.6.32.15)
Update, 2010-11-22: Added driver for 2.6.32.15-ge2fb08e.
Update, 2010-11-23: Added driver for 2.6.32.15-g59b9e50.

recant: love this idea when trying to keep this stock

Sounds like it would go well with Fresh's new rom.

ericwgarza1 said:
Sounds like it would go well with Fresh's new rom.
Click to expand...
Click to collapse
+ 1 on that I agree

sweet I like. Does it change the kernel version?

Too weak... funny considering there is more work involved in setting this up than most linux guys even do on a pc... let alone a phone.
tatnai said:
what's this here? sounds like an add on for those too weak at heart to flash a modded kernel. will likely find some friends, strong work.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

tatnai said:
what's this here? sounds like an add on for those too weak at heart to flash a modded kernel. will likely find some friends, strong work.
Click to expand...
Click to collapse
Maybe not. I run the netarchy kernel but don't OC because it seems to crash at random times. I use it because the battery life is better than stock.
I'll revert to a clean back-up and give this a try just for giggles.

I would like to see some results.
I say that because I have tried a few havs roms and get worse battery life.
I think what a lot of people don't realize unless they are heavily into overocking is that microadjustments just dont have much effect there needs to be some substantial drops to really have any effect on battery and heat.
I realize that this is no desktop or laptop cpu, and that this cpu is based off such low voltages but such minor voltage adjustments, 80-100mv just arent going to have the desired effect unless that equates to a "substantial" voltage drop.
Not to mention the fact that most of you are going to overclock your phone without the faintest idea that doing so, even with a lower cpu voltage, will still cause worse battery life. This is a fact.. to argue it is futile. Its the nature of the beast.. do some reading and find out for yourself.
You can overcome some things by using on demand overclocking but you have to do extensive testing to find the sweet spot.
fr4nk1yn said:
Maybe not. I run the netarchy kernel but don't OC because it seems to crash at random times. I use it because the battery life is better than stock.
I'll revert to a clean back-up and give this a try just for giggles.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Nice work. I'm not interested in oc'ing, nor flashing a custom kernel. I may give this a go after a few others check in w/ results. I just want to know that it's stable.
I went to your other thread and saw the source. Clever solution, nice work. I really do like that you wrote a device to /proc that does a little more than report the frequencies back. This will make it very easy to write some scripts, or even a UI, that lets me tweak the settings. Hopefully I have some time to work on that in the upcoming weekends.

Will take a look at this first chance I get. Trying to finish my battery logger since everything available now doesn't log exactly what I want to know. Kudos.

Does this make HAVS obsolete ?

iscaela said:
This kernel module allows you to run any stock HTC Froyo kernel with lowered CPU voltages. Reducing voltage decreases power consumption by the CPU, thus lowering heat and increasing battery life.
INSTALL:
You need root or an unrestricted recovery image (e.g ClockworkMod) to install this. The default settings decrease voltage by 75-100 mV which seems stable on my device (HTC Desire) and is reported to be fine on the EVO. Just download the attached file and select it from recovery or ROM Manager.
I've built "update.zip" file for the EVO with Linux kernel version 2.6.32.15-g746f4f0. You can check your kernel version in Settings->About phone->Software information.
Other HTC devices running Froyo are supported. If you have a different device, please give me the full version number and I can add an update.zip for it.
Full details and source are in the original thread in the Desire forum:
[KERNEL] Undervolt driver for the stock HTC kernel for Desire and others (2.6.32.15)
Click to expand...
Click to collapse
Undervolting meaning only when screens off or on and off ?

I installed and will get the best battery life yet. Better than when I was with King and other kernels....thanks!!!

Anyone have any results from flashing this yet? How is battery life? Any stability issues?

look4wisdom said:
Anyone have any results from flashing this yet? How is battery life? Any stability issues?
Click to expand...
Click to collapse
No stability issues and it seems to help on battery a little bit but I really can't tell a big deference. I was expecting for it to help out more. Thanks anyways OP for the share

i did say those little microvoltages aint gunna make any difference.
plus if you try to overclock you just cancelled any lowered voltages and actually cause higher power draw than stock mhz at stock voltages.
higher mhz equals higher power draw whether you have it undervolted or not.
you have to make a signifigant drop in voltage to make any difference at all. let alone if you try and overclock.
not trying to dog the guy who discovered this i am just sing plain and simple math, heat, and electronic voltages.
Sent from my PC36100 using XDA App

question there a some diference between this kernel and the once from King and Net, talking about battery life and performance

juancaperez2000 said:
question there a some diference between this kernel and the once from King and Net, talking about battery life and performance
Click to expand...
Click to collapse
This isn't a kernel its just a couple of files that go with the kernel. One file for initial boot ect/initd and a .ko file that goes in system/lib/module folder.

I have an Evo, [email protected] #11. I would like to try it. Please build an update.zip to support it.
Cheers.

snovvman said:
I have an Evo, [email protected] #11. I would like to try it. Please build an update.zip to support it.
Cheers.
Click to expand...
Click to collapse
OP
Sent from my EViO + PURE= PURE Baked EViO

[KERNEL][FROYO][OC][08-08-11]PeanutButta Jelly Time - OTB Edition

For the people that want overclocking, here is your chance. I took my standard voodoo kernel, and put in the stuff needed to overclock it. Thanks to nemesis2all and his OTB kernel from the Fascinate for the code needed to get this to work. Also, use extreme caution when using the higher clock speeds. The stock "max" voltage for the CPU is 1300mv, and 1500MHz and 1600MHz are both at 1500mv, so it's heavily over-volted at the top end. By default, the system will boot to 1000MHz and you need to set the speeds you want in Voltage Control App. I don't personally use this because I think overclocking is useless, so any bug reports need as much information as possible, or they will be dismissed and not looked into at all. If you run into an issue with the system locking up, odds are that you have undervolted to much for a given clock speed. Other than that, you're on your own. Same FAQ applies as the regular PBJ kernel, so look there until I get a chance to post it here as well.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0808
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB Storage in recovery
0730
Updated CWM binary
Custom boot animation support
0709
Voodoo Sound V10
0615
Overclocking - Use Voltage Control App to adjust clocks and voltages
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Smooth out boot animation
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.

FAQ Placeholder

2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts

Undervolted and running ok so far.
Sent from my SCH-I510 using XDA App

Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!

ZeppelinJ0 said:
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.

will2live said:
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
Click to expand...
Click to collapse
Well it's definitely enabled. I just must have set the CPU settings poorly because this thing is crawling right now, I can't even scroll through the app drawer!
I've been trying to CWM back to the other PBJ kernels however my phone hangs on reboot, I'm guessing because those need to be flashed with Odin.

asenduk said:
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Click to expand...
Click to collapse
I wish I knew what I was doing wrong.. running at 1.4 and my quadrant scores are exactly the same.... not that it really matters but still...

imnuts said:
. I don't personally use this because I think overclocking is useless.
Click to expand...
Click to collapse
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.

das7771 said:
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
Click to expand...
Click to collapse
Use a program like CPUSpy that shows you the clock speed stats of your phone. >75% of the time, it will likely be in 400MHz or less, this probably approaches >90% if you say 800MHz or less, especially if you are not a heavy user. At that point, why overclock your phone? To get the overclocking stable, you need increase voltages across the board, and despite undervolting, you'll never get the same power usage as you can with a non-overclocked kernel as some of the voltage changes you can't revert. My opinion is that while overclocking can smooth some stuff out, for most day-to-day usage, it has no practical benefits and only causes more battery drain than you would otherwise have. Given how precious battery life is these days, why knowing make your battery drain faster?

it's funny you say that becuase i noticed with ludeboy's kernel that when overclocking system panel very rarely showed my phone running over the stock speed. Usually it was as you stated some where around 800mhz..I understand what your saying...Thanks for the quick response.

So what if we run stock clock...but undervolt? Do you think we will see any batt savings?

Backup SD and app data b/c crashing/freezing can corrupt files.
Edit: Also keep Voltage Scheduler Remover on your phone just in case.
1600
1500
1400
1300 -0
1000 -25
800 -50
400 -75
200 -100
100 -150
"interactive" was unstable a couple kernels ago so I haven't tried it.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
Potentially, yes, but you may lose stability.

Awesomeness
I love it. I can deal with a slightly shortened battery life. I wanted to OC because a lot of the more intense games don't run as smooth as I would like. With OC, its all butter. Thanks!! I have mine set at 1400, and it really didn't improve my quadrant scores, but there's a noticeable decrease in lag going from one app to another.

suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
You would see better battery life at stock clock speeds if you just used the standard (ie. not overclocked) kernel I built.

Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
I'm on board with not thinking it's necessary - though I can see how the tinkerers and speed demons would love it. (And all the more power to them, literally)

I don't know imnuts, I always noticed when I forced the phone into a higher overclock it always seemed quite a bit snapier.

Keep it on conservative. Interactive is buggy.
ZeppelinJ0 said:
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse

underscored said:
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
Click to expand...
Click to collapse
This will remain separate from the standard kernel most likely. I will see if I can build off of this source without overclocking and have it work, though I don't know if it will. I want to keep them separate for stability and battery life reasons.

Kernels

Can anyone explain to me what kernels are what is their function? I noticed that the update did not change my kernel. Is that a bad thing that they did not include a new one in the update? Also I am voinv to be installing xboarxers stock. Rom first to root the phone and I want know if I should chance the kernal and what effect it will have. I am taking small steps because want to understand what I am doing. Thank for any help you guys can give me.
Sent from my LG-P999 using XDA App

The kernel is the lowest point in the system. It controls how the software communicates with the hardware: how the CPU behaves, how the buttons behave, how the screen functions, etc.
The main use of custom kernels is to Overclock and Undervolt. OC means pushing your CPU to be faster than it was ever intended to be; you get better performance but if overclocked too long, it will be damaged. Worst case scenario, you will literally melt your motherboard. But this is only a danger if you leave it overclocked 24/7 and constantly push the CPU to its limits (playing 3d games for instance)
Faux's kernel can OC to 1.5 GHz and Morfic's can OC to 1.1.
The next common use is Undervolting, which means giving your CPU less electricity than it would like. This again is extremely dangerous if not done properly, but yields noticeably better battery life. Morfic's is the best for UV IMO, though you cannot change the undervolting, he has it locked into what he has found to be the best. And this isn't necessarily a bad thing, as too much UVing will cause potentially serious stability issues with the device. It's not nearly as dangerous as improper OCing (it won't permanently ruin the hardware) but it is a danger. Faux's lets you UV to your heart's content.
Faux's is better if you want performance, because it has higher OC. Morfic's is better if you want battery life, because it has better UV and the CPU clock speeds themselves are better tuned for lower speeds than higher ones.

I absolutely love my faux kernel. its at 1.4 and amazing battery life. The screen sensitivity is awesome. Honestly its all prefrence.... I won't go away from cm7w/ faux
Sent from my LG-P999 using XDA Premium App

http://en.wikipedia.org/wiki/Kernel_%28computing%29
I'd start here. Or just google info on the linux kernel (since that's what android runs on top of.)

Can you flash faux kernel on top of bionix 2
Sent from my HTC Sensation Z710e using XDA App

When you flash a kernel, you just need to know what the base of it is to pick the proper one. There are really only 3 bases at the moment:
1. Stock 2.2 That'd be faux's .5, and I know morfic has some older 2.2 based kernels in his thread.
2. Stock 2.3 (Which faux is working on now, there are a couple floating around)
3. CM7 Faux and morfic both have kernels that work here. (2.3.4 and 2.3.5 based roms use this, miui, and of course cm7 )
Bionix is based on 2.2 (Which I haven't actually checked, but I'm sure it's in the first post.)
For most of them, just read the first post, or even the title. It'll say what it's based on, and then you can flash whatever you want. Just always do a nandroid backup before, you never know if you might for whatever reason have to flash back. If you don't, you need to reinstall your rom (or manually change the kernel and modules, of course) to get back to what the rom came with.
Happy flashing.

If i am running stock rooted GB OTA, can I flash faux's latest Kernel 006 with ext4?? Or do you have to have an ext4 rom to be able to flash ext4 kernels?
Thanks.

Thanks a lot that shed some light on. The subject
So it appears that the dev will tell you which mernels arw compatible with their rom in the thread for that particilar rom. If I want to use eglesblood which is 2.3.4 or.5 xan I use tbe stock kernel? Also what is the difference between the .3 .4 and .5 in the gingerbread make is that carrier specific or moel specific like the blackbwrry 8520 is for tmo and 8530 is for sprint?
Sent from my LG-P999 using XDA App

2.3.4 and 2.3.5 are based on cm7 code, so you'd use the cm7 based kernel. (LG hasn't given us 2.3.4 or 2.3.5).
As far as ext4, it's a different file system is all. Faux's kernels mount the data and system partitions as ext4, but don't actually convert them. Morfic's do a full convert. Ext3/4 support is in the kernel, not the rom, so as long as the kernel supports it you can do it. (Which every custom kernel I've seen supports ext4)
If you want more information, google is your friend. Here is a pretty simplistic explanation of the ext2,3,and 4.
http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
As for the differences, 2.3.3 to 2.3.4 had some major framework changes. 2.3.4 to 2.3.5 seems to be only minor bugfixes. If you want full changelogs, I'd google them.

So if I want to use eglesblood then I have to change the kernel too? Do I have to do it separately or is it included in the rom?
Sent from my LG-P999 using XDA App

You never *need* to change kernels. Using the kernel that comes with the roms works just fine. Only time you need to change kernels is if you want to overclock, (never really saw the point in it, and quadrant benchmarks are useless.) want tun or cifs support, undervolting, ext4, etc.
If you don't need any of those things, or don't know what they are, just stick with the kernel that comes with the rom.

Okay that's cool so all I have to do is put EB on my SD card and flash away I am thinking about starting simple first with either xboarders stock or tweeked
.
Sent from my LG-P999 using XDA App

I still have random reboots....

Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)

Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA

ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.

tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.

If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.

tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.

I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..

AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.

zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.

bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.

Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.

Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..

Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.

Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.

hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2

bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...

Will reflashing reset UV?

I'm about to flash seans sky ics and gonna be going with the cymbaline kernel cause I want to undervolt, new to this but my battery needs to last a bit longer. The thing I'm wondering is, say once I have it undervolted and everything, then after a while I wanna switch to a different rom. So I wipe everything, clear the caches and so on, flash a new rom. Will the CPU still be uvd? Or would I need to redo that? If it depends on which method I use to UV it, well, not sure yet cause I can't seem to find the voltage tab in system tuner , and I can't seem to find an app that has options for UV, only overclocking and I'm not too sure about that yet cause idk how it would mix and I wanna get a general idea on what voltages keep my phone stable before I go ramping up the processor. OK that was a bit rambl l I did find an awesome mod to UV just by flashing with cwm so I might use that, just waiting for info o whether or not its strictly for HTC.

Short answer yes you will loose UV if you reflash. However if you use TB to backup the app that you UV with then after the flash you restore app and data you will have your UV values back. And System Tuner only shows the voltage tab if your kernel allows UVing.

Thanks so much. I thought that might be the issue, I'm on whatever stock kernel is included in mods unnamed rom which def doesn't support UV. I figured that would make the most sense but, Feels a lot better knowing for sure