5 ms·

> While yes, as a user you need to grant some permissions to the app, it works without a problem. Without the problem for YOU, because, presumably, you have a

> While yes, as a user you need to grant some permissions to the app, it works without a problem. Without the problem for YOU, because, presumably, you have a non-shitty phone. It is a much more severe issue on the likes of Samsung / Xiaomi / Huawei. See https://dontkillmyapp.com https://dontkillmyapp.com

NGRhodes 5y ago
So the issue is not Android (AOSP) provided by google, but OEMs ?
- Andrew_nenakhov 5y ago
  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.
- WastingMyTime89 5y ago
  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.
  - deleted 5y ago
    [deleted]
  - schadara 5y ago
    From the link posted above parent: https://dontkillmyapp.com 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.
    - WastingMyTime89 5y ago
      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.
- ohgodplsno 5y ago
  AOSP is horribly crippled by Google, as they move more and more features towards play services. Location, push notifications, etc.
izacus 5y ago
> Without the problem for YOU, because, presumably, you have a non-shitty phone. It is a much more severe issue on the likes of Samsung / Xiaomi / Huawei. See https://dontkillmyapp.com https://dontkillmyapp.com And if you force Google to stop verifying proper behaviour in CTS, do you expect those manufacturers to allow you to run background services at will? They already kill off anything that's not whitelisted to keep those battery numbers up. The every new major OEM release we developers find bunch of new ways the try and kill background apps.
- Causality1 5y ago
  I can back that up. Oneplus is infuriating in that they include a way for you to whitelist apps and then kill them anyway. I essentially have to plug my phone in if I want to run, say, a torrent client for more than two minutes.

NGRhodes 5y ago

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

Andrew_nenakhov 5y ago
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.
WastingMyTime89 5y ago
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.
- deleted 5y ago
  [deleted]
- schadara 5y ago
  From the link posted above parent: https://dontkillmyapp.com 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.
  - WastingMyTime89 5y ago
    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.
ohgodplsno 5y ago
AOSP is horribly crippled by Google, as they move more and more features towards play services. Location, push notifications, etc.

izacus 5y ago

> Without the problem for YOU, because, presumably, you have a non-shitty phone. It is a much more severe issue on the likes of Samsung / Xiaomi / Huawei. See https://dontkillmyapp.com https://dontkillmyapp.com And if you force Google to stop verifying proper behaviour in CTS, do you expect those manufacturers to allow you to run background services at will? They already kill off anything that's not whitelisted to keep those battery numbers up. The every new major OEM release we developers find bunch of new ways the try and kill background apps.

Causality1 5y ago
I can back that up. Oneplus is infuriating in that they include a way for you to whitelist apps and then kill them anyway. I essentially have to plug my phone in if I want to run, say, a torrent client for more than two minutes.