I'm really getting bored about this...
Basically happens that the push notifications are completely delayed (or temporarily stopped) after a while im on wifi..
everything is set correctly, wifi sleep policy is set to keep awake even on sleep...
with 3g network everything is ok, push notificaton works fine...instead on wifi after a while, notifications stops (gtalk messages, mails, whatsapp,..), they back all together at some point later...so the solution is to wait (couple/ten minutes) or I have to put wifi toggle off and on to get notifications all together
the wifi and network indicator are blue...but i supect the synch with google services is lost, since if i log out from gtalk and log in again, gtalk don't come online soon...when it finally come online, the i got all notification all together...
the wifi has no proxy or something..a simple wpa home wifi..
what could the problem? someone encountered it? tips? its only me? (i can't believe only me)
to me is seems like after the phone go on sleep, the connection to google services is lost, and it come back only after some several minutes (when probably a reconnection is being forced)..this is annoyng when chatting on gtalk...i also noticed that doesn't never happen if screen is on and im currently using gtalk for example..
currently im with stock JB 4.1.1 (see signature), but was happening with ICS also, and even with my previous htc desire..but now with JB seems to happen more often and in a fast way, it loose the push notification connection much sooner than ICS..and also, let me say: we are on android 4.1 and still google didn't fix this? wtf those android push are not reliable, and note that I'm a big android fan so..
its some bug on android or something wrong with my wifi router/network (even if I tried also in my parent house, and its same)?
also, i tried using static ip, google dns, 2.4ghz only..what else to try?
really appreciate some tips..thanks in advance! and sorry if my english not perfect!
No one?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Does it do that on other devices that you own? (Nexus 7 maybe?)
Also, you're saying that this is happening after the update, right?
At the moment I have only this device
It happen before with ICS and also now with JB
But I don't think Im the only one that have this..
Inviato dal mio Galaxy Nexus con Tapatalk 2
So no one have delayed push notification under wifi??
/last bump
I have the similar problem (except I don't get notification unless I connect via mobile data).
Since on ICS, no push notifications over WiFi (everything works fine on mobile data though). Acc sync is on, WiFi set to never sleep (which I think doesn't really matter, because I'm not gettin any push notif. even when the phone is awake).
Also tried different ROMs, kernels, factory resets etc. (rooted), nothing helps. I have to open the app when I want notification update (using Gmail, Whatsapp, Foursquare, Friendcaster).
This is really a pain, could anyone help pls?
I use SGS GT-I9000, currently on SLIM rom, Semaphore kernel (see attached img).
Hey bro, is there any updated solution on the push notification failure on Jellly Bean???
It's frustrated to get in whatsapp for msg everytime.
gase888 said:
Hey bro, is there any updated solution on the push notification failure on Jellly Bean???
It's frustrated to get in whatsapp for msg everytime.
Click to expand...
Click to collapse
the real solution is a good mobile carrier and a good wifi router
I think google will never take care of other's fault
andQlimax said:
the real solution is a good mobile carrier and a good wifi router
I think google will never take care of other's fault
Click to expand...
Click to collapse
Disagree. As I tried (as suggested by others on XDA), i open whatsapp and then off the screen. The push notification works.
So it's not about the strength of signal.
The push notification framework is one service that run for all the apps.. So it's not related to one or to an other app
Whatsapp not use push notifications when you have it opened, it only use push after some minutes that you don't open it
Its not a problem of signal strength, is a problem of connection timeout... Every carrier have different timeout for long connections... The push connection is a long running connection, that should always be alive to work correctly
Inviato dal mio Galaxy Nexus con Tapatalk 2
I'VE FOUND A WORKAROUND of this no-push-notif during deep sleep problem.
Earlier, I tried holding partial wakelock so the device never sleep, this of course works alright, but drains battery very rapidly (5% / 30mins).
This is NOT ACCEPTABLE.
So, I tried something else :
automatically waking up the device regularly every 30mins, with the help of Tasker (which doesn't turn on the screen at all).
The result is :
7 hours after screen off and a good night sleep, in the morning I sent myself a BBMsg and it arrived perfectly in about 5 secs.
Battery consumption is totally acceptable : only 4% drop during 7 hours (dual sim ON, data ON).
That's days ago, and still works perfectly until now, I'm happy with it, so I'd like to share the AWESOMENESS.
I'm not sure about push notif from Google servers via GCM, I don't use any app which takes advantage of GCM, I only use BBM which uses its own servers.
In this case, you should first try adjusting heartbeat interval using PushNotificationFixer (which can't help me since it only resends heartbeat to Google server).
Tasker setup :
1. create new profile : Time
* uncheck both start & end time (so it starts and ends from midnight to midnight)
* check Repeat : every 6 minutes (during deep sleep, this 6 mins expands 5x to 30 mins)
2. add new task :
what you do in this task doesn't really matter, the point is to do something in a regular interval (I only use Alert Morse, so I know that the profile is still running)
GODSPEED !!!!
PS. :
if you're not familiar with Tasker, after installation you have to :
1. allow it as admin (system Settings > Device Administrators)
2. turn on its service (system Settings > Accessibility)
3. put it on auto-start list
Related
. I'd like some help to try and find a solution to this problem. It seems all instant messenger apps have very delayed messages most of the time.
Gtalk & Google+ messenger- are extremely unreliable for me. Up until about 3 months ago they worked flawless, I'd get notified of a message as soon as it was sent, be it on 4G or Wi-Fi. Now, 90% of the time I'll only get the message if I go into the app. And yes all settings and notification settings are turned on to sync. Sending is never an issue. And if I stay in the application messages are pretty reliable although not 100% reliable. I will get instances where it won't receive messages even when I'm in the app. My cell reception and router is always near perfect reception.
Whatsapp messenger more reliable in that messages will come through within a half hour if they aren't coming through. Although if I'm in the app its quite flawless. This app is much more unreliable when on Wi-Fi. With 4G its actually reliable. What I do notice though when going into the app with Wi-Fi and its not syncing up is that the up arrow on Wi-Fi will be flashing but no down arrow. Once the down arrow begins turning on everything works.
To note is that I have tried switching to a stock rom to no help, same things happen. Tried uninstalling all these apps, and done a clean install, still no help. I have other phones in the house, a galaxy S, and these apps all work the way they should on both 4G and Wi-Fi. So I know it should and can work. All my emails from Gmail come through just fine as do my Google+ notifications from people replying on posts. So any help will be greatly appreciated as I want to get to the bottom of this. Currently running on CM9 stock kernel, with uglc1 modem and newest boot loader.
Anyone? I can't be the only one with this issue...
I am having this problem on the stock radio, UGLC1, and XXKK6 too
I think its something updated within the Google Talk apps?
I started having the same issue after the OTA 4.0.4 came out.
Has anyone resolved this?
from what i have seen, its the google push service (used from gtalk, gmail, whatsapp, and every push app) that sometimes do some sleep..had this on my previous device also sometimes
when people say "before was working" "now is not working well anymore" it depends from how much attention u give to it...
the push service require a constant connection to the google services, sometime this connection hang or stops, usually after 10 minutes i can see this connection is restored and chat messages, mails, etc, come all together (or if u dont want to wait, disable and enable the conenction again, or disable/enable synch)
edit: SOLUTION here http://forum.xda-developers.com/showthread.php?t=2142503
I've had this problem for almost a year now.. Ever since I went from iOS to Andriod.. On my HTC.. What I noticed is when my phone goes into sleep it's all over, I guess it falls into a deep sleep.. When I awake it all message from all messengers comes flooding through. I thought maybe it was a software problem and all problems would disappear after upgrading to android 4.0 from 2.3.. But still the same.. Same as you everything works fine when the phone is alive, wifi or 3G.. So I was thinking its HTC and about to upgrade to Samsung S111 so touch wood that works ok..
online4yourmind said:
I've had this problem for almost a year now.. Ever since I went from iOS to Andriod.. On my HTC.. What I noticed is when my phone goes into sleep it's all over, I guess it falls into a deep sleep.. When I awake it all message from all messengers comes flooding through. I thought maybe it was a software problem and all problems would disappear after upgrading to android 4.0 from 2.3.. But still the same.. Same as you everything works fine when the phone is alive, wifi or 3G.. So I was thinking its HTC and about to upgrade to Samsung S111 so touch wood that works ok..
Click to expand...
Click to collapse
My nexus 4, does the same thing.. ANNOYING!
Hi guys,
I've searched the whole forum but I couldn't find any other thread about my problem.
When I connect my HOX to WiIF (Sitecom WL-370 - 300N Gigabit Dualband Router) everything works fine at first, but after a few minutes (5, or sometimes 15 minutes) I've got no Internet anymore but I'm still connected. Also WiFI Analyzer still detects the network. I've this problem both on 2.4 GHz as on 5 GHz. I've also tried switching channels.
The strange thing is, I can still receive a WhatsApp message but I can't send any, also I can't browse on the Internet or things like that.
After turning my WiFi off and on it works fine again for the few minutes..
Best Wi-Fi performance is turned on and the other devices at home haven't got this problem.
Anyone having the same problem or knows a solution?
I've got the same problem and it seems to be totally random. What i noticed is that my Google Play Store always stops working (no connection) shortly after i turned on the phone (~10 minutes). Switching Wifi off and on again doesn't seem to change it, i need to restart my HOX to get it working again while other apps connect just fine after turning Wifi off and on again.
Edit: Stock Vodafone ROM (1.28.161.9)
I have the exact same issue and i went through every setting in my router trying to fix this.
I would turn on my WIFI, connect to my home network, and start downloading. After a few minutes it'll either stop (the dl percentage not change) and then if i reload the market/youtube/browser or any app that users the net, it'll say no connection.
The weird thing about this is that it LOOKS like i am connected to wifi (in the notification bar).
This may be a separate issue, but i tried to turn it off and then on again to get around the issue. This time around i would try to connect to my home wifi and it'll just say 'Saved' and then the network would go out of range.
I am running Leedroids rom.
I might have found a solution:
Under Settings -> Wifi -> Menu -> Extended there is an option for Wifi Power Saving. After unchecking it all my connectivity problems are gone.
May be worth trying a static IP configuration, if you know enough about ip4 to do it. I've seen problems with android Wi-Fi since version 2.2 - if your router issues an indefinite dhcp lease, it can show exactly the symptoms you describe. Only a possibility but worth a try.
Sent from my HTC One X using XDA
I have the exact same issue - the wireless shows connected yet you cannot browse the Internet etc. I have also tried every setting on the Wireless AP without any success. Even tried static IP and that does not fix it either. Whilst other devices in the house are ok...
The weirdest thing is though it does not happen everywhere i.e. at other places like work (where at least the same type of AP is in use) or at my brothers' house (where he has a Linksys). This is pretty much the only thing that bugs me with the HTC - the only workaround I have found is to make sure that WiFi is kept on only at times when plugged in - this doesn't actually fix the issue but it does mean that the phone will disconnect the WiFi and get a new connection next time it wakes up - this way I find I get the problem much less than when I have it set to Always.
I might have found a solution:
Under Settings -> Wifi -> Menu -> Extended there is an option for Wifi Power Saving. After unchecking it all my connectivity problems are gone.
Click to expand...
Click to collapse
I already unchecked it but it didn't solved my problem
May be worth trying a static IP configuration, if you know enough about ip4 to do it. I've seen problems with android Wi-Fi since version 2.2 - if your router issues an indefinite dhcp lease, it can show exactly the symptoms you describe. Only a possibility but worth a try.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Also no success
I have the exact same issue - the wireless shows connected yet you cannot browse the Internet etc. I have also tried every setting on the Wireless AP without any success. Even tried static IP and that does not fix it either. Whilst other devices in the house are ok...
The weirdest thing is though it does not happen everywhere i.e. at other places like work (where at least the same type of AP is in use) or at my brothers' house (where he has a Linksys). This is pretty much the only thing that bugs me with the HTC - the only workaround I have found is to make sure that WiFi is kept on only at times when plugged in - this doesn't actually fix the issue but it does mean that the phone will disconnect the WiFi and get a new connection next time it wakes up - this way I find I get the problem much less than when I have it set to Always.
Click to expand...
Click to collapse
Yeah, exactly, I've got the same problem. At school I've got no problems with the WiFi. I already send a message to HTC and I'm waiting on there answer.
I have kinda the same issue.
Using a HOX and at work I'm connected to Wifi and I can browse. At my house I can connect to the wifi, my IP is right that I'm getting from DHCP (I even tried putting in a static IP) but I can't browse
I also have a HTC Sensation, same setup and it works. The sensation can browse at work and at my house.
Why would this be?
Tried all sorts of solutions, but the only one that works is disabling the N-band and only leave B and G. This means that your laptop won't connect with the faster N, but at least the HOX works (what's more important )
Well I tried broadcasting a separate SSID on the b/g interface only for the exclusive use for the hox but that hasn't made any difference...my workaround is to have tunein radio in the background streaming whilst surfing...if I get bored of that solution my next workaround will be to trade the hox for an s3 as much as I despise TW...
Sent from my HTC One X using xda premium
I tried all the bands "B, G, N" and nothing works. So tired of this crap. Think I might just get a S3
RenVilo said:
I tried all the bands "B, G, N" and nothing works. So tired of this crap. Think I might just get a S3
Click to expand...
Click to collapse
I was thinking to do the same but there is no chance in hell of me doing that after I compared my HOX with a display model at the phone shop. Pentile screen vs LCD on the HOX? HOX = Sharper and better whites - the white on the S3 is bluish and so obvious. Another thing also I noticed is that the aggressive auto brightness on the S3 is too much - you won't tolerate it and you will likely be forced to manually adjust all the time. That plus reading that the S3 goes through the battery like no mans business when on standby unless you turn off all the features and put it in power save mode (might as well buy a Nokia then) at least the HOX uses the Ninja core and actually does save your battery in standby mode.
Anyway - the reason I replied is that I found a workaround (note, workaround does not mean a fix) - I put in a wifi extender in an area where I tend to spent most of my time with the HOX - this has not fixed the problem per se but rather seems to have elevated it somewhat. Basically now if the HOX drops from the main offending AP it automatically gets hooked up on to the extender and carries on working! I say this because (and I saw this only twice so far) I realised that when the phones Internet connection stops and you load a new page it timed out and get page cannot be found but when I hit refresh it works again you do notice a 3-4 second lag (this never happened before the extender came into play). Not sure if anyone else has tried this but I got a Linksys/Cisco extender for £69 and so far at least it has given me a workaround. Of course your mileage may vary...so don't splash out on an extender and come and blame me if it doesn't work for anyone here...
I am also having this issue with my HOX has anyone found a fix for this?
i have tried everything listed and nothing works.
its weird though because i have NO issues on my home network, but my network in my apartment here and at work network i get this issue
!!
bbbbbbbbbbbbbbbbuuuuuummp any fixes??? this sucks !!!!
What versions of android you guys have? Stock, sense, vanilla android, ics, jelly bean? Because I didn't encounter this problem when running stock or ics custom roms. After I updated hboot to 1.31 and tried different jelly bean sense roms it appeared. I also tried some stock android roms (ice cold jelly and liquid smooth) and wifi seemed to work fine. So is this sense problem only?
Ot1s said:
What versions of android you guys have? Stock, sense, vanilla android, ics, jelly bean? Because I didn't encounter this problem when running stock or ics custom roms. After I updated hboot to 1.31 and tried different jelly bean sense roms it appeared. I also tried some stock android roms (ice cold jelly and liquid smooth) and wifi seemed to work fine. So is this sense problem only?
Click to expand...
Click to collapse
The only change for me is update to HBOOT 1.31 and then things started happening. Otherwise runnin 4.0.4.
No workaround so far, at least i have not founf a way.
Since I started using my Wonder I've had the clock set to use network values. Yesterday after battery pull it went out of sync and failed to correct the date and time. I can't seem to get it to sync. Tried several reboots, cleared caches and fix permissions, flight mode nothing works. Any ideas?
Sent from my Wonder
Best to set the time n timezone manually then only set to synch. network values...can't really rely on the Telco's value.
In my country my Telco's time is very similar to our Satellite TV provider...so been following it ever since.
The sync. may not be accurate and I sometime believe it is a GB bug coz I had faced it before using CM7 on my HTC Tattoo.
But on the W so far had not faced it...maybe a few minutes of variance.
Why dun you try to remove the battery and let the phone be totally out of power for about ten minutes or so like using a BBerry..
Power back on and let it self auto sync.
Sent from my GT-I8150 using xda premium
Tried pulling the battery and leaving it out for several minutes but still couldn't sync properly. It put me 2 days earlier and 3hrs late. I can't seem to force it to sync with the network.
Sent from my Wonder
the best solution (tested and approved to work)
clocksync from playstore
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&feature=search_result
and its great plug-in "TimeZoneDB for ClockSync"
https://play.google.com/store/apps/details?id=ru.org.amip.timezoneservice&feature=search_result
P.S. needs root access
Dont 4gt to hit the thanks button
i have searched every possible threads and browsed Google for hours to find for a solution. but i couldn't find any. i have a stable WiFi connection,yet, my whatsapp messages are delayed.( they are not delayed if i am using mobile data). if i send a msg now it takes forever to send it.moreover if someone send me a messsage , i receive it lately,probable 3,4 messages together. i have also noticed that my WiFi do not stay active when i use whatsapp.probably this is the reason my messages do not get sent instantly. the two small arrows in the WiFi bars disappears.which means data are not being sent or received.i have to open the play store or browse the internet to make the connection active. why is it that when i use whatsapp the WiFi connection becomes inactive but when i browse,WiFi is healthy? is there any way that i can force WiFi to stay active and connected when i am using whatsapp?or is it possible to increase the priority of whatsapp to use the max WiFi strength just like browsers and play-store? i really can don't care about battery if i can use whatsapp properly.is there any modded whatsapp apk which can force max wifi to stay active etc etc... i am really frustrated. any help is highly appreciated.
p.s: i have changed kernels, from Franco to trinity than Franco again, unchecked "avoid poor WiFi connections", set WiFi sleep policy to "never"
Sounds more like a problem with your WIFI router then the phone itself. Have you tried to reboot your router?
WIFI High performance widget might help you to keep the WIFI alive when screen off.
Playstore link: Here
Herman76 said:
Sounds more like a problem with your WIFI router then the phone itself. Have you tried to reboot your router?
WIFI High performance widget might help you to keep the WIFI alive when screen off.
Playstore link: Here
Click to expand...
Click to collapse
i hope it helps.i will report if the problem persists.thanks for helping
well..its not helping.still the msgs get delayed in sending and receiving.i have to browse the internet to send a msg.only then the msgs get sent... helpless here
Have you tried with other Wi-Fi networks?
Swype'ed on my CM10 Galaxy Nexus
mohaimed said:
i have searched every possible threads and browsed Google for hours to find for a solution. but i couldn't find any. i have a stable WiFi connection,yet, my whatsapp messages are delayed.( they are not delayed if i am using mobile data). if i send a msg now it takes forever to send it.moreover if someone send me a messsage , i receive it lately,probable 3,4 messages together. i have also noticed that my WiFi do not stay active when i use whatsapp.probably this is the reason my messages do not get sent instantly. the two small arrows in the WiFi bars disappears.which means data are not being sent or received.i have to open the play store or browse the internet to make the connection active. why is it that when i use whatsapp the WiFi connection becomes inactive but when i browse,WiFi is healthy? is there any way that i can force WiFi to stay active and connected when i am using whatsapp?or is it possible to increase the priority of whatsapp to use the max WiFi strength just like browsers and play-store? i really can don't care about battery if i can use whatsapp properly.is there any modded whatsapp apk which can force max wifi to stay active etc etc... i am really frustrated. any help is highly appreciated.
p.s: i have changed kernels, from Franco to trinity than Franco again, unchecked "avoid poor WiFi connections", set WiFi sleep policy to "never"
Click to expand...
Click to collapse
Did you tweak the Wifi parameters with your custom kernels (low latency mode)? Have you tried flashing back stock kernel to see if that fixes the issue?
not yet. but my question is if the wifi network was the problem then my brothers htc one x running ics and galaxy tab running gingerbread should also face this problem in whatsapp,ryt? but they dont.is it the rom i am using?do u think getting back to stock might help? any recommendations? i love xenon
I know exactly what you're talking about because I experience it as well. It doesn't matter what ROM, (stock, CM10, PA etc) kernel, (stock, Franco, Trinity etc) or what WiFi network I'm on (work, home, coffee shop etc) but whenever I'm on WiFi my messages in WhatsApp are delayed when the application isn't open. I've basically concluded it's the app itself that has a problem with WiFi. I have no fix, I just keep hoping that the next update will fix it.
The developer website isn't very helpful either. Basically suggesting not to use WiFi if the other fixes they suggest don't work.
http://www.whatsapp.com/faq/en/android/20887936
glitchexe said:
I know exactly what you're talking about because I experience it as well. It doesn't matter what ROM, (stock, CM10, PA etc) kernel, (stock, Franco, Trinity etc) or what WiFi network I'm on (work, home, coffee shop etc) but whenever I'm on WiFi my messages in WhatsApp are delayed when the application isn't open. I've basically concluded it's the app itself that has a problem with WiFi. I have no fix, I just keep hoping that the next update will fix it.
The developer website isn't very helpful either. Basically suggesting not to use WiFi if the other fixes they suggest don't work.
http://www.whatsapp.com/faq/en/android/20887936
Click to expand...
Click to collapse
but how come the other users of jellybean are not facing this problem?
mohaimed said:
but how come the other users of jellybean are not facing this problem?
Click to expand...
Click to collapse
No idea unfortunately
I know it was running fine for me on ICS, but I noticed it changed after JB. I run the version of WhatsApp offered directly from the website which I think is different from the Play Store, so I don't know if it was a version change, or something specific to JB.
If I know I'm going to be using WhatsApp I stay off WiFi. Not ideal, but it's the only thing I've done that's "fixed" it.
mohaimed said:
not yet. but my question is if the wifi network was the problem then my brothers htc one x running ics and galaxy tab running gingerbread should also face this problem in whatsapp,ryt? but they dont.is it the rom i am using?do u think getting back to stock might help? any recommendations? i love xenon
Click to expand...
Click to collapse
If you always had this problem since the day you bought the phone and on stock (not sure if you flashed a custom ROM right on the first day you owned it), probably not. But if whatsapp worked fine before and the problem was introduced after flashing a custom ROM/kernel, I'd say returning to stock will probably fix it.
Petrovski80 said:
If you always had this problem since the day you bought the phone and on stock (not sure if you flashed a custom ROM right on the first day you owned it), probably not. But if whatsapp worked fine before and the problem was introduced after flashing a custom ROM/kernel, I'd say returning to stock will probably fix it.
Click to expand...
Click to collapse
i have not tried using whatsapp in stock.i will probably try that.i will flash android revolution hd.thats based on stock,ryt? i will report soon.thanks for ur concerns
went stock. but the problem persists... is it a problem with whatsapp or jellybean???
mohaimed said:
went stock. but the problem persists... is it a problem with whatsapp or jellybean???
Click to expand...
Click to collapse
I've used whatsapp since day 1 I have my gnex. No issues whatsoever, not on ICS nor on JB. I also don't see this forum flooded with people complaining about whatsapp, so I'd say it's a specific problem linked to your whatsapp account and/or phone.
Petrovski80 said:
I've used whatsapp since day 1 I have my gnex. No issues whatsoever, not on ICS nor on JB. I also don't see this forum flooded with people complaining about whatsapp, so I'd say it's a specific problem linked to your whatsapp account and/or phone.
Click to expand...
Click to collapse
how can it be a problem in my whatsapp account?. and i would like to believe that its not a problem with the phone.if it was a problem with the phone than i guess other apps should face it too. dnt kno what to do
mohaimed said:
how can it be a problem in my whatsapp account?. and i would like to believe that its not a problem with the phone.if it was a problem with the phone than i guess other apps should face it too. dnt kno what to do
Click to expand...
Click to collapse
Beats me. However, with millions of users and billions of messages sent per day, things obviously can go wrong. Try contacting whatsapp support.
Petrovski80 said:
Beats me. However, with millions of users and billions of messages sent per day, things obviously can go wrong. Try contacting whatsapp support.
Click to expand...
Click to collapse
i agree things can go wrong.but not everyday.probably i will contact whatsapp support
I've used Whatsapp for a very long time, previously on an HTC Desire S and now on my GNex GSM and never had issues.... I'm on stock JB rom but I've tried several others with diff kernels and no probs whatsoever. Until today. Faced the exact same prob as the OP described (whatsapp msg's go thru or come very late on wifi but do so fine on 2G/EDGE - however everything else works just fine re gtalk msg's/browsing etc and whatsapp works fine too on my brother's SGS3 on wifi).
Was going nuts googling about it when my brother informed me that he'd changed the home ISP and now our wifi router was pumping out access from a new ISP's modem. So I tried switching back to the old ISP to test (swapped the cable modem that connects to our wifi router) and whatsapp works fine again. Then my brother switched back to the new ISP's modem and same problem for me on whatsapp! So we factory reset the router after upgrading it's software to latest from the manufacturers website and now, finally, whatsapp works fine for me on both ISP's modems.
Maybe you can try messing with your router (factory reset or look thru its settings or try another ISP input just to test?), maybe it will help. It's a strange issue though. (FWIW my router's a cheap one by TENDA and my phones wifi sleep policy is set to always on).
Guiding.God said:
I've used Whatsapp for a very long time, previously on an HTC Desire S and now on my GNex GSM and never had issues.... I'm on stock JB rom but I've tried several others with diff kernels and no probs whatsoever. Until today. Faced the exact same prob as the OP described (whatsapp msg's go thru or come very late on wifi but do so fine on 2G/EDGE - however everything else works just fine re gtalk msg's/browsing etc and whatsapp works fine too on my brother's SGS3 on wifi).
Was going nuts googling about it when my brother informed me that he'd changed the home ISP and now our wifi router was pumping out access from a new ISP's modem. So I tried switching back to the old ISP to test (swapped the cable modem that connects to our wifi router) and whatsapp works fine again. Then my brother switched back to the new ISP's modem and same problem for me on whatsapp! So we factory reset the router after upgrading it's software to latest from the manufacturers website and now, finally, whatsapp works fine for me on both ISP's modems.
Maybe you can try messing with your router (factory reset or look thru its settings or try another ISP input just to test?), maybe it will help. It's a strange issue though. (FWIW my router's a cheap one by TENDA and my phones wifi sleep policy is set to always on).
Click to expand...
Click to collapse
it helped..my brother changed those settings.i reverted it and nowwhatsapp is fine.. u r the maaannnn!!!!
mohaimed said:
it helped..my brother changed those settings.i reverted it and nowwhatsapp is fine.. u r the maaannnn!!!!
Click to expand...
Click to collapse
I knew it was something with the router
Swype'ed on my CM10 Galaxy Nexus
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
Update 2012-10-02:
OK, I have eliminated my firewall from the equation: obviously I can't necessarily just whack the work's firewall without consequences. Nothing's blocked, and all services on the phone seem to work.
As for other devices: I dug up my old Nexus One (Gingerbread, stock), and upgraded my Transformer Prime to Jelly Bean. Both do not show the error in logcat, and neither have the battery drain issue. Just for kicks, I checked the version of the Google Services Framework on all three:
Samsung Galaxy Nexus: 4.1.1-398337
ASUS Transformer Prime: 4.1.1-438695
HTC Nexus One: 2.3.6
Wanna bet there's a bug in 4.1.1-398337 that got fixed in 4.1.1-438695?
Further update:
I also tried the following with no success:
Delete app data for Google Services Framework (NOT RECOMMENDED!)
Remove Google accounts from the phone.
Re-add Google accounts to the phone.
Update: 2012-10-04
I think I found a workaround. It looks like it's a domino effect thingy that happens here:
1) I've got a Netgear N600 ADSL/Wifi router at home. On my 2.4GHz radio, I set up two access points: one for my stuff and one for guests. I made sure to delete the guest account from all my Wifi equipment to make sure there's no "fighting" or "flapping".
2) It appears that the phone ignores the Wifi-'stay connected while sleeping' setting, or the radio is broken. When the phone goes to sleep, it disconnects from Wifi.
3) When the phone disconnects from wifi, the Google Services Framework lose connection: this causes the phone to wake up.
4) When the phone wakes up, Wifi gets re-established. This makes Google re-connect.
5) The phone goes back to sleep and we return to step #2.
This causes a LOT of wakeups, lost connections and other crap. Since the phone doesn't lose connection when it's awake, it's fricken difficult to debug. Also, it's NOT a signal quality issue. My phone can be right next to the access point and it wouldn't help.
So, could you guys try different access point settings at home? I've heard WMM, QoS and some of the protocols could cause the Galaxy Nexus's radio in Jelly Bean to go a bit wonky.
-- Jan Gutter
jangutter said:
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
-- Jan Gutter
Click to expand...
Click to collapse
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Petrovski80 said:
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Click to expand...
Click to collapse
Nope, I checked that: there's no firewall. At work there is, but it doesn't affect my phone (services are not affected visibly). Google Talk works fine in both situations.
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Exactly the same
cricka15 said:
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Click to expand...
Click to collapse
Does anyone have solved this.. i have got exactly the same situation as Jan. No trouble at work but only at home.
Not affecting ASUS Transformer Prime
Nothing new here, except I also cross-checked with my ASUS Transformer Prime. There's no drain on it, and also no errors in logcat about GTalkService.
I'll post an update once I've checked my trusty old Nexus One out of storage, that'll happen next week, though.
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
sgtlange said:
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
Click to expand...
Click to collapse
Just take note: in general Wifi uses a LOT less battery than 3G. A better test might be to disable Wifi AND sync.
Jan
some decent insightful ideas here. My S3 on official stock based custom has bad drain over wifi. My google services framework version is the 4.1.1-438695 which isn't affected in your case so it's not that.
Better battery stats at first put google maps as the wakelock so I realised it's location service was left on so I turned that off. Then BBS varies and shows different apps and what not causing wakelocks but the drain remains the same.
My router is an Asus with custom linux firmware Tomato with a robust plethora of functions. I updated it yesterday and put the settings back closer to default. I'll have to try disabling WMM and QoS settings as their both already on at the moment. Also the kernel developer i'm on to quote: "Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets."
After leaving wifi on last night the drain still remains at about 10% per 3 hours. Compared to before it used to be almost 15% per 3 hours. BBS doesn't show wlan_rx_wake as the top wakelock as most common before as that's down to running for 8 minutes in 9 hours rather than the top around 45 minutes. Instead battery-monitor is the top at a little over half an hour in the 9 hours. Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Infy_AsiX said:
Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
Click to expand...
Click to collapse
Have you tried disabling the WiFi Power Save Mode on the S3? From this article:
http://www.s3forums.com/forum/galaxy-s3-general-discussion/1329-wifi-tip.html
1. Open up the Galaxy S3 phone dialer
2. Dial *#0011#
3. Look for the “ServiceMode” screen and press the left menu button
4. Select “WiFi”
5. You should see that the “WiFi Power Save Mode” button is “ON” – turn it “OFF”'
My colleagues with the same phone has serious battery drain until they use that.
Infy_AsiX said:
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Click to expand...
Click to collapse
I seem to recall that the Google framework sends/receives a keep-alive packet once every hour or so. LOTS of stuff in the Android framework keep TCP connections open from the server side because otherwise the service provider just kills them. Blame stateful firewalls.
What could be happening here is that the WiFi chip offloads a number of these functions from the main CPU: i.e. it's got a simple TCP offload stack that just queues data for the main CPU to wake up. If the WiFi chip receives a keep-alive TCP packet with no payload, it doesn't bother to wake up the CPU and just absorbs it. If the WiFi chip goes to sleep, rather, it never receives these, the connection dies and the CPU needs to wake up on timeout and re-establish everything (eating battery in the process). It's paradoxically cheaper to keep the WiFi chip running on full power, than to let it go to sleep. This is pure speculation, and only one of many scenarios that might fit the facts.
The S3 has the *option* to change the WiFi sleep-mode from aggressive (default) to a value that lets the entire system use less battery. The Galaxy Nexus doesn't: which means that it may, or may not have the sleep-mode built in. In any case, it seems my router can remotely trigger disconnects when the main CPU is off, and by switching settings on it, I managed to perform a workaround. Unfortunately the Galaxy Nexus (on Jelly Bean, at least) seems to have a serious bug in this respect, and other people are not so lucky: http://code.google.com/p/android/issues/detail?id=35352
It seems that the core issue (WiFi disconnect), causes a knock-on effect, raising Google Services Framework, Android OS and potentially anything that syncs's battery profile.
Jan
Getting good drain now 1% an hour compared to 3%. Seems setting WMM to auto rather than enabled in tomato fixed it. The night before I had it disabled as well as QoS and it was bad as well. I will test further to be certain what's the scenario.
I've got a second S3 that's been suffering as well. Having two to test makes testing much faster. The service menu power save mode off didn't help. It caused strange disconnects with WMM in all states. S3 wifi menu would state poor connection and wouldn't reconnect. Note the S3 already has strange disconnects to begin with I find but in this case it sometimes wouldn't reconnect. Also restarting the phone resets the power save mode to enabled.
Can't find any information on a difference between enabled and auto in tomato WMM. I'll be sure to keep testing.
Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
New Google Services Framework
Hey guys,
looks like Google Services Framework got a version bump on the latest Galaxy Nexus update: it's now listed as version 4.1.2-485486
This is for JZO54K (4.1.2).
It could be that they've fixed the knock-on effect (but the core issue is likely the same, since the radio code is apparently exactly the same).
Jan
I have this same wakelock on my evo 4g lte. Same log error exactly. Only on my works wifi. Problem is eliminated when running a Vpn on the phone. Only caveat Is all the free vpn services seem to disconnect after a period of inactivity.
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Rawi666 said:
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Click to expand...
Click to collapse
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
SpinTX said:
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Try lowering this value to 10 or 8 and see if it helps.
Rawi666 said:
Try lowering this value to 10 or 8 and see if it helps.
Click to expand...
Click to collapse
Thanks, will give it a shot. Also, because of your post, I discovered that toggling wifi on and off stops Google Services from draining. It will still drain, if your wifi is set to turn off, when the device sleeps. I really think you hit the nail on the head, discovering the source of the problem. It's an issue I have been trying to fix for a long time and your post at least got me to toggling the drain. So thanks again!
Sent from my SGH-T999 using xda premium
Would love to he root cause of this... I had the same problem on my s3 and now on the s4.with and without custom roms etc. The problem only is work, and I'm putting it down to some service that the work firewall or something blocks... Only solution I've come up with is turning off the wifi when I'm at work.. Else I get in excess of 15min /hour of wakelock.
All apps etc. Up to date, sync on/off, no difference, all "location" settings turned off.
I give up.
Wifi signal strength!
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
keltickal said:
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
Click to expand...
Click to collapse
A friend with the nexus 4 and same problem told me to try disabling Google hangouts (formally talk).. Apparently it keeps refreshing itself once ur signed in (and it signs in automatically)... Will experiment tomorrow at work where I get the problem.
Sent from my GT-I9500 using xda premium