IssueTracker

Have this issue and modifying the cfg file solved issue.

Best way to identify this issue will be to stream music on Radio Apps like TuneIn or Pandora where the music cuts out exactly at sleep time.

Example : Display Sleep time set to Lock time to 30 sec and then Display Sleep time to 1 mins, the Wifi breaks at 1 mins.
This has something to do with the Sleep time.

Also, as long as the phone is unlocked or in use, the wi fi doesn't break.

Nexus 4 with 4.2.1.

Thanks
Avik

@2 It sounds as if you simply have set your wifi to turn off when the screen turns off.  Have you checked your settings in "advanced wifi settings"?  The ARP issue is does not manifest itself simply by turning your screen off.  Streaming would certainly just continue even with the issue present when you lock your device.  

Hello,

Thanks for your insights. But this is not the case.
The setting says keep the Wi Fi alive.

The way I see it, the code never receives the instruction to keep the Wifi alive even when the display goes to sleep.

The streaming is interrupted because the Wi Fi drops and starts again. This indicates there is a problem with the code. Changing Router settings is not an option.

I can tweak the phone codes myself but then I want Google to wake up.

It is a pure mismatch of understanding user requirement and finalizing technical specifications. It happens all the time in softwares.

The end users want Wi Fi to be alive even when the Display is on Sleep.
But in 4.2.1, the Sleep setting puts the Wi Fi on sleep too.

You will not observe this problem if you keep the phone awake. The Wi Fi works flawlessly.

I believe it can be fixed.

So far, there are 5 friends of mine who have taken the N4 and all of them have the same problem.

@4 Thanks for explanation.  From your own words, I still see what you're seeing as an entirely different issue.  Even with the issue being discussed in the bug report here, the device maintains an active connection with the router at some level, whereas with you, it seems that the entire connection (read: all ports and communication with the router) becomes inactive when you turn the screen off.  Almost sounds like a hardware issue of some sort rather than the device not responding to broadcast/multicast requests.  

In any case, back to the topic, I can confirm this issue.  The fix presented in the OP restores broadcast responses from the device.  However, it can be noted that reserving a static IP at the router negates the need for requests and replies as far GMail services go, so I have chosen to keep the wifi INI at its default values, allowing Gmail to operate as it should (receving emails instantly).  But, I still run the risk of various other services not working as expected in the future if the device cannot respond accordingly to broadcast/multicast requests.  

Hey, this is being fixed in the Qualcomm driver to support ARP offload when filtering broadcast packets

Thanks, I thought as much as I've been following 40065

Cheers :)

same issue here. Wifi fails to respond when the device sleep. please provide a solution for same.

Also these are the issue I got:
1. Wifi worked fine at home, whereas the same didnt work at my office network. I had HTC Desire S previously and didnt face any problem both at Office and home.

I have this issue, so says isher in 40065, I can't modify that config file I presume because I am not rooted.  What are my options, would buying a new router help?  Is there a whitelist of good routers?  It's there an eta on Qualcomm fix and can it be delivered ota?

Thanks.  I do not want to root my phone, that is not an option for me.

A current workaround for this is to add a static ARP entry on your router (if it supports it). Unfortunately, No ETA yet on the qualcomm fix but it will go out at some point.

@isher - I  was able to add a static ARP in my dd-wrt router.  After router reboot, I set the phone down for an hour.  When I pick it up after the hour the problem is back.  Both the wifi and cell bars are full and blue but there is no internet, the emails I can see on my computer are not received on the nexus 4 and chrome will not load a web page.  Do I belong back on 40065 and what other advice can you offer?

Startup command for reference: arp -i br0 -s 192.168.1.254 FF:FF:FF:FF:FF:FF

More information -  I reproduced this on a second Nexus 4, the first runs 4.2.1 the second one runs 4.2.  Once the problem starts toggling airplane mode will not fix it.  Turning off WiFi forcing cellular data does fix it.  Turn wifo back on, you get blue wifi bars but still no internet.

@tantdy, I suspect that your problem is not related to this issue of ARP broadcast requests, as the symptoms of your problem are not consistent with what others report, nor with my experiences.  Could be an entirely different bug or a finicky wifi connection, an over taxed router, TCP timeouts, or any variety of bugs.  

But, instead of setting a static ARP using a command, why don't you just reserve a static IP address on your router?  In so doing, it appears that a static ARP is also created and it has allowed me to sidestep the problem a dd-wrt router.

@tantdyalf, appears you are not hit by ARP, can you let know what your current WMM & APSD settings on thte router are ?

You could try changing these to see if it makes a difference

Thank @rsry, I added a static IP, won't be home long enough to test for a while but will get back to you if that works.

@isher -

Wireless Multimedia Support Settings -

WMM Support Enable (Default: Enable)
No-Acknowledgement Disable (Default: Disable)

