Develop Bugs

WIFI Problems since MyFroyo RC4

Ever since going from MyFroyo RC4 to RC5 & RC6 (and even the Cyanogen RC01, I have had problems with my wifi.
I am posting here to see if anyone else is experiencing these problems, and to find out what changed between RC4 and RC5.
I have no cell service at my house, so when I flash a new ROM, I need to leave the house and go to an area where I get service before I can connect to the Google Servers to set up my device. When on Wifi, I also have problems downloading Google items in the market (such as Google Search Bar) and can't even use Google.com to search for anything. It times out. I can, however, use other websites and download other items (once I've set up my device remotely).
If I am setting this up over Edge or 3G, there are never any problems.
If I re-flash back to MyFroyo RC4, I can use my wifi with no problem to do everything I need.
I really love the updates since RC4 - but am worried that I'll be left in the dust since all the builds since RC4 have had this issue for me. :-/

I'm in the same boat and experience the same WiFi issues.
Sent from my HTC mytouch slide using XDA App

I've never had a single Wifi issue, although I never really tested on RC1 too much. I'm currently running Eugene's newest CM6, have you tried that one yet?
Sent from my T-Mobile myTouch 3G Slide using XDA App

supposed to be a cyanogenmod issue though i havent experienced it myself (i also have horrible service 1-2 bars edge max) using wifi everything loads up fast and everything downloads just fine! but if i were you i would try the nightlies they are supposed to have fixed the problem by now if im not mistaken

I've experienced a lot of this too. Marker downloads were pretty much not happening for me, no matter what - Wifi or Data. On data, it would download but never install. On Wifi no images in the market would load and no download would activate. I also couldn't use Google.com or sign into Gmail via the browser or other Google services. I did a lot of searching and heard it could be Google.
What I did to fix it... I did some nandroids, I did some wipes and updates and complete formats, etc. What I finally think I had was a problem in my packages.xml file where so many programs were mismatched due to Froyo's ability to use apps2fat32. I think at some point some nandroiding I had done,etc screwed up my package assignments and then I just fresh installed and DO NOT BACK DATA/SETTINGS UP WITH GOOGLE! haha, I honestly think that had a lot to do with it also...Go into your Privacy and turn auto restore off, turn backup data off, then reset your device with a wipe of it all and such, boot up and don't select backup with Google. I've had no more issues really.

TJD319 said:
I've experienced a lot of this too. Marker downloads were pretty much not happening for me, no matter what - Wifi or Data. On data, it would download but never install. On Wifi no images in the market would load and no download would activate. I also couldn't use Google.com or sign into Gmail via the browser or other Google services. I did a lot of searching and heard it could be Google.
What I did to fix it... I did some nandroids, I did some wipes and updates and complete formats, etc. What I finally think I had was a problem in my packages.xml file where so many programs were mismatched due to Froyo's ability to use apps2fat32. I think at some point some nandroiding I had done,etc screwed up my package assignments and then I just fresh installed and DO NOT BACK DATA/SETTINGS UP WITH GOOGLE! haha, I honestly think that had a lot to do with it also...Go into your Privacy and turn auto restore off, turn backup data off, then reset your device with a wipe of it all and such, boot up and don't select backup with Google. I've had no more issues really.
Click to expand...
Click to collapse
I've actually tried the new nightly's and still have the same problems. I've also tried completely wiping it and starting from scratch- and made sure not to back up w/ GOOGLE servers- but to no avail.
I wonder if anyone on here can figure out what changed between MyFroyo RC4 and RC5 that could cause this - seems something is blocking the Google Synch. I've also experienced the problems mentioned above regarding the market items not downloading, no images, etc. Just seems weird that it worked completely fine before RC5, which came out around the same time as the Cyanogen 6 Slide RC1

From my personal experience I'd have to say that wifi is slightly bugged. Drops randomly and occassionally won't detect my network when other Android devices will (any encryption, which is for suckers anyway )

At least I know I'm not the only one w/ this problem. I couldn't find a cyanogen defect for this issue.

Same here. I have no wifi. My g1 connects just fine and my hd2 but on the slide its a no go. Ive tried everything but eventually just gave up. Im using Eugenes Ota update. Im not sure if its just the slide in general but my wifi doesn't work period. It'll connect but if i load up youtube or try the web I get a no connection error. Its very peculiar. Incredibly peculiar.

I am having the same issue. I noticed people talked about it with CM6 rc1 but not everyone was having the issue and the subject died off. Ive tried reloading, wiping everything, htcclay's new version but nothing seems to help. The wifi is just strange will work for a page or two than fail to load or loads half way. Also tried on several different networks. Does anyone know if the driver is the same in eugenes as in these later ones?

After wiping and keeping a good eye on everything, the issue I have with Wifi and the browser is that sometimes it just hangs about 75% page load and doesn't really change unless I leave the phone go for a bit and wait for it to load.
Downloaded Opera Mini (only browser I could find that doesn't use the native browser). With Opera, I've actually hadn't had any loading issues or anything weird like that happen. So many a possible partial-bypass is using another browser? It helped me, just thought I'd share.

acejoker25000 said:
supposed to be a cyanogenmod issue though i havent experienced it myself (i also have horrible service 1-2 bars edge max) using wifi everything loads up fast and everything downloads just fine! but if i were you i would try the nightlies they are supposed to have fixed the problem by now if im not mistaken
Click to expand...
Click to collapse
WesGarner is looking into this problem with...
the wifi issues.. asap he's juggling this and vibrant please be patient i've spoken to wes myself and he's told me when he has the time this will be one thing he looks into

I 2nd this, my friend...
r0man said:
From my personal experience I'd have to say that wifi is slightly bugged. Drops randomly and occassionally won't detect my network when other Android devices will (any encryption, which is for suckers anyway )
Click to expand...
Click to collapse
Same bugginess happening here, too. Iffy, at best. Other than that and of course the non-necessary FN and CAPS light, this is the only issue, anymore, that I can see.

Virus1x said:
WesGarner is looking into this problem with...
the wifi issues.. asap he's juggling this and vibrant please be patient i've spoken to wes myself and he's told me when he has the time this will be one thing he looks into
Click to expand...
Click to collapse
Thanks for the update - I look forward to the day when I can use the wifi AND a camera MyFroyo RC4 is still working well for me, but I miss my camera

Does anyone know if there is any headway in fixing this issue?

DenominatorX said:
Does anyone know if there is any headway in fixing this issue?
Click to expand...
Click to collapse
not to knowledge

Post logcats to Pastebin and/or the issue tracker so Wes has more data on the issue.

r0man said:
Post logcats to Pastebin and/or the issue tracker so Wes has more data on the issue.
Click to expand...
Click to collapse
Unfortunately I'm not familiar with what logcats or pastebin is - If anyone can point me to an issue tracker, I'd be glad to oblige.

HebrewToYou said:
If anyone is having issues with the Android Market over wifi, please post a logcat of the issue along with the relevant details over at the CM6 issue tracker. We're trying to pin down this annoying bug. Here is a link to the issue:
http://code.google.com/p/cyanogenmod/issues/detail?id=2153
Click to expand...
Click to collapse
I believe this is the right place...

donkey72 said:
I believe this is the right place...
Click to expand...
Click to collapse
Thx donkey72!

Google Talk issue - after a few minutes Contacts are all offline when not

I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?

i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.

I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!

carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?

Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium

Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny

dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.

RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.

If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.

RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.

Same problem here.
Although I have not tried it with stock non rooted phone...

I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.

Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)

I updated my software which included an updated gtalk with video..so far so good.

crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.

DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.

Exact same problem with my I9100, Gtalk with video. Very annoying.

I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).

Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?

Are there any news about this issue? I'm having the same problem.

[Q] Issues with [AOSP] Jellybean RC3

I recently flashed the Jellybean RC3 rom and noticed some issues.
Chrome causes my phone to do an automatic restart and I can't find a way around it.
It tends to lag in terms of responding to clicks or movements.
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Does anyone know what could be causing these issues and how to fix them?
Update: I just tried with the Tiny CM10 and it is the same issue.
It worked fine before flashing to these roms. Any idea why that would be?

This is a known bug launching chrome from the dock. Either launch it from your desktop, or another workaround apparently is to put it in a folder in the dock.

I had RC3 for a while, then switch over to CM10. Everything seemed to be a lot more stable, but Chrome also does weird stuff on CM10 as well. Never could get it to work normally on my DINC

