yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] thracemerin:
Given that even with the "fixes" from Qualcomm it's not entirely fixed, you're assuming that this is an easy fix, when the evidence suggests that it's not.

The WNCSS WiFi drivers are closed source, which means that Google has to wait for Qualcomm to solve the issue and give them the updated drivers.
[Nexus 4 General] thesebastian:
Yeah but they started too late.... Or not? This issue is being carried since November.
[Nexus 4 General] thracemerin:
Maybe, but even if a solution was found by Qualcomm today, there's testing at Qualcomm, then they pass the fixes along to Google and LG who have to incorporate it into Android and do any device specific work, then there is testing at Google, then they release a fix. This isn't a 1-2 day process, it's likely to be a 1-2 month process minimum assuming the first try works, but if it doesn't the process starts again.

Also keep in mind, there are people who have never had this problem, even on pure stock, there are also those who have had serious problems with the "fixed" drivers, so there are factors outside the N4 (router hardware, network encryption, etc...) that further complicate this problem and make it difficult to find a 100% solution.

Edit: I'm not defending Google here, this is a serious problem, but software development cycles at large corporations take much longer than you think they would, and we're dealing with 3 rather large companies here Qualcomm, Google and LG.
[Nexus 4 General] Blockberd:
But as far as I could read the problem did not exist in 4.2 and/or 4.2.1. Most people faced the issue with 4.2.2 if I am correct. If...

Still the issue is annoying but the device itself is great... Too bad that I gave my HTC Desire away already.
[Nexus 4 General] meangreenie:
The problem was not noticed as much in 4.2.1 because of the wakelocks.
[Nexus 4 General] Blockberd:
Yes, possible... I read something about that. I think thats what AWL is doing (keeping the wifi awake).

Problems everywhere. Nowadays buyers are always beta testers. So many things which are fixed/which are working properly after (many) patches while the things are already "in the wild".

And I would not call myself an early adopter (I bought the N4 just 3 weeks back).
[Nexus 4 General] thracemerin:
The problem was at least as bad in 4.2.1 but like meangreenie said there were other issues keeping the phone awake that masked it somewhat.
[Nexus 4 General] thesebastian:
Mm maybe we won't have the final prima fix for 5.0. If 5.0 is released on May.
[Nexus 4 General] thracemerin:
5.0 will be announced in May, it probably won't be released in May.
[Nexus 4 General] bigmase521:
When this whole thing started and the initial bug report was filed back in November, I admittedly thought it couldn't possibly be so hard to fix. Now we're almost in April, it's obvious that the problem is not trivial. My whole beef is that a Google rep admitted in the bug report that it was a known buggy Qualcomm driver. So the fact that Google launched the phone with this buggy driver means either:

A) They knew the driver was buggy, but decided to release the phone anyway and hope that Qualcomm fixed it quickly after release. Or

B) Neither Qualcomm, LG, or Google QA'd the driver software enough to catch the multiple Wi-Fi problems with this device. How do 3 major corporations miss this?!

I'm not sure which is worse as both scenarios are pretty damn bad if you ask me, but I'm definitely not happy that either scenario has tainted my experience with an otherwise amazing device.
[Nexus 4 General] polipetto:
does this mean something is going on?

https://www.codeaurora.org/gitweb/e...it;h=5994295376662b74bee0d245df8b4f35553ea0fb
[Nexus 4 General] fozzie:
Yes.
[Nexus 4 General] dmillerzx:
Sadly static ARP didn't help my situation at all for my Galaxy Nexus (toro) :( :(

I suffer from this problem greatly on my Galaxy Nexus (toro).

This always fixes the issue for me for at least awhile (Credit goes to baldwinguy77 of Shiny rom)..... (this is the temp fix until your wifi toggles after a reboot)

Go to Advanced WiFi settings

For the Keep WiFi on setting, choose "Never"

For the Keep WiFi on setting, choose "Always" (steps 2 & 3 toggle the setting)

Long press power button, long press "Power Off", reboot your phone

The main thing that bugs me about this is that I love using the app smart wifi toggler (https://play.google....fitoggler&hl=en) best wifi app for saving battery life and really works amazing. Sadly if you use this app or any other like it with 4.2 you'll run into data stalls all of the time because of the App toggling wifi. Once the toggle takes place baldwinguy77's steps need to be performed again in order to prevent the bug from happening. Really surprising that more people aren't stressing over this one......

The frequency of which this problem manifest its self seems to depend on wifi radio toggles and a user's router setup.... All though the same routers do not have these issues with my wifi client if running 4.1

Sucks! I hate seeing those damn grey bars after waking my phone. Removing my favorite app (mentioned above) has greatly cut down on the frequency of the problem because wifi isn't being toggled as often.. It's always running

Note that this was never a problem before 4.2! 4.1 never suffered from this. It's a damn shame Google can't get this fixed. I'm been hoping for a dev to come to the rescue on this; however, nothing as of yet.

If anyone can come up with a permanent fix I will donate 50 bucks!
[Nexus 4 General] alguien24:
I also have delayed notifications with 3G, can be the WiFi issue related with this?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 General] thracemerin:
Toro uses a Broadcom WiFi chip that has open sourced drivers, N4 uses a Qualcomm atheros WiFi chip that doesn't, since the problem appears to be largely in the kernel the two issues are similar but unrelated as were talking about two different pieces of hardware and two separate drivers. Any fix found for the N4 is not directly transferrable to the GNex and vice-versa.

Nope, delayed 3G notifications is almost certainly an issue with your mobile provider.
[Nexus 4 General] alguien24:
But I came back to 4.2.1 and the problem disappeared, that's why I don't like 4.2.2

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 General] sam10000:
Hi, all

As a consequence of the Qualcomm bug (and others?), does the Nexus 4 usually awake from sleep and re-establish a Wifi connection with a mere 1Mbps speed? Is it commonplace that the figure will then rise gradually, but only to a maximum 72Mbps, even in the presence of a strong signal?
[Nexus 4 General] lolo.19900:
alguien24 i have the same problem but just not only 3g also wifi .

How you back to 4.2.1?
[Nexus 4 General] JoshinPl:
Flash stock rom via toolkit or recorvery, with all wipes :)

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 General] thesebastian:
My recommendation for people right now is flash stock 4.2.2 Google system.IMG and boot.IMG. and after that flash thracemerin Kernel WiFi v3

No need to wipe anything if you are coming from an stock ROM.
[Nexus 4 General] meangreenie:
Seems the majority of kernel devs here don't like fixes?

... scratches head
[Nexus 4 General] thracemerin:
It's not as straightforward as that

1) My kernel doesn't seem to fix it 100% for everyone, though it has solved the issue for most and fixed some other BT/WiFi related stuff for some as well.

2) My kernel occasionally responds to ARP requests with a bad MAC address (stock never does this, it just doesn't respond at all with the screen off)

3) Kernel authors in general don't like to include modifications to binaries that normally ship with the ROM (WiFi firmware in this case) as it prevents switching between kernels easily and can lead to other issues.

The MAC address issue is the most troubling to me, I'm still not sure why the heck it's doing that and I'm concerned its in one of the binaries and not something that I can find and fix.

These reasons aren't a reason people shouldn't use my kernel, they are reasons that other Kernel devs are reluctant to pull the trigger on the fixes.
[Nexus 4 General] [V]endetta:
will this fix connectivity issue with enterprise wifi? 802.1xx

been scratching my head since i bought this phone..but yet able to connect to enterprise network
[Nexus 4 General] fozzie:
No, this has nothing to do with the ability to connect to WiFi networks; it's about remaining connected when the screen's off.
[Nexus 4 General] moorzel:
Hi all!

I don't actually understand, why I don't get push notifications (gtalk for example) immediately on WiFi when screen is off. WiFi policy is set to be always connected. I have CM10.1 and stock CM kernel. I've tried to test it on many ROMs (stock, AOKP, PA etc.).

By tcpdump on router I see, that packets are received by the phone (tcp ack message is sent back to the server). So ARP is working propertly. Notification may occur after some time (1-5 minutes) after it was sent. When screen is on or phone is connected to charger - everything is OK. On cellular data everything is OK too (screen is off)...
[Nexus 4 General] Blockberd:
There are two issues here in general.

The first issue is that the WiFi connection breaks directly after screenn goes off. No notifications are received then.

The other issue is that notifications are just received few minutes later (as you explain).

Now some ppl are having first issue and can fix it with Advanced WiFi Lock (see ap store), some ppl have the delayed notifications and may try Push Notifications Fixer (see app store) and other ppl have both issues.
[Nexus 4 General] moorzel:
Thnx for answer.

