Timeline for START_STICKY, foreground Android service goes away without notice
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2015 at 21:48 | comment | added | IgorGanapolsky | Well, was your Galaxy Tab experiencing low-memory conditions, or perhaps your Service was doing something memory intensive on the main thread? | |
| Nov 12, 2013 at 16:12 | answer | added | Sazzad Hissain Khan | timeline score: 2 | |
| Oct 22, 2013 at 10:23 | history | edited | Marek Sebera | CC BY-SA 3.0 |
formatting
|
| Aug 4, 2011 at 10:16 | vote | accept | Dennis | ||
| Jul 29, 2011 at 19:19 | answer | added | Kevin TeslaCoil | timeline score: 11 | |
| Jul 9, 2011 at 1:02 | comment | added | Dennis | Sadly, the success of reversing that sequence was short-lived. Seems to be a bit of a gamble as to whether the sticky will "stick." With many dozens of attempts at starting this service, I have had it remain started three times so far. :( | |
| Jul 9, 2011 at 0:19 | comment | added | Dennis | Hmmm... I read more about startForeground, and it seems that this just sets a flag on a notification object, rather than actually taking some action. So on a whim, I reversed the sequence so that now startForeground precedes NotificationManager.notify. So far, it's looking pretty good. So now I'm searching for that example that led me to do it the other way... | |
| Jul 8, 2011 at 1:50 | history | asked | Dennis | CC BY-SA 3.0 |