IssueTracker

I have same issue, but in addition many a time, when I switch on Bluetooth, the WiFi connection drops.

There is in fact an issue with wifi on the Nexus 4.  I've written it up here:

http://things-linux.blogspot.com/2013/01/do-not-write-on-board.html

Thanks... but that is not the same issue...  I can leave wifi on all the time and it will never drop connection.  Even when screen blanks out.  The wifi will only drop when I turn on bluetooth.

The issue with bluetooth killing wifi is a known Android 4.2.1 issue.  Whether or not it is related to other wifi issues has yet to be determined, since the cause of the wifi bug has not been made public.  I have also seen the bluetooth killing wifi bug on My Nexus 4, all I have to do is turn on my paired Plantronics headset.

And for clarity, my wifi doesn't "drop" either.  But after the screen has been blanked for about a minute, it stops communicating.  A simple ping test to your N4 can verify this.  If you turn the screen back on you still see the wifi icon, but it will be greyed out. After a few seconds with the screen on, it will turn blue again (and ping will again reach your device).

Yeah, I had a discussion with a level 2 Google Play support rep.  They said they are aware of the issue and to please be patient for an update.  I think we need to make this more publicly known so that they get on top of it...

My wifi icon is always blue (when bluetooth isn't on, that is)... even after the screen's been off for quite some time and then turn back on.  Still blue...

Thanks for the update.  How did you get to discuss this with a level 2 rep?  Did you call Google Device support and escalate?

Figures.  I've done essentially the same thing trying to track down the wifi sleeping problem.  I've RMA'd two Nexus 4's, and the third one has the identical problem as the other two. It's about time for me to call them back again.

Level one said I could do a warranty replacement, but if they don't find my issue, they would charge me full price for the new Nexus.  Didn't want to risk it...  Just send the update!!!

Interesting!  The reps gave me no problems whatever when I described the problem, said they'd RMA the phone each of the two times I called and described the problem.  In a subsequent follow-up email one of the reps said they'd never heard of the problem, so I sent them my write up (above) as well as this link:  http://code.google.com/p/android/issues/detail?id=40065

I told them they could read all about it there.

I've got this same problem on both of my Nexus 4s and one Nexus 7.

I've experienced the bluetooth bug on my Nexus 4, as well as several problems with WiFi.  However, I thought I'd share a few positives about the phone:  http://things-linux.blogspot.com/2013/01/the-good.html

I just posted about this in issue # 40065 (Comment 422 and 445) and that has been assigned an owner.
hopefully a fix is being cooked and its here soon.

I usually take calls via bluetooth and it is posing a challenge now with constant skips when the WIFI is on. :(

An estimate of when Google will have a fix ready for the N4: http://things-linux.blogspot.com/2013/01/count-down.html

I experience the exact same issue and I have submitted my bug report on Nexus 4 help page.

I am having the same issue. Was given an rma number but told I will receive a refurbished device and if there was no problem found with the phone, I will be charged...


I will be filing a complaint with the BBB. Putting a consumer in this type of position is completely unacceptable.

@16, agree this is unacceptable, especially since Google has finally acknowledged that Android 4.2.1 is the source of the wifi and bluetooth problems, not the Nexus 4 hardware.  See this blog post for details:  http://things-linux.blogspot.com/2013/02/the-natives-are-getting-restless.html

Once there click on the code forum link to see all the feedback there, or you can go directly to the Google developer post acknowledging specific problems: http://code.google.com/p/android/issues/detail?id=40065#c803

I have the exact same issue, wife works until I connect a Bluetooth headset then the WiFi will constantly drop and reconnect.  Making it impossible to use the Bluetooth headset over a WiFi connection.  

[Comment deleted]

I got N4 two days ago and found the same issue which makes it impossible to use skype with a bluetooth headset. Looks like it's been a while. Wondering how long they still need to fix this annoying problem... Or maybe I should just think about return the device?

+1 from me. As soon a phone calk starts over Bluetooth the WiFi connection dies. If I do a VoIP call over WiFi with a BT headset, the call will die because the WiFi connection dies. This is unacceptable for a flagship phone in 2013.

I am seeing something similar as well. Leaving Bluetooth off solves the problem, but isn't exactly an ideal workaround.

Got the same issue. :-(

Same here as well.  

individually they work fine, but it is impossible to use both wifi and bluetooth together.

Just updates my nexus 4 to android 4.2.2 and the problem is still there. Every time you use a Bluetooth headset when WiFi is on, WiFi connection will die.

Exactly same issue. I only found it when I tried to do VOIP using a bluetooth headset and the call won't go through since the WiFi will drop.

I got the latest 4.2.2 and tested and this problem still exists in 4.2.2

Same here, pls fix

Same in my NExus 7 with 4.2.2. waiting for a new release, google?

Took me one day to notice I also have this problem on my 4.2.2 nexus 4. Even in "safe mode" The second a Bluetooth device becomes active WiFi drops out, the bar goes grey or disappears. How can this problem not have more publicity. Any news of a fix on the way would be much appreciated

Fix asap!

Nexus 4 Report Card:  http://things-linux.blogspot.com/2013/02/google-and-nexus-4-users-report.html

I have the same issue in my Nexus 4. This issue is not random. But its there in all Nexus 4 devices and consistent.
@google - please fix this ASAP.

Google, this matter needs attention.

Same here. Pretty useless when used wifi+bluetooth. I am connected through slimport to my TV and BT mouse and keyboard that seems to be working fine but WiFi keeps dropping connection, it just disconnects and does not even see any networks and the, after some time, reconnects. So even a try to watch youTube over wifi while having any BT devices connected is not possible. This needs fix it sucks like this! And we need option to shutoff screen while HDMI connected ... Come on google developers you are working for 100k salary make this happen and fix it.

I have the same issue. But just occasionally. I have the impression that the wifi keeps connected when it's under "heavier" use (e.g. pings from a computer). But if it disconnects from wifi i'm able to reconnect it with just entering the wifi settings screen.
I will try some more in the next time.

Same problem here. Makes using a Bluetooth keyboard while sending emails or browsing website pretty unbearable.

I also have the same problem. Very annoying especially when I am making a call with my Bluetooth headset with wifi killed temporarily, my Nexus 4 keeps trying to reconnect to the wifi and directly makes interruptions to my conversation. I can still bear if there is no wifi when I am making calls with my Bluetooth headset but really cannot tolerate this bug disturbing my conversations. I do not have this issue when I use my Galaxy Nexus with the same Android 4.2.2 version. So I really doubt it is the problem of LG. Hope Google can fix it ASAP.

Same here with 4.2.2 on Nexus 4.  Google! For crying out loud, FIX this bug or else!

For whatever reason, Google has been incapable of fixing this problem, and they certainly do not show any concern over it.  I've decided to move my Nexus 4 over to CynaogneMod, where they at least have a viable, working bug reporting system and a developer team that is hard-working and who provides feedback to their users.  It's not for everyone, because it entails unlocking your phone, rooting it, and flashing a new OS onto it.  But as I said, the CM folks at least have a viable bug tracking system.  

I've written about it here, check it out:  http://things-linux.blogspot.com/2013/03/cyanogenmod.html

I'm having the same issue. I can't stream internet radio from my N4 to my bluetooth speaker, the wifi symbol turns grey and disappears causing the stream to stop.

I have just started getting this issue with no apparent changes in apps or hardware. The only change i can pinpoint is that i'm out of data range for t-mobile (e icon when not on wifi).

Same problem here. Please pay attention and fix ASAP! Not possible to browse the internet while listening to music with my bluethooth headset...

You all can stop wasting your breath yelling at Google, it's been 179 days since this was reported.  Maybe it will be fixed in Key Lime Pie.  But don't hold your breath:  http://things-linux.blogspot.com/2013/03/since-last-post-weve-tried-cyanogenmod.html

Yep, same bug in my nexus 4 with 4.2.2. Google, are you on this?

I also have same problem with nexus 4 dropping WiFi quite frequently while using Bluetooth headset.... Driving me crazy these last few days and the troubleshoot went to the max... Finally I disabled all sorts of options one at a time until I got to turning off Bluetooth.... Ding ding ding WiFi issues went away... Turn it back on with headset and instantly I get WiFi issues.    Bummer.   Definitely affects my daily use.   Thanks for addressing this everyone, and thanks for your time resolving the bug Google.    

Ever since I got my Nexus 4 in January) I have this problem.

As soon as I make a phone call with a Bluetooth Headset connected wifi disconnects and stays disconnected.

Nexus 4.2.2 Stock image. With the Galaxy Nexus everything was working fine.

Google, come on.

It is ridiculous that this bug is listed at priority "medium" -- still here on 4.2.2

Pretty disappointing that after 4+ months this phone has been released we have seen ONE single bug fix OTA while this phone has so many, especially bug fixes for such as basic features like BT + Wifi not working properly.

Google isn't listening or just can't fix it.  Only solution is to notify your favorite tech blog and maybe they'll post something about it.

this is so frustrating, 4.2.2 sort of fixed bt a2dp sound streaming, but my bluetooth gamepad instantly breaks wifi :(

I'm getting the same issue. Bought my Nexus 4 last week and have JB 4.2.2. Bluetooth and WiFi work fine independent of each other. But, they don't seem to play nice together. For me, the problem arises when I try to stream music to my Bose BT speaker. While on WiFi, the connection will go in and out, making it unusable. To be clear, I don't encounter any problems using BT without WiFi. That is, I'm able to steam music via HSPA+ to the speaker without issue. It's only once I turn on WiFi that the connection problems occur.

Google, I left iOS after four years to give Android a fair shake. Please don't disappoint.

[Comment deleted]

Steve's upcoming counseling session:  http://things-linux.blogspot.com/2013/03/steves-upcoming-counseling-session.html 

I have this issue as well.  Just received my N4, and I cannot actively use bt without wifi dropping out, meaning i cannot actively use both connections.  I am on the verge of returning the device, but I'd really rather not.

Still on Nexus 4 (4.2.2) please fix.

Regards

March 2013. I just got two N4. same issue. useless phone in such state. galaxy nexus is flawless with same stock ROM and build. 4.2.2 DOES NOT FIX THE ISSUE. Also it's not caused by third party app. Google stop with the lame excuses. Contacted Google. They never heard of such issue.

Same issue here

I have the same issue with a BT keyboard and mouse too.
Very annoying, please fix!

4.2.2 unboxed.  Same issue.

Let's all call support at the same time at 6pm PST and remind them :).   I went from telling everyone this is the greatest phone to venting about my BT WiFi woes.   Wah

OP Here...

4.2.2 does not solve these issues.  Wifi still breaks when bluetooth is in use.

:(

Let's all call and ask for Steve:  http://things-linux.blogspot.com/2013/03/steves-upcoming-counseling-session.html

I'm also noticing that the Nexus 4 BT doesn't always remember previously paired devices. Sometimes, I'll have to re-initiate the pairing process which can be annoying. I've had this occur on two different speakers. This is leading me to believe the Nexus 4 may have a faulty BT, although don't know if this is a hardware or software problem. Either way, it is ridiculous that we have not heard anything about it. I have to toggle my WiFi off when I want to stream music, which I can do because I have an unlimited mobile data plan, but I have to think this would be a dealbreaker to many other users.

This issue is driving me crazy. I have been using the Nexus 4 since January, and even two android upgrades couldn't fix this bug. It is so annoying to toggle between wifi and bluetooth. To add to the woes off late the 2 finger swipe doesn't respond. This is an intermittent behavior and I have to reboot my mobile to reset this feature.
I am almost embarrassed that I recommended this phone to my friends.
I knew I was compromising on battery life and other hardware issues when I bought the phone but such a shoddy software job by Google is unacceptable.

Give Steve (see above) a call: 1-855-836-3987 to let him know.

FWIW: I just got the Xperia ZL from Sony. It uses the same S4 pro and i assume the same BT chip and this same bug is also present there. As soon as you start using a BT headset wifi dies.

It just buggy drivers that for some reason are never fixed.

@69: That is interesting, it is the first real evidence that the problem is not a hardware issue with the Nexus 4. And yet more evidence of Google's sloppy QA and customer support.

Re. Jonathan - Thank you for sharing the info re. Xperia ZL / Snapdragon S4 chipset having similar issues... this may turn into a product recall it would seem, damn it, I really love the phone besides this hardware problem, soooo annoying!

RE: DJ

It won't be a product recall...it will be a driver fix from Qualcomm. Hopefully sooner than later.

Same issue here. I called Google customer service. They had no idea how to solve the problem and recommended a replacement phone.

RE: clay
How will the driver fix be installed? Manually, or through an OS update?

Possible that one of the custom kernels will implement it before a Google release, but most likely it will be a OS update from Google.

Had the same problem. Returned the phone to my retailer. They sent it to LG (Greece)
LG Greece said they performed "software upgrade" whatever that means.
Problem seems to be solved but will keep an eye on it.
I would recommend trying to contact LG instead of google.

@76: The only thing that could mean is that, if they actually did anything, they installed a new kernel with updated Qualcomm wifi and bluetooth drivers.  Can you actually use wifi and bluetooth at the same time now?  Can you please go to Settings --> About Phone and tell us what it says for Kernel version and Baseband version, and Android version?

Thanks.

false alarm. worked for one day, now problem comes up again.
android is 4.2.2
baseband M9615A-CEFWAMAZM-2.0.1700.48
kernel 3.4.0-perf-g7ce11cd

returning the phone on Monday, they said they would replace it.
let's see

@78: Those are the stock 4.2.2 kernel and baseband.  LG didn't install any new drivers on your phone.

Well I know that now! If I get a replacement I will let you know how that works.

A replacement will not help. It is a driver problem Google is bothering to fix.

So does this happen to ALL nexus 4?

Yes

Yes. All of them - if you have a 2.4 GHz wifi access point.  I've heard that connecting the Nexus 4 to a 5 GHz wifi AP does not have this same issue.  But I don't think I believe it.

Correct. a use of a 5Ghz access point solves the problem but this is not a solution. Not everyone has a dual band access point at home.

Same problem here.
4.2.2
Google, please bother to fix it. This is so annoying.

Same issue on the Nexus 4 I received today paired with a BT250-XT+.  Stock 4.2.2.  It's an issue in that it prevents me from using Google Voice via Internet and use the headset.  It's the curse of living on the edge of cell service, I must have the phone in a cradle in order to have cell service inside the house.
So my two choices are:
1) Turn Wireless off / Bluetooth on/ have phone in cradle.  This is how I have always been even with the prior cellular service provider.
2) Turn Wireless on / Bluetooth off / hold phone in hand.  I can still get/receive calls to my cell via Google voice / Allows me to roam the house on wireless.  Pain in the neck (no pun intended) if I intend to be on the computer while talking.

I must say Google, I may have to hold off chanting praise in your direction until you resolve what is a (simple) core item.  Wifi and Bluetooth are fairly mature features.

The Google remains unconcerned.  Their stock response:  http://things-linux.blogspot.com/2013/01/have-nice-day.html

Got the replacement phone. It did the same thing. I also tried Bluetooth tethering through WiFi and both worked together at the same time. It seems not a hardware bug. Bluetooth headset always kills WiFi connection when in use.

Google, fix the bug please.

Google, Naivete, the Nexus 4, and Little White Corporate Lies: http://things-linux.blogspot.com/2013/04/the-fine-art-of-corporate-fibbing.html

They're lying, they know all about it. Here's an email message that we sent to the Google Press Office, and the Google Board of Directors last January:  http://things-linux.blogspot.com/2013/01/letter-sent-to-google-press-offices.html

Doug, much as I'm sure we all enjoy your blog, this is a bug report and shouldn't be used to drive traffic. You have linked your blog 12 times in this report so far; please stop.

I'm not asking you to stop writing about it. In fact, please do continue to write about it; I have your blog in my RSS feed and I read your posts. However, If you have information to contribute to the bug, please include it directly in the bug tracker instead of repeatedly linking to your blog.

I'm not going to get into a discussion about how terrible Google are at managing these bugs; I think that's pretty much evident to everyone (except Google).

I'll make this my last comment on this topic -- there are other people subscribed to this bug who want to see useful updates rather than my rants about bug tracker etiquette.

P.S. Ctrl-F, "//things" ;)

[Comment deleted]

:)

