IssueTracker

People is trying to track all emoji issues. I shared this one, check https://code.google.com/p/android/issues/detail?id=73248

Already (at least partially) fixed in FutureRelease. Keeping open to make sure everything is actually fixed.

What happened here (follow link below)??? Why did the help desk person turn into a blob?? This is a serious step in a terrible direction for emoji on Android.

http://emojipedia.org/information-desk-person/

Thank you for your feedback. We have tried our best to address the issue reported, however our product team has shifted work priority which doesn't include this issue. For now, we will be closing the issue as "Won't Fix (Obsolete)". If this issue still currently exists, we request that you log a new issue along with the latest bug report here: https://goo.gl/TbMiIO and reference this bug for context.

Tengo problemas con la conexion WiFi en mi nexus con jb 4.1.1

[Comment deleted]

I'm getting roughly half the signal strength on my galaxy nexus gsm version. I just got the phone so i can't compare the signal strength to ICS. currently running 4.1.1 baseband I9255XXLF1. My router is a buffalo whr-hp-g54
 Wireless mode 11g/11b. Encryption WPA psk.

same issue: dropping out of range with 4.1.1 where i didn't with 4.0.4

Same Issue with jb 4.1.1 (but also with ICS), nexus GSM version.
Wifi suddenly stop to work : very low wifi signal, Wifi range and signal level is too poor.
I can't use any wifi connection, at home and outside.

Same problem here. After a while the WiFi icons become grey and I can't use the connection even if it appears to be connected. The only way to solve this is to turn the WiFi off and back on again (airplane mode works too)

Same problem here too. I had no WiFi issues with ICS and could use WiFi on my balcony. I barely can now. If I leave the phone sleeping for a few minutes and then unlock it WiFi is dead and I have so switch it off and then back on again for it to start working as before. ICS WiFi connections were way more reliable. I have no idea what's causing this and thought I was the only one at first before I saw this.

This is a real issue. I got my phone a few days ago and while I was on ICS for a few hours before updating to JB, the wifi connection was much more stable than JB. Rather wierd. Here's a thread that references back to this thread: http://forum.xda-developers.com/showthread.php?t=1769908

Sitting next to the router (literally 5 feet) and I get not more than 3 bars, that too gray! Bring back ICS wifi goodness please.

Please provide router details for the issues where the network is shown as "out of range"

Galaxy Nexus 4.1.1 JRO03C
Since upgrading to Jelly bean, cannot access home wifi.

Since upgrading my Galaxy Nexus to Jelly Bean 4.1.1 JRO03C
My wifi connection has been unstable as it will drop even having 3 or 4 bars and while I am sitting within a foot of the router.  As well, if the signal does not drop my phone loses connection to all google services.

WiFi will connect then drop while saying its still connected.  Very frustrating.

I am having the exact same issue, I had never encountered WiFi problems when I used to run ICS. After I updated to JB, my connection would drop very frequently. I found and disabled the advanced setting to avoid poor connections, it dropped slightly less frequently but still very often. Most of the time my WiFi notificafion bar shows blue bars as though it is connected to the network fine, but it will have no internet access - cant load web pages in the browser, load the Google Play Store, or send messages on my Whatsapp messenger or Hookt. This is very frustrating and definitely a huge turnoff for Jelly Bean.

Galaxy Nexus 4.1.1 JRO03C
Since upgrading to Jelly Bean (a few days ago), access to (home) wifi connection fails after a short time. Same problem as the rest in this post. Please HELP. What can we do?

Same issue!!! Galaxy Nexus 4.1.1 JRO03C

I wonder how can this be classified as "Medium" priority...

