I'm using CM7 on my Nexus One. The issue happened twice; right now the GPS is working fine but I'd like to find what can be done to diagnose this, or if there's anyone out there who already knows a fix...
Here's what it looks like:
I turn on the GPS, open GNavigation (or Waze, or Maps). GPS gets a fix but when I start driving, it doesn't update my location. After a while, it loses the fix, the reacquires it, still doesn't update it, loses fix again, and this keeps happening as 5-minute long loops.
Here's how it looks like in the GPS Status app:
It's as if GPS gets a fix, then hangs (my coordinate are not updated in GPS Status app) without giving any errors, then turns itself off and on, gets a fix again, rinse and repeat.
What I tried:
Reset and download A-GPS state. Reset dalvik cache using recovery. Reset A-GPS state, turn off GPS, turn off phone, turn on phone (and variations of this). Didn't work...
What worked:
Finally I got sick of it and took out my real GPS device. I didn't turn off nexus' navigation (wanted to torture it a bit out of spite and frustration).
After driving for 40 minutes (and nexus finding, losing, finding ... GPS fixes as I was driving), suddenly it got a fix, and it just started working again without problems.
Anyone know what's happening here and how to fix it? Thanks so much in advance
You are not alone
Rebooting almost always fixes it for me. Unfortunately it takes several minutes.
Airplane mode also instantly fixes it, but then you lose A-GPS and all communications.
Radio updating may fix the problem.
Try flashing a latest radio image.
Latest radio
Thanks. I guess a new, functioning radio would indeed solve the problem.
However, I already have the latest radio flashed: 32.50.0032U_5.12.00.08 for the Nexus One. Earlier radios have other heavy shortcomings, so they are not a good option.
i wold know if it was good be4
cuz it was worked fine but now ive same problem
i thought this problem form rom
but now i dont know the reson
sorry 4 broken eng
thx
I am waiting for ICS and hope that will fix it.
I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.
BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0
Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.
Up
Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.
Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.
Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.
I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV
Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.
I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.
Hi, a few months ago I've noticed that when I try to turn on bluetooth (which is usually turned off) everything freezes the moment I 'click' on the turn on/off switch. After the freeze it takes around one-two minutes to restart the phone and then I can normally turn the bluetooth on.
The strange thing is that I can turn it off and on then and it will work, but when I turn it off and leave it off for a few days, and then try to turn it on the phone will freeze again...
Did anyone had the same issue?
Android version: 7.0 (B394)
I installed B395, but the problem hasn't gone away. Anyway, for the first time after this 'freeze' the message box saying that 'the interface app stopped working' showed up and I could 'stop' the interface app.
However, the update did not solve the problem.
Same problem here did you find a solution?
Same problem here for years! Android 7.0. Did anyone found any solution yet?
My build number is EVA-L09C432B505. Stock firmware, regulary updated.
@zozo77, Have you regularly updated your stock firmware?
What is your full build name/number, like EVA-L09c432b504 or what?
PS: @Chelmiannin
Since this was a question for help, it should have been opened as a regular thread, not for voting, so that people can normally cite and answer
I have a WW model still on version WW_16.0631.1910.64 (rooted). Currently having a few oddities and wondering if an update might help?
Some of the things I’m noticing:
System Ui randomly stops working.
Phone calls and text messages dont come through, I have to reconnect via toggling airplane mode every 30ish min to ensure they come through.
A recent reboot has me in a extremely slow and unusable state where I had to reboot again.
I see some posts about people updating to 10 and they had battery issues, is this something that everyone seems to experience? If I give updating a shot, how would I update and keep my root/data?
Anyone else experiencing GPS issues on the S23?
Sometimes it will work fine for a day, sometimes for a couple of hours. Then it stops.
Occasionally rebooting resolves the issue, but generally it doesn't. Yesterday I restarted and/or turned off/on 5 times without resolving. Some hours later, it just starts working again.
Looking at nmea loggers and GPS Test app, when it stops it either shows no data at all, or sometimes shows signal from just one or two and never finds any more so can't get position lock (other than network based). My old S20 right next to it will show 18-20 satellites at the same time and never faults.
I submitted a fault to Samsung. They said the uploaded system log showed nothing coming from GPS (fault was currently being exhibited) and phone will need to go back. This isn't always the case however, as sometimes it works OK.
Is there anything I can try before I send it off?
Have others had similar issues?
Try restarting in emergency mode (SOS) and do your tests.
If I were you, I would factory reset or even install firmware with Odin just to make sure everything is OK.
Send to Samsung is the last attempt.
Thanks for the suggestions. I'll give them a go and see what happens.
Calibrate your GPS in google maps. Tap your location and it had you move your phone around to increase its accuracy.