i was driving w/ my captivate plugged in the docking system (charging) and with my nav. on paired w/ bluetooth gps receiver. Blutooth also was connected w/ my head set and I was talkign on the phone. this multitasking was going on about for 30minutes... when i took off my phone from the docking, it was very hot, so i checked the battery temp. it said 57C.... It had gone upto 45 C before when I did stability test for about 45minutes but never this hot before... Did i just cheat death and never do this stunt again? or it can survive this high teperature?? I normally listen music via BT and sometimes use nav. at the same time... so I wonder it I can continue to do that or not. fyi I'm on FF 2.5 w/ stock kernel.. not oc/uv'd
Thanks
It won't certainly be healthy for your battery though... I know what you mean though. It's having Bluetooth on and GPS turned on at the same time that seems to drive my temperature up as well (and it's really hot summer here).
I try not to use GPS on it for too long, I get a bit paranoid :/
Related
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS?
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?)
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?)
How much battery does it suck down?
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Can't really comment on accuracy, but it has me plotted on the correct roads on Google Maps and MS Live Search.
GPS reception is fine in the car, although initial satellite lockings seems faster when I put the phone on the dash. After that, I can pretty much put the phone anywhere near the drivers seat.
Takes a minute to a couple minutes for me to get a fix.
Its sucks batteries fast. Slightly faster then the trickle charger is charging the phone. So on a long drive, I imagine you will kill the battery on the Tilt using the GPS.
Don't know about the last question.
Braingears said:
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS? :iterally its pinpointed me w/in 5 ft
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?) In the car its fine, dont have woods here in miami, but in the everglades it works just fine.
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?) approx 10-15 s
How much battery does it suck down? Dont know, I dont have it on for a long time
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Click to expand...
Click to collapse
Havent tried that yet, meaning using google maps & windows live?
I've only had it working for a short time, but based on what i've read its fairly accurate (someone got it within 15', mine was within 30' but that was google maps and i dont think it does off-road)
I established the connection on my porch (so i could use my wifi) and it followed me inside the house. 9 satellites outside, 6 in my chair. its a small house, but still nearly completely obstructed due to rain clouds and being indoors
If you use a program like GPSTest or GPSViewer to establish the connection first, they go very quickly. otherwise it may run into some problems connecting due to the timeout settings.
battery power no idea...
As mentioned earlier, i try a light weight program to establish the initial connection and the actual program to use it. from what i've seen you can see two but not sure how well it'll work n the end.
hey i got my tilt, I really don't know how things works, I mean I installed live search on it, but you know I can't get the current GPS postion, how does this thing work? anyone? can you guys tell us the steps for those of who are new to this whole GPS thing, thanks
redpoint73 said:
Its sucks batteries fast. Slightly faster then the trickle charger is charging the phone. So on a long drive, I imagine you will kill the battery on the Tilt using the GPS.
Click to expand...
Click to collapse
I noticed this too.
Is there a way to fix this?
It is very annoying.
With a car charger I should be able to at least keep the battery at the same level.
(PS: I am using a car-to-USB adapter and the USB/Sync cable that came with the tilt)
Back when I was using the att flash, I'd need to use a program to jumpstart gps. It'd take about 2 minutes. Afterwards, I could use google maps without issue. But if I drove around, I'd constantly be losing the gps and need to hit retry.
Then I flashed to htc. Google maps always picked up the lock in about 10 seconds. I'd still lose it if I drove around.
But then a few days ago, google maps stopped picking up gps. Even using other programs, I'd run it for over 10 minutes without getting a lock. Haven't gotten gps working at all in the past few days. Not sure what's going on. Hopefulyl a future firmware will fix this. Not going to bother with it for the time being. Being able to use google maps is really enough. gps is pretty silly to me.
Braingears said:
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS?
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?)
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?)
How much battery does it suck down?
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Click to expand...
Click to collapse
Accuracy -- I can't speak as to "within x meters", but I can tell you that when using it with mapping software, the location fix is right on the money as to where it shows me being in the car.
Length of time to obtain a signal -- after the initial "fix", I can open my mapping software and in the length of time it takes to select my destination, it has already paired with the GPS chip.
Battery Life -- I keep my Tilt on the car charger when using GPS -- at least, I did until a few days ago. I forgot to plug it in to the cigarette lighter and the battery was dead running the GPS constantly in 5 hours.
Multiple apps at once -- Can't comment on that one.
When I use telenav , most of the time it is accurate close to about 15 feet.
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
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 ?
When I try to navigate with SatNav app the battery overheats and then doesn't charge. Eventually the phone dies.
The first time I discovered this I thought I was going to be stranded and lost. Very fortunately I had AirCon in the hire car and I was able to jam the phone in the cooler vent fins!
It's worst with Sygic, which appears to be a very intensively written SatNav program. It's also the only one I have that I can use abroad with offline maps.
I've tried Waze and Google Maps but even these overheat it after an hour.
What to do? It's the same with a Mugen battery and the same with a Samsung battery. Taking off the back helps a little but not by much.
This is a deal breaking nightmare. Why do SatNav apps even have to have any display anyway?
How's about underclocking? I'm on Semophore 1.2.5 at the mo with the 333 ICS rom which I was thinking of upgrading to v2 of the ROM when I have a spare day to mess around getting everything working again.
Alternatively, if there is no way... would a Motorola DroidPro do a better job (I have one spare)