BTW, it recently came to light, to me, anyhow, that this bug only manifests itself when the N4 is using a 2.4 GHz wifi access point, and not when you are using a 5 GHz one. That sort of screams BLUTOOTH DRIVER BUG to me.

Not, apparently, that anybody on the Google/Qualcomm/dev side of the issue seems to care enough about to investigate, or acknowledge, even.

I've been following this thread for some time now, and quietly waiting to hear more information about possible fixes.

I first ran into this issue using a VOIP and my bluetooth headset. It seems that occasionally, I would stop hearing the person talk and they would stop hearing me talk. After some time (say 4 to 10 seconds), the past 4 to 10 seconds would play back rapidly (like chipmunks talking). Occassionally, it would drop the wifi connection and I'd have to dial back.

My point about this comment is: if there's anyway I can help provide debug information or ideally any logs, let me know.

Re: #99

That sounds like it makes sense. It would also explain the somewhat sporadic nature of it. I sometimes get it on a few different APs (2.4Ghz only), though I've not yet worked out what's the common factor. It could be related to the wifi channel in use, or potentially interference from other nearby wifi APs, even if you aren't connected to them. If that is the issue, that would make it more difficult to tie down, given how saturated the wifi spectrum is in many areas.

[Comment deleted]

Same bug occurs on my end. It is extremely dissapointing because I bought Slimport cable to use my Nexus 4 as a PC (something like Asus Padphone) and while I can use my bluetooth keyboard and mouse I can't use wifi which kind of ruins the whole idea. Why bother adding a Slimport module in a first place?

