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
Related
Sometimes my internet will not connect unless I quick reboot and even then there is no guarantee it will and other times it connects fine. I don't think its a signal issue, it just seems to be quite tempremental. Is this a common issue or is just one of those things. I'm using a HD version of Froyo and wondered if there was an app or widget to force the internet on and off. Any help would be great. Thanks.
Sent from the future
I personally have found that with custom roms some arn't "made" properly and so things like this happen. Happened to me plenty of times. I guess you can update you radio to 5.14.05.17 if you haven't.
GoogleJelly said:
I personally have found that with custom roms some arn't "made" properly and so things like this happen. Happened to me plenty of times. I guess you can update you radio to 5.14.05.17 if you haven't.
Click to expand...
Click to collapse
Cool, I will check that out thanks.
Sent from the future
Similar issue with VillainROM 0.9
I have a similar issue after I used WiFi.
After reboot the Mobile Data Connection works properly. But if I activated WiFi in the meantime, it will not switch back to MobileData after stopping WiFi.
The only method to get Mobile Data working again is to reboot or switch to flight mode and back.
As well the Mobile Data's ToggleButton in the status bar and the option in the settings sometimes show the exact opposite.
Anyone to confirm this issue?
im would update the kernel and the radio, newest kernel should be no problem but im would not install the newest radio because a couple of people had some problems with the newest version.
Thanks to all for helpful replies, will have a bash with a different radio and rui.
Sent from the future
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
some people say drop data problem on Galaxy Nexus, it is related to radio/baseband issue, a lot of people recommend the following components
Radio/Baseband:
cwm-radio-i9250-xxla2 (latest radio from Google)
Kernel:
franco.Kernel-r158 (best kernel on market)
ROM:
aokp_maguro_build-35 (latest aokp rom)
Just go back to 4.0.2
Sent from my Galaxy Nexus using XDA
I have the above combination and it's worse. The radios in my device are going nuts.
How can it be so bad?
I'm like going crazy!!!
Its the worst phone ever !!!!!!!!!!
Sent from my Galaxy Nexus using XDA
Was at the Verizon store today and there floor model had no drop issues. Tried mine right next to it and it started to randomly drop. They are sending me a new one and are saying it will be here tomorrow hopefully I don't have the issue after the new one. The tech has a nexus and said he has no issues with his.
Sent from my Galaxy Nexus using Tapatalk 2
i had the same problem, it would drop data even though it showed i had strong signal until i set the min cpu to 700mhz. after i did that i never had any data drop problems
hope that helps
Came here to ask about this. Was wondering why it keeps happening. Was working fine when I was on stock 4.0.4 but since flashing aokp it happens all the time.
Sent from my Galaxy Nexus using XDA
I had these issues with aokp and Franco kernel m3. Switched to revolution hd and James Bond kernel. Haven't had a single drop since.
Skickat från min Galaxy Nexus via Tapatalk 2
I'm completely stock IMM76I, rooted and I sometimes get data drops.. this happens more frequently when I haven't rebooted my phone for several days. Sometimes the signal letter (H) disappears completely until I turn airplane mode on/off. Other times I see H but there is no data, only a reboot fixes it.
I'm using Tasker to auto-reboot the phone every day at 5AM, but this is gettig really annoying. I wasn't having any issues prior to that IMM76I OTA.
edwin124 said:
i had the same problem, it would drop data even though it showed i had strong signal until i set the min cpu to 700mhz. after i did that i never had any data drop problems
hope that helps
Click to expand...
Click to collapse
Noticed this was happening only when I was commuting on the highway, my phone loses data connectivity (albeit still showing 'H') and never gets it back until I reboot.
I'll try the set 700MHZ method and report back. But will increasing the min CPU from 350 to 700 hurt battery life a lot?
gabster21 said:
I'm completely stock IMM76I, rooted and I sometimes get data drops.. this happens more frequently when I haven't rebooted my phone for several days. Sometimes the signal letter (H) disappears completely until I turn airplane mode on/off. Other times I see H but there is no data, only a reboot fixes it.
I'm using Tasker to auto-reboot the phone every day at 5AM, but this is gettig really annoying. I wasn't having any issues prior to that IMM76I OTA.
Click to expand...
Click to collapse
I get this a lot, it's really annoying.
I'm really hopping they fix this in the next update, it totally ruins the experience of using the phone. You don't know what you'll get half the time.
gabster21 said:
Noticed this was happening only when I was commuting on the highway, my phone loses data connectivity (albeit still showing 'H') and never gets it back until I reboot.
I'll try the set 700MHZ method and report back. But will increasing the min CPU from 350 to 700 hurt battery life a lot?
Click to expand...
Click to collapse
Based on my exp, you don't lose much battery life. I accidentally left the CPU at minimum 691 MHz and got similar battery life with 307 MHz as my minimum.
Sent from my Galaxy Nexus using Tapatalk 2
If you don't have PRIMELA03* bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
blowtorch said:
If you don't have PRIMEKL03 bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
Click to expand...
Click to collapse
I just noticed I'm on the 4.0.1 bootloader. I'll flash the 4.0.4 one when I get home to see if I can finally get rid of this issue.
I tried flashing radios and RILs and it really hasn't helped...
I had similar issues though mine were mostly when leaving a wifi area my phone would not grab my cell data until I toggled airplane mode on then back off. Later I found out about GetRIL and discovered that most ROMs (due to being based on 4.0.4) have the XXLA02 RIL (Radio Interface Layer) while I was running the UGLC1 radio. GetRIL checks for you and allows you to flash the proper RIL (if rooted with busybox). I flashed the matching UGLC1 RIL and havent had a drop since
blowtorch said:
If you don't have PRIMEKL03 bootloader and I9250XXLA02 radio on ICS 4.0.4 you are going to have these issues. Google even said so!!! ref. http://source.android.com/source/building-devices.html dont blame google or samsung this phone is rock solid when used properly
fyi AOKP is notoriously buggy, every release is
Click to expand...
Click to collapse
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
andQlimax said:
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
Click to expand...
Click to collapse
As per my previous post I didnt change my Radio but rather matched my Radio to my RIL (Radio Interface Layer). My phone hasnt dropped data in the longest time since I've owned it and shows no signs of ever dropping it (unless of course I lose signal ).
WoodroweBones said:
As per my previous post I didnt change my Radio but rather matched my Radio to my RIL (Radio Interface Layer). My phone hasnt dropped data in the longest time since I've owned it and shows no signs of ever dropping it (unless of course I lose signal ).
Click to expand...
Click to collapse
Ya..wait for it
Inviato dal mio Galaxy Nexus con Tapatalk 2
andQlimax said:
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
Click to expand...
Click to collapse
This question has been asked way too many times. I say the same response because it helps people solve this problem. The bootloader and radio configuration needs to be correct at least as a starting point and first step in trouble shooting. you assume everyone has the correct bootloader and radio, now that is just presumptuous. I'm so happy that you know "everything" about radios bootloaders and apns that is righteous! your post was very helpful, a great help thanks so much.
andQlimax said:
u say always the same response to everywhere...but its wrong (PRIMEKL03 doesn't exists..did u noticed?)
the suggested bootloader is the PRIMELA03..that page have just a typo (i asked to jbq and he confirmed the typo, he will update in future that page)
and EVERYONE have the correct PRIMELA03 bootloader
the signal issue is related to some bugs in the 4.0.4 roms
it happens randomly for some people in some network conditions..is like the phone is not able to get the data network...no way to solve this until a next update from google
the people that said "i solved by changing radio/rom/etc", just didnt test long enough to get the same problem again
if u (and of course lot of other people) don't have any network problem, then u are lucky living in a place where the network and ur operator are perfect...end of story
i'm not pessimistic, this phone is perfect, but will be really perfect when they will fix this...i had other android phones before this, and none had this problems...i know everything about radios, apn, networks..but there is nothing i can do to make it working fine ALWAYS..sometimes the mobile network works, sometime there is no way, even after a reboot, only moving temporarly to a different area solve the problem sometimes, even if signal was full bar
Click to expand...
Click to collapse
This is actually not true. I was on 4.0.4 but had the 4.0.1 bootloader somehow.
I haven't had a single data drop since flashing the new bootloader with XXLA02. The real test will be tomorrow, when I take my phone into work (big metal building). If I get no data drops at all tomorrow, problem fixed.
Hey There,
I've just installed this fine ROM today, and it seems great,
but for some reason, the wifi reception is BAD now.
It works fine if I seat near my router, but if I move 3 meters away
it looses the connection ... and says the reception is POOR.
Any1 else has this problem?
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Thanks for the quick replay
I flashed the "[08-09] [ROM] CyanogenMod 10 - Endeavor Unleashed" rom.
I don't think this is the same cm10 everyone's using.
and I don't really understand, doesn't the Kernal comes with the rom?
Can I change it without changing a rom ?
alexx_za said:
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
I notice the same problem a few days ago (I think is since I have install CM10). I have switched on OrDrost since 2 days, I tried the Faux kernel and finally I just revert to full stock rom and my wifi signal haven't change :/
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Thesalan said:
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Click to expand...
Click to collapse
But on the stock rom WIFI was ok.
Update: Ok I did the "Squeeze" test. Wifi is great whn I squeeze
So it is a hardware problem?? How it only started after I put CM10?
Have you reinstalled the stock rom since you have the problem?
I don't know if CM10 is the cause, or it's a coincidence..
there's an UNOFFICIAL release at the moment which may fix some issues, though I've not noticed anything and I've had every release since A10 installed, so it could be a hardware issue.
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Thesalan said:
Have you reinstalled the stock rom since you have the problem?
Click to expand...
Click to collapse
Not yet, I really hate the stock rom.
tgcp, Where can I get this rom?
(Although it really seems like an hardware problem,
I heard the latest stock update helps a little so there
might be a software solution)
Rodbouy said:
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But if you use Cm10 without that little earphone cable, the wifi won't work good?
BTW, what does htc support ask to fix the problem? Do they care you rooted and unlocked the device?
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
but it is noticeable!
I can't move more then 2 meters from my router or it disconnects.
Does your wifi issue not that bad? (without the cable's help)
With out my fix the signal is a joke. 1 bar when 3 feet away. Wasnt usable.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Problem is I can't get back to stock! from what I understand the Stock RUU for my phone wasn't released ...
Do you think HTC will be "understanding" and fix the wifi issue even with a custom rom?
(they'll know anyway that I opened bootloader)
Try flash the Rom with the stock kernel, that will surely solve the WiFi problem.
Sent from my HTC Desire C using xda premium
Did you not do a backup before installing custom rom. Im positive that even if you relock the bootloader they can see that if they went in to recovery. But unlikely. So if you flash stock rom and re lock bootloader, remove root you should be fine
Sent from my HTC One X using xda app-developers app
Hi, try using tbaldens CM10. It can be found under HTC ONE X ORIGINAL ANDROID DEVELOPMENT. I found this to be the best CM10
I have been chasing this problem ever since installing CM10 on my Evo 4g LTE. I was getting 4 times the wifi distance on the stock rom. I go about 30 ft. outside the office and wifi drops. Also, what is the most annoying... I stream over our LAN, and when the screen is off, it turns wifi off after a few minutes. (and yes, the check box is checked to keep wifi alive). I've also tried all of the wifi fix apps and none work. If I leave the screen on and stream........ it is good anywhere from 1/2 hour to an hour, then it will just stop. This kills my battery of course. The problem 1st occured when I first bought my OEM 4g lte, but there was an option in the advanced menu "best wifi performance", after checking that, it worked great, then I switched to CM10 and I now have the wifi issue, and there is no option for "best wifi performance". I've tried a couple other jellybean roms and they have the issue as well. This is driving me nuts. I hope someone finds a solution. I don't think the average person would find this as a problem, but when I stream over the net and move all about the shop, it is unacceptable.
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
rectorfury said:
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
Click to expand...
Click to collapse
I've tried changing my Region Code, but for some reason it keeps defaulting back to Europe... Any ideas? I've tried changing it numerous times, same result.
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.