Apparently I'm an idiot. The problem is not with the ringtone, but with our activity, which (when the screen is off) gets an onPause immediately after starting up.
I guess the system is pausing the activity because the user can' see it, and it doesn't want to waste effort running it. Does that mean we need to move our playback works to a Service ? Thanks, Richard On Jan 15, 6:34 am, Dave Sparks <davidspa...@android.com> wrote: > I'd have to look at the code, but it doesn't surprise me. The phone > app/lock screen is a tricky bit of code and I don't think it was > intended for the ringtone to play while the screen is off. > > Is there a reason you chose the Ringtone class to play your sound? > There are other options e.g. Notification Manager, MediaPlayer. > > On Jan 14, 4:16 pm, jarkman <jark...@gmail.com> wrote: > > > We have an app which uses Ringtone.play() to play tones. > > > We've found that when the screen is off, calls of Ringtone.play() in > > our Activity do not make any noise (although the activity is > > definitely running). > > > However, calls of Ringtone.play() from our BroadcastReceiver always > > make a noise, even when the screen is off. > > > What's going on here ? Is this a deliberate platform behaviour ? > > > Thanks, > > > Richard > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