Well done Google.

Been following these threads (there are about 30 on this bug tracker, tracking similar BT issues) for about 8 weeks now and I keep seeing the same trends:

Google won't take responsibility for the fault. One developer implies it will be fixed in Key Lime Pie.

Now, I would happily wait 6 months for that to happen, perhaps even plumping for an N5, but judging by Googles complete inability to recognise, communicate and fix the issue, I've just ordered a Galaxy S3 for £20 more than an N4. Google have simply failed to instil faith in their competence at fixing this and this is seen among other users on these threads.

So congratulations Google. Your incompetence is now not only losing existing customers, but also potential new ones. Which is a shame because the N4 seems like a great piece of kit, save for this one minor bug (I played on a friends N4).

I'll be unsubscribing from all trackers soon. Come Thursday, I just won't give a shit about the Nexus as a brand anymore.

For reference, I have borrowed an old HTC Wildfire (after my Nokia E5 gave up) and now want to give the phone back and get something a bit quicker. N4 was in the spotlight, but now I've voted with my wallet. 8 weeks is frankly, long enough and in fact, this issue has gone on MUCH longer than this.

I'm not advocating others jump the Nexus ship. Google may well get their act together. But for me personally, I'll be moving into a job role soon where reliability of features on a phone is more important than anything else.

I've been having this issue (and a myriad other bluetooth ones) since I got 2 Nexus 4's in December. My recommendation to my friends has been to get the Nexus 4 only if they don't need BT.

It's disappointing that Google doesn't seem too keen to communicate when or if they plan to fix the issue. My next phone will not be a Nexus. I value working features over broken ones with the promise of future updates.

RE>  #103 crazyman...@gmail.com

well said, and bravo sir... upwards and onwards!

Been experiencing the same since I got my N4, now running 4.2.2. Voice on bluetooth headset (Motorola H720) breaks off when WiFi is on and connected. Wish Google and/or LG addresses this very serious problem.

It turned out there is a compatibility issue between Nexus 4 and my ATT
uverse 2Wire router. I disabled the ATT WIFI and connected my old Netgear
WAP. Bluetooth suddenly works fine. No more WIFI dropping issue when using
Bluetooth. However, this does not rule out the bug in Nexus 4 because
Ipad+2Wire Router+Bluetooth does not have any issue.

@zh, was 2wire 2.4ghz only I assume, and the other was dual 2.4/5.0? I believe it has been said using a 5.0 fixes it, but maybe that isn't the case. In your case, sounds like you found out the same thing.

[Comment deleted]

RE> #108 edwardkn...@gmail.com

Both routers are 2.4GHz only. Mode name for Netgear: WGR614 V5. A pretty old one.