I "fixed" the wifi problem with static ip in the phone, now i only have problem with mobile data ( i can't get static off course ).

That's not it. I have static IP and the problem is still present.

For me works perfect, but only for wifi for 3g/edge/gprs still the problem.

I can see the Wifi strength is good. but when I try click connect...it just shows the connection as saved, and a notification for "Wi-Fi networks available", pops up.

Doesn't actually connect.


After a while it will connect but then eventually drop again. Worked fine with ICS.

Same issue here, range very low, even next to the router, the signal bars and strength is low. Hoping for a fix soon.

Same issue here! :(

Upgraded from ICS 4.0.4 to JB 4.1.1 my GN a few days ago, in general connection with my home wifi base (WPA2) seems ok, but connection in the office (WPA enterprise, PEAP) is lost, unable to connect and very low signal strenght.
Agree that this is not a medium priority issue, I lost one of the most useful functionalities on my phone! A prompt remedial to this is expected, thanks!

I face the same issue and try this solution and find it better.

First for WIFI go to setting>wifi>advance > Wifi frequency band >2.4 GHZ only (may be 5 GHZ only should work too but I have no router to try.

The signal change from 1 bar to almost Full.This location about 5 meter in front of router. All device I had try show full. For this solution it almost fix but not 100% but it better than do nothing.

I am experiencing the same issue regardless of wifi frequency.

Same issue here on GSM Galaxy Nexus.  Phone is brand-new and updated to Jelly Bean (4.1.1.) within a few minutes of turning on.  Router is an Asus RT-N16 running Tomato 1.28.

Related issue: WiFi connection drops in sleep mode. Tested unprotected and WPA2 on 2 identical Galaxy Nexus Yakju devices. TP-Link routers & AP's.

Try to put static local ip address from your network, this "fixed" the problem with wifi for me "no grey bars idle", in wifi set it for static ip, put correct dns.
This work fine for me.

Galaxy Nexus with Jelly Bean 4.1.1 JRO03C

The wifi range does not seem to be the problem. But as soon as the phone goes into "sleep" mode the phone loses connection. Sometimes i have to turn off wifi and then turn it on again to reestablish connection. sometimes it will connect automatically.
the option "keep Wi-Fi on during sleep" is on "always" and "avoid poor connections" is deactivated.

i did't have these problems with ICS 4.0.4

i have the problem with different routers.

How to fix wifi:

Be sure you are connected to your wifi router/ap and follow this steps:

1- Go to System settings
2- Wireless & networks> wifi, long press on your wifi network and press in the menu
   Modify Networ

3- Tick on: Show advanced options

4- ip settings change dhcp to static
   ip address : your local ip address Example 192.168.*.*
   gateway: your router/ap ip
   network prefix: 24
   dns1: choose your prefered dns or use google or opendns
   dns2: choose your prefered dns or use google or opendns

Using a static IP doesn't solve the problem. I always use a static IP when I'm home. To be honest I solved the problem flashing a custom made kernel.

Agree, static IP doesn't solve the problem. It's a shame, we have to look for custom kernel to solve the issue, the whole purpose of getting this phone is getting updates directly from Google. BTW, which custom kernel did you flash.

My solution is for wifi become grey when the phone was idle for a while.

Yep - static IP not solving it for me either.  I am having the same issues on the Wi-Fi network at work that is using a Linksys E3200 router (problem occurs at both 2.4 and 5 GHz).

@praveen using franco's now, but it's too early to see if it's working correctly. I agree it's a shame that we have to use custom kernel, but it's the only way, at least until the stock get fixed.

I have the same problem at work. The Wifi Signal is too weak with JB, although I can easily connect with any laptop.

Static ip and dns works for me as a workaround. Thanks!!!

Yes, it appears if I set it to Static ip and enter the correct dns info it functions a little more stable and does seem to be a decent work around for the problem.

At least it seems to work so far for me. Hopefully other people have as much luck!

Hi,

In order to look into this issue, we'd like to collect more information from those who received the OTA update to Jelly Bean.

If you're experiencing reduced Wi-Fi stability after updating from Ice Cream Sandwich:

1. Follow the instructions below:
http://support.google.com/mobile/bin/request.py?&src=6829972&contact_type=android_bugreport
(Note that this link is only valid for reports about reduced Wi-Fi stability after the Jelly Bean update)

2. Please include exact router details (manufacturer and model, security settings, firmware versions, advanced settings, etc.)

We appreciate this information as we look into your reports,
Ethan

Ethan - just uploaded a bug report, hope you guys can get this resolved.  Thanks!

Same here, WiFi drops and bad reception after latest Jelly Bean update on Nexus.

Same problem with my Nexus S after updating to Jelly Bean JRO03E. Using a Cisco EPC 3925 router and a range extender.

I had the same issue here at my office using 3 different CISCO routeurs as wifi bridge with 3 different Name (i.e. routeur1, routeur2 etc). WHen I checked on the ipconfig of my laptop connected to the same routeur as my Nexus S, I remarked that I have two two different gateway visible there 192.168.1.1 and 192.168.0.1. My nexus s was connected using dhcp on the 192.168.1.1 and now I pass it to static IP using the 192.168.0.1 and it works fine. Before I was always able to connect to my routeur but I had no internet connection (gray icon). So I guess the mapping is not correctly done on Jelly Bean (4.1.1)

Nexus S / 4.1.1 / I9020XXKL1 / JR003E
installed jelly bean on a clean completely formatted phone.
Wifi signal seems normal, but every few minutes the wifi icon on the notification bar just turns gray and connectivity dies. I have disable/enable wifi for it to come back. This is a HIGH priority issue.

Galaxy Nexus / 4.1.1 / TAKJU

I am starting to beleive that this is in connection with my issue.

Testing it for more than 3 night now it turned out that my phone is kept awake for too long during night if its connected (ornot???) to a wifi network.

With wifi connected it loses 31% of battery in 7 hours and it is shown in the battery graph that something keeps waking up my phone in every 2-3 minutes... could this be the wifi itself, triying to connect each time?

With only 3G enabled during the night, and having all the syncs enabled it only consumes 3-4%. Thats just to big difference to reject.

What do you think?

seems like the bug is on the motorola xoom too. I now have both a nexus s and a xoom with problems staying connected to my wifi. They had no problems while on ice cream sandwich.

Same problem here on my stock Galaxy Nexus 4.1.1 YAKJU. WIFI turns grey and connectivity dies. Was working perfectly on ICS

I also now have poor range and connectivity problems with my Xoom since upgrading to 4.1.1.

ICS worked really fine - after JB wifi just went down to 20% - please fix it.

Same here.  :(

Everyone who's having issues - please submit a bug report as mentioned in post #43.

http://code.google.com/p/android/issues/detail?id=34942#c43

I thought I was having this problem (comment #2) but after quite a bit of testing, I'm not blaming Jelly Bean anymore. I conducted signal strength vs. Download / Upload speed for the following devices:
Nexus 7 Jelly Bean JRO03D
Galaxy Nexus GSM Jelly Bean JRO03C
TMobile HTC One S ICS 4.0.3
Galaxy Nexus GSM ICS 4.0.4 (separate unit from Samsung ordered under warranty for this issue)
Samsung Vibrant ICS CM9

My conclusions:
1) I found no quantifiable difference in signal strength or wifi speed between ICS and JB on my GNex units (they both were terrible compared to the other devices).  2)There was no difference between how ICS and JB scale the bars in the notification area to the signal strength.
3)At low signal strength both GNex's would drop the connection and the speedtest.net app would report a 'network error' within about 30sec of any lack in data sent or received. All other devices would just sit waiting for data to re-establish (I stopped the test on those after 2 minutes of lack of data)
4)The more modern HTC One S really kicks butt on upload speed (maybe higher power or better antenna?)

#3 may be why people are experiencing the grey'd out bars on their units.

For now I'm keeping the GNex cause I like the immediate updates to the lastest OS from Google. I guess I'm just going to have to blanket my house with high power wifi repeaters...

My data can be found here:
https://docs.google.com/spreadsheet/pub?key=0Apz8NjH1yi7bdGVYSnEzdHhHeFdHRjBaQVB0cVI1X3c&output=html

 

Would be so nice if Google could communicate something officially about this issue...

Not impressed with JB, supposed to be feature rich and optimized for Nexus, end result is terrible network connection and truly HORRIBLE battery life, same settings as I had on ICS, and went from zero network disconnects at home to pretty much any time I want to do something on the network it needs to be done with 5 minutes or connection is dropped and I have to start again, Priority should be High at least, this is a severe issue which is impacting my work as a network tech.

I have been experiencing this issue since updating to Jelly Bean. It is possible to trigger it by turn on Airplane Mode, then turning it off, there will now be no wifi. Going into wifi and manually selecting "Connect" has no effect. Device is Nexus S.  

dmesg contains errors:

<4>[ 1119.784992] =========== WLAN going back to live  ========
<4>[ 1119.785081] sdio_reset_comm():
<4>[ 1119.793040] F1 signature read @0x18000000=0x9934329
<4>[ 1119.795014] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 1119.839951] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
<6>[ 1119.917197] wake enabled for irq 164
<4>[ 1119.918335] wifi_get_mac_addr
<4>[ 1119.919904] Firmware up: op_mode=1, Broadcom Dongle Host Driver mac=b4:07:f9:08:xx:yy
<4>[ 1119.925610] Firmware version = wl0: Apr 11 2012 15:30:54 version 4.218.248.42
<3>[ 1119.926539] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23
<3>[ 1120.326295] WLDEV-ERROR) wldev_set_country : wldev_set_country: set country for GB as EU rev 5
<3>[ 1120.336432] WLDEV-ERROR) wldev_set_country : wldev_set_country: set country for GB as EU rev 5
<4>[ 1120.449268] link down, during connecting
<3>[ 1120.449376] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed
<3>[ 1121.454929] CFG80211-ERROR) wl_run_escan :  Escan set error (-16)
<3>[ 1121.456568] CFG80211-ERROR) wl_run_escan : error (-16)
<3>[ 1121.458094] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)
<3>[ 1122.467569] CFG80211-ERROR) wl_run_escan :  Escan set error (-16)
<3>[ 1122.467877] CFG80211-ERROR) wl_run_escan : error (-16)
<3>[ 1122.468280] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)
<3>[ 1123.476486] CFG80211-ERROR) wl_run_escan :  Escan set error (-16)
<3>[ 1123.476682] CFG80211-ERROR) wl_run_escan : error (-16)

