New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages not delivered until signal is opened since upgrade to Android 6.01 #5578

Closed
leo-b opened this Issue Jul 19, 2016 · 13 comments

Comments

Projects
None yet
10 participants
@leo-b

leo-b commented Jul 19, 2016

I have:


Bug description

Since I upgraded to Android 6.01, incoming messages are only delivered when the app is opened.
I think I am suffering from the same problem as @sesse commented here

I did already try all steps suggested in http://support.whispersystems.org/hc/en-us/articles/213190487-Why-is-there-a-delay-in-receiving-messages-.

  • GCM ist working, the Play services monitor shows successful pings
  • Is doesn't matter if the phone is connected via Wifi or mobile data.
  • A reboot doesn't help
  • reinstalling Signal (with re-registering and reimporting data) doesn't help
  • other GCM push services like Whatsapp, Facebook or Hangouts work fine
  • clearing the cache and data of Google Play Services and Google Services Framework doesn't help

Device info

Device: Samsung Galaxy S5 (rooted)
Android version: 6.0.1
Signal version: 3.16.0

@gjallarhorn

This comment has been minimized.

Show comment
Hide comment
@gjallarhorn

gjallarhorn Jul 20, 2016

You did not write anything about battery optimizing features (which is usually the reason behind these problems). So have you:

  1. Whitelisted Signal in Doze (part of Android 6). See this link:
    http://www.cnet.com/how-to/stop-specific-apps-from-using-doze-on-android-6-0-marshmallow/
  2. Samsung have something called "power save" which I think should only be enabled when you really need to save all the battery you can. Whitelisting Signal in this does not help, so I recommend you to disable it instead.

gjallarhorn commented Jul 20, 2016

You did not write anything about battery optimizing features (which is usually the reason behind these problems). So have you:

  1. Whitelisted Signal in Doze (part of Android 6). See this link:
    http://www.cnet.com/how-to/stop-specific-apps-from-using-doze-on-android-6-0-marshmallow/
  2. Samsung have something called "power save" which I think should only be enabled when you really need to save all the battery you can. Whitelisting Signal in this does not help, so I recommend you to disable it instead.
@leo-b

This comment has been minimized.

Show comment
Hide comment
@leo-b

leo-b Jul 20, 2016

Whitelisted Signal in Doze (part of Android 6).
Samsung have something called "power save"

Did that. (Power saving mode is disabled, Ultra power saving mode is disabled, Signal ist whitelisted as app.) Just re-checked.

leo-b commented Jul 20, 2016

Whitelisted Signal in Doze (part of Android 6).
Samsung have something called "power save"

Did that. (Power saving mode is disabled, Ultra power saving mode is disabled, Signal ist whitelisted as app.) Just re-checked.

@sesse

This comment has been minimized.

Show comment
Hide comment
@sesse

sesse Aug 9, 2016

Here's something strange: Today, Signal got updated to 3.16.1, and it seems like the problem has disappeared; my phone now receives Signal messages while it's in my pocket with no issues at all. But there are no code changes from 3.16.0 to 3.16.1…?

sesse commented Aug 9, 2016

Here's something strange: Today, Signal got updated to 3.16.1, and it seems like the problem has disappeared; my phone now receives Signal messages while it's in my pocket with no issues at all. But there are no code changes from 3.16.0 to 3.16.1…?

@n76

This comment has been minimized.

Show comment
Hide comment
@n76

n76 Aug 9, 2016

If you look at the commit history you will see that a number of changes have been made along the way, just never released. When the version was bumped, and a new build released, those changes were, in effect, released.

n76 commented Aug 9, 2016

If you look at the commit history you will see that a number of changes have been made along the way, just never released. When the version was bumped, and a new build released, those changes were, in effect, released.

@sesse

This comment has been minimized.

Show comment
Hide comment
@sesse

sesse Aug 9, 2016

I looked at the commit history, and couldn't find any changes. Neither does “git diff v3.16.0..v3.16.1”. What git-fu am I missing?