I have a new Nexus 4 and when paired with a Samsung Monte I can't send files: the Nexus asks me to 'confirm' the transfer but there's no button to press to confirm it! I guess this isn't the same problem as the rest of the people here, but maybe it's related in some way. I'm confused.

RE:  #107 zhihez...@gmail.com

THANK YOU!!!  I have UVerse/2Wire - picked up a TTL-WR740N router (dd-wrt compatible) from Amazon for 19.99 - arrived next day - all working :)

Finally I can use my N4 with BT headset to stream MediaMonkey library via UPnP/DLNA without the constant disconnects!!!

good luck to all

The problem has everything to do with the Wifi and BT sharing the same 2.4Ghz Frequencies. I have a Nexus 7 and Nexus 4 and Bluetooth will NOT WORK unless I use the 5Ghz WiFi Connection.  I have a Netgear WNDR3700v2 Dual 2.4/5Ghz Router at home and verified this.  However, it sucks when I am at work all day because I primarily use VOIP and Google Calls and Skype and can't use my BT headset. Maybe Google just can't fix it because of the design...

Re 2.4 GHz compatibility.   The 740n router I mentioned earlier is only 2.4 GHz and it works fine.    If I had the time I would go through every granular setting to see where it breaks.   Some day.  Some day.  

[Comment deleted]