The last error lines are then repeated many times.

There is a workaround: turning wifi off and back on again brings the wifi connection back up.

Funny thing is that amateurs modders who mostly dont get paid for they work have almost instantly fixed this problem. Insted from google there is still silence and this HUGE problem has still a "medium" priority.
Wow.

After some more testing, I don't seem to encounter this anymore. When I read someone fixed it by checking "Avoir poor connections" in the Wi-Fi Advanced settings, I checked it and it was working better right away. I just checked my settings again and the checkmark is now gone. I wouldn't know why though. Still no issues so far. Strange bug. I had the Wi-Fi issues only when the phone entered sleep mode. It would always disconnect while sleeping while I didn't have this issue with ICS. If I find something else I will report again.

Same problem with my Galaxy nexus

Shame on you Google, this is a fundamental problem that existed since ICS for me and it's still not fixed. I know my GNexus is wrong because it never happened on my iPhone 3gs, which is supposed to be inferior.

Are you listening to us Google?
Remember, Google should fix this major bug even before we had to file a report, not the other way around. This is extremely disappointing.

[Comment deleted]

[Comment deleted]

Same problem to me
The wifi connection is extremely unstable
I'm connecting to 3g instead till Google find a solution

There is certainly a problem with JB. I noticed poorer WiFi connection (range-wise) on Galaxy nexus HSPA+ right after updating to JB from ISC. And same was true for Xoom, after updating to 4.1.1. from 4.0.3.

Same problem here ICS reached all the way down my garden no problem

Jb lucky if it reaches the front door approx 4 metres

Wifi signal strength dropped after jelly bean install. Can not use wifi on JB in all areas of my home had no problem  with ICS with the same wifi router.

im going insane... not only is it dropping wifi but ithen goes into continuos reboot with the nexus "X" that i cant get past.... sick of this problem... please fix this google... sorry i ever got a nexus...

Same here with my Galaxy Nexus GSM. Tested with multiple routers (Zyxel, TP-Link). Wi-Fi signal is low and connection dies frequently.

Same issue here. have an Asus RT-N56U, and at 10 feet, it was complaining about poor conditions and refuses to connect. I thought it was the hardware again (this Nexus has been to the shop for a broken wifi antenna 10 days into use), so I flashed the device back to 4.0.4 factory image.

Over the Air upgrade to 4.1 seems to have no issues so far. Not impressed with this feature....

Constant WiFi drops and reconnects at low signal, and JB signal reports low anywhere beyond the same room as the router. So far behavior has been consistent both at home and with other access points. Problem seems to combine very limited range with poor handling of what JB perceives as marginal signal.

Nexus 7 Tablet
Android 4.1.1
Kernel 3.1.10-g52027f9
Build JR003D

It's still very strange that this problem is not existing on all the Nexus
devices. Many others report that there's nothing wrong with the WiFi signal
or whatsoever.

Google please tell us something as this issue is driving us crazy for real.

bad wifi with my galaxy nexus gsm im sitting 2meters from my router it gives just 2 signal bars please google give us a reason for this and a fix for that fast
on jelly bean

Still no response.  I've flashed both the Trinity and Franco kernels and neither has helped resolve this issue.

I have the same issue. My wifi signal reception considerable dropped after the jelly bean upgrade was pushed to my phone. I can't be the only one that has this issue so this might be a duplicate already. I looked thru the open issues and didn't find any...

The phone drops the connection and it take a long time to connect. I have other devices laptop, iphone, ipods, ipad and they always show strong signal.

Galaxy Nexus
4.1.1
Baseband Version
I925XXLF1

Kernel
3.0.31-g6fb96c9
android-build@vpbs1 )
#1 SMP PREEMT Thu Jun 28

Build Number JRO03C

What is most disappointing about this issue is that there is no feedback from Google whatsoever.  Surely they have a basic understanding of service management to know that the first thing you do is acknowledge that there is a problem and assure clients that you are looking at it.  Even that is not happening.

BTW, the problem is not limited to Netgear routers, the N band, or one version of Android.

[Comment deleted]

Actually, it did help to change to static IP as indicated above although it still has issues.

Same here. Constant WiFi drops and reconnects at low signal, and JB signal reports low anywhere beyond the same room as the router.

Stock Samsung Galaxy Nexus GSM. Jelly Bean JRO03C 4.1.1.
Router : TP-Link 450 Mbps Dual-Band Wireless N Gigabit router TL-WR2543ND

[Comment deleted]

I think that the problem was there, where is the modem + router. Modem at me have IP 192.168.1.1 and router for wifi have IP 192.168.2.1
ICS 4.1 at me on advance option have default gateway 192.168.1.1, so look for DHCP IP higher 192.168.1.100>> but there is no responce (modem will not give the IP)
When i put static IP 192.168.1.110 (or somethink higher then 100)the default gatawey was change on 192.168.2.1 - that was the right!And wifi conection was start immediately.
Sorry for my english :)

When i put static IP 192.168.1.110 >>> mistake
When I put staic IP 192.168.2.110 >>> is right

I have tried all of the fixes on here, static IP, unchecking "avoid poor connections", etc., but it's not really a fix for the range issue. There's no reason for the device to only show half strength when you're only 10-15 feet from the router. I have contacted Google about this issue directly and the guy acted like this is not an issue he was aware of and offered to swap out the device. I don't want a refurbished phone for the brand new one I bought last week, especially when I know that won't fix the issue. I even sent him a link to this thread, asking him to raise the priority or forward this issue to someone who could look into it. All he did was offer a replacement. I expected more from a "pure Google experience" phone. I'll definitely wait it out, but I'm really waiting for Google to step it up here. I have seen Verizon users having to root their phones and patch the wifi with a file from the 4.0 system folder. We shouldn't have to resort to that.

Static IP address does seem to connect faster. Also unchecking the "avoid poor connections" does too help...

I was doing some development work on a network related app and happened to be running adb logcat when my wifi connection dropped. There was an error immediately preceding the resulting IOException:

08-25 19:20:59.483: E/GPS(248): [assist_update_network_state][line = 1199] : Failed to call BrcmLbs_sync()

Suggests that network dropping out may be caused by some interaction between the Broadcom GPS driver and the Broadcom wifi.

Some interesting comparisons: This issue is definitely evident with my 4.1.1 Galaxy Nexus GSM, but is *not* present with my 4.1.1 Nexus S AWS.

Same problem, with Nexus i9250 Original ROM 4.1.1

Did you guys really read the comments?
Google has replied on Comment 13 (https://code.google.com/p/android/issues/detail?id=34942#c13) and Comment 43 (https://code.google.com/p/android/issues/detail?id=34942#c43)

If you only mentioned "same problem here", it will not help to solve the problem.
Click star icon has the same meaning, rather than spam other people mailbox with "same problem" emails.

Asus rt-n56u, wireless n router

WiFi is unusable on my gnex in bedroom, while my wife's old Sony Ericsson xperia arc has almost perfect connection.

WiFi is so poor on JB, I never got any problem with ICS. Stock ROM and kernel.

I can only use the WiFi when 2 feet from my router.

[Comment deleted]

Hello
I have the same problem, I bought the phone today, if not the solution I return it to the retailer. Please advice whether it is somehow anstavit to work steadily wifi.

I use wifi modem
VDSL modem Comtrend VR-3026 Multi - DSL

Equipment purchased today
Galaxy Nexus
Android 4.1.1
Core 3,0,31 - g6fb96c9
android - build @ vpbs1)
Preempt # 1 SMP Thu Jun 28 11:02:39 PDT 2012
The build number
JR003C

Please correct way to stability of the connection. Change DHCP to static did not help me. In a notebook in the same place at -50 signal strength fluctuates phone power outages and signal strength is not above -70. Thank you for the advice.

First: Sorry for the poor english, I´m from Sweden! :-))

Same problem here.
With ICS, no connect problem.
With upgrade to JB I can´t connect to an open Linksys.