(Both are on default, which do you suggest changing)

ASPD:

Can't find this setting, also mostly striking out searching for it on internet with respect to dd-wrt routers, looks like it is associated with WMM, but its not listed under Wireless > Advanced Settings.

I did change last night to WEP2 / AES by the way, that doesn't seem to have changed behavior at all.  I look forward to your next suggestion.

APSD is automatic power save. You can probably find a setting called power save may be.

Also, You could try disabling WMM to see if it helps

Some routers support "proxy arp" where the router will answer ARPs on behalf of the phone. This may provide a router-based solution util the patch goes live. Of course this won't help when you;re not home but trying to use a hostspot you can't control.
So maybe the best solution is still to use the patches provided on xda-dev, still not sure about battery impact since the phone will now process every broadcast and multicast, so it could be a lot more processing in busy environments (university, coffee shop....)

isher, how do you/Qualcomm intend to deal with high broadcast/multicast traffic? are we going to see poor battery life when Wi-Fi is on, or does the Qualcom offer MAC/chip level filtering that will not wake the entire phone?

@19 isher said Qualcomm are releasing a driver which will support ARP offload, offload I assume means on the WLAN chip so there should be no/immeasurable battery impact.

Actually since oyu mention ARP offload, it implies it would be handled on-chip, not wake up the phone, so sounds like the right fix.

ARP offload will allow the WLAN chip to respond to ARP requests without waking the host up

I tested a static IP (and verified the phone had it) as well as disabled WMM at the router overnight.  The problem still exists.  What are my next steps isher?

[Comment deleted]

@isher What else should I try?  If you don't have any other ideas could you help me get a RMA for this device?

@25 This is not a support forum. If you don't like it take the phone back, otherwise be patient until an OTA fixes the bug.

@26:  Given that it took nearly two months to even get Google to acknowledge this particular Nexus 4 bug, and given that this bug report and others related to the Nexus 4 have been active since as far back as November 20th, 2012, and given that the Google developers have given absolutely no indication that the source of the multiple wifi and bluetooth problems with the Nexus 4 (Issue 36949180, Issue 36949180 to name just two of them besides this issue), much less indicating any time of estimated time to fix, I believe #25's request for assistance regarding RMA'ing his Nexus 4 was perfectly reasonable.  

@25: Here is the number for Google Device Support.  They can help you with your RMA request: 1-855-836-3987

For the rest of you with faulty, buggy Nexus 4 phones, you can read all about one person's experiences here: http://things-linux.blogspot.com/

@tantdyalf, Is the version of DD-WRT for your router the latest available one ?

@isher it does appear to be so, when I check the router database at dd-wrt it has the version I am running as the most recent for my router (Asus RT-N13U -- build 14896).

@jbriz sorry you were bothered by my request, if you have any suggestions for me to troubleshoot or contribute towards a solution I am happy to.  If you know of a pending OTA that I should be patient for I would be open to not returning my device that is past the 15 day return window.

all who are working on this issue--thank you

@29 Sorry if I came across a bit abrupt, I meant no offence. I just didn't want you to come here expecting support, then not receive any, just because this is a bug tracker so people don't usually come here looking to help others.

I'm confident the issue will get fixed within the next few OTAs because #6 says it's being fixed in the driver, but who knows when they will be. It is affecting me too, but not very often so it's not too bothersome.

Thanks @tantdyalf, This is being internally tracked with Qualcomm.

When is the fix coming? There are massive delays in email coming through and my nexus 4 keeps going missing when trying to do wifi sync on winamp and spotify. Please fix.

So, in the 4.2.2 update the new driver wasn't included because the problem still exists! When will this bug finally been fixed?

The driver fix did not make it to 4.2.2 release

@isher: An estimate, please, of when it will.  

Unfortunately, the time frame of next update is not clear at this point

@isher: Can you indicate, even, whether there will be an update to fix this issue?

For what its worth the Play Store gave me an RMA for my device that was well past the 15 day return window (months past), I have to wait 21 days to see if I get my refund, but I expect I will.  If this issue gets fixed I'll come back to the Nexus 4, other than this issue I thought it was great.  But this issue made the device impractical for me.

@38: I am in exactly the same situation.  Either this issue gets fixed, or the phone goes back.

> The driver fix did not make it to 4.2.2 release

This is unacceptable. egg on your face Google.
The N4 is the last Google device I buy on release.

In the meantime hopefully someone will come up with a 3rd party ROM that fixes it. Google Wallet will complain that my phone is rooted, but I'd rather have working wireless.

[Comment deleted]