As I understand the steps when phone is receiving incoming push notification via WiFi. Correct me if I wrong.

1. Server sends some notification packet inside existing TCP session to phone.

2. Phone receives this message, some wakelock must be done by WiFi to wake up system.

3. Phone wakeups and downloads full message from the server.

4. Phone displays notification (sound, vibration etc.).

What can be done by the applications you wrote about:

1. Push Notifications Fixer.

This app changes heart beat interval (hello packet) inside gapps to some another to default value. So, if for some reason TCP session is broken, phone can reconnect to the server faster (after 5 minutes instead 15 min for default).

2. Advanced WiFi Lock.

This app prevents phone going deep sleep making additional wakelocks when screen is off. It works for me. But it significantly makes my battery life shorter...

In my case phone receives packet inside existing TCP session. Also, I can successfully ping it from router and another PCs in network. I try to understand, why phone not waking up and not displays notification when screen is off? And why is difference from cellular connection?
[Nexus 4 General] [V]endetta:
so any workaround connecting to enterprise wifi?
[Nexus 4 General] Rizy7:
Sorry I'm a noob.. How do I remount /system as rw?

Im using es file explorer and granted it superuser permissions to access the files.

I see I can also choose an option to mount /system as writable.. Is that the same?
[Nexus 4 General] zaptac:
Yes.

Send by me.
[Nexus 4 General] Rizy7:
Sorry were you replying to me lol?
[Nexus 4 General] thesebastian:
Yes.

You need to mount it as rw (read/write) partition.

However....kernel with new drivers is the only real solution until Google updates it.
[Nexus 4 General] tuan209:
Hi,

I am not sure if this is the same problem as everyone here but I can connect to my school wifi no problem, but there are times when the wifi icon just grays out. When this happens, I cannot re-connect to the wifi unless I turn the wifi off and back on. If I dont do this, the wifi icon is just grayed out and insanely drains my battery.

I dont have this problem on my home wifi....

Is there a fix for this? From reading the first few posts, most people seem to only lose connection when their screen is turned off but is able to reconnect when their screen is on in this thread?

T
[Nexus 4 General] spicediablo:
I have just flashed air kernel. Have yet to encounter message lag for few hours. Will continue testing and feedback so users here can have possible solution

Sent from Mako
[Nexus 4 General] thracemerin:
Air kernel just updated prima to 3.2.3.90, as proven in my thread on a number of occasions this doesn't completely fix the issue and causes a whole new set of different issues instead.
[Nexus 4 General] spicediablo:
Yr kernel fixes this problem?

Sent from Mako
[Nexus 4 General] Blockberd:
As far as I got it it does not.
[Nexus 4 General] n2d551:
Possibly a fix?

http://www.androidpolice.com/2013/0...e-4-2-2_r1-2-here-is-the-developer-changelog/
[Nexus 4 General] thracemerin:
Not even close. This is regulatory stuff related to WiFi channels only.
[Nexus 4 General] n2d551:
So does this make worse. Like I saw removing the 5ghz
[Nexus 4 General] thracemerin:
No, I just think it blocks 5ghz when it can't figure out what regulatory domain you are in based on cell signal, if you are in an area that normally allows 5ghz it shouldn't do anything.
[Nexus 4 General] sam10000:
Hi

Since Google has failed to fix these bugs after months, has anyone managed to find a wireless router which works well with the Nexus 4, without disconnections, delayed notifications, etc?

Thanks.
[Nexus 4 General] Blockberd:
As far as i know there is no way that a router will fix this issue completely. For me the app "advanced wifi lock" and "push notification fixer" are doing their job just great.
[Nexus 4 General] Dawn Breed:
Just flashed the new SaberMod Kernel. Let's see if there is some improvement.

n

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 General] zerow:
Hello to everyone. Some noobish questions i have regarding this problem:

1) Do i have to have CM to install the fix included in the original post ? I am running rooted stock now.

2) Does this solution affect something different from the solution from Thracemerin ?

3) If i combine this fix or maybe Thracemerin's soltuion with the push notification app and advanced wifi lock, do they interfere one with the other or i should try one thing at a time ?

4) My phone delays notifications on wifi but also on mobile data. So i cannot understand, if this problem is wifi-driver related why it apppears also on 3G ? Is there any indication an official fix is on the way ?

Thanks to everyone who shed some light for me !
[Nexus 4 General] ag2000ir:
Hi all,

