So for the past few weeks (honestly, about 2+ months) I've been having problems locking onto GPS with my Pixel, and when it does lock, it'll be a few miles (30+ miles or 45+ km) from where I actually am. After turning off the GPS about 10+ times, and flipping airplane mode on and off about the same number (sadly, I'm probably undershooting how many times I do this) it'll finally work - half the time.
Is there anything I can do to make the signal lock on properly and consistently? Anything I can flash? Delete?
Here's my setup:
Stock 8.1.
Stock kernel (3.18.70)
Magisk Root + Systemless Xposed
Updating to Pie isn't really an option because of one module I use for Xposed.
Related
Ever since i did the update, the GPS takes several minutes to get a lock. Even if I exit Google Maps after it gets a lock and then re-start GMaps again within seconds, it takes again several minutes to get a lock. As if it is doing cold start every time GMaps gets active.
Before OTA update it would take a second to get a lock after just exiting GMaps and re-starting it. A couple of hours later, and dozen miles away, it was still locking within 10 seconds.
Now everything takes many minutes.
GPS Status is showing strong signal from 4-5 satellites, but GMaps is not locking.
Does anyone else have similar problem?
Are you actually getting a lock from gps status or just 4-5 satellites?
I had a similar problem before the update, first lock took about half an hour in gps status, after that it was quicker but still not great.
Sorry to report the update fixed the issues in my case. It could be due to the old radio being better suited to your geographic location than the new one. Unfortunately its hard to really test this unless you are willing to s-off and test some radio/ril combinations.
Sent from my Cyanogenmod hungry Htc Sensation.
My experience is pretty much the opposite of the OP. I've noticed GPS locks are much faster after the OTA. Using GPS Test they were fast before, typically less 15 sec and nearly always under 30 sec, and after the update closer to 5 sec. However, over time I've seen a good bit of variation day-to-day so I can't say with any certainty that my observation is directly related to the OTA. And based on the reports in this thread it seems likely the OTA didn't fix or break GPS.
I have seen Google Nav take much longer than GPS Test to get a lock. I've also had it completely hang my phone where a battery pull was the only option. This when GPS Test would work fine. So I'm quite certain that Google Nav is buggy. Mostly it works, but sometimes not. If it's taking too long to get a lock I will exit, use GPS Test to get a lock, then go back to Nav and it typically locks quickly.
Regarding GPS Test taking minutes to lock that's most likely due to either not having a data connection or a corrupted ephemeris. If you do have a data connection then use the options to clear and update the AGPS data. The next lock may take 20-30 sec but after that it should be back to normal.
samnada said:
My experience is pretty much the opposite of the OP. I've noticed GPS locks are much faster after the OTA. Using GPS Test they were fast before, typically less 15 sec and nearly always under 30 sec, and after the update closer to 5 sec. However, over time I've seen a good bit of variation day-to-day so I can't say with any certainty that my observation is directly related to the OTA. And based on the reports in this thread it seems likely the OTA didn't fix or break GPS.
.
Click to expand...
Click to collapse
EXACTLY the same as that.. 6+ satellites in less than 10 seconds (usually about 5) and the same is true when using google maps.
same thing here instant lock few seconds
less then 30 sec inside
The thing with the GPS Status is that it is showing many satellites with strong signal (i.e. 11 with green bars) but it is not locking either for minutes.
alexsql said:
The thing with the GPS Status is that it is showing many satellites with strong signal (i.e. 11 with green bars) but it is not locking either for minutes.
Click to expand...
Click to collapse
Are you running stock or a ROM?
I'm on stock and have seen this a couple of times. I've been able to fix it by clearing and reloading the AGPS data. This can be done under Settings in GPS Test (https://market.android.com/details?id=com.chartcross.gpstest&hl=en).
OK, i fixed it.
I am on stock and I've tried reloading AGPS but that did not fix it.
I used GPS Status ->Settings ->GPS&Sensors ->Sensor Filtering
After I changed the filtering from Weak to None the GPS locks within seconds.
The weird thing is that now, if I change the filtering back to Weak or even Strong, it still locks in seconds
alexsql said:
OK, i fixed it.
I am on stock and I've tried reloading AGPS but that did not fix it.
I used GPS Status ->Settings ->GPS&Sensors ->Sensor Filtering
After I changed the filtering from Weak to None the GPS locks within seconds.
The weird thing is that now, if I change the filtering back to Weak or even Strong, it still locks in seconds
Click to expand...
Click to collapse
When you say reloading AGPS didn't fix it, how long did you wait for a lock? It can take longer for the first lock after reloading than normal. From your description it may have been the AGPS reload that actually fixed it, then once it got the first lock it was back to the normal fast locks regardless of the filter setting. Just a guess. I haven't played with the filter setting since far as I can tell it's only available in GPS Status, which I normally don't use.
Regardless, glad it's resolved. Also glad to know about that filter setting for future reference.
I did AGPS reload 2-3 hours ago and it did not work until I did the filter thing.
alexsql said:
I did AGPS reload 2-3 hours ago and it did not work until I did the filter thing.
Click to expand...
Click to collapse
Ok. That does seem odd. Also odd that changing the filter back didn't break it. Hard to diagnose that without knowing a lot more about how it works underneath. Still a useful trick to know about. Thanks.
samnada said:
Ok. That does seem odd. Also odd that changing the filter back didn't break it. Hard to diagnose that without knowing a lot more about how it works underneath. Still a useful trick to know about. Thanks.
Click to expand...
Click to collapse
That filtering is for the sensors for your gyroscope on the device not the GPS. It smoothes out the display in the program so your "bubble" in your compass isn't jittery.
I'm using a Nexus 5, its my first Android device, and so my first time rooting.
I rooted yesterday using the Android SDK, and installed TWRP.
The root worked perfectly, and I have tested it. All I have done since rooting (unlocked boot loader at the same time, so I'm clean on stock), is install a few Play Apps like Twitter, WhatsApp and then BusyBox and dSploit.
I haven't added any customisations or anything, and my battery is now awful!
i.imgur/AkdAKjW.jpg (Can't post links yet)
My screen has been on for 50 minutes...
I have brightness on the lowest setting, have turned off vibrate on touch, turned off Wi-Fi, turned off Location, set to use 3G not 4G, set display to turn off after 15 seconds...
Im sure it can't be anything to do with the root, but I don't really know too much about it. Is there a problem with 4.4.2 and battery life?
What else can I do to improve it?
Ideally I'd like to be able to have a max of 3-4 hours screen time, and the device to last for 14-15 hours.
I was easily getting 14 hours before I rooted/updated, but now my battery life has just screwed up.
Why is the OS using up so much?
7ewis said:
I'm using a Nexus 5, its my first Android device, and so my first time rooting.
I rooted yesterday using the Android SDK, and installed TWRP.
The root worked perfectly, and I have tested it. All I have done since rooting (unlocked boot loader at the same time, so I'm clean on stock), is install a few Play Apps like Twitter, WhatsApp and then BusyBox and dSploit.
I haven't added any customisations or anything, and my battery is now awful!
i.imgur/AkdAKjW.jpg (Can't post links yet)
My screen has been on for 50 minutes...
I have brightness on the lowest setting, have turned off vibrate on touch, turned off Wi-Fi, turned off Location, set to use 3G not 4G, set display to turn off after 15 seconds...
Im sure it can't be anything to do with the root, but I don't really know too much about it. Is there a problem with 4.4.2 and battery life?
What else can I do to improve it?
Ideally I'd like to be able to have a max of 3-4 hours screen time, and the device to last for 14-15 hours.
I was easily getting 14 hours before I rooted/updated, but now my battery life has just screwed up.
Why is the OS using up so much?
Click to expand...
Click to collapse
Is this not the first charge since you first saw the problem? The Android OS bug occurs sometimes. I would reboot and see how it is on the next full cycle.
sreen may be turning in coz some apps might be asking for root access.
I think you try greenify app and hybernate useless apps, m sure this will help you.
Hey gang, quick question.
Just installed CM11 & minimal GAPPS.
Took phone outside with a clear view of the sky for several minutes, I am showing no satellites whatsoever. I confirmed that location mode is set to "high accuracy."
Thoughts?
Thanks!
Strange, try getting GPS status app and use it to download agps data. That might make GPS fix faster.
Sent from my SGH-T959V using XDA Free mobile app
Nice!
Okay, tried it. It would "see" one satellite, briefly two. After about 10 minutes, no lock on either, and no fix (minimum of 3 required for a 2D GPS fix). :dunno:
Worked fine in Gingerbread.
I flashed dj's latest (slimkat) again last night. It took a long time before locking in on some (maybe ten minutes), but, I was inside. This morning, I hit it again. 10 sat lock under two minutes (inside again). Connect to wifi with no SIM card. Afaik, you do need some form of data at first.
Interesting. So part of this was user-error. I did not realize that the "GPS Status" app's default behavior is to turn off GPS when the screen is off. So when I was testing yesterday of course I turned the screen off!
Anyway, fixed that. After 10 minutes I had 6-7 satellites for several minutes but no lock. :dunno:
Greets lads,
For "TL/DR"s: Not gaining any battery improvements with root/xposed capable tools (Greenify/Amplify); losing important features like on-time notifications; need help on Greenify settings or alternatives for them.
I am facing an issue, in fact, i always did, when trying to follow battery tips people go for when they root their phones.
I've just recently rooted my Note 8 (Exynos), nevertheless, i always go for a self-controlled system on my phone rather than very modified Custom ROMs, either i modify my stock rom, or find a minimally touched one in the custom rom threads.
Usually, if i achieved massive battery improvements, i ended up with a lot of sacrifices. In previous phones (Note 3, Galaxy A3 2014, HTC M8), i managed to get twice the screen time and battery life when i set-up the usual procedures to , which are: De-bloat (what i dont need and is safe to get rid off), Xposed because of Greenify and Amplify (PowerNap too).
The issues that i would get at these times were delayed notifications i.e from messaging apps, delayed waking up from sleeps (my sleeping, not phone ones) cause the alarm would never make it on time. Now all these apps were white-listed from all the apps that are supposed to limit them.
Now with Samsung Oreo, things look way to weird. My alarm app (Timely) works flawlessly and wakes me up as supposed to, it's untouched by the Samsung Device Maintenance, it is not on the Greenify list, and on Amplify it's not even taken in to consideration as i use the only two features that it allows you in the non-donated version, to limit the wake-ups of Play Services.
However, many messaging apps (obviously white-listed), turned very strange. Many times im in front of my computer, talking on the same platforms already existent on my phone, and 20 minutes later, i open my phone, and i am bombarded by all the incoming communication that i already witnessed on the desktop. This doesnt make any sense.
First, i have already acknowledged them, i was texted on them, i replied, on the desktop. The fact that they show up on my phone means they probably make it in time on my phone, but my phone decides not to wake up. Sometimes it does this without opening the phone up, maybe after 20 to 30 minutes after.
My set-up is: Samsung Galaxy Note 8 (Exynos, SM-N950F), TWRP, rooted with Magisk v16.6, Xposed (Modules: Amplify, Greenify, MinMinGuard), Greenify is Donated version, Amplify is not (would love to, but impossible in my region due to racist google), and root permissive apps such as AdGuard (which is terrible), FX File Explorer (for obvious reasons), Trimmer fstab (not sure if i actually need it), Termux for root shell.
My questions is, WTH am i doing wrong.
BetterBatteryStats shows the usual output on root too, nothing major draining it, but no whatsoever gains of battery life compared to the unrooted past, i mean, 2h screen time with 24h battery life, pathetic, that was the default on my previous 4/5 year old phones, and when i set-up the usual rooted procedures, i would get 4/5h screen time in 48h of battery life.
Any tips on Greenify settings? Any tips for alternative/substitution apps for the ones i already use? (WakeBlock i.e never worked or made my phones unbootable)
Thanks in advance.
Totally feel you and I'm searching for an answer to this, too. I had Greenify installed via the discontinued Magisk module and Xposed, and it started getting REALLY wonky, freezing up and ****. After reading that a lot of people here don't think it's even necessary beginning with Oreo, I uninstalled it and now the lag on my OP3 is pretty horrible, even after freezing the bulk of my apps with TB.
I too would appreciate any advice that can be given... have a OP3 on OxygenOS Oreo 8.0, rooted with Magisk, have Xposed, have debloated everything I have found safe, and using Nova Launcher.
I write this after trying different things for months without success. When I bought the oneplus 6 almost a year ago I got 7-8 hours of screen with 16-20 hours of use. From one month to the next the battery has dropped to 5-6 hours of screen with 10-12 hours of use. The applications that I use and the use of the smartphone is the same. I have tried:
-Reinstall rom with clean installation (several times)
-Use programs to block wakelocks (servicely and grenify)
-Install custom kernel (franco and ex)
-use Doze all the time.
I suspect it's been happening since some oneplus update, but I have not seen anyone talking about this in the forum. I'm currently with 9.0.5 with XXX ROM and some modules with magisk.
Any help or advice? Thanks
sakun-ice said:
I write this after trying different things for months without success. When I bought the oneplus 6 almost a year ago I got 7-8 hours of screen with 16-20 hours of use. From one month to the next the battery has dropped to 5-6 hours of screen with 10-12 hours of use. The applications that I use and the use of the smartphone is the same. I have tried:
-Reinstall rom with clean installation (several times)
-Use programs to block wakelocks (servicely and grenify)
-Install custom kernel (franco and ex)
-use Doze all the time.
I suspect it's been happening since some oneplus update, but I have not seen anyone talking about this in the forum. I'm currently with 9.0.5 with XXX ROM and some modules with magisk.
Any help or advice? Thanks
Click to expand...
Click to collapse
Similiar setup, and no battery drain issues.
First - Try testing also after a clean flash and see if your battery drains (without installing too many apps)
Second - You should try to monitor your battery and applications to find the culprit.
Are you restoring app data after fresh flashes?
It's either software or hardware - so only thing you can really do is check to see what software is causing it.