yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] chrisgtl:
Does anyone else get high pings like me?

This log is started at same time as switching Nexus 4 on. Running 4.2.2 /w franco #83 kernel.

C:\Documents and Settings\User>ping 10.0.0.75 -t

Pinging 10.0.0.75 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 10.0.0.75: bytes=32 time=27ms TTL=64

Reply from 10.0.0.75: bytes=32 time=44ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=9ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=75ms TTL=64

Reply from 10.0.0.75: bytes=32 time=99ms TTL=64

Reply from 10.0.0.75: bytes=32 time=19ms TTL=64

Reply from 10.0.0.75: bytes=32 time=35ms TTL=64

Reply from 10.0.0.75: bytes=32 time=158ms TTL=64

Reply from 10.0.0.75: bytes=32 time=78ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=88ms TTL=64

Reply from 10.0.0.75: bytes=32 time=6ms TTL=64

Reply from 10.0.0.75: bytes=32 time=62ms TTL=64

Reply from 10.0.0.75: bytes=32 time=292ms TTL=64

Reply from 10.0.0.75: bytes=32 time=81ms TTL=64

Reply from 10.0.0.75: bytes=32 time=44ms TTL=64

Reply from 10.0.0.75: bytes=32 time=53ms TTL=64

Reply from 10.0.0.75: bytes=32 time=3ms TTL=64

Reply from 10.0.0.75: bytes=32 time=201ms TTL=64

Reply from 10.0.0.75: bytes=32 time=120ms TTL=64

Reply from 10.0.0.75: bytes=32 time=38ms TTL=64

Reply from 10.0.0.75: bytes=32 time=264ms TTL=64

Reply from 10.0.0.75: bytes=32 time=209ms TTL=64

Reply from 10.0.0.75: bytes=32 time=121ms TTL=64

Reply from 10.0.0.75: bytes=32 time=41ms TTL=64

Reply from 10.0.0.75: bytes=32 time=267ms TTL=64

Reply from 10.0.0.75: bytes=32 time=187ms TTL=64

Reply from 10.0.0.75: bytes=32 time=108ms TTL=64

Reply from 10.0.0.75: bytes=32 time=321ms TTL=64

Reply from 10.0.0.75: bytes=32 time=236ms TTL=64

Reply from 10.0.0.75: bytes=32 time=173ms TTL=64

Reply from 10.0.0.75: bytes=32 time=94ms TTL=64

Reply from 10.0.0.75: bytes=32 time=305ms TTL=64

Reply from 10.0.0.75: bytes=32 time=2ms TTL=64

Reply from 10.0.0.75: bytes=32 time=143ms TTL=64

Reply from 10.0.0.75: bytes=32 time=62ms TTL=64

Reply from 10.0.0.75: bytes=32 time=291ms TTL=64

Reply from 10.0.0.75: bytes=32 time=209ms TTL=64

Reply from 10.0.0.75: bytes=32 time=129ms TTL=64

Reply from 10.0.0.75: bytes=32 time=51ms TTL=64

Reply from 10.0.0.75: bytes=32 time=277ms TTL=64

Reply from 10.0.0.75: bytes=32 time=198ms TTL=64

Reply from 10.0.0.75: bytes=32 time=117ms TTL=64

Ping statistics for 10.0.0.75:

