RiotX consumes huge amounts of battery

[Half-Shot]

I can't point my finger at any one reason for this, but anecdotally I've found RiotX to use a large amount of power compared to it's usage time. @anoadragon453 and @babolivier can confirm this as well.

For example, for around a hour of reported screen time, RiotX had taken 25% of the total power draw for that day.

(I am using the gplay build)

[anoadragon453]

Yep, made my phone only last 1/3rd of a day.

[Cadair]

I have not noticed this (using the F-Droid build)

[babolivier]

Can confirm, on my other phone installing and starting using RiotX made my battery life drop from around a day to less than 10h.

[Half-Shot]

I looked again after matrix sync this morning and it's used 6% of my charge so far today. This seems to be related to some background tasks the app is running, because a lot of the charge seems to be drained while the phone is idle.

The google play version isn't trying to sync, is it?

[lpulley]

My RiotX installation (from Google Play Store on Galaxy S8 running Android Pie) has been perfectly fine on battery life. 0.7% since about four hours ago, with very light usage.

[bmarty]

We just have fixed an issue (in v0.5.0 release): Riot was syncing continuously, even if when in background, when the network was back (ex: when exiting airplane mode).
It should be better now.

[progserega]

After update to 0.5.0-dev [10000500] (G-07fca092) RiotX begin "eat" 30% of battery.
This is occur after bad network connectivity. And continuous after network resume to good connectivity.

[shumvgolove]

Considering the fact that RiotX should replace old Riot™ we need to deal with this problem ASAP.

I am running pure LineageOS without GCM (or recently FCM?) and RiotX consumes at least ~30% of my battrry life (not to mention that this issue directly related to notifications, for example I receiving them with ~8 minutes delay or not receiving at all) that prevents me using RiotX in general. This is disaster for mobile phones. There is similar issues dating from 2016 that people experienced and still not fixed even at the end of 2019:

• #167
• #616
• #994
• #1066
• #1370
• #2220
• #3016
• #3180
• #3152
• riotX#27
• riotX#684

Taking into account that Matrix is good and actively developing IM alternative to XMPP (which lacks development for clients, not to mention XEP's, that you should check for both server and client), Signal (that requires phone number, centralized and not available in F-Droid (see this good article)) and Wire (which has shaddy Privacy Policy (see this)) we need to implement proper syncing solution which fixes both notification and battery issues.

Like what was mentioned in #3152 I think we should implement SSE (Server Sent Events), considering that PR for SSE is ready for review – matrix-doc#2108 and matrix-doc#2024 for reference.

[fbruetting]

Is this still true or can this be closed? I never experienced an energy issue in the last three/four months.