Related
HI all, I am new to android
Followed the excellent tutorials in this forum and upgraded to 2.2 using a file downloaded directly from a HTC link (sorry cant find right now)
Everything is superb but the gps cant get a fix. It has been a few days and I tried various things like restarts, remove battery, clear sky, leave google maps running for long, checked it is enabled in settings etc.
What to do?
What should be the correct version information after the 2.2 update? (in case i installed a beta/incomplete version)
Please help this new droid get back on its feet
I am sorry I have no solution, but I have the same issue. This has nothing to do with 2.2 I think, because it happened all of a sudden. At least it felt like it happened jus like that. I have been using 2.2 for a long time and used GPS. Only recently I noticed the issue.
from my post here http://forum.xda-developers.com/showpost.php?p=7773080&postcount=9
It worked for me! I went to the roof as today is a bright day and used Tricorder app's Geo tab. Touched on it to show satellite.
It kept trying to connect to satellite. The tricorder app shows some satellites as green. Presumably as they are chosen to calculate location. It didn't finally lock-on till it was showing 12 satellites and 4 of them were green. I noticed that I had to remove the jelly cover and :
1. Stand still, she how many satellites it shows signals. In a few seconds it will stop detecting new ones.
2. It it hasn't locked on then move around a bit and change some orientation then step 2 again
3. Repeat above till it latches to atleast 4 green or 12 total signals (dont know which one works the 12 signals or 4 green)
and after that it easily updates even indoors for me.
I usually get a fix in the first minute, usually under 30 seconds. But this time no satellites were showing, not even after 15 minutes. I switched roms and it's working fine again.
I think I must have messed up something by reflashing multiple times. (I was trying to get the bios boot image to work, but sadly no avail )
I've just updated to voda standard 2.2 rom OTA this morning
1st thing I've noticed is the gps is a no go, no sats in view at all.
(using gps test the 'on button' only stays yellow too)
I've not 'messed' with my phone at all other than the standard updates
I must admit I've not tried a hard reset yet but I think that's going to be the last hopeful resort otherwise it's going back for a replacement
Although I have been doing a lot of reading the last few months, I am new to posting, so please bear with. My DINC just started randomly rebooting about 2 weeks ago and I am trying to figure out why. It was running great before with (rooted) Skyraider 3.0 RC3 Vanilla, kings BFS#5, S-Off, 2.15 radio and HBoot .79. The problems began when I installed Juice Defender, didn't really like it, and then un-installed it. I did not disable anything JD did before un-installing. Now, with the same set-up as before, I get random reboots when I'm on Explorer for a few minutes, when GPS Navigation is on, and then randomly on GChat and the Market. It seems to happen more when the temp is higher, but it's rarely over 100 degrees F. Half of the reboots end up in QualComm debug mode. I have tried a full wipe and reinstalling the ROM, kernel and prior settings. The only thing I can think of is that Juice Defender changed some type of setting, application or system, and now it's having fits. I downloaded aLogCat and had it running during the last reboot and can PM the .txt file if you think that would help. Does anyone know what's going on or how I can fix it? Any help is great appreciated!
Also, the current applications that I have are:
ad-free
advanced task manager
beautiful widgets
setCPU
amazon reader
scorecenter
Mint.com
switchpro
bump
battery indicator
astro
root explorer
rom manager
barcode scanner
facebook
goggles
dspmanager
handcent
linpack
metamorph
mixing
papertoss
pandora
shazam
spare parts
tapatalk pro
titanium backup
weather channel
widget locker
BUMP....anyone?
mjmdmd said:
BUMP....anyone?
Click to expand...
Click to collapse
Are you overclocking? Some phones can't handle much and it's known to cause similar problems. Other than that I'm not sure if anything JD changes would remain once it's un-installed; but if so you might install it again, change everything back to stock, then un-install it. Just a guess, hope you get it figured out
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
SynbiosVyse said:
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
Click to expand...
Click to collapse
Same here. Exchanged it with Verizon, almost no questions asked. Got AMOLED refurb, so far so good. Replacement was with OTA installed though, so waiting for new root.
You should revert your phone to fully stock, turn S-ON, unroot, stock ROM, etc. Make it look as legit as possible. If your problems go away then obviously something got screwed up in the flashing process. If your problems remain, then it's something wrong with the actual phone, and since you just made it completely stock you're in the perfect shoes to go exchange it.
In summary, the best measure to take if you're having reboot problems is to exchange it at a Verizon store; that's what most people are doing.
I'm going to exchange mine tomorrow. It should be covered under the 1 year warranty so you should not need insurance to do it.
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Sounds to me that you have the faulty overheating 3G radio..it is a somewhat documented problem and I believe it's the same problem I have. The only solution is to swap it at a verizon store. I'm afraid other ROMs or anything else you do will not solve the problem.
mjmdmd said:
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Click to expand...
Click to collapse
Odds are your radio is failing, which is a relatively common problem. Your symptoms are pretty much a textbook example and something that I experienced firsthand on my previous Incredible. The only fix is a warranty exchange.
That's disappointing. Thanks for the info everyone. I guess it's time to start the process of unrooting...
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Miltos1 said:
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Click to expand...
Click to collapse
Interesting. I'm using the big batt too, but my only reboots happen with GPS. As I'm driving (unfortunately) with my Nav on, all of a sudden, I look to see what my next turn is, and I'm on the "HTC Incredible" splash screen! Most annoying thing ever.
I'm still waiting for a fix. I really don't want to unroot, lose everything, and have to exchange for a warranty phone.
By the way, with a fix like this, I feel like my blackberry days again!
Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.
have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?
I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.
Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App
There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?
Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.
Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).
It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.
I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.
I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.
It happened to me many time already. I still use stock htc desire rom and never rooted..
I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?
Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward
I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing
Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...
This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this
Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.
Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy
I've been running the only official lt28 JB firmware for over a month now on an LT28at with AT&T as the carrier. Overall pretty happy with it, haven't noticed any 'day 1' bugs accept for the video recording lag (which for whatever reason is phone playback only? on my pc, through vlc, all the video's look great.)
However, only July 22nd, Google released the updated maps app....and things have kind of gone south for literally anything gps related ever since...
The issue is tricky. After i installed the updated maps app, my phone froze on the map screen while searching for a gps signal. After about 5 seconds, the phone rebooted...but it wasn't a full reboot it seemed...it only took another 5 seconds or so before i was back at the lock screen. If i hadn't been physically looking at the phone, i never would've noticed it happened. Before this update; i had never encountered this problem.
After the kind of 'mini' reboot thing...no matter what, any gps related app (my tracks, gps status, Torque Pro, etc.) would do exactly the same thing. If i turned the gps off or never used a gps related app, the phone would function normal as ever...after manually rebooting the phone by either a full reset, or just turning the phone on and off...the gps would function normally again...I could get a lock, could use any of the apps, etc...
after a few hours, though...it would freeze up on gps stuff again, and get into the same boot loop issue with any time the gps sensor was used.
I've tried rolling back maps, but the problem remains...and i'm kind of stuck now...I'm positive this showed up with the newest maps update, as i had been using JB for a while before it and never had any gps problem of any kind...
what i've tried so far:
flashed an AT&T ICS firmware back...gps functioned properly for 2 days without a single problem. because this is an LT28at, pc companion cannot do a repair for this firmware. I get a 'we couldn't find any software for this device' or something of that nature. I've wiped everything through flashtool, and reflashed multiple times, without any form of back up data. I'm not rooted anymore, as i wasn't crazy about the rooting method for JB to begin with. figured i'd just wait for the time being.
tried 2 different .ftf files of the same JB firmware...both have the problem.
clearing cache of any gps related app i have doesn't seem to effect anything.
the only thing that seems consistent is that the problem only starts happening after the phone has been on for a few hours. If it try gps after a fresh boot, it works perfectly. If i try again a few hours later, most of the time it freezes and quickly resets, but keeps doing it non-stop until i shut the phone off.
is anyone having anything like this? Any help would be greatly appreciated...
EDIT: this can be marked as solved i guess...found info on other phones with 4.1.2 having similar problems...something to do with memory allocation and the adreno 220 gpu...rooting and running a memory tweaker/task killer (greenify or autokiller memory optimizer both worked) has been a good enough work around for the time being...hasn't happened once since i switched autokiller to 'aggressive' memory management...no gps problems, and not one redraw...phone is actually running better than new now haha...
I recently updated my unrooted phone to OTA Kitkat and in hindsight wish I didn't. The GPS that worked flawlessly in 4.3 is no longer locking with the satellites( at max 3 or 4 fixes) and Navigation has become useless. I installed GPS Status and performed the usual steps(reset, get xtra data) to get a lock but several minutes would pass by before a single satellite was found. This was done outside under a clear sky. Has anyone run into this issue after the update? Any advice is appreciated.
Not sure why that might be happening.
Especially on a unrooted device.
I assume you don't have a custom reovery or anything like that either correct?
I would first try going into the recovery and wiping cache and rebooting.
Sometimes if old data is held there I remember that causing issues on my vibrant a while back.
If that don't work you might need to try a master reset of the phone and see if that fixes the problem.
If you are worried about loosing app data you can get Helium Backup from the market and backup apps and their data.
Just needs a computer to trigger it at first that is running windows, since you are not rooted.
TheArtiszan said:
Not sure why that might be happening.
Especially on a unrooted device.
I assume you don't have a custom reovery or anything like that either correct?
I would first try going into the recovery and wiping cache and rebooting.
Sometimes if old data is held there I remember that causing issues on my vibrant a while back.
If that don't work you might need to try a master reset of the phone and see if that fixes the problem.
If you are worried about loosing app data you can get Helium Backup from the market and backup apps and their data.
Just needs a computer to trigger it at first that is running windows, since you are not rooted.
Click to expand...
Click to collapse
Thanks for the suggestions. Here's what I did since I didn't want to reset the phone. I downloaded GPS Test and went outside in the Minnesota cold and waited for satellite fix. After 13 minutes, the phone found 7 satellites. I hopped into my car and started google navigation and drove for half an hour from work to home. Everything worked fine all the way home. An hour later I wanted to see if the GPS issue was truly gone and to my dismay after waiting for 10 minutes it didn't get a fix. This is really a bummer that the KitKat upgrade did something to the GPS functionality that it's taking so long to set the gps location compared to the 20 seconds under 4.3
I will give another try tomorrow and then will probably factory reset and start anew.
samaruf said:
Thanks for the suggestions. Here's what I did since I didn't want to reset the phone. I downloaded GPS Test and went outside in the Minnesota cold and waited for satellite fix. After 13 minutes, the phone found 7 satellites. I hopped into my car and started google navigation and drove for half an hour from work to home. Everything worked fine all the way home. An hour later I wanted to see if the GPS issue was truly gone and to my dismay after waiting for 10 minutes it didn't get a fix. This is really a bummer that the KitKat upgrade did something to the GPS functionality that it's taking so long to set the gps location compared to the 20 seconds under 4.3
I will give another try tomorrow and then will probably factory reset and start anew.
Click to expand...
Click to collapse
Something is amiss in 4.4.2 GPS. I had the same trouble, although with GE 4.4.2 ROM and not the official OTA.
What I did was to restore my original 4.3 ROM (dbombROM) followed by restore of GE, wiping cache and dalvik cache both times. I can't explain why that helped. But it restored my GPS function. While I was not able to get a lock for many many minutes, I get a lock now within few seconds (10-15 seconds may be).
Note that when I went back to 4.3 ROM, the GPS did not work in 4.3 either, while it was working fine just before upgrading to 4.4.2... So, lot of mystery there! But try restoring 4.3 ROM and restoring 4.4.2 again.
---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------
Oh...you said unrooted. Most likely you don't have nandroid backups of previous ROMs. Sorry man!
I'd try the faster fix app: https://www.google.com/search?clien......1c.1.37.mobile-gws-hp..1.8.789.USXOSBGtK7o
Sent from my SGH-M919 using XDA Premium 4 mobile app
samaruf said:
I recently updated my unrooted phone to OTA Kitkat and in hindsight wish I didn't. The GPS that worked flawlessly in 4.3 is no longer locking with the satellites( at max 3 or 4 fixes) and Navigation has become useless. I installed GPS Status and performed the usual steps(reset, get xtra data) to get a lock but several minutes would pass by before a single satellite was found. This was done outside under a clear sky. Has anyone run into this issue after the update? Any advice is appreciated.
Click to expand...
Click to collapse
Glad to hear that I am not the only one. This is my 3rd replacement phone already. The first phone was completely replaced because the battery was overheated and drained within 3 hours. The second phone was replaced because of the GPS locked issue. The third one which is the one I am using right now is having the same issue. I noticed the issue after I did the OTA from 4.3.
I also noticed that if GPS cannot be locked, pull down the menu, either switch off turn back on the airplane mode or the GPS will immediately patch the problem. It's just an inconvenient when you need to reach at the phone clipped at the windshield from the driver seat when cruising 70 mph without a long hand or worst... need to do that in traffic packed road.
I almost got the same issue before. I just rooted the phone and flashed the custom rom. Now it works