Packets: Sent = 52, Received = 47, Lost = 5 (9% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 321ms, Average = 113ms

C:\Documents and Settings\User>arp -a 10.0.0.75

Interface: 10.0.0.95 --- 0x2

Internet Address Physical Address Type

10.0.0.75 f8-**-f3-**-4c-** dynamic
[Nexus 4 General] skezza:
High pings? Those numbers are quite normal for WiFi.
[Nexus 4 General] neer2005:
I get like 8-10ms on my wifi
[Nexus 4 General] zdenoh1975:
I definitly confirm, that this wifi fix under 4.2.2 (under new radio and bootloader) dont work... I tryed everything.

With 4.2.1 ROMs this fix worked very good. I must go back to old radio and old 4.2.1roms. Maybe I give it up with my N4 and after many years with android phones.. Very big disappointment from Google. :(
[Nexus 4 General] Lownita:
So they don't fix it, but even make the fix obsolete, lol!
[Nexus 4 General] darkamikaze:
Hmm so does it not work or does it work. The OP post is the opposite of recent user posts.

This is a bit disappointing for my first Nexus device ): .. I miss using AirDroid and this bug completely owns the app.
[Nexus 4 General] zdenoh1975:
I tryed stock 4.2.2, most custom 4.2.2, with flash bootloader, radio, with all wipe, full wipe and system of course too, and never this fix worked..

I came back to 4.2.1 with previous radio and fix work.

exactly - they don't fix it, but even make the fix obsolete.....strange
[Nexus 4 General] mobilehavoc:
I can confirm I'm on stock rom 4.2.2 and this fix works perfectly still. You are having some other issue that's causing the problem. Sadly there are many with this phone and wifi.
[Nexus 4 General] ComRaider:
In another forum a mate said that he found a temporally solution. He flashed montley 57 kernel from 2.2.1 on 2.2.2.

He now receive notifications in time. Sorry for my english.

Enviado desde mi Nexus 10 usando Tapatalk 2
[Nexus 4 General] NeoDaemon:
if u are talking of HTCMania, the same user posted later that said solution only worked for 10~15 minutes.

Link to said thread: http://www.htcmania.com/showthread.php?t=553026 < Spanish forums talking about this issue.

Man this bug is a real pain in the ass, for me 4.2.1 works fairly good with wifi notifications on deep sleep, tried 4.2.2 and every time the screen goes off notifications get delayed(3G works good), even with the fix on first post.

I hope Google/Qualcomm fixes this asap. :silly:

Grettings:good:
[Nexus 4 General] TheProf82:
I have this problem too and the fix didn't work, running 4.2.2 stock with franco kernel (both franco and stock kernel were tried). Too bad, it's very annoying.
[Nexus 4 General] Ivancp:
here the same problem, with notifications and with the grey icon wifi too. If i have the screen off about 10-15 mins, I have to turn off and turn on the wi-fi because internet fails and there's no internet, sorry for my baad english
[Nexus 4 General] Liam0o:
I have this issue too, when phone is on wi-fi and screen is off i get no push notifications, as soon as the screen is turned on i get a barrage of late messages

I don't understand how this isn't a priority for google, it's a potential deal breaker for a lot of people, i don't intend on spending all my time turning my screen on and off just in case i MIGHT have a message or important e-mail
[Nexus 4 General] Primetime_de:
I'd just informed some German sites and magazines about this issue, but I think that make no difference...

But maybe it helps.
[Nexus 4 General] MonztA2:
Fix (n4-wifi-sleepfix-bcast_only) works fine for me on stock 4.2.2. But not on the first boot after flashing. I needed to reboot after flashing.
[Nexus 4 General] el_charlie:
Let me tell you my experience.

In my workplace, wifi works fine (Linksys WRT110), but at home I had many problems with my Dlink DIR 600 rev B router. I had DD-WRT on it and tried almost EVERYTHING (change to N-only, to mixed, to B-G, disable security, reduce TCP timeout, reduce beacon interval and so on) and none of that worked.

I also tried the patch here. It didn't work.

I decided to go back to stock DLink firmware. I found out on DLink's site that a firmware was released this month for my router. I gave it a try. It was a PITA because I had to use a special method called Emergency Room interface to remove DD-WRT. After I did it, I had to configure everything again.

Surprise! WiFi works now! I even had a skype call to my girlfriend.

So, my solution is to use stock ruter firmware and update it if necessary.

Cheers!
[Nexus 4 General] mobilehavoc:
I don't get why its not working for other people. The config file change works perfectly for me on 4.2.2
[Nexus 4 General] Liam0o:
I've tried this fix on stock 4.2.2 and i have to say it's much much better than before, messages are at most a few minutes late compared to not coming through at all before (until screen was turned on)

Even if there is a bit of a drain on the battery it's worth it, at least until Google gets their act together and fixes the issue

I changed the values manually with ES file explorer, made sure permissions were set correctly and rebooted, waited 5 minutes and rebooted again, since then i've noticed the improvements, it might not work for everyone but it's worked for me
[Nexus 4 General] chrisgtl:
http://code.google.com/p/android/issues/detail?id=40065

Found a different bug tracker but is related to the same problem.
[Nexus 4 General] giacomowrc:
Maybe a solution?

Hi guys, search on play store Push Notifications Fixer

I have the problem with 3g and I hope this solve It. The developer says that work for the wi-fi also. Anyway, there is a description of the problem in the application page. I hope will help you.
[Nexus 4 General] iceman92:
using the fix. working great. no longer having delayed whatsapp msg. thank you :)
[Nexus 4 General] Zaldi00:
Hello!!!!! This zip works fine in Spain!!!!

