Develop Bugs

Proper GPS fix

I've seen quite a few "flash back to stock, then flash AOSP" fixes to get your GPS working. All you have to do to really fix the GPS is:
1. Backup your stock ROM's EFS through your recovery. (Do NOT wipe prior to doing this.)
2. Wipe
3. Flash AOSP based ROM.
4. Restored your ROM's EFS through your recovery's advanced restore.
Done.

GPS is my ROM's Bane!
ivanmmj said:
I've seen quite a few "flash back to stock, then flash AOSP" fixes to get your GPS working. All you have to do to really fix the GPS is:
1. Backup your stock ROM's EFS through your recovery. (Do NOT wipe prior to doing this.)
2. Wipe
3. Flash AOSP based ROM.
4. Restored your ROM's EFS through your recovery's advanced restore.
Done.
Click to expand...
Click to collapse
So, I am having a GPS issue that I've been unable to solve through any of the numerous method's posted around XDA (my primary source of all things android) and related sites. It could be a simple solution, but I've exhausted my very limited knowledge and am hoping you have some input or suggestion...
I'm on the LS970 and in an over-caffeinated moment, I fully wiped the stock ROM without a backup. I know that is totally stupid, and have been much more careful with my fingers since then. :silly: I have been unable to get a GPS lock on Spleef's Carbon 4.3 20131020 (or any previous), so tried to factory restore and TWRP flashed a ZV9 ODEX (failed install), ZV7 STOCK (failed install) and SPR-ZVB which flashed successfully but gave me FCs and reboots everytime I opened an app that would get a GPS lock. I have tried the FasterGPS, GPS Status and Toolbox, and edited my GPS.conf. Since I can't get back to factory, I need another way to get to a "factory-enough" for a GPS lock...
Any ideas? I think maybe there's a path/process to follow to be able to go from AOSP to stock that I'm not doing, but I have no idea what it is.
Fingers Crossed!

I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.

etownguy said:
I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.
Click to expand...
Click to collapse
Fabulous! Thank youuuuuu!
EDIT: Is this it? http://forum.xda-developers.com/showthread.php?t=2468979

Got the GPS Lock!! (Carbon4.3)
etownguy said:
I was having the same issue with Bean Stalk then carbon also. using the app GPS essentials it would show 0 satellites in the sky even though GPS was enabled.
I flashed the Optimized ROM in the DEV section and this did bring back the GPS functionality.
just an FYI since your stock ROM is gone.
Click to expand...
Click to collapse
You have SAVED MY WORLD!! HUURAAAAYYYYY!!!!!! :highfive:
The OpTimized ROM was PERFECT in bringing back my GPS, it locked in seconds. It took me a few tries to get it active on Carbon4.3, so I'm going to give my "steps" for successful completion.
I FULL WIPED before flashing OpTimuS_V4.4 (ODEX) - that's Data, System, Dalvik and Cache. (Obvious? I first ran a full TWRP Backup of the system, data, boot)
Then I flashed, booted, and let it go through its process. It took its own "soft reboot" which I thought would turn "Bootloop" but it did NOT... rebooting to the "Semi Stock OpTimuS" perfectly. It did the "Activate" process on its own.
Then - I went to System Updates. PRL first, then Profile. Then the VITAL UPDATES were Google Maps and Play Services.
After this, I rebooted to let it reacquaint, and then installed FasterGPS, using it to clear the current aGPS. Next, installed FreeGee.
Opening the updated Google Maps, I IMMEDIATELY got the lock, but let it sit for 5 minutes. (reset "display time" to 5 minutes to keep track.)
Next - AFTER the GPS locking for 5 minutes, I did a backup of EFS with FreeGee. If you have PREVIOUS BACKUPS on the Internal Storage, they need to be replaced. This can be easily done with ES File Explorer, or any which allow root access. Go to the active (sdcard on LS970) FreeGee, copy the EFS settings, and replace those in the "/0" or Legacy FreeGee folder.
This may be "overkill" but I went back into Google Maps, got a Lock again, let it sit a few minutes and "tested" the navigation function.
While still in Maps, I powered down. Booting into Recovery (I use TWRP), I ran a RESTORE of my TWRP Backup, since the backups aren't "install" compatible. My fear was the "Restore" would override my updates, but when you run it, just "uncheck" EFS in the restore choices and you're :good:.
My LS970 booted up LOVELY, ran its normal boot process, and when I opened Google Maps .... ~*Aaaaaaaahhhhhh~* light from the Heavens! It locked FAST, and the Nav even worked!!
I have been trying to find this Fix for almost TWO MONTHS so I am on Cloud 9 right now!! Thank You @etownguy!!!