I did not expect this from company like Google.. my God - wifi is the main feature!  Big disappointment. Its shame... :(  

@isher:  Specific question, please answer: Does changing the status to "FutureRelease" mean that this particular bug will be fixed?

@44: what if the answer is "yes"? how does that help you?

It'd be nice if this thread was more about technicals and less about rants. Nobody's happy with the current status of this issue. I don't think someone at Google's headquarters is sitting now rubbing their hands with pleasure whispering "we showed them. Ha ha". Granted, the Nexus 4 launch was far from being perfect but all of these rants around here sound more like coming from a pile of crybabies.

[Comment deleted]

@45: It would help me to get an answer.  If the answer is "Yes", then I may keep the phone.  If either there is no answer, or the answer is "No", then I'm sending it back.  It's that simple.

So yes, I want an answer.  No rant involved in the process.

From other sources, btw, I gather that the delay in getting a fixed version of the Qualcomm driver out to the Nexus 4 has nothing to do with technical issues, but rather legal issues that are keeping Qualcomm from giving up their code to be distributed as AOSP.

Which, since you seem to want one, is reason enough for a rant.  I purchased a product from Google that was defective, when Google knew it was defective.  That's bullshit.

@47, then it'd be more appropriate to ask "when will it be fixed" (which has been asked here before), rather than asking, generally, whether it'll be fixed in the future. Besides, from my experience with the software world, usually "FutureRelease" means that the bug is acknowledged, and is *intended* to be fixed, just not sure exactly when. The uncertainty with respect to timing may have something to do with the fact that the fix is done by an third party (Qualcomm), so third party's interests/priorities are involved as well.

@49: "usually means" isn't good enough. We want a definite yes or no answer.  Is that asking too much?

And if you read back up the comment list a bit, you will see that I already did ask when it would be fixed, and the answer was "we don't know", hence the follow-on question.

And by the way, 49: who put you in charge of determining what constitutes an "appropriate" question?

The question still stands, isher: will the buggy wifi driver be fixed, and be pushed out to Nexus 4 owners?

@50, I did read up the comment chain. So, to summarize: yes, the bug is acknowledged. Yes, it will be fixed in the future (concluded from "FutureRelease". That's how we tag issues that are targeted for future, timing-unknown, release). So it's up to you whether you maintain patience or return the product. I'm OK with assuming that "FutureRelease" means "Will be fixed in a future release" - it's up to you as a consumer to decide whether it's good enough for you.

But the thing is that there's absolutely no point in ranting over it over and over again in *THIS* forum. That would answer your "who put you in charge" comment. Appropriateness is a matter of context. In other words: rants - go for it, but please, *elsewhere*. This is an issue tracker, not Hyde Park.

[Comment deleted]

Interesting perspective, 53.  But unless I'm mistaken, it was you who took us to Hyde Park by calling other posters "crybabies".  

Kettle, meet pot.  Karma's a bitch, it'll catch up to you almost every time.

As to your faith in "FutureRelease": over on  Issue 36949180  Isher, in comment 535, January 14, promised us all that the Qualcomm bug would be fixed in "the next release", which turned out to be 4.2.2.

Guess what: the buggy driver is still with us, so pardon me if I don't put the same faith into "FutureRelease" that you do.

I'm beginning to suspect that you either are a contributor to the Android code base, or are a Google employee; otherwise I can't see why you are willing to spend so much energy apologizing for them.

They *did* have time to include a "fix" that prevents LTE from being activated from the service menu.
Nice to know where the priorities lie!

[Comment deleted]

It appears that my first guess was correct.  Our name-calling, comment-moderating, pot-calling-the-kettle-black (referring to you, #53) commenter is in fact a Google-oriented developer of some sort, according to his code.google.com user page. I'm guessing Android is his flavor, but it could be anything, really. C++ perhaps. Or java. Or javascript. Or Go.

So Isaac, interesting to meet you, especially since we have so much in common, what with me also being a developer, blogger, and writer. Just not for Google, in my case.

Oh, and by the way, pardon my taking up some of the precious bandwidth in *THIS* forum (emphasis yours), but the bug has been tracked, acknowledged, and most importantly, not fixed.  The only bit of additional useful information that anyone could hope to see here is a statement by a Google representative indicating that the problem had been fixed, and that a release was in progress.

So in the meantime: blogger-to-blogger, let me just say that I've been following this particular bug since November 20, which is when the Issue 36949180 bug thread was initiated.  In fact, I have been blogging about it nearly daily since December, 2012, which is when my first (of what ultimately turned out to be four) Nexus 4 phones arrived.

The experience of Nexus 4 ownership has been fascinating, to say the least.  Fascinating enough that I shared part of that experience with this article that was published in Linux Today a little while ago:  http://things-linux.blogspot.com/2013/01/has-google-become-institution-bound.html

Since then, I've written about this particular bug a number of times. One post was even devoted to the topic of Goggle continuing to sell the Nexus 4 with full knowledge that it was defective: http://things-linux.blogspot.com/2013/02/what-is-evil.html

I will have to confess that I am not totally, or even partially surprised that the Nexus 4 is still being sold today after the 4.2.2 release with the buggy Qualcomm wifi driver still installed. After all, I've had over three months to experience the massive indifference that Google has manifested towards getting this bug fixed. Speaking of Google's massive indifference: http://things-linux.blogspot.com/2013/02/massive-indifferent-brooding-silence.html

In fact, I may even be sufficiently fascinated by the Google / Nexus 4 experience to hang on to this, my 4th Nexus 4, to continue to write about its buggy wifi and bluetooth behaviours until such time, if ever, that they finally get fixed.  Or until such time that Google determines that they can't fix the phone and decide to abandon it instead.

Cheers, and enjoy your cool, drizzly weather up there in Vancouver.

--Doug

First bluetooth fiasco with missing MP3-tags( please star: http://code.google.com/p/android/issues/detail?id=48321&sort=-id&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars)
and now this. What the heck are you guys at google smoking? Every elementary feature a modern smartphone has or should have is not working on this phone. It's called smartphone for a reason! I'm so pissed and I doubt I will keep this phone for a long time.

@58, answer quick: what's my favourite coffee joint?

Look, I'm happy (and, must say, flattered and creeped-out at precisely the same time) that you took the time to research my background.

That aside: there are virtually dozens of forums dedicated for discussing Android. Some of those are sampled/monitored by Google people. Therefore, it follows that this particular site is not the only way to get Google's attention.

I am not saying that the situation doesn't suck - it does. I am not refuting any of the references you provided. But this is not the point. The point is that ranting in this particular forum isn't going to help anybody. It's not going to help get the issue delivered to our phones sooner. Do you really think that people in Google count the number of rants here and prioritize bugfixes according to the rant count?

The only effect that rants carry in this forum is the repeated alerts that people, who had starred this issue, keep getting whenever someone threatens to return their phone. (Of course, they get those alerts pushed to their phones after a significant delay, when WiFi is on and the phone is asleep)

So, yes. Within the context of this particular website, comments such as "Egg on your face, Google" and other non-technical rants and threats are not much more than noise. It does very little more than raise antagonism within other readers here that actually *do* want to help, including Google employees.

All indications show that the bug has been acknowledged. It's not about people not knowing how to fix it, but rather about release schedules and other factors (such as legal issues) - *NONE* of which can be affected by rants in this forum. Perhaps a group action of some sort would help. Ranting here won't.

(I don't work for Google - never have)

[Comment deleted]

I'll satisfy myself with just eliminating the obvious, Isaac (presuming we know each other well enough by now to be on a first name basis): Starbucks is probably not it.

Back on-topic: since the  Issue 36949180  thread has been closed, it turns out that this forum is the only avenue of feedback available to us Nexus 4 stuckees who wish to try to urge the massive, indifferent Google to fix the Nexus 4's broken wifi, and the related Nexus 4 wifi-killing bluetooth problems.  

If you call the Google Device Support Team's support number, you will be told that there are no known issues with the Nexus 4, but that they'd be happy to let you exchange it for another Nexus 4 that will also have no known issues.  Don't believe me?  Try it yourself: 1-855-836-3987.  I believe that number will work from Canada as well.

The point being, of course, that if there was a viable product feedback channel to Google, we'd all be using it. There isn't.

Although I confess to having emailed a couple of my more pointed blog posts regarding the Nexus 4 to press@google.com, and also to directors@google.com, the email address for Google's Board of Directors. Imagine a gnat flying around an elephant's ass, and you have a close approximation of the effect those messages had.

Oh, and I also sent a politely-worded personal message to Larry Page via g+. Ibid.

So in summary, in lieu of a working feedback channel, the poor, put-upon Google developers will just have to suck it up and absorb all the rants that come their way.

After first turning on the screens of their respective Nexus 4 phones, as you note.

Cheers,

--Doug

(Google offered to try to hire me once.  I declined.)

Here you go, Google devs, just in case no one told you about the fun bluetooth wifi interaction on the Nexus 4.  I never was able to get anyone to confirm if this behavior is related to the buggy Qualcomm wifi driver, or if it is something else.  I just updated my Nexus 4 OTA to 4.2.2, and bluetooth still kills wifi.

http://things-linux.blogspot.com/2013/02/very-little-surprise-here.html

@63 your blog reads like you are a spoiled 12 year old child. Yes, we know you are pissed, yes, the bug affects everyone else and we're pissed too. But we don't need to get 50 emails every day because you're ranting about it ON A BUG TRACKER.

Send the phone back for all we care, or a the very least leave the ranting to your blog.

Can a google dev change it so that only comments from project members generates an email?

64 dude, chill.  We get it that Google doesn't care.  Believe me we get it. Google's indifference to the customer is massive.  It is epic. It is, well, Google world class.

It is, if I may, an Epic Fail...  http://things-linux.blogspot.com/2013/02/epic-fail.html

But seriously, chill. Getting that worked up is seriously bad for you.

@65, You know, it didn't think it was possible for Google to be any more insulated from customer feedback, but I think you've thought of a way.  Congratulations!  Points for ingenuity!

Don't listen to customer feedback. That's the ticket!

Err, you can still spill your drivel on here, just everyone who has starred this issue won't have their inboxes filled with it.

There is actually an official forum for Google-related customer feedback and discussion. Here's the thread related to this issue, and it actually has a Google employee monitoring: https://productforums.google.com/forum/#!msg/mobile/SQH6JnIFYcQ/fnJRtgd1EYMJ

As mentioned before, this isn't a forum, or a place for customer support; it's a bug tracker, plain and simple. Anyone here who claims to be a developer should know what that is and what it's used for. The latest discussion here is highly inappropriate for a bug tracker.

Thanks for pointing out that forum.  Here's another devoted to this same topic: https://productforums.google.com/forum/#!category-topic/mobile/android-devices/Y33mbUPrbsU%5B1-25-false%5D

The problem with these Google forums is they are one-way communication channels.  Product complaints go in, but no responses from Google ever come out.

Would you care to point out the value of that?

Thanks for spreading the word, guys.  Maybe your management will finally start to look at improving your working environment.  Changing things around so that you have some chance to be responsive instead of just reactive.  And not very effectively, at that.

But probably not.

http://things-linux.blogspot.com/2013/02/stealthy.html

I have to say, unfortunately, I might have to RMA this phone if the wifi bug begins to affect me. I haven't noticed it until now, but perhaps I've been ignorant somewhat. However I too suffer from it, and I've now noticed there is a delay when receiving messages, if it begins to really irritate me, this is going back and I will demand a refund because this isn't what I paid for. Google have a perfectly good OTA system which they prefer not to utilize unlike every other manufacturer with a working OTA (I'm thinking a big half eaten fruit here!)

How disappointing. Great phone, broken software.

Good point, 72.  Google has known about wifi bug since November 20 last year (in case all you experts tracking this bug didn't know that).  That was 87 days ago.  Why has the fix not been pushed out?  I mean, granted, we'd all have to unblank our Nexus 4  screens to get all those ARP packets flowing again, but heck, I'm willing to do my part.

And before all you geniuses start bitching again about daring to ask a question like that on a bug tracking forum, let's all stop and consider the following: what good is it having a bug tracking forum if bugs get reported over and over again, but never get fixed? Might as well save everybody a whole bunch of time, admit that you can't, or are not going to fix the bug, and just move on to something more productive. Which would be just about anything else.

For pity's sake, fix it.

#73, I'm with you on that.

It's a shame and disgrace, the way Google handles those bugs. At least be transparent, communicate and ack that the bug exists and let us have a schedule for a fix!

And yes, *THAT* is what a bug tracking service is for.

We're talking about the #1 basic functionality for a smartphone. That, together with the BT bug and how contacts don't sync well - render this phone an amazingly-low-priced joke. Damn it.

See what happens when you get all bitchy and snippy, developers?  Customers (yes that's US) who are fed up with the vendor (that's YOU) begin to snip back.

Rather than getting all huffy with us nasty irritating, whiny complainy customers, you might consider getting up off your collective asses and just fix wifi on the Nexus 4.  And once you've done that, if the problem of bluetooth killing wifi still exists on the Nexus 4, then we'd be really *really* obliged if you fixed that one as well.  Unless that one is a hardware problem. In which case you'd basically be screwed.

Personally, I'm having a hard time believing that a hosed wifi driver could let the bluetooth radio reach out and kill the wifi radio whenever they are both being used at the same time, but I guess it's possible.

Not sure where you guys work that bug trackers are also used for release schedule announcements. They've acknowledged the existence of the issue and said they're working on a fix. The bug report has served its purpose. I don't understand why you guys think complaining about lack of communication here would do any good. The bug has been closed and owner removed, that means Google will not see any of this. The place to lodge your complaints is on the product forums that I linked earlier.

It's real easy to explain, 77: We're not satisfied that after 87 days, the only response we get from Google is "FutureRelease".

No indication of when.

No explanation of what.

No explanation of why.

The "take it or leave it" attitude is insufficient.

And as I've mentioned before here: the Google product forums are simply honey traps set up for people to vent.  Google never provides any feedback there. Posting anything on those forums is a waste of time.

Actually, I might have to take that last part about the Google forums being worthless back.  Someone just posted an interesting alternative to being tied to the whims (and incompetence) of that crack Google support infrastructure:

http://www.pcpro.co.uk/news/380008/ubuntu-for-phones-to-arrive-next-week-on-nexus-4

Will most certainly check this out.

Guys, as a temp workaround, follow this thread:
http://forum.xda-developers.com/showthread.php?t=2072930

Hi,

I just noticed that Wifi connectivity went very bad on 4.2.2 JB update.
At 4.2.1 i didnt noticed any issues connecting to home router either on 2.4Ghz or 5Ghz.

After update (clean stock, no mods, no tweaks) i cant use wifi without setting static IP on my phone (looks like DHCP issue)

Anyone know any fix for this instead of setting static IP?

Adam

For your entertainment, since the Google devs have closed this one out: http://things-linux.blogspot.com/2013/02/google-and-nexus-4-users-report.html

when i update to 4.2.2 i have this problem, wifi goes to sleep

Updated to 4.2.2 and stopped recieving push notifications like whatssap, wifi seems to sleep after a while and stop reciving data till screen is on

Hope you can fix this as soon as possible with an OTA, because is really annoying

I have exactly the same situation as the one described above. Really annoying!

Just one question: Why is this thread closed? Is this normal for a known bug?

@86: It is against Google's policy to share any information with its customers. Information, like for example, when this bug will be fixed.

A side effect of this bug for developers using ADB through WiFi, is that any session on the phone using adb shell will freeze when the screen goes off and is responsive again when the screen is on.

Same problem here.

Breaks the phone, in my opinion. Needs a fix urgently.

Please FIX this bug ASAP

Instead of everyone complaining why dont all developers try diagnosing the problem? Like the previous entropy issue? Just a suggestion as itll get fixed much quicker

The problem is one of the wifi chip's manufacturer, who hasn't supplied Google with an updated version to allow for offloading of ARP requests, as mentioned here.  You can fix it with a simple edit to one of the files, which requires root access, but this will require more CPU cycles and more power.  That's why Google apparently decided to shut if off by disabling requests.

I meant an updated version of the driver in my above post.  And surely, there's no source code for it, otherwise the devs would have gotten their hands on it long ago.

Maybe it's time for us, the consumers, to apply pressure on the WiFi chip manufacturer (Qualcomm I believe), even though they're almost the only game in town now that TI is folding, so they may laugh at threats to stop purchasing phones equipped with Qualcomm WiFi chips. Still wouldn't hurt. Send to their CEO, their relations people and copy any press of your choice. Heck copy Google too.

Here are two email addresses that I have used in the past to encourage Google to take more proactive measures in getting this particular Nexus 4 issue fixed:

press@google.com - The Google press office, and
directors@google.com - The Google Board of Directors

The more mail they receive, the more likely we will see action on this.

Just contact engadget, gizmodo, crunchgear and other sites, and let them know of this huge problem. It will make a difference.

@92, I did root my N4 and applied the patch to the Qualcomm wifi init file to tell the driver to not filter multicast or broadcast traffic when the phone was in suspend.  It helps, but it does not completely fix the problem, as the phone takes a couple of seconds to respond to ARP requests while the screen is off.

But it helps.  What astonishes me is that Google did not even include this trivial one-character fix in the 4.2.2 update for the Nexus 4.  Something within Google's support infrastructure is very badly broken.

@96: You, and others are welcome use any of the recent material on my Things Linux blog when contacting those tech sites you mentioned.  This blog has been devoted almost entirely since last December to this and one other related bluetooth problem on the Nexus 4. My suggestion is to use this particular post when contacting those sites:

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

There are other posts that you might consider using as well.  This one gives a detailed account of the Google support experience that I had after first discovering the ARP wifi bug:

http://things-linux.blogspot.com/2013/01/time-frame-of-nexus-4-wifi-bug-issues.html

Finally, this one addresses the broader issue of Google's lack of responsiveness to customer complaints, in particular complaints about Android bugs and bugs that affect the Nexus 4.  It was published in Linux Journal a month or so ago:

http://things-linux.blogspot.com/2013/01/has-google-become-institution-bound.html

For everybody currently reading this particular bug forum who, like myself, has wondered if Google is even aware of the severity of the Nexus 4 wifi and bluetooth deficiencies, let me share that somebody inside Google is at least reading this particular thread.  Someone at Google came to the Things Linux blog and read the three recommended posts listed above minutes after I posted comment #98. I'm guessing the visitor was probably just some technical staff member who, like us, is fascinated by how badly Google has handled the Nexus 4 product issues, rather than a manager with any capability or interest in actually fixing things.

Here's their visit:

Page Views:
3
Entry Page Time:
20 Feb 2013 09:44:27
Visit Length:
4 seconds
Browser:
Chrome 26.0
OS:
Linux
Resolution:
2560x1600
       
Total Visits:
1
Location:
Mountain View, California, United States
IP Address:
Google (216.239.45.93) [Label IP Address]
Referring URL:
(No referring link)
Entry Page:
 things-linux.blogspot.com/2013/01/time-frame-of-nexus-4-wifi-bug-issues.html
Exit Page:
 things-linux.blogspot.com/2013/02/google-and-nexus-4-users-report.html

Nexus 4, day 93 since this bug first showed up over on Issue 36949180.  Oh, and it's still not fixed.  Neither is the issue of bluetooth killing wifi. Keep up the good work, boys & girls.

we need a fix fot this soon!

The "google"´s smartfone nexus 4 cant stay w/o reciving push notifications ....

please fix this issues ASAP google..
so annoying a smartphone can not receive push notification with wifi and screen off..

http://www.xda-developers.com/android/receive-notifications-more-quickly-thanks-to-push-notifications-fixer/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+xda-developers%2FShsH+%28xda-developers%29

Here's potentially the best fix yet. Just popped up on XDA. Haven't needed to try this, but it sounds promising.

I have the same probleme here.

please fix it

96 days, and counting:  http://things-linux.blogspot.com/2013/02/96-days-and-counting.html

any news about a fix?

fix it please!

come on... a 4 cores mobile phone and cant even recieve whatsup notifications at time?

we need a fix now, cant wait 3 months to solve this issue

You should fix this asap.

Whats happening mi notificatios i recive it very late. We need and Ota that fix this problem

Fix-It-Felix !!!!

please fix it

I have a Nexus 4. Connected to wifi worked perfectly notifications with Android 4.2.1

Since I upgraded to 4.2.2 or fail notifications or tardy.

Google please, fix that annoying bug

another day and the problem persists.....

WE NEED A FIX!!

Same issue in Nexus 4 with 4.2.2:

ping 192.168.1.7
PING 192.168.1.7 (192.168.1.7): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
Request timeout for icmp_seq 4
ping: sendto: Host is down
Request timeout for icmp_seq 5
ping: sendto: Host is down
Request timeout for icmp_seq 6
ping: sendto: Host is down
Request timeout for icmp_seq 7

Fix it please!!!!

fix it please

Tras actualización 4.2.2 , notificaciones instantaneas tipo whasapp no funciona, patético Google.
Arreglarlo ya

Fix it please!

4.2.2 se ha caragado las notificaciones push via wifi cuando el telefono entra en deep sleep. Me parece un error muy grave. Una compañia seria ya hubiese sacado un fix.

I am extremely disappointed with the Nexus 4. After three updates after buying it, this is a problem that still persists. I fear that this error will be with us forever.

El wifi va fatal, las notificaciones fatal, no se que habréis echo pero como sigáis asi no le veo futuro alguno a este teléfono.Arreglarlo bien de una vez por todas.
Saludos

Desde que he actualizado a 4.2.2 las notificaciones push no funcionan bien. Tengo que desbloquar la pantalla para que entren. Reloj de whatsapp cargando mucho tiempo. FATAL la actualizacion.
Arreglarlo ya por favor, saludos.

4.2.2 and we have to stay in 4.2.1

good job google

4.2.2 -> Notifications don't come in after a while when phone is on deep-sleep.

According to http://www.xda-developers.com/android/receive-notifications-more-quickly-thanks-to-push-notifications-fixer/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+xda-developers%2FShsH+%28xda-developers%29 , seems like "heartbeat" is set too long, so the connection on port 4223 is automatically closed due to too many idle time and push server can't "hear" the phone heartbeat so it thinks phone is not listening. As a result: No push notifications. When screen is on again, a reconnection is called.

It's waaaay easy for Google to fix it, simply set a shorter value for heartbeat (i.e. 5-7 minutes) so the connection will not close due to idleness. It can be made automatically, as this value is automatically downloaded (and set) by the phone every 12 hours. An OTA update is even not needed!

Please Google FIX IT !!!!

it seems a shame to have a nexus, purchased 8/14/2012 and to this day nothing but have updated in the 4.1.1 OTA, shameful by Samsung.Y no friends that are updated for 4.2. 2.Me it shameful that we have a product of google and not updated.

I can confirm that adding static arp entries on the router fixes this issue.  Phone does not lose connectivity to the router.

root@ZOMGWTFBBQWIFI:~# ip nei show | grep PERM
192.168.1.191 dev br-lan lladdr e8:92:a4:93:xx:xx PERMANENT

[Comment deleted]

Shame have to stay in 4.2.1 to can recive notifications

please fix it

High priority Google! Come on!

come on! google wont say nothing about this and give us a fix?

Just starting happening to me as well. So frustating.

has this issue also something to do with the lags of the youtube app on wifi?

same here  4.2.2

[Comment deleted]

I'm frustrated with this. Tried a lot of things to fix this, but i can't. Every possible fix i do...after a couple of minutes becomes a placebo.


If you want to try if you have this issue i suggest using my method:

1) Open a friendly (but not primary) Gmail account on a "PC/Desktop/Laptop Browser". www.gmail.com
2) Lock your Nexus 4. (Important: Don't use any charger/dock, just use your N4 battery).
3) Open a chat window and send a message to you primary (Nexus 4) account ---> You probably receive the message ASAP.
4) Count to 10 and send another message... ---> You probably (again) receive the message.
5) Count to 40 seconds....and try it again.
6) Now you can also try pushing the button "Start Voice Call" and see what happens..
7) If nothing is happening...just press LOCK button and you instantly receive all the messages and maybe the "ongoing call" too.


Same happens with Viber, Whatsapp, etc.

Tried to replicate the issue with the old Samsung GT-i9000 (Samsung Galaxy S1) using CyanogenMod 10.1 (Android version 4.2.2)...but i couldn't.

It receives messages and voip calls ASAP when screen is off (and disconnected from charger). (Even after....30 minutes of sleep/screenOFF the reception is instantaneous)

So i think it's a Nexus 4 issue.

any news or dates to a fix for us?

#139 - It is specifically a Qualcomm Prima WLAN issue.  This also appears to affect the Xperia T (another Prima WLAN device).

ARP offload is currently broken on prima wifi chipsets.  If you enable it by changing hostArpOffload to 1 in the cfg file:
1)  ARP responses when offload is active have the wrong MAC address on mako - it appears to be an endian-swapped version.  e.g. if your MAC is AA:BB:CC:DD:EE:FF, the responses will be DD:CC:BB:AA:FF:EE
2)  On Xperia T, you will still not get ARP responses.  (I am going to try updating the firmware blob this weekend to see if the firmware from the latest Jellybean release is different...) - This is in CM10 with Qualcomm's opensource prima, I'll also try with a Sony stock kernel to determine if this is kernel-side or blob-side - at least from looking at the kernel source so far, this is a blob-side issue.

