Looking in location settings and there are three options. Use wireless network, use gps, and use sensors. Ive never seen the "use sensors" option before? Im assuming for best gps performance is to have all three checked?
I'm interested to know this as well...
Sent from my SPH-D710 using XDA App
Well the description that pops up when you check it elaborates pretty well. From what I gathered, it's mainly meant to be used as a battery saver when you're using the GPS walking around, especially indoors. What I think it's doing is using things such as the accelerometer and compass to aid the GPS in determining the direction and speed that you're moving in, thus meaning the GPS doesn't need to actively search for your signal as hard, which would drain your battery when that signal is weak (I.e, indoors).
What really excites me about this feature is not the battery savings,but the potential that the gps might now finally be able to keep a lock in an urban downtown. I live in , so the mountains combined with the buildings means that once I set foot downtown my gps is next to useless. This new feature seems to have the capability to eliminate that.
Plus, it might result in overall accuracy improvement in any generic gps scenario.
Sent from my SPH-D700 using xda premium
Im sure sensors mean accelerometer/gyroscope for navigation while driving? Like when you hit the brakes, accelerate, turn, etc. seems cool
Edit: and what squshy said lol
Coming from an Evo 4G and only used Google Navigation once in my car so far. I enabled the sensors for GPS when it prompted, and I noticed the tracking was off when the car was stopped, mainly at an intersection.
It showed me moving back and forth on the road, enough that it showed crossing the intersection, and twice it showed me turning. Again this was all while still but I was holding the phone when looking.
So maybe by sensor they mean the motion sensors and the slight movements were putting it off? I'll be using it again today and I'll try with the sensors for GPS disabled.
And just to add, overall the GPS still worked in terms of getting me where I needed to go, just haven't seen that kind of tracking jitter from the Evo.
conscio said:
Coming from an Evo 4G and only used Google Navigation once in my car so far. I enabled the sensors for GPS when it prompted, and I noticed the tracking was off when the car was stopped, mainly at an intersection.
It showed me moving back and forth on the road, enough that it showed crossing the intersection, and twice it showed me turning. Again this was all while still but I was holding the phone when looking.
So maybe by sensor they mean the motion sensors and the slight movements were putting it off? I'll be using it again today and I'll try with the sensors for GPS disabled.
And just to add, overall the GPS still worked in terms of getting me where I needed to go, just haven't seen that kind of tracking jitter from the Evo.
Click to expand...
Click to collapse
Interesting. Looking forward to your results with the setting off.
---------- Post added at 09:57 AM ---------- Previous post was at 09:56 AM ----------
squshy 7 said:
Well the description that pops up when you check it elaborates pretty well. From what I gathered, it's mainly meant to be used as a battery saver when you're using the GPS walking around, especially indoors. What I think it's doing is using things such as the accelerometer and compass to aid the GPS in determining the direction and speed that you're moving in, thus meaning the GPS doesn't need to actively search for your signal as hard, which would drain your battery when that signal is weak (I.e, indoors).
What really excites me about this feature is not the battery savings,but the potential that the gps might now finally be able to keep a lock in an urban downtown. I live in pittsburgh, so the mountains combined with the buildings means that once I set foot downtown my gps is next to useless. This new feature seems to have the capability to eliminate that.
Plus, it might result in overall accuracy improvement in any generic gps scenario.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I get the description but im curious if this is a setting we should leave on all the time or if it is better used for specific uses.
Haven't driven yet but did bit of Googling. I'm conditioning the battery, bored waiting for it to charge fully, lol.
squshy 7 has it in that it's the gyro motion sensors. A few other Samsung phones with the feature say that's it's meant for pedestrian navigation and urban areas where it's having a trouble tracking enough satellites.
Samsung's docs didn't say anything about disabling it outside those scenarios, but there are some forum posts regarding GPS stability issues and people seemed to have better results when they disabled sensor aiding for driving.
Some users mentioned that calibrating the gyro motion sensors and the compass helped. One Samsung user guide said to keep the phone flat and pointing in the direction you're moving and to avoid any magnetic fields.
So still testing it later while driving, also going to try both on and off while doing walking navigation. I'm in downtown LA so I'll be able to test the urban effect.
There's a good sized thread on the Galaxy S II forums about gps issues. Skimming around it looks like it's split between people saying GPS is fine and otherwise.
conscio said:
Haven't driven yet but did bit of Googling. I'm conditioning the battery, bored waiting for it to charge fully, lol.
squshy 7 has it in that it's the gyro motion sensors. A few other Samsung phones with the feature say that's it's meant for pedestrian navigation and urban areas where it's having a trouble tracking enough satellites.
Samsung's docs didn't say anything about disabling it outside those scenarios, but there are some forum posts regarding GPS stability issues and people seemed to have better results when they disabled sensor aiding for driving.
Some users mentioned that calibrating the gyro motion sensors and the compass helped. One Samsung user guide said to keep the phone flat and pointing in the direction you're moving and to avoid any magnetic fields.
So still testing it later while driving, also going to try both on and off while doing walking navigation. I'm in downtown LA so I'll be able to test the urban effect.
There's a good sized thread on the Galaxy S II forums about gps issues. Skimming around it looks like it's split between people saying GPS is fine and otherwise.
Click to expand...
Click to collapse
Good info. Since i live in a rural area i may just disable it for now.
Related
Now i love my desire... Its fantastic but it isnt without some issues...
One ive noticed that could be a problem esp when your working with reality overlay apps...
The compass doesn’t seem to work that well...
Its slow to respond to movement and even when it does move its horridly inaccurate. north seems to have a room for error of 60-90 degrees.
Has anyone else noticed this? Is it the same for most digital compasses? or do i have a faulty module?
Hi Nutsy,
I've also noticed these issues with the compass in the Desire. I've worked with magnetic compass chips before and I think it's all to blame on the way these compasses work:
To sense the earth's magnetic field they use a two- or three axis magnetometer. Although it's a very accurate way to sense the earth's weak magnetic field, it's also very sensitive to any other magnetic field. That means that the presence of ferromagnetic materials (like iron) or electrical currents in the vicinity might really screw up your compass reading.
So electrical wires, iron piping, laundry machines (almost anything that you would find indoors that runs on electricity or contains iron), will interfere with your compass.
a good alternative would be to use a gyroscopic compass like they do on submarines, but I don't think these fairly expensive devices aren't used in mobile equipment yet. So the only thing to do is to stay away from anything that might interfere.
The slow response to movement might be caused by internal filtering. These analog sensors produce quite an amount of measurement noise. In order to cancel this, they probably use some sort of filtering algorithm like this one:
step 1 -> Take a new sensor reading.
step 2 -> Add it to a buffer that contains the last 25 readings.
step 3 -> Calculate the mean value of all measurements in this buffer. This will be the compass heading that is sent to Android OS or your application.
step 4 -> Repeat this cycle every 25 milliseconds.
Hope this answers your questions. Of course if you compass readings never make any sense under any circumstances, the thing might just be broken...
Friendly regards,
Joost
Ps.
There's an App in the market called "Metal detector" that actually uses the interference "problem" with the compass to detect ferromagnetic metals.
Wow Thanks for the really detailed reply...
Im glad its not just me then... Didnt really want to RMA it over a dodgy compass unit.
And thanks for letting me know about that app... sounds usful... I guess it could be used to detect wireing in plaster as well?
You're welcome.
In theory you could use it to detect metal or wires in a plaster wall. I've just tried it, and it works quite well. On the other hand, I really don't want to risk electrocution by trusting a telephone to find electrical wires...
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
jimmymagix said:
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
Click to expand...
Click to collapse
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Smauglys said:
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Click to expand...
Click to collapse
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
poldie said:
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
Click to expand...
Click to collapse
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
Click to expand...
Click to collapse
Just tried what you said. It did not help for me. I turned it of completely.
Smauglys said:
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
Just tried what you said. It did not help for me. I turned it of completely.
Click to expand...
Click to collapse
Just went outside to test it again. And I think I found how to get it working. If i launch the compass application, and try to turn the phone in the flat position (on its back), then the arrow moves in random directions. But if i lift the phone that it is facing straight to my face, and then turn left and right a few times, like a steering wheel, the compass "calibrates" as I can see. And then when I lay it down again flat, it starts to work normally. Can anyone try this, if you understood my instructions?
A more accurate way of calibrating the compass is by rotating the phone twice around each axis, ideally you should do this away from anything metallic or any interfering magnetic fields preferably outside.
Er......
Where is the compass?
I dont seem to have a compass! In my list of apps there just isnt one called compass...
The Analogue Compass app is very buggy for me so I use the Compass app -> http://www.androlib.com/android.application.com-apksoftware-compass-qAC.aspx
When taking readings, I;
Always have to recalibrate on startup as far too many objects cause large interferences within the sensor making it go astray, even the charging cable causes it to go berzerk. The known working routine is to calibrate by fast twisting and turning the phone [I do it after running the built-in figure 8 calibration routine]
Keep it mid-upper body height with no metals nearby (jewellery/belt/metallic objects minimum >5ft away), holding still and level across the x-axis
Point the upper-end of the phone in the direction I want the bearing of (this depends on the type you use though, I use the digital type)
I spin the phone around and then retake 2 more readings for a total of 3 readings - averaging them out for a final mean reading
I only have 2 directions calibrated through professional consultation when this room extension was built a few years back and know the rough directions all sides this property faces, but in particular, I'm 100% sure of the exact degree reading one wall faces. This app using the built-in compass sensor reads that bearing spot on everytime after calibration (fluctuation is 1-2 degree max).
Some friends in a Lithuanian Android forum, suggested to do this, like it is shown in the video. Works perfectly every time. And I thought that something was wrong, because I never had to do anything like this on my G1.
Youtube video ID, because I cant add link because of spam protection http://www.youtube.com/watch?v=sP3d00Hr14o
I have a Hero and have tried several running apps and some are better than others.
I like RunKeeper http://runkeeper.com/home and find it to be ok for accuracy but not perfect. On a clear days it works well but cloudy days its a bit off. I don't think the accuracy issue is due to RunKeeper I think it is the phone. However other apps are terrible for accuracy like Cardio Trainer which shows 4.3 miles for a 5K/3.11 miles.
Here's a map showing what it looks like on a cloudy day using RunKeeper
http://runkeeper.com/user/d12bn/activity/26716842
Showing 3.36 miles for a 5k/3.1 miles measured with a Garmin and my car.
Its not bad but my Garmin would still be very accurate on the same day. So just wondering if the EVO GPS is any better?
Thanks JB
Personally, my gps is spot on. If it says X is 5 miles away, I only have +/- .1 tolerance.
I have not tested it over distance like this, but I do know that I've seen my GPS as accurate as 4m.
I havent tried mine over several different weather conditions but when I have tried it I can watch the little arrow move from the front of my house (facing east for example) to walking around to the back yard and facing another direction... Even if I turn it on in the house, or somewhere else, it always places me w/in the same 1/4 of a block -- I know that's not a scientific measurement, but all I'm sayin is that for me, the times I've tested it, it's pretty dang accurate... Also, I havent tested it over distances when runnin (it is accurate in the car)... But I think I'll give it a shot now that you mention it
Simply better than any other GPS for me so far. I agree on couple of meters difference.
Thanks
Cool let me know what you find. I can say using my Hero for navigation while driving works great. However using it to measure walking/running may have to be more accurate, 3 tenths of a mile short or long makes a difference at the end of 3 miles.
blakjak220 said:
I havent tried mine over several different weather conditions but when I have tried it I can watch the little arrow move from the front of my house (facing east for example) to walking around to the back yard and facing another direction... Even if I turn it on in the house, or somewhere else, it always places me w/in the same 1/4 of a block -- I know that's not a scientific measurement, but all I'm sayin is that for me, the times I've tested it, it's pretty dang accurate... Also, I havent tested it over distances when runnin (it is accurate in the car)... But I think I'll give it a shot now that you mention it
Click to expand...
Click to collapse
d12bn said:
Cool let me know what you find. I can say using my Hero for navigation while driving works great. However using it to measure walking/running may have to be more accurate, 3 tenths of a mile short or long makes a difference at the end of 3 miles.
Click to expand...
Click to collapse
Mine has been as accurate as I previously stated, even when walking.
teh roxxorz said:
Mine has been as accurate as I previously stated, even when walking.
Click to expand...
Click to collapse
Mine has been accurate down to 3 meters. Walking down to the park (about 1.7) miles is pretty much spot on in google maps. I just have to tap the little blue arrow a couple of times to "improve" the location before I start walking or driving anywhere.
Longest I've tested it is about 17 miles driving. It was off by about .1 as a prior user stated.
First of all, my GNex gps works.
But, my experience so far were bad and got into my big frustration.
I went to France by car, about 1200 km.
During this trip I used three devices:
- HTC Desire, stock Android 2.2, no sim card
- Nexus S, stock Android 4.0.4
- Galaxy Nexus, stock Android 4.0.4
All used the same navigation software, Sygic 11.2.6.
Weather was very good, bright and clear.
The navigation performance, HTC Desire is the most solid and stable. No jumpy routing. It was almost flawless.
The Nexus S was also stable, no jumpy routing and again almost flawless. Sometimes between high buildings area, it could lost the gps signal.
The GNex was terrible! Very often the routing was jumpy, especially when my car stop. The navigation think my car was in other road! That caused the routing to spin and I must drive further to stabilize the routing. It was frustrated and I lost confidence with using it as car navigation, period.
The HTC is my main device for car navigation, because its so stable, no jumpy no spinny routing, solid performance. But one day the battery run flat for no reason. Thats why I must use my supposed to be the best device, the GNex to replace it to continue. But alas, as I explained above, it was terrible experience. I was lucky that I brought my Nexus S, to save the day.
This GNex bad car navigation is my biggest frustration.
I cannot fault the weather brcause it was clear sunny and I could get sat fix.
I cannot fault the Sygix either because the other two devices were fine, no problem.
But why is this jumpy and spinny routing on GNex?
Ok, I cannot test Google Navigation, because I cannot afford data connection during this trip, roaming.
So, my question, have you ever got the same experience? Terrible, jumpy, spinny routing with GNex car navigation?
Is there any way to improve? Or makebthe gps work much better?
Is there any ROM specialized to improve the gps for navigation?
Thanks
I believe the GPS unit in the GN is weak compared to my old iPhone 4. Though, I was able to get decent, more accurate performance by disabling "Google's location service". I use the GPS for directions in Google Maps as well as RunKeeper and it's really made a difference for me.
Side note, my iPhone locked in my GPS location while I was at work (5-story building, 3rd floor) without a hitch. The GN tries to lock, but it's 50/50...
I hope this helps... Good luck!
Doubt it'll help...
But it WILL help get a faster lock in the case of a GPS drop.
Mine locks in in like 3-5 seconds after using Faster GPS.
I, however, very rarely use GPS for actual navigation.
In fact...I haven't had to yet with my GNex. So I can't say if I do/don't have a problem.
Before Navigating, i usually open GPS test Plus to lock-in my location...then it's smooth sailing after that. Btw, i use CoPilot Live Premium.
PS. It takes the phone around 10 secs to get an accurate lock in.
babymatteo said:
Before Navigating, i usually open GPS test Plus to lock-in my location...then it's smooth sailing after that. Btw, i use CoPilot Live Premium.
PS. It takes the phone around 10 secs to get an accurate lock in.
Click to expand...
Click to collapse
How is this CoPilot?
Does it run smooth?
When the car stop at traffic light for quite long periode, does it jump or spin to other road?
PS: I turned off Google Location Service already, never used it.
My first nexus also had a very bad GPS unit.
I got new one and it was much better but after installing 4.0.4 it is worse again.
If this will not be fixed with the next update I will sell my Nexus and maybe buy a HTC one x.
By the way, this is a short video that shows the problem with my first device. If this is the problem you have you should change your device to a new one:
http://www.youtube.com/watch?v=8ueTSHyZHyw
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
FWIW, I've had little to no issue using the stock GPS and built-in Navigation.
I get weird GPS navigation sometime where it thinks I'm off the rode to the right and driving through houses basically. Or i get turned around for no reason. The kicker is that I check GPS test and my accuracy is spot on with a healthy number of satellites so I'm not sure just a weak signal problem.
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
That would explain why the gnex won't get a fix while at cruising altitude..
Beamed from my iPad Mini
Hi,
I had the same issue with my galaxy SII i9100g.
I had a mountain climbing with a summit of 4500 meters, in the beginning we really didn't need gps tracking because there was signs showing the track in the mountain. I checked the device and everything was fine the first day the signals were ok and I had my position on the phone. but in the second day when it got foggy we were in trouble as I wanted to know our altitude. and gps signals wouldn't fix. I had ten or so satellites in view but the message said "waiting for gps fix" and it didn't fix at all. I also restarted the device but it wouldn't help.
in another trip on a plane I started recording the route with gps, and I noticed last recorded point was at an altitude of 3985 meters. and when the plane reached higher altitudes i lost the fix.
I think they should give us warning about using such devices in hiking trips. it could make real trouble for me.
It might be a problem specific to the GPS receiver used in Google Nexus. Giving that I've noticed GPS late fix problems with my Nexus (compared to a Galaxy S3), I'll try checking out the internet myself too.
Have a good day!
I find it remarkable that high-tech companies such as Google or Samsung keep managing to put in design flaws or outright defects that can easily kill people. The one described here is an outstanding example. If using the GPS with good success while hiking, nobody in his right mind would ever get the idea that the GPS would suddenly stop working above a certain altitude. So some programmer has intentionally put in a deadly trap (unless you want to believe that a command like "if (altitude >= 4000) return null;" can be written inadvertently). This is sabotage of a very dangerous kind.
Another less obvious example is the design of the power button, which can easily be activated inadvertently. If somebody needs the phone to navigate and survive in the wilderness and decides to power the device down until the next critical point to keep the battery charged for a long time, the device can easily lose all power just because of an inadvertent power push in a bag or pocket. The obvious solution here is a recessed power button or, in a cinch, that the device automatically powers down again if no user action happens within reasonable time after power-up.
The rule is generally that the design is stupid, the defect is obvious, at least one solution is also obvious, and even when the flaw or defect is brought to their attention, it is not fixed. Dangerous idiots at work. Perhaps they reckon if somebody actually dies, it will be impossible to prove that the smartphone design defect was a contributing factor. It is the responsibility level of a school child.
I am sure there are more examples for this behavior.
I am not saying that people should hang their lives on their smartphones. If the smartphone is the only thing that keeps you alive, then you have already made a planning mistake. But we all know that one can get into situations inadvertently where several things go wrong in unlikely ways. In such a case you can get into a situation where your life depends on the GPS in your smartphone, and then either of the defects described above could conceivably seal your death.
My screenshot from the plain
Sent from my Nexus 5 using XDA Free mobile app
giacomociani said:
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
Click to expand...
Click to collapse
Which model is you GN?
Sent from my Galaxy Nexus
Jar3112 said:
Which model is you GN?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It's a Samsung Galaxy Nexus I9250.
I should also mentioned that in the meanwhile I have found on various forums a (very limited) number of users reporting the same problem with the same phone, but no one reporting that it works for him. So I start to be confident that it is a problem of this particular model...
Does anyone else have this issue? My GPS loses connection to the satellites every couple minutes. And yes, I have the latest map update.
Must be the bug in update. Try to use 3rd party app! Just because i never updated mine, and is working like a charm
Sent from my LG-E988 using xda app-developers app
The GPS in my phone is not very accurate. Maybe its just this phone. I only get relatively good GPS reception at night.
Sent from my LG-E980 using Tapatalk
Thanks guys. I'm starting to think it may just be this phone as well. The first map told me I was 3 miles away from my house....lol...and the second was accurate but keeps dropping the signal. I do have carhome. I'll try that and see what happens.
I also have this issue though the GPS (which is used a lot by me) was quite OK in the beginning after I bought my LG OG PRO.
I read in one of the Samsung NOTE forums that people mention the same problem claiming that the drops come when there is an "interruption" (which can be an incoming call or SMS or switching from 3G antenna to 3.5G for example). After reading this I realized that my GPS gets lost always after an incoming call plus I see at least a couple of places along my daily driving routine where GPS is lost exactly at the same place every day (making antenna switch assumption logical).
There were no any conclusions or suggested solutions in these forums, people even do not know if it is software or hardware related.
Anyone has such an issue too? Any recommendations for possible fix?
I can't believe but it seems I solved the problem with GPS - 15-20 seconds for GPS lock, no dropping and GPS test application shows very nice picture of 8-9 satellites constantly locked up while most of the signal bars are yellow (i.e. the signal strength is good).
I searched a lot as it really bothered me because I use my GPS very much plus I can say that beside this annoying thing I am very satisfied with my LG OG Pro, but nothing helped until I found this video: https://www.youtube.com/watch?v=QBpNtWvY454 (it explains the solution for Nexus 5, but my problem is identical)
Basically, the problem is that there are special contacts on the motherboard connected to the GPS antenna which is part of the back cover and the contacts are not tightened well to the GPS antenna (look at the attached picture where I put the red arrows at the relevant places). Due to the bad touch between the contacts and the antenna, the GPS does not work properly. So, all you need to do is to remove your back cover, gently "un-glue" the GPS antenna end (the rectangle part on the back cover containing 2 golden dots), lift it up a little and put a piece of paper that will tighten the antenna and mother board contacts when the back cover is returned. Good luck.
It is NFC Antenna, you cant fix GPS this way.
I have same issue, but i think NFC and GPS antennas are different. I am disassemble the phone and pull up all golden springs - but gps still very weak(((
Any solution?
same GPS problem for my g pro.
GPS is weaker and weaker
I realigned all the pins inside the phone and fixed it for a bit, but the signal was still weak. I figured it was the modem. I installed a custom rom and it worked like a charm!