Hey guys, I recently got a brand new HTC U11 , and everything was perfect with the phone until I had to use the GPS navigation.
Even on a clear day with no clouds in the sky, phone stuck to the car windshield and screen always on, the GPS signal will get lost very frequently, like every 10 minutes, and some times it won´t recover until a reboot.
I don´t think it is a case of poor signal, because using a GPS diagnostic app I can see that it is connected to at least 15 sats, and then when it loses signal, it loses all satellites, so it seems to me that GPS location is getting somehow disabled from time to time.
Could anyone point me out to a possible solution?
Maybe the Boost+ is the culprit?
You have to take into consideration that in the last several weeks we have had several geomagnetic storm courtesy of the Sun. When the Sun produces a CME (Coronal Mass Ejection), or sunspots develop they will have an effect on satellite communications. The RF output of GPS sat's is very small by time the signal makes it to the planets surface so any disruption in the upper atmosphere will have a negative effect on our GPS's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow, I had no idea about that.
But anyway, as I described, it seems to me that this is more like the GPS was turned of, maybe by some power optimizer or something?
In fact, I have an external bluetooth GPS, and when I use it, I get no GPS signal loss at all.
Sounds more like a hardware issue to me.
The battery opimization wouldn't kill GPS in an active foreground app.
Actually batttery optimation just kills inactive apps, services.
A 3rd party app could just turn GPS off, when it has root rights.
Related
I have find some good posts on XDA to configure/tweak GPS settings for faster locks/accuracy.
May be these will be helpful for many users:
http://forum.xda-developers.com/showthread.php?t=1248375
http://forum.xda-developers.com/showthread.php?t=1233359
http://forum.xda-developers.com/showthread.php?t=1695425
Errors on GPS Signal:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sometimes our GPS devices guides us to a wrong path. Have you ever thought of the reason behind. The GPS signal from the satellites before reaching the GPS receiver, gets degraded, affecting it accuracy. There are about 4 important factors causing GPS errors:
* Troposphere and Ionosphere Delays
The satellite signal as it passes through the earth layers viz Ionosphere and Troposphere, slows down a bit. This time delay may cause error in calculating the exact time and position. To overcome the problem, the GPS system employs a built in model that estimates an average delay time in order to correct the error partially.
*Orbital Error
The orbital errors are caused due to the inaccuracies of the reporting location of satellite. They can be also known as ephemeris errors.
* Signal Multipath
Tall buildings and large rock surfaces reflects off the GPS signal, increasing the travel time to reach the receiver. Since the time reaching the GPS receiver is delayed, the signal causes error.
*Receiver clock error
The receiver clocks on the GPS receivers are not as accurate as the atomic clocks on the GPS satellites. Hence timing errors may occur slightly.
One of the other factors that may lead to inaccuracy of data is visibility of the satellites. More the GPS receiver can see satellites, more accurate the calculations are. The visibility of the satellites cannot reach underwater, indoors and underground hence the GPS device do not work at these places.
Source: Google
100% functioning
As with practically any other device, the Samsung Galaxy S3 has its fair share of complaints. Some have workarounds, some can be solved with mods or apps, and some seem to have no fix at all.
One common issue on the GS3 is that the GPS won't seem to work at all, refuses to lock onto any satellites, or frequently loses the connection, making it pretty much useless. But there does seem to be a quick (and somewhat unthinkable) solution to this—tightening a few screws.
You don't even have to take the battery out for this!
Just pop off the back cover on your GS3 using a flat head screwdriver, spudger, or your fingernail. Around the phone's edges, there are 10 screws. Use a small Phillips screwdriver to tighten them as much as you can.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you're finished, put the back cover back on and try out your GPS again. You should be able to get a lock on more satellites along with faster navigation and less signal dropping.
If you start to notice issues again, just retighten the screws, just like you would for that wobbly dining room table that always needs retightened.
It may be annoying, but it's free and a lot quicker than getting a new phone. And this should be your first DIY fix tried before resulting to installing new ROMs, flashing back to stock, trying aGPS patches, editing your gps.conf file, uninstalling/reinstalling Maps, etc.
Did this trick work for you? Let us know in the comments below.
Got wonky working Wi-Fi on your GS3? Try out this trick for getting a better signal.
Umm, you're about 4 days late on this one. There is already a thread announcing this fix:
http://forum.xda-developers.com/showthread.php?t=2201668
I've had the phone for just over a day now and the battery life has been fantastic when outside where I have great coverage. However, for the past couple of hours I have been studying in the basement of the library at my college and I noticed that my battery drains around 20-25% per hour (not a typo) when my phone is not attached to AT&T's network, and it is searching for a network. The only application that I have that accesses data when the screen is off is Google Now, and even that has location settings turned off.
It appears that Google Now will constantly try an access a data network even if you are in an area with no coverage at all. My Galaxy S3 did not have this issue. The phone would simply stop accessing data after a short period of time if it could not attach to a data network.
Anyone else have this issue? I have had to turn data off and it seems to have fixed the issue. My phone is no longer using any battery idly.
You can see what I am talking about in this picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5 using Tapatalk 2
ComradeNF said:
You can see what I am talking about in this picture
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Does that drain persist after a reboot? My phone started chewing through battery for no reason at about 35 hours of uptime.
From what I experienced on my S3 and also the N5, whenever I go to school, I'd have to turn off my data because my coverage sucks there. However, if I leave the data on, it begins to roam/search for 3G signal and will eventually drain my battery. What you're experiencing seems normal to me. Just turn off your data and hop onto the WI-FI connection to conserve your battery. Seems to do the trick for me all the time.
So my Nexus gets very poor reception. And I've seen some other reports, but I think this problem is also responsible for all the people complaining of inconsistent connections and drops as well as bad battery.
When the signal is less than -90dBm the phone drops connection, so because the reception is poor this happens A LOT. When laying the phone on the router, I only get -40dBm, and 2 feet away -75dBm. 20 away it hovers high -80's or worse.
Also the bad battery because the dropped connections lead to scanning and scanning leads to battery drain. In my bedroom, where I have bad reception, my battery drained completely from full over night, but when left down stairs near the router I just only 10%.
And I know it's not the router because when comparing with my Galaxy Note 8 tablet I'll get -56dBm in my bedroom compared to -87dBm with the Nexus.
Sent from my Nexus 5 using xda app-developers app
So look at Dominion SSID...
The first 2 pics are from the Nexus and GNote respectively. Dominion and Dominion2wire SSIDs are about 20dBm stronger on the GNote, and you'll notice the GNote gets far more SSIDs in the scan.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second 2 pics show a range extender for Dominion I have setup upstairs in the next room. The Nexus only sees the Extender, not the downstairs signal. GNote sees both and sees the extender very well. Almost 30dBm stronger in this picture.
Have you rooted and/or flashed a ROM on your Nexus 5?
If not, you might want to try that, go into recovery, then wipe your data and fix permissions. Not to sure what's happening with your device, but it's worked for me when I've had similar issues with other devices.
Hello All,
On both my wife's and my Tmobile S7s running 6.01 on the November security patch, the location services are terrible. The phone keeps thinking I am at my house when I am 20 miles away at work. My wife has the same problem. If I toggle location services off then on, it instantly updates to the correct location. Eventually if defaults back to my house. This wouldn't be such a huge deal if I didn't have a SmartThings home automation system. SmartThings keeps unlocking my front door, turning on lights, and putting the heat back on because according to the phone I am at my house and the automation kicks in. Here is what I have done to try to fix the location issue:
- Location on with method = GPS, Wi-Fi, and mobile networks.
- Improved accuracy on with Wi-Fi scanning and Bluetooth Scanning enabled.
- Under Optimize Battery usage, I have unoptimized Location Services (meaning it should always be running).
Does anyone else have this problem with their S7s? If it were jsut mine, I would chalk it up to a faulty device, but it is happening to my wifes as well. Any other tricks to make this stop happening?
Check your apps to make sure the location permission hasn't been unchecked. Exactly which app could be missing that is hard to say. A factory reset might be your friend for this kind of situation.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}