Android 0.9.27 service killed on app swipe #48
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Opened 4 years ago
Last modified 2 years ago
#1904assigneddefect
Android 0.9.27 service killed on app swipe
Reported by:Licaon_KterOwned by:Meeh
Priority:
major
Milestone:
0.9.42
Component:
apps/android
Version:
0.9.27
Keywords:
Android, service, swipe, background
Cc:
str4d
Parent Tickets:
Sensitive:
no
Description
In 0.9.26 one could just swipe the app away in the task manager, since it uses a (notification the) service (it) will be kept in memory in background running just fine.
Now in 0.9.27 swiping the app away will kill the service too, so one needs to keep the app opened all the time.
Testing the official build ( Outside I2P (0.9.27) here https://geti2p.net/en/download#android ) it did not have this problem at the first try, but it did several hours later in another test.
App is excepted in Doze/battery app, happens in Android 5.1.1 and Nougat Preview 4, notification even stays on after the service is killed (!!!) and you can't dismiss it (yes, you can hide it).
Rebooting the device will have the app running in background at start just fine, until you open it, swiping away will kill it then.
Subtickets
I just checked this on an Android 7 and an Android 10 with I2P for Android 0.9.49. This issue is no longer observed or reproducible. Closing.
comment:2 Changed 2 years ago by zzz
Milestone:0.9.29 →
0.9.42Owner:
changed from str4d to _Meeh_Status:accepted →
assigned
comment:1 Changed 4 years ago by str4d
Status:new →
accepted
The likely cause of the problem is that in 0.9.27 I updated the build SDK version to 25, in order to update to the latest version of the support libraries. However, I don't know why it could have caused a behavioural change like this, because I explicitly kept the target SDK at 22 (so it should still be operating in compatibility mode for later SDKs).