Skip to content
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

"Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification or "1 app is active" – and needs to be enabled/toggled/disabled each time to revert #8659

Open
nabijaczleweli opened this issue Oct 5, 2023 · 4 comments
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@nabijaczleweli
Copy link

nabijaczleweli commented Oct 5, 2023

Steps to reproduce

  1. Settings -> Notification -> Background synchronisation -> Background Sync Mode: set to No background sync
  2. Settings -> Notification -> Notifications -> Enable notifications for this session: disable
  3. (I'm assuming "session" means device as a matrixism)
  4. Fully exit out of the app, make sure it's dead
  5. Next time it opens the startup will take a while with a throbber and "Importing your data"
  6. The persistent "Listening for notifications" notification appears
  7. OBSERVE: Settings -> Notification -> Notifications -> Enable notifications for this session: it's "disabled"
  8. OBSERVE: Settings -> Notification -> Background synchronisation -> Background Sync Mode: somehow set to "Optimised for real time"
  9. toggling "Enable notifications for this session" (and even "... for this account") doesn't kill the persistent notification or change the "Background synchronisation" mode
  10. Need to: Settings -> Notification -> Notifications -> Enable notifications for this session: enable (since this undisables the Background Sync Mode button)
  11. Need to: Settings -> Notification -> Background synchronisation -> Background Sync Mode: set to No background sync
  12. Need to: Settings -> Notification -> Notifications -> Enable notifications for this session: disable

Outcome

What did you expect?

My configuration is preserved.

What happened instead?

See above, steps 6-.

Your phone model

Sony Xperia Z

Operating system version

9

Application version and app store

1.6.6 [40106051] (F-fd6a45a3)

Homeserver

nabijaczleweli.xyz Synapse 1.93.0-1

Will you send logs?

No (I would've said yes to this but (a) even after enabling the rage shake it doesn't work, (b) "shaking my phone to make something happen" is demeaning bull shit I ideologically refuse to do, and (c) /rageshake doesn't work! it does on desktop, why did you remove it? what purpose does this serve?).

Are you willing to provide a PR?

No

@nabijaczleweli nabijaczleweli added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Oct 5, 2023
@nabijaczleweli nabijaczleweli changed the title "Enable notifications for this session" not nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification – and needs to be enabled/toggled/disabled each time to revert "Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification – and needs to be enabled/toggled/disabled each time to revert Oct 5, 2023
@kittykat kittykat added A-Notifications S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely labels Oct 27, 2023
@Massedil
Copy link

I'm also affected by this issue. Have you succeeded to reproduce the problem ?

@nabijaczleweli
Copy link
Author

Still reproduces consistently for me.

@foresto
Copy link

foresto commented Mar 6, 2024

+1

Element 1.6.12 from F-Droid
Android 10 (LineageOS 17.1)

@nabijaczleweli nabijaczleweli changed the title "Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification – and needs to be enabled/toggled/disabled each time to revert "Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification or "1 app is running" – and needs to be enabled/toggled/disabled each time to revert May 3, 2024
@nabijaczleweli nabijaczleweli changed the title "Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification or "1 app is running" – and needs to be enabled/toggled/disabled each time to revert "Enable notifications for this session" nominally-respected across restarts, but "Background sync mode" automatically reset to "Optimised for real time" – with the persistent notification or "1 app is active" – and needs to be enabled/toggled/disabled each time to revert May 3, 2024
@nabijaczleweli
Copy link
Author

I can repro this on a system so fresh you can't put it down to compat: LineageOS 21 (Android 14), im.vector.app 1.6.12.

If you select "No background sync", exit, then start again, you get the "1 app is active" thing in the notif drawer and it's Element:
Screenshot_20240503-150106_Element
and Settings -> Notifications -> Background Sync Mode is reverted to "Optimised for real time".
Setting it to "No background sync" again kills the activeness for one time, and then the next time it's the same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

5 participants
@kittykat @foresto @nabijaczleweli @Massedil and others