GPS locking issue
Hello all,
I am an intermediate novice at flashing, but Ive gained some knowledge over the recent years here and there. Heres the issue, I am running into the same issue as euphoric fuzion except I have exhausted all that I know. I rooted, unlocked bootloader and flashed my ls970 without creating an official Rom backup or backing up my EFS- I know, not bright of me. After using my new roms I realized that MY GPS isnt locking. So, Ive done everything from writing new NPS locations in gps.conf, attempting to go back to stock via LGNPST-Ive used the auto option, Flash tool and they dont seem to recognize my phone via download mode but the drivers are installed-pc recognizes. One flash tool actually recognizes my phone as another model. Ive tried to flash stock based Roms-one ins particular at no suceess-symlink failure. Attempted to flash ZVC stock based Rom with Firmware flash- the phone remains in bootloop from my previous ROM. In order to use the phone I have to reinstall CM11- my fav for now- but I cannot lock my GPS with out SPrints PRL update, or network update for my profile. Any suggestions? Thanks in advance

No gps signal lock T999-V on 4.4.2

Hey everyone, really need some help getting my GPS working again.
Used to be on slimkat but went back to stock, everything was fine. Saw the OTA for 4.4.2 and installed, didnt notice any issues. Was trying to use GPS the other day but couldnt get a lock so heres what I've done so far
-download GPS status and clear then refresh AGPS data, left alone for a bit, nothing.
-In bootloader cleared cache, tried GPS status app again with no luck
-In bootloader did a factory reset, booted up without importing data, tried GPS status app with no luck.
-Checked screws around case, tried GPS status app, no luck.
-Downloade and flashed stock 4.4.2 firmware via odin, no luck.
-Tried alternative GPS fix (http://forum.xda-developers.com/showthread.php?t=2211690) booted up GPS status app and left, managed to see 3 satalittes(my nexus 7 '13 see's 8-12 in same spot) but wasn't able to give a lock
- Tried changing CSC (http://androidforums.com/samsung-galaxy-s4/761247-gps-fix-dummies-guide.html#post6105418 Its for the S4 but well **** I'm willing to try anything) phone was on the wrong one and changed it to the correct GLW code, cleared cache, tried GPS status app, nothing.
I need help, could this be a modem thing? any help would be seriously appreciated
Also mad love to geohot for towelroot

Try GPS test by chartcross. Also how long did you give it? On the Sprint port some had to let it sit and keep trying for over ten minutes. But after getting the initial lock it was much better afterwards.
Since youve been messing with different fixes and files though, you might want to reflash the firmware first.

Is there a phrase for when you unplug the cable and it doesn't fix it but the IT guy tells you too and say you have but you do it anyways and it fixes the problem?
I must've flashed stock 4 times yesterday with no luck then you tell me to do the same thing and it works...... Lol I guess you scared the gremlins away.
I noticed that if I restart my phone I need to use a app to refresh agps data afterwards I have instant lock and see 20+ sats
DocHoliday77 said:
Try GPS test by chartcross. Also how long did you give it? On the Sprint port some had to let it sit and keep trying for over ten minutes. But after getting the initial lock it was much better afterwards.
Since youve been messing with different fixes and files though, you might want to reflash the firmware first.
Click to expand...
Click to collapse

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!

Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.

You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck

Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.

Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.

No sensors/GPS with custom roms

Last weekend I flashed an old HTC One X I had lying around with This Cyanogen
After a while I noticed location services was barely working.
Using androsensor I saw that, apart from sound and battery, none of my sensors were registering anything (waiting for event, or zero), and GPS saw NO satellites at all. (Sony in at the same time saw 21)
Being my first flash, I was thinking user error, everything else was working but hey.
I tried this resurrection remix, exactly the same result
I went back to old storage layout and tried the latest cm-11 snapshot, no difference.
Since I didn't think of testing the gps & co before flashing, I wanted to try to return to stock rom. but that's not as easy as it sounds apparently.
Backups got wiped while I was trying to get my first flash, and online references and links to tools are mostly invalid now.
I tried an original recovery and locking the bootloader, but got an error running the presumably correct RRU.exem, probably due to the 1.7x HBOOT I have.
There might be a hardware issue, I opened the device to check a dicky USB connector, but don't see any damage.
Finally tried This cyanogen again no difference.
So is there anyone left here with some more experience/insight that can help me get the sensors working in custom rom, OR be able to get me back to stock, so I can test them there.
If you need any more details, just ask.

GPS is not working after flashing Lineage 14.1

GPS is not working after flashing Lineage 14.1
I tried (GPS Status) but still says "Looking for GPS location..." and nothing happened.
Also, I wiped cache and dalvik many times.
Device : HTC One M8

Now, I tried "Venom Roms" and the same issue nothing fixed!
Is some file missing when I rooted or Rom?
Any help will be appreciated..

GPS is working now
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

mhb3000 said:
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?

Gara91 said:
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?
Click to expand...
Click to collapse
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.

GeoFisher said:
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.
Click to expand...
Click to collapse
I do have a gps lock now on the lineage os...i just followed the steps from guy above... My mistake was when i install a lineage os i allways do the bootloder unlock, then immediately i flash twrp and than a full phone wipe (system, data, cache, internal memory). This time i relocked the bootloader, installed the ruu, then unlocked the bootloder again, after that i let the stock system to fully boot... I go through the first set up and after all that i flashed the twrp, and installed the lineage os but this time without a system wipe, just data, cache and internal memory (internal memory is not a must, but i love when i install a new rom to get totally fresh and clean install).
I don't have a clue why this works but it worked for me and maybe it can work for you...
My HTC M8 is European model but it doesn't matter, because if you do all this step with the stock ruu (Verizon ruu in your case) the files for the gps will be there... Good luck..
Edit: I am using the Navigon Europe and my gps locks instantly like on the stock android 6.0.

Hello, I've got an almost the same issue with GPS, it seems, the "assisted" function isn't work correctly. When I switch on the GPS, I have to wait 3-5 minutes to start working. After a few minutes there is no any issue with that, but a little bit annoying if I want to navigate from an unknown place and I have to drive "blind" for 5 minutes. I use the latest nightly build on my M8. I've started use the previous unofficial build, but currently I always upgrade to the latest nightly. Any idea?
Thanks in advance!

This fixed the GPS for me.
I'm was on LOS nightly 14.1-20170413 when i removed # in gps.conf. (use total commander app)
When phone start bootloop, i use the right quickpulldown to GPS and only 1 touch to disable. In current nightly, it's 2 touchs to disable GPS so have to be even faster before the bootloop or otherwise tap the airplane mode instead to stop bootloop. Also make sure you have screen lock = off or swipe.
now restore # in gps.conf and GPS is working.
/system/blobs/
This might help.
https://www.reddit.com/r/LineageOS/comments/5z8zju/gps_not_great_on_htc_m8/

Hi,
I recently went into the same issue with GPS on my m8. It was not working at all. I spent couple of days trying to flash different stock roms, RUU, factory reset, editting gps.conf file, even the solution described here: https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999. Nothing helped. No matter what I did, I couldn't get GPS working. I mean there was no signal at all.
Finally I wiped MISC partition and it solved the issue. It turned out that some wrong data was held on misc partition that stopped GPS from functioning correctly. One important notice - I was on stock firmware when I wiped MISC partition. Stock firmware managed to reinitialize it properly. If you are on custom FW, I am not sure it will work. You can try and if it will not work, it mean you should be on stock FW.
And just few commands for those who don't know how to do it:
With fastboot:
Code:
fastboot erase misc
If the above gives you "not allowed" error you can do it through adb:
Code:
su -
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Obviously you should be rooted or you can do the same through TWRP shell.
Hope it will help someone.