Database Develop

GPS Continuously Loses Lock

I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app

I use gps daily and i've only come across an issue with it 2x when i went to New York City. basically, it was putting my location all over the map, as if it couldnt find me. Im guessing the high rise buildings had something to do with it.
as far as gps losing lock, I have notice that as well. I never toggle it off and yet I have to turn it maybe once/twice a month

The lock problem I have is pretty continuous, and restarting doesn't seem to help. Wondering I'd there was a bad run somehow.
Sent from my XT1053 using xda app-developers app

I also encountered this issue.
I reset the phone and it went back normal; however, it occasionally still acts weird. I'm on tmobile as well.
Hope someone can figure this out
Sent from my XT1053 using xda app-developers app

For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.

Solutions Etcetera said:
For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.
Click to expand...
Click to collapse
As a matter of fact I do see this. Any idea what might be going on?
Sent from my XT1053 using xda app-developers app

Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1

monorailmedic said:
I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
So you are saying this can be software issue? I have a T-Mobile Moto X and I use the phone mostly for Navigation and this is driving me crazy. I am thinking that my phone is defective and been on the phone for 30+ min trying to get support.

I have the same issue
Sent from my XT1053 using Tapatalk

Solutions Etcetera said:
Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1
Click to expand...
Click to collapse
I went ahead and posted my situation to https://forums.motorola.com/posts/8a2bf78f04?commentId=755612#755612. There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.

I must add that I also had this problem on my previous phones, Note 2 and Galaxy Mega 6.3. The problem started around the past summer.
Sent from my XT1053 using Tapatalk 2

I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Sent from my XT1053 using Tapatalk 2

x2h said:
I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Click to expand...
Click to collapse
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.

Solutions Etcetera said:
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.
Click to expand...
Click to collapse
I mean rebooting the phone. I use Waze everyday for commuting. I will report back if this fix doesn't work.
In terms of side effects, I have not seen any yet.
Sent from my XT1053 using Tapatalk 2

I see both, and if I stop one, I get no better GPS lock.
I've been getting g terrible GPS lock recently and also posted a thread.
Driving me nuts.
Sent from my XT1060 using XDA Premium 4 mobile app

monorailmedic said:
I went ahead and posted my situation to ... There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.
Click to expand...
Click to collapse
I have the same problem. XT1053 on T-Mobile constantly loses GPS signal while driving. Happens in wide open areas with no buildings. I have tried wiping the device and not installing any additional apps and have the same results. I can be sitting at a traffic light have GPS signal, lose it for a few seconds then get it back without having moved.

Here is a poorly shot video of this happening. I will try and get something more clear tomorrow.
http://www.youtube.com/watch?v=N5MeEVS1DW0
Sent from my XT1053 using xda app-developers app

I returned my phone for this issue yesterday. I had navigation issues along with the drive assist problem. While driving maps world just stop. If I was at a turn and turned left the map would stay stuck at the turn long after I turned. It eventually would catch up. Loosing and gaining lock would perfectly explain this.
Update: I got a replacement phone. The new phone has the same problems. May be a bit worse.
Sent from my XT1053 using Tapatalk

Been chasing this one for a while and still think this isn't hardware related (lots of Nexus 5 users seeing this on KK as well).
My latest theory, which I have yet to disprove, is that the GPS data downloaded from some cell towers (this is the A in AGPS) is either wrong, or is somehow getting corrupted.
When this happens to me, turning on airplane mode immediately restores a quick and persistent lock. And using GPS Status to reset/erase the AGPS data returns normal operation... for a while.
It's like the initial fix info is fighting with the actual GPS readings. As soon as you turn off the cell towers, or clear the data they are providing, all is well.
I am in T-Mobile fringe area and see it fairly often. So far it has always cleared up by trying the above.

This is am interesting theory. I will check it out a bit. Most interesting is the idea that the agps data structure may be slightly different for kitkat v ICS, and that it may also be different for TMO. The main idea supporting this (though purely anecdotal) is that it does happen on both my tmo Xs but neither of my VZW Xs.
Sent from my XT1053 using xda app-developers app

Smart Lock not Working

Just upgraded to 5.0 via the ROM flash to keep root. I flashed the stock ROM, not deodexed.
Smart Lock is the main feature I need in 5.0. I have a Moto360 and want my phone unlocked when the watch is present by using it as a Trusted Device. Immediately after flashing, I set a lock pin so that Smart Lock was available. Everything was working as designed.
All of a sudden, I am having to enter my lock pin again. I go into Security settings and Trusted Devices and Smart Lock are both greyed out. How can I reenable?

No one?

