Hi guys,
Im noticing that when I have my navigation on for 15 mins or so,
thr screen and the back (around camera) gets noticeably hot.
is this normal?
try ingress - hot in 5 minutes
yeah, it's ok. try don't place phone not in direct sunlight though
Related
*repost from PPCgeeks*
This just started happening within the last couple hours. I haven't recently installed/uninstalled ANYTHING, haven't messed with any settings, no reg. edits, nothing at all. When restarting, I notice that sometimes it takes longer that it usually does to load my today screen. I'm noticing no differences in RAM at startup. I notice, for example, going back and forth between tabs on HTC home, the phone will freeze for a couple seconds and resume working normally after that. When receiving a phone call, it takes FOREVER for it to respond when trying to accept or deny the call. While in a call, it responds terribly slow when trying to raise/lower volume. Sometimes going from portrait to landscape and vice versa even takes longer than normal. I've had ZERO problem with my Mogul since I first got it 4 months ago and now I'm ready to throw it out the damn window. What's the word guys? I can go on about a couple other things that the device is slowing on, but I think you guys get the picture. TIA.
On another note, I first noticed it doing this when I plugged the device into my car charger. After that, regardless of being on battery power or external power, it was sluggish like never before. I noticed today, my battery died faster than usual. About 1.5 hrs ago, it was at 40% charge, and within less than an hour it dropped down to 10%. I had data turned off all that time and I still noticed the battery drop as well as hotter than normal backplate. Could it be something with the power source? I remember once, quite awhile ago, my phone totally died and after I charged it for a bit and turned it back on, it ran the same way, hhhmmmmmmmmm.
i've got the AC in my room on at 23*C and.. my phone got to 39*C haha..
tethering + charging + making a skype call on fring makes for a really hot battery.
Not sure about Celsius but Fahrenheit 109 degrees
109 = 42c, quite hot, the point is that the battery need to stay as cold as possible, there's a very good thread about battery somewhere but for some reason it doesn't seem to have been made sticky
P00r said:
109 = 42c, quite hot, the point is that the battery need to stay as cold as possible, there's a very good thread about battery somewhere but for some reason it doesn't seem to have been made sticky
Click to expand...
Click to collapse
Yea I was using the hell out of it on 3g and downloading while charging...
I'm trying to get it up to 150... blow the thing out my hands....
I don't know actual numbers, but I was in the car on a hot day... it was plugged into a charger, giving Navigation directions, and I was using the 3.5mm jack to play it through my car stereo... and for some reason (heat or cause of the 3.5mm jack) it started playing music and skipping all over. Was really annoying because I was nearing my destination and really needed to pay attention to all the turns it was giving me, and the damn thing was skipping every 3 seconds from one song to another, pausing to give a direction, skipping to another song, skip, skip, directions, skip, skip, skip, skip... directions.
I got where I was going, had to circle the block because of a missed turn. Picked up the phone and the screen did not respond, the phone was almost too hot to hold (wasn't in the sun any of this time but I also don't have AC). The screen seemed to respond but the whole system was very slow. Took over 10 seconds for a response. I had to remove the power cord and pull the battery. I left the battery out for 10 mins while I went inside my destination. Had the phone in my pocket and my pants were on fire. But I put it back in and it booted fine.
TL;DR Too hot to handle!
Mine got hot enough in the car for the screen to stop responding as well.
I believe I got it to 119*F at one point. But now it tops out at 113*F after driving with nav and music for about 30 mins.
I have no clue how hot it was but driving down to Baltimore and using my N1 on the windshield for GPS in a 95 degree day. The phone got hot enough that holding it hurt.
53.3C/128F with GPS on, on a 100F day
nexous one
my phone got 151 degrees F
and it was on the car doc charging in the sun and its fine
Ive got you all beat...
I was running eVils ROM OCd and forgot to scale it down for charging...
Running Google Nav and charging under the sun and...whammo!! phone shut itself down and would not reboot until it cooled off. I couldnt even hold the phone in my hand it was so friggin hot.
All is good now....
joshlusignan said:
Ive got you all beat...
I was running eVils ROM OCd and forgot to scale it down for charging...
Running Google Nav and charging under the sun and...whammo!! phone shut itself down and would not reboot until it cooled off. I couldnt even hold the phone in my hand it was so friggin hot.
All is good now....
Click to expand...
Click to collapse
Thats intense. Surprised it didn't say "phone too hot" or something.
Mine has reached 45c. I have that at my threshold and setcpu throttles it down to 600~mhz.
does anyone has this kinda problem?? i noticed that every time the temperature id hot, my HD2 is also warm n then comes the lagging problem. but after i turn it off for a couple minutes or to let it cool down, it's working just fine after it's back on.
"BUMP" 10 characters???
Ok. This is extremely wierd.
So unplug my phone off the charger in the morning use it a bit. 1hr later I feel it burning a hole in my pocket. Its extremely hot, I take it out and try turning it on but the screen wont turn on. Battery pull and its fine.
Go to battery history and the battery life vertical dropped 15% in that time.
Happens 1 to 2 times a day. Any idea whats wrong?
Thanks
No matter on which kernel I am ,stock/franco/semaphore etc... When I play heavy games like asphalt8 ,nfs mw and GTA VC my battery drains like hell ,and then the % stuck and not going down for about 30 minutes. Here is an example:
Had 25% ,launched NFS MW and played for 5 minutes on low brightness. After 5 minutes showed up on my screen the low battery notification ,4% left. Resumed the game and after 20 seconds my phone showed "Shutting down".
It happens everytime ,no matter how many cycles I'm doing. Another example:
Yesterday I had 69% ,played GTA VC for a couple minutes and boom ,35%. After that I surfed in the web ,listened to music in Soundcloud ,and did a lot of things with screen on and battery was stuck on 35% for about 30 minutes. Launched NFS MW ,played about 2 minutes just to see what happens and boom - battery droped to 25%.
It happens only when I play heavy games. Please help me ,what can it be? Tried many roms too ,same result. Now I'm on stock JWR66Y with stock kernel.
thats normal behavior. when using the device heavily, battery drops faster. unfortunately, our battery stats are 100% accurate. when the battery drops fast, actually showing a little more battery used than it actually used. so what you are experiencing is the bounce back affect. what its doing is making itself accurate again. sometimes after using the battery alot and fast, if you let it sit there, the battery % will rise, kinda looks like its being charged without plugging in.
simms22 said:
thats normal behavior. when using the device heavily, battery drops faster. unfortunately, our battery stats are 100% accurate. when the battery drops fast, actually showing a little more battery used than it actually used. so what you are experiencing is the bounce back affect. what its doing is making itself accurate again. sometimes after using the battery alot and fast, if you let it sit there, the battery % will rise, kinda looks like its being charged without plugging in.
Click to expand...
Click to collapse
Ok ,got it. But what is the explanation to situation like I described here:
"Had 25% ,launched NFS MW and played for 5 minutes on low brightness. After 5 minutes showed up on my screen the low battery notification ,4% left. Resumed the game and after 20 seconds my phone showed "Shutting down".
Then I turned on my phone and battery % was 10 ,and stuck for a couple of minutes on 10.
davidbar93 said:
Ok ,got it. But what is the explanation to situation like I described here:
"Had 25% ,launched NFS MW and played for 5 minutes on low brightness. After 5 minutes showed up on my screen the low battery notification ,4% left. Resumed the game and after 20 seconds my phone showed "Shutting down".
Then I turned on my phone and battery % was 10 ,and stuck for a couple of minutes on 10.
Click to expand...
Click to collapse
our battery stats inaccuracy.
sometimes, when benchmarking at high cpu speeds at 70% battery left, for example, and the phone crashes, itll boot back up and show that theres 20% left(for example). then if you reboot the phone again, it go back to 70%. or if you let it just sit there at that 20% with the screen off, youll notice it slowly "charge" itself without being plugged in. this happens often. and happens on every single android phone starting with tge originally released g1. yes, our battery status is just very inaccurate and inefficient. youve probably heard of people experiencing the rlod(red light of death). this is also a good example. sometimes the phone itself creates a situation that itjust thinks that the battery fell below 0%(which creates the rlod issue). and when people get their phone up and running again, itll show 50, 60, 70%..
simms22 said:
our battery stats inaccuracy.
sometimes, when benchmarking at high cpu speeds at 70% battery left, for example, and the phone crashes, itll boot back up and show that theres 20% left(for example). then if you reboot the phone again, it go back to 70%. or if you let it just sit there at that 20% with the screen off, youll notice it slowly "charge" itself without being plugged in. this happens often. and happens on every single android phone starting with tge originally released g1. yes, our battery status is just very inaccurate and inefficient. youve probably heard of people experiencing the rlod(red light of death). this is also a good example. sometimes the phone itself creates a situation that itjust thinks that the battery fell below 0%(which creates the rlod issue). and when people get their phone up and running again, itll show 50, 60, 70%..
Click to expand...
Click to collapse
It's so annoying ,I'm getting crazy with that.
Anyway thank you @simms22 for your answer and your help ,appreciate it.
:good: