title: Sticky foreground service fails to restart with a "process is bad" error
body: <p>I have a started foreground service.
  I've taken care to return START_STICKY from <code>onStartCommand</code>.
  I've observed that foreground services don't run indefinitely but are periodically terminated by an Android internal module called the <code>RestartProcessManager</code>. Essentially a process LRU is maintained and the newly terminated service gets scheduled again if it's configured to do so(sticky or not).</p>
  
  <p>The issue I'm facing is with how the restart is being handled. Logcat indicates the service intent was being delivered, but failed because the <strong>"process is bad"</strong></p>
  
  <p>After scouring through other sources I was led to believe that there's a memory leak within my service. To validate this claim I created a vanilla foreground service that did nothing other than log a statement during <code>onStartCommand</code> within the same app. This too observed the same issue.</p>
  
  <p>Tried the exact same thing in a new project (with a new package name obviously) and service restarts worked perfectly fine. Also, I simulate a restart by clicking the red cross button under <strong>studio->logcat</strong> (which essentially kills the process). Anyway, the service intent was successfully delivered this time and the service was up and running again.
  I assumed it could be some dependencies in my project that may be messing in some manner. I replicated the dependencies in the new project and it continued to work as expected.</p>
  
  <p>Now this is where it gets absurd. I change the package name in the buggy project and I don't encounter the issue anymore. I'd have settled for this as a fix because I spent close to 2 days diagnosing this, but changing the package name isn't feasible for me as my app is published already.</p>
  
  <p><strong>Edit-1:</strong> I must mention that I've observed this currently on my device running Oreo(one plus 5)</p>
  
  <p><strong>Edit-2:</strong> 
  The service is running in the same process as the app. And I've included the logcat dump as well.</p>
  
  <pre><code>02-15 14:26:50.850  1395  1445 D RestartProcessManager: updateSelf :  com.ambee, size : 30
  02-15 14:26:50.852  1395  1445 D RestartProcessManager: com.ambee got score 26.17240489145331 in DayDuration for duration : 525176
  02-15 14:26:50.853  1395  1445 D RestartProcessManager: com.ambee got score 99.80218232889891 in DayLRU for LRU diff : 47707034
  02-15 14:26:50.853  1395  1445 D RestartProcessManager: com.ambee got score 90.9090909090909 in DayLaunchTimes for launch times : 10
  02-15 14:26:50.854  1395  1445 D RestartProcessManager: com.ambee : X : 2727.272727272727, Y : 785.1721467435993, Z : 2994.0654698669673
  02-15 14:26:51.082  1395  1445 I ActivityManager: Killing 13839:com.ambee/u0a260 (adj 200): [BgDetect][RNK] kill com.ambee (uid 10260) usage 4
  02-15 14:26:51.083  1395  1445 D ActivityManager: Process com.ambee has 1 services
  02-15 14:26:51.083  1395  1445 W ActivityManager: Scheduling restart of crashed service com.ambee/.vson.LinkService in 10996ms
  02-15 14:26:51.084  1395  1445 D EmbryoManager: prepare com.ambee user 0
  02-15 14:26:51.099  3710  3710 D NotificationListener: onNotificationRemoved# hash: 68226270 sbn: StatusBarNotification(pkg=com.ambee user=UserHandle{0} id=903 tag=null key=0|com.ambee|903|null|10260: Notification(channel=default pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x72 color=0x00000000 actions=2 vis=PRIVATE))
  02-15 14:26:54.121  1395  1444 I ActivityManager: Start proc 22570:com.ambee/u0a260 for embryo com.ambee
  02-15 14:26:54.121  1395  1444 D Embryo_Uterus: Embryo created.com.ambee, pid=22570
  02-15 14:26:54.796 22570 22570 D Embryo  : preload com.ambee, 10ms, hwui=true, layout=false, decor=false
  02-15 14:27:02.084  1395  1445 W ActivityManager: Unable to launch app com.ambee/10260 for service Intent { cmp=com.ambee/.vson.LinkService }: process is bad
  02-15 14:27:04.214  1395  1444 D Embryo_Uterus: rank:63, com.ambee, 35767806
  </code></pre>