Related
Im running drods 1.5ghz kernel set at 1.4ghz and bamf 1.3 with extended battery. at idle the phone runs around 87. But when performing simple tasks like streaming music through bt or using kik it quickly gets up too around 108. Is this normal should i be worried? My incredible oced too 1.2 would never breach 100 even if i was throwing everything at it.
sent from somewhere
108 is not a bad temperature don't sweat it. I usually set my safety profile for 120.0
I has an overcloked d1 running 1.25ghz constantly running between 105-115. Zero problems and my friend is using it a year and a half later as his phone.
I would recommend you use a setcpu profile to bring the overclock down while charging too. Phone gets hot while charging.
Sent from my ADR6400L using XDA App
I use a wall charger for my battery's. ive also noticed it only really gets this hot with the radio on with kik running in the background or any small task really. On wifi it cools right on down. weird. Thanks for your input
I don't really pay to much attention to the battery temperature (maybe I should?) But I have seen it range from 84F - 102F when glancing at the battery stats.
I'll easily get over 100. But it's also 90 outside anyways. It does seem to get hotter than other phones, I don't know why. Using current widget I can see that it pulls a lot of mA.
I don't run much under 85 all the time.
Ya i live in florida its starting to get up there. Guess ill live with.
sent from somewhere
I had the Tbolt in the car the other day (gps mode) when i undocked it it was really hot / checking i saw it at 55C (131 F) / Usually its bet 28 and 34 C
Mines 88 @ work right now surfing on 4g 66% battery left according to setcpu off of newest bamf and the new kernal. Room temp is about 77... CPU set to smartass haha I love this stuff I have not touched my awesome custom built by me gaming pc all weekend aside from rooting my tbolt
I'm overclocked to 1408. My GPS is on along with wifi. Just finished Playing a game (Geared) and my temp is 96 degrees.
Sent from my ADR6400L using XDA App
My phone was idle for a while, picked it up was 80. Opened internet and came here after a couple posts 90.
105* under heavy usage
87-95 depending on how heavy usage is. Never above 100 for me. (Extended Battery btw)
Running the TB @ 1.2ghz and I get a usual of 25-35c.
my phone idle while charging with wifi on is 35 celcius.........i cnt find Fahrenheit on my phone anywhere -__-
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
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
recDNA said:
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
Click to expand...
Click to collapse
It looks like that most people that end up with this problem (sleep of death, blank screen of death, or whatever you want it to be called) were either underclocking to low or undervolting to low, some governors have also been the culprit on some devices. Not all of our thunderbolts are the same, guess solder joints are weaker or something that makes this such a random problem. Your best solution is to try different kernels, cpu settings, and governors to find out what your phone likes. I personally haven't had this issue with eternity. However, some others have! Good Luck
Yes, what the above poster said. Like for my phone it does not like smartass gov. It will work but the screen will freeze as you have experienced also. Also overclocking, i can overclock to 1.7ghz but will also freeze randomly as you experienced.
Sent from my HTC ThunderBolt using xda premium
I think (but could be mistaken) this is more like the opposite of black screen of death. I believe that is when the phone wont wake from sleep.
My problem occurs only when phone is awake and being used heavily. The screen isn't black nor blank - I see whatever screen I am on when it happens: lock screen, an app, home screen, keyboard, etc. I see all the icons but screen becomes totally unresponsive to touch. Wide awake.screen but no matter how you tap, slide, or use capacitive buttons nothing works.
Only way out is to pull battery or hold down up volume, down volume, and power key simultaneously to force a restart.
There is someone out there who understands this phenomenon better than I and can suggest approaches but I must be clear - this is.not a black or blank screen and doesn't occur when clock speed is low.
I would.guess cpu is operating at full 1 ghz when screen freezes occur in my tbolt. I am not overclocking at the moment but I do believe overclocking makes it worse but not sure.
Mine was doing that at being underclocked too low keep it at say, 368 mine never did it again, also don't undervolt too much it can cause phone to power down. I use ondemand and keep you lowest speed to 368 and you should be fine. Using battery saver mode for kernel in speedtweak may be undervolting your phone to much if you are using that.
Try this kernel working great for me. http://db.tt/QqkRvtjm jdk newest kernel.
Sent from my ADR6400L using XDA App
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That might be the case if we all used the exact same set up. We don't some change fonts, some use different apps, and there are so many variables.
Nothing unusual going on in my tbolt. 1.0.9 cubed with no unusual apps or settings. I seldom add.an app to my bolt unless it has 1000's of downloads in the market with high ratings. I learned that back before I rooted. I bet someone who writes.kernels understands this phenomenon and could point me in the right direction. Imagine if your computer was bonked up and advice was to randomly try changing settings?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That sounds more like your phone doesn't like whatever voltage is set for your top end frequencies. Might want to try IncrediControl from the market and increase the vdd levels a little. I think a lot of the kernels floating around are under volted a little. Could be the cause.
Sent from my ADR6400L using Tapatalk
Its worth a try. I never tried that. Thanks.
You say it only happens when using your bolt, maybe the processor is just maxed out. How long do you wait to see if it comes back around?
I have waited as long as 10 minutes but usually ibjust restart within 30 seconds based on experience. Once "frozen" it has never recovered on its own.
What's interesting is the processor is still working whilebthe screen becomes unresponsive. I know this because I was streaming a r radio into a jawbone earpiece and when I switched apps the screen froze yet the radio continued to play. I HAD to restart to stop the music since the screen wouldn't respond to touch.
I flashed Imo's lean Sense Kernel and haven't had a freeze yet. I hope this has solved the problem. There is a little lag now when I hit a widget or app shortcut but no more freeze.
Your lag is prob due to being in safe made, put in normal mode in speed tweak to rid yourself of lag.
Sent from my ADR6400L using XDA App
No, I'm in standard mode. I chose #1 in speedtweak. I varified at 1.4 ghz max/ 254 min
I couldn't figure out how to raise min value in speedtweak so I reinstalled set cpu and set min to 368. Seems to reduce the lag.
Still a slight lag but most importantly no screen freeze since installation.
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
mkitchen said:
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing a stock ruu in fastboot? You may try to go back to completely stock and then go from there. You could try a different rom too and wipe the system partition as well as the usual stuff first.
Sent from my ADR6400L using Tapatalk
I went back to the stock ROM using clockwork mod recovery, and the problem persists. I am wiping system partition now, but I did some of the stuff that has worked for me in the past such as dalvik, user data, and cache.
Wiping system may help but if that doesn't I'm not sure what else for you to try except fastboot flashing an ruu.
Sent from my ADR6400L using Tapatalk
Actually wiping system worked, I may have not done it in the correct order the first time I tried to flash back to stock. I really appreciate the help.
Hello!
I just installed Titan Kernel (over ThiaiZO3D V2.7.1) and i'm feeling my O3D a little more hot than usual.
The temperature now is 36.8 c / 98.2 f.
Sometimes it gets to 40 c +.
What is the normal temperature for this cellphone?
Thanks a lot!
I m having 26c now.
Sent from my LG P-920 using ghost call method...
without using the phone too much mine usually is below 30ºc (rushdroid @ 1.2ghz), currently it's at 25.6ºc . but i've seen it go high as 42ºc but usually only when gaming...
Dont worry about it. The phone will shut off when it gets too hot.
Sent from my LG-P920 using xda premium
I've seen mine reach up to 42 c when gaming. When idle, it should be around 26 c. Light - Medium use can get up to 36 c.
The max temp I've had is about 46 whilst charging and gaming with the cpu maxed at 1.4ghz with apps in background and i coudnt get it any higher, tried too though.
Btw that is only battery temp anyway isn't it, the cpu may be a bit cooler.
Alright guys, thanks a lot! I was almost going back to the normal kernel because I thought the phone was overheating, no I would just forget about it as long it doesn't get too hot.
Sent from my LG-P920 using xda premium
Just remember that even if your phone runs fine at a higher temperature, it will reduce the life of what ever is running at a high temp.
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.