Confirmed... No further intermittent WiFi disconnections while using a Bluetooth mouse when the WiFi is changed to 5GHz.

But we don't all have dual band routers.

Anyway, I'd like to point out that you don't need to connect a device - merely turning on Bluetooth for a few seconds at a stretch when WiFi is connected (even if you don't have a device paired) results in the same problem.

Yes I find the same issue tonight, when I'm using the bluetooth keyboard to typing.
My mobile is Nexus4 with the 4.2.2.
Could you resolve the urgent issue as soon as possible?

Same problem here, it is extremely annoying. My wifi drops and reconnects every 30 seconds or so when bluetooth is connected and in use. My nexus4 also has much lower data and voice signal on tmobile network compared to my previous phone. Whether this is a nexus problem or an android problem Google has to fix it as there are network problems all the way around.

I also have the same issue when using a bluetooth mouse while connected to my 2.4 GHz wireless N. The connection is either unusable slow or drops out completely, cellular data works fine.

Its pretty simple. Not only the nexus has this problem. My note 2 and htc one x have the same problem. The big problem is that wifi and bluetooth are transmitted and received by the same hardware. For some reason the bluetooth and wifi together isdisrupting eachother badly making the wifi to drop totally. I dont think there is a fix for this... except for making different hardware for both wifi and bluetooth. Devices get smaller and smaller so to preserve space stupid choices are made often.. its to bad... but i think we have to live with them.

Same issue.  upgraded to verizon samsung S4 over the weekend, streaming music to my bluetooth speakers like have I have been for 2 years with my old phone, WIFI corrupted after 20 minutes.  Had to get my old phone back out.  Crazy and disappointing.  So it is not simply the spectrum contention, as my 2 year old Droid Bionic works fine...but it's not on Android 4.2.2

I think i have the same problem on my two Nexus 4 16G 4.2.2.
Wifi + Bluetooth tends to broke wifi connexion.
Please fix it in next release.

samsung s3 have the same issue

I seem to have had this issue as well. But only occasionally and only seems to be when streaming video over WiFi. Using just 2.4Ghz band (on BT Home Hub 3). I've been able to stream music (eg. Google Play Music) and listen using my Bluetooth headset and browse web pages over WiFi without issue.

With an active Bluetooth connection I have not noticed the WiFi signal drop - the icon has remained blue and active. Although the WiFi icon has often been hidden when watching full screen video.

However, trying to stream video (eg. watching live TV with TVCatchup or BBC iPlayer) and the audio/video would stutter until it would eventually freeze entirely. Turning off the Bluetooth headset resolves the audio and video playback.

HOWEVER, it is currently (and rather suddenly) working perfectly! (I'm watching TVCatchup and listening on my Bluetooth headset). Earlier this evening it didn't work and I have changed nothing. There are often neighbouring WiFi networks that are barely in range - could this be an issue?!

Stock Nexus 4, Android 4.2.2

The issue only arises when actively using both WiFi and Bluetooth, so, for example, listening to play music with Bluetooth without issues probably just means it already had it in its temporary cache. It caches alot on its own, not just when you explicitly tell it. Loading a page while using a browser is the only time that it may be interrupted when browsing. As long as it isn't extended use, like watching a YouTube video in the browser app, you shouldn't have the issue. TV catch up may buffer quickly or something, or it let's you grab the whole episode to your device. No idea. Being in USofA, can't test that part. Really wish the problem will see a fix in the next month or 2 via 4.3/5.0/etc., whatever they'll call it. Its hurting massive markets by affecting huge flagships. Here's hoping...

this is quite a big problem, I have a 3G wifi router in my car so that I can check email and calendar or traffic situations while on the phone.  This bug makes that wifi router useless while it worked excellent with my Galaxy Nexus.  I was not expecting this kind of thing from a Nexus phone or I'd expect such a major bug would be dealt with in weeks not months.

same problem with my Nexus4 rev11 (Android 4.2.2)

Have the same problem with my Nexus 4 stock 4.2.2, hope Google wakes up and fixes the issue.

Can you please fix this issue?? it is really annoying~~~!!!

This must be fixed, incredibly silly useless bug

Found my way to this bug report within 30 mins of unboxing my new Nexus 4. Very disappointing.

Looks like it is not only a nexus4 problem, other android devices have same problem.

Found my error just as fast...have returned the nexus 4 twice so far, neither time has fixed it.  I believe they are putting an previous version of Android OS on it this time, thinking that 4.2.2 just won't work with bluetooth and wifi at the same time.  And after all this time, no word from anyone on when it might be fixed.  I thought google was better than this.

HTC One S on Android 4.1.1 have this issue too...

I am new to galaxy mobile and surprised to see that this is very basic and needed feature from any user and how come google is not capable of fixing it. I will stop recommending/buying galaxy phone now onwards...

This is so lame.

How long has it been since Nexus 4 has been released? Like ... 8 months or something? And how long since this bug has been reported here? Six months... ? And there is still no at least remotely official response from Google at all? Are you kidding me? What kind of joke is that?

From now on, Google, please put a large sticker over all you Nexus stuff that says: "This device can not handle simultaneous wifi and blootooth connections!" It is completely ridiculous that you are selling these phones/tablets/etc/... while knowing that there is this serious issue and intentionally hiding that from your customers! I would not be surprised if you will face a large lawsuit for that.

Google has repeatedly proven that it absolutely does not care about its customers. Its managers are apparently only interested in selling their stuff, forcing people to use their services and filling every application with their ads. Some bletooth/wifi compatibility, however critical it might be, is apparently on the absolute end of their priority list. What a shame.

Google may, or may not fix this problem with the 4.3 release.  If not, then Google may, or may not fix this problem in the Key Lime Pie release.

On a plus (maybe), it looks like someone from Android (I hope) has looked at the issue and added some labels.  Comment #137.  That's good.... I guess...

As an addendum, Google might, or might not have fixed this problem in 4.2.2.  And, they might, or might not have fixed it in 4.2.3.

We're beginning to see a pattern here.

The same issue as described I encounter on my Nexus 4 with Jawbone Era and Blueant Q2.
Customer support informed the that google is working on to fix the issue.