Depending on the device, you may still be presented with your lock if that device ever got out of range. Happens to me all the time at work. I have my watch set up as a trusted device and leave my phone on my desk. When I get back, lock enabled. However once unlocked, if I stay within range it never re-enables.

lordmorphous said:
Depending on the device, you may still be presented with your lock if that device ever got out of range. Happens to me all the time at work. I have my watch set up as a trusted device and leave my phone on my desk. When I get back, lock enabled. However once unlocked, if I stay within range it never re-enables.
Click to expand...
Click to collapse
Thanks for the reply. This is not the case. I can't get Smart Lock to work at all. Again, it worked right after I flashed the phone, now it doesn't work at all. Also, Smart Lock and Trusted Devices are both greyed out in the Security menu.

I have issues with inconsistent or I'd rather say "almost not working" Smart Lock. I have OC4 deodexed/rooted and set up lockscreen with fingerprint. Despite of trying to scan my fingertips several times with different angles and stuff it still works so-so for pointing fingers and kinda bad for one-handed use with a thumb! BUT I'd better keep device secured with it in case of lost or stolen phone with all my banking info and things like that will be available right away with a swipe! So the nice feature of trusted devices for smart lock works great and I don't need to worry either in my car (bluetooth handsfree set) or in a gym (NFC headphones). Even nicer feature with trusted places doesn't seem to work tho! I tried to downgrade maps, play services, remove/add nearby places like next 2-3 houses but nothing helped. And apparently gps connection/location detection doesn't work instantly like less than a second and that leads me to fingerprint scanner everytime... extremely annoying! Any known workaround or temp fix?

Having to constantly use password instead of fingerprint on 6.0.1

Not sure why, but it seems like every other time I turn my tablets screen on it wants my password to be typed in rather than fingerprint because of security policy. I never had this issue in 5.1.1
Anyone else noticing this or know of a way to fix?

It's set up to request pin after each reboot or 24 hours of inactivity. Do either of these apply to your situation?
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

papashex said:
It's set up to request pin after each reboot or 24 hours of inactivity. Do either of these apply to your situation?
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
It definitely does it each reboot. I never really go >24hours without touching it, but I'm sure it would ask for it then too. It asks for password after much less time than 24 hours to me, also seems to do it when I change locations (i.e. when I get home from work). It's become so frequent and annoying that I've set a basic, easily-hacked PIN rather than the lengthy, complex password I was using on 5.1.1. Also, even though I've set my car stereo as a smartlock trusted device, it frequently asks me for the PIN whenever I get in my car and start driving (I use tab for music/nav).
The fingerprint sensor on this tablet has never been anywhere near as good as on my nexus phone, often taking 2-3 tries for it to read it, but now that it won't even accept my print for unlocking the device 1/2 the time it's able to read it, it's to the point where I just dont even bother and just skip it and go to PIN entry instead

DAMN. Mine was working fine until I read your post. Now fingerprint recognition has gone wonky. Trying full wipe / reset to see if I can clear things up (maybe app / setting issue).

Facial recognition issues anyone?

Anyone else getting face unlock issues? It works fine then suddenly stops working. Says it can't recognize a face. If I try to delete and re program the facial recognition, an error shows up saying the feature isn't working and the phone needs to be restarted. After restart, it works fine again. Happens now once daily.

twistanesh said:
Anyone else getting face unlock issues? It works fine then suddenly stops working. Says it can't recognize a face. If I try to delete and re program the facial recognition, an error shows up saying the feature isn't working and the phone needs to be restarted. After restart, it works fine again. Happens now once daily.
Click to expand...
Click to collapse
yes, I am having the same issue though it's perhaps once every three weeks.
I tried clearing the cache and data in the App manager but did nothing.
I am thinking it might be the app that scans for apps and it they are not used within three days it puts them to sleep. But that shouldn't cause it not to even run.
I think this is why Samsung put an option in the settings to auto restart your phone weekly or what not.

Mine acts up once in a while, so just switched back to IRIS. Anyone notice that there is no Preview Screen now? Just text at the top of the screen with instructions. (I like it better without the preview screen, thought it was tacky).

Have had this problem intermittently from day one, on this and another note. It's not so reliable. Fingerprint still the fastest.

Seriously facial recognition is garbage
Sent from my SM-N950F using XDA-Developers Legacy app

there is a setting which lets you make a less secure faster facial recognition. I use this with no problem...

OK Google - very poor functionality

I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.

fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.

SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.

fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."

I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk

Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.

Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.

Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk

fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.

Ok google for me just does not work.

Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.

Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!

I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help

This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk

May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...

gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.

Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?