4 ms·
There's no pathology, it's just really really hard. Any single component not sleeping properly and keeping the CPU, buses or radios active immediately ruins the
by izacus 3y ago
There's no pathology, it's just really really hard. Any single component not sleeping properly and keeping the CPU, buses or radios active immediately ruins the battery life for everyone.
Power saving is all about racing towards that sweet idle state where every chip is clocked down and nothing radiates.
Which means that good power saving requires full vetting of every process on the system and making sure they all cooperate or, at least, are forced to sleep.
Android needed years to get into that state and developers/hackers are still sour about the restrictions it puts on them to keep battery life in check.
- minimalist 3y ago> Android needed years to get into that state and developers/hackers are still sour about the restrictions it puts on them to keep battery life in check. True. In my experience, many desktop applications do not care about minimizing idle cycles or network activity. So you end up with your radios always active, or some persistent CPU activity. For example, if one were to use Element Desktop, Signal Desktop and Discord simultaneously on PPP (all electron apps), we're looking at ~20% CPU utilization, idle! Mobile Linux will get there eventually!
- jwells89 3y agoI always wondered what exactly it is that Electron apps are doing to use that much CPU when they're sitting in the background doing nothing, often not even being on screen. For something like chat I guess it could be polling (surely sockets are more popular now?), but it's not uncommon to see this behavior even in completely offline Electron apps. It seems like they're never truly idle.