I do not have any wifi issue when I am on campus, but when I am home this issue is very serious and my Nexus 4 is the only device at home that has this problem.

Would appreciate if somebody can explain why the issue is router dependent.

Thank!
[Nexus 4 General] Richieboy67:
I have a belkin dual and have no Wi-Fi issues at all with nexus 4.

Sent from my shiny new, scratch less Nexus 4!
[Nexus 4 General] sam10000:
Which Belkin model? I'd like to look up its chipset and other spec's.

Thanks.
[Nexus 4 General] Blockberd:
1) no. Your phone just needs to be rooted. You only need ClockWorkMod to apply the files. But you can appy the changes manually on every rom if you have root.

2) i dont know what tracermerins fix is doing but hee mentioned that his fix resulted in different other issues for different people.

3) they not interfer but its useless. You either do the ini change or use AWL. As you are already rooted you may want to try the ini change. AWL is keeping WiFi just awake during sleep.

4) the delayed notifications are different from the WiFi issue. People tend to mix them up as they "look" the same. As you have delayed notifications on 3g and WiFi you should try PNR. Keep in mind that PNR will not have affect on the dropping WiFi connection. If connection drops during sleep you will still have delayed or no notifications at all (during sleep).

Broadcom is already working on the WiFi issue. See first post for details. Hope they push it soon and google pushs it ASAP to the phones.

Hope that helps.
[Nexus 4 General] apex88:
Hi, can these files work with TWRP recovery?

I tried to change the file manually, remounted system as RW via terminal emulator but unable to edit the file, getting "this operation requires elevated premissions, try to change the root access".

i have root.
[Nexus 4 General] Blockberd:
Maybe your editor does not have root access. Better you use ES File Explorer to change the permissions (R/W etc.), edit the file, save it and change the permissions back to previous (important!).

As far as I understood, the files are specifically made for CWM Recovery. So I doubt that they will work with TWRP.
[Nexus 4 General] apex88:
i tried ES file editor and cm file editor got the same on both, cant change the file.

i used the following command to remount the system as RW: # mount -o rw,remount /system.
[Nexus 4 General] strainhunter:
No, it works with TWRP too.

And do it manually with rootexplorer by going to the system-folder where the file is, make it rw, longpress on file and select open with -> pick text editor -> make changes -> save (this way it makes a backup of the file you´re editing automaticaly (if you enables this in settings)...
[Nexus 4 General] Headcase_Fargone:
Can someone that's used this procedure let me know if it does anything to solve incoming voip calls? I can't use Csipsimple on my Nexus 4 at all currently, as it doesn't ring if the screen is off.
[Nexus 4 General] SpookyTunes:
Have you tried the built in SIP client? It is well integrated with the stock ROM. I am stock and have been using it with Callcentric (T-Mobile HSPA and WiFi).

Phone > Call settings > Internet Call Settings
[Nexus 4 General] Headcase_Fargone:
Tried that a while back. It actually would wake my phone up in time to answers, so incoming calls worked with this method. But there's no way to make outgoing calls (that I'm aware of) using an account like PBXes.org and your GVoice number with Internet Calling.

I did try staying registered in both Internet Calling (set for incoming only) and Csipsimple (set for outgoing only), but I couldn't get Csipsimple to actually connect the call when I tried to make one.
[Nexus 4 General] SpookyTunes:
2 options, one is to use SIPSorcery.com with a IPKall DID.

You setup SIPSorcery with your Google Voice account and forward your IPKall DID to your [user@sipsorcery.com] SIP address.

Add the IPKall DID to Google Voice and you can use the native Android dialer. It worked well on WiFi, but I had audio issues on mobile data.

The other is to use a app like "Voice+ (Google Voice callback)"

I use this with CallCentric as they are in NYC and it works over mobile data for me.

I wasn't a big fan of PBXes.org myself, as I prefer a real DID over a XMPP gateway (less conflicts with Google Talk client).

Most free SIP accounts will only allow you to receive calls, so GV dial-back turns outgoing calls into incoming calls.
[Nexus 4 General] Headcase_Fargone:
While I appreciate the suggestions, that sounds like an awful lot of hassle just to get incoming calls working when they should be working in Csipsimple to begin with. This exact same setup worked great on my Galaxy Nexus, and I never had wake issues on incoming calls with it.

