Skip to main content

mastodon - Link to source

I installed #Signal and #Conversations_im on a clean install of #GrapheneOS on my Pixel 4a and measured the battery impact. The results are shocking!

Both messengers had only one contact: my regular phone.

I used my regular phone to send messages to the Pixel 4a (which was not used for anything else over the course of the experiment).

I always sent the same message via Signal and #XMPP (mixing up which app went first). In total I sent ~32 messages in intervals of 10mins to a few hours.

Battery usage stats from an Android phone. The battery is down to 10% after 20 hours since last full charge. Signal has consumed 95% in that period and Conversations 5%
#xmpp #signal #grapheneos #conversations_im

FediVerseExplorer reshared this.

in reply to Daniel Gultsch

مسعود
mastodon - Link to source
مسعود
• •

Truly shocking.

What push mechanisms are you using for Signal and for Conversations?

in reply to مسعود

Daniel Gultsch
mastodon - Link to source
Daniel Gultsch
• •

@masoud Both have direct connections to their respective servers because #GrapheneOS comes without Play Services. Both apps prompted me for exemptions to "Battery optimizations" which I granted.

On the sending side I made sure (by looking at the double ticks ✅ ) that the messages were delivered instantly.

#grapheneos @مسعود
in reply to Daniel Gultsch

MattJ
mastodon - Link to source
MattJ
• •
I wonder if this is related to the bandwidth/power optimizations that XMPP clients/servers support (e.g. CSI) or just general app bloat.
@masoud
@مسعود
in reply to Daniel Gultsch

mathieui
mastodon - Link to source
mathieui
• •
This is in line with my experience with signal. I have revoked all battery optimization permissions and essentially allow my phone to insta-kill it once it goes to the background. I don’t receive messages unless I open it, but my battery last eons longer.
in reply to Daniel Gultsch

adb
mastodon - Link to source
adb
• •
I did some tests in the past as well and I remember #Conversations was one of the best apps on optimal battery usage, great work Daniel! 👌
#conversations
in reply to Daniel Gultsch

Remus
mastodon - Link to source
Remus
• •
Do you plan to make experiments with element, too?
I would expect Conversations to perform a lot better since matrix is known to be more heavy on ressources but i mention it because it feels like an obvious direct competitor
in reply to Remus

Daniel Gultsch
mastodon - Link to source
Daniel Gultsch
• •
@ikonoklast the thing about #Signal that it was at least reliable. Messages were delivered instantly (same as with Conversations). From what I've been hearing about Element is that it becomes notoriously unreliable when it’s working without an external push service. And then it obviously becomes hard to measure battery impact if the app is dead half the time.
But yes maybe. Signal vs Conversations was easy to pull off because I use both apps on a daily basis anyway. I don’t use #Matrix
#matrix #signal @Remus
in reply to Daniel Gultsch

iamreinder
mastodon - Link to source
iamreinder
• •
That seems quite significant. I have looked into hosting my own XMPP server in the past. I like the idea of a small non-bigtech chat platform for my inner circle. Unfortunately, the biggest challenge is to get people to switch their conversation with you over to a different app.
in reply to Daniel Gultsch

床井 一郎
mastodon - Link to source
床井 一郎
• •

So I suspect Signal has a wakelock problem as they haven't tested extensively on devices without Play services? The battery drain is running at almost constant speed.

Conversations is great. There's not much to modify/customise before getting it to run on my devices.

in reply to Daniel Gultsch

Sandro
mastodon - Link to source
Sandro
• •
Signal is probably not testing/optimizing for phones without Play Services.
in reply to Daniel Gultsch

Ichthyx
mastodon - Link to source
Ichthyx
• •
btw molly a signal soft fork have unified push support. So we can use correct software (Conversions) as a notify provider 👍
in reply to Daniel Gultsch

jr conlin —〰—
mastodon - Link to source
jr conlin —〰—
• •

Not really surprised.

The CPU and Radio on your phone are both high draw devices. It's why your phone wants to kill or sleep any program as soon as possible. FCM & APNS use carrier data (& no encryption) which use much lower power stuff.
Otherwise you get what you see, or worse)

That's why Firefox only does Push it we have access to native, but also why data is encrypted.

in reply to Daniel Gultsch

Râu Cao ⚡
mastodon - Link to source
Râu Cao ⚡
• •
While you're testing with GrapheneOS, maybe you could check if it keeps the connection open for longer when the phone is locked. Since a couple of months or so, I see 0 connections in the widget when unlocking my phone after a while, but then it reconnects quickly. However, the battery savings settings are the same as before and I don't know why it would disconnect otherwise.
in reply to Râu Cao ⚡

Daniel Gultsch
mastodon - Link to source
Daniel Gultsch
• •
@raucao Both apps had no problem maintaining their respective connections. Messages were delivered instantly (as indicated by double check marks + me hearing the notification when I happened to be in the same room as the test phone)
@Râu Cao ⚡
in reply to Daniel Gultsch

Râu Cao ⚡
mastodon - Link to source
Râu Cao ⚡
• •
I meant more like leave phone untouched for at least a few hours, then check.
in reply to Daniel Gultsch

gumnaam
mastodon - Link to source
gumnaam
• •
though I am sure Signal is more battery consuming than any other XMPP app, I am unsure if the difference is as dramatic as shown in this screenshot. There is 20% usage by Signal and 12% usage by Monocles on my phone.
in reply to gumnaam

Daniel Gultsch
mastodon - Link to source
Daniel Gultsch
• •

@gumnaam Note that in my testing I never actually opened or otherwise interacted with the apps. (I did make sure that messages got delivered though).

As soon as you start interacting with the apps or if/when they receive a different amount of messages your results get skewed (Screen time is obviously a big contributor to battery consumption)

@gumnaam
in reply to Daniel Gultsch

gumnaam
mastodon - Link to source
gumnaam
• •
my screen time shows 1 minute for both apps. So, I don't think the result should be THAT skewed.
in reply to Daniel Gultsch

Moritz
mastodon - Link to source
Moritz
• •
It's a well known problem: github.com/signalapp/Signal-An…

Signal consumes half of my battery (no google services or microG) · Issue #9729 · signalapp/Signal-Android

I have searched open and closed issues for duplicates I am submitting a bug report for existing functionality that does not work as intended I have read https://github.com/signalapp/Signal-Android/...
GitHub
in reply to Daniel Gultsch

Norbert Tretkowski
mastodon - Link to source
Norbert Tretkowski
• •
Known issue since years...
github.com/signalapp/Signal-An…

Signal consumes half of my battery (no google services or microG) · Issue #9729 · signalapp/Signal-Android

I have searched open and closed issues for duplicates I am submitting a bug report for existing functionality that does not work as intended I have read https://github.com/signalapp/Signal-Android/...
GitHub
in reply to Daniel Gultsch

Marek
mastodon - Link to source
Marek
• •
Mhh, Signal always keeps a connection to their server open for push messages. Maybe try Molly (Signal fork) with UnifiedPush and use Conversations as UnifiedPush provider.
in reply to Daniel Gultsch

n00b0ss
mastodon - Link to source
n00b0ss
• •
I use the @mollyim fork and it looks like that it does not use that much battery
Screenshot of the Battery Power usage charts TIDAL 37% Fairmail 24% Molly 6 % Tusky 5% Element 4%
@Molly
⇧