This is not an issue with devices that use Broadcom bcmdhd (such as I9000) - bcmdhd has had working ARP offload for a very long time.

[Comment deleted]

[Comment deleted]

My hypothesis is that there are 2 main problems here (both related with DEEP SLEEP):

1) A WiFi driver problem. Which affects receptions of notifications during WiFi + Deep Sleep.

2) A Google's push service issue because of the current configuration. Which can be fixed (probably) with "Push Notification Fixer" (Play Store app). This problem may affect both Wifi and 3G. (And maybe...internet stability could be a one of the ingredients of this problem).

Some people are confusing (including myself) the problem 1 with the problem 2. The problem 1 is the more aligned with this topic/issue.

@139, Google acknowledged that the Qualcomm wifi driver was the cause of the Nexus 4  ARP offload suspend wifi issue on January 14, and people have been complaining about it since November 20.  A fixed Qualcomm driver was not included in the 4.2.2 update for the Nexus 4; do you have any idea what is taking so long to get this done?

It seems that the issue is getting worked on. The aurora git shows this issue being fixed. Here is the commit difference to see how it's getting implemented:

https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git;a=commitdiff;h=b8ddf46808da1267b35086b478884bed27360e5c

Assuming the fix works we now have to wait for Google to push the update.

Google we need a fix ASAP