At wi-fi settings I can see full signalbars for the Linksys, but on the statusdisplay there is nothing, no bars, no nothing except battery, 3G and time.
When connecting Linksys it switch over from connecting to "Saved" in Wi-Fi settings meny.

It can´t connect it, no matter what. Before upgrade it connected on auto without problem.
I have checked most tips above without result, it doesn´t help.


No point to have wi-fi if you have to be so close as 5m.

[Comment deleted]

Same issue here on Nexus S with French FreeBox & Livebox :

With ICS, no connectivity problem.
With JB, WIFI connection hang every 2-5 min.
Back to ICS, also no connectivity problem.

I have the same issue, wifi signal is good on Nexus S using ics but very poor and almost unusable when updated to jelly bean.

With Franco kernel r250 the problem has been completely solved! Google has fixed that in its sources

Same problem with Nexus S.Google wake up !

The new driver still not fixing my WiFi.

Same issues here on Galaxy Nexus after Jelly Bean update. 2.4 GHZ very slow connection and dropped connections. 5 GHZ ok.

Same issues here on my Nexus. Weak signals, 2.4 is semi stable and 5GHZ not working at all.
Both freq worked fine in 4.0 ICS.
Cisco E3000
No issues with any other wireless devices.
You can see in the attached the 5GHZ drops off. Its like this ALL the time.

Is there any fix release from Google ? It been so long....at least a beta
release ?

I emailed Google asking if they were working on a fix for this and here was my reply sent on September 4th, 2012:  

"Thank you for contacting Google. There are no known issues with the Galaxy Nexus not being able to get good reception with WiFi."

... :(

I am also noticing lower signal strengths in the status bar, but also drop outs while browsing from my bed, where it worked perfectly before update to Jellybean.

I'm another GNex user affected.  Most of the time the device is less than a meter from the AP.  After a while it shows the wifi grey and apps all complain about lack of internet.  I usually reboot at which point it works perfectly for a while.  Completely unaffected are the Galaxy Tab sitting next to it, my laptop, Roku, Wii, AppleTV, a Linux based HTPC etc.  The only device with problems is the GNex.  4.1.1 was installed as a clean wipe and I do have settings to always keep wifi on and ignore poor reception.

Ive got the same issue, the receiving signal of ics is much better than on JB please  provide a fix. thanks

I am having same issue.
Using Gnex 4.1.1. I am loosing wi-fi and network signal. Tried all the work around mentioned here. No luck.

definitely having this issue with new GN 4.1.1 -can't even get signal out on the road in very strong reception areas with AT&T - are people getting this same problem with T-Mobile?

Brand new gnex immediately flashed to jelly bean and wiFi got slow immediately. Please fix!

Same issue here, brand new Galaxy Nexus, will not connect to wireless

Nexus S.After JB update wifi drops every 3 mins or so in the next room from the router.
I thought it was just me having problems but obviously not.
ICS connected all the time.

[Comment deleted]

Same here Galaxy Nexus JB 4.1.1 flashed with official JB build JRO03C (baseband: I9250XXLF1) have 2 bars having a phone 1ft from router and it disconnects every minute or so ... streaming youtube or similar became practically impossible (to stream shotcast I need to have 30sec buffering and still it's painful), on ICS 4.0.4 works like a charm (tryed to revert to ICS for testing)

[Comment deleted]

While that can help fix the bug, but how will you get the details from
public networks like Starbucks, McD's ? I initially thought it's my router
and tried at Starbucks but the same issue.

[Comment deleted]

I have the same issue but nearly as bad. I do have issues with the phone (maguro) dropping the connection to Google after a while when idle for a few minutes (when set to keep wifi on during sleep).

Could the issue be caused by the version mismatch between the broadcom kernel driver (currently 5.90.195.104) and the firmware blob fw_bcmdhd.bin (currently 5.90.195.61 Date: 2012-04-26)? Something could've happened in those roughly 4 months (the kernel drivers is from August). Before JB, the blob was always updated in sync with the kernel driver.

After airplane mode for several hours phone is unable to connect to (WPA) wifi.

Phone: Google Nexus S.

Router: Sagemcom, Model Number F@ST2504n, Firmware Version 6.14.1a4N_UNI (supplied by Sky Broadband UK)

dmesg:

<3>[287805.353077] CFG80211-ERROR) wl_run_escan :  Escan set error (-16)
<3>[287805.353341] CFG80211-ERROR) wl_run_escan : error (-16)
<3>[287805.353555] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)
<3>[287806.356646] CFG80211-ERROR) wl_run_escan :  Escan set error (-16)
<3>[287806.356956] CFG80211-ERROR) wl_run_escan : error (-16)
<3>[287806.357356] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)
<3>[287807.127311] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
<4>[287807.128891] wl_android_wifi_off in
<6>[287807.129153] wake disabled for irq 164
<4>[287807.129344] wifi_set_power = 0
<4>[287807.129427] =========== WLAN placed in RESET ========
<4>[287811.065900]
<4>[287811.065914] Dongle Host Driver, version 5.90.195.75
<4>[287811.065919] Compiled in drivers/net/wireless/bcmdhd on Jul 13 2012 at 11:51:41
<4>[287811.066167] wl_android_wifi_on in
<4>[287811.066242] wifi_set_power = 1
<4>[287811.271825] =========== WLAN going back to live  ========
<4>[287811.272547] sdio_reset_comm():
<4>[287811.283378] F1 signature read @0x18000000=0x9934329
<4>[287811.298708] DHD: dongle ram size is set to 294912(orig 294912)
<4>[287811.385117] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
<6>[287811.462676] wake enabled for irq 164
<4>[287811.463533] wifi_get_mac_addr
<4>[287811.464419] Firmware up: op_mode=1, Broadcom Dongle Host Driver mac=b4:07:f9:08:a6:29
<4>[287811.469837] Firmware version = wl0: Apr 11 2012 15:30:54 version 4.218.248.42
<3>[287811.470709] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23
<3>[287811.958578] WLDEV-ERROR) wldev_set_country : wldev_set_country: set country for GB as EU rev 5
<4>[287812.923860] connect failed event=0 e->status 0x1
<3>[287812.925198] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed
<4>[287815.487821] connect failed event=0 e->status 0x1
<3>[287815.488533] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed
<4>[287818.146768] connect failed event=0 e->status 0x1
<3>[287818.147472] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed

Then it loops showing the "CFG80211-ERROR" and "connect failed" lines repeatedly.

And then:

<4>[288408.183545] connect failed event=0 e->status 0x1
<3>[288408.183638] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed
<4>[288408.731665] dumpstate: page allocation failure: order:5, mode:0x40d0
<4>[288408.731746] Backtrace:
<4>[288408.732014] [<c003f8a4>] (dump_backtrace+0x0/0x10c) from [<c056e09c>] (dump_stack+0x18/0x1c)
<4>[288408.732082]  r6:00000000 r5:000040d0 r4:00000001 r3:00000000
<4>[288408.732446] [<c056e084>] (dump_stack+0x0/0x1c) from [<c00d94bc>] (warn_alloc_failed+0xc8/0x100)
<4>[288408.732574] [<c00d93f4>] (warn_alloc_failed+0x0/0x100) from [<c00dbe60>] (__alloc_pages_nodemask+0x5a0/0x78c)
<4>[288408.732643]  r3:00000000 r2:00000000
<4>[288408.732825]  r8:00000000 r7:000040d0 r6:00000005 r5:00000000 r4:00000001
<4>[288408.733195] [<c00db8c0>] (__alloc_pages_nodemask+0x0/0x78c) from [<c00dc064>] (__get_free_pages+0x18/0x5c)
<4>[288408.733322] [<c00dc04c>] (__get_free_pages+0x0/0x5c) from [<c0109594>] (kmalloc_order_trace+0x2c/0xec)
<4>[288408.733448] [<c0109568>] (kmalloc_order_trace+0x0/0xec) from [<c0109814>] (__kmalloc+0x1c0/0x1e4)
<4>[288408.733572] [<c0109654>] (__kmalloc+0x0/0x1e4) from [<c012f248>] (seq_read+0x260/0x4e0)
<4>[288408.733700] [<c012efe8>] (seq_read+0x0/0x4e0) from [<c010f028>] (vfs_read+0xac/0x13c)
<4>[288408.733774] [<c010ef7c>] (vfs_read+0x0/0x13c) from [<c010f0fc>] (sys_read+0x44/0x70)
<4>[288408.733894]  r8:00000000 r7:00000003 r6:00008000 r5:bea8f82c r4:e16ba880
<4>[288408.734315] [<c010f0b8>] (sys_read+0x0/0x70) from [<c003ba40>] (ret_fast_syscall+0x0/0x30)
<4>[288408.734382]  r9:e427c000 r8:c003bbe8 r6:00000000 r5:0000000a r4:400696bd
<4>[288408.734794] Mem-info:
<4>[288408.734856] Normal per-cpu:
<4>[288408.734921] CPU    0: hi:   90, btch:  15 usd:   0
<4>[288408.735047] active_anon:56254 inactive_anon:65 isolated_anon:0
<4>[288408.735051]  active_file:5304 inactive_file:5097 isolated_file:0
<4>[288408.735056]  unevictable:83 dirty:20 writeback:0 unstable:0
<4>[288408.735061]  free:3360 slab_reclaimable:971 slab_unreclaimable:3249
<4>[288408.735066]  mapped:14273 shmem:73 pagetables:1851 bounce:0
<4>[288408.735483] Normal free:13440kB min:2396kB low:2992kB high:3592kB active_anon:225016kB inactive_anon:260kB active_file:21216kB inactive_file:20388kB unevictable:332kB isolated(anon):0kB isolated(file):0kB present:359788kB mlocked:0kB dirty:80kB writeback:0kB mapped:57092kB shmem:292kB slab_reclaimable:3884kB slab_unreclaimable:12996kB kernel_stack:5296kB pagetables:7404kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
<4>[288408.735798] lowmem_reserve[]: 0 0
<4>[288408.736040] Normal: 2304*4kB 248*8kB 64*16kB 22*32kB 6*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 13440kB
<4>[288408.736869] 10557 total pagecache pages
<4>[288408.746957] 118528 pages of RAM
<4>[288408.747034] 31475 free pages
<4>[288408.747097] 3370 reserved pages
<4>[288408.747214] 3632 slab pages
<4>[288408.747276] 126632 pages shared
<4>[288408.747340] 0 pages swap cached
<4>[288410.748299] connect failed event=0 e->status 0x1
<3>[288410.748442] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed
<4>[288413.303817] connect failed event=0 e->status 0x1
<3>[288413.303989] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed

And then those last two lines repeated hundreds of times.

logcat shows repeated loop like:

I/wpa_supplicant( 3480): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
E/wpa_supplicant( 3480): Retrying assoc Iteration:1
I/wpa_supplicant( 3480): wlan0: Trying to associate with 4c:17:eb:56:a9:58 (SSID='WIFI' freq=2412 MHz)
I/wpa_supplicant( 3480): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
E/wpa_supplicant( 3480): Retrying assoc Iteration:1
I/wpa_supplicant( 3480): wlan0: Trying to associate with 4c:17:eb:56:a9:58 (SSID='WIFI' freq=2412 MHz)

