With dumpsys activity | grep "Proc #" | grep my.package.name It looks like the app was in "fg-service" before getting killed.
Looking at the source code here: 6968<http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.4.2_r1/com/android/server/am/ActivityManagerService.java#6968>, it seems that the process should only be killed if "non-interactive". On Thursday, March 13, 2014 12:36:03 AM UTC-4, Digipom wrote: > > I'm running into an issue with my app on KitKat 4.4.2: when it's > recording, and the user later sends it to the background and swipes it away > from the recent apps list, the app is killed, even though it called > startForeground! > > This did not happen on 4.3, and to add insult to injury, the notification > doesn't disappear and the app services still appear in the "running > services" in the device settings. > > However, I see that this isn't happening for all apps. I downloaded some > other recorders, and I can confirm that their processes remain active in > memory even though I've also removed them from the recent apps list using > the same method; they remain active even if not recording! I thought it > could be an issue with the target API, but lowering that to 14 didn't help > (I don't think I could lower it further than that if using Action Bar > Sherlock). > > Does anyone have any ideas? It's definitely not cool from a customer's > point of view, so I really want to find a solution. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
