Hacker News Reader

Comment by NGRhodes | Hacker News Reader

So the issue is not Android (AOSP) provided by google, but OEMs ?

AOSP is not Android. What Google distributes to OEMs and its direct customers is not AOSP. It is AOSP and the different Play Services including the Play Store and the Google applications with contracts mandating that they have to be provided to customers.

If you think people talk about AOSP when they talk about Android, you are always going to miss the point of these conversations.

From the link posted above parent: https://dontkillmyapp.com

> Unfortunately, vendors (e.g. Xiaomi, Huawei, OnePlus or even Samsung…) did not seem to catch that ball and they all have their own battery savers, usually very poorly written, saving battery only superficially, with side effects.

Heck, I was following the discussion regarding the notification system and how you couldn’t really do without and thought the link was actually relevant to the discussion without checking.

My apologies to NGRhodes, the link does indeed refer to an issue with OEM and not what Google supplies. I don’t really see what it has to do with the topic we were discussing however.

The issue is the locked-in requirement to rely on the sole source of push notifications built into the system. Running your own persistent app is an ugly workaround that doesn't work more often than does.

Also, such apps are unloaded from time to time even on stock non-modified Androids.

AOSP is horribly crippled by Google, as they move more and more features towards play services. Location, push notifications, etc.

Reply on news.ycombinator.com