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
I recently installed GingerVillian on my G2 but after trying all the reboots. and other solutions i've read on the forums i still can't get wifi to work. After rebooting once it will let me add my wifi network but it will never connect. It tries to then wifi turns off and back on and does this repeatedly never connecting. I turned off wifi sleep so that isn't the issue neither. How do i fix this? I'd love to have GingerVillian on my G2 but it's just not functioning properly for me. Any resolutions to this issue and i'll try again but for now i'm gonna restore my old OS
was it 1.5?, I think I had it work for me, when I get home I will reflash and post result.
Sent from my HTC Vision using XDA Premium App
try rebooting it
I would agree, try rebooting. Just loaded 1.5 on my G2 and the wifi works here at home.
I got exactly the same problem after installing ad free, and titanium backup..
Don't know if any of those apss could result in such behavior.
Tried Fix Premissins through Rom Manager with no luck.
Tried also to uninnstall those programs, still no luck.
It seems like the phone dissconnects the wifi after a short while.
i have to re-enable it, but still no luck.
Enabling Wifi-tethering works though. the AP appears on other devices, an connects. Also enabling traffic passing through my 3g connection.
egotr1p said:
I got exactly the same problem after installing ad free, and titanium backup..
Don't know if any of those apss could result in such behavior.
Tried Fix Premissins through Rom Manager with no luck.
Tried also to uninnstall those programs, still no luck.
It seems like the phone dissconnects the wifi after a short while.
i have to re-enable it, but still no luck.
Enabling Wifi-tethering works though. the AP appears on other devices, an connects. Also enabling traffic passing through my 3g connection.
Click to expand...
Click to collapse
i have the same problem. my wifi isn't working on ANY rom. i read in various forums that some people just had to get replacement phones.
egotr1p said:
I got exactly the same problem after installing ad free, and titanium backup..
Don't know if any of those apss could result in such behavior.
Tried Fix Premissins through Rom Manager with no luck.
Tried also to uninnstall those programs, still no luck.
It seems like the phone dissconnects the wifi after a short while.
i have to re-enable it, but still no luck.
Enabling Wifi-tethering works though. the AP appears on other devices, an connects. Also enabling traffic passing through my 3g connection.
Click to expand...
Click to collapse
FYI, i called t-mobile and are sending a free replacement. now i just have to figure out how to revert to stock os
Flashed with CynogenMOD.
Works perfect untill i enable WIFI, then it boot cycles.
Rolled back to GingerVillian, Same problem as before.
Flashed my radio, and now it works perfect again.
Seems like a glitch in the radio image or something?
solution: newest Radio?
So which radio would you suggest?? I am having a problem with my wifi running the radio ending in 26, which I believe is from T-mobile.
I am not sure witch Radio you should pick,
I found mine under Phone specific tutorials.
My signature shows whitch i am currently using.
Go visit the phone specific forums and search for your newest radio in some of the tutorials.
A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse
Basic question. Still, have you backed up and tried Factory restore?
recently my phone doesn't read the SIM after a few hours of use. Says there's no SIM.
Sent from my HTC One X using Tapatalk 2
agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi
wilku said:
agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi
Click to expand...
Click to collapse
I do not agree. I'm also using 2.17 and everything with GPS and wifi is OK.
Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2
omaboy said:
Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I used only files from the instalation guide. No other modifications
CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)
krivas said:
A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse
Click to expand...
Click to collapse
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2
Hunt3r.j2 said:
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2
Click to expand...
Click to collapse
I did not drop the phone, or did something strange with it. The only thing i want from a device that costs € 500,00 is that everything is does work.
I've have experienced a drop in mobile network signal after the 2.17 update. Haven't tested GPS but WiFi seems alright. I have not dropped the phone nor done anything unusual to it, just updated. Before, I had 5 bars/full signal all the time, and when I checked battery stats the network signal indicator throughout the day was green. Now, after the update the indicator is yellow and I have around 1-3 bars if signal.
Also, I'm in Denmark so I got the 1.29.xxx.12 update which was supposed to optimize signal strength. So right now I hope they are working on a similar fix.
Sent from my HTC One X using xda app-developers app
smidgeox said:
CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)
Click to expand...
Click to collapse
The Custom ROMMERS part worked for me.
I had the same Problem. Just checked after a half hour and it still works.
Just try this method
Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.
I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app
dzdimov said:
I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app
Click to expand...
Click to collapse
To me, your issues sound like radio related issued, although I could be wrong. You both on custom roms? With custom recoveries? I suggest if 1.29 worked better signal wise that you flash that radio in your custom recovery. That might improve your signal. Its basically different for everyone which radios work the best so basically it's trial and error.
Lemme know how you get on :thumbup:
Nightscope said:
Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.
Click to expand...
Click to collapse
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now
duckysempai said:
I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now
Click to expand...
Click to collapse
Hi, have you flashed any different radios? What's your current software version and does your Wifi drop as well? Or is it just mobile data?
After the 2.17 OTA update, the signal is always medium...but now there r no call drops or loss in signal
sandipbarik said:
I got my 2.17 OTA update last night, immedietly after the update my wifi signal was dropping, which was pretty stable 3 bars before that.
Today morning im getting dropped gsm signal...sometimes its showing no signal...eve a manual signal search gets me no network, omly airplane mode on/off gets the signal back.
I m not unlocked and not rooted...just plain factory stock.
should i unlock it and flash the radio from the 1.29 rom ??
Click to expand...
Click to collapse
That's up to you, but many users have experienced that some radios work better for different people. 2.17 works ok for me, maybe you should try.
Sent from my HTC One X
I think i have the same problem, when data On, GPS On he sometimes turn of after i turn in and when put the pin and he try to connect to the carrier turn of again. This only happens now when i flash faux kernel and before with alex-v kernel..
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
I know this has probably been asked many times before but i can not find an acceptable answer. My WiFi will not automatically connect to known WiFi spots i know they are solutions to try like turning wifi optimisation on/off and you can always manually go into wifi and it will connect, but its not right it is not how it should work. I'm wondering if it is linked to hardware as in a certain batch of components not working properly with the software. Anyway is there a permanent proper fix other than flashing back to an early release. Also I have tried many 4.3 roms including stock and they are all the same
Tasker Fix
goatimus said:
I know this has probably been asked many times before but i can not find an acceptable answer. My WiFi will not automatically connect to known WiFi spots i know they are solutions to try like turning wifi optimisation on/off and you can always manually go into wifi and it will connect, but its not right it is not how it should work. I'm wondering if it is linked to hardware as in a certain batch of components not working properly with the software. Anyway is there a permanent proper fix other than flashing back to an early release. Also I have tried many 4.3 roms including stock and they are all the same
Click to expand...
Click to collapse
Had the same issue. Having success with a Tasker rule that turns off wifi for 1 minute when wifi connection is lost and then turns it back on. This seems to reset the wifi so when I return to a known wifi, there is a reconnect. At wost have to wake the device (hit the power button) and then wifi comes alive.
bigknowz said:
Had the same issue. Having success with a Tasker rule that turns off wifi for 1 minute when wifi connection is lost and then turns it back on. This seems to reset the wifi so when I return to a known wifi, there is a reconnect. At wost have to wake the device (hit the power button) and then wifi comes alive.
Click to expand...
Click to collapse
Thanks for help I've decided to go back to 4.2 for now. It really bugs me when something doesn't work as it should and refuse the 'workarounds' as a matter of principle. Does anyone know though if it is a hardware batch kind of problem as it just doesn't seem to make sense that some people have the problem where others do not. I hope 4.4 doesn't have the same issue.
goatimus said:
I know this has probably been asked many times before but i can not find an acceptable answer. My WiFi will not automatically connect to known WiFi spots i know they are solutions to try like turning wifi optimisation on/off and you can always manually go into wifi and it will connect, but its not right it is not how it should work. I'm wondering if it is linked to hardware as in a certain batch of components not working properly with the software. Anyway is there a permanent proper fix other than flashing back to an early release. Also I have tried many 4.3 roms including stock and they are all the same
Click to expand...
Click to collapse
Having the same issue here on my toroplus. I've noticed three different behaviors: automatically connects, connects right after screen turns on (before unlocking), and doesn't connect until I tell it to "Connect". I've read that some people have reported the issue on the Nexus 4, but I don't know if that means anyone is working on fixing it...but being on multiple devices, someone that can fix it ought to notice it, right? I hope so; it's definitely starting to annoy me too!
Its annoyed me to the point I think 4.3 is unusable. I have limited data usage and with my very useless memory I keep using it up as I've forgot to manually connect to WiFi. I've even tryed looking through all the system folders to see if I can edit some setting but I don't really know what I'm looking for.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Recently tried 4.3 again with the same problems as usual. Buuuut after a week of using it the WiFi issue seems to be fixing itself!?!?! More and more often its connecting by itself yet I have not changed a single thing. I am on stock unrooted 4.3. So maybe its just a case of a bit of patience.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
No, I can't confirm that. I've been using 4.3 for at least 2 months and the issue hasn't fixed itself the least.