Related
Someone help if possible! My GPS on my Tilt was working perfectly with Google Maps and LiveSearch... but today i turned it on and it's locking onto a position about 500+ miles away. I have VisualGPS installed and it now is only locking onto a max of 3 satellites (but sees many more satellites) when it used to lock onto about 6+! It also thinks i'm at 57,000 feet and somewhere over the gulf of mexico when i'm currently in south carolina on a trip! I tried soft resetting about 5x and ran QuickGPS a few times as well... nothing has fixed it. Any suggestions?
did you install anything new or do anything major like settings or drop the phone?
Nope...it was working fine one day, and not working the next... phone wasn't dropped and no new software was installed and no settings were changed. Not sure if the chip is malfunctioning or not...but it does lock onto a location... the wrong location.... but it is consistently putting me in somewhere in alabama at the moment
Hi UTZorro
I can't really help you with your problem but I did notice on mine the other day that the satalites would drop in and out quickly and never lock onto more that 3. It was a very clear day with clear view of the sky. The co-ords were out by quite a long way because of it. The DOP was never very good. I restarted and it seemed to solve the problem but it wasn't a good sign. I know I hadn't dropped mine and the quickGPS data was current.
I also noticed that the voice in tomtom was all over the place.. I had to reinstall tomtom to fix the problem and put the voice on the main memory. At the time I thought it might be my 4GB SDcard but now I'm not so sure.
Dylan
Hi
Have you tried leaving it on for several minutes? GPS on these sorts of devices make several assumptions as they try to lock on quickly so you don't have to wait, sometimes that initial lock is wrong due to these assumptions. Either turn it on and leave for it around 10-15 minutes in clear view of the sky or try running QuickGPS, that may help.
I've had this happen now and again, just leaving it for several minutes to get a "proper" fix and all is well.
Regards
Phil
I saw the same problem, i was driving and according to my gps i was going 485 km/hr and i was "flying": above the sea. kept the copiliot log as thought it was funny
I rebooted my kaiser and it went back to normal
This randomly happens to me also on a Stock HTC rom. Not too often though so not a major problem.
Reboot fixes it ...
I had the same problem last week. I Soft reset the device and removed the battery before it booted back up. After about a minute I put it back in and it was OK again.
happens to me as well, soft reset solves the problem... also if you have your GPS app on your SD card removal fixes this as well, very peculiar problem
PhilipL said:
Have you tried leaving it on for several minutes? GPS on these sorts of devices make several assumptions as they try to lock on quickly so you don't have to wait, sometimes that initial lock is wrong due to these assumptions. Either turn it on and leave for it around 10-15 minutes in clear view of the sky or try running QuickGPS, that may help.
Click to expand...
Click to collapse
I second this: I had strange behavior after a lockup and it took several tries with 10minute or so open-sky accesses to clear up:
http://forum.xda-developers.com/showpost.php?p=1650269&postcount=31
Go sit on a park bench for 15 minutes or so with the GPS on and open in an app which shows the satellites in view - like TomTom/Mapopolis/whatever and see if you don't eventually get back up to the 7+ birds you normally get.
Good luck!
Richard
recently this error has been happening more frequently to me with TomTom, restarting doesnt seem to fix it all the time anymore... does anyone know what causes this? It constantly showes me somewhere in Ontario, Canada about 500 miles from where I actually am.
Is there a way to disable and re-enable the GPS chip via software similar to what a hard-reset does but without the 30 seconds+ downtime associated with the hard-reset?
This is being caused by Quick GPS. If you have not connected to the internet via Activesync for a while then when you first start your internal GPS or lose sat coverage it diverts to the last stored Quick GPS data for the most prominant 3 sats (they show up as full signal when you look a gps data in you mapping SW) that should be in your area.
Either sync at least every 5 days (on a PC with T'internet connection) or disable quick GPS and be patient for a lock.
Hope this helps.
Hi
I had the same problem, but it seems I found a solution.
I'm not 100% shure, but for what I remember I had this problem very often. like every time I was starting navigation it was wrong, so I had to soft reset - Everthing was fine - till next time when it was wrong again - and soft reset and again, again and agian.
It was so annoying - then on a Polish forum a guy wrote somethign about downloading quickGPS data (what he read here) and quickGPS was the solution, but for me it was to disalbe every sync function - because I set to sync evertime it was possible I believie that was it.
Now I'm using kaiser for about a week and testing it 2-3 times a day. and it never failed. I'm not 100% shure it was it - but it looks fine now.
So after a few days after I originally posted with this problem, it noticed it had spontaneously fixed itself after my flight back to town and I pinpointed what fixed it. (keep in mind i have stock Tilt Rom, QuickGPS was updated at the time (about 25x to be exact) and I had even hard resetted and it didn't fix it)... but here's what did fix it interestingly enough:
So, for some reason, if you have flight mode enabled on the phone, then you turn on the GPS (which I admit I did while bored midflight wondering how high up we were) it MAY get messed up like what happened to me. The only way to fix it is by putting the phone back in flight mode turning the GPS back on and then turning it off again and re-exiting flight mode. I have no idea why flight mode and the gps would be related in this siutation (it makes no sense to me)... I didn't believe it myself until I repeated this experiment twice!!! So, i'm posting this for reference to anyone who may have the same problem in the future if their phone was in flight mode and their GPS got activated and then subsequently messed up! Any thoughts?
I have noticed that my kasier seems to loose time. I will check the current GPS time and by my trusty watch (lol) and then set the time on the device. A few days later or so and the time on the clock on the device has lost about 10 mins! Anyone else have this issue?
Aside to this, does tha kaiser auto update the time from the service provider or from anywhere else?
I had exactly the same problem, seems the time difference between my home computer and work computer was to blame. I had it sync the time at home but not at work.
At least it gave me an excuse for being 20mins late on Monday
Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.
For the last few weeks, my AT&T Note 3 has started randomly rebooting. It can happen when I'm viewing email, when the phone is in my pocket, or even in the middle of the night when it is just sitting recharging. The rebooting is roughly once per day: somedays more than once, other times it can go over 24 hours. The problem seems to have started after I updated to 5.0. I have tried a factory reset, but the problem came back. I called AT&T support and they said that they've had a lot of problems with Samsung devices after the 5..0 roll out, with random rebooting, or the Bluetooth failing, or the WiFi failing. They said that they need to replace the Note 3, but because it is over a year old I must pay $100 for the replacement through Asurion (I have been paying the insurance fee).
Searching on line has not provided much on this problem. Does the AT&T comment make sense? If I need to replace the phone, shouldn't it be for free because the problem was caused by AT&T?
I'd appreciate any comments.
Note that I realize it could be related to an App I use being incompatible with 5.0, but I need to use my phone for work pretty much constantly, so troubleshooting which one (if any) is not practical.
Mine started doing the same thing about a week ago. Till then it was not having any problems with the 5.0 version.
They need to figure out the problem and push out a update. Otherwise it is like they don't care about us, unless we go out every year and buy a new phone !
Problem solved?
After trying a reset and cleaning checking the battery contacts didn't work, I looked for other patterns. It seemed to me that one of the most common times it rebooted was when I checked my email with the K9 email client - something that is always running in the background, and could have caused it to reboot when on charge overnight.
I uninstalled K9 and that didn't help - the phone rebooted after about 9 hours. However, since that reboot it has now gone nearly 48 hours without rebooting. Maybe I was right about K9 and uninstalling it wasn't enough - I should have also manually rebooted the phone.
The phone has been rebooting at random times, sometimes as short as about 5 hours apart and sometimes more than a day apart. It could be that right now I'm at one extreme and it will reboot randomly today. But if it makes it through tomorrow morning without rebooting then K9 was probably the problem.
It has now been over 72 hours since the last reboot, which does suggest that the original problem was the K9 email client, crashing and forcing a reboot on the phone after the Android 5 update.
Problem NOT resolved!
A few minutes ago, roughly 76 hours after the last random reboot, when I thought that the problem was resolved, I heard the reboot tone coming from my phone that was sitting on the table.
So, while removing K9 reduced the frequency of the reboot, it did not solve the underlying problem.
Use Titanium Backup and backup all user apps and data. Factory reset and reflash stock if you want to take the extra step. Use standard Google and Samsung apps for a while. Do not restore accounts or system data automatically. Removing and reconnecting accounts and clear data for an app in app manager are always good quick troubleshooting options. Restore apps as you need them, if you really need them. Favor stability over extraneous features.
.......................................................
Galaxy Note 3 - AT&T (sm-n900a)
Since I removed K9 and rebooted the phone, it has only rebooted randomly once in 5 days: this was at 72 hours, and now it has been up for 65 hours since then. Trying what you suggest would take weeks, given the current frequency of random rebooting. Plus, my phone is used for work constantly - I couldn't get by with just the Samsung and Google apps built into the basic phone image.
For the moment, I will just live with the phone as-is and hope that Samsung issues a new version of 5 soon.
Now at nearly four days since the last crash/reboot, or only one in seven days. At that frequency, it is certainly not worth the effort of trying to track down the secondary cause (it could take months), now that I know that K9 was the main problem.
It has been a while since I started this discussion, with no conclusion. The phone still randomly reboots - only once all of last week, but then it woke me up on a reboot at 4:30 am this morning, and rebooted again while I was checking Facebook at 7 am.
I'm having a rebooting issue as well with my Note 3. It started about a week ago and will do it many times during the day. I have tried wiping the cache partition, doing a factory reset and the other day I downgraded the software from 5.0 to 4.4.2 and rooted it and froze the over the air update from AT&T but still have random rebooting. I have had the reboot issue with and without the SD card installed so I know that is not the issue either. I was thinking it was a software issue so that is why I did all of the stuff listed but now I'm wondering if it could be hardware. I guess I'm just at a loss of what to try know and was hoping someone on here had any suggestions.
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
jeffp25 said:
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
Click to expand...
Click to collapse
It happens both when charging and when sitting unplugged. I even tried swapping the battery for a new one and the contacts and also clean
Well, it was an idea. I did the same thing, buying a new OEM battery and hoping it would help. It didn't. But then again, mine often reboots at night (it woke me up at 4 am this morning), so I knew it was unlikely to be a battery issue in my case.
Yeah thanks for the idea but it seems like I'm running out of things to try
I feel the same. The only thing left would be to wipe out the phone and try it with nothing but stock, non-upgrades, apps. But I use the phone for work, and it can go more than a week between reboots (or less than a day), so that isn't practical.
I might just end up mailing my phone into Samsung to be repaired but now that I have it rooted is there any special steps that need to be done to unroot it? I was just going to do a factory reset and let AT&T android 5.0 do it's update if that will kill the root. I'm not worried about warranty since it is no long under warranty.
Maybe use logcat and letting it run and wait for a reboot to happen so you can see what is going on. However the logs could get big and it might not capture what happens right before it reboots.
After the update a few issues have risen. I've attempted to search for solutions for each one, with no avail.
These are issues that never happened before the update, and started right on the next day.
1. Audio apps close when locking the screen.
When I have a podcast running (on beyondpod) and I lock the screen from the off button, the app will either keep running, or close.
I have found a few questions like this on here and other forums, but none with a definative answer.
I've done a few of the suggestion, like cleared the cache. But is there an actual solution to this?
2. Bluetooth turns off/loses connection to my pebble 2. I think these might be connected.
While using a bluetooth headset, there are no issues. However I constantly (should) have my pebble connected to my phone. However, very quickly it loses the connection. It randomly finds the connection again randomly, but it wont stay connected for very long. Sometimes I catch my phone with the bluetooth turned off, however turning it back on wont neccessarily connect it to the pebble. I also tested out with IFTT, and everytime the phone cut the bluetooth connection it woul send me a notification. And it happened multipe times within the hour. Sometimes taking tens of minutes to reconnect, sometimes not reconnecting it at all.
3. Google Timeline (the thing that draws a map of where you've been and how you've traveled)
I used this to follow my cycling and walking, since step counters dont recongnize cycling very well or at all. However since the update the pages are all empty. It just wont recognize my movement at all. I later noticed that the location gathering accesses had been reset, but even after giving them access again there is absolutely nothing saved onto my timelines.
Please, if you have any ideas what is doing this, or any ideas how to fix one, or each of these, leave a reply...
If nothing else I'll have to rollback to Marshmallow... And I've really grown to like the split screen!
hi, having same problem as #3 on my brand new Huawei Mate 10 pro. did you ever solve the issue? thanks