Originally created by @faulker on GitHub (Jan 22, 2025).
What was the Problem?
I'm having battery usage issues, the usage has been much higher than in previous app versions. After about two hours of playtime, it has been running in the background for 6+ hours and accounted for 35% of my battery usage, five times the usage of any other app.
Steps to Reproduce the Issue
Use the app on a similar phone
What was Expected?
Less battery usage
Phone Model
Pixel 7a
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.9.78
Installation Source
Google Play Store
Additional Notes
I do have the widget enabled, I've removed it to see if that makes any difference.
Originally created by @faulker on GitHub (Jan 22, 2025).
### What was the Problem?
I'm having battery usage issues, the usage has been much higher than in previous app versions. After about two hours of playtime, it has been running in the background for 6+ hours and accounted for 35% of my battery usage, five times the usage of any other app.
### Steps to Reproduce the Issue
Use the app on a similar phone
### What was Expected?
Less battery usage
### Phone Model
Pixel 7a
### Phone OS
Android 15
### Audiobookshelf App Version
Android App - 0.9.78
### Installation Source
Google Play Store
### Additional Notes
I do have the widget enabled, I've removed it to see if that makes any difference.
adam
added the bug label 2026-04-24 23:49:30 +02:00
Was this with streaming or a downloaded book? Was the app connected to the server or listening in offline mode (not attempting to sync progress to the server)?
I just checked my usage, and a downloaded book took 16% of my battery after 7.4 hours on a Pixel 6a
@nichwall commented on GitHub (Jan 22, 2025):
Was this with streaming or a downloaded book? Was the app connected to the server or listening in offline mode (not attempting to sync progress to the server)?
I just checked my usage, and a downloaded book took 16% of my battery after 7.4 hours on a Pixel 6a
It is an audiobook that I have previously downloaded from the server, I am not streaming anything from the server.
Removing the widget didn't help, today I listened for less than an hour yet the battery usage is around the same 37% of my used battery was from the app. The app is reporting that it has been running in the background for 3h 52m.
This time around I'm disabling the "pin media player" option to see if that helps at all
@faulker commented on GitHub (Jan 22, 2025):
It is an audiobook that I have previously downloaded from the server, I am not streaming anything from the server.
Removing the widget didn't help, today I listened for less than an hour yet the battery usage is around the same 37% of my used battery was from the app. The app is reporting that it has been running in the background for 3h 52m.
This time around I'm disabling the "pin media player" option to see if that helps at all
I've also noticed this since the last last updated, 0.9.78. I'm listening to a downloaded book and it uses a significant amount of battery (something is using a lot of CPU as the phone warms up). Android claims 45% battery usage for ~5 hours of runtime.
@Zibbp commented on GitHub (Jan 23, 2025):
I've also noticed this since the last last updated, 0.9.78. I'm listening to a downloaded book and it uses a significant amount of battery (something is using a lot of CPU as the phone warms up). Android claims 45% battery usage for ~5 hours of runtime.
Its the same for me. After the last pixel 9 update (android 15, security patch of January) my audiobookshelf app uses up to 40% of my battery every day. Before this update it was not noticeable. Im listening to an downloaded audiobook and the network usage is almost 0.
@schinguhl commented on GitHub (Jan 23, 2025):
Its the same for me. After the last pixel 9 update (android 15, security patch of January) my audiobookshelf app uses up to 40% of my battery every day. Before this update it was not noticeable. Im listening to an downloaded audiobook and the network usage is almost 0.

Same issues for me also! One thing I've noticed is everyone who's stated a phone model all seem to have pixel devices?
I myself are in a pixel 7 pro, might just be representative of the community here I'm not sure, but could be pixel devices specifically effected?
@TDderpy commented on GitHub (Jan 23, 2025):
Same issues for me also! One thing I've noticed is everyone who's stated a phone model all seem to have pixel devices?
I myself are in a pixel 7 pro, might just be representative of the community here I'm not sure, but could be pixel devices specifically effected?
Noticed the same with me on my P8P. Now I can almost confirm 100% it's something (not sure what) in the pixel stock ROM that is causing it. When running a custom ROM, I can listen for hours, nearly half the day and it's only 15-20% battery drain. On Stock ROM I lose about 15% batter an hour listening. All books are streaming for me.
@kingmike67 commented on GitHub (Jan 23, 2025):
Noticed the same with me on my P8P. Now I can almost confirm 100% it's something (not sure what) in the pixel stock ROM that is causing it. When running a custom ROM, I can listen for hours, nearly half the day and it's only 15-20% battery drain. On Stock ROM I lose about 15% batter an hour listening. All books are streaming for me.
Same issue on my Pixel 9 Pro, very recently started burning through battery while in background and not listening. Yesterday I listened to downloaded audiobook for about 2 hours total, and audiobookshelf accounted for 57% of my daily battery usage. And that was with my battery having run down to 10% at the point when I checked, so a very significant amount of the battery.
@Vilhjalmr26 commented on GitHub (Jan 23, 2025):
Same issue on my Pixel 9 Pro, very recently started burning through battery while in background and not listening. Yesterday I listened to downloaded audiobook for about 2 hours total, and audiobookshelf accounted for 57% of my daily battery usage. And that was with my battery having run down to 10% at the point when I checked, so a very significant amount of the battery.
Same issues for me also! One thing I've noticed is everyone who's stated a phone model all seem to have pixel devices?
I myself are in a pixel 7 pro, might just be representative of the community here I'm not sure, but could be pixel devices specifically effected?
I have a Samsung S22 running Android 14 so I don't believe it is limited to Pixels.
@Zibbp commented on GitHub (Jan 23, 2025):
> Same issues for me also! One thing I've noticed is everyone who's stated a phone model all seem to have pixel devices?
> I myself are in a pixel 7 pro, might just be representative of the community here I'm not sure, but could be pixel devices specifically effected?
I have a Samsung S22 running Android 14 so I don't believe it is limited to Pixels.
I have a Samsung S22 running Android 14 so I don't believe it is limited to Pixels.
Samsung Galaxy S20 Pro / Android 13 / One UI 5.1 / Nova Launcher Prime 8.0.18
ABS Mobile Version: 0.9.78-beta
ABS Server Version: 2.18.1 docker
No significant increase of CPU Load while streaming over cell and wifi as well as local playback. Widget enabled. Foreground and Background playback.
(You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch)
@theniwo commented on GitHub (Jan 23, 2025):
>I have a Samsung S22 running Android 14 so I don't believe it is limited to Pixels.
Samsung Galaxy S20 Pro / Android 13 / One UI 5.1 / Nova Launcher Prime 8.0.18
ABS Mobile Version: 0.9.78-beta
ABS Server Version: 2.18.1 docker
No significant increase of CPU Load while streaming over cell and wifi as well as local playback. Widget enabled. Foreground and Background playback.
(You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch)
Disabling "pin media player" had no effect, battery usage is still extremely high (41% over 7 hours today) with only 30 mins of listing time.
@faulker commented on GitHub (Jan 23, 2025):
Disabling "pin media player" had no effect, battery usage is still extremely high (41% over 7 hours today) with only 30 mins of listing time.
Its the same for me. After the last pixel 9 update (android 15, security patch of January) my audiobookshelf app uses up to 40% of my battery every day. Before this update it was not noticeable. Im listening to an downloaded audiobook and the network usage is almost 0.
It doesn't even show up in my battery usage history of this week. But I have 60 minutes sleep timer enabled, though.
@theniwo commented on GitHub (Jan 23, 2025):
> Its the same for me. After the last pixel 9 update (android 15, security patch of January) my audiobookshelf app uses up to 40% of my battery every day. Before this update it was not noticeable. Im listening to an downloaded audiobook and the network usage is almost 0.
>
It doesn't even show up in my battery usage history of this week. But I have 60 minutes sleep timer enabled, though.
Just wanted to say I'm also having this same experience.
ROG Phone 6
app version 0.9.78-beta
listened to about 20 minutes of a (locally downloaded, not streamed) book this morning, did not download any other books or interact with the app outside of playing and pausing.
@kymahi commented on GitHub (Jan 23, 2025):
Just wanted to say I'm also having this same experience.

ROG Phone 6
app version 0.9.78-beta
listened to about 20 minutes of a (locally downloaded, not streamed) book this morning, did not download any other books or interact with the app outside of playing and pausing.
Can you check the battery setting of the app (App-Info -> Battery)?
Mine is set to optimized. The other two options translate to
Not limited: Allows the app to use the battery without limits. Can decrease battery lifespan.
Limited: Limits the use of battery in the background. App can misfunction etc.
Make sure, you don't have it on Not limited, or whatever the setting is called in english.
@theniwo commented on GitHub (Jan 23, 2025):
It was active in the background for 6.5 hrs.
Can you check the battery setting of the app (App-Info -> Battery)?
Mine is set to optimized. The other two options translate to
* Not limited: Allows the app to use the battery without limits. Can decrease battery lifespan.
* Limited: Limits the use of battery in the background. App can misfunction etc.
Make sure, you don't have it on Not limited, or whatever the setting is called in english.

