Greetings,well i think its a common issue for Hero but until now i was unable to find a solution to any other threads in this forum for my occasion.So here is my story: After i updated my radio i lost GPS signal.After that i tried reinstalling Radio,Installing other versions of radio,instaling other versions of custom android even bringing back a nandroid backup of my original ROM,but none of these helped me.Also i tried turning GPS on and rebooting,reinstalling radio with GPS turned on.
Anyone can give me a hand?
Bump.Still having the issue.Currently on Villain ROM 10.
And you do a full wipe every time before switching to a new ROM?
ddotpatel said:
And you do a full wipe every time before switching to a new ROM?
Click to expand...
Click to collapse
Well yes almost every time.I am not performing full wipe when the developer says it is optional.
yeah, optional means do it if you have problems...
update radio to latest, full wipe, reflash rom. then get gps test from market, activate gps and go outside, wait for at least 3 minutes and you should see at least one satellite. it can take up to 20 minutes for a fix the first time, that is how gps works. on the hero usually faster thanks to agps.
Thanks for the answer.I downloaded GPS test from market,but i am unable to understand how this app might fix my GPS.Does it run a test or something?All i can see is just some info about where sun is etc.At the moment i have my phone by the window with the app turned on.I will just wait like that to see if it will find any sattelite.
By the way,yesterday i installed a new ROM and i did a full wipe before (all but Dalvik Cache).Do i still need to reinstall ROM and Radio?
Thanks again Kendong.
TheoKondak said:
...yesterday i installed a new ROM and i did a full wipe before (all but Dalvik Cache).Do i still need to reinstall ROM and Radio?...
Click to expand...
Click to collapse
Why not the DalVik Cache? I assume a full wipe means to wipe the lot?
ddotpatel said:
Why not the DalVik Cache? I assume a full wipe means to wipe the lot?
Click to expand...
Click to collapse
Today i followed step by step kendong2 advice and seems it kinda works.I got signal from some satellites by using Google Maps, and mobile maps 10, but that was just for 1 time.I just checked with Gps Test and getting signal from only one satellite.
I don't remember where exactly (i think it was in this forum) i read that we should not wipe DalVik Cache for some reasons.Well i guess it was inaccurate.I think i need to study what all those do by my shelf.
Related
I have rooted Froyo (Kaos) and the gps functionality is broken. Basically, the screen remains stuck at "searching for gps" and "follow route" on top.
I've had some good luck with an ap called GPS status, available for free via the market. Once launched, open settings>GPS & sensors>Manage A-GPS state, then click reset to clear your GPS cache...I also clicck "download" to pull sat info from the internet. I find that doing this every once in a while helps keep my GPS working snappy.
Also, make sure you have Kaos's most updated version (v34 as of now), and I'm running it with the CFS v4 kernel. I have zero GPS issues having done all of the above.
Hope that helps.
^ ditto
Sent from my FroyoEris using XDA App
Did this.
1. Upgraded to Kaos's v34 (also did factory/format reset, cleared Davik's cache)
2. Installed GPS Sensor, reset status, download option chosen as well.
Same problem
ChadZ said:
Did this.
1. Upgraded to Kaos's v34 (also did factory/format reset, cleared Davik's cache)
2. Installed GPS Sensor, reset status, download option chosen as well.
Same problem
Click to expand...
Click to collapse
have you tried any other roms besides kaos? if you have gps satalllites enabled in settings/location&security and its happening on every rom you try, id take advantage of the warranty...
frosteddroid said:
have you tried any other roms besides kaos? if you have gps satalllites enabled in settings/location&security and its happening on every rom you try, id take advantage of the warranty...
Click to expand...
Click to collapse
+1. It would take like fifteen minutes to pop out your SD card, plug it into your computer, transfer another ROM, reboot to RA, backup your current ROM, clear flash+dalvik, then flash the .zip, and reboot.
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Did you try format system in recovery. Do after you wipe data and cache.Then load ROM.
Good luck it is nice ROM
Sent from my HTC ThunderBolt using XDA App
i am having this same issue regardless of what rom I use. It fc and then it acts like it has lost the 3g signal. I am going mad here with trying to figure out what is causing it to crash when I try calling. It isnt consistent either as some numbers arent crashing. any ideas?
I had issues with mine until I did a full wipe, loaded the radio first (MR2.5) followed by installing LTBv2.3. Make sure the back is on too. I kept wondering why I only had a x1.5 connection for a couple hours, thought I had screwed up installing the radio. Eventually I popped on the backing and it was fine.
A lot of what your experiencing is either a radio issue or a full wipe issue,,, I wipe data, cache, and dalvick cache at least twice and then load whatever radio that the rom suggests and when the rom loads up give it time to normalize, dont rush it. Be careful reformatting anything in cwm it will erase data on your SD card.
nrbowler said:
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Click to expand...
Click to collapse
I just flashed back to Vegan Ginger. My GTab spent most of its life on that ROM. Since I flashed back to it, though, the wi-fi doesn't turn on when I turn on the tablet--I have to manually turn it on each time.
That's not that bad, but I think it's related to my real problem--some apps are telling me they don't have a network connection and to make sure the tablet isn't in airplane mode. The New York Times app always does this now, and it never had an issue before, on any other ROM, including Vegan Ginger. The wi-fi is on and it is definitely connected to the internet. I am sure it must be a setting, I just can't find the one to change. Anyone seen this before?
Thanks in advance.
fre1102 said:
I just flashed back to Vegan Ginger. My GTab spent most of its life on that ROM. Since I flashed back to it, though, the wi-fi doesn't turn on when I turn on the tablet--I have to manually turn it on each time.
That's not that bad, but I think it's related to my real problem--some apps are telling me they don't have a network connection and to make sure the tablet isn't in airplane mode. The New York Times app always does this now, and it never had an issue before, on any other ROM, including Vegan Ginger. The wi-fi is on and it is definitely connected to the internet. I am sure it must be a setting, I just can't find the one to change. Anyone seen this before?
Thanks in advance.
Click to expand...
Click to collapse
Flashed back from what? When you flashed VG did you do a data/factory reset, wipe cache & wipe dalvik cache?
Hm. I probably flashed from CM7.1.0. It's possible that I flashed from stock 3588 immediately after an NV Flash, but I think I went from CM7.1.0 after I couldn't figure out how to activate USB transfer on CM.
Either way, my process to flash a new ROM is:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) Install ROM from SD card
5) Reboot.
What's weird is how VG was different on this install than the previous one. The lock screen was slightly different. Same ROM zip file that's been on the SD card since the first time, though.
fre1102 said:
Hm. I probably flashed from CM7.1.0. It's possible that I flashed from stock 3588 immediately after an NV Flash, but I think I went from CM7.1.0 after I couldn't figure out how to activate USB transfer on CM.
Either way, my process to flash a new ROM is:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) Install ROM from SD card
5) Reboot.
What's weird is how VG was different on this install than the previous one. The lock screen was slightly different. Same ROM zip file that's been on the SD card since the first time, though.
Click to expand...
Click to collapse
The 3 versions (Froyo, Ginger, HC)each have different locks.
I seems to remember either CM7 or one of the kernels not working with USB.
If I were you I would try a Fix permissions & see if that fixes it. If not, redo your process above.
I meant like it was different from VEGAn Ginger when I had it installed the last time on my GTab a week ago. I got it to go back, mostly, it just seems like the preferences were different. Which is why I thought the wi-fi might be a preference issue--the wi-fi box unchecks itself each time the tablet is rebooted.
I'll try fixing the permissions, that sounds promising.
Wait...uh...what's that? (Or how do I do it?)
Thanks.
fre1102 said:
I meant like it was different from VEGAn Ginger when I had it installed the last time on my GTab a week ago. I got it to go back, mostly, it just seems like the preferences were different. Which is why I thought the wi-fi might be a preference issue--the wi-fi box unchecks itself each time the tablet is rebooted.
I'll try fixing the permissions, that sounds promising.
Wait...uh...what's that? (Or how do I do it?)
Thanks.
Click to expand...
Click to collapse
It's in CWM, go to Advanced, Fix Permissions!
aabbondanza said:
It's in CWM, go to Advanced, Fix Permissions!
Click to expand...
Click to collapse
Found it, thanks. Didn't fix it.
Hm. Have re-installed VEGAn GE several times. No improvement.
It's in Brilliant Corners on the 1.2 BL too--you open the NY Times app and it says there's no connection and to check that you're not in airplane mode.
Fixing permissions doesn't seem to do anything. The app worked before on this GTab, and it works fine on my Droid Pro. What the heck?
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.