The last lines are repeated hundreds of times.

After the above issue, I rebooted the phone and still couldn't connect. After rebooting the router I was finally able to establish a connection.

It's not just JB

Two of us at my office experiencing same poor WiFi connecting to a VZ SCH-LC11 using WPA PSK

My phone recently started experiencing this issue.  It's still ICS.

Galaxy Nexus
4.0.4
Baseband Version
I515.10 V.FC04 / I515FC05

Kernel
3.0.8-gda6252b
android-build@vpbs1 #1
SMP PREEMT Fri Apr 13

Build: IMM76K

Co-worker is on JB and also has same intermittent connectivity.

Nexus 7 Tablet
Android 4.1.1
Build Number CM 10 10-20120920-NIGHTLY-grouper

We are within 3 ft of the MiFi access point. Signal goes from full strength to "Avoided Poor Internet Connection"  randomly.

Thx
- Bill

Same here with a Nexus 7 Tablet (never updated from previous version). Problem occurs with every single router I've been on so far. What happens very often is that the Nexus shows internet available with good strength (3 blue bars) but there is no connection. Chrome, play, facebook all give a connection error. Most of the times going to airplane mode and back works, not always though. Sometimes restarting helps or waiting some time works too.

I have wifi issues on my gnex jellybean 4.1.1 yakju .. it gets disconnected randomly and gets stuck at obtaining IP but does not really connect.. all other devices at home work perfectly.

+1
same problem here. I bought two Nexus 7 and both devices could not live with Wifi without disconnecting every 10 minutes (saying "Obtaining IP address"). I also upgraded my Samsung Galaxy 2 from CM9 to CM10 (jellybean based) and stated to experience wifi connectivity problems.
"Static IP fix" works for me, but I could not be so confident in my wifi connection anymore - the signal drops from time to time even with "static ip fix".

Can you elaborate how static IP fix works??

[Comment deleted]

to #127
basically you need to do two things:
1) change your router settings, so that android devices use static IP instead of getting it from DHCP. Usually this can be done by 'MAC address - IP address' association.
2) change it in your android device settings: long press on wifi connection -> modify network -> advanced -> enter static IP that you previously assign to android device in router's admin panel.

After making these changes I no longer see "Obtaining IP address" and wi-fi connection is more or less stable, although not as stable as it was on ICS on my galaxy-s2.

PS
It could be router specific issue. Mine is ASUS RT-N16. I did't have a chance to check it on different router.

[Comment deleted]

Thanks a lot .. will try this but need update for this issue soon.. we should not have to go through this trouble

Please, everyone, report these through the site

http://support.google.com/mobile/bin/request.py?&src=6900052&contact_type=android_bugreport

And reference this thread number in the email you send in.

Rob

same problem here... jellybean crashes my cisco router e4200 (v1)

I've reported the bug through the Google support link but it seems that Google engineers do not want to give any feedback. Bug resolution is supposed to be a two-way process; for all we know, Google engineers may have already fixed the bug in their internal builds, and we are just wasting our time uploading bug reports.

Has this issue been reproduced at Google? It is not difficult to reproduce, it happens every single day on my Nexus S - I wake up, turn off airplane mode, and the phone wifi fails to come back up. When I turn wifi/airplane mode off and on several times, it seems to crash the router's wifi (ethernet connected devices still work fine, but all wifi devices can no longer access the internet, and the router has to be hard reset.)

Given how easy it is to reproduce, I find it hard to believe that Google's engineers haven't reproduced these issues. Which means that either this bug is either not a priority and is not being actively investigated, or it has been reproduced but is difficult to fix (perhaps the bug is in the baseband firmware), or it has already been fixed but an OTA update has not been arranged yet. Or perhaps the issues are indeed rare, and only occur on a minority of OTA updated phones with certain configurations and Google has been unable to reproduce those conditions. Either way, it would be nice to have some feedback. I am going to have to buy a new wifi router for myself as it is unacceptable to keep crashing the shared router; this shouldn't be necessary.

There is also a similar thread on this issue limited to Nexus 7 devices only
http://code.google.com/p/android/issues/detail?id=35496 

So there are much more people with this kind of problem аnd maybe if we double the number of prayers GOogle will hear us.

It looks like they've changed the process for submitting bugs.  The link I provided on Oct 1 doesn't seem to work.  I think this is the new way.  But it doesn't mention the USB debug related file.

https://code.google.com/p/android/issues/entry?template=User%20bug%20report%204.0

Rob, that link appears to be for 4.0 ICS, Jelly Bean is 4.1.

Yeah, they don't have a 4.1 link.  If anyone can find the new place let us know.

