ryanheise
ryanheise
Still ideally that configuration option should not make the OS so eager to kill the app. That issue has come up before but I haven't gotten to the bottom of...
Actually, `androidStopForegroundOnPause` defaults to true anyway, and the `example_playlist.dart` example you said you tested just uses the default. So maybe that can't be the difference?
Android Auto support is largely contributed by people who use that feature. If you are interested in contributing yourself, that's great, although if you would like someone else to work...
FYI, the latest release 0.18.7 contains some contributed updates to the Android Auto code. This may or may not affect your issue, so you may like to test your issue...
Thank you for the report, I shall look into this tomorrow.
It may take me a while before I can set up an environment to test this, but in the meantime would you be willing to provide a stack trace inside...
Sorry I understand what is going on now, and this is by design, not contrary to the API documentation. Still, your minimal reproduction project was helpful. There are two things...
> Is it possible (for us, in a forked version of `audio_service`), to recognize that the warm up process is originated from a push notification and not run the warm...
Do you mean the splash screen in your Flutter UI or in the Android XML layout?
I'll need a repro project for that.