I have this issue—the screen stays black when I wake up the phone—, so I have to do “adb reboot” manually. I global undervolted 50mV and my phone is on franco. Do you think undervolting may have caused this problem? I do not have enough data in order to judge if undervolting is the main cause. Thanks in advance.
ericjslee said:
I have this issue—the screen stays black when I wake up the phone—, so I have to do “adb reboot” manually. I global undervolted 50mV and my phone is on franco. Do you think undervolting may have caused this problem? I do not have enough data in order to judge if undervolting is the main cause. Thanks in advance.
Click to expand...
Click to collapse
no, its not undervolting. it sounds like sod, sleep of death. it could be kernel or rom related, among other things. anyways, next time so you dont have to connect to adb, press your power button in for 15-30 seconds, itll reboot.
Thank you!
Sent from my Nexus 5 using Tapatalk
Try global 25 to prove the point?
Sent from my Nexus 5 using Tapatalk
Undervolting can certainly cause a phone to be really slow to wake up. Turn off undervolting and see if it continues
Sent from my Nexus 5 using Tapatalk
rootSU said:
Undervolting can certainly cause a phone to be really slow to wake up. Turn off undervolting and see if it continues
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Undervolting is the most likely culprit for your SoDs. No reason to do it anyhow. Although, franco kernel has had that issue with some releases, but are usually fixed very quickly.
Undervolting will add minutes only to SoT and next to nothing for overall time. It's not worth the trouble it can cause.
Just my opinion....and experience.
guys, while undervolting can affect turning on the screen with a slight delay, most likely its not in this case. and undervolting does not cause sod.
simms22 said:
guys, while undervolting can affect turning on the screen with a slight delay, most likely its not in this case. and undervolting does not cause sod.
Click to expand...
Click to collapse
Given that we're using sod as a generic term, I respectfully disagree. It definitely can cause trouble coming from the sleep frequency to the minimum frequency if the voltage is too low, it cannot make the transition. He definitely should roll it back and rule it out before doing anything else. This goes for any instability issue.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Given that we're using sod as a generic term, I respectfully disagree. It definitely can cause trouble coming from the sleep frequency to the minimum frequency if the voltage is too low, it cannot make the transition. He definitely should roll it back and rule it out before doing anything else. This goes for any instability issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
of course it can cause trouble coming from sleep frequencies, but it wont cause sod. yes, undervolting can and will cause stability issues, but it wont cause the screen not to come on. it would cause a delay in the screen coming on, but the screen would turn on still.
if it cannot get to 300MHz from sleep, the screen won't come on.
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Undervolting will add minutes only to SoT and next to nothing for overall time. It's not worth the trouble it can cause.
Just my opinion....and experience.
Click to expand...
Click to collapse
It can help with heat tho if you're having issues in that department
Sent from my Nexus 5 using Tapatalk
Ben36 said:
It can help with heat tho if you're having issues in that department
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup. Maybe good for gamers....or frequent navigators.
kj2112 said:
Yup. Maybe good for gamers....or frequent navigators.
Click to expand...
Click to collapse
I'm neither and always UV by a bit. I also revert to troubleshoot if I run into any problems. In this case I'm betting a revert to stock voltages cures the OPs issues.
theesotericone said:
I'm neither and always UV by a bit. I also revert to troubleshoot if I run into any problems. In this case I'm betting a revert to stock voltages cures the OPs issues.
Click to expand...
Click to collapse
I'm all for anyone doing anything to their device.... That's what android is all about.
But undervolting and under clocking is just something I personally never got. I suppose aside from trying to curb heat issues. But not to prolong battery life. It just makes such a minor difference. I've never seen proof showing otherwise.
But, to each their own.
kj2112 said:
I'm all for anyone doing anything to their device.... That's what android is all about.
But undervolting and under clocking is just something I personally never got. I suppose aside from trying to curb heat issues. But not to prolong battery life. It just makes such a minor difference. I've never seen proof showing otherwise.
But, to each their own.
Click to expand...
Click to collapse
True that.
I look it it this way. Less heat equals less stress. Less stress equals longer life. Use any analogy you want but the theory is there. If I ever run into an issue with my device the very first thing I do is revert my UV settings. If it persists, at least I've ruled out UV.
I believe the idea of UVing devices comes from an era not that long ago. IE, inefficient processors. Modern(the last two years) processors don't seem to have that much inefficiency. Could be snake oil on my side. It's habit though.
theesotericone said:
True that.
I look it it this way. Less heat equals less stress. Less stress equals longer life. Use any analogy you want but the theory is there. If I ever run into an issue with my device the very first thing I do is revert my UV settings. If it persists, at least I've ruled out UV.
I believe the idea of UVing devices comes from an era not that long ago. IE, inefficient processors. Modern(the last two years) processors don't seem to have that much inefficiency. Could be snake oil on my side. It's habit though.
Click to expand...
Click to collapse
I hear ya! Just see sooooooo many thinking they'll see big battery life gains.... And it seems they usually do this for battery more so than heat.
But yeah, I get the heat and stress part of it. Again, especially for games and GPS and what not.
Related
Not all phones can be overclocked safely. Not all CPUs can handle overclocking. If you've ever overclocked a computer CPU, you'd know that no two CPUs are exactly the same.
Well, my Captivate heats up a lot, quickly. It heats up so much that the screen literally CRACKED. After using Screencast w/ Droid VNC, I've managed to backup with Titanium Backup and I'm ODIN flashing back to stock.
I'm trying to get it fixed by Samsung...
We'll see if I can say it's because of the phone overheating that I can get it covered (I didn't drop it for it to crack like that).
I know I'm warning overclockers, but the funny thing is, I didn't use an overclocked kernel (Cognition 3.04). This happened with stock speed!
CLShortFuse said:
Not all phones can be overclocked safely. Not all CPUs can handle overclocking. If you've ever overclocked a computer CPU, you'd know that no two CPUs are exactly the same.
Well, my Captivate heats up a lot, quickly. It heats up so much that the screen literally CRACKED. After using Screencast w/ Droid VNC, I've managed to backup with Titanium Backup and I'm ODIN flashing back to stock.
I'm trying to get it fixed by Samsung...
We'll see if I can say it's because of the phone overheating that I can get it covered (I didn't drop it for it to crack like that).
I know I'm warning overclockers, but the funny thing is, I didn't use an overclocked kernel (Cognition 3.04). This happened with stock speed!
Click to expand...
Click to collapse
First off wrong forum... Second off their is no way the phone could get hot enough to crack this glass unless it had defective regulation or the glass was damaged.
Gorilla glass is tempered in a special way, it is tougher then pyrex, thermal shock would not crack this glass.
slayp00n said:
First off wrong forum... Second off their is no way the phone could get hot enough to crack this glass unless it had defective regulation or the glass was damaged.
Gorilla glass is tempered in a special way, it is tougher then pyrex, thermal shock would not crack this glass.
Click to expand...
Click to collapse
"No way"?
It's not the gorilla glass. The glass is in fine condition. It's the digitizer/amoled screen under the glass. The heat comes from the CPU.
Plus, I'm not the first one:
http://forum.vodafone.co.uk/t5/Galaxy-S/Overheating-caused-Galaxy-s-screen-to-crack/m-p/643601
CLShortFuse said:
"No way"?
It's not the gorilla glass. The glass is in fine condition. It's the digitizer/amoled screen under the glass. The heat comes from the CPU.
Plus, I'm not the first one:
http://forum.vodafone.co.uk/t5/Galaxy-S/Overheating-caused-Galaxy-s-screen-to-crack/m-p/643601
Click to expand...
Click to collapse
Something is seriously wrong with any phone that could get that hot, My phone never breaks the mid forties, even while charging and tethering.
slayp00n said:
Something is seriously wrong with any phone that could get that hot, My phone never breaks the mid forties, even while charging and tethering.
Click to expand...
Click to collapse
Hottest I ever gotten was 114°F. And im at 1.4. Its gotten worst but that was at 1.6 and I let it freeze so I can drain the battery, but damb was ut hot
Sent from my GT-I9000 using XDA App
As I said, not everyone's phone is the same. Yes, there is something wrong with my phone. That's why I'm sending it in.
If my phone was this bad without overclocking, other people may have not-as-bad phones where overclocking pushes it past its limit.
goob1284 said:
Hottest I ever gotten was 114°F. And im at 1.4. Its gotten worst but that was at 1.6 and I let it freeze so I can drain the battery, but damb was ut hot
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
thats 45C so about the same as mine.
I don't remember what cognition version I was on when it happened, but I was tethering and fell asleep. Woke up when I rolled over onto my phone which was extremely hot. I know my heat safety control is working, shuts down normally about 115 F. But for some reason this time it didn't. I quickly opened it up, popped the battery out and started blowing in it. I couldn't even touch the battery at first it was so hot. So I can testify that sometimes craziness happens and can jack up your phone.
This is a fairly common problem with blackberrys I have heard stories about the phones getting insanely got and just frying the whole phone. My personal bet is on a problem with the cpu temperature regulation or something funny going on with the battery.
Sent from my SAMSUNG-SGH-I897 using XDA App
Besides the unusual problem mentioned above, what other issues overclocking could cause to my captivate? Force closes? Freezes? Charge Deaths? Anything else? Anything REAL bad?
sorry for the newbie question...
ddoubt said:
Besides the unusual problem mentioned above, what other issues overclocking could cause to my captivate? Force closes? Freezes? Charge Deaths? Anything else? Anything REAL bad?
sorry for the newbie question...
Click to expand...
Click to collapse
Cpu failure, true bricks.
Not really a need to oc right now, not worth the risk for me. Just bragging rights imo.
boborone said:
I don't remember what cognition version I was on when it happened, but I was tethering and fell asleep. Woke up when I rolled over onto my phone which was extremely hot. I know my heat safety control is working, shuts down normally about 115 F. But for some reason this time it didn't. I quickly opened it up, popped the battery out and started blowing in it. I couldn't even touch the battery at first it was so hot. So I can testify that sometimes craziness happens and can jack up your phone.
Click to expand...
Click to collapse
Tethering was the culprit here. It seems Samsung's (and many mfr.) engineers didn't anticipate anyone would want to run the 3G and WiFi radios simultaneously as wireless tethering wasn't included in Android at the time. It produces tons of heat and uses battery by the gallon. The old open-source wireless tethering app needed for 2.1 had a battery temp indicator for this reason.
Overclocking is considerably less risky. If anything it will simply cut power to the unit at a threshold temperature before damage is incurred. The real risk of soft-bricking while overclocking comes from if an overaggressive clock setting is permanently saved before a crash, which is easily avoided with reasonable care.
Using an overclocking kernel (Suckerpunch ftw!) that also allows for undervolting helps diminish excess heat somewhat. I've run Stability Test and Neocore stress-tests for an hour each at 1.4GHz undervolted, reaching 45 degrees C with no issues. My typical use patterns seldom put that much load on the phone though, so I'm not worried.
slayp00n said:
thats 45C so about the same as mine.
Click to expand...
Click to collapse
i remember mine going upto 48 C.
diablo009 said:
i remember mine going upto 48 C.
Click to expand...
Click to collapse
That's why we like to overclock our phones here in Winnipeg- helps keep us warm at night
You probably got drunk and dropped your phone
Sent from my SAMSUNG-SGH-I897 using XDA App
I thought you bailed on the captivate cl?
Sent from my SGH-T959 using XDA App
Wow that's serious; mine never really gets that hot though, even when I'm charging and using a lot of applications at the same time. It gets to around 44C max; ruccintg 1.2ghz.
But yea I think something might have been wrong with the phone; of course undervolting helps as well and Im' sure that's attributing to my phone staying cool 80 percent of the time.
I think it's more to so with the radios. My phone isn't very overclockable and it freezes long before the chip puts off heat. My phone gets hot running navigation and charging at the same time. it also has gotten hot with roms that suffer from battery drain. I doubt that the battery drain is ever cpu related.
Sent from my SGH-I897 using Tapatalk
The phone would have froze up and crashed before hot enough to crack screen.
:
clemmie said:
That's why we like to overclock our phones here in Winnipeg- helps keep us warm at night
Click to expand...
Click to collapse
LOL......probably need all the heat you can get this winter my Canadian friend....stay warm!
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 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.
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.
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
Don't overclock that high. 2419MHz at most. Overclocking too high will cause more heat and throttle earlier, only useful for a short benchmark such as HWBot Prime or Quadrant (Antutu takes longer and will overheat by the time it finishes). Trinity also supports up to 3014MHz, OP hasn't been updated.
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
You don't want to push the phone too much I think the Nexus 5 runs at 2.3 GHz. 2.7 MAY not be too bad but honestly, the phone runs pretty smooth as is. What benefits are you looking for from overclocking?
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
if you really wanted, the phone won't explode if you run it at 3015mhz either. the worst that will happen is that your phone won't be able to run that high, and will freeze and reboot.
and don't listen to all.. run your phone how YOU like. yes, it'll cause a little(not much) more heat, and will throttle a little earlier, but that's why people like me disable throttle, so that's a non issue. I run my phone at high CPU speeds all the time, and use 2880mhz high/300mhz low quite often. just because I feel like it, no other reason.
oh, I run trinity as well, and do all of Trinity's testing
MaLing15 said:
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
Click to expand...
Click to collapse
It's just what @jsgraphicart said. You're not really getting more out of your phone by overclocking. It's not going to run smoother, and most games don't lag anyway so they probably won't run better. I think most people just do it for benchmarks or just to check if it can run on a certain clockspeed.
Also what @simms22 said. You can do it if you want to, but simply because you want to because as far as I know there aren't really any benefits.
Back in my Palm Pre days, we used to overclock that thing to 1GHz. The default setting was 500MHz. I think it was even pushed to 1.2GHz. And it ran fine. But back then, you could tell the difference between a little lag at 500MHz and smoothness at 1GHz. With this phone and how Android has gotten smoother with every update, it's kind of hard to see any difference when overclocking. It will be smooth regardless.
oh, benefits, not really. a little more speed, yes. bit I would never call it a benefit, unless the speed difference was drastic, and its not.
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
bblzd said:
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
Click to expand...
Click to collapse
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Lethargy said:
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Click to expand...
Click to collapse
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
simms22 said:
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
Click to expand...
Click to collapse
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Lethargy said:
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Click to expand...
Click to collapse
on some devices??? on most devices! anyways, stability is overrated
LOL...no explosions on XDA allowed!