[Enhancement]: Allow browsing books by author / series (and a full list) on Android Auto #969

New Issue

2026-04-24T23:44:28+02:00

adam commented

2026-04-24 23:44:28 +02:00

Originally created by @kuldan5853 on GitHub (May 16, 2024).

Describe the Feature/Enhancement

right now, only a very small (random?) selection of your books is listed in Android Auto.

I would like to be able to have the same options to browse for a book available on Android Auto that I have on the Phone app (Browse by Series, sort by latest date, and so on), with a way to basically navigate my library by selecting an author, a series, and then the specific book I'm interested in.

Also - it would be useful if there would be a "List" view in Android Auto instead of Cover only.

Why would this be helpful?

Right now, to switch between books that have not yet been started / are listed on the results in the app, I would have to pull out my phone to interact with ABS, which is a serious safety issue.

Future Implementation (Screenshot)

Make Android Auto work similarly to the stock app interface

A good way to see how I would envision the implementation is the app "listen audiobook player" which has a fully browsable library on Android Auto.

If useful, I can take a few photos when I'm in my car the next time as I would like a similar implementation to how they did it.

Audiobookshelf App Version

Android App - 0.9.63

Current Implementation (Screenshot)

No response

Originally created by @kuldan5853 on GitHub (May 16, 2024). ### Describe the Feature/Enhancement right now, only a very small (random?) selection of your books is listed in Android Auto. I would like to be able to have the same options to browse for a book available on Android Auto that I have on the Phone app (Browse by Series, sort by latest date, and so on), with a way to basically navigate my library by selecting an author, a series, and then the specific book I'm interested in. Also - it would be useful if there would be a "List" view in Android Auto instead of Cover only. ### Why would this be helpful? Right now, to switch between books that have not yet been started / are listed on the results in the app, I would have to pull out my phone to interact with ABS, which is a serious safety issue. ### Future Implementation (Screenshot) Make Android Auto work similarly to the stock app interface A good way to see how I would envision the implementation is the app "listen audiobook player" which has a fully browsable library on Android Auto. If useful, I can take a few photos when I'm in my car the next time as I would like a similar implementation to how they did it. ### Audiobookshelf App Version Android App - 0.9.63 ### Current Implementation (Screenshot) _No response_

adam added the enhancement android auto labels 2026-04-24 23:44:28 +02:00

adam closed this issue

2026-04-24 23:44:28 +02:00

adam commented

2026-04-24 23:44:28 +02:00

@ISO-B commented on GitHub (Aug 4, 2024):

I have started implementing this. Way how I am planning to do this is making following structure under libraries option:

Library
- List of authors
  - Series
    - Books
  - Non series books
Series
- List of series
  - Books
Collections
- List of collections
  - Books

So first you select which library you want to use and then navigate with that hierarchy. I am not sure does android auto support sorting by anything else than name, but we will see.

@ISO-B commented on GitHub (Aug 4, 2024): I have started implementing this. Way how I am planning to do this is making following structure under libraries option: 1. Library - List of authors - Series - Books - Non series books 2. Series - List of series - Books 3. Collections - List of collections - Books So first you select which library you want to use and then navigate with that hierarchy. I am not sure does android auto support sorting by anything else than name, but we will see.

adam commented

2026-04-24 23:44:28 +02:00

@kuldan5853 commented on GitHub (Aug 4, 2024):

So first you select which library you want to use and then navigate with that hierarchy. I am not sure does android auto support sorting by anything else than name, but we will see.

If you want to see a possible implementation, look at Listen Audiobook player - I worked with the dev to have a fully browsable library (that simply follows the file system structure in that case) implemented into the app a while ago. So at least there is no technical limit that prohibits you from showing large lists or anything like that that I could see..

As for how you propose, that sounds great to me as it would give you full flexibility browsing your library.

While you're at it, could you also look into the adjacent topic of the download function losing all folder structure? It would be great if the app would support sort of an "offline" mode where we only see the content we have downloaded locally (but with the same structure as in online, so library/series/collections) - not every country has good internet throughout, especially when driving.

That had been my main use case before I switched to Audiobookshelf - I used a booksonic server to manage my books and download them to the phone, but since the app was near useless in android auto (didn't work offline at all), I only used it to download the books (which neatly kept the folder structure of author\series\book intact) and then pointed Listen Audiobook player to the same folder for actual playback on the phone/in the car.

@kuldan5853 commented on GitHub (Aug 4, 2024): > So first you select which library you want to use and then navigate with that hierarchy. I am not sure does android auto support sorting by anything else than name, but we will see. If you want to see a possible implementation, look at Listen Audiobook player - I worked with the dev to have a fully browsable library (that simply follows the file system structure in that case) implemented into the app a while ago. So at least there is no technical limit that prohibits you from showing large lists or anything like that that I could see.. As for how you propose, that sounds great to me as it would give you full flexibility browsing your library. While you're at it, could you also look into the adjacent topic of the download function losing all folder structure? It would be great if the app would support sort of an "offline" mode where we only see the content we have downloaded locally (but with the same structure as in online, so library/series/collections) - not every country has good internet throughout, especially when driving. That had been my main use case before I switched to Audiobookshelf - I used a booksonic server to manage my books and download them to the phone, but since the app was near useless in android auto (didn't work offline at all), I only used it to download the books (which neatly kept the folder structure of author\series\book intact) and then pointed Listen Audiobook player to the same folder for actual playback on the phone/in the car.

adam commented

2026-04-24 23:44:29 +02:00

@ISO-B commented on GitHub (Aug 8, 2024):

Just small progress update. Progress has been bit slow as I don't have previous experience from android and android auto development. I managed to get android auto browsing hierarchy for library and series to work. It works, but needs caching and sorting by title/name for every view. When I get those things done it is quick to add collections.

About those large lists. It seems that there is no technical limit on android side, but for people who have very large libraries load times might be bit long, but we will see. If that is case then we just add some kind of paging system.

@ISO-B commented on GitHub (Aug 8, 2024): Just small progress update. Progress has been bit slow as I don't have previous experience from android and android auto development. I managed to get android auto browsing hierarchy for library and series to work. It works, but needs caching and sorting by title/name for every view. When I get those things done it is quick to add collections. About those large lists. It seems that there is no technical limit on android side, but for people who have very large libraries load times might be bit long, but we will see. If that is case then we just add some kind of paging system.

adam commented

2026-04-24 23:44:30 +02:00

@kuldan5853 commented on GitHub (Aug 24, 2024):

About those large lists. It seems that there is no technical limit on android side, but for people who have very large libraries load times might be bit long, but we will see. If that is case then we just add some kind of paging system.

I think also as you said before, maybe the answer here would be local caching of the directory structure (not the metadata itself), so that browsing the trees happens "offline" (with a sync of course while online). Metadata loading for selected books from the online source (or a downloaded copy) would then be quite fast in comparison.

Also, a suggestion from my side would be to also have a toggle for an offline mode in which only the locally downloaded library items are taken into consideration - this could make browsing in the car a lot easier too if you are the type to keep local copies of books due to bad connectivity (like I am).

At any rate, I really appreciate you working on this and look forward to being able to try it out :)

@kuldan5853 commented on GitHub (Aug 24, 2024): > About those large lists. It seems that there is no technical limit on android side, but for people who have very large libraries load times might be bit long, but we will see. If that is case then we just add some kind of paging system. I think also as you said before, maybe the answer here would be local caching of the directory structure (not the metadata itself), so that browsing the trees happens "offline" (with a sync of course while online). Metadata loading for selected books from the online source (or a downloaded copy) would then be quite fast in comparison. Also, a suggestion from my side would be to also have a toggle for an offline mode in which only the locally downloaded library items are taken into consideration - this could make browsing in the car a lot easier too if you are the type to keep local copies of books due to bad connectivity (like I am). At any rate, I really appreciate you working on this and look forward to being able to try it out :)

adam commented

2026-04-24 23:44:30 +02:00

@ISO-B commented on GitHub (Aug 26, 2024):

It seems that there is limit on android auto side for how many things your list can contain. Over 1000 items will prevent list loading. So I need to implement paging system for authors and series. I am thinking to add page changing entries to top of list and next page entry at bottom. Does that sound like good idea or does somebody have better idea?

Entries could be like:
Page 1 | A -H
Page 2 | H - O
Page 3 | O -Z

@ISO-B commented on GitHub (Aug 26, 2024): It seems that there is limit on android auto side for how many things your list can contain. Over 1000 items will prevent list loading. So I need to implement paging system for authors and series. I am thinking to add page changing entries to top of list and next page entry at bottom. Does that sound like good idea or does somebody have better idea? Entries could be like: Page 1 | A -H Page 2 | H - O Page 3 | O -Z

adam commented

2026-04-24 23:44:32 +02:00

@kuldan5853 commented on GitHub (Aug 28, 2024):

It seems that there is limit on android auto side for how many things your list can contain. Over 1000 items will prevent list loading. So I need to implement paging system for authors and series. I am thinking to add page changing entries to top of list and next page entry at bottom. Does that sound like good idea or does somebody have better idea?

Entries could be like: Page 1 | A -H Page 2 | H - O Page 3 | O -Z

I wouldn't use it as strict as this but just use a fixed paging size of maybe 50 to 100 entries per page - maybe even adding an #, A - Z before as a downselect (especially for Authors and Series) and then page the results by 50..

@kuldan5853 commented on GitHub (Aug 28, 2024): > It seems that there is limit on android auto side for how many things your list can contain. Over 1000 items will prevent list loading. So I need to implement paging system for authors and series. I am thinking to add page changing entries to top of list and next page entry at bottom. Does that sound like good idea or does somebody have better idea? > > Entries could be like: Page 1 | A -H Page 2 | H - O Page 3 | O -Z I wouldn't use it as strict as this but just use a fixed paging size of maybe 50 to 100 entries per page - maybe even adding an #, A - Z before as a downselect (especially for Authors and Series) and then page the results by 50..

adam commented

2026-04-24 23:44:32 +02:00

@ISO-B commented on GitHub (Sep 3, 2024):

Current implementation is following. If there is under 1k items the show items as normal. You can jump to specific letter by using android auto filter/jump to button. If there is over 1k items show first letters only. Next level shows items if there is less than 100 items otherwise show selected letter + 1. This loops until there is under 100 items.

I will try to find time to make pull request tomorrow with all changes so you can get to testing.

@ISO-B commented on GitHub (Sep 3, 2024): Current implementation is following. If there is under 1k items the show items as normal. You can jump to specific letter by using android auto filter/jump to button. If there is over 1k items show first letters only. Next level shows items if there is less than 100 items otherwise show selected letter + 1. This loops until there is under 100 items. I will try to find time to make pull request tomorrow with all changes so you can get to testing.

adam commented

2026-04-24 23:44:33 +02:00