Play audio in the background.
- Continues playing while the screen is off or the app is in the background
- Control playback from your flutter UI, headset, Wear OS or Android Auto
- Drive audio playback from Dart code
This plugin provides a complete framework for playing audio in the background. You implement callbacks in Dart to play/pause/seek/etc audio, which means that you will need to use other Dart plugins in conjunction with this one to actually play the audio. This gives you the flexibility to play any kind of audio in the background. For example, if you want to play music in the background, you may use the audioplayer plugin in conjunction with this one. If you would rather play text-to-speech in the background, you may use the flutter_tts plugin in conjunction with this one.
audio_service itself manages all of the platform-specific code for setting up the environment for background audio, and interfacing with various peripherals used to control audio playback. For Android, this means acquiring a wake lock so that audio will play with the screen turned off, acquiring audio focus so that you can control your app from a headset, creating a media session and media browser service so that your app can be controlled by wearable devices and Android Auto. The iOS side is currently not implemented and so contributors are welcome (please see the Help section at the bottom of this page).
Since background execution of Dart code is a relatively new feature of flutter, not all plugins are yet compatible with audio_service (I am contacting some of these authors to make their packages compatible.)
Client-side code:
AudioService.start(
backgroundTask: myBackgroundTask,
notificationChannelName: 'Music Player',
androidNotificationIcon: "mipmap/ic_launcher",
);
Background code:
void myBackgroundTask() {
Completer completer = Completer();
MyAudioPlayer player = MyAudioPlayer();
AudioServiceBackground.run(
onStart: () async {
player.play();
// Keep the background environment alive
// Until we're finished playing...
await completer.future;
},
onStop: () {
player.stop();
completer.complete();
},
onClick: (MediaButton button) {
player.togglePlay();
},
);
}
class MyAudioPlayer {
// your custom dart code
}
Android manifest file:
<manifest ...>
<uses-permission android:name="android.permission.WAKE_LOCK"/>
<application
android:name=".MainApplication"
...>
...
<service android:name="com.ryanheise.audioservice.AudioService">
<intent-filter>
<action android:name="android.media.browse.MediaBrowserService" />
</intent-filter>
</service>
<receiver android:name="android.support.v4.media.session.MediaButtonReceiver" >
<intent-filter>
<action android:name="android.intent.action.MEDIA_BUTTON" />
</intent-filter>
</receiver>
</application>
</manifest>
Application class:
public class MainApplication extends FlutterApplication implements PluginRegistry.PluginRegistrantCallback {
@Override
public void onCreate() {
super.onCreate();
AudioServicePlugin.setPluginRegistrantCallback(this);
}
@Override
public void registerWith(PluginRegistry registry) {
GeneratedPluginRegistrant.registerWith(registry);
}
}
-
If you know how to implement any of these features in iOS, pull requests are welcome! As a guideline, prefer to keep the same dart API for both Android and iOS where possible. In cases where there are unavoidable differences between Android and iOS, name the feature with an
android
orios
prefix. -
If you find another flutter plugin (audio or otherwise) that crashes when running in the background environment, another way you can help is to file a bug report with that project, letting them know of the simple fix to make it work (see below).
Here is a sample bug report.
Flutter's new background execution feature (described here: https://medium.com/flutter-io/executing-dart-in-the-background-with-flutter-plugins-and-geofencing-2b3e40a1a124) allows plugins to be registered in a background context (e.g. a Service). The problem is that the wifi plugin assumes that the context for plugin registration is an activity with this line of code:
WifiManager wifiManager = (WifiManager) registrar.activity().getApplicationContext().getSystemService(Context.WIFI_SERVICE);
registrar.activity()
may now return null, and this leads to aNullPointerException
:E/AndroidRuntime( 2453): at com.ly.wifi.WifiPlugin.registerWith(WifiPlugin.java:23) E/AndroidRuntime( 2453): at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:30)
The solution is to change the above line of code to this:
WifiManager wifiManager = (WifiManager) registrar.activeContext().getApplicationContext().getSystemService(Context.WIFI_SERVICE);