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

Removed function: ability to set custom sync/check frequency #1815

Closed
AUSITStuff opened this issue Jul 27, 2020 · 6 comments
Closed

Removed function: ability to set custom sync/check frequency #1815

AUSITStuff opened this issue Jul 27, 2020 · 6 comments

Comments

@AUSITStuff
Copy link

It appears that the ability to set custom sync/refresh frequency was removed in the move from latest RiotX to Element 1.0
We operate on an offline network without access to GCM/Apple Push and as such this meant the app was always up to date. Yes it came at the expense of battery but that's a trade off it was worth being in control of.
Is this functionality likely to be restored?

@ralaud
Copy link

ralaud commented Jul 27, 2020

I was searching this feature too. Live notifications are nice especially important for voice/video calls, but to slow down battery drain on devices without FCM this feature was very useful.

@ghost
Copy link

ghost commented Aug 15, 2020

For privacy reasons, no Google services are installed on my device, so I also would be very happy if this feature could be used again.

PS: Due to heavy battery drain I had to deactivate Element and told my friends to send me an XMPP message in urgent cases...

@dkm
Copy link

dkm commented Aug 19, 2020

That's indeed a real problem (no gapps here). I have to «force close» the app after each check. It would be nice to have at least a way to make it «offline».

@vibrys
Copy link

vibrys commented Sep 9, 2020

updated from riotx to element and stumbled upon battery drain problem. more: I have notifications off for the account and I have impression that battery gets drained - riotx didn't drain then.

@dkm
Copy link

dkm commented Sep 19, 2020

Not sure why you closed it? Is it fixed somehow or has it been considered as wontfix ? Could not find any reference elsewhere.

@mcg-matrix
Copy link

Looks like this was resolved in version 1.0.7 which brought along #2080 for #2055. It seems to work well on my devices with all parameter value combinations I've tested – just don't set "Sync request timeout" to anything larger than 59 (see #2169).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants