mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-03-02 22:46:55 -05:00
[Bug]: the phone's battery drains rapidly and overheats severely. At this point, opening the Audiobookshelf app results in a blank screen. #2634
Labels
No labels
authentication
awaiting release
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/audiobookshelf-advplyr#2634
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zhuzhu88920 on GitHub (Mar 1, 2025).
What happened?
During normal playback of audiobooks on the iOS client, the phone's battery drains rapidly and overheats severely. At this point, opening the Audiobookshelf app results in a blank screen. After exiting and reopening the app, playback resumes normally, and the phone gradually cools down, with battery consumption returning to normal. However, this issue recurs after a while, particularly after the server was updated to version 2.19.5, when it becomes even more frequent.
What did you expect to happen?
fix bug
Steps to reproduce the issue
Audiobookshelf version
0.9.79-beta
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
@nichwall commented on GitHub (Mar 2, 2025):
Likely a duplicate of https://github.com/advplyr/audiobookshelf-app/issues/1341
@zhuzhu88920 commented on GitHub (Mar 3, 2025):
Yes, this issue is very similar to #1341. I'm using an iPhone 14 with iOS 17~~18.3 (this bug has been around for a long time, and despite multiple system upgrades, it remains the same, though it has become more frequent recently). When I use nplayer to play through a WebDAV connection, everything works perfectly, which makes me feel like the problem is related to the network connection. The speed is very fast when I connect with nplayer, while Audiobookshelf is quite slow even when connected to the local network.
@nichwall commented on GitHub (Mar 3, 2025):
If it has been happening for a while, this will be an issue with the mobile app instead of the server.
Also https://github.com/advplyr/audiobookshelf-app/issues/1334
@zhuzhu88920 commented on GitHub (Mar 6, 2025):
Yes, this issue has become more frequent since the server was upgraded to 2.19.5. I also believe that #1341 and #1334 are related to the same problem I'm experiencing.
@zhuzhu88920 commented on GitHub (Mar 6, 2025):
Moreover, the ABS connection to the server is very slow. It takes several minutes from opening the app to logging into the server, selecting the audio file, and starting playback, even when connected to the local network. Other apps connect to my NAS within seconds on the same local network. Why is ABS so slow?
I suspect that the earlier issues are caused by the unstable network connection mechanism of ABS.
@nichwall commented on GitHub (Mar 6, 2025):
Does rolling back to an older version of the server change anything? How are you connecting to the server? Direct IP, reverse proxy, VPN?
This still sounds like an issue with the app and not the server, especially if you have an unstable connection.
@zhuzhu88920 commented on GitHub (Mar 8, 2025):
When I'm on the local network, I use a direct IP connection, and when I'm outside, I use a reverse proxy.
@zhuzhu88920 commented on GitHub (Mar 8, 2025):
I have also tried using a VPN, but the issue persists.
@nichwall commented on GitHub (Mar 10, 2025):
Can you confirm that the behavior still happens with an older version of the server?
@zhuzhu88920 commented on GitHub (Mar 13, 2025):
yes ，confirm
@advplyr commented on GitHub (Sep 6, 2025):
Is this an issue with the ios mobile app or the web client?