OxygenOS discussion about dont-kill-my-app HOT 23 OPEN

@Xalaxis Yep, its a typo, my version is 20190123.
I will add it to the optimized list and check it (although the optimized list means its more likely to be removed from the background).

Thanks for the info,
Eli

from dont-kill-my-app.

@elich11 Darn, I'm running the same version (9.0.4), no issues 🙁 (even when not on charge) . This is so puzzling.

from dont-kill-my-app.

Essentially I'm wondering if the reason OnePlus made number 2 on the list are historical (their position needs adjusting), or whether there are some confirmed still-active problems on older devices that might lack recent OxygenOS revisions or have different patch trees.

A third scenario is of course that my device is somehow unique, in which case hopefully Urbandroid can point me towards any useful system information to identify why I've had no issues with sleeping behavior.

from dont-kill-my-app.

For reference, I'm running a OnePlus 6, OxygenOS 9.0.3 (Android 9).

from dont-kill-my-app.

Users discussing how these battery issues seem not to be a problem with OnePlus 6 devices.

http://disq.us/p/1yznlqu

from dont-kill-my-app.

I'm on 9.0.3 no battery optimizations on the app, and no deep battery optimizations, use the latest sleep beta - 201190123.
oxygenOS closes the app every night, currently no solution/wordaround.

Eli

from dont-kill-my-app.

@elich11 What device are you using?

from dont-kill-my-app.

@elich11 What device are you using?

@Xalaxis OP6

from dont-kill-my-app.

@elich11 We are running exactly the same config (device, OxygenOS version) except for the fact that I haven't excluded Sleep from battery optimizations and I'm running version 20181212 (the latest stable(?)).

Are you sure that version number is correct, it seems very strange.

from dont-kill-my-app.

@elich11 Yeah, if it turns out that apps excluded from optimization are being killed but those included aren't, then that's a pretty big bug.

from dont-kill-my-app.

@Xalaxis after one night test, this workaround works perfectly.
The app doesn't get killed!
Good work.

Eli

from dont-kill-my-app.

@elich11 Great!

@Artaud, Can you try to reproduce or forward on to the correct person at Urbandroid?

from dont-kill-my-app.

@Xalaxis after more tests, I think that what fixed it is the device is plugged in to the charger all night.

Eli

from dont-kill-my-app.

@elich11 Hmm, so perhaps this is somehow a (device) sleep related issue. I don't think I've seen that problem myself, but I can't risk testing this until Wednesday night. I'll give it a test then (not having the device plugged in).

from dont-kill-my-app.

@Xalaxis second night it works (which is unpresedented for me), I think its a legit workaround.

Eli

from dont-kill-my-app.

@elich11 I've just tested with my phone, Sleep was not killed during the night (when on battery). Sorry for the delay in getting back to you. Did you confirm whether the charger seemed to effect survival through the night, or whether it was the previously thought battery-optimization settings?

from dont-kill-my-app.

@Xalaxis Yes, I'm using it without an issue with the charger connected for about 2 weeks now.
I will run a test tonight without the charger to make sure the issue is reproduced.

from dont-kill-my-app.

@Xalaxis the issue reproduced without a charger, even when using the latest os version (9.0.4).

from dont-kill-my-app.

It's mid 2019 and I'm still looking for a reliable way to run my foreground location service on a Oneplus device. Any workaround? :(

from dont-kill-my-app.

It's mid 2019 and I'm still looking for a reliable way to run my foreground location service on a Oneplus device. Any workaround? :(

Hi @eminemoholic , we've not been having any issues with foreground processes. What's the symptoms of your problem?

from dont-kill-my-app.

It's mid 2019 and I'm still looking for a reliable way to run my foreground location service on a Oneplus device. Any workaround? :(

Hi @eminemoholic , we've not been having any issues with foreground processes. What's the >symptoms of your problem

@Xalaxis For me the notification attached with the foreground service disappears after sometime and thus the service gets killed, without triggering any of the lifecycle events.

from dont-kill-my-app.

@eminemoholic Have you ruled out an extreme out-of-memory state?

from dont-kill-my-app.

So now with the release of the Don't kill my app tester, I think we can empirically say that at least my OnePlus 6 seems to not encounter any of these issues. I'd like to once again raise the case for the OnePlus ranking to be reviewed.

from dont-kill-my-app.