GPS issues suddenly with OG Transformer. - Eee Pad Transformer Q&A, Help & Troubleshooting

So I picked up a refurbed Transformer about a month ago. I rooted it a few weeks ago and everything has been okay. A few lockups here and there, but I was running a custom kernal so whatever. Then a few days ago my GPS starts searching all the time. This was a few days after installing the .21 rooted update. I put GPS Status on it, and it worked for a while. It started up again yesterday, so I flashed an old backup, it worked, until I rebooted. To try and keep it short, it seemed that yesterday if I flashed a new ROM or backup, it would work fine, until I rebooted the device. Well, while trying to NVflash, my recovery got borked so now I'm back to pure stock.
I've tried it on stock .19, .21, rooted, unrooted, let it sit for 30 minutes. It will sometimes pick up 10 satellites with decent signal, but will not get a fix. After the first couple of flashes yesterday, it took about 5s to get a fix.
I've tried:
Clear cache/Delvik cache
Flashed backups
Nvflashed back to stock unrooted
GPS fix, GPS Status, GPS test from the market.
It's just odd that with no changes it went from great to bleh. Any help would be great. Sorry about the book.

jasonwuzthere said:
So I picked up a refurbed Transformer about a month ago. I rooted it a few weeks ago and everything has been okay. A few lockups here and there, but I was running a custom kernal so whatever. Then a few days ago my GPS starts searching all the time. This was a few days after installing the .21 rooted update. I put GPS Status on it, and it worked for a while. It started up again yesterday, so I flashed an old backup, it worked, until I rebooted. To try and keep it short, it seemed that yesterday if I flashed a new ROM or backup, it would work fine, until I rebooted the device. Well, while trying to NVflash, my recovery got borked so now I'm back to pure stock.
I've tried it on stock .19, .21, rooted, unrooted, let it sit for 30 minutes. It will sometimes pick up 10 satellites with decent signal, but will not get a fix. After the first couple of flashes yesterday, it took about 5s to get a fix.
I've tried:
Clear cache/Delvik cache
Flashed backups
Nvflashed back to stock unrooted
GPS fix, GPS Status, GPS test from the market.
It's just odd that with no changes it went from great to bleh. Any help would be great. Sorry about the book.
Click to expand...
Click to collapse
I had this problem too... I fixed it by modifying the gps.conf file to use some US Navy ntp servers instead of the stock ones... get fix within 20 seconds the first time, and like 1 or 2 seconds rverytime after that... pm me and I'll send it to you... You're rooted right??

^^^The force is strong with this one.^^^ Thanks!

Related

No signal since root

Hi Guys,
I rooted my Desire S last night with the help of Alpha Rev, I'd originally only planned to install the standard HTC rom so i could get rid of all the crap Orange stick on the phone BUT it wasn't that easy.
Alpha went through fine and so did the root, once done i ran the image from the HTC website i found here http://forum.xda-developers.com/showthread.php?t=1002506 (first one in the list) and this installed ok but then i suddenly lost mobile signal, the wifi was fine but no mobile network. After 20 mins it appeared but then promptly went again 30 seconds or so later. This happened on and off for 20 mins so i decided to go back to the standard Orange rom and have another look. Again i downloaded it from the above link but this time got the Orange rom, now the same thing was happening on this one. I started to panic at this point! I had a search around and noticed some people thought it could be to do with the radio. So i downloaded the correct radio and tried again, still the same, signal on for 10-30 seconds then goes.
As a last ditch attempt i downloaded this rom - http://forum.xda-developers.com/showthread.php?t=1122797 installed and now all is fine? I don't understand why it keeps loosing signal on the original rom yet on a cooked rom it works fine!
Thanks for reading, I'm quite new to all this so any help is much appreciated.
Thanks
coz cooked rom is better
also u can try this one
http://forum.xda-developers.com/showpost.php?p=15800407&postcount=151
its shipped+root so u can remove all bloatwarez
Thanks dude, i'll give that one a go tomorrow morning.

No signal for 1-2 secs

Hi everyone! So I got G2X last week and the first day it worked great. It shipped with 2.3.3 on the device. Ended up rooting it and flashing a custom 2.3.3 rom, followed by Cyanogen mod nightly 2.3.5. Now, next day was my first day back at work and for some weird reason my signal would drop completely for 1-2 secs followed by device re-acquiring it and everything is fine again... super annoying and results in crappy data . Basically 4G/3G completely turns off, same goes for the radio, then its back to normal, anywhere from 2-4 bars usually. Any ideas?
That happened to me on CM7 aswell. I'm not exactly sure what causes it, but I haven't had any problems on the stock ROM.
I usually just have gps locking issues
We had a new Guy start today and he's gone the same phone on 2.2 though, doesn't seem as if he has same issues.
Are you just running stock rooted rom now?
FatalityBoyZahy said:
That happened to me on CM7 aswell. I'm not exactly sure what causes it, but I haven't had any problems on the stock ROM.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

[Q] How are your reboot issues?