I've decided to kill two birds with one stone and ordered an Obihai Obi100 that I'm going to set up at home. That's really the only place that I NEED incoming calls to work over IP since I don't have cellular reception inside. So I'll just forward all calls to it as well as my cell. If the cell doesn't ring, no big deal, I can pick up one of the old-school cordless phones at home.
[Nexus 4 General] octobclrnts:
If I could ask, how did you fix the echo issue in the built in SIP client? Are you fixing it on the callcentric side?
[Nexus 4 General] SpookyTunes:
I tried Sipdroid, CSipSimple, and Linphone back on my Nexus S with 2.3.x All 3 had more echo, even after setting up the "echo canceling" option when available. The native SIP client paired to my old bluetooth headset (phone audio profile) on WiFi had the least echo. Finding a server with the lowest latency also helped a lot.
[Nexus 4 General] Whyzor:
Can we get some responses on whether the .ini mod worked for those on 4.2.2? I just tried it on my stock rooted 4.2.2 and doesn't work. 'Advanced Wifi Lock' app works (with higher battery drain).

I know the OP said in post #1 it's confirmed to still work, but recent posts in this thread by a bunch of people also said it doesn't (I have read through the entire thread & the Google bug tracker history yesterday). Could it be something to do with using the .ini mod from 4.2.1 carries over to 4.2.2, but not newly applied to 4.2.2?
[Nexus 4 General] estejabo:
Hi.

I was reading the 4th point and I think i got both problems, Im already a rooted user and i have change the parameter in the .ini file. the phone now responds to ping normally when the screen is off, but the messages are still late, can you explain me what is PNR? and what should i do to fix it? Thx in advance:good:
[Nexus 4 General] Blockberd:
PNR is short for Push Notification Fixer. You may get it in the play store: https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer

Now I also see that he added the information that the app is only for rooted phones. This is intresting because I did not face any delayed notifications anymore after installing this app. Anyhow... As you are rooted you may give it a try.

Good luck!
[Nexus 4 General] estejabo:
Ok, thanks so much, i got one last question, as this aplication needs root acces.... it will modify archives that i will need to be untouched to get the next OTA?, in the description the developer puts: Added ACCES_SUPERUSER manifest permission (best practice only),

Thx in advance
[Nexus 4 General] Blockberd:
I am sorry but I am not 100% sure what exactly you mean with "it will modify archives that i will need to be untouched to get the next OTA?".

The root access seems to be required to set the specified Google service timeouts properly.

The "ACCES_SUPERUSER" is a permission which is (as far as I could work it out) a "should use" and not a "have to use" for apps which require root access.
[Nexus 4 General] estejabo:
Well, as far as I know, an OTA is some kind of update for the system, and it wont go well if you have files of the system whit modifications, so i was wondering if this aplication modifies some of those files, just like the ini file for the wifi.
[Nexus 4 General] DesmoDavid:
I love the guy who started this topic! Your .ini file plus PNF solved the problem with my N4. I've added your thread index in my signature with another link of your fix on my Google Drive account and another link to play store for PNF! :D
[Nexus 4 General] viktorlj:
I use Best WiFi Keeper app on stock unrooted ROM. That app fixed all network problems.
[Nexus 4 General] andy o:
Does anyone know how to set a static ARP on DD-WRT? I just installed it on a Netgear WNDR4000, but all the references to static ARP I googled were regarding Wake-on-LAN. Much appreciated in advance.
[Nexus 4 General] Fire-Dragon-DoL:
I may have found a temporary fix for this which doesn't involve rooting or static ARP table.

The basic problem is that I have a Tasker task that when it loses my home wireless network connection, it does some things (which involves even turning on the screen and showing a scene). So basically this "blocks" from deep sleep AND waste battery because it turns on the screen, yay.

I've disabled the "optimize Wi-Fi" option (under Wifi => advanced), this seems to stop deep sleep or, in any case, solve the problem.

I also noticed that the issue happens earlier with 5Ghz network and a bit later with 2.4Ghz.

This should also allow people to keep using OTA. Hope this helps you guys.

If anyone can confirm, let me know. Also tell us the consequences, I have no idea how much battery will drain.
[Nexus 4 General] Blockberd:
Advanced WiFi Lock does not require any of these, too. ;)
[Nexus 4 General] acid74:
Tried it,no help:crying:
[Nexus 4 General] navegaamorim:
I tried every thing that i see, but i just solved my problem changing to a old router that I have... Its really annoying that Wi-Fi turns off when phone get into deep sleep