Originally created by @cremonies on GitHub (Feb 13, 2024).
Steps to reproduce
Connect phone to car
Open audiobookshelf though android auto car screen
Expected behaviour
connects to server and shows available books
Actual behaviour
shows an empty download screen
If I open the app before connecting it to the car it will connect to the server and shows the books on the car screen.
If I open the phone app after connect it to the car, I have to unplug it or select the book though the phone to play it.
Originally created by @cremonies on GitHub (Feb 13, 2024).
### Steps to reproduce
1. Connect phone to car
2. Open audiobookshelf though android auto car screen
### Expected behaviour
- connects to server and shows available books
### Actual behaviour
- shows an empty download screen
If I open the app before connecting it to the car it will connect to the server and shows the books on the car screen.
If I open the phone app after connect it to the car, I have to unplug it or select the book though the phone to play it.
adam
added the bug label 2026-04-24 23:41:04 +02:00
Did your just start happening like mine? I just updated a week ago and
noticed it happening now.
I was trying to find if I needed to change a setting with reverse proxy.
@cremonies commented on GitHub (Feb 13, 2024):
Did your just start happening like mine? I just updated a week ago and
noticed it happening now.
I was trying to find if I needed to change a setting with reverse proxy.
On Mon, Feb 12, 2024, 9:22 PM Kevin ***@***.***> wrote:
> I have experienced this as well.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/advplyr/audiobookshelf-app/issues/1081#issuecomment-1940362429>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AZ42QDJM657P6XDHC7X5XHLYTLMAHAVCNFSM6AAAAABDFWGHPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBQGM3DENBSHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
My main issue seems to be that if I don't open the app prior to android auto launching, no socket connection is established. So it goes to the downloads screen.
@donkevlar commented on GitHub (Feb 16, 2024):
My main issue seems to be that if I don't open the app prior to android auto launching, no socket connection is established. So it goes to the downloads screen.
Even after the app is open on my phone, the android auto app doesn't change, unless I restart android auto or reconnect my device to my car.
@donkevlar commented on GitHub (Feb 16, 2024):
Even after the app is open on my phone, the android auto app doesn't change, unless I restart android auto or reconnect my device to my car.
Even after the app is open on my phone, the android auto app doesn't change, unless I restart android auto or reconnect my device to my car.
I have the exact same issue.
How long have you been using the app and was this always an issue?
I'm trying to find out why this is now happening and didn't before.
@cremonies commented on GitHub (Feb 16, 2024):
> Even after the app is open on my phone, the android auto app doesn't change, unless I restart android auto or reconnect my device to my car.
I have the exact same issue.
How long have you been using the app and was this always an issue?
I'm trying to find out why this is now happening and didn't before.
It's happening to me as well. I kinda thought I had navigated to the downloads screen and there was no way back from there.
Testing it, I see that @donkevlar is at least partly correct: if the app is open when Android Auto starts, the browsing screen (as opposed to the playing screen) fully populates with tabs for "listening," "libraries," and "Downloads."
The problem is tied to the design of the browse screen: Tmthe first level into each of those tabs has no "back" functionality because you are expected to click directly to one of the other tabs (when you select a library in that tab, it adds a back button for you to press to go back to the top level).
When only the "Downloads" tab is generated because of this bug, you don't get access to the other tabs. You can still run books and podcasts from the app on the phone, but it doesn't seem to refresh this page after it fails the first time.
At the very least, @donkevlar's suggestion seems to be a good workaround to this problem. I couldn't force the bug by opening the app after Android Auto starts, but following @donkevlar's approach restored the app to normal on Android Auto.
@aureateflux commented on GitHub (Feb 20, 2024):
It's happening to me as well. I kinda thought I had navigated to the downloads screen and there was no way back from there.
Testing it, I see that @donkevlar is at least partly correct: if the app is open when Android Auto starts, the browsing screen (as opposed to the playing screen) fully populates with tabs for "listening," "libraries," and "Downloads."
The problem is tied to the design of the browse screen: Tmthe first level into each of those tabs has no "back" functionality because you are expected to click directly to one of the other tabs (when you select a library in that tab, it adds a back button for you to press to go back to the top level).
When only the "Downloads" tab is generated because of this bug, you don't get access to the other tabs. You can still run books and podcasts from the app on the phone, but it doesn't seem to refresh this page after it fails the first time.
At the very least, @donkevlar's suggestion seems to be a good workaround to this problem. I couldn't force the bug by opening the app after Android Auto starts, but following @donkevlar's approach restored the app to normal on Android Auto.
The way this will work is pressing the "disconnect" button in the side drawer will put the app in "offline mode". Once in offline mode the app doesn't try to connect to the server on subsequent app launches.
That way if you were going off grid for a while you can stop android auto and the core app from trying to connect to the server every time it gets opened. Offline mode is still getting smoothed out.
@advplyr commented on GitHub (Feb 21, 2024):
I fixed this for the next release.
The way this will work is pressing the "disconnect" button in the side drawer will put the app in "offline mode". Once in offline mode the app doesn't try to connect to the server on subsequent app launches.
That way if you were going off grid for a while you can stop android auto and the core app from trying to connect to the server every time it gets opened. Offline mode is still getting smoothed out.
Of course I don't know how it works yet, but it would be great if it could be made always start offline and change to online mode automatically once a sever connection can be established to mitigate this problem.
@raphpa commented on GitHub (Feb 22, 2024):
Also related to #310
Of course I don't know how it works yet, but it would be great if it could be made always start offline and change to online mode automatically once a sever connection can be established to mitigate this problem.
This still happens, if ABS is open and has an active connection to the server then AA works as expected. otherwise I see an empty downloads screen with no on screen ability to do anything with ABS. https://github.com/advplyr/audiobookshelf-app/issues/1292
@ozhound commented on GitHub (Aug 21, 2024):
This still happens, if ABS is open and has an active connection to the server then AA works as expected. otherwise I see an empty downloads screen with no on screen ability to do anything with ABS.
https://github.com/advplyr/audiobookshelf-app/issues/1292
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @cremonies on GitHub (Feb 13, 2024).
Steps to reproduce
Expected behaviour
Actual behaviour
If I open the app before connecting it to the car it will connect to the server and shows the books on the car screen.
If I open the phone app after connect it to the car, I have to unplug it or select the book though the phone to play it.
@donkevlar commented on GitHub (Feb 13, 2024):
I have experienced this as well.
@cremonies commented on GitHub (Feb 13, 2024):
Did your just start happening like mine? I just updated a week ago and
noticed it happening now.
I was trying to find if I needed to change a setting with reverse proxy.
On Mon, Feb 12, 2024, 9:22 PM Kevin @.***> wrote:
@donkevlar commented on GitHub (Feb 16, 2024):
My main issue seems to be that if I don't open the app prior to android auto launching, no socket connection is established. So it goes to the downloads screen.
@donkevlar commented on GitHub (Feb 16, 2024):
Even after the app is open on my phone, the android auto app doesn't change, unless I restart android auto or reconnect my device to my car.
@cremonies commented on GitHub (Feb 16, 2024):
I have the exact same issue.
How long have you been using the app and was this always an issue?
I'm trying to find out why this is now happening and didn't before.
@aureateflux commented on GitHub (Feb 20, 2024):
It's happening to me as well. I kinda thought I had navigated to the downloads screen and there was no way back from there.
Testing it, I see that @donkevlar is at least partly correct: if the app is open when Android Auto starts, the browsing screen (as opposed to the playing screen) fully populates with tabs for "listening," "libraries," and "Downloads."
The problem is tied to the design of the browse screen: Tmthe first level into each of those tabs has no "back" functionality because you are expected to click directly to one of the other tabs (when you select a library in that tab, it adds a back button for you to press to go back to the top level).
When only the "Downloads" tab is generated because of this bug, you don't get access to the other tabs. You can still run books and podcasts from the app on the phone, but it doesn't seem to refresh this page after it fails the first time.
At the very least, @donkevlar's suggestion seems to be a good workaround to this problem. I couldn't force the bug by opening the app after Android Auto starts, but following @donkevlar's approach restored the app to normal on Android Auto.
@advplyr commented on GitHub (Feb 21, 2024):
I fixed this for the next release.
The way this will work is pressing the "disconnect" button in the side drawer will put the app in "offline mode". Once in offline mode the app doesn't try to connect to the server on subsequent app launches.
That way if you were going off grid for a while you can stop android auto and the core app from trying to connect to the server every time it gets opened. Offline mode is still getting smoothed out.
@raphpa commented on GitHub (Feb 22, 2024):
Also related to #310
Of course I don't know how it works yet, but it would be great if it could be made always start offline and change to online mode automatically once a sever connection can be established to mitigate this problem.
@advplyr commented on GitHub (Feb 22, 2024):
Yeah as far as I know we don't have enough control to do that in Android Auto
@advplyr commented on GitHub (Mar 5, 2024):
Fixed in v0.9.73-beta
@ozhound commented on GitHub (Aug 21, 2024):
This still happens, if ABS is open and has an active connection to the server then AA works as expected. otherwise I see an empty downloads screen with no on screen ability to do anything with ABS.
https://github.com/advplyr/audiobookshelf-app/issues/1292