It seems that on the Incredible the startForeground() call is non- functional, causing my process to be put into the background scheduler class even though it has an active ongoing notification. I'm calling it the same as on other 2.x devices (through reflection as suggested by Diane for backward-compatibility), and this works fine on the Droid, with the same OS level (2.1-update1). I can see in the debugger that it gets all the way to ActivityManagerNative.setServiceForeground() with the notification param being non-null, so it's got to be in the ActivityManager or below.
The really telling thing is that the stock music player acts the same way. When I'm playing a song and go to the home screen the com.htc.music process goes into the bg class, even though its notification is still active. This is a real problem for us, as it denies us the CPU we need to play back music in some cases without stuttering. Any ideas on whether this is getting fixed, and how I might work around it? -- 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