I didn't have any when I first got my phone, right at release. About 2 weeks in I started to get the freezing/reboot issue occasionally. It went away for a time when I started modding my phone with ROMs. I'm currently running Weapon G2X, and for a time had no reboot issues. Now, about 3-4 weeks into using that rom, they are becoming a problem. My G2X now seems to reboot once every couple of days or so, normally when I'm using the phone. I'll be in messaging, hit back, then it locks up and reboots on me.
How are your issues? Still having them or no? I plan to update Weapon sometime in the next couple of weeks, or perhaps give CM7 a go.
Just got mine from CL last week. Have yet to experience a reboot or freeze. Maybe it's just a few batches of G2x's that experience that.
mine hardly ever freezes up to be honest. I am using xboarders tweakd GB rom. But then again, I've never really had an issue where it just reboots itself even before rooting. my phone does sometimes run really slow though.
running_penguin said:
mine hardly ever freezes up to be honest. I am using xboarders tweakd GB rom. But then again, I've never really had an issue where it just reboots itself even before rooting. my phone does sometimes run really slow though.
Click to expand...
Click to collapse
Really? Slow-ness should definitely not be an issue with this phone. Have you tried Weapon or Cm7?
I've only had one reboot and I had this phone for 5 months. I got a reboot when I was showing my friend. How fast and cool my new phone was. He asked to see it then he pulled down the notification bar and it just rebooted. Other then that one time, never happens.
Sent from my LG-P999 using xda premium
One freeze and one reboot on a stock rom in a month.
Sent from my LG-P999 using xda premium
What reboot issues?
Never had it happen after 5 months of owning the phone.
Stock, rooted, Go launcher ex, SetCPU -> almost no reboots.
Before those steps, quite a few reboots per week.
Sent from my LG-P999 using xda premium
I've been trough various roms and had the stock froyo in the beginning for quite some time - never had a reboot or a freeze. Only once, I remember, it would not recognize the headphones that I was plugging in and I had to reboot.
I've only had my phone reboot once when messing with SetCPU. Other than that, no reboots. I got my G2x within a week of it coming out and have never exchanged it.
i'm using pure stock so i'm not sure if you want my opinion but i've had the phone for a month now. it was perfect in the beginning with zero issues but up until last week it's been freezing constantly and rebooting. i've had to do three battery pulls and it's rebooted on me three times. and i thought i got lucky with a "perfect" phone i really want to try exchanging it but i'm afraid to get an even worse one and i am not paying 20 bucks to get a refurbished phone that's insane
U should flash newest weapon room, this is great room and will fix reboot bug
I used to get freezing and rebooting all the time several times a day on stock froyo but ever since I started going on nightlies since around #60 I think it was, I rarely have reboots... my wife got the phone on the same exact day and she's still on stock rom with no issues
Running stock since I got it a month ago. No reboot issues. The only freezing issues I have is when I try to use ANY screen capture app. I managed to get one of them to work...once. After that, back to freezing. So as long as I don't use any screen capture apps, I have a smooth working G2x, lol.
I got 2 g2xs. One of them got reboot issues. Called T-Mobile and got replacement and no more complaints. All is good now. Last fewweeks I got flashaholic buy. Flashing different rom every 2days.
Stock Froyo rooted. Used to get SOD freeze and reboots every week. Started daily shutdown/restarts a few months ago - never had either problem since.

[Q] Skyrocket freeze/shutdown on signal loss

Hi. Let's get right to it, shall we?
I was running a 4.3 Rom on my phone. Worked great while I was at my house though I did notice my signal seemed lower than before I installed it. But I didn't worry about it too much. Ran the Rom all weekend without any issues. Coverage in my city is pretty good, so I never had a signal drop.
I work in a pretty rural area of PA which causes me to lose my signal a couple of times while commuting there. So, on Monday when I got to work, I had a blank screen and all buttons were unresponsive. I did a hard reboot which went fine until the phone tried to reconnect to the network. Then it went back to the blank screen and forced another hard reboot.
Thinking this was an issue of cm10.2, I went home and reloaded a 4.2 Rom. Again, it worked great until the next day when I returned to work. Then the shutdown/freeze issue arose again. So I went to stock 4.1.2 with stock kernel and radio. No extra apps, nothing. The only thing custom on my phone was the recovery. Anyway, I still had the same problem.
As long as I don't lose my signal, my phone works awesome. And it's not the loss of signal that's bad, it's when the phone reaquires the signal that it breaks. I went to AT&T and discussed with a rep but I seemed to know more about phones than he did ( his words, not mine ) and I couldn't reproduce the problem because, of coarse, there was a perfect signal at the store.
So, I'm asking for thoughts, ideas, and suggestions on how I might fix this problem or what might be wrong. I respect and appreciate, any help I might get from this fine community. Thank you all in advance.
So when you say after you went to stock the only thing custom was a custom recovery ...
Odin a ucmc1 stock the one which also takes you to stock recovery and do your wipes from there.
See if this resolves the issue
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Commodore 64 said:
So when you say after you went to stock the only thing custom was a custom recovery ...
Odin a ucmc1 stock the one which also takes you to stock recovery and do your wipes from there.
See if this resolves the issue
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
How does the recovery effect the phone when it's on normal and not in recovery mode? Please ( and this isn't sarcasm ) Talk to me like I'm four years old.
Mine did something like that also, I was on CM10.2 20130920 Nightly clean install with TWRP 2.6.3.0 and everything was fine then phone froze and started vibrating, camera flashed, power button wouldnt do anything I pulled battery and reinserted it and same thing just vibrated. Finally was able to go to DL and reinstalled stock booted just fine I set up the phone and couple hours latter same thing phone locked up started vibrating and nothing.
I know it is recommended to use CWM 6.0.3.7 but figured the lates TWRP would work. Now I have a worthless Skyrocket that all it does is vibrate, I can take the battery out and use it as paper weight.

g930a keeps crashing after about a few weeks of a reload

I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.

Categories

Resources