不要GCM CCS上游消息强制重新连接到网络GCM？ [英] Do GCM CCS Upstream Messages force a re-connection to the GCM network?
问题描述
我有GCM推送通知不能在Android设备上正确地到达一些问题。经过几天的研究，我发现，那Android设备使用心跳保持到GCM服务的连接。可悲的是，心跳似乎太高了，因此（从WLAN切换到3G时，例如）在Android设备可以（但并不总是如此）失去连接到GCM服务。
I am having some issues with GCM push notifications not arriving properly on Android devices. After days of research I found out, that Android Devices use a heartbeat to keep the connection to the GCM services. Sadly, the heartbeat seems to be way too high and thus the Android device can (but not always does) lose connection to the GCM services (e.g. when switching from WLAN to 3G).
有已经有很多讨论关于谷歌的产品论坛，但似乎不存在其他真正的解决办法不是使用像parse.com
There has been a lot of discussion about this problem on Google's product forums, but there doesn't seem to exist a real solution other than using a third party push service like parse.com
现在谷歌已经宣布了GCM云连接服务器，这使得Android设备上的应用程序通过GCM发送上行消息发送到第三方应用程序服务器。
Now Google has announced the GCM Cloud Connection Server, which enables Apps on Android devices to send upstream messages through GCM to a third party app server.
有谁知道，如果上游信息的使用强制重新连接到网络GCM当连接不可用？
Does anyone know if the usage of upstream messages forces a re-connection to the GCM network when the connection is not available?
推荐答案
我测试了这一点，它似乎不那么。但是，你可以强制的Android发送定期心跳通知发送以下广播意图：
I tested this and it doesn't seem so. But you can force Android to send a regular notifications heartbeat by sending the following broadcast intents:
com.google.android.intent.action.MCS_HEARTBEAT
com.google.android.intent.action.GTALK_HEARTBEAT
我从谷歌播放推送通知的应用程序定影液（我不是开发者）得到这个。
https://play.google.com/store/apps /details?id=com.andqlimax.pushfixer.noroot
这篇关于不要GCM CCS上游消息强制重新连接到网络GCM？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
