View Single Post
Posts: 248 | Thanked: 1,142 times | Joined on Dec 2014 @ Earth
#2044
Originally Posted by alfmar View Post
Sailfish is a true multitasking system (I clearly hear Apple fanbois woohooing). Sailfish doesn't enforce memory/network/CPU/background limits, thus an app could actually waste 100% CPU cycles even in background.

Native Sailfish apps have to be well-behaved. Currently it's easy to spot a new app wasting resources for no reason... because most of native apps are actually well-behaved (thanks also to Qt/QML).

With the exception of old batteries (many hundreds of recharge cycles), if Sailfish wastes too many milliamperes then most probably you have to blame some Android app.
I confirm, in my past experience with a Jolla 1, Android has always been the most awefull power-hungry explanation of battery drop.

Worst offenders seemed to be online chat application.

I've mitigiated by :
  • Switching Facebook, Messenger and Skype, to Facebook Lite, Messenger Lite and Skype Lite (that last one might not be available on the Play Store in your territory, you might need to get it from apkmirror). Saddly no such thing as official WhatsApp Lite, yet.
  • in Settings -> Apps -> turn off background alert on any app that I don't explicitely need.
  • replace as many application with native apps (e.g: my sports tracker is MeeRun).
  • when not needed (e.g.: when I don't need to receive WhatsApp messages), shut down alien-dalvik (you can even add a toggle switch on the notification pane using a plugin from CoDeRus)

That has *tremendously* helped both battery life and memory/swap pressure.

I haven't installed enough (bovine manures) on the Xperia X to be affected by battery problems.
 

The Following 10 Users Say Thank You to DrYak For This Useful Post: