That is similar to how I was using the onStartCommand() method. I check for a null intent and then if it's not null check to see if there is a specific intent extra passed. If that extra is passed then I know the user explicitly started the service and not the system. This is an issue for me because when the system kills my service and restarts it, the onDestroy() method is never called and the status bar icon and notification are never removed. This makes the user think that the application is still running (which it should but at that time I was not using START_STICKY) when it actually was not.
I looked into using startForeground() but saw there is a major issue with HTC devices ignoring that method, so that was a no go for me. As a quick aside... does anyone know why it is that HTC seemingly ignores that method? It seems to me like they purposely do so. That seems wrong to me because I believe that the device manufactures should not be allowed to mess with the very basic functionality of the Android OS. If it was something that was not part of the official SDK or OS (read: ContentProvider) then fine I get that, but basic functionality should always be supported IMO. Anyway, that is why I was asking Ms. Hackborn how it specifically works... because if onStartCommand() ever has an instance that it might not be called then I was going to have to figure out how to work around that. -- 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