http://db.tt/48PvAEkQ

Change 2 lines in WCNSS_qcom_cfg.ini

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 General] Ivancp:
About 1000 people with this bug, look the coments and the starts... https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=40065

Please help to fix this, sendmessages to google
[Nexus 4 General] bLank-Mind:
tried both of for this issue.. working better than before.. but the question : is this fix make the notification real time when the screen of or just make it better than before? because i still have delayed around 1 - 2 minutes..

i'm sorry for OOT but i'm so curious about radio on this nexus.. i have no idea about that.. can someone give me short explanation..or ref link?
[Nexus 4 General] albertbm:
I'm getting really high pings aswell, I'm stock and unrooted this is my Nexus 4

Ping statistics for 192.168.1.129:

Packets: Sent = 65, Received = 65, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 3ms, Maximum = 510ms, Average = 151ms

And as comparison my old HTC Desire:

Ping statistics for 192.168.1.132:

Packets: Sent = 54, Received = 54, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 60ms, Average = 2ms

I'm so happy with the device in every other way :(
[Nexus 4 General] gravityz3r0:
Is it true that this fix also work on 4.2.2? Because i seriously doubt so, on 4.2.1 it was working perfectly but after the update, this fix does not work anymore. Am i missing something somewhere?
[Nexus 4 General] elandune:
So sad need to come back to 4.2.1 to recieve notifications....
[Nexus 4 General] mobilehavoc:
Again I'm on stock 4.2.2 and the fix works perfectly for me still. So if you're having an issue it might be something else causing it.
[Nexus 4 General] MonztA2:
See http://xdaforums.com/showpost.php?p=38238797&postcount=213
[Nexus 4 General] JoshinPl:
The fix from 1st page dont work for this issue for me... It's very dissapionting.... I'm on 4.2.2

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 General] mobilehavoc:
I still have mine on but did you try turning off the option to optimize wifi for battery life?
[Nexus 4 General] arby80:
Well this sucks I thought it was just a problem with the custom Rom or Kernel I installed. It is disheartening that this is truly a google issue that my phone will not stay synched on wifi with the phone off. I just switched over from the Galaxy Nexus and after first upgrading to 4.2.2 my Wifi would not connect at all, connecting once and then completely locking up the wifi until reboot. Eventually I got it to work on that phone.

Hopefully this fix will work for me. It is a shame how much of a step back that Google made upgrading to 4.2.1, Android did work perfectly before the "upgrade". Hopefully they will actually test Key Lime Pie before releasing it.
[Nexus 4 General] TaintedByte:
This fix works for me. I'm on cm10.1 (4.2.2) and on franco's kernel. I get pings with the screen off, notifications are a little bit slower than my Nexus 7 but still within the minute, much better than not at all and finally; Airdroid works perfectly with the screen off.

For those that are not working either the changes aren't sticking or the permissions for the file are wrong. Double check that. If it's still giving you trouble then it is something else interfering with the problem. But on stock ROM and CM10.1 it will work.

