Database Info

why not overclock the Xoom more?

just curious lol I love to push my devices to the limit!

I'm pretty sure a 50% increase in CPU speed on a dual core processor is more than enough for this guy. Why would you even need to go higher? You'll just end up breaking your device and come here complaining to the devs that it's their fault..
Sent from my Xoom using XDA App

I had mine set to 1.5 and it was very smooth and fast. But I noticed that if I was watching a movie, my xoom got pretty hot in my hand. Maybe not such a good idea to go that high or much higher than that perhaps?
Sent from my Xoom using XDA Premium App

chrisharmful said:
I had mine set to 1.5 and it was very smooth and fast. But I noticed that if I was watching a movie, my xoom got pretty hot in my hand. Maybe not such a good idea to go that high or much higher than that perhaps?
Click to expand...
Click to collapse
Exactly. Same here!

i think if it was totally safe motorola would have been the one to do it and brag that they have the fastest tablet in the market with a 1.5 - 2.0 Ghz Processor. if you want you device to last, leave it with the stock speed, this thing is pretty fast as is, and if you do have to overclock i think the max would be what others have said 1.5. there is no other benefit, and i doubt you will notice any difference. other then your battery lasting 2 hours and your web pages loading a second faster (not important), and maybe apps opening a little faster(won't notice) and then your device getting hot as other have said, which can bcome an issue with other things on the the motherboard becoming hot. and in the next few months you'll end up with a Motorola DOOM

Is it dangerous heating the phone to up to 41C every day?

So I started playing this game Order and Chaos Online (kinda MMO similar to WoW) and the temps get very high, up to 41C on WiFi and 43C on 3g. The phone is burning to a point that it hurts my hand. I'm playing aprox 2-3 hours per day, sometimes maybe 4 hours, how dagerous is that to the phone? Can it do any significat damage over time?
I am using the jame bond kernel at 1ghz, which is also a bit undervolted, don't know the values tho, governer is set to ondemand. I tried to underclock it to 800mhz but the game lags sometimes and is a no-go.

ukhm, khm....

Well if the phone is heating up and it sounds pretty bad, I'm pretty sure its dangerous. Maybe not, but IMO it is. My Sprint HTC Hero has over heated a few times and after that it had small little dots on the screen. Hopefully your phone don't fry.
Sent from my Nexus S 4G

kijp15 said:
Well if the phone is heating up and it sounds pretty bad, I'm pretty sure its dangerous. Maybe not, but IMO it is. My Sprint HTC Hero has over heated a few times and after that it had small little dots on the screen. Hopefully your phone don't fry.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
What are you usual temps? Do you ever get any values similar to mine?

lvnatic said:
What are you usual temps? Do you ever get any values similar to mine?
Click to expand...
Click to collapse
Mines usually sits between 34°C - 36°C, its seems like a normal temp IMO. I've never had my phone hit 41°C before and I sometimes i tether my phone via usb and it still dosent hit that high. If your is hitting that high, it could also be the temp around your home or something. But I wouldn't use your phone to play MMO, especially if your playing 2-4hrs everyday. Just saying..
Sent from my Nexus S 4G

kijp15 said:
Mines usually sits between 34°C - 36°C, its seems like a normal temp IMO. I've never had my phone hit 41°C before and I sometimes i tether my phone via usb and it still dosent hit that high. If your is hitting that high, it could also be the temp around your home or something. But I wouldn't use your phone to play MMO, especially if your playing 2-4hrs everyday. Just saying..
Sent from my Nexus S 4G
Click to expand...
Click to collapse
What ROM/kernel are you using? I never had such low values on intense usage...

lvnatic said:
What ROM/kernel are you using? I never had such low values on intense usage...
Click to expand...
Click to collapse
Well I'm at stock right now because I'm waiting for the ota tomorrow. But I was using koushdecks 1.2.1 with matr1x kernel 4.0 bfs version. Clocked it up to 1.3ghz - 100hz, switched between smatass to ondemand everyone ounce in awhile and I still was at 36°C. I use setcpu's widget to always check my temp and it never goes higher then 36°C. Fact.
Sent from my Nexus S 4G

Can anyone else pls tell their usual temps, this got me a bit worried. On browsing the net I achieve 38C, on some intensive games I can get over 40C. When idle it usually stays at 30C, sometimes in the morning I find it with 28C. Is this normal?
Sent from my Nexus S using Tapatalk

MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheat

MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431

I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium

If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.

jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"

psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk

I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.

Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.

erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium

I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App

No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.

gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium

Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium

erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.

Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.

psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium

mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.

I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.

Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!

lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.

Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.

S3 get hot?

My s3 gets hot so fast. I'll be looking at tweets or browsing pulse and BAM. I don't even want to hold it, its so hot. Yes I am on a custom ROM, cm10 to be specific but this happens to me on stock as well. My governor setting are default for the rom, no custom kernels installed. What do you guya recommend? Should I return it and will vzw accept it?
Sent from my SCH-I535 using xda app-developers app

How hot is it getting? Actual temps I mean.
Install system tuner and that will give you cpu temps. I can't think off hand of any apps except wifi tether for root users that will give you a battery temp.
Before I got a case I thought my phone was getting way too hot, turns out it was no where near dangerous levels but it was hotter than other phones I've had. It's just a thing with the S3.

I'm not sure what could be wrong but just want to throw in that my phone does not get hot at all, it doesn't even get a little warm, and I use my phone quite a bit, pulse is one of my favorites, I play a couple games etc. I am stock but was running CM10 and my phone never got hot.
Sorry I couldn't help just wanted to let you know that simply using your phone shouldn't make it hot, not sure why yours is like that.
Sent from my SCH-I535 using xda app-developers app

What temperatures are in the "redzone" as far as the phone's safety. I'm Overclocked and will sometimes get up to about 120F, but have seen it get as high as 130 before.
To the OP, can you give us any numbers? I use System Tuner to find out mine.

josh995 said:
I'm not sure what could be wrong but just want to throw in that my phone does not get hot at all, it doesn't even get a little warm, and I use my phone quite a bit, pulse is one of my favorites, I play a couple games etc. I am stock but was running CM10 and my phone never got hot.
Sorry I couldn't help just wanted to let you know that simply using your phone shouldn't make it hot, not sure why yours is like that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The 4g is one of the biggest culprits for heat. My phone heats right up if I'm tethering or downloading directly. And I imagine there's a lots of back and forth data with Twitter along with the other browsing he mentioned.
noingwhat said:
What temperatures are in the "redzone" as far as the phone's safety. I'm Overclocked and will sometimes get up to about 120F, but have seen it get as high as 130 before.
To the OP, can you give us any numbers? I use System Tuner to find out mine.
Click to expand...
Click to collapse
Those temps are fine. If I have my phone plugged in and tethering I've seen low 150s. I usually try to cool it down at that point but just so it won't go higher. I've been told that 160f shouldn't hurt it.

Brian Gove said:
Those temps are fine. If I have my phone plugged in and tethering I've seen low 150s. I usually try to cool it down at that point but just so it won't go higher. I've been told that 160f shouldn't hurt it.
Click to expand...
Click to collapse
Awesome! Thanks! My old laptop would often get up to almost 200, in fact it would idle around 180, but I was pretty sure the phones would withstand far less due to the fact that it is in a much smaller package and that there is no heatsink, I just wasn't sure how high it can go.

noingwhat said:
Awesome! Thanks! My old laptop would often get up to almost 200, in fact it would idle around 180, but I was pretty sure the phones would withstand far less due to the fact that it is in a much smaller package and that there is no heatsink, I just wasn't sure how high it can go.
Click to expand...
Click to collapse
A CPU is a CPU pretty much. The heatsink just helps keep the temp down. Equivalent of taking the back of our phone and putting a fan on it almost.

Critical temp is around 180. Our phones will automatically shut down
Sent from my Galaxy Nexus using xda premium

Lol kindve dangerous if your not careful but I put my phone in a airtight zip lock back and ran cold water on the outside, cooled down pretty quickly. Dont let water touch the zip part of course, but maybe another option.
Sent from my SCH-I535 using xda premium

Brian Gove said:
How hot is it getting? Actual temps I mean.
Install system tuner and that will give you cpu temps. I can't think off hand of any apps except wifi tether for root users that will give you a battery temp.
Before I got a case I thought my phone was getting way too hot, turns out it was no where near dangerous levels but it was hotter than other phones I've had. It's just a thing with the S3.
Click to expand...
Click to collapse
Thanks for the tip! i've been having the same concerns. I'll be downloading the system tuner software to keep an eye on the heat.

Noticed change to phones ability to take a charge
I had my phone get quite hot the other day after I switched to cleanrom 6.5 and now the phone doesn't want to take a charge like it did before. Could that be some indication of some damage done?
I didn't have the frame of mind to check the temp at the time. It was noticeable hot though. Even through the case.

fawkiPhone said:
Lol kindve dangerous if your not careful but I put my phone in a airtight zip lock back and ran cold water on the outside, cooled down pretty quickly. Dont let water touch the zip part of course, but maybe another option.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I would advise against that. at the very least use room temp water, not cold. sudden temp changes are never good. could induce cracking in the glass or other components

Heat issue ,is this normal?

I am running cm9(beast mode wifi calling one ) atm but I have a heat issue with my phone around the camera and speaker area where the phone is really hot but by the battery n bottom half it is much cooler.
is this normal for you guys? N gals? And even if I turn of the phone n it cools to 91 is shoot back up again
Sent from my SGH-T959V using xda app-developers app

I'm running on demand btw and around of charge 98-113 charging 109-123
Sent from my SGH-T959V using xda app-developers app

idunno why but we have the same problem..
i think that the reason why it heat up is because you overclocking it?
when i set it max it really heat up quickly.

Install betterbatterystats and see how much CPU you are using and on what.
Sent from my SGH-T959V using xda premium

Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out

dgmoodey said:
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
Click to expand...
Click to collapse
i do that but it goes to 200 mhz never 100

xtrem88 said:
i do that but it goes to 200 mhz never 100
Click to expand...
Click to collapse
That's a 'feature' of the ICS+ kernels. While 100MHZ is the minimum, if it's actually set to that, the kernel is set to go back to 200MHZ anytime it gets the chance. You can watch this happen if your scheduler/governor app actually updates on current min/max speeds. ROM Toolbox PRO, SetCPU, ROM Control, and CM's Performance controls all display this shifting, though with luck you can sometimes get it to stick at 100MHZ. It just takes some persistence.

The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.

airfluip1 said:
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
Click to expand...
Click to collapse
well i left i think it was kj2 and flashed lb6 and i started using greenify hasn't really happened now

No to open another thread I have a Android backup issue any suggestions?
And power managed is on even though wifi is off
Sent from my SGH-T959V using xda app-developers app

I never got my phone to go into deep sleep when I selected ondemand (or maybe it was ondemandx). I would try a couple of the other governors & see if that would help.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app

OndemandX gives me good sleep, but forces the phone to minimum speeds when the screen is off. That tends to cause issues if I'm trying to use GPS or music without the screen burning.
As to what will work best... that depends on unique your phone, its apps, any tweaks that have been made, and your specific combination of scheduler/governor settings. I'm a fan of SIO, but sometimes the tweaks make that (and deadline) stick at max MHZ, in which case noop is great. At various times, I go with any of the SA2-based 'intelligent' options (SavagedZen, brazilianwax, SmoothAss, or SmartAssv2) or the OndemandX/Conservative basic sets. The others have gotten stuck more often and tended to allocate more processor than I think it needs.

I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.

FBis251 said:
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
Click to expand...
Click to collapse
That's usually the one I always fall back on too despite new ones all the time and everything, it's my default now on any ROM.