3 ms·

> but can then run indefinitely Just bought a Xiaomi Redmi Note 7 and it kills everything including foreground services with a notification. A simple user sti

by yonixw 7y ago

> but can then run indefinitely Just bought a Xiaomi Redmi Note 7 and it kills everything including foreground services with a notification. A simple user still can allow it but it will require some tech knowledge to follow instruction that are described here: https://www.reddit.com/r/Xiaomi/comments/amcck5/miui_10_keep_killing_background_apps/ https://www.reddit.com/r/Xiaomi/comments/amcck5/miui_10_keep...

qmmmur 7y ago
I found the easy fix was to flash another rom. I fought against that OS for way too long.
- ekianjo 7y ago
  > found the easy fix was to flash another rom. You don't always have that luxury.
- BiteCode_dev 7y ago
  I don't think I make a wild statement by saying that most android users don't share the same definition of "easy".
  - lazyier 7y ago
    people get 'simple' and 'easy' mixed up. If a OS is actively sabotaging you, then yes, the only real solution is to replace it with something else. That's the simple and obvious solution. The simplest way to do this is to not buy a phone with shitty OS in the first place. As in "Don't buy a phone from Xiaomi". And when users complain about it you tell them that the problem is their phone manufacturer. If you can, of course, give them a work around so the app will work. But eventually they'll plug all the holes that allow for a functional phone. So it may not always be a option.
    - dspillett 7y ago
      > tell them that the problem is their phone manufacturer Despite this being true many will see is as an excuse, or worse just a plain lie, and leave you a 1* (or 0* if possible) review ranting about your attitude and bad coding. How dare you criticize their choice of device?!
- tsukurimashou 7y ago
  This issue looks very similar to web devs still struggling with legacy code to support IE. Should you simply drop support for IE and punish people relying on it and hope it dies quickly? Or should you maintain legacy code, and actually helping IE to survive by supporting it? I find that issue to be quite complicated and I'm still unsure if there is a right answer to that.

by yonixw 7y ago

qmmmur 7y ago

I found the easy fix was to flash another rom. I fought against that OS for way too long.

ekianjo 7y ago
> found the easy fix was to flash another rom. You don't always have that luxury.
BiteCode_dev 7y ago
I don't think I make a wild statement by saying that most android users don't share the same definition of "easy".
- lazyier 7y ago
  people get 'simple' and 'easy' mixed up. If a OS is actively sabotaging you, then yes, the only real solution is to replace it with something else. That's the simple and obvious solution. The simplest way to do this is to not buy a phone with shitty OS in the first place. As in "Don't buy a phone from Xiaomi". And when users complain about it you tell them that the problem is their phone manufacturer. If you can, of course, give them a work around so the app will work. But eventually they'll plug all the holes that allow for a functional phone. So it may not always be a option.
  - dspillett 7y ago
    > tell them that the problem is their phone manufacturer Despite this being true many will see is as an excuse, or worse just a plain lie, and leave you a 1* (or 0* if possible) review ranting about your attitude and bad coding. How dare you criticize their choice of device?!
tsukurimashou 7y ago
This issue looks very similar to web devs still struggling with legacy code to support IE. Should you simply drop support for IE and punish people relying on it and hope it dies quickly? Or should you maintain legacy code, and actually helping IE to survive by supporting it? I find that issue to be quite complicated and I'm still unsure if there is a right answer to that.