Now, the fact that this issue even exists is very depressing. I remember that my previous phone, the EVO 4G LTE had the same exact issue (not driver related -- but the problem was the same). I remember telling myself that my next phone would be a Nexus so I wouldn't have to deal with problems like those. Now I'm not so sure what to tell myself. I hope Google releases a fix soon for this. Can't wait 2+ months for Key Lime Pie, nor should we have to.
[Nexus 4 General] meangreenie:
Seems the more people complain/beg for them to fix it makes them all the more determined not to :(

It's like we have done something wrong for telling them that something important doesn't work.
[Nexus 4 General] Primetime_de:
Can anyone from the States inform the IT press and online magazines about this issue?

Maybe it helps.

I'd done this here in Germany but no response so far...
[Nexus 4 General] elandune:
Im writing to google and some android spanish blogs

lets hope google read and do smth...

Im in 4.2.1 + franco r13 kernel and notifications are perfect, but wanna update to 4.2.2 w/o losing them
[Nexus 4 General] praveenmarkandu:
Would I able to OTA update or manually flash a new update from google in the future? Or would I have to revert to the original file before doing so?
[Nexus 4 General] arby80:
The zip file seems to have worked for me on AOKP build 4. After spending the weekend trying to figure out the problem.
[Nexus 4 General] Stryder5:
Since this is a file in the system partition, I believe you would have to revert the original file. Either that, or the OTA will automatically revert the file for you. I'm not sure which is the case since I don't keep my phone stock.
[Nexus 4 General] praveenmarkandu:
I believe this is bug report is related as well http://productforums.google.com/forum/#!category-topic/mobile/android-devices/zzogpq4hjbU[1-25-false]

17 pages of crap.
[Nexus 4 General] edenist:
Have performed this ini modification, though it does not seem to make enough of an improvement.

I'm of the opinion that this modification *lessens* the effect of this bug, but the bug is still very present.

After making the change, my phone now reponds to ICMP [ping] packets when the screen is off *most* of the time. [Previously it would not respond to any of them].

However it does not seem to make any difference to wifi receiving packets.

I can test this in a much more objective way than by noticing how long my gmail notifications take, I use the DI.fm app extensively throughout the day. Nothing illustrates this bug more than having music constantly drop out when the screen turns off.

I have Wifi optimisation disabled which has no effect relating to this bug.

Will see what I can find but otherwise this is still an ongoing issue as everyone here can attest to...
[Nexus 4 General] yogeshmha:
@op

can you create a poll in here to check for how many peoples this fix seems working and how many not.

thanks
[Nexus 4 General] darkamikaze:
The fix seems to work for me however pinging to my phone shows really bad response times. I guess that's better than no pings at all.
[Nexus 4 General] praveenmarkandu:
I'm guessing this degrades battery life somewhat.
[Nexus 4 General] andy o:
Does anyone know if any 4.2.2 custom roms don't have this problem? I was testing yesterday, and the CM10.1 M1 build (4.2.1) didn't have this, but all the 4.2.2 builds do have it. I couldn't test on the latest 4.2.1 nightlies. I saw this thread and bug report only after updating to the 4.2.2 builds a few days ago, noticing my VoIP calls weren't ringing, and searching for an answer. Reverting to 4.2.1 M1 sort of confirmed my suspicions that this bug in stock Android was somehow, purposely or not, bypassed in the 4.2.1 builds.
[Nexus 4 General] meangreenie:
Could be that the 4.2.1 buggy sleeping mode kept WiFi alart, masking the problem.
[Nexus 4 General] mobilehavoc:
That sounds like a different bug. The app if its written correctly should create a wake lock to keep wifi running when the screen turns off. Very odd.
[Nexus 4 General] andy o:
Was this a known issue?
[Nexus 4 General] Entropy512:
1) I'm not sure about prima (I will dig into that this weekend), but at least with bcmdhd, ARP packets make it through regardless of IP broadcast/multicast filter settings. In fact, any decent wifi chipset has ARP offload support where the chipset will itself handle ARP requests without waking the host.

2) This WILL have a negative impact on battery life for many people. Seriously, on Cyanogenmod kernels for many Samsungs with bcmdhd drivers, we've done the EXACT opposite of what you suggest with zero negative effects and massive positive effects (in terms of battery life) for many users. (My guess is that the only thing that would actually need multicast while a device is asleep is a DLNA server.) That said, since mako can resume from sleep in 9ms and suspend in 32 (as opposed to around 650/150 for Exynos4), the impact will be less than on an Exynos device - but it WILL be negative.

That said, arping seems to fail when the device goes to sleep. This is interesting, however I have never had any issues with notifications coming in while the device is asleep despite this. The solution is not to baseball bat it by letting through all broadcast traffic - you WILL have a major negative impact on battery life. The proper solution would be to figure out why ARP offloading is busted.

There's a setting in that config file for ARP offloading, however... it seems like it has some sort of odd endianness issue. The first four bytes of the MAC are reversed when the device is asleep, and then the next two bytes are also reversed.
[Nexus 4 General] Entropy512:
Yeah, that'll happen for any incoming packet that wakes the device.
[Nexus 4 General] andy o:
Do the notifications come in instantly, or do they take their time, like tens of seconds or more? I don't have a problem receiving them either, just getting them instantly, which is essential for VoIP calls.
[Nexus 4 General] darkamikaze:
Yeah the problem with it is that there's a delay of sometimes 10 seconds to minutes before I get a proper notification. It sometimes feel like you're running Juice Defender set to check notifications at intervals. :/

