After a very disjointed and failure-ridden afternoon I’ve finally managed to get UnifiedPush working on Molly. The intention is to benefit from better battery life (over websocket). So, this really is a question to my more experienced peers: Have you noticed less battery drain after switching to UnifiedPush? If so, could you quantify how (roughly) the impact on your battery? (I’ll do likewise once I have observational data. I just thought it would be nice to compare.)
Interesting! I tried both websocket and Unified Push with Molly, but I couldn’t really spot a significant improvement in battery life with UP. But as it’s difficult to quantify on the MK it’s more of a perceived reality. I do know that the idea behind Unified Push is that it becomes more efficient the more apps are using it. So, my guess is that with only one app there will not be much of. a difference.
But I’m very curious about your experience!
OP here. One thing I’ve noticed is that message previews aren’t shown using InkOS using UnifiedPush. They used to be displayed using websocket. I’ve tried re-enabling notifications in inkOS and will see how it goes.
Let’s hope it’s not one step forward, two steps back.
Update 15.01.2026 There’s a bug in v7.68.5-1 of Molly. It’s the first unified app (combining Molly and Molly-FOSS). When UnifiedPush is enabled, Websockets should become disabled, but it stays open. This makes the app run very slowly and it drains battery. I’ve logged a bug report on github and in the meantime switched to the latest Molly-FOSS release (pre-unification) to support UnifiedPush v.7.66.x. It works well. Message notification preview lines are working again, too!
Will report back with findings and we’ll see if it’s all been worth it.
OP here. After setting up Molly to receive UnifiedPush notifications (instead of Websocket), I’d say I get about half a day’s extra battery. I stream via bluetooth for hours daily and when I’m not doing that, I’m always listening to a podcast with the built-in speaker on max. Throw in a few calls (cellular/Signal). With that I’m averaging about 3.5 days. Previously it was 3 days. Not at all bad. My iPhone would struggle to make to the end of day 1.
So, my experience is that enabling UnifiedPush won’t radically transform your life or use of the device, but neither is it insignificant e.g. approx. 17% battery saving in my case.
I had an issue with the display of notifications running inkOS, but disabling it via ADB and re-enabling it seems to have resolved it. Now, they’re as clean as a whistle.