views:

119

answers:

0

Hi , we observed one scenario where activity manager killed our application process(it includes 5 running services) and then when it re-started the application process, it re-started only 1 service (this service was first one to be destroyed) .

I/ActivityManager( 1660): No longer want com.android.bluetooth (pid 4961): hidden #16
I/ActivityManager( 1660): No longer want com.lge.sns (pid 5815): hidden #17
W/ActivityManager( 1660): Scheduling restart of crashed service com.lge.sns/.client.widget.FeedWidget.FeedWidgetUpdateService in 5000ms
W/ActivityManager( 1660): Scheduling restart of crashed service com.android.bluetooth/.bpp.BluetoothBppsndService in 14977ms
W/ActivityManager( 1660): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 24977ms
W/ActivityManager( 1660): Scheduling restart of crashed service com.android.bluetooth/.ftps.BluetoothFtpsService in 34977ms
W/ActivityManager( 1660): Scheduling restart of crashed service com.android.bluetooth/.hid.BluetoothHidService in 44977ms
W/ActivityManager( 1660): Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 54977ms
I/ActivityManager( 1660): Start proc com.lge.sns for service com.lge.sns/.client.widget.FeedWidget.FeedWidgetUpdateService: pid=6337 uid=10054 gids={3003, 1015}
I/ActivityManager( 1660): Start proc com.android.bluetooth for service com.android.bluetooth/.bpp.BluetoothBppsndService: pid=6371 uid=10016 gids={3003, 3002, 3001, 1015, 1006}

What could be the reason for this behavior ? Please suggest . Other 4 services were never started by AM .