This workaround is working for me great. Using airdroid the whole day and my drain is as expected for me. :/ Until we figure out a proper fix this will have to do.
[Nexus 4 General] meangreenie:
We need the guy/hero from the UK orders thread to contact the Google boss again.
[Nexus 4 General] thesebastian:
I have exactly the same problem, with an exception:

There are no problems at all when Nexus 4 is connected to the charger.

I think it has something to do with "Battery". When you unplug your N4 from AC and screen=OFF...somethings happens with the WiFi behavior.

Issues only appears while on Battery.

Current router model: TL-WR740N

Method to replicate the issue:

1) Send Whatsapp/Viber message. (Sometimes message arrive).

2) Start Viber call. (Sometimes the 1st call arrives). --> Manually Lock N4 again.

3) Start another Viber call + 2 o 3 Whatsapp/Viber message, Gtalk message, etc. ==> none arrives.

4) Press N4 lock button => All the things arrives ASAP, including the ONGOING Viber call.

I tried:

Router:

- Updating this router firmwares to the newest version (2013 february).

- Use DMZ

- Change from WPA/WPA2 (Auto) to WPA2 only.

Android:

- Disabling/Enabling Wifi Optimization

- Enabling this wifi fix in system/etc/wifi (directly flashing the zips with CWM).

- Trying "Push Notification Fixer" on the store.

- 2.4Ghz or Auto options.

- Changing wifi Sleep policy to "When the screen is off" and then...to "never" again.

- Try with franco kernel

- Try with Paranoid Android kernel

- Most of the time i tried with Google Kernel/ROM (flashing system.img and boot.img).
[Nexus 4 General] Entropy512:
*facepalm*

No, it has nothing to do with battery. Seriously, since the beginning of Android, charging has always held a wakelock and inhibited deep sleep.

So, DUH - a problem that only occurs during deep sleep isn't going to occur on a charger, EVER.

Bet you'll have the exact same results if you use the Wake Lock app when unplugged as you do when plugged in. This will make your battery life suck of course.
[Nexus 4 General] thesebastian:
But, do i have a problem here? or it's just normal behavior?

I don't care to receive messages with delay.

But i really care to receive voip calls ontime (like viber)...

If i try to call myself nothing happens...But when i press the lockbutton (to turn on the phone) the incoming call appears in 0-3 seconds.
[Nexus 4 General] andy o:
Of course it's not normal. This has been known and even the solution known in the first post for a long time. Take a look at the link to the google bug report. We're all waiting for a Qualcomm driver that Google didn't release in 4.2.2. That's the fix, and the other things are workarounds, which for some don't work on 4.2.2, including me. I also need immediate notifications for VoIP, even 10 seconds is not enough.
[Nexus 4 General] thesebastian:
Andy. Is there a way to manually update the WiFi driver then?
[Nexus 4 General] andy o:
Well the point of all the complaints about Google/Qualcomm is that there is no driver out yet, so no.
[Nexus 4 General] thesebastian:
Sorry i tough it was released by Qualcomm but not Google.

Well I hope that this driver is generated.
[Nexus 4 General] edgemaster:
I wonder why this thread only has 26 pages so far.

One of the most important features on a Smartphone is to be available at all times and for that notifications are needed.

Does this problem only occure for people running custom roms or also stock?

Also are some just lucky that the problem doesn't occur for them or how can i understand.
[Nexus 4 General] elandune:
both

totally agree
[Nexus 4 General] andy o:
My guess is that many like are not noticing it cause notifications do arrive, only tens of seconds delayed, which could just be acceptable or unnoticeable for them. My problem is more with VoIP calls for example, and not everybody uses that. Also for some reason I don't think this happened with the 4.2.1 builds of cyanogenmod. I know for sure it doesn't happen with the M build, and I have tested the VoIP apps extensively with those nightlies. Only a couple of days after the first 4.2.2 update I noticed this bug and found this thread.
[Nexus 4 General] thesebastian:
FYI i just tried to replicate this issue with an old Samsung GT-i9000 (Samsung Galaxy S1) using CyanogenMod 10.1 (Android version 4.2.2)...but i couldn't. (I used one of the latest nightlies)

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)

These are the steps i use to check this: