ryanheise

I've just published the platform interface with the proposed new API, and merged to the `minor` branch an implementation of the API for Android, iOS and macOS. Since the platform...

The above changes have now been published on pub.dev so I'll close this, although see the comment above for usage hints.

Thanks for letting me know of your success. Would you mind sharing your recipe notes here in this issue or in an issue on audio_session?

Note if you go through `AudioSession.instance` (the cross platform interface), the proposed code becomes: ```dart final session = await AudioSession.instance; await session.setActive(false, avAudioSessionSetActiveOptions: AVAudioSessionSetActiveOptions.notifyOthersOnDeactivation); ```

Although I'm not personally an Android Auto user (I don't even have a car!) I can say that I have tried to at least wrap all of the APIs that...

Some recent discussions about Android Auto in #956 .

Definitely should be some options here, but still some of the options are available on the audio source and others on the seek operation. See: `AVURLAssetPreferPreciseDurationAndTimingKey` and `AVPlayer`'s `seekToTime:toleranceBefore:toleranceAfter:`. Although...

> It looks like seeking already has a tolerence of zero That can change. The question is really what the new API will shape up to be, and to inform...

In a recent release I added some options for precise seeking on both Android and iOS in de7a461c95217048ca614b5103d93c09cb0c69df and 93abeba0d891319d2163ed7f798f43974e3167b3. You can experiment with the `options` parameter to [ProgressiveAudioSource](https://pub.dev/documentation/just_audio/latest/just_audio/ProgressiveAudioSource-class.html) to...

You could make a separate feature request for it, although it would be necessary to think about what specific options you want exposed from the underlying native APIs for iOS/Android....