Is google working on this at least? WE NEED A FIX ASAP

Well....if it's true that "Prima" is something related with this....then maybe this current qualcomm project is an incoming fix...

https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git;a=shortlog

But maybe it's just for another device.

Acabo de comprar el Nexus4, Si hubiera sabido que en la 4.2.2 no habian arreglado el problema, no lo hubiera comprado, estoy pensando en devolverlo por esta razón.
Pease fix it. You are Google, no a litle company, all the custumers are waiting for it
my  acount, fergarmar803@gmail.com

Please fix it. You are Google, no a litle company, all the custumers are waiting for it

Maybe by the time the Nexus 5 comes out, it'll be fixed....


lets go Google, lets get this fixed!!

Please fix ;)

por favor arregladlo

Fix it please!

Fix it please!

There are custom fixes but need to be root. I don't understand why it takes so much time to have an oficial fix.

Fix it!

The same problem please fix it

still nothing??

I have the same problem, i tryed all type of things, and the problem sometimes happens with 3g too. We need a solution!!! so many difficulties for only one driver?

I hope better things about Google, but i´ve seen it´s like another company... customers is the last priority...

Fix this problem, because it is not a bug.

Please fix it...

Fix it please!

Fix it please  (Nexus 4 - 4.2.2)  no notifications at all a few minutes after screen goes off while on wi-fi at home.  Data won't be up & running until tomorrow so can't comment on that.

Real time notifications are one of the most important features of a smartphone, so a fix must be released soon. Please Google, listen to us and give it attention

I tried two brand new N4, and they have same issue. Ended up returning them both.

I have the same problem with wifi and 3G connection

Lamentable un telefono que no puedes conectar a internet si estas con el en stan by.... FIX IT!