Related
If your GPS isn't working with your new ROM, then try this method. It has worked for me for every ROM I've used with a problem connecting to GPS. I've seen the problem posted in several ROM threads, and instead of posting it in each one and having it get lost in the hundreds of pages of posts, I figured I'd start a new one which might be searched for a little more easily.
- Open 'Settings' and go to 'Applications'. Choose 'Manage Applications'.
- Choose 'Running Apps'
- Find the 'Maps' app and open it. Click 'Force Stop' and choose 'Clear Data'.
- Go back to your app drawer and open 'Maps'. It will have you check off the disclaimers. Close it after you have done this.
- Open your 'Navigation' app and check off the disclaimers there. It should connect after that.
Like I said, this has worked for every ROM I've tried with a problem connecting to GPS. I don't know why it works, but it does.
tags: gps not working, gps won't connect, gps issue, broken GPS
Didn't solve my GPS issue...which is that it doesn't toggle on what so ever.
Each new nightly I flash, I have to push an old gps.vision.so in order to get my gps to toggle on and off again.
Thanks anyway.
edit: No app on the market will make my GPS work...That is the type of GPS problem that I and some others are having.
try install the gpxfix or gps status from the market.. work well for me..
Same here...this didnt help.
Also installing GPS status did not help either.
As discussed in the nightlies thread, Cyanogen presumeably updated a crucial library responsible, among other, for GPS functionality which requires the/a new radio.
This also could explain why some users while having identical devices to other users do have GPS while others dont. They simply did upgrade the radio already earlier while the ones which are stuck with a bon-working GPS didnt and are still on the original radio, an "old" one in regards to the prerequisites of the "new" library added to the build.
Makes sense?
schaggo said:
As discussed in the nightlies thread, Cyanogen presumeably updated a crucial library responsible, among other, for GPS functionality which requires the/a new radio.
This also could explain why some users while having identical devices to other users do have GPS while others dont. They simply did upgrade the radio already earlier while the ones which are stuck with a bon-working GPS didnt and are still on the original radio, an "old" one in regards to the prerequisites of the "new" library added to the build.
Makes sense?
Click to expand...
Click to collapse
Yep...this is 100% correct.
And for what its worth, I went a head and flashed the new radio again just too see if in fact it does fix the GPS and yes it does.
Back to the T-Mobile US OTA radio and the gps.vision.so from Nightly #4 or earlier.
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
evilive27 said:
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
Click to expand...
Click to collapse
Did you happen to use the app 'GPS Status' to check your gps after you upgraded? If not, what was the first gps application that you opened after you upgraded to CM7, if you can remember?
Scratch that....just reflashed the radio and nightly 13. Gps works a charm now! Thanks
Sent from my HTC Vision using XDA App
Im on the stock ROM and have a problem. I think the GPS on these phones are messed up big time. Here is my problem.
stock rom with ota update and ota update radio= no GPS AT ALL it will just stick there blinking tryin to get a fixed signal but it wont! Happens in alll my GPS app not just maps.
So I downgraded my radio to the pre-ota one and GPS gets a fix but takes a minute or so.. after that I can leave the app and come back and itll refix itself within 5 seconds (what it should be normally).. So even downgraded I still have slight issues with gps.. plus for some reason if I loose signal for more than 5 mins on this radio it wont ever get a signal unless I reboot.
Im going to try your method but dont think itll work since my problem is not Maps specific.
EDIT: this seems to have worked, even on my the ota radio. I just dont understand why Maps would break GPS for all apps. Funny things is when something like this usually happens I clear app data but didnt do it here because it was all my GPS apps.
I'm glad it has worked for a couple people anyway. I don't know what the problem is that causes this, but it has worked on the ROMs I've flashed, so I figured it might be a good step to take before updating radios and things like that. Just in case the solution is as simple as just stopping Maps and clearing the data... If you have done more modification to your phone beyond just flashing ROMs, then this may not work for you since the problem may be bad radios or other issues. If you are just a ROM flasher without tweaking too much else, then this may solve your problemo.
evilive27 said:
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
Click to expand...
Click to collapse
And I have the old radio, and never had a gps issue. Maybe not all the batches in the factory has the same chip, ic whatever?
Sent from my HTC Vision using Tapatalk
I used to not have GPS issues either - european Desire Z btw - having said that, CM7 #14 breaks with that uuhm... tradtion. It's the first build giving me no GPS unless a new-ish (the 26.04 and 26.06 works) radio is flashed.
So wat is the new radio, I recently flashed a different radio but I'm not sure if its the latest radio out. Thx
Sent from my HTC Vision using XDA App
New to this, can some on explain how to find an old radio and flash it? I am using CM9 build 78.. my GPS hasnt worked for any rom ive used since rooting..
dannynyc said:
New to this, can some on explain how to find an old radio and flash it? I am using CM9 build 78.. my GPS hasnt worked for any rom ive used since rooting..
Click to expand...
Click to collapse
Follow the instructions in this thread. Flash the updater and then the efs wipe tool through recovery.
http://forum.xda-developers.com/showthread.php?t=1632482
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
shadowspires said:
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
Click to expand...
Click to collapse
So you just took apart and reassembled and that got it working?
Maybe
xvanwilderx said:
So you just took apart and reassembled and that got it working?
Click to expand...
Click to collapse
Tried to sell phone on ebay because the wifi adapter was showing issues with range... I bought another and it was clear that the range of the older phone was having issues...
Tried to sell on ebay and buyer couldn't activate... just sent back and I can't get it to accept a flash at all... maybe trying the taking apart trick again...
Crazy
Hello! I know this is a common thread, but i'm desperate!
My GPS is not locking at all, i left the phone for 10 to 20 minutes and i got nothing...
I'm using the CM10.1 MoDaCo ROM, but i tried so many ROMS, fixed configuration files, walkthroughs, etc, but none of them seem to work.
I'll list all the methods that i try so far.
1) Flash a fixed configuration file
2) Change the ROM: i tried with the stock 4.2.2, CM10, CM10.1 Nightlies, CM10.1 Experimental, MoDaCo CM10.1
3) Flash different radios. I live in Chile, so i tried UGLL1 and UGKL1
4) Clear data of Google Services Framework, restart, etc
5) Used FasterGPS to set my location in the right area
6) Used GPS Status to improve AGPS
7) Change the build.prop file
I tried every method and the combination of them, but nothing has worked for me so far....
The GPS is very important for me because i use it to track my rides with Strava, and since the GPS is not working, i cannot start the application...
I really need help...
I use a Galaxy Nexus Maguro without Wallet and live in Chile. I cannot tell exactly when the GPS started to fail, but at least in the stock 4.1.2 it was working perfect, so i guess it started failing when i updated to CM10 and then to CM10.1.....
Ok try this if you haven't.
In settings turn off all location. Reboot
Make sure location reporting is still off.
Clear data on Maps force stop maps
Reboot
Clear data on maps and force stop again
Enable location
Get gps lock with maps or easy gps.
Might not work but I have had your same problem and this fixed it .... good luck
G-Nexus Sent
Hi!
Thanks for your answer, but unfortunately i've already tried this method with no succeed. I tried again but it didn't work...
Thanks anyway, i'm going to try to roll back to stock 4.1 (because the GPS was working with that version)
and if it really works i'm going to upgrade to 4.2 to see if i can find the error...
If someone else can give me a solution i'll appreciate it!
Sent from my Galaxy Nexus using Tapatalk 2
duqueso said:
Hi!
Thanks for your answer, but unfortunately i've already tried this method with no succeed. I tried again but it didn't work...
Thanks anyway, i'm going to try to roll back to stock 4.1 (because the GPS was working with that version)
and if it really works i'm going to upgrade to 4.2 to see if i can find the error...
If someone else can give me a solution i'll appreciate it!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Flash stock, just to make sure it isn't hardware related.
pr0xyw0rm said:
Flash stock, just to make sure it isn't hardware related.
Click to expand...
Click to collapse
I already tried, but with Android 4.2.2 and it didn't work.
Before i flashed the 4.2.2 i was using stock 4.1 without problems, so i believe, and hope, that this is a software issue in the 4.2.2 update...
I'm going to try it now and i let you know.
Sent from my Galaxy Nexus using Tapatalk 2
My GPS got worse after upgrading to 4.2.2. Lock takes much longer and finds less satellites
- wore out your welcome
More info
Well, i returned to Stock Android 4.1.2 using Fastboot, but the GPS didn't work either... So i updated via OTA to 4.2.2 and the GPS didn't worked again...
But i noticed that the Nexus S belonging to my sister, wich uses CyanogenMod 10, is not working either!
So i have a doubt now: Is it possible that CyanogenMod could have ruined our GPSs? If i erased everything via fastboot, is it possible that some remains of CyanogenMod could still be breaking my GPS? Or are our GPSs, strangely, broken at the same time?!
Please Help!!!
GPS
duqueso said:
Well, i returned to Stock Android 4.1.2 using Fastboot, but the GPS didn't work either... So i updated via OTA to 4.2.2 and the GPS didn't worked again...
But i noticed that the Nexus S belonging to my sister, wich uses CyanogenMod 10, is not working either!
So i have a doubt now: Is it possible that CyanogenMod could have ruined our GPSs? If i erased everything via fastboot, is it possible that some remains of CyanogenMod could still be breaking my GPS? Or are our GPSs, strangely, broken at the same time?!
Please Help!!!
Click to expand...
Click to collapse
Did you try changing the file referenced in this discussion? It worked fine for me.
http://forum.xda-developers.com/showthread.php?t=1722983&page=2
If you've flashed the Google factory image, you have an active sim card with data connection, and gps does not work, then you have a hardware problem.
klobkelosh said:
If you've flashed the Google factory image, you have an active sim card with data connection, and gps does not work, then you have a hardware problem.
Click to expand...
Click to collapse
And is there a way to fix it?
duqueso said:
And is there a way to fix it?
Click to expand...
Click to collapse
Out of my realm of expertise, but I imagine the sirf chipset is not user serviceable. Your best bet would be Samsung factory service. I'm sorry.
Well, after giving up on trying to solve my GPS problem, it fixed itself.... i know that sounds weird, but the only thing that i did was update the CM10.1 to the latest RC2 and the problem was fixed, at least partially. Now it can find some satellites and it takes like 100 seconds.
The Gnex GPS isn't the best one, so it behaves a little weird some times, but at least is fixed now...
I really don't know what could be the problem, because i tried with almost any Rom, officials and no-officials...
Finally, the CM10.1 RC2 fixed my problem, hope this could help someone else.
Enable wifi & mobile network location in settings
Should be some code in 4.2.2 that prevents you from getting AGPS data if you disable the said option.
Enable wifi & mobile network location in settings
Should be some code in 4.2.2 that prevents you from getting AGPS data if you disable the said option.
Click to expand...
Click to collapse
The problem is fixed now, but i tried everything, from rolling back to 4.1 official to 4.2.2 official, CM9, CM10, CM10.1, AOKP, etc. So i really don't know what could be the problem. I also tried the solution that you told me, but that didn't work either.
Right now, with CM10.1 RC2 my GPS is working great and i'm able to use Strava again.
I've been having the same issue. I'm running a Stock Verizon Galaxy Nexus, on my third one now. I have tried everything from apps, to resets, to disconnecting the gps, and nothing seems to work. It just seems to take forever to get a GPS lock, sometimes I just have to reset it. Not sure the issue, and I can't seem to find anyone with answers either. IDK if anyone found anything??
wpeen001 said:
I've been having the same issue. I'm running a Stock Verizon Galaxy Nexus, on my third one now. I have tried everything from apps, to resets, to disconnecting the gps, and nothing seems to work. It just seems to take forever to get a GPS lock, sometimes I just have to reset it. Not sure the issue, and I can't seem to find anyone with answers either. IDK if anyone found anything??
Click to expand...
Click to collapse
Cold start gps can take up to 20 minutes outdoors with a clear view of the sky if you don't have current agps data. Thereafter, you should have quick starts for a day or two.
Is your data working properly? Do you have sync settings turned off?
klobkelosh said:
Cold start gps can take up to 20 minutes outdoors with a clear view of the sky if you don't have current agps data. Thereafter, you should have quick starts for a day or two.
Is your data working properly? Do you have sync settings turned off?
Click to expand...
Click to collapse
My data is working just fine, I actually have great 4g where I'm at, and all my sync is turned on. I've never had GPS problems with any of my other phones. I had an EVO 3D, and it worked great, cold starts would take seconds to find GPS.
wpeen001 said:
My data is working just fine, I actually have great 4g where I'm at, and all my sync is turned on. I've never had GPS problems with any of my other phones. I had an EVO 3D, and it worked great, cold starts would take seconds to find GPS.
Click to expand...
Click to collapse
And you have certified that all the gps settings/permissions are turned on? Even in the Google settings app?
Since you are stock, it might be helpful for diagnosis to preform a factory reset.
Edit - I see on another thread that you have already performed a factory reset. Next step would be to flash the factory image and see if that helps.
klobkelosh said:
And you have certified that all the gps settings/permissions are turned on? Even in the Google settings app?
Since you are stock, it might be helpful for diagnosis to preform a factory reset.
Edit - I see on another thread that you have already performed a factory reset. Next step would be to flash the factory image and see if that helps.
Click to expand...
Click to collapse
Thanks, I'll have to look up and see how to do that without root and boot loader unlocked, this is my third Galaxy Nexus from Verizon, they keep replacing it and I keep having the same issue
And yes all setting have been turned on, kind of driving me nuts
I'm sorry for you. it must be very frustrating.
As far as flashing an official factory image, I think you can do it unlocked if you have adb set up. Or use a toolkit, unlock, flash factory, relock (or not, why not keep it unlocked?)
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
Hi all, pretty much at the end of the line trying to fix this.
I bought the phone at the end of November, and immediately rooted it, S-OFF etc. The first ROM I tried was Android Revolution HD, and everything worked fine, except for the GPS. It enables, and using an app like GPS Test says I can see 27 satellites or whatever depending where I am. However, it just won't get a fix and lock on. Using Google Maps, it just says 'waiting for location', but never locks on.
So, I recently tried the ViperRom (android 4.4.4), but same issue.
So, I thought I'd put everything back to stock. I followed this guide: http://forum.xda-developers.com/showthread.php?t=2735235, and all the flags in the bootloader look as they should. Stock ROM also.
Still no luck.
So I tried converting it to a Google Play Edition running Lollipop 5.01, using this thread and the links graffixnyc provided.
Again, everything works, but the same GPS problem.
Does anyone have any suggestions..? I can't think of anything else to do
Thanks for any help!
Following this I've tried some different radio versions to see if it makes a difference, and on some I don't pick up any satellites at all. Something to note is that GPS Test picks up satellites inside as well, which makes me think it's not actually picking anything up...
In no cases can I get a fix
If you tryed all of that... you would think its probably a hardware issue
That is what I'm thinking now, just wondering if anyone had a magic solution I hadn't thought of! Really like the phone otherwise