[fix]GPS_FIX (last updated 10.02.2017)

MeThisGuy

Member
Jul 2, 2014
7
4
0
unbelievable

Holy carp, the GPS_FIX1-cm13.zip attached in the first post of this thread solved my two week long search for the mystery that was seemingly randomly soft-rebooting my phone.
But you see... tis a good 'ol LG L70 MS323 (w5) that came out more than 3 yrs ago. Still going strong and thks to Vasy i've been running the lineageOS 15 (Oreo) - unofficial.

I had finally narrowed it down to it occuring while accessing the GPS or thereabouts but since this phone has been through the wringer i figured it might be a bad sensor by now. Too many Gs on the GPS sensor or whatnot, and it also has a nice glass fractal screen which has never once affected the still silky touch capabillities (presumable enhanced by Oreos quicker pace altogether).

Anyway, came across this thread, copied the file over in a root enabled explorer after backing up the old one, and haven't looked back since.
$30 phone, android 8, twice the battery life as 7, and a quarter of the boot time. Some of the notification features take a bit of getting used to (or rid of) but overall i like it a lot, and even better now that iT fixed :cool:

thankS again XDA community for all hat you do!
 

viachy

Member
Nov 29, 2012
17
2
23
Can I flash this fix on the latest ViperOS Coral 20171122? I experience random reboots, mostly when I use gps on my redmi 3s and cannoot find fix anywhere. I have been on RR rom but now switched to Viper OS, random reboots continue...
 

MeThisGuy

Member
Jul 2, 2014
7
4
0
Can I flash this fix on the latest ViperOS Coral 20171122? I experience random reboots, mostly when I use gps on my redmi 3s and cannoot find fix anywhere. I have been on RR rom but now switched to Viper OS, random reboots continue...
after backing up or renaming the original file I don't see what you have to lose.

The last active post on this thread was from Feb; the folder structure inside the 'GPS_FIX1-cm13.zip' (1st post in this thread) will show where to extract or copy the file to on you Android, but funny enough the original is in a 'lib64' folder, while mine isn't 64 so i just stuck it in the /system/lib folder (with root priveledges, after renaming/backing up the original file.) Haven't looked back since.
It truly has been a blessing, and why it's been known about since feb and not patched is frustrating but that's why the "unofficial" tag on my lineageOS build (no complaining!). My understanding is that Giggle itself patched it between 8 and 8.1 and I never previously had any problems on 7 (L-OS 14). Fresh wiped install by the book too. But it's probably hardware specific. And another reason maybe why is that for me personally it was a ***** to pinpoint because I had logcat records up the ass or 'to boot' so to speak and I saw process codenames and PIDs that would change upon the soft reboots. And I was not looking forward to starting fresh nor painstakingly eliminating every one of the apps on my system and waiting 2 days to see if it would happen again at random.
On a seperate issue I just noticed my system partition has about 300 MB sitting empty thx to the lean size of LineageOS and pico Oreo openGapps. Yet even with SDext2 (hardly use itanymore) and adoptable storage in limited use (ancient microSD bus speeds) my /data partition is almost always maxed. Guess you can't expect too much with 4GB total onboard, and about 1.5 free stock user. But read today that fresh OS install doesn't usually resize partitions so therefor the gap, or 300mb empty canyon in my case. Supposedly possible to resize /system and /data internal partitions accordingly without data loss using the 'resize2fs' function in TWRP recovery. Onto the next challenge, although this last one really was more of a ****ing annoyance, i'm sure you know what I mean lol, oh hello semi-bootscreen sans liveboot... again!.. that kind of thing
Hope it works for ye, cheers!



 

Noru29

Senior Member
Jul 13, 2017
155
48
38
can I use this fix on AEX v4.6 unofficial based on OS 7?
thx
A 3 years old solution.... There are easiest ways to fix GPS on Land.
  1. Be sure to have the last stable Global firmware installed. And you can installed it again to be sure it wasn't corrupted by many ROM's changes.
  2. Download some compass app on Google Play Store (for exemple Compass Steel 3D) and GPS Locker.
  3. In Magisk Manager Downloads section, install "Global Optimized GPS File Replacer" version 6 and reboot.
  4. After rebooted your device, make sure your location settings is setup on mode "Device only".
  5. Go outdoor and then calibrate the compass (activate "real cap" and "Pitch & Roll" in advanced options).
  6. Launch GPS Locker app and wait for the first time fix/lock. This is necessary and essential because the app will recognize some GPS satellites signals for the very first time.
  7. All your hardware is calibrate and you can use GPS Locker in futur to automatically launch your favorite GPS app when it catch signal.

For me, the first time, GPS Locker took 30sc to catch the GPS signal... then it took between 1 and 3 sc since.