sesse commented Aug 9, 2016

I looked at the commit history, and couldn't find any changes. Neither does “git diff v3.16.0..v3.16.1”. What git-fu am I missing?

@n76

This comment has been minimized.

Show comment
Hide comment
@n76

n76 Aug 9, 2016

Sorry, I was wrong. . . I was going by noticing the last check-in date as shown on the GitHub website occasionally changing. But when I actually do a "git diff" between 3.16.0 and 3.16.1 the only change appears to be the version code and version name in the manifest.

n76 commented Aug 9, 2016

Sorry, I was wrong. . . I was going by noticing the last check-in date as shown on the GitHub website occasionally changing. But when I actually do a "git diff" between 3.16.0 and 3.16.1 the only change appears to be the version code and version name in the manifest.

@Trolldemorted

This comment has been minimized.

Show comment
Hide comment
@Trolldemorted

Trolldemorted Aug 12, 2016

Contributor

my nexus 4 (CM13, Android 6.1) is affected too, but not always.

@leo-b does this always happen? i have the impression that disabling wifi or something like that is triggering this.

Contributor

Trolldemorted commented Aug 12, 2016

my nexus 4 (CM13, Android 6.1) is affected too, but not always.

@leo-b does this always happen? i have the impression that disabling wifi or something like that is triggering this.

@tecufanujacu

This comment has been minimized.

Show comment
Hide comment
@tecufanujacu

tecufanujacu Aug 13, 2016

Me too sometime I have the same problem.

@sesse some months ago I received the messages only opening Signal, I simply uninstalled and reinstalled it to partially solve the problem, now only sometime I don't receive some message until I don't open Signal.

Me too sometime I have the same problem.

@sesse some months ago I received the messages only opening Signal, I simply uninstalled and reinstalled it to partially solve the problem, now only sometime I don't receive some message until I don't open Signal.

@2-4601

This comment has been minimized.

Show comment
Hide comment
@2-4601

2-4601 Aug 15, 2016

Contributor

I had these a couple of times a month or two ago on 6.0.1. Haven't had since. Sounds like intermittent GCM issues.

Contributor

2-4601 commented Aug 15, 2016

I had these a couple of times a month or two ago on 6.0.1. Haven't had since. Sounds like intermittent GCM issues.

@d4l3k

This comment has been minimized.

Show comment
Hide comment
@d4l3k

d4l3k Aug 17, 2016

I've been having this occur pretty regularly on Android 7.0 preview 5.

d4l3k commented Aug 17, 2016

I've been having this occur pretty regularly on Android 7.0 preview 5.

@Hedaja

This comment has been minimized.

Show comment
Hide comment
@Hedaja

Hedaja Oct 4, 2016

Same problem here.
Honor 6 H60-L04
Emui 4.0
Andorid 6.0

All permissions are given. It's whitelisted from power saving. Notifications and everything is activated....

Hedaja commented Oct 4, 2016

Same problem here.
Honor 6 H60-L04
Emui 4.0
Andorid 6.0

All permissions are given. It's whitelisted from power saving. Notifications and everything is activated....

@Hedaja

This comment has been minimized.

Show comment
Hide comment
@Hedaja

Hedaja Oct 4, 2016

Forgot to mention that I had quite a few apps (also certain Google apps disabled) in an older issue someone reported that activating them solved the problem. So I'm trying that right now.

Hedaja commented Oct 4, 2016

Forgot to mention that I had quite a few apps (also certain Google apps disabled) in an older issue someone reported that activating them solved the problem. So I'm trying that right now.

@automated-signal

This comment has been minimized.

Show comment
Hide comment
@automated-signal

automated-signal Apr 3, 2018

GitHub Issue Cleanup:
See #7598 for more information.

GitHub Issue Cleanup:
See #7598 for more information.

@signalapp signalapp locked and limited conversation to collaborators Apr 3, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.