Related
Hey guys,
Tried searching for this, but nada.
Anyone else having issues with your phone being idle but powered on ans upon bringing on the screen you receive a google talk notification that's old? Is been happening to me lately, and I can't tell if it's the phone or the fact that my desktop version is intercepting the message and preventing the phone notification.
I'm tempted to no longer use the desktop built in gmail version, but I wanted to see if others are having similar issues.
Thanks in advance!
Sent from my HTC One X using xda premium
Can't guarantee this, but I have a feeling it may have something to do with the phone letting the Google talk process close when the phone is in it's sleep state. I've noted that I keep having to re sign in to gtalk when I wake up my phone and suspect that it is an issue with the horrible multitasking that HTC has bundled into sense 4.0.
I assume both of you also get delayed notifications with push email using the native Gmail app? I also frequently get logged out of Google Talk when I put the phone in standby mode. When I am logged out of Google Talk, my push emails are delayed in the Gmail app until I log back into Google Talk.
So it seems to be some problem of getting disconnected from google services when the phone is asleep.
I don't think i've been getting delayed notifications, but I do notice that my chat gets out of order a lot. My replies will be above whoever is talking to me no matter what order each was sent in.
Almost every phone that comes out gets a google talk going eventually so there is lots out there, but each phone has it's own issues. Here is a thread that was pretty good from the Galaxy Nexus Forums.
http://forum.xda-developers.com/showthread.php?t=1400367
With the HOX I have had issues with Google Talk not working great when the wifi is dropping, so this might be part of the wifi issue that pretty much everybody is having with this phone. The wifi stays connected but seems to go to sleep so your phone only gets the notification once it is woken up. Try turning off the wifi and seeing if you have the same problem.
As for Google Talk, there are some oddities that go along with using it on multiple devices. Here is some stuff I figured out playing around with it on multiple devices and computers at the same time. (I posted this in the GN forums as well)
"Google Talk is my main means of communication it seems so I have played with it a lot. Here are my observations.
1. To keep it "up" all the time in the Talk App hit the menu button (three dots now) >settings>uncheck automatic away status. Also make sure your phone has automatic syncing turned on for your gmail account: Setting>Accounts and Sync>ON (for your chat gmail address anyway). Additionally make sure your mobile data is turned on if you are ever off wifi: Settings>More>Mobile networks>Data Enabled (checked to turn on)
2. You can have up to 6 devices linked to your talk account at once, after that they just stop working.
3. When you receive a IM it appears on both your phone and your gmail account. If you start typing on the gmail account (or G+) it hijacks the whole session and you phone no longer gets the notifications, but the conversation still shows up on the chat window on the phone. When you are done with the IM session make sure you close the window on gmail (or G+) and send one last message from your phone or tablet to take the session back over, if you don't your phone will not receive future chat notifications. You can also just log out of your gmail/G+ session and it will automatically return everything to your phone/tablet but who ever does that?
4. To figure out how it all worked and tinker with it I use both of my gmail accounts and chat back and forth with them. You can do it from separate browsers or just open an incognito window in Chrome and log into your other gmail account. I would recommend this so you can see all of this stuff in practice.
Good Luck, hope this helps"
Gtalk and gmail delays
Hi all,
I have performed tests and discovered that if i disable WiFI and only use the phone's data connection "4g" or LTE that i receive all my messages with no problem even when the phone locks/goes to sleep. However if i leave wifi turned on, within 5-10 seconds i stop receiving them and will only receive them when i wake up the phone/unlock or wait for the delay which can be anywhere from 5-15 mins.
Trying to figure out a way to by pass this, but can't seem to figure it out. I don't want to keep my wifi off when i'm at work or home so i don't use data as i have 3GB and not unlimited so it kind of sucks that i have to keep wifi off for now. Any thoughts/ideas would be great, thanks.
k0sun7eash3d said:
Can't guarantee this, but I have a feeling it may have something to do with the phone letting the Google talk process close when the phone is in it's sleep state. I've noted that I keep having to re sign in to gtalk when I wake up my phone and suspect that it is an issue with the horrible multitasking that HTC has bundled into sense 4.0.
Click to expand...
Click to collapse
This. I have issues with timely/accurate reception of notifications from GV. I only use my account for voicemail, but typically I only get voicemail notifications if I open the actual application (which I do because my gmail account receives an email notification now, as well). Sometimes I notice GV as a running task, but often times not, so to me it seems that (possibly) multitasking or some other form of process management in ICS or Sense is not prioritizing the GV process and it's associated actions. I dont mind the aggressive multitasking, but it would be nice to have the option of protecting some processes, such as GV.
I removed google + app completely with titanium backup, and the problem is gone., I get the messages immediately
Push Notifications Fixer can fix it
xda http://forum.xda-developers.com/showthread.php?t=2142503
play store https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer
I'm running the latest Viper, I've never had an issue receiving or sending msgs. The only time the phone won't alert me is if I am actively typing in the browser window.
I'll note though that I never have wifi on, it's always on the mobile network.
andQlimax said:
Push Notifications Fixer can fix it
xda http://forum.xda-developers.com/showthread.php?t=2142503
play store https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer
Click to expand...
Click to collapse
I tried everything not even this works for me
Same problem, screen off - phone disconnects, unlock the phone - messages start to appear
Same problem on 2 different phones and 2 different numbers
I don't use G Talk, but I see the same thing with G Voice. I almost never get voicemail notifications on my HOX (they show up instantly on my old GNex). I blame Sense (for this and other things).
Same problem, but with Nexus 4 when I am on WiFi. With data connection, it works without problems.
FEATURED by Whatsapp Support Page
Hi everyone,
Are you experiencing delayed push notifications from GTalk/Hangouts, GMail, Whatsapp (partial fix), Facebook, Play Store web install, etc? If so, then this app its for you!!
It's FREE! No banners. No ads. Please consider donating to the developer (link in the app).
This app work for EVERY phone. ROOT is NOT required
Root version here: http://forum.xda-developers.com/showthread.php?t=2142503
This app basically keep alive the push connection on your phone. It avoid the tcp connection timeout that can occurs on some wifi routers or on some mobile carriers.
You will always receive instantly push notifications.
● Why were my notifications delayed in the first place?
Apps using Google's push service (Hangouts, Gmail, Facebook Messenger, e.g.) connect your phone to Google’s servers via one TCP connection (on port 5228).
To keep this connection alive, Android uses a periodic heartbeat to prevent the connection from timing out. By default, this heartbeat occurs every 15 minutes on wifi and every 28 minutes on a mobile data connection.
This is problematic because most Wi-Fi routers and mobile carriers will automatically terminate this connection after a short time of inactivity.
Because your phone is not aware that this connection was externally closed, you will not receive push notifications until this connection is reestablished when the next heartbeat is sent.
● How does PNF solve this problem?
Every x minutes it invoke an android activity that will send an heartbeat network packet on the push connection. Sending an heartbeat every 5 minutes should be enough to always keep the connection alive and all your push notifications will be instantly.
The battery should not be much impacted over a day.
Download here: PLAY STORE LINK (or get the attached APK in case not available on your country for some reason)
Please, if the are problems don't rate bad, send me an email ( [email protected] ) or post the problem in this thread and I'll answer you as soon as possible.
Feedback are welcome!
Changelog:
See post Number 2
FAQ:
See post Number 3
Report to google here: https://productforums.google.com/fo...onnecting-to-networks-and-devices/fslYqYrULto
Download it from play store to receive future app updates
Changelog:
Version 2.5, 2016/09/10:
- Small update. Soon new things!
Version 2.0, 2015/06/30:
- Fix PNF auto-startup after phone reboot
Version 1.5, 2015/01/04:
- Material design for android lollipop
Version 1.1, 2014/03/06:
- Fix app not autostart at network changes on some phone
- The app start at phone boot itself, no need to start it or do anything
Version 1.0, 2013/11/05 :
- First release
FAQ
Q: Does this app drain battery in background? Does lowering the heartbeat interval too much cause more battery drain?
A: It should have not a big impact on the battery during your daily use. I recommend hearbeat set to 5 minutes, it should be enough to make you receive instantly notifications.
Q: What does mean "set the heartbeat to x minutes" ?
A: It means only that android will send a network packet over the push connection every x minutes instead of the default 15/28 minutes to keep alive that connection. It does NOT mean that you receive push notification every x minutes. Notifications are instantly if the push connection is alive.
Q: Why Whatsapp messages are still delayed sometimes?
A: Whatsapp, and some others apps, don't completely rely on google push service (GCM). Those apps start their own connection when you open the application, and the messages come through this connection. The heartbeat is sent by android only on the push connection on the port 5228, and so it only keep-alive that particular connection. Blame those apps that doesn't have a keep-alive mechanism for their connection or that doesn't use full push messaging.
A workaround for whatsapp is to swipe it away from the recent apps when your finished a chat session. In this way it's connection is dropped and you will be notified of new messages through google push notifications.
I start seeing some download, but few stars.. Come on show your gratification with 5 stars
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
How?
Hi, Im using your application, the root one.
But I'm interested in how this one works.
I recently developed an app that use GCM to send messages between devices.
If you can answer me... How do you send the heartbeat through an Activity? This can help a lot of people since Google don't do anything.
Thank you
Hitsbam said:
Hi, Im using your application, the root one.
But I'm interested in how this one works.
I recently developed an app that use GCM to send messages between devices.
If you can answer me... How do you send the heartbeat through an Activity? This can help a lot of people since Google don't do anything.
Thank you
Click to expand...
Click to collapse
Basically to trigger an heartbeat you only need those 2 lines (those are undocumented, I it discovered by decompiling GSF):
Code:
context.sendBroadcast(new Intent("com.google.android.intent.action.GTALK_HEARTBEAT"));
context.sendBroadcast(new Intent("com.google.android.intent.action.MCS_HEARTBEAT"));
where context is the application context.
Those intents will be "catched" by GoogleServicesFramework (GSF) that will physically send the heartbeat packet to the google servers. If an aswer come back instantly the push connection is alive, otherwise if in 60 seconds there is no answer back, GSF will initiate a new push connection without to wait the next heartbeat.
The first intent is for Ice Cream Sandwhich and below "I think", while the second one is used in new android versions, should depend from the GSF version installed..But you can safety fire both, since one of the two won't just do anything.
Not sure if it is a good practice to place it inside an application, since if every developer will do that the battery will be killed. Maybe you can invoke that only in some situations.
andQlimax said:
Basically to trigger an heartbeat you only need those 2 lines:
Code:
context.sendBroadcast(new Intent("com.google.android.intent.action.GTALK_HEARTBEAT"));
context.sendBroadcast(new Intent("com.google.android.intent.action.MCS_HEARTBEAT"));
where context is the application context.
Those intents will be "catched" by GoogleServicesFramework (GSF) that will physically send the heartbeat packet to the google servers. If an aswer come back instantly the push connection is alive, otherwise if in 60 seconds there is no answer back, GSF will initiate a new push connection.
The first intent is for Ice Cream Sandwhich and below "I think", while the second one is used in new android versions, should depend from the GSF version installed..But you can safety fire both, since one of the two won't just do anything.
Not sure if it is a good practice to place it inside an application, since if every developer will do that the battery will be killed. Maybe you can invoke that only in some situations.
Click to expand...
Click to collapse
Thanks a lot.
Your right, if every developer use it then can turn in to a problem.
I'm not going to use it, only in the start of the app if the users reports me problems. But first i'm going to suggest your application, i think is a better solution by the moment :good:.
Thanks for satisfy my curiosity.
PNF root reached 50.000+ downloads!
PNF no-root need more advertising..Share it to people may need this app and give 5 stars!
Great app :good:
I'm new with android. How can I swipe whatsapp away from the recent apps in settings when I finished a chat session?
Thanks in advance
lefty68 said:
Great app :good:
I'm new with android. How can I swipe whatsapp away from the recent apps in settings when I finished a chat session?
Thanks in advance
Click to expand...
Click to collapse
Depends from your phone I think, just launch the recent apps list and remove / swype whatsapp from there..
On the Nexus phones there is a dedicated on screen button to open the recent app list, on some Samsung phone I think you can long press the home button.
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
andQlimax said:
Depends from your phone I think, just launch the recent apps list and remove / swype whatsapp from there..
On the Nexus phones there is a dedicated on screen button to open the recent app list, on some Samsung phone I think you can long press the home button.
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
Click to expand...
Click to collapse
On Huawei g300 phone I can long press the home button to open the recent app list too, but it seems like in android 2.3.6 I can't swipe apps away. Any alternative action?
andQlimax said:
Basically to trigger an heartbeat you only need those 2 lines (those are undocumented, I it discovered by decompiling GSF):
Code:
context.sendBroadcast(new Intent("com.google.android.intent.action.GTALK_HEARTBEAT"));
context.sendBroadcast(new Intent("com.google.android.intent.action.MCS_HEARTBEAT"));
Click to expand...
Click to collapse
Hi, I'am using the same method in my product.
Can we reach an agreement how to reduce the frequency of these intent calls?
I have no idea to realize any heartbeat timeout settings in my app (hard policy).
I can't listen for these intents cause it requires com.google.android.c2dm.permission.SEND permission that can't be acquired.
For example, can you send some additional broadcast intent (w/o permissions) when fire heartbeat?
I'll listen for it and reset own alarms to not to do the same action.
dd00_xda said:
Hi, I'am using the same method in my product.
Can we reach an agreement how to reduce the frequency of these intent calls?
I have no idea to realize any heartbeat timeout settings in my app (hard policy).
I can't listen for these intents cause it requires com.google.android.c2dm.permission.SEND permission that can't be acquired.
For example, can you send some additional broadcast intent (w/o permissions) when fire heartbeat?
I'll listen for it and reset own alarms to not to do the same action.
Click to expand...
Click to collapse
I have to check, there is an other intent directly fired by android which indicate that an heartbeat has been sent, you can listen that intent I think
I don't remember it right now what, I will check tomorrow maybe and will let you know
dd00_xda said:
Hi, I'am using the same method in my product.
Can we reach an agreement how to reduce the frequency of these intent calls?
I have no idea to realize any heartbeat timeout settings in my app (hard policy).
I can't listen for these intents cause it requires com.google.android.c2dm.permission.SEND permission that can't be acquired.
For example, can you send some additional broadcast intent (w/o permissions) when fire heartbeat?
I'll listen for it and reset own alarms to not to do the same action.
Click to expand...
Click to collapse
@dd00_xda
It seems there isn't an android system intent that you can listen to check if an heartbeat has been sent.
About your request to send some broadcast intent in my app, what will be the advantage for you? I mean, if you already need my app installed, then you don't need at all your own alarm..My app by default send and heartbeat every 5 minutes for example (the alarm will start every time a connection is made) and in that way the push connection is already alive..and every notification you app need to listen, it will always being received
Thanks very much for creating this app! I have a question about it.
I previously had a Samsung Galaxy S3 running Android 4.1.2. Push notifications worked fine over Wi-Fi when I was at home.
I have now switched to a Nexus 5 running Android 4.4. I'm still using the same router at home, but I'm getting an issue with notifications being delayed. Sometimes I will not get any notifications for a while, then a bunch will turn up at once from different apps.
Does the issue I've described sound like it's related to the problem that this app is designed to fix? If so, how come everything worked fine with my S3 with the same router?
Many thanks!
funksoulbrother said:
Thanks very much for creating this app! I have a question about it.
I previously had a Samsung Galaxy S3 running Android 4.1.2. Push notifications worked fine over Wi-Fi when I was at home.
I have now switched to a Nexus 5 running Android 4.4. I'm still using the same router at home, but I'm getting an issue with notifications being delayed. Sometimes I will not get any notifications for a while, then a bunch will turn up at once from different apps.
Does the issue I've described sound like it's related to the problem that this app is designed to fix? If so, how come everything worked fine with my S3 with the same router?
Many thanks!
Click to expand...
Click to collapse
maybe the issue is that the device loose the network while the screen is off? that's a common problem on some device, it is not fixed by PNF
andQlimax said:
maybe the issue is that the device loose the network while the screen is off? that's a common problem on some device, it is not fixed by PNF
Click to expand...
Click to collapse
Thanks for the reply!
Do you have any recommendations of how I could troubleshoot this issue? I really don't know what the cause is - I just know it happens, and if it was a widespread issue with the Nexus 5 then a lot more people would be talking about this issue. I've only seen a handful of folks mentioning it.
Thanks again.
funksoulbrother said:
Thanks for the reply!
Do you have any recommendations of how I could troubleshoot this issue? I really don't know what the cause is - I just know it happens, and if it was a widespread issue with the Nexus 5 then a lot more people would be talking about this issue. I've only seen a handful of folks mentioning it.
Thanks again.
Click to expand...
Click to collapse
if the phone disconnect from the wifi while the screen is off (happen also with only some routers sometimes), you usually should see the phone reconnect as soon as you wake the screen..if you pull down the notification bar and open the toggle switch, you should see the wifi icon orange (no connection to google server) and in few seconds become white again (connected).
andQlimax said:
if the phone disconnect from the wifi while the screen is off (happen also with only some routers sometimes), you usually should see the phone reconnect as soon as you wake the screen..if you pull down the notification bar and open the toggle switch, you should see the wifi icon orange (no connection to google server) and in few seconds become white again (connected).
Click to expand...
Click to collapse
Thanks again.
I don't believe the Wi-Fi is disconnecting. I can ping the device when the screen has been off for ages and notifications do come in when the screen is off - they're just delayed and sometimes I don't get a notification at all, yet I'll get an email notification on my PC.
funksoulbrother said:
Thanks again.
I don't believe the Wi-Fi is disconnecting. I can ping the device when the screen has been off for ages and notifications do come in when the screen is off - they're just delayed and sometimes I don't get a notification at all, yet I'll get an email notification on my PC.
Click to expand...
Click to collapse
that's strange...anyway my nexus 5 is arriving, I will do some tests and see if PNF is working correctly on KitKat
Apps not working when connected to WiFi.....apps background sync doesn't work when connected to WiFi......please help me....I am using stock android
Probably an issue with your WiFi. Can you open a browser? Does it work?
Browsing works....but the background sync doesn't work
amitkapate said:
Browsing works....but the background sync doesn't work
Click to expand...
Click to collapse
What do you mean by apps don't work on Wi-Fi? Also, the apps that don't sync, which ones and is back getting syncing enabled.
Sent from my Nexus 5
Delete and re-install it...
Means the I get Facebook notifications when mobile n/w is on.....but when I connect to WiFi there is no notifications.... Same with whatsapp also
BAckground Apps IsSue
amitkapate said:
Means the I get Facebook notifications when mobile n/w is on.....but when I connect to WiFi there is no notifications.... Same with whatsapp also
Click to expand...
Click to collapse
Hello, I have recently started having the same issues with my F6 not being able to load any background data as well. I believe your solution can lye within the apps that are being used. I Use a stock ROM too for my phone as there are no others out yet for it, and so, I also use ROM toolbox. This morning i could not for the life of me remember what i was doing to make the phone function this way, but remembered that i was dabbling with the DNS and server operations on ROM toolbox the night prier. I was a bit frustrated that there was no easy answer posted anywhere online (google) and had to figure it out myself.. (not so bad) . and since i have been constantly figuring out my ROMS abilities on STOCK I have acquired much knowledge for the F6 root and recover operations. IF you are having problems with any data being transmitted between apps and have been disabling ads through ROM toolbox be sure to make the right changes. For when you wake up to having no data app connection and your clearly connected to the internet it can become jarring.
hope this helps
Hi there,
I recently got a Z3C and rooted it, then upgraded back to 23.4.A.0.546. I removed some apps that I dislike with Root App Deleter and installed my other favorite apps, including AdAway.
Now, the issue I experienced since the first boot is that all apps are not receiving notifications in real time, I have to open the app to "stimulate" to fetch stuff.
So for example if my phone is in stand-by and I don't turn it on, no WhatsApp messages are received. I actually think I receive nothing until I open the app itself, and also when I am writing, it seems like the app is having troubles at getting online and delivering as it shows a waiting mini-icon on messages instead of instantly delivering them.
I am pretty sure this is not due to the rooting, maybe AdAway could be involved, but it's probably something that changed from Android 4.4 to 5.1, as I had same set of apps on 4.4 (Z1) without problems.
I checked that apps are allowed background traffic, and they are. I also get this problem on either HDSPA or wifi.
Any thoughts/ideas? Thanks in advance!
Hi,
Wondering if anyone has run into the following issue with their Pixel. My phone is an international model (G-2PW4200) and I bought it exactly a month ago.
The issue is this: I seem to never be able to download any decent size file (e.g. a video on social media sites or apps like Facebook, YouTube, Whatsapp, etc., or to download any app on the Google Play store) via WiFi without the download getting "stuck" half way, sometimes not even at 10%. The download would get stuck indefinitely, and only resume once I disable WiFi and start downloading via LTE. Sometimes it also comes back if I just disable WiFi and enable it again. Another problem I have is that my phone seems to go offline when it's not being used for extended periods of time (that being in the 5-10 minute range given I look at it almost every 10 minutes) despite having WiFi during sleep set to be always on. I can tell this because when I try to log in to something like Whatsapp Web it complains that my phone is offline, and this is a problem that never happened with me with my previous phone in the same setting.
A few points to keep in mind:
1- I have "Keep WiFi on during Sleep" set to "Always"
2- This happens everywhere (at home, work, friends', public WiFi, etc.) so it's not related to just my router's setup, and it happens every single day and almost every single time.
4- System is "up to date" and I have the latest update installed (Android 7.1.1, build NOF26V)
3- I'm still able to browse web pages (via Chrome), and browse apps like Facebook, Whatsapp, etc. without getting interruptions or showing any signs of disconnect. It's only the above two issues that I see when downloading big chunks of data, and for some reason my phone appearing to be offline during sleep when it shouldn't be.
Any idea what may be wrong here and how I can fix this? I really would like to keep this phone, but this is really becoming frustrating.
Thanks.
Have you factory reset?
mngdew said:
Have you factory reset?
Click to expand...
Click to collapse
Yes. And ironically enough I ran into the same problem immediately while restoring my backup as the phone was trying to redownload the previously installed apps. It would get stuck not downloading anything but not complain about a lost connection until I disable WiFi and switch to cellular data.
This reminded me that the first time I ran into the problem was also the very first time I used the phone when also downloading my apps.
contact google and get warranty service
can you test your wifi performance with another device?
and also try some download manager like ADM and check download with it.
Geeks Empire said:
can you test your wifi performance with another device?
and also try some download manager like ADM and check download with it.
Click to expand...
Click to collapse
Given that this happens everywhere, not just with my home WiFi, I know the issue is specific to my Pixel. Unfortunately no one at work has a Pixel to try it, but all other devices connected to the same WiFi spots are fine.
I was told by someone that disabling LTE and sticking to 3G cellular data will fix my WiFi issues. Will be trying that at work today.