Closed fd0 closed 8 years ago
Just opened EDIT: and unlocked TS and received a message from 16 hours ago. Used the phone all day long expect for TS. Battery always 75%+ https://gist.github.com/6a868f5e04079c1f8e49
The other day was similar, though I opened TS only some hours after the message was sent https://gist.github.com/anonymous/c916ce1fb7ea807760d9
Maybe these information are already known. I've already posted them in #4070.
Needless to say that none of the usual explanations like using Titanium fits here. I wonder, whether it might possible to detect those situations automatically and fix it or request user action?
In my case the problem was solved with upgrade to TS 2.26.5. But i can't tell the reason, because PlayStore forced me remove some apps and i also upgraded some Google-apps at the same session. So it could have been:
I reported on this issue 18 months ago. I fixed it back then by reregistering. Haven't had the problem again since then.
Maybe this very broad and general ticket could be closed. I do not know if any of the other early reporters have seen the issue of missed/delayed messages again lately?
I support the idea to close this broad general ticket. I haven't had any delivery issues lately.
closing, please reopen if you encounter this again...
i also have this problem on the phone from my wife. (fairphone - latest updates) i tried everything/alot, gapp reinstall, google services to latest version, Push Notifications Fixer (changed nothing) .... - mobile internet working fine. also if the app is in foreground everything is fine. a few seconds after close - everything fine. but then after 5minutes or 2 or 30min , no messages
Just for the record: My Problem is solved, without changing something. The problem started in January last year out of nowhere. I know now, it was a GCM issue. The same day jnachtigall commented two weeks ago the problem was solved without changing something. All other GCM apps started working again too which did not work for the last year too. To make that clear again: I haven't changed any google settings or anything related on this phone since months, because I already gave up on this issue.
@Frankstar I think you should send the Signal debug logs from your and your wife's phone (See the point Debug logs under https://github.com/WhisperSystems/Signal-Android/wiki/Submitting-useful-bug-reports#how-to-capture-data)
well, thats weird. My Wife dont Update Apps she dont use - so there was an Update for Google+ and Gmail. I updated both and now its working without a problem on mobile data and wifi.
@Frankstar I've owned a Fairphone before, and part of what you describe sounds familiar to me.
After every update to, say, a new FP OS, my phone wouldn't connect to Play Services, so that Google Cloud Messaging wouldn't work. After a week or so, my phone would automatically connect to Play Services again. Before that, an update of an arbitrary existing app or the download of a new one would lead to a connection, so that Signal messages would be received again. See a post in the FP forum: https://forum.fairphone.com/t/phone-not-connected-to-google-play-services-after-every-reboot/6279
If the behavior reappears, you could enter *#*#426#*#*
in your FP's dialer to test whether a missing connection to Play is the root of the problem. If so, the phone would be to "blame", not Signal.
@AlfonsoMuskedunder Ok, but the Updade was months ago - it never connect on its own. Also the Apps worked in Foreground and we/she downloaded things from Play Store without a Problem. Anyway - i never blamed Signal for that behavior - but i like to Update "Threads" like this for others that run in similar issues.
Ty for the tip (*#*#426#*#*
)
When messaging a friend of mine via push, most messages are delayed a few hours. Background data is enabled. Sometimes messages are even not delivered at all or arrive in different order than sent. This also happens with messages other people send him, although I can exchange messages with these people without problems (delivered within a few seconds). He runs a Nexus 5 with the latest stock Google Android and is perfectly reachable via Hangouts the whole time.
Any idea how to debug this?