Related
Good evening guys-
After updating from ICS to JellyBean, my gps cannot find or lock onto any satellites.
If I enable wifi, its accurate to 20meters.. If not, it won't lock even after 15 minutes.
Any help is greatly appreciated-
mine has been similar in PA2.00 and CM10.
It actually will lock after a long time. Sometimes up to 30 minutes.
Interested in any answers... I noticed in the gps.conf file agps appears to be off. I don't know if that is the issue.
Unfortunately searching for a fix just reveals too much information with a lot of supposed fixes, but no consensus so far as i can tell.
brian Marshall said:
mine has been similar in PA2.00 and CM10.
It actually will lock after a long time. Sometimes up to 30 minutes.
Interested in any answers... I noticed in the gps.conf file agps appears to be off. I don't know if that is the issue.
Unfortunately searching for a fix just reveals too much information with a lot of supposed fixes, but no consensus so far as i can tell.
Click to expand...
Click to collapse
Actually agps was turned off to improve lock times...some people noticed no difference with it off, others noticed huge improvements with half the lock time
You can change it to true, then wipe cache and dalvic cache in recovery and see if it makes a difference
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
Actually agps was turned off to improve lock times...some people noticed no difference with it off, others noticed huge improvements with half the lock time
You can change it to true, then wipe cache and dalvic cache in recovery and see if it makes a difference
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
is that a 'go ahead and try it, it wont work, but go ahead and try it anyway' ?
It seems like a lot of people are having problems with GPS in jellybean, and some aren't. There's so many 'this worked for me' solutions, but I'm starting to think it's coincidence.
Someone mentioned installing and running copilot once. Did that. it didn't work. Without root permissions what could it really change to improve anything?
I ran Faster Fix. It edited my gps.conf file (which it doesn't tell you that it does) It didn't help. it might have made it slightly worse.
I found a few other gps.conf files for jellybean ROMs, but haven't tried those yet.
This is how we learn and share our info, by trying. Just make a back up of anything that you want to change or replace.
GPS works perfect on my PA Jelly Beaned Infuse. First I ran GPS Test, it took a good twenty minutes if not more for it's first lock.
But now, I get a lock in a few seconds.
GPS Test, is free in the market.
Planning my escape!
GPS Test has kicked my GPS in the butt and got it working with almost every ROM I've flashed. Once you get over that first delay (downloading satellite data?) the first time you run it, it locks on fairly well afterward. At least, that's been my experience
Truckerglenn said:
This is how we learn and share our info, by trying. Just make a back up of anything that you want to change or replace.
GPS works perfect on my PA Jelly Beaned Infuse. First I ran GPS Test, it took a good twenty minutes if not more for it's first lock.
But now, I get a lock in a few seconds.
GPS Test, is free in the market.
Planning my escape!
Click to expand...
Click to collapse
I've already done that. It helped the next time I ran maps. When i left work yesterday I had maps give me turn by turn directions home. It took a couple minutes to lock, but after that it was working.
Then this morning I tried again. It wouldn't lock at all on the way in to work this morning. (only a 15 minute drive)
I also tried editing my GPS conf file this morning. I tried using ES file explorer, root explorer, and flashing. All three resulted in an empty file. ES says it was successful. Root explorer gives an error message 'there was not enough free disk space to complete the paste operation'
Flashing says it was successful, but again, it ends with an empty file. 0 bytes.
The file i used for the flash attempt is here. http://forum.xda-developers.com/showthread.php?t=1817558
With the gps.conf file I'm going to go leave the phone out in my car with gps on and see if it locks.
I understand that developers do a lot of work on this. I'm not trying to be a jerk. I just see a lot of people having the same issue and no agreement on a solution or even what the actual problem is.
brian Marshall said:
...
I understand that developers do a lot of work on this. I'm not trying to be a jerk. I just see a lot of people having the same issue and no agreement on a solution or even what the actual problem is.
Click to expand...
Click to collapse
I believe this is because there is no solution. If you want to try to help solve the problem, "adb shell" in and start tinkering.
You'll quickly find that GPS is anything but an easy thing to fix. A good SUPL provider for you may be completely different for others.
I can't find the Answer that fixed it for me,
but what I did:
Plug phone in, disable wifi, leave phone near window, and let
https://play.google.com/store/apps/...251bGwsMSwyLDYsImNvbS5hbmRyb2lkLmdwc3Rlc3QiXQ..
that app run... :45 minutes later it locked (GPS icon on Status Bar stopped blinking and showed locked, solid) with 7 satellites.
waited, rebooted the phone, and it locked in about 3 minutes.
-hope this helps.
other than that, love this ROM!
choffman said:
I believe this is because there is no solution. If you want to try to help solve the problem, "adb shell" in and start tinkering.
You'll quickly find that GPS is anything but an easy thing to fix. A good SUPL provider for you may be completely different for others.
Click to expand...
Click to collapse
Now that is an actual answer.
I suppose part of the problem for us noobs sorting through 300 page threads is all the filler with people saying "great rom omgz so awesome" even when they are posting on the first page and the ROM hasn't even been up long enough to do much more than flash it and swipe through the home screen.
All through out the CM10 and PA threads there are people saying GPS is working flawlessly... and then other people saying they have some fix. I guess people aren't supposed to post frivolous stuff in the dev threads, but they do.
Anyway, I ended up going back to GB as GPS is something I really need.
Hey guy's, i've also been having allot of issues with GPS just not being what it used to be, and it's pretty obvioius that this is an issue across the board for all JellyBean roms. I think those who mention that "GPS works flawlessly" don't quite understand the issue with AGPS (Assisted GPS), or they are not quite testing it thoroughly enough to see the problem.
To get an understanding of what AGPS is, and how it helps improve initial lock times, have a read here: http://en.wikipedia.org/wiki/Assisted_GPS
Also, to gain a better understanding of what I mean by "cold start" as you read below, and how it differs from a warm or hot start please read the following: http://m.gsmarena.com/glossary.php3?term=gps
That being said, i have been doing allot of digging in the hopes that someone out there has a solution to the problem with AGPS on the CM10 based ROMs on our phone.
To clarify the problem: AGPS does not seem to work and Initial lock times from a cold start can take several minutes, (this is not normal if AGPS is doing it's job). To clarify further, no one is saying that GPS does not work, it does in fact work, it just takes it's sweet time to lock and it seems to rely on pure GPS to download ephemeris data from the actual GPS birds for satelite lock acquisition, rather then downloading AGPS data over the network to speed things up. After the initial lock though, GPS functions as it should. After this point, if you do not use the phone again for several day's, it seems that upon first firing it up again you will experience the long delay in first lock. This is especially true if you keep GPS services turned off ussually to conserve battery. Those who report GPS is fine are probably keeping GPS services on all the time, and your GPS is probably working in the background at times and obviously will start up allot faster then it would from a cold start. (This is where i believe all the conflicting info comes from!)
The only info i have been able to find that did actually have an impact on my lock times was the thread below.
http://forum.xda-developers.com/showthread.php?t=1881655
I just started testing this out yesterday and i have seen some positive results. But i would caution those of you out there, and say that this is probably not a "fix" per se, but it did help cut down lock times in my case and at the very least it is a very inoformative thread that everyone should read.
What i have realisticly been able to achieve from a cold start is about 75 seconds to lock at the fastest. i.e. GPS services were off, i turned them all on, and now i started up GPS Status or GPS Test to get a lock. After that, as long as I haven't rebooted my phone it takes only a few seconds to lock.
How i tested, i started GPS Status, I then went to Tools --> MANAGE A-GPS STATE -> RESET (This is important to ensure you are clearing previously cached data. We want to make sure your previous cached info does not skew the effects of your changes.
I then replaced the gps.conf with the one contained in that thread, and i also made the change that was suggested in the Notes section that suggested modifying or adding a line in your build.prop file to "ro.ril.def.agps.mode = 1". This change set's your gps to use AGPS in Mobile Station Based (MSB) mode. For reference, setting it to "2" would set your AGPS to function to Mobile Station Assisted (MSA) mode. (Mode 1 - gave me more accurate initial locks at the expense of a bit longer lock times, Mode 2 gave me slightly quicker initial lock times, but was rather flaky and my position drifted quite a bit until GPS was running for quite some time.)
If your curious what is the difference between the two modes, see here: http://en.wikipedia.org/wiki/Assisted_GPS#Modes_of_operation
After making the changes to gps.conf and build.prop i rebooted my phone. When phone reboots, i then go back into GPS Status app, select settings, Tools --> MANAGE A-GPS STATE -> RESET, and then back to settings, Tools --> MANAGE A-GPS STATE -> DOWNLOAD (This should force the phone to attempt an AGPS download, if it hasn't already done so upon launching the app).
I have seen this same gps.conf being used in the newer RemICS-JB build. However based on the lack of feedback in that thread, i don't know if this is the golden fix we have all been looking for.
Even though this may not fix all your issues, i hope at the very least it helps clear up what the actual problem is, and how AGPS is supposed to work.
** Important Notes: **
- The version of the config that i was using was the Download the Google Specific No-SSL v3.1
- If you use the SSL version, then it will also require that you download the certifcate file. It's best to just stick with NO SSL as is explained in the thread.
- You should also note that i have cleaned out all the live wall papers, face unlock, and allot of other crap that i don't use to free up space in the /SYSTEM partition. I now have aproximately 21MB free in this partition. I think at least part of the problem with certain ROM's is that they have the /SYSTEM partition filled to the max with virtually no free space at all. I'm no expert on the subject, but i'm guessing that the AGPS data get's downloaded to this partition some where. Obviously if there is no space, then that would cause issues. Several others have reported shortened initial lock times after making room in the /SYSTEM partition.
- Another mistake people are making when testing AGPS and reporting false info, is having their WIFI on when testing GPS. To isolate the issue guy's you need have wifi off and you need to use a tool like GPS Status or GPS Test that shows that actual lock to satelites. You cannot properly test this and see the issue by using WIFI and turning on Google maps. Google maps will look at your reported wifi position and to you it looks like bamm.. i just got a lock in 2 seconds to withing 50 meters, wow these guy's are nut's, my GPS is awesome. Guess what.. your wifi and google maps is awesome.. not your GPS.. lol
- If anyone is familiar with running log's, it would be great if you could do a comparison of before and after. Showing the log of a completely fresh JB build, that shows that the AGPS data is not being downloaded, and then another log after all the changes above (including freeing up space in /SYSTEM) and hopefully it will show that AGPS data is now being downloaded and utilized. I myself am not familiar with logging data on the infuse, so i cannot and will not call this a fix until someone can actually show with real log's that AGPS data is now being utilized after these mods.
Thankfully, I'm one of the lucky ones who have always had a working GPS. It worked great when I was running AT&T stock Froyo, really good while I was on XDA GB roms, and fair > good after I went to PA JB. By far Scott's latest release of PA JB has been the best in this respect, but I can't help but tinker now that I've turned into a Droid zombie Strictly speaking the stock GPS configuration included on Scott's PA JB ROM worked charmingly, but I still had an issue whenever the phone went into deep sleep (say overnight without using it) the GPS lock the next morning took almost as much time coming from a sleep state as a cold boot. So, Like DaMeatMan I decided to give http://forum.xda-developers.com/showthread.php?t=1881655 a go. I chose the flashable option, and like DMM also edited the prop file. I picked the Google "no SSL" version 3.1 instead of the AT&T specific version. I figured I would give that one a try.
I'll keep everyone posted, buy my first impression (could be placebo effect) is that this configuration file and modification actually does improve over the original PA JB configuration by a small margin. Reported accuracy is better (by 10ft on average). Satellites in view and actually locking are 1-2 better than before. My main hope is that I can actually fire up Navigation in the morning and get working directions without having to fire up GPS Test first and relock all the NA satellites. I travel a lot, both for business and outdoor sports (hunting and fishing), and I have come to rely pretty heavily on GPS. I got spoiled when I got my first GPS capable phone because that meant I could leave my handheld GPS at home most of the time and that was one less thing I had to carry.
wevsspot said:
Thankfully, I'm one of the lucky ones who have always had a working GPS. It worked great when I was running AT&T stock Froyo, really good while I was on XDA GB roms, and fair > good after I went to PA JB. By far Scott's latest release of PA JB has been the best in this respect, but I can't help but tinker now that I've turned into a Droid zombie Strictly speaking the stock GPS configuration included on Scott's PA JB ROM worked charmingly, but I still had an issue whenever the phone went into deep sleep (say overnight without using it) the GPS lock the next morning took almost as much time coming from a sleep state as a cold boot. So, Like DaMeatMan I decided to give http://forum.xda-developers.com/showthread.php?t=1881655 a go. I chose the flashable option, and like DMM also edited the prop file. I picked the Google "no SSL" version 3.1 instead of the AT&T specific version. I figured I would give that one a try.
I'll keep everyone posted, buy my first impression (could be placebo effect) is that this configuration file and modification actually does improve over the original PA JB configuration by a small margin. Reported accuracy is better (by 10ft on average). Satellites in view and actually locking are 1-2 better than before. My main hope is that I can actually fire up Navigation in the morning and get working directions without having to fire up GPS Test first and relock all the NA satellites. I travel a lot, both for business and outdoor sports (hunting and fishing), and I have come to rely pretty heavily on GPS. I got spoiled when I got my first GPS capable phone because that meant I could leave my handheld GPS at home most of the time and that was one less thing I had to carry.
Click to expand...
Click to collapse
I have been have many of the same problems as others in this thread but I tried the fix in the S3 thread quoted above and it seems to have helped for right now. The first time I ran GPS Test after rebooting it did take a while (5-8min), but after that I get a lock in few seconds. I used the Google "no SSL" package also. I will do some more testing tomorrow and see if its reliable.
Hi guys,
I run PA 4.4 for like 10 days now. Since a week ago I have strange locations in my Google location history - constantly, when not moving - and rather accurate when I am outside (maybe has something to do with the wifi connection when stationary at home or at work?)...
One interesting part of it is: the first days of my new PA experience everything was fine. So probably it does not have anything to do with it. That first day I had the issue my phone crashed earlier while I was outside and I had to do a reboot. Maybe some settings were changed during that!? Or... maybe it doesn't and it's just a coincidence after some apps where updated (Google Search or so)...
I tried quite some settings to figure out what happens here - and it is not trivial - to my mind:
I did another clean install of the ROM; had the same issue again
I changed between "high accuracy" and "battery saving" mode in the location settings; no change
I went to the developer settings and unchecked "accept mock locations" (is that how the option is called in English?); no change
I have a Nexus 10 also running Android 4.4.4 and started to record my location history from that device with different settings: all are fine and accurate! When I record from both devices I can actually see my history jumping in 5-minute-mode...
Any ideas, any suggestions?
Please...
Two more findings, which make this issue even stranger:
When I move in the house - e.g. 2nd instead of ground floor - I get different locations, some 100 or 200 meters away, but both far from home.
I turned wifi off for one and a half hour - that resulted in perfect locations!! Locations were inaccurate after turning wifi on again...
What is wrong here?? So I get more inaccurate locations when connected to wifi!?
i always run straight gps and never wifi. imo its a conflict of interest.
gps is dead accurate, so the only time you could benefit from wifi is when you are in a building with no gps signal, and frankly, why would i need 100% accurate gps if im already in the building.
again imo, what is happening is, it can only reference wifi that it knows the exact location of. it has no way to tell how far from that wifi you are, so its guessing based on a limited gps signal and known wifi points.
i think its a waste of battery to be scanning wifi points all the time any ways, unless you have a constant use for it.
bweN diorD said:
i always run straight gps and never wifi. imo its a conflict of interest.
Click to expand...
Click to collapse
Thank you for the answer! And I sort of agree...
But the question is:
what did change that day when my location started to be different? I never had problems for more than two years of using the location history. Even after moving in April everything was fine with the wifi locations. I get one accurate reading like every one to three hours - so the location jumps from time time. Why is that? Is that a gps reading?
Plus: how could I change the settings? The only thing I can chose from is: "battery saving" (cell towers and wifi) or "high accuracy" (the same plus gps). I selected the second option but obviously still the Google location service does not really use it. When I turn off wifi it can only use cell towers plus gps... but obviously I want to be connected to the wifi when being at home.
I can't say why it started acting up.
If you use WiFi you are kinda stuck.
I only have GPS on and denied anything that wants to use WiFi for any reason.
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Click to expand...
Click to collapse
I guess that option is the "use wifi for location detection although wifi is turned off" which can be found in the wifi advanced options. But I turned that on and off, no change.
But one more test from myself:
I let wifi on but disconnected from my home network. The result is: accurate locations! So the problem is not the wifi itself but a connected wifi!? And it is not only the home network because I had the same issue at work.
Plus: we just had a thunderstorm, that could have been the reason why cell towers and/or gps reacted differently: my location was at some new place about more than a mile away. The worst thing is: accuracy of that location point was about half a mile -- which means: my real location was not inside the accuracy cycle (that blue cycle when using location history)!!
The accuracy cycle is always very small when I get the real readings at home and always about half a mile in radius when somewhere else...
that is basically the problem with using wifi to help. there are too many variables. location needs to know the location of the wifi, but then there is a broadcast radius that decreases accuracy. there is also the question, what does it do when you are connected to a wifi it doesnt know the location of?, that could cause inaccuracy. maybe it makes an uneducated guess, who knows. there is also the issue, what if it thinks it knows the location but its actually wrong?
the list of possible scenarios could go on and on as to why it isnt reporting correctly.
the only way to truly know why it is wrong is to find out why exactly it thinks you are where you are when its wrong. there has to be some exact source of information its using to base your wrong location on. unfortunately, i doubt there is any way for the common user to get this information, let alone take corrective action so its not inaccurate in the future.
wrong locations only when wifi is connected, only on one device
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Tho-D said:
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Click to expand...
Click to collapse
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
On my phone I can force it to use GPS only, I have the option anyways.
Under location I have device only or something like that, it says it only uses GPS when that option is selected.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
Click to expand...
Click to collapse
I thought about that, too. Means to installiert something else, CM11 vor so...
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
Ohh OK, I didn't know that. Thanks for the info
Sent from my LG-VS980 using XDA Premium 4 mobile app
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
so i did a little test today on the way home from work, as i took a different route than normal to avoid traffic.
when i started "maps" i had to allow google location services to navigate. so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
last week i navigated a 3 hour trip, on a different rom, with no issues. today, maps couldn't seem to start gps to find my location to start navigating. so i turned on "high accuracy", more to test than anything else, and it found my location and we were navigating home .
i knew where i wanted to go but at some points that varied from where maps wanted me to go. for a while it did good at making quick corrections to my path. about 20 minutes in, i didn't follow its directions again. well this time, it didn't recognize that i didn't turn, then advised me to make a subsequent turn onto a road that was off the road i didn't turn onto. now, the road i am on is about 1/4 mile from the road it thinks im on, the 2 roads are parallel. well it took maps over a mile, after i made another turn towards the road it thought i was on, before it realized it was wrong and made corrective instructions. after that, i made a quick stop to grab some liquid refreshment for the night and turned off navigation, as i was close to home.
this really goes to prove nothing more than "high accuracy" is not always highly accurate. i traveled across 3 states last week for 3 hours on "device only" and never once was it wrong about my exact location.
just wanted to share my experience, really doesn't help or fix your problem, but may shed some light on the possible inaccuracies across multiple devices.
bweN diorD said:
so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
Click to expand...
Click to collapse
I tried this and yes, Maps works with the "device only" setting. But when using Now it said that location-based cards (weather, traffic, ...) only work with "high accuracy" or "battery saving". So for me this setting is useless.
I guess I'll do another clean install and try CM11 or so...
it's not ROM related
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Tho-D said:
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Click to expand...
Click to collapse
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
bweN diorD said:
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
Click to expand...
Click to collapse
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Tho-D said:
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Click to expand...
Click to collapse
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
bweN diorD said:
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
Click to expand...
Click to collapse
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format /data". Should I try this one?
Tho-D said:
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format data". Should I try this one?
Click to expand...
Click to collapse
I'm pretty sure it says data/media. I don't have cwm on right now or I would check, but I think it is under mounts and storage. It was in the same dir where you can format system and such if I remember correctly.
Its also possible someone removed that option from your version, but I don't know why they would unless your phone doesn't have that partition.
Sent from my LG-VS980 using XDA Premium 4 mobile app
I have a new OnePlus One which I updated to 44S. The GPS will not lock on signal reliably since I received it.
Neither Google Maps and the GPS Status tool cannot lock onto to GPS or it can take up to ten minutes for a GPS lock or it will never lock. I have tried High Accuracy and Device Only Location settings, also updated Google Maps, and applied all stock OnePlusOne updates. Indoors, I can lock onto perhaps 0-1 satellites and outdoors about 2-5. Eventually, I can lock up to 11-12 if I let it sit for a while outside. GPS signal is always lost immediately while in High Accuracy mode after I start moving the vehicle.
I have emailed OnePlus support and got a reply back the next day asking me to create a video. Therefore, I created a video which is linked below on Youtube which shows what it does in Device Only mode.
youtube.com slash watch?v=kDcLk_IuKQ4
Sorry for the URL, I'm a new user here. My question is what can I expect from OnePlus support on this issue and does anyone else have this problem? Today I got an answer to my last reply with the video that I should just do a factory reset and update to 44S from a different tech, so it's not going too well now and I don't think they really try to resolve anything.
I have read lots of threads on the Internet regarding running various fix apps (such as Faster GPS) which means I need to root it but I saw limited success in those posts (I have not rooted yet). I personally think it's a hardware problem since GPS Status cannot lock onto anything unless I give it a lot of time and clear blue sky.
I apologize if this is a repeat post or I committed any other newbie offesnes, but I could not determine a real solution to this problem. Should I keep pursuing an exchange or refund or spend hours more rooting and dorking around with gps.conf settings?
Thanks!
Usually I leave my GPS turned off and when I read your post I went ahead and turned it on and set it for 'Device Only' and experienced the issue. rebooted the phone with the GPS turned on and now I get an almost instantaneous locking.
not sure if you leave your GPS off like me or if you have it on all the time but If it was off when you started the phone try turning it on and reboot the phone and see if you'll get better results.
TheManDroid said:
Usually I leave my GPS turned off and when I read your post I went ahead and turned it on and set it for 'Device Only' and experienced the issue. rebooted the phone with the GPS turned on and now I get an almost instantaneous locking.
not sure if you leave your GPS off like me or if you have it on all the time but If it was off when you started the phone try turning it on and reboot the phone and see if you'll get better results.
Click to expand...
Click to collapse
I have done the reboots. Does not make a difference in getting a lock or not. The GPS has to be left ON for a while to find the necessary number of satellites needed to lock.
Same issue
Did you get a solution from one plus? I have the exact same issue. I use my GPS for driving 3 or 4 times per day since the 44s update I have had 2 GPS locks which I believe is a problem.
Hopefully the upcoming update fixes all!!
Hi, not sure if you found a fix but I had same issue with my OPO so I contact OPO support and they instructed the following:
Please try this software patch as this may fix the issue for you meanwhile we have assigned this ticket to our specialist who will get back to you soon.
Please reply us if this patch does not fix your device
We prepared an Automated batch file which will fix your issue automatically, all you need to do is to download the zip file from the link below and extract it, after extracting please open the "README.pdf" and follow the instructions.
PLEASE NOTE :- IT WILL DELETE ALL YOUR PHONE'S DATA> PLEASE BACK UP YOUR PHONE'S DATA
https://s3.amazonaws.com/oneplussupport/ONEPLUS+ONE-FIX-Windows.zip
Click to expand...
Click to collapse
It fixed my GPS issue for the time being. I'll test out the GPS for a few days and report back. Let me know how things go for you.
Thanks,
Neel
Hello community,
thanks in advance, I have used this site as a knowledge base many times in the past and always found something helpful. Now, however, I will have to ask since I don't now what to do anymore.
I run an i9195 (serranoltexxx) with cm13 and gapps installed. Everything worked just fine. Then I dropped my phone into a bucket of water/household cleaning agent, took out the battery immediately and dried the phone. When I took out the battery, the inside of the device was still dry. After that, I could not use the earpiece for a few days, but this issue has healed itself. Also after this incident happened, my gps was still working.
Now, all of a sudden, gps does not work anymore. I have tried google maps naviation app, gps test and gps status to check, no satellites are found. When using google maps and driving around, the device keeps the rough location, I assume by using the other sources like wifi networks or broadcast cells. Hence I do not think that the location service is entirely faulty.
Now, do you think this is a software or a hardware problem? How can I find out wether or not the gps antenna is broken and needs to be changed? Please be a bit gentle with your answers, I do use a custom rom but would not describe myself as an experienced user
I have a Verizon unlocked Pixel with Magisk 16.4 installed. I have seen a few other threads from maybe a year ago about this same problem, they all seem to suggest the issue is hardware. I want to check to make sure I haven't missed any software check first.
For about a half year now my Pixel has had trouble locking on GPS. Fitness apps like Strava or Endomondo are super inaccurate or report no distance traveled. Google Maps will work, but only in areas heavy with WiFi. I've mostly ignored it, but in the past week I was out of town and could have really used Maps Navigation, so now I'm trying to figure out if there's anything I can do.
I have tried (combined with numerous reboots):
Confirming "High Accuracy" being selected, and also tried "Device Only"
Tweaking Bluetooth and Wifi Scanning
Using AGPS apps to clear and update GPS, followed by letting the apps scan for 10 - 15 minutes while the phone is screen-on and outdoors.
Going into the list of apps and Enabling a previously Disabled "Device Policy" app
Reading /system/vendor/etc/gps.conf (but I don't know what it means)
Flashing to the latest Pixel sailfish images (June 2018 bootloader, boot, radio, system, etc.) and thus removing Magisk
Uninstalled Android Auto
Removing my SIM card, restarting the phone, and then re-inserting it.
The GPS apps I've tried (GPS Status and GPS Test) both show that they can see satellites (18 to 23 at any given moment) but that they can't get a fix. If I'm outdoors, sometimes 1 satellite can be fixed for a minute or two and that's it. The only repair attempt that had any effect was enabling "Device Policy", after which GPS worked perfectly for about 20 minutes before returning to poor operation again.
The issues only seemed to appear after I upgraded to 8.1, which may be coincidence and me just perceiving the timing poorly.
Apart from a Factory Reset which I'm nearly ready to do, is there any other thing I can do, try, or test to get GPS working? I'm not sure how to debug from adb shell properly but I do have access to use adb and get more information if required... or should I accept that my hardware is damaged and that it may be time to upgrade phones? (I'm definitely out of warranty at this point though...)
I have had to return 2 pixel devices with a GPS issue. So it's probably the device.
I would have reset first, then if that didn't work roll back to 8.0. then start trying all that other stuff.
Probably screwed
ohioDroid said:
I have a Verizon unlocked Pixel with Magisk 16.4 installed. I have seen a few other threads from maybe a year ago about this same problem, they all seem to suggest the issue is hardware. I want to check to make sure I haven't missed any software check first.
For about a half year now my Pixel has had trouble locking on GPS. Fitness apps like Strava or Endomondo are super inaccurate or report no distance traveled. Google Maps will work, but only in areas heavy with WiFi. I've mostly ignored it, but in the past week I was out of town and could have really used Maps Navigation, so now I'm trying to figure out if there's anything I can do.
I have tried (combined with numerous reboots):
Confirming "High Accuracy" being selected, and also tried "Device Only"
Tweaking Bluetooth and Wifi Scanning
Using AGPS apps to clear and update GPS, followed by letting the apps scan for 10 - 15 minutes while the phone is screen-on and outdoors.
Going into the list of apps and Enabling a previously Disabled "Device Policy" app
Reading /system/vendor/etc/gps.conf (but I don't know what it means)
Flashing to the latest Pixel sailfish images (June 2018 bootloader, boot, radio, system, etc.) and thus removing Magisk
Uninstalled Android Auto
Removing my SIM card, restarting the phone, and then re-inserting it.
The GPS apps I've tried (GPS Status and GPS Test) both show that they can see satellites (18 to 23 at any given moment) but that they can't get a fix. If I'm outdoors, sometimes 1 satellite can be fixed for a minute or two and that's it. The only repair attempt that had any effect was enabling "Device Policy", after which GPS worked perfectly for about 20 minutes before returning to poor operation again.
The issues only seemed to appear after I upgraded to 8.1, which may be coincidence and me just perceiving the timing poorly.
Apart from a Factory Reset which I'm nearly ready to do, is there any other thing I can do, try, or test to get GPS working? I'm not sure how to debug from adb shell properly but I do have access to use adb and get more information if required... or should I accept that my hardware is damaged and that it may be time to upgrade phones? (I'm definitely out of warranty at this point though...)
Click to expand...
Click to collapse
As much as I hate to say it you are probably screwed. My GPS worked when I very first got my Pixel but the day it updated to Marshmallow I started having the same issues as you. If I stand still it can get a lock but it can't keep up while I move. I've tried troubleshooting with Verizon, with Google, and a whole bunch myself. I've installed new ROMS, old ROMS anything I can find. I think they tweaked something after the 8.0 update that alters how the GPS chips function, and certain units are basically borked from it. They won't fix it now that my phone is out of warranty, I ended up buying a Garmin unit for my car out of frustration.