Stuff I've tried:
1) Removed all broadcast receivers from AndroidManifest.xml.
2) Removed all sendBroadcast calls from the code.
3) Removed all broadcast receivers from the code.
4) Removed all calls to AppWidgetManager.
5) (I don't have any calls to AlarmManager)
6) Delete all intent-filter
I decided to dig further into this based on readings from Googling, and
here are some stats from adb shell dumpsys activity:
Here's the last line I see an instant before the app is killed (I'm just
running it over and over):
Proc # 4: prcp F/S/IF trm: 0 17361:com.mypackage.name/u0a241
Try a search of the forum. There are some long threads on this issue.
It's also on the Android issues list in various guises.
Pent
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Based on those threads and the issues list, it seems that receiving a broadcast
is the main known way that this is triggered (aside from not having a
foreground service, but I do have one), but I have logs on all my onReceive and
it doesn't seem to be that. :(
On Mar 13, 2014, at 2:45 AM, Pent
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:
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:
6 matches
Mail list logo
