Forced phone locking to place notifications

[kikithegecko]

When my phone is unlocked and Tusky is not in the foreground, I've experienced the following behaviour: The phone freezes for a couple of seconds with the display going dark, then my lock screen appears with a new notification from Tusky. It seems to me that the app somehow wants to place a notification on the lock screen and therefore locks the phone.

I'm not sure if this also happens with Tusky in the foreground, I didn't pay attention on that. Also not sure if this issue arises when a notification is already there but I think not. Sorry for the vague info!

---

• Tusky Version: 2.2

• Android Version: 6.0.1

• Android Device: Fairphone 2

• Mastodon instance (if applicable): chaos.social

• I searched or browsed the repo’s other issues to ensure this is not a duplicate.

[charlag]

Hi! I don't think we do anything like that. Could it be that you have Ambient Display or something like that on and it dosesn't work properly?

[kikithegecko]

There's no Ambient Display setting in my display settings and I've not installed any such app. Also, Tusky is the only app which has this behaviour and I've been using this phone since its release with almost 900 hours of uptime.

[charlag]

It's super weird and I don't know why it may be happening. Not sure how to debug it either but we'll try looking into this.

[kikithegecko]

Thanks! Feel free to reach out if you need more info :)

[connyduck]

Getting more reports about this https://social.tchncs.de/@sumomi/100448010590162510
🤔

[kikithegecko]

Short update:

• This issue still occurs with Tusky 2.3
• When there is already a notification, additional notifications don't lead to this issue.

[Bugsbane]

Yeah, I'm getting this, too:

Tusky Version:
2.1

Android Version:
6.0.1

Android Device:
ZTE 951

Mastodon instance (if applicable):
social.tchncs.de

I also noticed that it seems to happen less when Tusky is in the foreground, and when there is already a notification. The person in the mastodon post linked to above mentioned that it happened when the phone was first loading / booting, which would also coincide with going from no Tusky notifications to the first one (as Tusky initially loads).

PS, It's happened for a few versions now, but I don't think this happened when I first started using Tusky. If you can link to some older APK versions that what are in FDroid, I can always try them and see if I can narrow down which version the regression happened in...

[charlag]

@Bugsbane sorry, did you mean "not on F-Droid"?
Besides versions available via F-Droid we publish releases here:
https://github.com/tuskyapp/Tusky/releases

[rhonda]

It indeed seems to be an issue specific to Android 6.0.1, for which there aren't updates anymore for phones. It happens to me too, unfortunately I don't have any other device and there is no newer android available for my beloved nexus 5.

[Tak]

Bug in Android 6.0.1