My Milestone seems to have given up it's ghost.
I was driving along, tracking my position in google maps, and it froze up. After removing/replacing the battery, it will no longer turn on. No M logo, nothing. It was rather hot to touch at the time it crashed (OC'ed to 1ghz, GPS on, charging, GoogleMaps SatelliteView) so I suspect it simply fried itself. Bummer.
In some thread somewhere, someone mentioned to leave the battery out for a while so that an internal capacitor can discharge but no luck.
Anybody else run into this?
It may sound stupid but. Have you tried connecting the charger while the phone is off?
EDIT: the milestone always get very hot when running navigation or maps no matter what you do
Sent from my Nexus S using XDA App
I realized that your Milestone is overclocked to 1ghz. What ROM are you using?
It was running HO!NO! CM7.2.0-RC0 at the time, but since any CM-based rom will let you overclock I dont blame the rom.
I'm giving it 24 hours of no battery before trying again, pretty sure the battery had around 70% charge at the time it died.
shimbob said:
My Milestone seems to have given up it's ghost.
I was driving along, tracking my position in google maps, and it froze up. After removing/replacing the battery, it will no longer turn on. No M logo, nothing. It was rather hot to touch at the time it crashed (OC'ed to 1ghz, GPS on, charging, GoogleMaps SatelliteView) so I suspect it simply fried itself. Bummer.
In some thread somewhere, someone mentioned to leave the battery out for a while so that an internal capacitor can discharge but no luck.
Anybody else run into this?
Click to expand...
Click to collapse
It always get hot especially when it is charging. Good luck...
1ghz its not too much? XD im OC 800mhz max
Yay! It's back! Left it with no battery for 3 days and it powered right up after putting the battery in. Phew!
Bummer though, was looking forward to getting a captivate glide. oh well.
In the middle of September, I've added an option (in CM7 for Milestone) to automatically limit the max CPU frequency when the phone is in Car Dock.
It's there for a reason .
From the changelog (it's there since 7.1.0-RC15-11.09.14):
- added options to limit max CPU frequency when screen is off and when phone is in car dock
(When the phone is in car dock it can easily overheat as there is usually: heavy navigation app running, gps in use, battery charging, 3g in use, sun shining directly at phone behind front car window. All this together can lead to battery temperature rising above 50C at which point the charging is automatically stopped to prevent battery damage and you can end up with phone battery empty after some time despite phone being connected to charger. So the CPU freq limit for car dock is there to help with this temperature issue.)
Click to expand...
Click to collapse
kabaldan said:
In the middle of September, I've added an option (in CM7 for Milestone) to automatically limit the max CPU frequency when the phone is in Car Dock.
It's there for a reason .
Click to expand...
Click to collapse
Yes I use it, except in this case it wasn't in the dock, it was on my lap as I was the passenger.
Although I'm curious. I've disabled the dock observer (car mode just annoys me at the moment). I'm assuming a disabled dock observer means it doesnt reduce frequency when docked, right?
What ROM would be ideal to use with it ?
Related
So the other day, I forgot to close an app down--the Schwartz Unsheathed, if you are curious--and when I fished my phone out again, it was hot. Very, very hot. Battery information indicated 41C which, in the grand scheme of things, isn't that high (wouldn't worry me with a PC's graphic card, for example, or CPU) but it felt incredibly warm to the touch. Fine, I shut the app down, removed the battery cover and let the phone cool down. No problem.
It might be the apps I've been trying since then, but I have been experiencing performance and stability issues. Things slow down sometimes. On the Desire ROM, Rosie kept force-closing every now and again. On Enomther's which as we all know is just about the stablest thing that ever stabled, Launcher2 does ditto (the Launcher Dock may be the culprit, though, as it seems to do some weird **** and I've removed it since. Fiddling around with BetterCut also seems to cause force-closes). So could that be it? Did the phone overheat (but if so, shouldn't it have shut itself down) and now something's broken? Getting antsy. :/
41°C should not be a problem, but consider that this was a measurement from the battery pack and that a sensor like that can easily go +/- 5 to 10 degrees.
so well, some chip on the nexus could have gotten way hotter than 41°C. maybe something fried, some defect that was already there and now its really broken.
still, this can be a bit subjective, the phone will seem broken if you think it's broken you can always do a factory reset, reflash the current rom and try from there.
Yeah, could just be my own jitters--I'd experienced issues before, usually caused by a ROM or whatever--and lately my PC's been having problems, so it might well be some kind of placebo effect. Unless it and my N1 magically entered a symbiosis or something.
Thanks for the quick reply.
once my phone accidently fell onto my bed and under my pillow while i was charging it over night and i woke up at 4 am and found a burning out nexus under my pillow. i unplugged it and nothing seemed damaged but it still worried me.
I think if you are worried about it and you are rooted you should install SetCPU. It has a profile designed so that is you his a preset temp it will down clock your CPU.
I use setCPU to save my batterylife ie.
100% - 50% run full cpu on demand.
Idle/Standby downclock to 400Mhz
50% or less down clock to 600Mhz on demand
20% or less down clock to min.
I also complement this with locale for low bat. dimness, wifi off, bluetooth off. etc.. etc.. ( a little off topic I know)
Well, looks like updating More Icons Widget was what did it; things seem to work okay now.
Was wondering what the maximum advisable temperature is?
Maybe the phone has protection for the CPU? but Li-ion batteries dont like heat, it shortens their effective life.
my battery reached 44.3C yesterday on a 4 hour journey in the car using co-pilot and the phone actually net discharged despite the fact it was on a 1A USB charger for the entire journey - about 80% at start of journey and 20% at end.
I've installed setcpu now and set the temperature profile to drop the max speed to 768 if temp is >44C and another one to drop the speed if power is less than 30%, may need further tweaking though. This was not in my car and the back of the phone was effectively unventilated, in my car I have an open backed holder near an air vent.
hey guys,
I got my car dock a couple days ago and started using it day 1.
impressions:
its sexy but a little hard to move around (prob cuz its new)
but i have a major problem with the nexus one heating up to almost 120 degrees Fahrenheit! and this troubles me cuz i dont want my battery to lose its charge capacity.
and if im on lets say 50% battery and i drive somewhere for 10-15 min using the navi on the car dock
the temp shoots up to 115-120 and the charge goes down to ~30%
anyone else having a problem with overheating while in the car dock?
i used it during the day and night (only to check if the sun was affecting it)
no change in results
i used it with every option on the power control widget off
i ran Advanced task manager and ended all apps before launching navigation
im considered a tech whiz
so ive put this thing through its paces
and they only way to not have my phone burn hotter than the atlanta summer sun is by turning the screen off and listening to the navi...not veiwing it while its on charge and keeping all wireless options and sync off except GPS
ideas greatly appreciated....
oh yeah
rooted n1
running cyan 5.0.6xx if its any consolation...
and its not undervolted...(problem? but then what about non rooted phones)
EDIT:
oh and today
after using the n1 and removing it from the car dock the screen was not responsive. couldnt use it to navigate
has to reboot the phone
I also noticed my Nexus heated up to 40-42 degrees C while using GPS with Screen on for 15 minutes. Burning hot.
no one has any problems?
ive been noticing its msotly because of the sun that it gets scorching hot but at night it does rise past 115 degrees F
120 degrees fahrenheit (49 degrees celsius) is not very hot for computer parts. The reason it reaches those temperatures I guess is because of google maps (if you used that for navi). When you use google maps it's almost constantly using your data connection and that is one of the most battery intensive tasks if I remember correctly.
Oh and I wouldn't classify a little over 40 degrees celsius as burning hot, I've been to places hotter than that, but I guess it's subjective
Seems that overheating is mainly an issue for those running Cyanogen's ROM, no?
My N1 can get hotter than 50 Celsius in under 10 minutes. It's really a bit frightening. I have noticed, however, that this ONLY occurs when the battery is not near full. Turning the screen off seems to help cool it down (more testing needed). However, turning off the screen doesn't help when you need it for gps.
I am using cyanogen, but not the cyanogen kernel. Overheating occurs both in sunlight and at night. I believe it occurred while not running google maps as well, but I can't remember for sure.
I've had no problems, but I did notice how hot it was. I figured it was because of the sun since I had it mounted on my window glass.
SBS_ said:
When you use google maps it's almost constantly using your data connection and that is one of the most battery intensive tasks if I remember correctly.
Google maps only uses a data connection when it initally pulls down the route information and when it needs to recalculate the route.
You can put your phone into airplane mode after the inital pull and google maps will still function as expected (Except it will not pull down new maps if you stray from the path).
The issue is that you are trying to charge the phone and use it at the same time. The mechanism for doing this charges the battery and depletes the battery at the same time, this makes a really hot battery.
Keeping the screen off when its not needed in the dock and you will have less heat issues when you need to charge your phone in the car dock.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Devastatin said:
SBS_ said:
When you use google maps it's almost constantly using your data connection and that is one of the most battery intensive tasks if I remember correctly.
Google maps only uses a data connection when it initally pulls down the route information and when it needs to recalculate the route.
You can put your phone into airplane mode after the inital pull and google maps will still function as expected (Except it will not pull down new maps if you stray from the path).
The issue is that you are trying to charge the phone and use it at the same time. The mechanism for doing this charges the battery and depletes the battery at the same time, this makes a really hot battery.
Keeping the screen off when its not needed in the dock and you will have less heat issues when you need to charge your phone in the car dock.
Click to expand...
Click to collapse
yeah this car dock i am really getting mad at
i wasted 60 bucks for something that heats the hell out of my phone
i listen to music so loud the bluetooth speaker isnt loud enough to tell me where to turn when the screen is off so...
i guess ill try out enomthers rom with the UV kernal and report back
the major cause of it is the sun
because at night the phone doesnt go over 100 degrees F when using the navi
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Does anyone having this problem use "set cpu"?
I had a the same problem because my cpu was set to 998 during charging. so then I had the three main things that cause heat ganging up. battery, gps and cpu. All i did was set the cpu to 806 while charging and the heat problem went away...
I imagine that the stockers don't have this problem because they are under-clocked...
The main problem is the sun. I have Rodriguez's rom with the overclock and the only thing causing it to heat up is the sun.
Setting the CPU lower I will try but on setcpu I don't set it to userspace anymore. Its set to ondemand and no profiles set. Ill set a profile for overheating at 120°F to max 806mhz
-------------------------------------
Sent via the XDA Tapatalk App
NEXUS ONE
So, I took my Nexus One for a spin using Google Turn-By-Turn navigation and it was like a 25 minute drive and when I got home, the phone was really hot, to the point where i was afraid this thing may be close to being fried on the inside. The touch screen wasn't working properly (not responding to touch and being very inaccurate than normal). I left it on the desk and after 5 minutes it cooled down again and was fine.
What the heck is wrong? is it cause I kept it on the dash board against the dials, that area was kind of warm but nothing to heat up the phone that much, should I be using a cradle or something?
Its a fully stock Nexus with 2.2.1 FRG83D, not rooted and no other apps running. Same thing happened with the free program MapDroyd, so it isn't Google Navigation only issue either.
I don't use GPS much, but when I first got it, I did and it was fine. After about 9 months though its started getting pretty warm, within minutes of using 3g, roughly 38degrees celcius (about 100 fahrenheit), but apparently it's been tested and works fine up to 57 celcius (134 fahrenheit) or something like that.
it's not the gps .. it's the turn by turn navi.. it uses massive amounts of CPU that is what heats up
It is a number of factors, including the previously stated turn by turn navi. You also have the screen on permanently, plus at least where i live, anything in a car not in an air conditioning stream is going to heat up a lot.
I suggest getting a setcpu widget or some other temperature monitoring widget. I also set my cpu to underclock when it gets above 48 degrees C.
Heavy CPU usage, GPS probably generates some amount of heat, but mainly it also adds to the battery draw which adds heat. Screen is on, and you're possibly also downloading quite a lot of data unless your maps are entirely offline.
Also, your phone might be sitting in the sunlight, or in the winter might have the vents blowing over it.
So just the GPS? Not really. Run GPSTest sitting on your desk. You'll see significant battery usage (probably adds 120mAh to what it'd normally use) but it won't get hot.
Yeah, turn by turn navigation does seem to heat it up a lot, even when caching the map offline entirely on a Wifi network beforehand. My phone isn't rooted, but maybe I'll root it and use setCPU thanks.
Will actually heat up more if plugged in. Although mine never gets past 115 or so and this is with GPS and music playing.
Not Sent from a pc/mac
I only have 5 widgets, and my brightness is also low as possible. I have wifi off when i don't use it, but my battery still dies kinda fast. Should i delete cell standby? And what else can i do?
You really should define "kinda fast" so folks can answer objectively
Well just playing games like angry birds for 20 minutes it drops like 10%
EverythingNook said:
Well just playing games like angry birds for 20 minutes it drops like 10%
Click to expand...
Click to collapse
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
HotShotAzn said:
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
Click to expand...
Click to collapse
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
EverythingNook said:
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
Click to expand...
Click to collapse
What drain are you seeing with screen off/idle?
with the screen off for about 5 hours i saw a 21% drain.
Drop the widgets and livewallpaper if you've got it. Retest standby.
If you're getting high battery drain during standby your nook isn't going into deep sleep and chances are that background overhead translates to poor efficiency at idle when the nook is on as well. Couple poor idle efficiency with CPU intensive work while in use and your overall battery life is terrible.
If you're forcing the nook to stay out of deep sleep for other reasons like keeping wifi alive then you may be stuck with living with some sort of elevated drain but you can minimize it by reducing idle overhead by keeping widgets to a minimum and refraining from using live wallpapers and other background services that aren't critical.
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
distortedloop said:
Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running.
Click to expand...
Click to collapse
If you suspect it, disable it and see. I'm thinking that would be a prime suspect.
distortedloop said:
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Click to expand...
Click to collapse
I believe typically overnight you should see less than 10% drain.
In CM7 at least, in Spare Parts you can see what uses the battery while the NC is asleep.
distortedloop said:
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
Click to expand...
Click to collapse
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
No, not yet. It's 100% stock, other than rooting and downloading apps. I'm going to put SystemPanel on it and see if it gives a clue.
I've got a good idea of how to track down battery issues on most android devices, I was just mostly curious what the typical drain other rooted users saw was.
Thx for the suggestions to all.
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
Good lord, this isn't going to help anything. Normal Nook Colors on the stock ROM (and kernel....) use about .2%/hr in standby.
Clearly something is running wild on this guys NC, and needs to look at Spare Parts. Install it from the market.
System Panel as well as other tools can help as well.
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
distortedloop said:
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
Click to expand...
Click to collapse
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Extra deep. Two stages...
First stage 5 pins, second stage 12 pins...
Sent from my Nexus One using XDA Premium App
Yup same cable as my Droid2 and Droid before it....
Krazypoloc said:
Yup same cable as my Droid2 and Droid before it....
Click to expand...
Click to collapse
Does this mean we can use the droid2 and droid's cables as alternatives?
khaytsus said:
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Click to expand...
Click to collapse
Thanks for the extra info about the additional voltage; so it will charge much faster this way? (rhetorical question)
I still am annoyed at yet another non-standard cable that I'll have to carry around with me when I travel to keep various devices charged, but in the scheme of things it's a minor annoyance. Stuff like this should be standardized, IMHO.
And it's extra DEEP, not wide. It's the same width as a standard micro-usb cable or I wouldn't have been able to stick my phone's charging cable into it at all, but I was able to, it just didn't go in deep enough to charge at all. On the flips side, the B&N cable fits into my phone, but only inserts half-way deep; if it were extra wide it wouldn't fit into my phone at all.
Hi,
I've tried to search for a solution but haven't find any. You know there is a message when battery temperature gets too high then charging stops. The popup message is very very annoying: I use navigation and blackbox while driving. And when this message comes I have to press OK, and 5 secs after it appears again... very very annoying.
I agree with not to overheat the battery but why not just stop charging without this message? Is there any trick to eliminate this? In summer time and sunny days this msg comes very often. I have to place a piece of plastic to car's ventillation hole to minimizing the chance of this msg.
I don't care if it's charging or not, I just don't want to see this msg.
Please help if you have any idea!
I'm on stock JVR now, rooted, underclocked @ 800MHz. Other ROMs (CM7, MIUI) just stops carging without any message.
Had the same problem awhile back,reflash jvr, and dont use undervolting/overclocking programs/kernels.
faria said:
Had the same problem awhile back,reflash jvr, and dont use undervolting/overclocking programs/kernels.
Click to expand...
Click to collapse
+1 Dont OC/uV too much.
My apologies guys, but please read: I don't use OC/UV, I use stock and underclock.
With normal use and simple charging everything goes well but under heavy use I get this message while charging. Under heavy use I mean navigation, blackbox, and of course phone is at the windscreen while heated by the sun. The phone's glass is hot. It's normal of course because I use CPU intensive apps.
I repeat: I don't care about charging or not, just want this message to be disappeared.
I just unplug mine from the charger when this pops up. It happens with me in exactly the same circumstances. GPS navigation, dashboard of the car, and bright sunny days, it's not an overclock issue, just high ambient heat source, high cpu usage plus charging.
I also find it's aggravated by the silicon skin case I use.
PhilPassmore said:
I just unplug mine from the charger when this pops up.
Click to expand...
Click to collapse
Yes I'm doing the same as workaround. But other ROMs just stop charging and continue when phone cooled down without any message. It would be very nice to just remove this message by a script or editing a script or something else (I'm not a dev just an "I-like-to-hack" power user).
DO your devices get extremely hot at all? Mine did ,to the point that it was to too hot to handle, im surprised the dam thing did not exploded.
As for removing the message i have not a clue how too, i do know however that is is triggered by the thermal sensors.
I can also recall this happening with my windows mobile devices a few times,this happened when the gps services were stuck working in the background.
In all occasions the only fix a found was to re flash the rom.
faria said:
DO your devices get extremely hot at all? Mine did ,to the point that it was to too hot to handle, im surprised the dam thing did not exploded.
Click to expand...
Click to collapse
No, it's not too hot, it's just warm enough. I don't say it's abnormal because in direct sunlight while charging and using cpu intensive apps it's normal. Just try to figure out is there any chance to do this all without this message...
Ok, I'll wait for someone who knows something or know someone who has seen someone who know something...
Referring to other threads I'm not the only one with this problem and not SGS is the only one with this problem.
While this message is not needed and has no function it has to be eliminated some way because tapping OK is very disturbing while driving/navigating/etc...
Script? Kernel patch/hack? Something? If some ROMs can do it (like MIUI) there must be a way to have it disappeared...
I had the same problem with a Galaxy S II today. First, it began to warn me that was starting charging. And 1 second later it warn the Power Saving was activated and the charger was turned off.
Later, it said 'Charging pause. Voltage too high'. When I've tried to power off the phone, it was powering on by itself.
During the morning, I've used the phone to consume battery. At the afternoon, I put it via USB cable and it seems the problem is solved, for now.
I'm using the ICS ROM beta, by Samsung, have some days.