romeyjdogg said:
I had RC3 for a while, then switch over to CM10. Everything seemed to be a lot more stable, but Chrome also does weird stuff on CM10 as well. Never could get it to work normally on my DINC
Click to expand...
Click to collapse
I don't like chrome even on the galaxy nexus. Slower and buggy to me. I used to but stock is better.
Sent from my Galaxy Nexus using Tapatalk 2

AntiStache said:
I recently flashed the Jellybean RC3 rom and noticed some issues.
Chrome causes my phone to do an automatic restart and I can't find a way around it.
It tends to lag in terms of responding to clicks or movements.
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Does anyone know what could be causing these issues and how to fix them?
Update: I just tried with the Tiny CM10 and it is the same issue.
It worked fine before flashing to these roms. Any idea why that would be?
Click to expand...
Click to collapse
Chrome wouldn't even start on my Incredible with the RC3 ROM. I would advise using the stock browser until Albinoman works out all the kinks (although the work he's done so far is awesome!). I've also had connection errors before, primarily in the Play Store, retrying a few times seems to work. I always use Wi-Fi and haven't tried cellular data so I can't help you there if you're using 3G to stream.

AntiStache said:
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Click to expand...
Click to collapse
Maybe something to do with your Android ID changing when flashing these newer ROMs? Though that usually shows itself in problems downloading stuff from the Play Store... but you may need to clear data on the Google Music app, also maybe clearing data on the Play Store may help too.
andrewia said:
Chrome wouldn't even start on my Incredible with the RC3 ROM.
Click to expand...
Click to collapse
The main reason I dislike Chrome is because of the space it takes up. It eats up over 30Mb of app data, which on our Dincs is stored in the 150Mb datadata partition. So if you have a reasonable number of apps installed, it's very likely that Chrome will fail to install properly due to there not being enough space to install its data, and it will fail complaining that "your phone lacks functionality critical for running Chrome." In reality, the problem is that Chrome is just too bloated to fit on the limited partitions in our dincs.
(flashing the etx4all nodatalimit mod solves this issue, as does moving all possible apps to the sdcard, but IMHO Chrome is not nearly worth going to all that bother.)

[Q] Anyone having problems with CoPilot and Jellybean?

So I'm an avid fan of CoPilot. I'm able to go from point A to point B without data and using solely GPS. That said, since updating past CM 9, the GPS module has not liked to play nice with CoPilot! I have a video of what I'm talking about:
http://youtu.be/ZypwoUF8xvQ
If anyone has any ideas, I'm all ears. I do not want to go all the way back to ICS.

Is this experienced on one specific ROM, or is this on EVERY JB ROMs you have used? If not just swap a ROM and see what happens...
Sent from HTC Incredible S @ PACman v21

GPS has been wonky for me on all JB ROMs. You can try a program like GPS Test to clear GPS data. Works for me most of the time.
Sent from my SPH-D700 using Tapatalk 2

I agree with frosted. I've also been using GPS status. It allows you to download assisted GPS data and calibrate if needed. It results in much faster and better locks.
Sent from my SPH-D700 using xda premium

frostedunit said:
GPS has been wonky for me on all JB ROMs. You can try a program like GPS Test to clear GPS data. Works for me most of the time.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Never had a problem before JB roms. No need for any kind of data as I do not have data, and haven't for years. That's why I like this program...don't need data. I've been suggested this gps test program before and it had no effect.
It really baffles me why the GPS does what's shown in the youtube video. I thought it was coincidental until a second phone of mine did the exact same thing. Both are samsung epics. I've tried:
CM 10.1
AOKP 4.2.2
Pac Man latest (v22?)
All are the same.
Edit: GPS test sees some satellites, but never locks.

I'm on CM 10.1 and can not even FIND a GPS satellite let alone lock on it. I have tried all the GPS tests SNC fixes... NADA!! Clean ROM install also... Fixed permissions... Cleared everything... Uninstalled reinstalled... Never had issue before updating from Gingerbread!!

preston411 said:
I'm on CM 10.1 and can not even FIND a GPS satellite let alone lock on it. I have tried all the GPS tests SNC fixes... NADA!! Clean ROM install also... Fixed permissions... Cleared everything... Uninstalled reinstalled... Never had issue before updating from Gingerbread!!
Click to expand...
Click to collapse
Our phone was never meant to go beyond GB. The fact that it has ICS and JB based roms that were never meant for it is amazing in it's own right. With that in mind, if something doesn't work right give it time and devs will find a fix.

