I recently rooted and flashed a recovery on my M8.
I was experimenting with the Fake GPS Free app, and mock locations. Worked great.
But when I turned it off (developer settings, mock location-->None), Actual GPS doesn't work right.
Turned it off, removed mock location setting, deleted app, re-installed app, made sure it was turned off, deleted again.
'High Accuracy' sorta works. It gives an approx position. But using something like google maps navigation gives the message 'Searching for GPS...' and never finds it.
I tried a couple of apps 'GPS Status' and 'GPS Reset Com' which reset A-GPS, but it hasn't worked.
'Device Only' fails completely.
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Anyone have any ideas of what else I can try?
Restore the nandroid backup you made (you made one right?) before flashing a new ROM or playing with apps from /system
I actually did not make one. I've just been reading up what it is and what I should have done and now I feel a bit silly.
When it said 'backup your phone' I thought it was just the contents (messages, data, media, etc).
Oops!
It's still all a bit new to me..
Anything else I can try?
Backup your data and sdcard content then flash appropriate RUU, if it's not gonna work it's probably an hardware issue.
I have exactly the same problem with my M8. I tried exactly the same steps and still have the GPS issue. I also restored a previously made backup and did a clean flash of CM13... this couldn't solve the problem.
It can't be a hardware issue
UPDATE: I don't know if it would have worked before, but after reflashing I placed my phone on the ground outside, started GPS Status & Toolbox and waited for a GPS signal. after ~1 minute GPS signal was found and it works fine since then. Maybe I was just too impatient before.
jamesb457 said:
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Click to expand...
Click to collapse
Looks like you are new to the modding world. But if you are modding the phone (root, custom ROMs), you should always be prepared to recover from a factory reset (have your data backed up).
And if fact, if you are flashing ROMs without doing a factory reset (within TWRP) you are inviting all sorts of random bugs. In other words, the default wipe in TWRP (data, cache, Dalvik) is always recommended when flashing a new ROM.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.
I have been using CleanRom SE ATT 1.2 on my rooted Galaxy Note 2 for a while now. But something recently happened...
When I unlocked my screen with a swipe there was no sound, only the graphics of the water refraction. I first checked the volume and it was up. So I played some music it worked. I think that there used to be keyboard sounds also... Something just seems missing when I am typing.
So I thought what the heck I will just reflash. I reflashed and wiped everything except the "format data" (only because the TWRP 2.4.1.0 mentioned "most of the time you do not need to do this", Well that didnt work. New fresh rom and no sounds of the water again. So this time I wiped everything: cache, dalvik cache, factory reset, system, internal storage, and format data. All!
Still no sound in those particular areas. I have flashed this rom at least 5 times before this ever happened.Now I flashed 3 times trying different wiping and formatting methods and it is not working. What could have possibly happened?
note: The last thing I was doing was using rom toolbox to disable widgets from loading (so apps have like 20 widgets FN ridiculous!) That is the farthest I have ever gone with messing with system files and delving deep into my phone.
Any suggestions?
Well I found the problem... settings > sounds > locks screen sounds. This should have been a simple fix but I never thought to scroll to the bottom of the sound options to find a lockscreen sound check box.
The reason I never checked is because it was always default on and I have flashed quite a few times and never had to check or uncheck this box. But all of the sudden one day the sound is gone. And I reflash (LOL) and the default is not there.
SO I have a more technical questions. Why would this setting not go back to default even after flashing? Where exactly is this option stored? Google!?
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
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
At first it sounded like sudden death syndrome (a power button failure) but when you said turning off 4G fixed it that is very weird. Have you tried asking in the M.O.A.R thread?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Sprint Evo 4G "OG"
Stock - Cyanogenmod 7 - MIUI - Swagged Out Stock
Hit That "Thanks" Button if I Helped You!
Could be your kernel. Or any kernel tweaks you are using
joebeem said:
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
Click to expand...
Click to collapse
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
prboy1969 said:
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Click to expand...
Click to collapse
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
well, now it happened at home when turning on 4g... damn.
joebeem said:
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
Click to expand...
Click to collapse
joebeem said:
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
Click to expand...
Click to collapse
You did not mention wiping system. If you do not Wipe system, and also Factory Reset then it's really not a Clean install. I would still suggest a FULL Wipe, and Clean install. Then run the Device for a while without adding anything. See how it performs.
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
If you never wipe system you are definitely going to run into problems.
joebeem said:
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
Click to expand...
Click to collapse
You just do it in Recovery before you flash. If you look at my Sig on a PC / Internet Mode there is a link on how to do Full Wipe before flashing a Rom.
TEAM MiK
MikROMs Since 3/13/11