I have found this problem will all the custom roms I've tried (I didn't wait long enough to see a stock jb on sprint). My problem has been as described with the wifi connection constantly dropping out...often, it seems right when I would try to load a webpage. The Codename ROM also had this problem, until a version they released recently; I believe 3.6.0 is where they greatly improved it (I'm struggling to remember a time, now, where it dropped the connection when I needed it). It has made a world-of-a-difference for me. It was so frustrating...now I've got to wait until other ROMs fix it too. Is it just a problem with custom ROMs...hence why Google hasn't done anything to help it?

Anyone else notice that codename "fixes" the issue, or am I a lucky anomaly?

I have a MK808 mini android player 4.1.1
i have the same issue. wifi signal drop off.
not fun restarting wifi all the time

ci sono novità sulla correzione del bug??!?!

4.1.2 doesn't fix it either. Google, get this bug fixed. I don't want to have to buy an iPad Mini.

I finally made the decision to go with a smart phone after years of having a basic cellphone. My Wife and I both received our new android smartphones about two weeks ago. Everything worked fine for a few days until one day we noticed that our phones would not connect to our wireless network. The phones see our network, passwords are correct, but it said our phones were OUT OF RANGE. I tried everything to get the phones to connect. Forgetting the network, reentering the network, driving out of range, turning off wireless on the phones, etc.

So I started to troubleshoot the problem. We have had our wireless router for over a year with no problems ever connecting to other devices. I brought out my laptop to see if I could connect, and guess what? My laptop saw the network but would not connect. Well time to reboot the router. I rebooted the router, and everything worked again, for about a week, and then my router crashed again.

This is becoming really frustrating. I either can not use wireless on my phone and rack up data usage or I have to keep rebooting my router for any of my home devices to work. I have talked to some other people who say they have similar problems.

Actually, Princeton University had almost the same problem and have reported it to Google.http://code.google.com/p/android/issues/detail?id=11236 Google has yet to provide a fix. One work around is to have the setting for sleep with the WiFi set to never.

I just wish someone out there has an answer to this.

Thank you,
Jim

#144
Sorry your first cellphone and Android experience is so bad.  I've been using Google/Android for a few years now and and have an excellent experience with them ... up until now.  I hope this issue doesn't put you (or, indeed, me) off Android.

Even a progress update would be nice. Been since july and no info coming from gooooogle or broadcom. Its a shame. Im an inch away from tossing it all in favour of APPLE products. They work.

Well JB 4.1.2 has just been released for my phone but i need to flash stock back first so i will see if anything has been fixed/changed.

Nexus S btw.Love getting updates first!!
 
There is a change log here if anyone wants to look through it.
http://www.funkyandroid.com/aosp-JRO03D-JZO54K.html

Unfortunately the people who have received 4.1.2 for their Nexus 7's (who were reporting similar wi-fi problems) say that it does not fix the problem.

COME ON GOOGLE - WTF IS TAKING SO LONG?  HOW ABOUT AN UPDATE OF SOME KIND?

Same problems, though I read it's a 5Ghz issue. My 2.4Ghz connection works fine, but cannot get 5Ghz at all. Apparently after the OTA update 8???

Google ... put some effort in here!

My first Android phone and I am getting this problem, really sucks...really tempted to go back to my iphone 4s. As someone mentioned above, at least an update would be nice, but it looks like google is ignoring this problem.

same here, but with 4.0.4. WIFI only works extremely close to router and manually.
Samsun Galaxy S III GT-I9300
Also look at:
http://code.google.com/p/android/issues/detail?id=36993

I bought my google galaxy nexus when it just came out. There wasn't such a problem. I was satisfied. After updating to the latest Android OTA, now the wifi connection range really sucks. It's very unstable, even few feet away from the router, it shows only half of the signal. It appears that I am not alone.

Just updated to 4.1.2, PROBLEM IS STILL THERE.

same problem here with my Google nexus Asus .   very poor wifi signal when compared to my other wifi devices. my laptop and cellphone have twice the wifi signal strengh of the poor nexus signal. :(

May be returning my nexus 7 since this doesn't appear to be getting addressed.  Well iPad mini should be out soon.  Too bad Google :-(

[Comment deleted]

My wifi became weak after rooting - Cyanogenmod 9 galaxy s2. So are there any fixes?

To #157.
If you upgrade to CM10 (which is jellybean based) there is a good chance that your wifi  signal becomes even weaker.
I personally had no issues with wifi on galaxy s2 CM9. The problem started after upgrading to jellybean.

I second the comment #153: the problem remains after the update to 4.1.2. However, I cannot get what exactly triggers the "grey wifi" - sometimes a rather lengthy sleep mode still leaves the wifi intact while the other times the wife goes "grey" ("connected", but unusable) after a short "sleep".

Does anyone recommend using a 3rd party app like wifi fixer?

Just want to echo what others have been saying.

I've had the Gnex since April.  Initially it was great, and Wifi anyplace in my house was great.

After Jelly Bean I have weak wifi coverage. What used to be 4 bars can now be 1 or 2!

I have 4.1.2, that fixed nothing.

I chose the stock Android phone so that I would get fast reliable updates.

Maybe I need to rethink the iPhone 5.

I have Sanei N10 - At first it was OK then "Not in range" even standing 30cm away!
Signal strength is good when you scan but no connection.
Tried resetting router - Nothing.
N10 turn on/off - Nothing.
Rest wi-fi connection - Nothing.

What's up?
How can Google expect to champion when even wi-fi doesn't work!

Sanei again.
Factory reset & OK but why? as I never changed the wi-fi settings in the first place.
Just entered my wi-fi password, as before.
Now I have to reinstall the apps!

Hello,
Same problem here. Even during some time (about 10+- min.) Wi-fi are connected + Wi-Fi signal icon is blue (connected to Google services) but after 10min +- sometimes it goes to grey and stay only in local network without internet connection. On Router other devices (TV, PC, Notebook) still working with connection to internet. I have reservation for Nexus and other devices, everything are set correctly, but my Nexus disconnecting from internet :(

Stock T-Mobile Samsung Galaxy Nexus (CZ)

BTW: After reset device, same problem.

Thank you
Mark

Same issue here, range very low, even next to the router, the signal bars and strength is low. Hoping for a fix soon.

Same problems here. I Wifi is very bad on my Nexus phone.