I think I may have learned something. On the first boot, it seems to lock GPS just fine. No alternating like that video. I changed to Slim Bean rom, but I'm hesitant to reboot the device for risk of breaking my GPS. You guys think if it were to break in the future, wiping Dalvik Cache would work? I think I remember reading somewhere (on a different phone) that wiping dalvik cache was required to use a feature (which I believe was MMS). It's a stretch, I know.
Edit:
preston411 said:
I'm on CM 10.1 and can not even FIND a GPS satellite let alone lock on it. I have tried all the GPS tests SNC fixes... NADA!! Clean ROM install also... Fixed permissions... Cleared everything... Uninstalled reinstalled... Never had issue before updating from Gingerbread!!
Click to expand...
Click to collapse
I have a 3rd Epic that has this problem. I believe the GPS module might be fried, my friend. I upgraded two other Epics on the same upgrade path with no problems (well, until now).
@Dynamic - Yes, of course. What is done to this phone is simply amazing and has made it so I don't feel I need to upgrade. That, in its own right, is amazing. If the devs do not know that this could be a problem, well how are they going to fix it? I'm not selfish, just trying to help iron out all remaining problems. CoPilot is a great program, too!

TPMJB said:
I think I may have learned something. On the first boot, it seems to lock GPS just fine. No alternating like that video. I changed to Slim Bean rom, but I'm hesitant to reboot the device for risk of breaking my GPS. You guys think if it were to break in the future, wiping Dalvik Cache would work? I think I remember reading somewhere (on a different phone) that wiping dalvik cache was required to use a feature (which I believe was MMS). It's a stretch, I know.
Edit:
I have a 3rd Epic that has this problem. I believe the GPS module might be fried, my friend. I upgraded two other Epics on the same upgrade path with no problems (well, until now).
@Dynamic - Yes, of course. What is done to this phone is simply amazing and has made it so I don't feel I need to upgrade. That, in its own right, is amazing. If the devs do not know that this could be a problem, well how are they going to fix it? I'm not selfish, just trying to help iron out all remaining problems. CoPilot is a great program, too!
Click to expand...
Click to collapse
If I came off as negative in any way I apologize.

DynamicN said:
If I came off as negative in any way I apologize.
Click to expand...
Click to collapse
Oh, no. I was just thinking I came off as spoiled. Felt I needed to clarify.

Didn't reboot the phone, but tried again to lock the satellites and got the same phenomenon. Wiping the Dalvik cache seems to fix the problem, but I had to re-install CoPilot.
So does that mean there's a problem with the way App Data is being stored?

TPMJB said:
Oh, no. I was just thinking I came off as spoiled. Felt I needed to clarify.
Click to expand...
Click to collapse
Not at all

I'd just like to say that GPS test locks just fine, but it seems CoPilot does not. I'm assuming it's a problem with the application then?

TPMJB said:
I'd just like to say that GPS test locks just fine, but it seems CoPilot does not. I'm assuming it's a problem with the application then?
Click to expand...
Click to collapse
Have you cleared data in the app?

DynamicN said:
Have you cleared data in the app?
Click to expand...
Click to collapse
I have, but CoPilot randomly works and randomly doesn't. I really couldn't tell you either way if it's fixed. It seems to be a problem exclusively with CoPilot, if other programs work.

TPMJB said:
I have, but CoPilot randomly works and randomly doesn't. I really couldn't tell you either way if it's fixed. It seems to be a problem exclusively with CoPilot, if other programs work.
Click to expand...
Click to collapse
I agree, I think CoPilot is the culprit. If it hasn't worked on any JB roms then it sounds like there's an incompatibility issue which I'm sure will be fixed upstream at some point.

So it took me a LONG time, but I FINALLY figured it out! I now have CoPilot working %100, though it sucks my battery (even when plugged in).
On first boot, it works fine, but things I noticed:
-When somebody calls, GPS starts doing this again:
http://www.youtube.com/watch?v=ZypwoUF8xvQ
-Rebooting doesn't fix the problem
-Wiping Dalvik and/or cache does not fix the problem.
So what has to be done is you have to go into apps, select the copilot app, clear cache, then exit to homescreen.
Turn off GPS and start up copilot
Go to the "GPS" setting in the menu and turn on GPS
GPS should lock all fine! No more of what happens above.
I mean, it's annoying, but CoPilot is WAY better than my standalone GPS.

Android 4.3 WiFi Issue

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