Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Basic Android Auto support #50

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

Skehmatics
Copy link
Contributor

@Skehmatics Skehmatics commented Jun 19, 2020

Implement very basic Android Auto support, relying on ExoPlayer builtins such as MediaSessionConnector and TimelineQueueNavigator as much as possible to avoid introducing unnecessary complexity into the app.

Closes #12

Feature hitlist:

  • View playback state and current track from Android Auto
  • Transport (forward, back) controls
  • View / jump in Queue
  • Browse library

Bugs that need resolved:

  • Automatically switch to correct output
  • Avoid duplicate new track notification when fetching next track

@Skehmatics Skehmatics marked this pull request as draft June 19, 2020 13:18
@Skehmatics Skehmatics force-pushed the feature/basicAndroidAutoSupport branch from 259c1a0 to 052ae0b Compare June 19, 2020 13:33
@Skehmatics Skehmatics changed the base branch from master to develop June 19, 2020 13:33
Derek Schmidt added 2 commits June 19, 2020 06:34
Meet min requirements for Android Auto to connect to our mediasession

Still to go:
1. File browsing
2. Additional playback controls
Automatic next and previous implimentations!
ExoPlayer is rad
Should also help with metadata confusion when pre-loading the next track
for gapless playback
@Skehmatics Skehmatics force-pushed the feature/basicAndroidAutoSupport branch from 052ae0b to 8878cdc Compare June 19, 2020 13:34
@apognu
Copy link
Owner

apognu commented Jun 20, 2020

Wow, thanks for the PR.

I will need to read some documentation on how to test this without an actual Android Auto. I absolutely never touched that.

How does it work without a way to browse the library from the car? Is your phone used like I kind of advanced remote and your car dashboard like a playback display and speaker? Or does it need this browser implementation before or can be merged?

@apognu
Copy link
Owner

apognu commented Jun 20, 2020

I was able to lightly test part of this, and this is a really good start! I couldn't check audio itself as I could not make a sound in my current environment, but media controls and metadata display look OK.

I'll wait until you continue before inspect and comment the code, but I like where this is going.

Also, if I remember correctly, when MediaBrowserServiceCompat is implemented, this might also be used for future Android TV support.

@apognu
Copy link
Owner

apognu commented Jul 8, 2020

Did you have the opportunity to advance this further?

No pressure, mind you, I am just trying to schedule my testing sessions. :)

@arniom
Copy link

arniom commented Oct 5, 2020

Hello, i see today that you can use an emulator for testing AA on desktop : https://www.reddit.com/r/AndroidAuto/comments/j50fd6/after_5_years_google_released_an_update_for_its/

@th0mcat
Copy link

th0mcat commented Dec 5, 2020

I do have Android Auto, so if someone will compile an APK, I'll throw it on my phone and test it in my car.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Android Auto support
4 participants