Hacker News Reader

Comment by BugsJustFindMe | Hacker News Reader

Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users

If HN allowed emoji in comments, I'd have a U+1F923 here. Since I can't do that, you're adorable. The users, eh? The users are supposed to be burdened with checking the wake status and radio activation schedule of their apps? How was that supposed to work, exactly?

View on HN

I'm not sure what your point is here and your tone indicates you're not really looking for honest discussion. But FYI Android reports energy usage statistics to the user on a per-app basis. What I don't like is Android the platform telling me the user how my phone is best used. It's pretty crippling. Let's say I'm deploying Android on hardware that is always plugged in--something kiosk-style. Why shouldn't I be able to have an app that keep a persistent connection open to a network service for say real-time communication? You can't do that now.

And if Android itself didn't tell you enough, there were apps line OSMonitor that could give you more detail (at least until Google shitcanned the permissions that it relied on for "security" reasons).

Blame shitty mobile developers who screwed the pooch on Android. Even if you avoid shovelware, the quality is abysmal.

My Android phone still randomly lights up its screen several times a day, without a new notification having come in. Reporting overall energy usage doesn't help me track down the culprit.

It's not like anyone's written apps for real work on these devices anyway. It's all just second class software.

And what about the mysterious Android OS/Android System "apps" that show up on the battery usage screen? How do I know which app is hogging resources here? Should we expect users to inspect wakelocks?

Reply on news.ycombinator.com