Is anyone else having issues getting a GPS lock on the fire phone? I recently was gifted one after the fire sale and I have been having issues ever since. When it actually works, the GPS has significant drift, and it often has trouble catching up with me when I am walking around. It also takes forever to acquire a GPS lock, if it can at all. I have waited 10 minutes, inside an open park with no trees within 50 meters of me for a lock with no luck. I can't even get a lock inside my own home after trying to acquire a GPS lock for well over a half hour. Sometimes it acquires a lock after 5 minutes, most of the time it doesn't--draining my battery significantly in the process
This has been happening with Ingress, Google Maps, Chrome, the Silk Browser, the built in Maps app, and Waze, so I doubt it is an issue with a specific app not being compatible with the FireOS. I am running stock, unrooted FireOS 4.6.4 with Google services framework, Google play store, Google play services, as well as the Google account manager installed (I need it for Maps, hangouts, and ingress). I am also wondering if the Google Play services apps are somehow interfering with GPS services, but I am very reluctant to uninstall them as I would have to reinstall the delicate setup of old Google apps that allow vital apps like Hangouts, Google Account manager, and Ingress to function in at least a usable state. However, it is with noting that I have tried to see if uninstalling Google Maps would help to no effect.
Does anyone experience issues like this? Is this a common issue? If not, does anyone have any advice on how to resolve the issue? Because if not, I am probably just going to buy a new phone.
GPS works fine on mine with stock 4.6.3 (rooted), try a GPS tester (GPS Test is one) and see if it gets an accurate lock.
GPS disconnects for like 30 second every 2 minutes on mine. 4.6.3 rooted. No Google services. It was previously on AT&T 4.6.4.
Happens on the stock Maps app, Waze, and SatStat.
EDIT:
I tried flashing 4.6.5 and leaving it unrooted. Re-enabled almost all the Amazon apps and its still giving me issues. Maps just says "Searching for GPS..." all the time while trying to navigate to an address. I think this might be hardware issue. Trying to troubleshoot with Mayday.
UPDATE:
In case anyone lands here looking for answers...
After a couple weeks of dealing with Amazon's tech support, they decided to give me a new phone. The new phone's GPS works as expected! It's an AT&T model on 4.6.5 not rooted.
Related
Hey all,
I finally made the jump to the One M8 from my iPhone a few weeks ago, and I quickly unlocked, S-OFF'd, rooted, and flashed MaximusHD. I had to switch back to my iPhone for a couple of weeks for work reasons, and yesterday decided to switch back to the One. When I booted it up, I saw that an OTA was available for MaximusHD 7.1, so I installed it and realized that I was missing LTE and stuck on HSPA. A quick phone call to AT&T resolved my issue when I realized that it was simply a provisioning problem (since the 4S I had been using is LTE-less). Now for the strange part - after being on WiFi all day at home, I come to work and try to fire up the Google search app (while connected to LTE), no dice. The app throws a "Can't reach Google at the moment." So I fire up Chrome, and try google.com - after a painstaking few seconds, I get "Timed out". I navigated to a different site (CNN), just to test connectivity and voila! - the page loads immediately. I retried google.com, and the site still times out. Also, the Play Store has no connectivity over LTE, also throwing "Connection timed out." All other apps (Instagram, Speedtest, even GMaps/G-mail) work while on LTE. If I force the phone to drop to HSPA (by choosing GSM/WCDMA only in Mobile Network settings), then magically all the forementioned apps and google.com work properly. It seems that all the Google services are "blocked" while connected to LTE. So far I've tried:
- Airplane mode on/off
- Rebooting
- Clearing defaults and wiping all the application caches (as well as the Play frameworks)
- Factory resetting/Wipe Cache
- Flashing a different ROM (VenomOne) and starting fresh
- Confirmed that APN settings are correct (other sites other than google.com work fine)
- Deauthorized my phone in my Google account settings
- Created a new Google account
None of these worked. I also tethered my MacBook to the phone, and was able to access google.com via Safari perfectly fine while the phone was sharing it's LTE connection. I installed Firefox on the phone, and strangely google.com works fine as well. It seems as though any Google services that rely on my login fail to work on LTE, but work perfectly fine over HSPA. Google searches work, the GSearch app works fine, and the Play store loads immediately. Switch back to LTE, all other apps and sites load properly, Google services fail again (now including Sync).
Sorry for the lengthy post guys, but I'm out of ideas. I'm going to (unfortunately) flash the phone back to stock and see if that works, and if it doesn't, I'll drop by the AT&T store tomorrow and see if a new device makes a difference. It doesn't quite add up, unless its a weird provisioning problem. Hopefully you guys can help or might have an idea? Thanks!
Hey man, I'm jumping on board with you on this issue. I've been battling this same exact issue for the last month or so. I've literally tried everything in the book and can't seem to figure it out. Not hijacking your thread, but I was going to create a thread here as well since I'm out of ideas. Here's my experience, hopefully we can knock something out here to fix this plague of a problem.
I've flashed multiple different versions of firmware, multiple different ROMs, cleared every kind of cache you could imagine, etc. Often I can get the issue to disappear for a short while, but it always returns.
I did restore the phone to stock using the factory RUU. That actually did work for a short period of time, but then I started receiving a message that said "Restricted Access Changed - Data Service is Blocked".
That message led me to this site: Nexus 5 Restricted Access Changed Issue - Solved
After being 100% stock, I uninstalled updates for Google Play Services. That worked for 3 days. After 3 days, I connected to wifi for the first time, after I turned wifi off - no connection to the Play Store again.
That was last night. Flashed newest firmware (2.22.401.5) and Insert Coin 4.0.9 this morning... still no good. Google Search and the Play Store time out with "No Connection" messages.
The one thing I believe differs from me to you, is that HSPA+ (GSM/WCDMA) does not work either. I believe you said that worked for you?
Certain little things seem to randomly make it work for a short period of time. Once I flashed cache/dalvik and did a fastboot erase cache - magically worked after that. Though, that only lasted for a day or two.
Think I'm going to jump on Support Chat with AT&T to see if they can provide any help, though I doubt it. I'll update here as I go along so hopefully we can get this figured out. Sorry for the lengthy response.
Same issue, also from CT
Just responding to the OP, I am having the EXACT same issue as you with my Google Services not always connecting while I am on LTE. I wonder if it's a geographic thing as I am in Southeast CT Groton to be exactly although I have also had the same issues in Niantic at work. I also have AT&T service but my device is a HTC One M8 Developer edition. I sometimes can connect to Google services over LTE but it seems to be hit or miss. Services that I have been having trouble with include gouge search accessed through chrome, google now/voice search, Play store and Wallet. I have not had any issues streaming music over Google Play music, even when my other services were not functional over LTE for some reason. I have tried all the suggested trouble shooting steps such as uninstalling Google updates, clearing google play services cache and app data, verifying my date and time setting, etc. I even unlocked and rooted just to delete the hosts.txt file as was suggested in the system/etc folder. So far nothing I have done has completely fixed my LTE issue, it was the exact same behavior on kk 4.4.3 and after I applied the kk 4.4.4 OTA update. I have not tried S-off or installing any custom ROMs. As I type this my Google services ARE working over LTE but I'm not expecting that to remain constant based on past experiences.
trailrunnerx said:
Just responding to the OP, I am having the EXACT same issue as you with my Google Services not always connecting while I am on LTE. I wonder if it's a geographic thing as I am in Southeast CT Groton to be exactly although I have also had the same issues in Niantic at work. I also have AT&T service but my device is a HTC One M8 Developer edition. I sometimes can connect to Google services over LTE but it seems to be hit or miss. Services that I have been having trouble with include gouge search accessed through chrome, google now/voice search, Play store and Wallet. I have not had any issues streaming music over Google Play music, even when my other services were not functional over LTE for some reason. I have tried all the suggested trouble shooting steps such as uninstalling Google updates, clearing google play services cache and app data, verifying my date and time setting, etc. I even unlocked and rooted just to delete the hosts.txt file as was suggested in the system/etc folder. So far nothing I have done has completely fixed my LTE issue, it was the exact same behavior on kk 4.4.3 and after I applied the kk 4.4.4 OTA update. I have not tried S-off or installing any custom ROMs. As I type this my Google services ARE working over LTE but I'm not expecting that to remain constant based on past experiences.
Click to expand...
Click to collapse
Did you contacted your carrier about this LTE and Google services issues? Cause I can use all Google services on LTE. Its kinda a bummer that you cant use something that you are paying for tho.
Poslano z mojega HTC One_M8 z uporabo Tapatalk
This guy has the same issue: http://forum.xda-developers.com/att-htc-one-m8/help/lte-connection-issues-3-28-401-7-t2913168
He thought it was caused by flashing firmware. But based on your experience, it might just be a carrier issue.
I've had an LG G4, model H815 at Android 5.1 for the past two months. So far extremely satisfied, but it's been acting up for the past few days - battery drains for over 20% while I sleep for ~7 hours, and apparently Android System (specifically the GPS) keeps it awake and drains over 60% of the battery.
I keep GPS on high accuracy and I use the smart settings the phone has, but up until a week ago or so it didn't do any harm and it only lost about 2-5% every night - Same goes (more or less) for my previous phone. LG's subsidiary in my country just pushed an update a few days ago, so it may be relevant, but I don't recall if it happened before it or not (sorry).
I'm attaching a few pictures to this post, if there's any app you want me to run and post its output just let me know.
Any idea why this is or how to solve it?
Here is mine:
Okay...? So any idea why it happens to me but doesn't to you? This is a troubleshooting thread.
Same here. GPS in Android System seems to be nearly always on (up to 8 hours GPS usage, while I left the phone idle, without any App started) - with a huge battery drain.
I also suspect the firmware update received recently, since I became aware of this issue only some days ago. Using the phone, the GPS icon comes up every 2 Minutes or so and stays on for about 20 Seconds. That's definitely something I never observed before.
I googled a lot and found some articles describing similar problems. However, no working solution was given.
Here is what I did with nearly no impact:
- motion sensor and compass calibration
- cache wipe
- termination of the google app process, since I thought this might be the culprit (even cleared data)
- switched off google location tracking and smart lock
- switched off Android Device Manager under Device Administrators
Then, I did something that looks promising:
- I de-installed the updates of Google Play services and re-installed the latest version from Play Store. It was the Version 7.8.99 (2134222-220).
This solved the problem at least temporarily. I had a whole day where the system behaved as it should. However, this morning the problem came back.
- I de-installed the update of Google Play services once again, but this time without updating to a newer Version. I currently run version 7.5.71 (1955121-448).
To my surprise, even after reboot, the system does not ask me to update, so I leave it now as it is.
And the problem - again - seems to be gone. However, I am not sure whether this - again - will only be temporarily...
I think a good starting point for problem analysis might be to compare the running Versions of Google Play Services. What do you think?
Thanks,
toshiuser
I'm currently running Google Play services v. 7.8.99 (2134222-440). While writing this I'm clearing its cache and data and uninstalling updates, brings it back to the same stock version you mentioned. I'll see if it helps and keep you updated. Thanks a lot!
I think this has to do with carrier iq.. Not 100% sure though, but maybe you guys should look into it. I know my android system usage was really high also. Then I removed carrier iq and it went way down.
idowolf said:
I'm currently running Google Play services v. 7.8.99 (2134222-440). While writing this I'm clearing its cache and data and uninstalling updates, brings it back to the same stock version you mentioned. I'll see if it helps and keep you updated. Thanks a lot!
Click to expand...
Click to collapse
I also run Google Play services v. 7.8.99 (2134222-440) and also noticed GPS is On ever now and then even @ home. I wanted the latest Google Play Services and I enabled this Google Play Services drain fix. So far have not seen the GPS turn On without reason. Hope this will solve my overnight 20 % battery drained.
我從使用Tapatalk的LG G4 H815 US 4G LTE TMO發送
I had the same issue you're having. If you're rooted, it's an easy fix. Download any app ops application from the play store, and go in and disable the location permission for Android System. Has no effect on the device knowing your location whatsoever, and fixes the wakelock/battery drain from Android System.
Hope this helps!
uly609 said:
I think this has to do with carrier iq..
Click to expand...
Click to collapse
Thanks, but I cannot find a process called carrier iq on my phone (probably because my phone is an unbranded european retail version?).
rogconnect said:
I also run Google Play services v. 7.8.99 (2134222-440) and also noticed GPS is On ever now and then even @ home. I wanted the latest Google Play Services and I enabled this Google Play Services drain fix. So far have not seen the GPS turn On without reason. Hope this will solve my overnight 20 % battery drained.
我從使用Tapatalk的LG G4 H815 US 4G LTE TMO發送
Click to expand...
Click to collapse
Sorry, but I do not understand. Version 7.8.99 (2134222-440) has the problems (see post from idowolf). What did you enable as the "Google Play Services drain fix"?
mcnick0495 said:
I had the same issue you're having. If you're rooted, it's an easy fix. Download any app ops application from the play store, and go in and disable the location permission for Android System. Has no effect on the device knowing your location whatsoever, and fixes the wakelock/battery drain from Android System.
Hope this helps!
Click to expand...
Click to collapse
This sounds promising, but I'm not planning to root my phone (at least as long as there are chances for other solutions).
One update from my side: Still running Google Play Services Stock version 7.5.71 (1955121-448) and everything still seems to be ok. No battery drain from GPS. However, I am still not convinced that this will last long...
Thanks,
toshiuser
toshiuser said:
Thanks, but I cannot find a process called carrier iq on my phone (probably because my phone is an unbranded european retail version?).
Sorry, but I do not understand. Version 7.8.99 (2134222-440) has the problems (see post from idowolf). What did you enable as the "Google Play Services drain fix"?
This sounds promising, but I'm not planning to root my phone (at least as long as there are chances for other solutions).
One update from my side: Still running Google Play Services Stock version 7.5.71 (1955121-448) and everything still seems to be ok. No battery drain from GPS. However, I am still not convinced that this will last long...
Thanks,
toshiuser
Click to expand...
Click to collapse
if you don't intend to root i got nothing much to say.
uly609 said:
I think this has to do with carrier iq.. Not 100% sure though, but maybe you guys should look into it. I know my android system usage was really high also. Then I removed carrier iq and it went way down.
Click to expand...
Click to collapse
No carrier iq here and I've had the same issue a while back.
Update: No Problems with Stock Version of Google Play Services. Everything worked flawlessly the past few days - no battery drain.
Now reinstalled the current Version 7.8.99 (2134222-440) from Play Store to see if problems come back. I will keep you updated...
Last Update:
Google play Services 7.8.99 (2134222-440) is definitely faulty, at least in my configuration. “GPS always on“ and the huge battery drain almost immediately came back after reinstalling it. I was only able to achieve SOT of 2 and a half hours while GPS was active for several hours (in idle mode!).
Switched back to 7.5.71 (1955121-448), which works great, and will stay there with double SOT.
I did not see many posts regarding problems with Google play Services 7.8.99 (2134222-440), so this is either a rare problem or this is the reason why we read the many complaints about LG G4's supposedly “poor“ battery...
Hope that Google is aware of this problem and fixes it soon...
toshiuser said:
Last Update:
Google play Services 7.8.99 (2134222-440) is definitely faulty, at least in my configuration. “GPS always on“ and the huge battery drain almost immediately came back after reinstalling it. I was only able to achieve SOT of 2 and a half hours while GPS was active for several hours (in idle mode!).
Switched back to 7.5.71 (1955121-448), which works great, and will stay there with double SOT.
I did not see many posts regarding problems with Google play Services 7.8.99 (2134222-440), so this is either a rare problem or this is the reason why we read the many complaints about LG G4's supposedly “poor“ battery...
Hope that Google is aware of this problem and fixes it soon...
Click to expand...
Click to collapse
Did you tried (448) latest version..at least its same as 7.5.71(448)
faizalotai said:
Did you tried (448) latest version..at least its same as 7.5.71(448)
Click to expand...
Click to collapse
Google play Store only offers me (440). How can I change to (448) in play store?
toshiuser said:
Google play Store only offers me (440). How can I change to (448) in play store?
Click to expand...
Click to collapse
GmsCore (448)
This Night, I received Updates for Google Maps and Photos and a notification that these versions require an update of Google Play Services, perfect...
Therefore, I will give the Version (448) a try. Hopefully it does something better than the (440)...
mcnick0495 said:
I had the same issue you're having. If you're rooted, it's an easy fix. Download any app ops application from the play store, and go in and disable the location permission for Android System. Has no effect on the device knowing your location whatsoever, and fixes the wakelock/battery drain from Android System.
Hope this helps!
Click to expand...
Click to collapse
Thanks for this. It brought my Android System under control and significantly improved my battery life...well, closer to where it was before I rooted!
No luck,
even with Version (448) the problem persists.
I examined the problem again:
When I disconnect the phone from the power supply in the morning, it usually works normally. During the course of the day, at some point (not predictable), the GPS icon shows up for 2 minutes, grays out, disappears and comes back after a short time. Being in this state, Android system drains the battery due to high GPS usage (even if no app is active and even if locked in idle mode).
Now the interesting part:
If I open Google maps being in the problem state, it just takes 1 or 2 seconds to obtain a GPS fix. If I close it right after the fix, the GPS icon is gone and the phone behaves normally - sometimes for several hours. When GPS icon comes again and stays, I simply repeat the process.
For me it seems, that location service in Google play services is faulty since it sometimes cannot obtain a GPS fix whereas the algorithm in Google maps does it instantly.
toshiuser said:
No luck,
even with Version (448) the problem persists.
I examined the problem again:
When I disconnect the phone from the power supply in the morning, it usually works normally. During the course of the day, at some point (not predictable), the GPS icon shows up for 2 minutes, grays out, disappears and comes back after a short time. Being in this state, Android system drains the battery due to high GPS usage (even if no app is active and even if locked in idle mode).
Now the interesting part:
If I open Google maps being in the problem state, it just takes 1 or 2 seconds to obtain a GPS fix. If I close it right after the fix, the GPS icon is gone and the phone behaves normally - sometimes for several hours. When GPS icon comes again and stays, I simply repeat the process.
For me it seems, that location service in Google play services is faulty since it sometimes cannot obtain a GPS fix whereas the algorithm in Google maps does it instantly.
Click to expand...
Click to collapse
Very well described, I am seeing the exact same problem. I even upgraded to play services 448 like you.
I got strange GPS behaviour with my new OnePlus 3.
Symptoms:
1. Google Apps (like Maps or Fit) won't use GPS to determine the position. This is checked by GPS Status & Toolbox. If I start GPS Status & Toolbox by itself it directly hits up GPS. Same with non Google apps like HERE or EXIF Location Tags in photoapps.
2. When I start navigation on Google Maps it starts using GPS. When I stop it, GPS usage stops too.
3. When I force Google Play Services to stop everything works flawless. Maps and Fit start using GPS as it should be. After restarting the phone, Google Play Services is back up and same issues occur as stated above.
Tried with newest CB, 3.2.4 and Resurrection Remix (BJRR). My Google Play Services is 9.8.77 but I already tried older versions without success. I googled this problem, found something similar in google product forums (https://productforums.google.com/forum/m/#!topic/maps/l-YG1DB8jyQ) without solution.
Somebody know this problem or has any suggestions?
I know I have had a similar issue with my phone (Stock updated OOS rooted w/TWRP and Xposed) rebooting all the time during navigation, random loss of GPS-based location and being forced to reboot to bring it back, etc. I've had no issue with the rest of Google Apps, though.
My Pixel XL GPS doesn't report accurate location during navigation and it causes the navigation app to always show my car a few feet off the road and keep recalculating the route. It is more severe in Waze but it is noticeable in Google Map too. Someone created a video of the issue: See this videohttps://youtu.be/LyOZW3BSQcY
Talked to Google support per usual they say go to Safe mode or reset the device but it didn't help. Anybody else observed this issue? It is common enough that Sprint created a document on how to address it but it doesn't help. People have reported it on Reddit and Verizon forums too but wanted to see what has been the experience here.
no video link. Regardless I have only encountered what you describe once when there was a split in the highway for an exit. After I started pointing a different direction it snapped back into place. Outside of that my GPS has been great. I am on Verizon if that matters.
mehdi_s82 said:
My Pixel XL GPS doesn't report accurate location during navigation and it causes the navigation app to always show my car a few feet off the road and keep recalculating the route. It is more severe in Waze but it is noticeable in Google Map too. Someone created a video of the issue: See this video
Talked to Google support per usual they say go to Safe mode or reset the device but it didn't help. Anybody else observed this issue? It is common enough that Sprint created a document on how to address it but it doesn't help. People have reported it on Reddit and Verizon forums too but wanted to see what has been the experience here.
Click to expand...
Click to collapse
I had an incident yesterday where I was continuing on a freeway at 70 MPH,. But Google Maps thought I had veered from its directions by exiting on a low speed very curvy road, so regenerated directions for that. This never happened wth any of my Nexus devices.
Im having this issue as well. Google Maps seems fine, but Waze seems a lot more jumpy and recalculates my route every few seconds. Pretty annoying.
NWTSCL said:
I had an incident yesterday where I was continuing on a freeway at 70 MPH,. But Google Maps thought I had veered from its directions by exiting on a low speed very curvy road, so regenerated directions for that. This never happened wth any of my Nexus devices.
Click to expand...
Click to collapse
Yea I never seen this issue on any Nexus. Since it seem to be common,not sure if a replacement would solve it. Posted it on Google product forum too to raise it to Google:
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/y6G3etvT3U0
Sent from my Pixel XL using Tapatalk
Me Too...
So are you guys still having problems with this?
It's gotten to the point where I don't want to use Waze anymore - and I LOVE Waze. It seems like it should just be some sort of software tweak to fix this problem...
I hope it at least gets fixed before Waze comes to Android Auto.
Lame was hoping this got better and was looking forward to a working gps on Pixel.
Ive had this issue eventually pop up on every device. Currently on LG v10.. Upsetting :/
clockcycle said:
Lame was hoping this got better and was looking forward to a working gps on Pixel.
Ive had this issue eventually pop up on every device. Currently on LG v10.. Upsetting :/
Click to expand...
Click to collapse
Try deleting the app data and cache. Then uninstall and reinstall the app. So far its worked for me. Need to test it a few more days before I can confirm its a permanent fix.
I saw this post so I turned on Google Maps & used it to navigate home from work, about 15 miles. Not a big test, but it worked fine, followed be closely, always had me exactly where I was on the road down to the lane I was in.
I have had zero issues with Maps. I do not use Waze. (on ATT)
I have had the GPS issue first on the Pixel (was not following my location accurately and would not give me turn by turn directions) spoke with Google support, all their solutions failed including the factory reset so returned the Pixel and upgrades to the XL model have had it for 3 days and started having same issue again today!!! This issue is on maps and I have only downloaded normal certified apps I was very excited about the 1st Google phone as I love their products but this is very discouraging as the exact same problem has now happened with BOTH phone models. I have Verizon service but based on all of these comments am starting to believe it is a hardware issue and not the service provider. Hoping they can get this bug fixed and quickly otherwise I will be returning for a different device.
My Pixel XL was fine for the first few days. Then I put it in a case and rooted it, and ever since then the GPS is acting wonky in Waze, losing its fix, not getting satellites, acting nuts.
Trying to determine the issue...
I find it awful on maps!! I've had it showing me going backwards and the rotation is off!
Tried with waze and it was OK though so I've no idea
Sent from my Pixel XL using Tapatalk
Waze and Google Maps both keep losing GPS signal.
Waze starts to go absolutely haywire.
Google Maps just says "seeking GPS signal" every 30 seconds
Ive done a full factory reset and it's still happening.
Maybe something wrong with the GPS chip, or on the underlying OS??
Just spent 2 hours troubleshooting with a Google tech. They will be calling me back son (they just told me to test it after a full factory reset). No luck!
I'm also having this issue with the pixel xl. Seems much worse in Waze but happens in Google maps a little as well.
Well my GPS died some time this weekend. I was loosing GPS lock on google maps. GPS test is no longer shows it lock onto any satellites when my nexus 6 sees 7-9. Replacement is on the way. I would recommend anyone having this problem check with a gps test/info app and make sure the hardware is working correctly.
I replicated the problem on NDE63V, the OS the device shipped on and was working on before, along with NMF26O and NMF26Q.
Waze is unusable now. I am seeing the same behavior. Google Maps is ok, but waze jumps all over the place.
It is pure speculation, but I wonder if it is tied to how the OS is using the accelerometers. I think google Maps uses both the GPS position and accelerometers.
-J
1/2/2017 - Google Confirming Software Issue with GPS
I'm having the same problem.
Last week my GPS on my Google Pixel stopped working. When I open google maps, it shows the blue dot correctly with the compass working properly. However, when I start navigation or driving mode, it does not work. I also tried Waze and that also does not work - just holds on Searching for GPS. I also tried the app 'GPS Test' and it shows 'No Fix' on the GPS Status.
I contacted google pixel support this morning and they confirmed Google is aware of the problem and have identified it as a software issue.
nixforme12 said:
I'm having the same problem.
Last week my GPS on my Google Pixel stopped working. When I open google maps, it shows the blue dot correctly with the compass working properly. However, when I start navigation or driving mode, it does not work. I also tried Waze and that also does not work - just holds on Searching for GPS. I also tried the app 'GPS Test' and it shows 'No Fix' on the GPS Status.
I contacted google pixel support this morning and they confirmed Google is aware of the problem and have identified it as a software issue.
Click to expand...
Click to collapse
That's wonderful! Did they give you any information on how you others can refer to the issue, such as a bug number or anything?
I'm also having the same issue with my Pixel when using Waze, and since stopped using it, due to it being redirected consistently. Switching to Maps Navigation the issue doesn't seem to exists, however, if I just use Maps, I can see that the compass is not oriented in the correct direction, and have to do the figure 8 calibration consistently so that it can be oriented correctly. The blue indicator dot is also not correctly located on the map, and can be off by many feet/meter. This is the only way I have been able recreate the issue I'm seeing with Waze but on Maps this time, it seems that Maps Navigation is more forgiving on the GPS irregularities than Waze, which is why Maps Navigation is a much better experience than Waze on the Pixel or Pixel XL.
Haven't experienced anything drastic with the gps lock, but I do notice that the direction of where i'm facing is constantly off. Tried calibrating the compass to no avail. The direction feature would also throw off driving directions as it doesn't know which way you are headed when stopped.
I began noticing my Google Maps would say "searching" but never start giving directions. But sometimes it would work. Switching to WAZE, it works fine, except I don't like the voice commands for WAZE, not as responsive. Finally, I decided to not deal with it (online fixes did nothing) and buy a 4A-5G. It has a worse problem... it takes 3 screens to answer a call, and many drop before I get there. Kogan will refund the purchase. I'm tempted to go back to the 2XL since it does everything I need... if I can get the maps to work. Anyone else had this problem?