Pixel 7 Pro. I am streaming and it's used 77% battery in 11 hours of background use. I had my phone playing through Bluetooth speaker most of the day, I've plugged my phone back in multiple times through out the day because battery was getting low. Audiobook shelf is on Optimized.
@tdz262 commented on GitHub (Jan 24, 2025):
Pixel 7 Pro. I am streaming and it's used 77% battery in 11 hours of background use. I had my phone playing through Bluetooth speaker most of the day, I've plugged my phone back in multiple times through out the day because battery was getting low. Audiobook shelf is on Optimized.
Have the same issue (Pixel 8a).
I did a few tests and figured out that it does not matter if you are listening locally or streaming. In fact, the app drains the battery even when it is only running in the background and you are not listening to anything at all.
I downgraded the app to version v0.9.77-beta and the problem was gone. So, there is definitely something wrong with version v0.9.78-beta.
@Ich-Eben commented on GitHub (Jan 25, 2025):
Have the same issue (Pixel 8a).
I did a few tests and figured out that it does not matter if you are listening locally or streaming. In fact, the app drains the battery even when it is only running in the background and you are not listening to anything at all.
I downgraded the app to version **v0.9.77-beta** and the problem was gone. So, there is definitely something wrong with version **v0.9.78-beta**.
Same issue, Samsung A55 (Android 14), ABS server at v2.18.1; v0.9.78-beta absolutely murders my battery life just by idling in the background after I stop playing an audiobook (local, streaming, makes no difference) even with screen off. I had to downgrade to 0.9.77 so can't provide battery usage stats, but they're similar to those seen in previous posts.
@biuklija commented on GitHub (Jan 25, 2025):
Same issue, Samsung A55 (Android 14), ABS server at v2.18.1; v0.9.78-beta absolutely murders my battery life just by idling in the background after I stop playing an audiobook (local, streaming, makes no difference) even with screen off. I had to downgrade to 0.9.77 so can't provide battery usage stats, but they're similar to those seen in previous posts.
I believe I found the culprit for the battery issue. The hopeful fix is in v0.9.79-beta that was just made available in the app stores.
Please let me know what your experience is.
@advplyr commented on GitHub (Jan 27, 2025):
I believe I found the culprit for the battery issue. The hopeful fix is in [v0.9.79-beta](https://github.com/advplyr/audiobookshelf-app/releases/tag/v0.9.79-beta) that was just made available in the app stores.
Please let me know what your experience is.
Still having high battery usage in the background on 0.9.79-beta.
I had it in my car playing through Android Auto, then disconnected it and started playing it immediately after through the speaker, playing for about 20 minutes. Then I paused it and haven't used it since
@kymahi commented on GitHub (Jan 28, 2025):

Still having high battery usage in the background on 0.9.79-beta.
I had it in my car playing through Android Auto, then disconnected it and started playing it immediately after through the speaker, playing for about 20 minutes. Then I paused it and haven't used it since
Mine has definitely been better. Was listening for about an hour on Android auto this morning, then paused and unused since. Drain since pausing has been minimal, it still pulled about double the power of Android auto, but not sure how those normally lines up.
So usage still seems a bit high, but background seems better at the least.
@Vilhjalmr26 commented on GitHub (Jan 28, 2025):
Mine has definitely been better. Was listening for about an hour on Android auto this morning, then paused and unused since. Drain since pausing has been minimal, it still pulled about double the power of Android auto, but not sure how those normally lines up.
So usage still seems a bit high, but background seems better at the least.

Things are certainly better for me now, but usage is still the highest usage of all the apps, at around 40-60% but much less draining then before.
@TDderpy commented on GitHub (Jan 28, 2025):
Things are certainly better for me now, but usage is still the highest usage of all the apps, at around 40-60% but much less draining then before.
I'm pretty sure this is now isolated to android auto.
If users who don't use android auto at all can confirm they have seen improvement that would be helpful.
@advplyr commented on GitHub (Jan 28, 2025):
Thanks for reporting.
I'm pretty sure this is now isolated to android auto.
If users who don't use android auto at all can confirm they have seen improvement that would be helpful.
@jaredtodworkman commented on GitHub (Jan 28, 2025):
I don't use Android Auto and my battery is back to normal.
[Screenshot_20250128-164259.png](https://github.com/user-attachments/assets/f8ef622f-74fb-4fa2-93a0-ee46e4630a70)
I'm using 0.9.79-beta and today my phone was so sluggish to respond (i.e. it responded to the power button press after 2-3 seconds) I had to restart. I did use Android Auto earlier today. Funnily enough, force closing Audiobookshelf didn't resolve the sluggishness of the phone. I had to restart.
@lightheaded commented on GitHub (Jan 30, 2025):
I'm using 0.9.79-beta and today my phone was so sluggish to respond (i.e. it responded to the power button press after 2-3 seconds) I had to restart. I did use Android Auto earlier today. Funnily enough, force closing Audiobookshelf didn't resolve the sluggishness of the phone. I had to restart.

Check if sluggishness is caused by high CPU usage:
You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
@theniwo commented on GitHub (Jan 30, 2025):
Check if sluggishness is caused by high CPU usage:
You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
Check if sluggishness is caused by high CPU usage: You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
Thanks! Will check next time it occurs
@lightheaded commented on GitHub (Jan 30, 2025):
> Check if sluggishness is caused by high CPU usage: You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
Thanks! Will check next time it occurs
@thoughtlessdestiny commented on GitHub (Jan 31, 2025):
I've had high usage and just been streaming to Bluetooth earbuds. I'm on the 0.9.79-beta using a Pixel Fold.
@thoughtlessdestiny commented on GitHub (Jan 31, 2025):
I've had high usage and just been streaming to Bluetooth earbuds. I'm on the 0.9.79-beta using a Pixel Fold.

I've noticed some pretty wild battery drain on my android client, even when it is idle in the background not playing anything. I did see it as high as ~60% total battery drain after listening to maybe 2 hours of locally downloaded audio book (pixel 6 pro). I did turn on debugging and couldn't see anything abnormal (initially I thought it might have been played status updates getting sent back).
tcpdump on the server side had a message coming back when the whole thing was backgrounded (the query stopped when the app was forced to quit). Before I started killing the app it was coming through about once every 4-5 seconds. Afterwards I couldn't get it to repeat at any sort of frequency. It seemed to be a reply with just "Loading...".
@codhopper commented on GitHub (Feb 6, 2025):
I've noticed some pretty wild battery drain on my android client, even when it is idle in the background not playing anything. I did see it as high as ~60% total battery drain after listening to maybe 2 hours of locally downloaded audio book (pixel 6 pro). I did turn on debugging and couldn't see anything abnormal (initially I thought it might have been played status updates getting sent back).
tcpdump on the server side had a message coming back when the whole thing was backgrounded (the query stopped when the app was forced to quit). Before I started killing the app it was coming through about once every 4-5 seconds. Afterwards I couldn't get it to repeat at any sort of frequency. It seemed to be a reply with just "Loading...".
```
GET / HTTP/1.0
```
```
HTTP/1.1 200 OK
Content-Security-Policy: frame-ancestors 'self'
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 02 Feb 2025 21:42:10 GMT
ETag: W/"1028-194c89d2750"
Content-Type: text/html; charset=UTF-8
Content-Length: 4136
Date: Thu, 06 Feb 2025 12:30:44 GMT
Connection: close
<!doctype html>
<html lang="en" data-n-head="%7B%22lang%22:%7B%221%22:%22en%22%7D%7D">
<head>
<meta data-n-head="1" charset="utf-8"><meta data-n-head="1" name="viewport" content="width=device-width,initial-scale=1"><meta data-n-head="1" data-hid="description" name="description" content=""><meta data-n-head="1" data-hid="robots" name="robots" content="noindex"><meta data-n-head="1" data-hid="charset" charset="utf-8"><meta data-n-head="1" data-hid="mobile-web-app-capable" name="mobile-web-app-capable" content="yes"><meta data-n-head="1" data-hid="apple-mobile-web-app-capable" name="apple-mobile-web-app-capable" content="yes"><meta data-n-head="1" data-hid="apple-mobile-web-app-status-bar-style" name="apple-mobile-web-app-status-bar-style" content="black"><meta data-n-head="1" data-hid="apple-mobile-web-app-title" name="apple-mobile-web-app-title" content="Audiobookshelf"><meta data-n-head="1" data-hid="theme-color" name="theme-color" content="#232323"><meta data-n-head="1" data-hid="og:type" name="og:type" property="og:type" content="website"><meta data-n-head="1" data-hid="og:title" name="og:title" property="og:title" content="Audiobookshelf"><meta data-n-head="1" data-hid="og:site_name" name="og:site_name" property="og:site_name" content="Audiobookshelf"><title>Audiobookshelf</title><link data-n-head="1" rel="icon" type="image/x-icon" href="/audiobookshelf/favicon.ico"><link data-n-head="1" rel="apple-touch-icon" href="/audiobookshelf/ios_icon.png"><link data-n-head="1" data-hid="shortcut-icon" rel="shortcut icon" href="/audiobookshelf/icon.svg"><link data-n-head="1" data-hid="apple-touch-icon" rel="apple-touch-icon" href="/audiobookshelf/icon192.png" sizes="any"><link data-n-head="1" rel="manifest" href="/audiobookshelf/_nuxt/manifest.2f7e41c6.json" data-hid="manifest"><base href="/audiobookshelf/"><link rel="preload" href="/audiobookshelf/_nuxt/790ce0e.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/a66bc33.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/10761d5.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/8fa8266.js" as="script">
</head>
<body>
<div id="__nuxt"><style>#nuxt-loading{background:#fff;visibility:hidden;opacity:0;position:absolute;left:0;right:0;top:0;bottom:0;display:flex;justify-content:center;align-items:center;flex-direction:column;animation:nuxtLoadingIn 10s ease;-webkit-animation:nuxtLoadingIn 10s ease;animation-fill-mode:forwards;overflow:hidden}@keyframes nuxtLoadingIn{0%{visibility:hidden;opacity:0}20%{visibility:visible;opacity:0}100%{visibility:visible;opacity:1}}@-webkit-keyframes nuxtLoadingIn{0%{visibility:hidden;opacity:0}20%{visibility:visible;opacity:0}100%{visibility:visible;opacity:1}}#nuxt-loading>div,#nuxt-loading>div:after{border-radius:50%;width:5rem;height:5rem}#nuxt-loading>div{font-size:10px;position:relative;text-indent:-9999em;border:.5rem solid #f5f5f5;border-left:.5rem solid #000;-webkit-transform:translateZ(0);-ms-transform:translateZ(0);transform:translateZ(0);-webkit-animation:nuxtLoading 1.1s infinite linear;animation:nuxtLoading 1.1s infinite linear}#nuxt-loading.error>div{border-left:.5rem solid #ff4500;animation-duration:5s}@-webkit-keyframes nuxtLoading{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@keyframes nuxtLoading{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}</style> <script>window.addEventListener("error",(function(){var e=document.getElementById("nuxt-loading");e&&(e.className+=" error")}))</script> <div id="nuxt-loading" aria-live="polite" role="status"><div>Loading...</div></div> </div><script>window.__NUXT__={config:{version:"2.19.0",routerBasePath:"/audiobookshelf",_app:{basePath:"/audiobookshelf/",assetsPath:"/audiobookshelf/_nuxt/",cdnURL:null}}}</script>
<script src="/audiobookshelf/_nuxt/790ce0e.js"></script><script src="/audiobookshelf/_nuxt/a66bc33.js"></script><script src="/audiobookshelf/_nuxt/10761d5.js"></script><script src="/audiobookshelf/_nuxt/8fa8266.js"></script></body>
</html>
```
I've noticed some pretty wild battery drain on my android client, even when it is idle in the background not playing anything. I did see it as high as ~60% total battery drain after listening to maybe 2 hours of locally downloaded audio book (pixel 6 pro). I did turn on debugging and couldn't see anything abnormal (initially I thought it might have been played status updates getting sent back).
tcpdump on the server side had a message coming back when the whole thing was backgrounded (the query stopped when the app was forced to quit). Before I started killing the app it was coming through about once every 4-5 seconds. Afterwards I couldn't get it to repeat at any sort of frequency. It seemed to be a reply with just "Loading...".
Can you confirm which version of the app you are on?
Also if you are listening through android auto
@advplyr commented on GitHub (Feb 6, 2025):
> I've noticed some pretty wild battery drain on my android client, even when it is idle in the background not playing anything. I did see it as high as ~60% total battery drain after listening to maybe 2 hours of locally downloaded audio book (pixel 6 pro). I did turn on debugging and couldn't see anything abnormal (initially I thought it might have been played status updates getting sent back).
>
> tcpdump on the server side had a message coming back when the whole thing was backgrounded (the query stopped when the app was forced to quit). Before I started killing the app it was coming through about once every 4-5 seconds. Afterwards I couldn't get it to repeat at any sort of frequency. It seemed to be a reply with just "Loading...".
>
> ```
> GET / HTTP/1.0
> ```
>
> ```
> HTTP/1.1 200 OK
> Content-Security-Policy: frame-ancestors 'self'
> Accept-Ranges: bytes
> Cache-Control: public, max-age=0
> Last-Modified: Sun, 02 Feb 2025 21:42:10 GMT
> ETag: W/"1028-194c89d2750"
> Content-Type: text/html; charset=UTF-8
> Content-Length: 4136
> Date: Thu, 06 Feb 2025 12:30:44 GMT
> Connection: close
>
> <!doctype html>
> <html lang="en" data-n-head="%7B%22lang%22:%7B%221%22:%22en%22%7D%7D">
> <head>
> <meta data-n-head="1" charset="utf-8"><meta data-n-head="1" name="viewport" content="width=device-width,initial-scale=1"><meta data-n-head="1" data-hid="description" name="description" content=""><meta data-n-head="1" data-hid="robots" name="robots" content="noindex"><meta data-n-head="1" data-hid="charset" charset="utf-8"><meta data-n-head="1" data-hid="mobile-web-app-capable" name="mobile-web-app-capable" content="yes"><meta data-n-head="1" data-hid="apple-mobile-web-app-capable" name="apple-mobile-web-app-capable" content="yes"><meta data-n-head="1" data-hid="apple-mobile-web-app-status-bar-style" name="apple-mobile-web-app-status-bar-style" content="black"><meta data-n-head="1" data-hid="apple-mobile-web-app-title" name="apple-mobile-web-app-title" content="Audiobookshelf"><meta data-n-head="1" data-hid="theme-color" name="theme-color" content="#232323"><meta data-n-head="1" data-hid="og:type" name="og:type" property="og:type" content="website"><meta data-n-head="1" data-hid="og:title" name="og:title" property="og:title" content="Audiobookshelf"><meta data-n-head="1" data-hid="og:site_name" name="og:site_name" property="og:site_name" content="Audiobookshelf"><title>Audiobookshelf</title><link data-n-head="1" rel="icon" type="image/x-icon" href="/audiobookshelf/favicon.ico"><link data-n-head="1" rel="apple-touch-icon" href="/audiobookshelf/ios_icon.png"><link data-n-head="1" data-hid="shortcut-icon" rel="shortcut icon" href="/audiobookshelf/icon.svg"><link data-n-head="1" data-hid="apple-touch-icon" rel="apple-touch-icon" href="/audiobookshelf/icon192.png" sizes="any"><link data-n-head="1" rel="manifest" href="/audiobookshelf/_nuxt/manifest.2f7e41c6.json" data-hid="manifest"><base href="/audiobookshelf/"><link rel="preload" href="/audiobookshelf/_nuxt/790ce0e.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/a66bc33.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/10761d5.js" as="script"><link rel="preload" href="/audiobookshelf/_nuxt/8fa8266.js" as="script">
> </head>
> <body>
> <div id="__nuxt"><style>#nuxt-loading{background:#fff;visibility:hidden;opacity:0;position:absolute;left:0;right:0;top:0;bottom:0;display:flex;justify-content:center;align-items:center;flex-direction:column;animation:nuxtLoadingIn 10s ease;-webkit-animation:nuxtLoadingIn 10s ease;animation-fill-mode:forwards;overflow:hidden}@keyframes nuxtLoadingIn{0%{visibility:hidden;opacity:0}20%{visibility:visible;opacity:0}100%{visibility:visible;opacity:1}}@-webkit-keyframes nuxtLoadingIn{0%{visibility:hidden;opacity:0}20%{visibility:visible;opacity:0}100%{visibility:visible;opacity:1}}#nuxt-loading>div,#nuxt-loading>div:after{border-radius:50%;width:5rem;height:5rem}#nuxt-loading>div{font-size:10px;position:relative;text-indent:-9999em;border:.5rem solid #f5f5f5;border-left:.5rem solid #000;-webkit-transform:translateZ(0);-ms-transform:translateZ(0);transform:translateZ(0);-webkit-animation:nuxtLoading 1.1s infinite linear;animation:nuxtLoading 1.1s infinite linear}#nuxt-loading.error>div{border-left:.5rem solid #ff4500;animation-duration:5s}@-webkit-keyframes nuxtLoading{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@keyframes nuxtLoading{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}</style> <script>window.addEventListener("error",(function(){var e=document.getElementById("nuxt-loading");e&&(e.className+=" error")}))</script> <div id="nuxt-loading" aria-live="polite" role="status"><div>Loading...</div></div> </div><script>window.__NUXT__={config:{version:"2.19.0",routerBasePath:"/audiobookshelf",_app:{basePath:"/audiobookshelf/",assetsPath:"/audiobookshelf/_nuxt/",cdnURL:null}}}</script>
> <script src="/audiobookshelf/_nuxt/790ce0e.js"></script><script src="/audiobookshelf/_nuxt/a66bc33.js"></script><script src="/audiobookshelf/_nuxt/10761d5.js"></script><script src="/audiobookshelf/_nuxt/8fa8266.js"></script></body>
> </html>
> ```
Can you confirm which version of the app you are on?
Also if you are listening through android auto
Can you confirm which version of the app you are on? Also if you are listening through android auto
very rarely use android auto.
app 0.9.79-beta at the moment. Installed/updated through the google play store. If I had to make a guess the battery drain started mid-late December 2024. If anything I upgraded android OS, but also listening to downloaded books when on the local wifi.
Looking through the logs I went from Abs Android 0.9.65-beta to Abs Android 0.9.79-beta in July 2023.
Reading up on nuxt-loading it looks like there is an 'infinite linear' loading bar. It might be started as an async task and never stop, but can't see what sort of object is loading. The .js files are all quite generic looking to me.
I think it might be worth noting too I just (today) added some more ram to the computer running audiobookshelf and it does appear quite a lot snappier now. I could imagine ungracefully terminating a progress bar could accumulate a few tasks in the background looping.
@codhopper commented on GitHub (Feb 7, 2025):
> Can you confirm which version of the app you are on? Also if you are listening through android auto
very rarely use android auto.
app 0.9.79-beta at the moment. Installed/updated through the google play store. If I had to make a guess the battery drain started mid-late December 2024. If anything I upgraded android OS, but also listening to downloaded books when on the local wifi.
Looking through the logs I went from Abs Android 0.9.65-beta to Abs Android 0.9.79-beta in July 2023.
Reading up on nuxt-loading it looks like there is an 'infinite linear' loading bar. It might be started as an async task and never stop, but can't see what sort of object is loading. The .js files are all quite generic looking to me.
I think it might be worth noting too I just (today) added some more ram to the computer running audiobookshelf and it does appear quite a lot snappier now. I could imagine ungracefully terminating a progress bar could accumulate a few tasks in the background looping.
In v0.9.79-beta released on 1/27/25 I made an update that confirmed it was #1322 which has solved this issue for users that don't use android auto. It still has to be solved for android auto. There may be some devices calling the problematic function when not using Android Auto. If are looking at logcat you can check if you see logs from that function.
You may be having a different issue unrelated to this one
@advplyr commented on GitHub (Feb 7, 2025):
This issue was opened 2 days after `v0.9.78-beta` was released on 1/19/25 and the cause of the battery increase is this PR https://github.com/advplyr/audiobookshelf-app/pull/1322.
In `v0.9.79-beta` released on 1/27/25 I made an update that confirmed it was #1322 which has solved this issue for users that don't use android auto. It still has to be solved for android auto. There may be some devices calling the [problematic function](https://github.com/ISO-B/audiobookshelf-app/blob/ad7ca595321c69cd62efab71695bde229b09a01d/android/app/src/main/java/com/audiobookshelf/app/player/PlayerNotificationService.kt#L1024) when not using Android Auto. If are looking at logcat you can check if you see logs from that function.
You may be having a different issue unrelated to this one
I've got the same issue, but only started using the app a couple of days ago, so don't have context against older versions.
Pixel 9 pro, also used android auto, but haven't been using the app in the car.
@daiv92 commented on GitHub (Feb 8, 2025):
I've got the same issue, but only started using the app a couple of days ago, so don't have context against older versions.
Pixel 9 pro, also used android auto, but haven't been using the app in the car.

For me (Samsung S23+ with Android 13) also the app has high system resource usage:
@TheZoker commented on GitHub (Feb 8, 2025):
For me (Samsung S23+ with Android 13) also the app has high system resource usage:

As the bug is the first relevant result when searching issues regarding high battery usage, and the battery usage is insanely high. My phone (Galaxy S23 Ultra, v0.9.79-beta):
dies halfway through the day, so a full battery lasts < 12 hours
becomes very sluggish every evening, with 2-10 second delays to taps, button presses and any interactions, up until the phone becomes unusable and I have to restart it (or it restarts itself when it hangs for too long)
Some observations that I have systematically documented throughout past weeks:
force stopping Audiobookshelf doesn't help resolve the issue, I have to restart the phone to make my phone usable again
I usually use Android Auto daily, and suspected it was related. For past 3 days I have not used Audiobookshelf on Android Auto, so I suspect it might have been a red herring.
Check if sluggishness is caused by high CPU usage: You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
Weirdly, CPU usage is not high when the phone is sluggish.
This issue was opened 2 days after v0.9.78-beta was released on 1/19/25 and the cause of the battery increase is this PR #1322.
In v0.9.79-beta released on 1/27/25 I made an update that confirmed it was #1322 which has solved this issue for users that don't use android auto. It still has to be solved for android auto. There may be some devices calling the problematic function when not using Android Auto. If are looking at logcat you can check if you see logs from that function.
You may be having a different issue unrelated to this one
adb logcat | grep onLoadChildren yields 0 results for me. Was that the function you were referring to?
Any thoughts on how to debug this issue further are more than welcome. Happy to contribute in any way.
@lightheaded commented on GitHub (Feb 15, 2025):
As the bug is the first relevant result when searching issues regarding high battery usage, and the battery usage is insanely high. My phone (Galaxy S23 Ultra, v0.9.79-beta):
- dies halfway through the day, so a full battery lasts < 12 hours
- becomes very sluggish every evening, with 2-10 second delays to taps, button presses and any interactions, up until the phone becomes unusable and I have to restart it (or it restarts itself when it hangs for too long)
Some observations that I have systematically documented throughout past weeks:
- force stopping Audiobookshelf doesn't help resolve the issue, I have to restart the phone to make my phone usable again
- I usually use Android Auto daily, and suspected it was related. For past 3 days I have not used Audiobookshelf on Android Auto, so I suspect it might have been a red herring.
> Check if sluggishness is caused by high CPU usage: You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
Weirdly, CPU usage is not high when the phone is sluggish.
> This issue was opened 2 days after `v0.9.78-beta` was released on 1/19/25 and the cause of the battery increase is this PR [#1322](https://github.com/advplyr/audiobookshelf-app/pull/1322).
>
> In `v0.9.79-beta` released on 1/27/25 I made an update that confirmed it was [#1322](https://github.com/advplyr/audiobookshelf-app/pull/1322) which has solved this issue for users that don't use android auto. It still has to be solved for android auto. There may be some devices calling the [problematic function](https://github.com/ISO-B/audiobookshelf-app/blob/ad7ca595321c69cd62efab71695bde229b09a01d/android/app/src/main/java/com/audiobookshelf/app/player/PlayerNotificationService.kt#L1024) when not using Android Auto. If are looking at logcat you can check if you see logs from that function.
>
> You may be having a different issue unrelated to this one
- `adb logcat | grep onLoadChildren` yields 0 results for me. Was that the function you were referring to?
Any thoughts on how to debug this issue further are more than welcome. Happy to contribute in any way.
downloaded or streaming books direct from server does not matter
behaviour - I go to sleep, set timer to 15 minutes - audiobooks fades out after 15 minutes, app keeps running and doing something, draining the battery. Overnight I have seen 25 % up to 40 % of battery drain.
several system warnings that audiobookshelf app is using to much system ressources
playback speed 1.6 - 1.75 - maybe it helps :-)
won't give more screenshots - there are enough already
If you need some logs or troubleshooting - I'm willing to do that.
at them moment using web-browser on phone - no drain
@Gunsi1973 commented on GitHub (Mar 20, 2025):
Since it is not resolve I pipe in as well
- Samsung Galaxy S24 Pro
- downloaded or streaming books direct from server does not matter
- behaviour - I go to sleep, set timer to 15 minutes - audiobooks fades out after 15 minutes, app keeps running and doing something, draining the battery. Overnight I have seen 25 % up to 40 % of battery drain.
- several system warnings that audiobookshelf app is using to much system ressources
- playback speed 1.6 - 1.75 - maybe it helps :-)
- won't give more screenshots - there are enough already
If you need some logs or troubleshooting - I'm willing to do that.
**at them moment using web-browser on phone - no drain**
Pixel 9 user here. The Battery drain started some weeks ago. Usually listening 30 to 45 minutes in the morning through Android Auto.
I barely touch my phone at work. On my way home I have around 20% of battery left.
When I check Audiobookshelfs Battery Usage it says around 35-45% drain since last charge which is by far the most of all apps or system services.
Hope this gets fixed soon. If you need anything I will do my best to provide you with data.
Until then the app is pretty much not usable for me. Will try to switch to Chrome Webapp until the issue gets fixed. Thanks in advance!
@cruux13 commented on GitHub (Mar 24, 2025):
Pixel 9 user here. The Battery drain started some weeks ago. Usually listening 30 to 45 minutes in the morning through Android Auto.
I barely touch my phone at work. On my way home I have around 20% of battery left.
When I check Audiobookshelfs Battery Usage it says around 35-45% drain since last charge which is by far the most of all apps or system services.
Hope this gets fixed soon. If you need anything I will do my best to provide you with data.
Until then the app is pretty much not usable for me. Will try to switch to Chrome Webapp until the issue gets fixed. Thanks in advance!
I've disconnected Android Auto and am listening through bluetooth only. 3 weeks and no battery drain. As soon as I connect to Android auto, open ABS and boom, sluggish and drained battery.
I'm also more than happy to help in any way I can. Could we figure out how to add necessary debug logs somewhere?
FYI those having this problem, there are apps like Lissen out there that work as clients, and do the job reasonably well, but they're not official..
@lightheaded commented on GitHub (Mar 24, 2025):
I've disconnected Android Auto and am listening through bluetooth only. 3 weeks and no battery drain. As soon as I connect to Android auto, open ABS and boom, sluggish and drained battery.
I'm also more than happy to help in any way I can. Could we figure out how to add necessary debug logs somewhere?
FYI those having this problem, there are apps like [Lissen](https://www.reddit.com/r/audiobookshelf/comments/1gc1xei/introducing_lissen_an_audibookshelf_app_for/?rdt=38414) out there that work as clients, and do the job reasonably well, but they're not official..
I'm experiencing the same issue, about 60% of my battery/day on a pixel 7xl when listening for about 45 minutes in the morning via AA.
@zachsteffens commented on GitHub (Apr 10, 2025):
I'm experiencing the same issue, about 60% of my battery/day on a pixel 7xl when listening for about 45 minutes in the morning via AA.
Huge battery drain, with but also without use of Android Auto
So it appears the bug is still relevant.
Is there any way to downgrade to a lower version on Google Play Store?
@rafjaf commented on GitHub (Apr 23, 2025):
Just to share my own experience:
- AudioBS 0.9.80-beta
- Google Pixel 8 Pro
- Huge battery drain, with but also without use of Android Auto
So it appears the bug is still relevant.
Is there any way to downgrade to a lower version on Google Play Store?
@rafjaf Have you connected to wireless android auto? Are you listening through anything besides bluetooth headphones?
@advplyr commented on GitHub (Apr 23, 2025):
@rafjaf Have you connected to wireless android auto? Are you listening through anything besides bluetooth headphones?
Came here looking if this was already an issue. I also have the issue with Android Auto use causing huge battery drain.
Pixel 9 Pro XL
AudioBS 0.9.80-beta
For me the temporary solution is to just force kill the application when I get out of my car (as in hold the bottom to get the app thumbnails to load and swipe it away). This will stop the app from chewing through my battery but also I have to select it each time I get into my car, because it doesn't know that I want to use the app.
@dsgraham81 commented on GitHub (Apr 24, 2025):
Came here looking if this was already an issue. I also have the issue with Android Auto use causing huge battery drain.
Pixel 9 Pro XL
AudioBS 0.9.80-beta
For me the temporary solution is to just force kill the application when I get out of my car (as in hold the bottom to get the app thumbnails to load and swipe it away). This will stop the app from chewing through my battery but also I have to select it each time I get into my car, because it doesn't know that I want to use the app.
@advplyr No, I am connecting through hardwired Android Auto (+ bluetooth headphones). But I think there may be two different problems because two days ago I had not used my car, just listening with headphones, and there was also the battery drain. Today I uninstalled Audiobookshelf 0.9.80-beta, reinstalled the apk from 0.9.77-beta, did not even listen to any book and still after a few hours the phone is burning hot, the mike is grizzling in some apps (curiously not the phone app but Whatsapp) and the battery is drained. In other words, it may have nothing to do with the problems having appeared in version 0.9.78-beta and the use of Android Auto, but perhaps with a recently installed ROM for my Pixel 8 Pro? I remember a new ROM was automatically installed a few days ago (more exactly : on 5 April 2025), might this be the cause ? I don't know, but in the meanwhile I am forced to uninstall Audiobookshelf
@rafjaf commented on GitHub (Apr 24, 2025):
@advplyr No, I am connecting through hardwired Android Auto (+ bluetooth headphones). But I think there may be two different problems because two days ago I had not used my car, just listening with headphones, and there was also the battery drain. Today I uninstalled Audiobookshelf 0.9.80-beta, reinstalled the apk from 0.9.77-beta, did not even listen to any book and still after a few hours the phone is burning hot, the mike is grizzling in some apps (curiously not the phone app but Whatsapp) and the battery is drained. In other words, it may have nothing to do with the problems having appeared in version 0.9.78-beta and the use of Android Auto, but perhaps with a recently installed ROM for my Pixel 8 Pro? I remember a new ROM was automatically installed a few days ago (more exactly : on 5 April 2025), might this be the cause ? I don't know, but in the meanwhile I am forced to uninstall Audiobookshelf
Pixel 5a here, battery also getting drained rather hefty after listening/streaming with ABS 0.9.80-beta
so i need to force stop it to get over a day without charging.
my second most consuming app (home assistant, with permanent websocket connection to server) only uses a third to half of it.
@kobius77 commented on GitHub (Apr 25, 2025):
Pixel 5a here, battery also getting drained rather hefty *after* listening/streaming with ABS 0.9.80-beta
so i need to force stop it to get over a day without charging.
my second most consuming app (home assistant, with permanent websocket connection to server) only uses a third to half of it.
Android auto logs have been added in v0.9.81 (available as of yesterday). These could be helpful in gaining insight into why users that are not using android auto are also experiencing heavy battery drain.
In the logs page there are now logs for onGetRoot and onLoadChildren which are the two functions that get called by the media browser service. Here are logs from me connecting to android auto and navigating around.
For anyone not using android auto and getting battery drain it would be helpful if you check the logs page and specifically look for the onGetRoot log which will show the client package name making a connection.
@advplyr commented on GitHub (Apr 26, 2025):
Android auto logs have been added in v0.9.81 (available as of yesterday). These could be helpful in gaining insight into why users that are not using android auto are also experiencing heavy battery drain.
As I mentioned in https://github.com/advplyr/audiobookshelf-app/issues/1446#issuecomment-2643168585, the functions set up to load data for android auto could be getting called when not using android auto. Android auto connects to a [media browser service](https://developer.android.com/media/legacy/audio/mediabrowserservice) and requests data that is then fetched from your server. This data loading is the main suspect for heavy battery drain.
In the logs page there are now logs for `onGetRoot` and `onLoadChildren` which are the two functions that get called by the media browser service. Here are logs from me connecting to android auto and navigating around.

For anyone not using android auto and getting battery drain it would be helpful if you check the logs page and specifically look for the `onGetRoot` log which will show the client package name making a connection.
Was this with streaming or a downloaded book? Was the app connected to the server or listening in offline mode (not attempting to sync progress to the server)?
For me, it was neither streaming nor downloaded, I literally was not using the app at all yesterday.
I just made a post on Reddit that led me here... from unplugging my Pixel 7 Pro in the morning until plugging my phone in at night (when my phone was at 10%), Audiobookshelf ate 19% of my entire phone battery despite the fact I didn't play an audiobook, or even open the app the entire day (you can see all usage is background, zero screen time).
I had three business apps on which I spent 3-4 hours on conference calls with multiple video and audio streams on each, half of those hours on-screen, watching streamed video from multiple streams. Yet Audiobookshelf, which did literally nothing all day, somehow used the same/more battery than all three of these apps (Zoom, Chime, Slack) combined.
Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
And turning off background usage isn't a good option either, because if you do that, books will stop playing at some random point when the app is not in focus.
I really hope this gets fixed soon.
After yesterday I'm now playing offline with Listen, but it eliminates one of the main features of this service, which is syncing between devices.
My son listens to an audiobook at night and sometimes I play it for him on my phone while driving if he wants to listen to it in the car. This bug makes this use case extremely difficult to maintain because the tablet and phone will no longer sync with each other.
@fsudolphin commented on GitHub (Apr 30, 2025):
> Was this with streaming or a downloaded book? Was the app connected to the server or listening in offline mode (not attempting to sync progress to the server)?

For me, it was neither streaming nor downloaded, I literally was not using the app at all yesterday.
I just made a post on Reddit that led me here... from unplugging my Pixel 7 Pro in the morning until plugging my phone in at night (when my phone was at 10%), Audiobookshelf ate 19% of my entire phone battery **despite the fact I didn't play an audiobook, or even open the app the entire day** (you can see all usage is background, zero screen time).
I had three business apps on which I spent 3-4 hours on conference calls with multiple video and audio streams on each, half of those hours on-screen, watching streamed video from multiple streams. Yet Audiobookshelf, which did literally nothing all day, somehow used the same/more battery than all three of these apps (Zoom, Chime, Slack) combined.
Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
And turning off background usage isn't a good option either, because if you do that, books will stop playing at some random point when the app is not in focus.
I really hope this gets fixed soon.
After yesterday I'm now playing offline with Listen, but it eliminates one of the main features of this service, which is syncing between devices.
My son listens to an audiobook at night and sometimes I play it for him on my phone while driving if he wants to listen to it in the car. This bug makes this use case extremely difficult to maintain because the tablet and phone will no longer sync with each other.
Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
That's what I'm trying to find out and why I added a bunch of Android Auto logs in the last update that are visible on the logs page.
I rarely use android auto so I added logs for all the requests that the app makes for android auto and logs anytime a connection is made to the media browser service.
@advplyr commented on GitHub (Apr 30, 2025):
> Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
That's what I'm trying to find out and why I added a bunch of Android Auto logs in the last update that are visible on the logs page.
I rarely use android auto so I added logs for all the requests that the app makes for android auto and logs anytime a connection is made to the media browser service.
Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
That's what I'm trying to find out and why I added a bunch of Android Auto logs in the last update that are visible on the logs page.
I rarely use android auto so I added logs for all the requests that the app makes for android auto and logs anytime a connection is made to the media browser service.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
@nealhead commented on GitHub (Apr 30, 2025):
I can send my logs if they help. I'm an android auto user. Is it safe to upload or do I need to sanitize? Or can I send direct some way?
-------- Original Message --------
On 4/30/25 12:12 PM, advplyr wrote:
> advplyr left a comment [(advplyr/audiobookshelf-app#1446)](https://github.com/advplyr/audiobookshelf-app/issues/1446#issuecomment-2842694262)
>
>> Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
>
> That's what I'm trying to find out and why I added a bunch of Android Auto logs in the last update that are visible on the logs page.
>
> I rarely use android auto so I added logs for all the requests that the app makes for android auto and logs anytime a connection is made to the media browser service.
>
> —
> Reply to this email directly, [view it on GitHub](https://github.com/advplyr/audiobookshelf-app/issues/1446#issuecomment-2842694262), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAA5TZ4RHETJMBBQBR7RUET24D76PAVCNFSM6AAAAABVTYSZMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBSGY4TIMRWGI).
> You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
You can share them here or DM me on Discord. Server addresses are removed by default.
What is more helpful than just sending logs would be to send logs and specify how you were using the device in the time window. For example, battery drained 19%, didn't open the app on my phone or inside android auto but was using android auto throughout the day.
Or, used the app in android auto from X time to X time then was using other android auto apps.
Basically what I'm looking for is activity in the media browser service and whether or not you were using the app during the time of the logs I'm looking at is the most important.
@advplyr commented on GitHub (Apr 30, 2025):
You can share them here or DM me on Discord. Server addresses are removed by default.
What is more helpful than just sending logs would be to send logs and specify how you were using the device in the time window. For example, battery drained 19%, didn't open the app on my phone or inside android auto but was using android auto throughout the day.
Or, used the app in android auto from X time to X time then was using other android auto apps.
Basically what I'm looking for is activity in the media browser service and whether or not you were using the app during the time of the logs I'm looking at is the most important.
i for one can't really see any relation to Android Auto. I'm using it, yes, irregulary several times a week, but mostly for short local trips, so barely with ABS, usually it's only Spotify running.
The days i'm using ABS i'm going by bike, so no AndroidAuto used at all.
But if i don't kill (ie 'force stop') the app after listening, it's draining the battery, no matter if it was a 'bike day' or a 'car day'.
@kobius77 commented on GitHub (Apr 30, 2025):
i for one can't really see any relation to Android Auto. I'm using it, yes, irregulary several times a week, but mostly for short local trips, so barely with ABS, usually it's only Spotify running.
The days i'm using ABS i'm going by bike, so no AndroidAuto used at all.
But if i don't kill (ie 'force stop') the app after listening, it's draining the battery, no matter if it was a 'bike day' or a 'car day'.
That is another good example of what would be helpful. We see your battery drained 15% today and you didn't connect to android auto at all. Then the logs should not show any connections to the media browser service, but we can't know that without checking the logs.
@advplyr commented on GitHub (Apr 30, 2025):
That is another good example of what would be helpful. We see your battery drained 15% today and you didn't connect to android auto at all. Then the logs should not show any connections to the media browser service, but we can't know that without checking the logs.
I've found that pausing the app stops the drain. It's annoying, but less impactful than force killing. Open multitask view (swipe up), press and hold on the ABS icon, then select pause app.
@nojjynb commented on GitHub (Apr 30, 2025):
I've found that pausing the app stops the drain. It's annoying, but less impactful than force killing. Open multitask view (swipe up), press and hold on the ABS icon, then select pause app.
Then the logs should not show any connections to the media browser service
that means no onGetRoot and onLoadChildren, right?
@kobius77 commented on GitHub (Apr 30, 2025):
> Then the logs should not show any connections to the media browser service
that means no onGetRoot and onLoadChildren, right?
when I listen with USB-C Cable Headphones > Battery drain (only with Audiobookshelf, not with Audible, Youtube Music and so on)
when I listen with Bluetooth Headsets > no Battery drain
using BT-Headset now with no drain at all
@Gunsi1973 commented on GitHub (May 1, 2025):
found out something really strange:
- when I listen with USB-C Cable Headphones > Battery drain (only with Audiobookshelf, not with Audible, Youtube Music and so on)
- when I listen with Bluetooth Headsets > no Battery drain
using BT-Headset now with no drain at all
when I listen with USB-C Cable Headphones > Battery drain (only with Audiobookshelf, not with Audible, Youtube Music and so on)
when I listen with Bluetooth Headsets > no Battery drain
using BT-Headset now with no drain at all
I wonder if the headphones are making requests to the media browser service. If you have logs while using the headphones we can check
@advplyr commented on GitHub (May 3, 2025):
> found out something really strange:
>
> * when I listen with USB-C Cable Headphones > Battery drain (only with Audiobookshelf, not with Audible, Youtube Music and so on)
> * when I listen with Bluetooth Headsets > no Battery drain
>
> using BT-Headset now with no drain at all
I wonder if the headphones are making requests to the media browser service. If you have logs while using the headphones we can check
This is just a hunch, but very frequently the media artwork is not shown on my Android Auto device. And on Android phone, the artwork is often wrong (from another book or media that is present in ABS at all). Perhaps something is going wrong with transferring artwork and it keeps retrying?
@lightheaded commented on GitHub (May 4, 2025):
This is just a hunch, but very frequently the media artwork is not shown on my Android Auto device. And on Android phone, the artwork is often wrong (from another book or media that is present in ABS at all). Perhaps something is going wrong with transferring artwork and it keeps retrying?
@rafjaf commented on GitHub (May 8, 2025):
It remains to be confirmed in the following days but, although it does not officially address this issue, Google's latest security update of May 2025 seems to have resolved the battery drain issue on my Pixel 8 Pro (see https://support.google.com/pixelphone/thread/342669628/mise-%C3%A0-jour-google-pixel-%E2%80%93-mai-2025?hl=fr&sjid=17447671235608649225-EU)
Just discover this thread via google. I have the same issue sadly. Was it on S22 and now also on Pixel 9 Pro.
So for now as I understand there is no fix for it, right?
@rosejoystick commented on GitHub (May 12, 2025):
Just discover this thread via google. I have the same issue sadly. Was it on S22 and now also on Pixel 9 Pro.
So for now as I understand there is no fix for it, right?
I noticed just now, around 4pm, that my phone battery was low and noticed ABS took 57% of it. I have not used Android Auto today, but I did last night, for the first time in a couple weeks. My phone was fully charged at 6am this morning when I woke up and listened to ~3 hours of audiobooks, after which the book stayed paused and I started working (I work from home) without touching my phone. The last onGetRoot log entry is at ~10pm last night, which is when I was using Android Auto to listen to a book. Since then it has only been Sync and Shake detector entries.
While I typed this out, my phone dropped another 3%, so I am going to go plug it in!
@Zeoic commented on GitHub (May 12, 2025):
I'll toss in my experience from today:
I noticed just now, around 4pm, that my phone battery was low and noticed ABS took 57% of it. I have not used Android Auto today, but I did last night, for the first time in a couple weeks. My phone was fully charged at 6am this morning when I woke up and listened to ~3 hours of audiobooks, after which the book stayed paused and I started working (I work from home) without touching my phone. The last onGetRoot log entry is at ~10pm last night, which is when I was using Android Auto to listen to a book. Since then it has only been Sync and Shake detector entries.
While I typed this out, my phone dropped another 3%, so I am going to go plug it in!
It seems to me that things have much improved, with regards to this, since the May update on my Pixel 7a.
@bossanova808 commented on GitHub (May 13, 2025):
> It remains to be confirmed in the following days but, although it does not officially address this issue, Google's latest security update of May 2025 seems to have resolved the battery drain issue on my Pixel 8 Pro (see https://support.google.com/pixelphone/thread/342669628/mise-%C3%A0-jour-google-pixel-%E2%80%93-mai-2025?hl=fr&sjid=17447671235608649225-EU)
It seems to me that things have much improved, with regards to this, since the May update on my Pixel 7a.
@RadicalityIncident commented on GitHub (Jun 4, 2025):
I am having the same issue, most people here seem to be Pixel users but I am not. I was using audiobookshelf on an Asus Zenphone 9 and now am using it on a Motorola Razr Plus 2024. I can definitely confirm that I don't get the background drain issue when using bluetooth headphones but if I do any listening through android auto it will happen. It also seems to cause my phone to warm up quite a bit as nearly without fail I will get a message that google maps had to "disable 3D buildings because my phone needs to cool down" when streaming through android auto.
@RadicalityIncident commented on GitHub (Jun 4, 2025):
I am having the same issue, most people here seem to be Pixel users but I am not. I was using audiobookshelf on an Asus Zenphone 9 and now am using it on a Motorola Razr Plus 2024. I can definitely confirm that I don't get the background drain issue when using bluetooth headphones but if I do any listening through android auto it will happen. It also seems to cause my phone to warm up quite a bit as nearly without fail I will get a message that google maps had to "disable 3D buildings because my phone needs to cool down" when streaming through android auto.
Same thing here on pixel 7a . I've been listening to downloaded audiobooks for ages without noticing any battery issues. Just got a new car with android auto and boom, exactly this issue. It's like after my morning listen on commute to work (~30mins) the audiobookshelf just keeps running in the background for hours leeching the battery. It usually eats up about 40-60% of battery in background usage (since last charge).
@valeo956 commented on GitHub (Jun 18, 2025):
Same thing here on pixel 7a . I've been listening to downloaded audiobooks for ages without noticing any battery issues. Just got a new car with android auto and boom, exactly this issue. It's like after my morning listen on commute to work (~30mins) the audiobookshelf just keeps running in the background for hours leeching the battery. It usually eats up about 40-60% of battery in background usage (since last charge).
Android auto for 5mins today, then obscene battery drain.
@jakwinnem commented on GitHub (Jun 23, 2025):
Same issue on Nothing Phone (2)
Android auto for 5mins today, then obscene battery drain.

Using a Pixel 8a, 36% battery use today, 16 minutes screen time and 11 hrs 2 minutes background time. I used Android auto in the morning (about 45 minutes) and then played on phone speaker during lunch break (about 45 minutes also). Interestingly, battery use seems to have increased a bit after the lunch session. The phone was hot during the day.
I have had these issues since starting to use the app a few weeks ago. I actually thought I had a hardware issue after getting a screen replacement around the same time.
@mrtnbr commented on GitHub (Jun 24, 2025):
Using a Pixel 8a, 36% battery use today, 16 minutes screen time and 11 hrs 2 minutes background time. I used Android auto in the morning (about 45 minutes) and then played on phone speaker during lunch break (about 45 minutes also). Interestingly, battery use seems to have increased a bit after the lunch session. The phone was hot during the day.
I have had these issues since starting to use the app a few weeks ago. I actually thought I had a hardware issue after getting a screen replacement around the same time.

Same issue observed. With 2min screen time (11h39min background), battery setting is set to optimized, ABS is my highest use app with 34%.
[Edit] phone is pixel 9 Pro
When using the browser to listen to my audiobooks no such drain occurs.
@Hoembi commented on GitHub (Jun 28, 2025):
Same issue observed. With 2min screen time (11h39min background), battery setting is set to optimized, ABS is my highest use app with 34%.
[Edit] phone is pixel 9 Pro
When using the browser to listen to my audiobooks no such drain occurs.

I too suffer this issue, I often use ABS without unlocking my phone, hitting play/pause on my headphones and turning the headphones off when I will not be using the application for a while however the duration of this the battery is used considerably - sometimes finishing the work day with 30% battery after only 1 hour of audiobook listening.
Happy to provide any diagnostics data if requested.
Note: I start and end the day with android auto for 15~ minutes then swap to headphones for 30m-1h30m during the workday.
@gatehead commented on GitHub (Jul 11, 2025):
I too suffer this issue, I often use ABS without unlocking my phone, hitting play/pause on my headphones and turning the headphones off when I will not be using the application for a while however the duration of this the battery is used considerably - sometimes finishing the work day with 30% battery after only 1 hour of audiobook listening.
Happy to provide any diagnostics data if requested.
Note: I start and end the day with android auto for 15~ minutes then swap to headphones for 30m-1h30m during the workday.
I had about 100gb of local books downloaded, I deleted all of that except the current book I am listening to and it completely solved this issue for me. I went from draining the battery in less than 10 hours to lasting days.
@Elmegaard commented on GitHub (Jul 15, 2025):
I had about 100gb of local books downloaded, I deleted all of that except the current book I am listening to and it completely solved this issue for me. I went from draining the battery in less than 10 hours to lasting days.
Interesting development, I used my car again for the first time in a couple of weeks, and I decided to listen to the Radio instead, and ABS didn't autoplay or even open on Android Auto, yet this bug is still happening. For the last hour or so I have watched it slowly climb to 5% of my battery life usage for today, so I will be rebooting my phone shortly to stop it.
@Zeoic commented on GitHub (Jul 18, 2025):
Interesting development, I used my car again for the first time in a couple of weeks, and I decided to listen to the Radio instead, and ABS didn't autoplay or even open on Android Auto, yet this bug is still happening. For the last hour or so I have watched it slowly climb to 5% of my battery life usage for today, so I will be rebooting my phone shortly to stop it.
Not sure if this is already documented above because there have been a lot of reports, but I was able to test this today using Android Auto.
I fully charged my phone while listening and connected to Android Auto, and then I monitored the battery use over the next hour (ABS open in the background with the player active, but no media playing). ABS was responsible for 40% of the battery in the background over the 30 minutes after disconnecting from the car (other use including watching YouTube videos, Discord, and phone in pocket, about 10 minutes each).
I then closed the media player in ABS without closing the app (30 minutes after disconnecting from Android Auto), and repeated the same phone usage (YouTube, Discord, and in pocket). ABS stopped background activity and returned to very little battery use as soon as I closed the player.
I did not see anything in the app logs after disconnecting from Android Auto.
@nichwall commented on GitHub (Jul 18, 2025):
Not sure if this is already documented above because there have been a lot of reports, but I was able to test this today using Android Auto.
I fully charged my phone while listening and connected to Android Auto, and then I monitored the battery use over the next hour (ABS open in the background with the player active, but no media playing). ABS was responsible for 40% of the battery in the background over the 30 minutes after disconnecting from the car (other use including watching YouTube videos, Discord, and phone in pocket, about 10 minutes each).
I then closed the media player in ABS without closing the app (30 minutes after disconnecting from Android Auto), and repeated the same phone usage (YouTube, Discord, and in pocket). ABS stopped background activity and returned to very little battery use as soon as I closed the player.
I did not see anything in the app logs after disconnecting from Android Auto.
This is still going on for me. The app has been running playing a local book all day but this used to only use about 20% rather than the 70 I saw today.
@Spart4n commented on GitHub (Aug 13, 2025):
This is still going on for me. The app has been running playing a local book all day but this used to only use about 20% rather than the 70 I saw today.
<img width="1344" height="2992" alt="Image" src="https://github.com/user-attachments/assets/8a4d7a5e-d460-46f2-b778-b5c36e31c56d" />
@MatthewMooreZA commented on GitHub (Aug 28, 2025):
Still having this issue here. My temporary work around is to use the Routines feature on my Samsung to close the Audiobookshelf app. I found that using the Bluetooth disconnect event worked better than the Android Auto disconnect event. In rare circumstances wireless interference while driving can cause Android Auto to disconnect temporarily, but the Bluetooth connection stays established.
@MatthewMooreZA commented on GitHub (Aug 28, 2025):
Still having this issue here. My temporary work around is to use the Routines feature on my Samsung to close the Audiobookshelf app. I found that using the Bluetooth disconnect event worked better than the Android Auto disconnect event. In rare circumstances wireless interference while driving can cause Android Auto to disconnect temporarily, but the Bluetooth connection stays established.

@github-actions[bot] commented on GitHub (Sep 4, 2025):
Fixed in [v0.10.1-beta](https://github.com/advplyr/audiobookshelf-app/releases/tag/v0.10.1-beta).
I've been using it since the update in my car with AA, and have not seen any battery drain! It was massive before, so it's marked as fixed in my book.
The images for the books still do not load on my car screen, which i assumed had something to do with the battery drain, but it does not.
I'm very happy with the fix and love Audiobookshelf and the app. Thank you!
@agrajagged commented on GitHub (Sep 7, 2025):
I've been using it since the update in my car with AA, and have not seen any battery drain! It was massive before, so it's marked as fixed in my book.
The images for the books still do not load on my car screen, which i assumed had something to do with the battery drain, but it does not.
I'm very happy with the fix and love Audiobookshelf and the app. Thank you!
Well, for me battery drain is gone but it seems to have lost support for quick actions. I am not getting an interface to control my audio through car display. Also shortcuts as rewind, skip, play, pause do not work anymore. Audio is playing but I need to control it on my Smartphone.
@cruux13 commented on GitHub (Sep 8, 2025):
Well, for me battery drain is gone but it seems to have lost support for quick actions. I am not getting an interface to control my audio through car display. Also shortcuts as rewind, skip, play, pause do not work anymore. Audio is playing but I need to control it on my Smartphone.
I can confirm cruux13's observation that the app does not appear to register with Android as a media player after the update.
@jakwinnem commented on GitHub (Sep 8, 2025):
I can confirm cruux13's observation that the app does not appear to register with Android as a media player after the update.
I don't know if it's related, but I've noticed since this fix was implemented the ABS server (docker container) is running up the CPU and memory usage to ~100% multiple times per day to the point I cannot connect to the ABS server, nor can I even connect to the machine on which it's running. I have to force stop the entire machine and reboot it to be able to get back into it. I'd like to blame something other than Audiobookshelf, but it's the only container running on that machine, and of my ~20 VMs it's the only one misbehaving.
@amsolenberg commented on GitHub (Sep 12, 2025):
I don't know if it's related, but I've noticed since this fix was implemented the ABS server (docker container) is running up the CPU and memory usage to ~100% multiple times per day to the point I cannot connect to the ABS server, nor can I even connect to the machine on which it's running. I have to force stop the entire machine and reboot it to be able to get back into it. I'd like to blame something other than Audiobookshelf, but it's the only container running on that machine, and of my ~20 VMs it's the only one misbehaving.
I don't know if it's related, but I've noticed since this fix was implemented the ABS server (docker container) is running up the CPU and memory usage to ~100% multiple times per day to the point I cannot connect to the ABS server, nor can I even connect to the machine on which it's running. I have to force stop the entire machine and reboot it to be able to get back into it. I'd like to blame something other than Audiobookshelf, but it's the only container running on that machine, and of my ~20 VMs it's the only one misbehaving.
This issue is specifically for the Android app having high CPU and battery usage, the server being at 100% CPU will be something completely separate. You can open an issue with relevant server logs in https://github.com/advplyr/audiobookshelf
@nichwall commented on GitHub (Sep 12, 2025):
> I don't know if it's related, but I've noticed since this fix was implemented the ABS server (docker container) is running up the CPU and memory usage to ~100% multiple times per day to the point I cannot connect to the ABS server, nor can I even connect to the machine on which it's running. I have to force stop the entire machine and reboot it to be able to get back into it. I'd like to blame something other than Audiobookshelf, but it's the only container running on that machine, and of my ~20 VMs it's the only one misbehaving.
This issue is specifically for the Android app having high CPU and battery usage, the server being at 100% CPU will be something completely separate. You can open an issue with relevant server logs in https://github.com/advplyr/audiobookshelf
Okay. I assumed this wasn't the right place, just seemed like it might be related as it began the same day this fix was implemented. Didn't know if something else got changed at the same time.
@amsolenberg commented on GitHub (Sep 12, 2025):
Okay. I assumed this wasn't the right place, just seemed like it might be related as it began the same day this fix was implemented. Didn't know if something else got changed at the same time.
Workaround for missing Android Auto Media Player Interface:
Just enable developer options in AA settings. Allow Unknown Sources in AA developer options. Brought me back my AA Interface with all the media controls on latest beta release
@cruux13 commented on GitHub (Sep 13, 2025):
Workaround for missing Android Auto Media Player Interface:
Just enable developer options in AA settings. Allow Unknown Sources in AA developer options. Brought me back my AA Interface with all the media controls on latest beta release
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 @faulker on GitHub (Jan 22, 2025).
What was the Problem?
I'm having battery usage issues, the usage has been much higher than in previous app versions. After about two hours of playtime, it has been running in the background for 6+ hours and accounted for 35% of my battery usage, five times the usage of any other app.
Steps to Reproduce the Issue
Use the app on a similar phone
What was Expected?
Less battery usage
Phone Model
Pixel 7a
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.9.78
Installation Source
Google Play Store
Additional Notes
I do have the widget enabled, I've removed it to see if that makes any difference.
@nichwall commented on GitHub (Jan 22, 2025):
Was this with streaming or a downloaded book? Was the app connected to the server or listening in offline mode (not attempting to sync progress to the server)?
I just checked my usage, and a downloaded book took 16% of my battery after 7.4 hours on a Pixel 6a
@faulker commented on GitHub (Jan 22, 2025):
It is an audiobook that I have previously downloaded from the server, I am not streaming anything from the server.
Removing the widget didn't help, today I listened for less than an hour yet the battery usage is around the same 37% of my used battery was from the app. The app is reporting that it has been running in the background for 3h 52m.
This time around I'm disabling the "pin media player" option to see if that helps at all
@Zibbp commented on GitHub (Jan 23, 2025):
I've also noticed this since the last last updated, 0.9.78. I'm listening to a downloaded book and it uses a significant amount of battery (something is using a lot of CPU as the phone warms up). Android claims 45% battery usage for ~5 hours of runtime.
@schinguhl commented on GitHub (Jan 23, 2025):
Its the same for me. After the last pixel 9 update (android 15, security patch of January) my audiobookshelf app uses up to 40% of my battery every day. Before this update it was not noticeable. Im listening to an downloaded audiobook and the network usage is almost 0.
@TDderpy commented on GitHub (Jan 23, 2025):
Same issues for me also! One thing I've noticed is everyone who's stated a phone model all seem to have pixel devices?
I myself are in a pixel 7 pro, might just be representative of the community here I'm not sure, but could be pixel devices specifically effected?
@kingmike67 commented on GitHub (Jan 23, 2025):
Noticed the same with me on my P8P. Now I can almost confirm 100% it's something (not sure what) in the pixel stock ROM that is causing it. When running a custom ROM, I can listen for hours, nearly half the day and it's only 15-20% battery drain. On Stock ROM I lose about 15% batter an hour listening. All books are streaming for me.
@Vilhjalmr26 commented on GitHub (Jan 23, 2025):
Same issue on my Pixel 9 Pro, very recently started burning through battery while in background and not listening. Yesterday I listened to downloaded audiobook for about 2 hours total, and audiobookshelf accounted for 57% of my daily battery usage. And that was with my battery having run down to 10% at the point when I checked, so a very significant amount of the battery.
@Zibbp commented on GitHub (Jan 23, 2025):
I have a Samsung S22 running Android 14 so I don't believe it is limited to Pixels.
@theniwo commented on GitHub (Jan 23, 2025):
Samsung Galaxy S20 Pro / Android 13 / One UI 5.1 / Nova Launcher Prime 8.0.18
ABS Mobile Version: 0.9.78-beta
ABS Server Version: 2.18.1 docker
No significant increase of CPU Load while streaming over cell and wifi as well as local playback. Widget enabled. Foreground and Background playback.
(You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch)
@faulker commented on GitHub (Jan 23, 2025):
Disabling "pin media player" had no effect, battery usage is still extremely high (41% over 7 hours today) with only 30 mins of listing time.
@theniwo commented on GitHub (Jan 23, 2025):
It doesn't even show up in my battery usage history of this week. But I have 60 minutes sleep timer enabled, though.
@kymahi commented on GitHub (Jan 23, 2025):
Just wanted to say I'm also having this same experience.
ROG Phone 6
app version 0.9.78-beta
listened to about 20 minutes of a (locally downloaded, not streamed) book this morning, did not download any other books or interact with the app outside of playing and pausing.
@theniwo commented on GitHub (Jan 23, 2025):
It was active in the background for 6.5 hrs.
Can you check the battery setting of the app (App-Info -> Battery)?
Mine is set to optimized. The other two options translate to
Make sure, you don't have it on Not limited, or whatever the setting is called in english.
@tdz262 commented on GitHub (Jan 24, 2025):
Pixel 7 Pro. I am streaming and it's used 77% battery in 11 hours of background use. I had my phone playing through Bluetooth speaker most of the day, I've plugged my phone back in multiple times through out the day because battery was getting low. Audiobook shelf is on Optimized.
@Ich-Eben commented on GitHub (Jan 25, 2025):
Have the same issue (Pixel 8a).
I did a few tests and figured out that it does not matter if you are listening locally or streaming. In fact, the app drains the battery even when it is only running in the background and you are not listening to anything at all.
I downgraded the app to version v0.9.77-beta and the problem was gone. So, there is definitely something wrong with version v0.9.78-beta.
@biuklija commented on GitHub (Jan 25, 2025):
Same issue, Samsung A55 (Android 14), ABS server at v2.18.1; v0.9.78-beta absolutely murders my battery life just by idling in the background after I stop playing an audiobook (local, streaming, makes no difference) even with screen off. I had to downgrade to 0.9.77 so can't provide battery usage stats, but they're similar to those seen in previous posts.
@advplyr commented on GitHub (Jan 27, 2025):
I believe I found the culprit for the battery issue. The hopeful fix is in v0.9.79-beta that was just made available in the app stores.
Please let me know what your experience is.
@schinguhl commented on GitHub (Jan 28, 2025):
works for me :-) The battery usage is back to normal (Pixel 9).
@kymahi commented on GitHub (Jan 28, 2025):
Still having high battery usage in the background on 0.9.79-beta.
I had it in my car playing through Android Auto, then disconnected it and started playing it immediately after through the speaker, playing for about 20 minutes. Then I paused it and haven't used it since
@Vilhjalmr26 commented on GitHub (Jan 28, 2025):
Mine has definitely been better. Was listening for about an hour on Android auto this morning, then paused and unused since. Drain since pausing has been minimal, it still pulled about double the power of Android auto, but not sure how those normally lines up.
So usage still seems a bit high, but background seems better at the least.
@TDderpy commented on GitHub (Jan 28, 2025):
Things are certainly better for me now, but usage is still the highest usage of all the apps, at around 40-60% but much less draining then before.
@faulker commented on GitHub (Jan 28, 2025):
Honestly, the battery usage seems worse for me with 0.9.79-beta, if not worse it is the same
@advplyr commented on GitHub (Jan 28, 2025):
Thanks for reporting.
I'm pretty sure this is now isolated to android auto.
If users who don't use android auto at all can confirm they have seen improvement that would be helpful.
@jaredtodworkman commented on GitHub (Jan 28, 2025):
I don't use Android Auto and my battery is back to normal.
Screenshot_20250128-164259.png
@lightheaded commented on GitHub (Jan 30, 2025):
I'm using 0.9.79-beta and today my phone was so sluggish to respond (i.e. it responded to the power button press after 2-3 seconds) I had to restart. I did use Android Auto earlier today. Funnily enough, force closing Audiobookshelf didn't resolve the sluggishness of the phone. I had to restart.
@theniwo commented on GitHub (Jan 30, 2025):
Check if sluggishness is caused by high CPU usage:
You can add and enable a CPU Load Widget in Androids Developer Settings -> GPU Watch
@lightheaded commented on GitHub (Jan 30, 2025):
Thanks! Will check next time it occurs
@thoughtlessdestiny commented on GitHub (Jan 31, 2025):
I've had high usage and just been streaming to Bluetooth earbuds. I'm on the 0.9.79-beta using a Pixel Fold.

@codhopper commented on GitHub (Feb 6, 2025):
I've noticed some pretty wild battery drain on my android client, even when it is idle in the background not playing anything. I did see it as high as ~60% total battery drain after listening to maybe 2 hours of locally downloaded audio book (pixel 6 pro). I did turn on debugging and couldn't see anything abnormal (initially I thought it might have been played status updates getting sent back).
tcpdump on the server side had a message coming back when the whole thing was backgrounded (the query stopped when the app was forced to quit). Before I started killing the app it was coming through about once every 4-5 seconds. Afterwards I couldn't get it to repeat at any sort of frequency. It seemed to be a reply with just "Loading...".
@advplyr commented on GitHub (Feb 6, 2025):
Can you confirm which version of the app you are on?
Also if you are listening through android auto
@codhopper commented on GitHub (Feb 7, 2025):
very rarely use android auto.
app 0.9.79-beta at the moment. Installed/updated through the google play store. If I had to make a guess the battery drain started mid-late December 2024. If anything I upgraded android OS, but also listening to downloaded books when on the local wifi.
Looking through the logs I went from Abs Android 0.9.65-beta to Abs Android 0.9.79-beta in July 2023.
Reading up on nuxt-loading it looks like there is an 'infinite linear' loading bar. It might be started as an async task and never stop, but can't see what sort of object is loading. The .js files are all quite generic looking to me.
I think it might be worth noting too I just (today) added some more ram to the computer running audiobookshelf and it does appear quite a lot snappier now. I could imagine ungracefully terminating a progress bar could accumulate a few tasks in the background looping.
@advplyr commented on GitHub (Feb 7, 2025):
This issue was opened 2 days after
v0.9.78-betawas released on 1/19/25 and the cause of the battery increase is this PR https://github.com/advplyr/audiobookshelf-app/pull/1322.In
v0.9.79-betareleased on 1/27/25 I made an update that confirmed it was #1322 which has solved this issue for users that don't use android auto. It still has to be solved for android auto. There may be some devices calling the problematic function when not using Android Auto. If are looking at logcat you can check if you see logs from that function.You may be having a different issue unrelated to this one
@daiv92 commented on GitHub (Feb 8, 2025):
I've got the same issue, but only started using the app a couple of days ago, so don't have context against older versions.
Pixel 9 pro, also used android auto, but haven't been using the app in the car.
@TheZoker commented on GitHub (Feb 8, 2025):
For me (Samsung S23+ with Android 13) also the app has high system resource usage:

@lightheaded commented on GitHub (Feb 15, 2025):
As the bug is the first relevant result when searching issues regarding high battery usage, and the battery usage is insanely high. My phone (Galaxy S23 Ultra, v0.9.79-beta):
Some observations that I have systematically documented throughout past weeks:
Weirdly, CPU usage is not high when the phone is sluggish.
adb logcat | grep onLoadChildrenyields 0 results for me. Was that the function you were referring to?Any thoughts on how to debug this issue further are more than welcome. Happy to contribute in any way.
@Gunsi1973 commented on GitHub (Mar 20, 2025):
Since it is not resolve I pipe in as well
If you need some logs or troubleshooting - I'm willing to do that.
at them moment using web-browser on phone - no drain
@cruux13 commented on GitHub (Mar 24, 2025):
Pixel 9 user here. The Battery drain started some weeks ago. Usually listening 30 to 45 minutes in the morning through Android Auto.
I barely touch my phone at work. On my way home I have around 20% of battery left.
When I check Audiobookshelfs Battery Usage it says around 35-45% drain since last charge which is by far the most of all apps or system services.
Hope this gets fixed soon. If you need anything I will do my best to provide you with data.
Until then the app is pretty much not usable for me. Will try to switch to Chrome Webapp until the issue gets fixed. Thanks in advance!
@lightheaded commented on GitHub (Mar 24, 2025):
I've disconnected Android Auto and am listening through bluetooth only. 3 weeks and no battery drain. As soon as I connect to Android auto, open ABS and boom, sluggish and drained battery.
I'm also more than happy to help in any way I can. Could we figure out how to add necessary debug logs somewhere?
FYI those having this problem, there are apps like Lissen out there that work as clients, and do the job reasonably well, but they're not official..
@zachsteffens commented on GitHub (Apr 10, 2025):
I'm experiencing the same issue, about 60% of my battery/day on a pixel 7xl when listening for about 45 minutes in the morning via AA.
@rafjaf commented on GitHub (Apr 23, 2025):
Just to share my own experience:
So it appears the bug is still relevant.
Is there any way to downgrade to a lower version on Google Play Store?
@advplyr commented on GitHub (Apr 23, 2025):
@rafjaf Have you connected to wireless android auto? Are you listening through anything besides bluetooth headphones?
@dsgraham81 commented on GitHub (Apr 24, 2025):
Came here looking if this was already an issue. I also have the issue with Android Auto use causing huge battery drain.
Pixel 9 Pro XL
AudioBS 0.9.80-beta
For me the temporary solution is to just force kill the application when I get out of my car (as in hold the bottom to get the app thumbnails to load and swipe it away). This will stop the app from chewing through my battery but also I have to select it each time I get into my car, because it doesn't know that I want to use the app.
@rafjaf commented on GitHub (Apr 24, 2025):
@advplyr No, I am connecting through hardwired Android Auto (+ bluetooth headphones). But I think there may be two different problems because two days ago I had not used my car, just listening with headphones, and there was also the battery drain. Today I uninstalled Audiobookshelf 0.9.80-beta, reinstalled the apk from 0.9.77-beta, did not even listen to any book and still after a few hours the phone is burning hot, the mike is grizzling in some apps (curiously not the phone app but Whatsapp) and the battery is drained. In other words, it may have nothing to do with the problems having appeared in version 0.9.78-beta and the use of Android Auto, but perhaps with a recently installed ROM for my Pixel 8 Pro? I remember a new ROM was automatically installed a few days ago (more exactly : on 5 April 2025), might this be the cause ? I don't know, but in the meanwhile I am forced to uninstall Audiobookshelf
@kobius77 commented on GitHub (Apr 25, 2025):
Pixel 5a here, battery also getting drained rather hefty after listening/streaming with ABS 0.9.80-beta
so i need to force stop it to get over a day without charging.
my second most consuming app (home assistant, with permanent websocket connection to server) only uses a third to half of it.
@advplyr commented on GitHub (Apr 26, 2025):
Android auto logs have been added in v0.9.81 (available as of yesterday). These could be helpful in gaining insight into why users that are not using android auto are also experiencing heavy battery drain.
As I mentioned in https://github.com/advplyr/audiobookshelf-app/issues/1446#issuecomment-2643168585, the functions set up to load data for android auto could be getting called when not using android auto. Android auto connects to a media browser service and requests data that is then fetched from your server. This data loading is the main suspect for heavy battery drain.
In the logs page there are now logs for
onGetRootandonLoadChildrenwhich are the two functions that get called by the media browser service. Here are logs from me connecting to android auto and navigating around.For anyone not using android auto and getting battery drain it would be helpful if you check the logs page and specifically look for the
onGetRootlog which will show the client package name making a connection.@fsudolphin commented on GitHub (Apr 30, 2025):
For me, it was neither streaming nor downloaded, I literally was not using the app at all yesterday.
I just made a post on Reddit that led me here... from unplugging my Pixel 7 Pro in the morning until plugging my phone in at night (when my phone was at 10%), Audiobookshelf ate 19% of my entire phone battery despite the fact I didn't play an audiobook, or even open the app the entire day (you can see all usage is background, zero screen time).
I had three business apps on which I spent 3-4 hours on conference calls with multiple video and audio streams on each, half of those hours on-screen, watching streamed video from multiple streams. Yet Audiobookshelf, which did literally nothing all day, somehow used the same/more battery than all three of these apps (Zoom, Chime, Slack) combined.
Yes, I use Android Auto daily. What is ABS even doing in the background that uses so much energy? I'm gathering that's still a mystery to be solved?
And turning off background usage isn't a good option either, because if you do that, books will stop playing at some random point when the app is not in focus.
I really hope this gets fixed soon.
After yesterday I'm now playing offline with Listen, but it eliminates one of the main features of this service, which is syncing between devices.
My son listens to an audiobook at night and sometimes I play it for him on my phone while driving if he wants to listen to it in the car. This bug makes this use case extremely difficult to maintain because the tablet and phone will no longer sync with each other.
@advplyr commented on GitHub (Apr 30, 2025):
That's what I'm trying to find out and why I added a bunch of Android Auto logs in the last update that are visible on the logs page.
I rarely use android auto so I added logs for all the requests that the app makes for android auto and logs anytime a connection is made to the media browser service.
@nealhead commented on GitHub (Apr 30, 2025):
I can send my logs if they help. I'm an android auto user. Is it safe to upload or do I need to sanitize? Or can I send direct some way?
-------- Original Message --------
On 4/30/25 12:12 PM, advplyr wrote:
@advplyr commented on GitHub (Apr 30, 2025):
You can share them here or DM me on Discord. Server addresses are removed by default.
What is more helpful than just sending logs would be to send logs and specify how you were using the device in the time window. For example, battery drained 19%, didn't open the app on my phone or inside android auto but was using android auto throughout the day.
Or, used the app in android auto from X time to X time then was using other android auto apps.
Basically what I'm looking for is activity in the media browser service and whether or not you were using the app during the time of the logs I'm looking at is the most important.
@kobius77 commented on GitHub (Apr 30, 2025):
i for one can't really see any relation to Android Auto. I'm using it, yes, irregulary several times a week, but mostly for short local trips, so barely with ABS, usually it's only Spotify running.
The days i'm using ABS i'm going by bike, so no AndroidAuto used at all.
But if i don't kill (ie 'force stop') the app after listening, it's draining the battery, no matter if it was a 'bike day' or a 'car day'.
@advplyr commented on GitHub (Apr 30, 2025):
That is another good example of what would be helpful. We see your battery drained 15% today and you didn't connect to android auto at all. Then the logs should not show any connections to the media browser service, but we can't know that without checking the logs.
@nojjynb commented on GitHub (Apr 30, 2025):
I've found that pausing the app stops the drain. It's annoying, but less impactful than force killing. Open multitask view (swipe up), press and hold on the ABS icon, then select pause app.
@kobius77 commented on GitHub (Apr 30, 2025):
that means no onGetRoot and onLoadChildren, right?
@advplyr commented on GitHub (Apr 30, 2025):
Correct
@Gunsi1973 commented on GitHub (May 1, 2025):
found out something really strange:
using BT-Headset now with no drain at all
@advplyr commented on GitHub (May 3, 2025):
I wonder if the headphones are making requests to the media browser service. If you have logs while using the headphones we can check
@lightheaded commented on GitHub (May 4, 2025):
This is just a hunch, but very frequently the media artwork is not shown on my Android Auto device. And on Android phone, the artwork is often wrong (from another book or media that is present in ABS at all). Perhaps something is going wrong with transferring artwork and it keeps retrying?
@rafjaf commented on GitHub (May 8, 2025):
It remains to be confirmed in the following days but, although it does not officially address this issue, Google's latest security update of May 2025 seems to have resolved the battery drain issue on my Pixel 8 Pro (see https://support.google.com/pixelphone/thread/342669628/mise-%C3%A0-jour-google-pixel-%E2%80%93-mai-2025?hl=fr&sjid=17447671235608649225-EU)
@rosejoystick commented on GitHub (May 12, 2025):
Just discover this thread via google. I have the same issue sadly. Was it on S22 and now also on Pixel 9 Pro.
So for now as I understand there is no fix for it, right?
@Zeoic commented on GitHub (May 12, 2025):
I'll toss in my experience from today:
I noticed just now, around 4pm, that my phone battery was low and noticed ABS took 57% of it. I have not used Android Auto today, but I did last night, for the first time in a couple weeks. My phone was fully charged at 6am this morning when I woke up and listened to ~3 hours of audiobooks, after which the book stayed paused and I started working (I work from home) without touching my phone. The last onGetRoot log entry is at ~10pm last night, which is when I was using Android Auto to listen to a book. Since then it has only been Sync and Shake detector entries.
While I typed this out, my phone dropped another 3%, so I am going to go plug it in!
@bossanova808 commented on GitHub (May 13, 2025):
It seems to me that things have much improved, with regards to this, since the May update on my Pixel 7a.
@RadicalityIncident commented on GitHub (Jun 4, 2025):
I am having the same issue, most people here seem to be Pixel users but I am not. I was using audiobookshelf on an Asus Zenphone 9 and now am using it on a Motorola Razr Plus 2024. I can definitely confirm that I don't get the background drain issue when using bluetooth headphones but if I do any listening through android auto it will happen. It also seems to cause my phone to warm up quite a bit as nearly without fail I will get a message that google maps had to "disable 3D buildings because my phone needs to cool down" when streaming through android auto.
@valeo956 commented on GitHub (Jun 18, 2025):
Same thing here on pixel 7a . I've been listening to downloaded audiobooks for ages without noticing any battery issues. Just got a new car with android auto and boom, exactly this issue. It's like after my morning listen on commute to work (~30mins) the audiobookshelf just keeps running in the background for hours leeching the battery. It usually eats up about 40-60% of battery in background usage (since last charge).
@jakwinnem commented on GitHub (Jun 23, 2025):
Same issue on Nothing Phone (2)
Android auto for 5mins today, then obscene battery drain.
@mrtnbr commented on GitHub (Jun 24, 2025):
Using a Pixel 8a, 36% battery use today, 16 minutes screen time and 11 hrs 2 minutes background time. I used Android auto in the morning (about 45 minutes) and then played on phone speaker during lunch break (about 45 minutes also). Interestingly, battery use seems to have increased a bit after the lunch session. The phone was hot during the day.
I have had these issues since starting to use the app a few weeks ago. I actually thought I had a hardware issue after getting a screen replacement around the same time.
@Hoembi commented on GitHub (Jun 28, 2025):
Same issue observed. With 2min screen time (11h39min background), battery setting is set to optimized, ABS is my highest use app with 34%.
[Edit] phone is pixel 9 Pro
When using the browser to listen to my audiobooks no such drain occurs.
@gatehead commented on GitHub (Jul 11, 2025):
I too suffer this issue, I often use ABS without unlocking my phone, hitting play/pause on my headphones and turning the headphones off when I will not be using the application for a while however the duration of this the battery is used considerably - sometimes finishing the work day with 30% battery after only 1 hour of audiobook listening.
Happy to provide any diagnostics data if requested.
Note: I start and end the day with android auto for 15~ minutes then swap to headphones for 30m-1h30m during the workday.
@Elmegaard commented on GitHub (Jul 15, 2025):
I had about 100gb of local books downloaded, I deleted all of that except the current book I am listening to and it completely solved this issue for me. I went from draining the battery in less than 10 hours to lasting days.
@Zeoic commented on GitHub (Jul 18, 2025):
Interesting development, I used my car again for the first time in a couple of weeks, and I decided to listen to the Radio instead, and ABS didn't autoplay or even open on Android Auto, yet this bug is still happening. For the last hour or so I have watched it slowly climb to 5% of my battery life usage for today, so I will be rebooting my phone shortly to stop it.
@nichwall commented on GitHub (Jul 18, 2025):
Not sure if this is already documented above because there have been a lot of reports, but I was able to test this today using Android Auto.
I fully charged my phone while listening and connected to Android Auto, and then I monitored the battery use over the next hour (ABS open in the background with the player active, but no media playing). ABS was responsible for 40% of the battery in the background over the 30 minutes after disconnecting from the car (other use including watching YouTube videos, Discord, and phone in pocket, about 10 minutes each).
I then closed the media player in ABS without closing the app (30 minutes after disconnecting from Android Auto), and repeated the same phone usage (YouTube, Discord, and in pocket). ABS stopped background activity and returned to very little battery use as soon as I closed the player.
I did not see anything in the app logs after disconnecting from Android Auto.
@Spart4n commented on GitHub (Aug 13, 2025):
This is still going on for me. The app has been running playing a local book all day but this used to only use about 20% rather than the 70 I saw today.
@MatthewMooreZA commented on GitHub (Aug 28, 2025):
Still having this issue here. My temporary work around is to use the Routines feature on my Samsung to close the Audiobookshelf app. I found that using the Bluetooth disconnect event worked better than the Android Auto disconnect event. In rare circumstances wireless interference while driving can cause Android Auto to disconnect temporarily, but the Bluetooth connection stays established.
@github-actions[bot] commented on GitHub (Sep 4, 2025):
Fixed in v0.10.1-beta.
@advplyr commented on GitHub (Sep 6, 2025):
Can anyone confirm yet whether the update in v0.10.1 resolved this?
@agrajagged commented on GitHub (Sep 7, 2025):
I've been using it since the update in my car with AA, and have not seen any battery drain! It was massive before, so it's marked as fixed in my book.
The images for the books still do not load on my car screen, which i assumed had something to do with the battery drain, but it does not.
I'm very happy with the fix and love Audiobookshelf and the app. Thank you!
@cruux13 commented on GitHub (Sep 8, 2025):
Well, for me battery drain is gone but it seems to have lost support for quick actions. I am not getting an interface to control my audio through car display. Also shortcuts as rewind, skip, play, pause do not work anymore. Audio is playing but I need to control it on my Smartphone.
@jakwinnem commented on GitHub (Sep 8, 2025):
I can confirm cruux13's observation that the app does not appear to register with Android as a media player after the update.
@amsolenberg commented on GitHub (Sep 12, 2025):
I don't know if it's related, but I've noticed since this fix was implemented the ABS server (docker container) is running up the CPU and memory usage to ~100% multiple times per day to the point I cannot connect to the ABS server, nor can I even connect to the machine on which it's running. I have to force stop the entire machine and reboot it to be able to get back into it. I'd like to blame something other than Audiobookshelf, but it's the only container running on that machine, and of my ~20 VMs it's the only one misbehaving.
@nichwall commented on GitHub (Sep 12, 2025):
This issue is specifically for the Android app having high CPU and battery usage, the server being at 100% CPU will be something completely separate. You can open an issue with relevant server logs in https://github.com/advplyr/audiobookshelf
@amsolenberg commented on GitHub (Sep 12, 2025):
Okay. I assumed this wasn't the right place, just seemed like it might be related as it began the same day this fix was implemented. Didn't know if something else got changed at the same time.
@cruux13 commented on GitHub (Sep 13, 2025):
Workaround for missing Android Auto Media Player Interface:
Just enable developer options in AA settings. Allow Unknown Sources in AA developer options. Brought me back my AA Interface with all the media controls on latest beta release