Related
Hi,
I have a Desire HD with the stock everything, and by OTA it got the 2.2 so I can't temp root now(before you ask).
One mail reason I got a smartphone was for my love of using GPS. And all was working well, but recently, since almost last one month now GPS has almost completely stopped working. Sometimes I am able to see a fix of upto 4 satellites in GPS status, but the lock never happens. I have tried:
1) GPS status with reset and fresh AGPS data
2) disabling wifi/mobile data
3) removing battery and doing factory reset
4) Ensuring there is clear sky and keeping my phone stable for upto half an hour
5) Testing with Google maps
I read the gps.conf may be the common culprit but i see that the same NTP server of north-america is being used in my brother's Wildfire and it works perfectly and gets a lock within 10 seconds! So I would say rooting just to change gps.conf may not also help me out.
What else can i check? If possible I would want not to root and if required at all, would want to do a temp root if possible to save my warranty
Please help me guys to get my GPS back on my 2.2 DHD
I have read almost every forum post/article I could find which may help me with my GPS issue but none helped me and it seems more and more people are getting this issue. The last thing I would want is to send my dear phone to service center lest they take weeks to "fix" it.
So I was experimenting with any clue I could get. AND it seems I may have stumbled upon something here!
I THINK HTC Desire HD can boot into a safe mode which would help me find if there might be abackgrund process/app hurting my GPS. So to accomplish this I rebooted my HTC, and while booting up and kept the HOME button pressed till it booted up and showed the unlock screen.
GPS Status too about 5 mins but found 6 satellites and locked!!!
Not believeing what I was seeing, I started google maps, and within 5 seconds it locked on to 10 meter accuracy!!
2 questions now
1) Had I actually booted into safe mode, if not what happened here
2) If this was really about something interfering with my GPS, then which server/app is it? How to investigate?
I went into running services and found these running:
astrid backupservice
jbedvmnorunning service
calendar obexservice
htcsense immediatemodeservice
htcsense dashboardsvc
google cloud to device
google messaging
media
sound sdmsvc
cspeoplesync
google maps networklocation
market alarm
mail easappsync
touch input svc
Other 71 mb in 4, avail 247+241 in 43
I will try to find next day what services are running in regular boot, if gps stops working again
If this works for anybody else too, please comment as then we can try investigate together
Well, it turned out that my GPS working was more of a fluke. Didn't work again after that :'(
Not sure what else to try as I do not wish to take as I am not at all comfortable flashing etc. my phone just to make GPS work
hope this solves your problem
waveking9 said:
Well, it turned out that my GPS working was more of a fluke. Didn't work again after that :'(
Not sure what else to try as I do not wish to take as I am not at all comfortable flashing etc. my phone just to make GPS work
Click to expand...
Click to collapse
try FastFix from the market, its a free app, but i think it needs root access
alternatively, you can look in this thread, this helped many
http://forum.xda-developers.com/showthread.php?t=964333
There's a problem with gps on my phone Samsung FOCUS ,Gps is not working even in the open sky, tried several app like -> gpsinfo,wingps and others like RunKeeper,RunSat etc
Phone is Dev unlocked as well as Interop Unlocked with internet sharing enabled.
The update was done using forced method.Updated from stock firmware->7008->7032->7043->7720.68.
Versions ->
Diag app-> 0103
firnware - 2103.11.8.1
hardware rev. no. - 3.1.0.7
Bootloader ver. - 5.8.0.2
radio software ver. - 0.0.0.3
Please help?
Microsoft released a statement saying they don't blame people or doing the forced update... it doesn't do anything bad to the phone so I don't think that's the issue. You might want to try rolling it back to nodo, checking your gps and then reloading mango. if still no go. Hardware issue maybe??
Issue solved,thanks anyway
So, what was the problem?
Don't know, flashed mango again.That's it.
Gps locked in under 10 sec inside the room.
Hmm. My GPS will find my location fine but getting directions is terribly slow now and turn-by-turn will always just say "can't connect to satellites." Now I'm wondering if a rollback and updating again to Mango will fix this.
I'm on official Mango on an AT&T Focus (and I didn't force the update), and I'm having problems just like the previous posters with GPS fixes and 'can't connect to satellite' errors when trying to get directions.
I found a solution by going into another application that uses GPS, getting a GPS fix in there, then going back into the maps. The program I use is "GPS & GPX Logger." After that finds the satellites, the maps work as they should.
For background info, my phone went from NoDO->Mango Beta 2 (7661)->Mango Beta 2 Refresh (7712)->Unforced official Mango including "Samsung Update"
I tried the turn-by-turn again this morning and it actually worked. This is the first time it has since updating last wk. I didn't change a thing, so I have no idea why it work suddenly.
GPS works on Samsung Focus even after Tango update
I own samsung focus 1.3 (AT&T). I purchased it in the beginning of Sep. 2012 (quite late). As soon as I got the phone, I connected it to Zune for updates. After having updated to 7.10.7720.68, I started using the phone. The GPS did not work. I then updated it to 7.10.8773.98 with the hope that updates may make GPS working. I tried all possible tricks available on XDA as well as other forums. I tried following tricks with various permutation & combination:
(i) Pulling out the battery for 30 minutes.
(ii) Changing the MOLR CP/UP setting in GPS diagnostic to UP and CP (one by one),
(iii) Rebooting the phone with location off & again rebotting with location on
(iv) Apps like GPS info & others
& few more which I do not recall now.
After having tried for about a month, I reverted back to original OS version 7.0.7004.0 just to ascertain the availability/ functionality of GPS hardware as on some of the forums I read that their GPS stopped working after No-Do updates. The GPS did not work even after trying all above tricks on 7.0.7004.0 version of OS.
Finally I accepted my GPS to be faulty or not being there and again updated to latest OS version.
One day I read on some forum that putting off the location service & then switching on makes GPS working. Wow, I tried it today, IT WORKED. On bing map it locked, initially with a bigger circle & then reducing down to a dot. In areas covered with thick trees or high-rise buildings, the circle used to become bigger but again in clear sky area it used to reduce down to dot. I am keeping my fingers crossed. Let me observe for some more days to ascertain that this trick actually works.
Those who have not been able to make their GPS working with other tricks, please try this & let us have your feedback on this forum/ thread.
GPS not reliable
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
A. K. Jain said:
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
Click to expand...
Click to collapse
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
gilesjuk said:
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
Click to expand...
Click to collapse
The issue is not related with car glasses as I have tried a lot in clear sky on foot. The issue seems to be specific to Samsung focus drivers.
I'm having issue getting Android Auto to play nicely with the S6. Using the Nexus 5 had no problem at all, but the S6 edge loads AA on the Pioneer 4100nex, then defaults to a black screen with white text stating for me to check my phone when in a safe moment. This is after the initial setup having me to accept all the terms of maps, bluetooth, play music and the like. So I know the phone and the headunit are recognizing each other. I'm curious is the preinstalled "CarMode" app has something to do with it??? Its icon appears on the status bar nearly every time I connect via USB.
Any possible insight would be greatly appreciated.
I'm picking up my 64GB edge this Friday(verizon), and first thing I do when I leave the store is plug it into my 4100. Fingers crossed that it works, but I'll be reporting here with what I find.
mindtrip1016 said:
I'm having issue getting Android Auto to play nicely with the S6. Using the Nexus 5 had no problem at all, but the S6 edge loads AA on the Pioneer 4100nex, then defaults to a black screen with white text stating for me to check my phone when in a safe moment. This is after the initial setup having me to accept all the terms of maps, bluetooth, play music and the like. So I know the phone and the headunit are recognizing each other. I'm curious is the preinstalled "CarMode" app has something to do with it??? Its icon appears on the status bar nearly every time I connect via USB.
Any possible insight would be greatly appreciated.
Click to expand...
Click to collapse
I received my GS6 Edge yesterday and I'm having the same issue. It works great with the Note 4. Pioneer had a firmware update to allow for more models of phones. My guess is that they need another firmware update to include the S6.
Reporting back to confirm, having same issue on my Verizon edge. Like mcryans said, probably need an update for the 4100 for better compatibility.
Same here guys
I, too, am experiencing the same issues. I have a Pioneer AVIC-8100NEX and it worked great with my OnePlus One (Oxygen OS). But when hooking up my new S6 Edge (AT&T), it does not work. I spoke to a rep at Samsung and they were not aware of this issue nor even understood what Android Auto even was. The tech was hopeless and a waste of my hour explaining the problem. Hopefully Samsung and Google resolves this soon as many 2015 cars should come with Android Auto support.
I have the AT&T edge and just reporting that the latest Google Play Service update fixed anything wonky between my avh-4100 and my S6 Edge. I'll try voice commands on my way to work but otherwise works like a charm.
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.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.