My phone is burning up since faux kernel. Fast as hell, but with regular use gets up to 106 degrees. I've got the governor set to 245Mhz min. and 768 Mhz Max. OnDemand. Running CM7.0.3.
That's pretty hot, right? Too hot? What are the dangers?
Sent from my HTC Glacier using XDA Premium App
You should ask this question in the forum which handles your kernel. Faux does several kernels and you gave no information regarding rom, version, etc. Regardless, this shouldn't have its own thread in the dev forums.
Sent from my HTC Glacier using XDA Premium App
Why didn't you pm him?
Sent from my HTC Vision using XDA Premium App
I dont believe my phone has ever gotten that hot. I set a profile in setcpu to turn the processor down to 245 max with minmax or powersave if it gets too hot. Just like a little insurance incase im not watching it closely.
Related
Hey im just wondering what other peoples specs are for SetCpu?
12000-1000 is what I'm normally set at..
but as far as Voltage and Advance settings I don't know to much in these 2 area's...
so just curious in what people do with these options, and if it increases performance?
Kernal: Matr1x 11.5
Sent from my Nexus S 4G using XDA Premium App
I usually set mine to 1200 200 set it on lazy and its really smooth and very good battery life. I don't mess with the voltage.
Sent from my Nexus S 4G using xda premium
I usually undervolt and keep the stock 1000 / 100 (usually able to get about -75mV from each level w/ 100% stable. At -125mV I start to notice some instability.)
When I OC though I usually keep the voltage at stock and go 1200 / 250.
Anything over 1200 at stock and I find my phone starts getting unstable - everyone's is different though.
Interactive or Lazy Governors for both.
Currently running NexusBeam 4.1 and Glados 2.2.
Thinking about flashing back to ver. 3 though.
Thanks guys.. you guys dont touch options in advance?
Sent from my Nexus S 4G using XDA Premium App
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
Hello guys,
I'm here to ask for all of your opinions about the cpu Profiles, frequencies and governor.
For screen on I'm currently using 1200mHz on performance, I would like to know if it would save more battery by using on demand governor.
Some months ago I had a discussion with few xda members about this subject. But that was on aurora v4. Now I'm currently on v5 u17. Let me know your opinion. Thanks
Sent from my U8800 using xda app-developers app
To be honest, I've never experienced any benefits of setting cpu profiles for screen on, screen off etc. Your phone will work much more smoothly if you stick as close to the defaults as possible.
I don't use profiles. My min is 245 and max 1200, using on demand governor.
For a while I experimented with profiles, and had bad lag when unlocking the phone, and terrible battery use when screen on.
Independent of profiles, your governor will put your phone into deep sleep when the screen is off anyway.
Do a search for "race to idle" this explains in more detail the benefits of using ondemand as opposed to other governors in terms of battery use etc.
IMHO, Android as a platform would be far better served if people stuck close to the default settings and cpu profiles. Most of the time, any negligible benefits are just placebo.
Sent from my U8800 using xda app-developers app
So according to the race to idle running with performance governor saves battery
Sent from my U8800 using xda app-developers app
In theory yes, but if your cpu is always running at max frequency, ie even when doing nothing, then no.
I have done tests, and my battery always lasts longer using ondemand as opposed to performance, or other governors.
Sent from my U8800 using xda app-developers app
Use interactive/bfq that's the best in my opinion
Sent from my U8800-51 using xda premium
Is it ok for me to have a task in Tasker that changes the governor everytime the phone sleeps and wakes? Is that harmful to my device?
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
QUIETLYloud said:
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Brendan12695 said:
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Click to expand...
Click to collapse
You have it clocked at 28.8 GHz? Pretty sure you're going to melt your phone. (I kid)
I believe he meant 288 GHz. He's from the future and is trolling us.
Sent from my Nexus 4 using xda premium
Branden pls
Sent from my Nexus 4 using xda app-developers app
Totally fine, but you might encounter stability problems.
Lol. My bad, was just copying what Trickster Mod said.. :/ I have the min at 288 MHz so when power save is on it underclocks to that.
I just don't want to screw up the hardware by jumping back and forth between ondemand and powersave.
Sent from my Nexus 4 using Tapatalk 2
Try out this Tasker script : http://forum.xda-developers.com/showthread.php?t=1018245
does over clocking the setcpu to high frequencies use more battery on mytouch 4G? I'm using the venom viper rom.
Sent from my HTC myTouch 4g using xda premium
Yes, If you keep it at 1200 it shouldn't be much of an issue.
My conclusion is you almost have to overclock the available sense kernels in order for them to work right.
so my max should be 1200 and what should be my min?
Sent from my HTC myTouch 4g using xda premium
1200 is just a real safe overclock value. You can try other values and see how your phone reacts. Would be nice if there was kernel that could be undervolted. But that just isn't the case.
Min value I would just leave set at 245 or 368. Again you can try other values and see how your phone reacts.
okay thank you for the advice
Sent from my HTC myTouch 4g using xda premium