cm0002@lemmy.world to Selfhosted@lemmy.worldEnglish · 16 hours agoI threw away Audible’s app, and now I self-host my audiobooks - Ars Technicaarstechnica.comexternal-linkmessage-square66fedilinkarrow-up1460
arrow-up1460external-linkI threw away Audible’s app, and now I self-host my audiobooks - Ars Technicaarstechnica.comcm0002@lemmy.world to Selfhosted@lemmy.worldEnglish · 16 hours agomessage-square66fedilink
minus-squareDave@lemmy.nzlinkfedilinkEnglisharrow-up5·16 hours agoF-Droid. Might be relevant that I’m on GrapheneOS.
minus-squareenemenemu@lemm.eelinkfedilinkEnglisharrow-up2·6 hours agoIt’s working without issues on my gos
minus-squareDave@lemmy.nzlinkfedilinkEnglisharrow-up1·5 hours agoGood to know. I wonder what the issue is. It has always done it, for the year or more I’ve used it.
minus-squareenemenemu@lemm.eelinkfedilinkEnglisharrow-up2·5 hours agoIn the global app settings there is an entry “log” maybe you can find some useful info in there. Also, check out the Try the demo https://audiobooks.dev/ with demo/demo https://www.audiobookshelf.org/showcase
minus-squareDave@lemmy.nzlinkfedilinkEnglisharrow-up2·5 hours agoI’ve looked and looked and can’t find this “log” entry? By global settings, you mean tap the menu at the top right and tap settings?
minus-squareenemenemu@lemm.eelinkfedilinkEnglisharrow-up2·5 hours agoI mean the global android settings Android > settings > apps > audiobookshelf > view logs Also, you can have a look into the server logs, maybe there’s a hint. podman logs -f audiobookshelf (or docker)
minus-squareDave@lemmy.nzlinkfedilinkEnglisharrow-up2·4 hours agoAh I didn’t know about the android logs. Next time it happens I’ll check them. Normally I’m not near access to the server when it happens. I just tried to force android to kill it but I opened up 20 other apps and when I switched back it was still active so I guess I’ll just have to wait.
minus-squareShowroom7561@lemmy.calinkfedilinkEnglisharrow-up4·16 hours agoHmm. Perhaps. I’m just on stock Android, so I couldn’t even test further if I wanted to :( Sorry, mate.
F-Droid. Might be relevant that I’m on GrapheneOS.
It’s working without issues on my gos
Good to know. I wonder what the issue is. It has always done it, for the year or more I’ve used it.
In the global app settings there is an entry “log” maybe you can find some useful info in there. Also, check out the
Try the demo https://audiobooks.dev/ with demo/demo https://www.audiobookshelf.org/showcase
I’ve looked and looked and can’t find this “log” entry? By global settings, you mean tap the menu at the top right and tap settings?
I mean the global android settings
Android > settings > apps > audiobookshelf > view logs
Also, you can have a look into the server logs, maybe there’s a hint.
podman logs -f audiobookshelf(ordocker)Ah I didn’t know about the android logs. Next time it happens I’ll check them. Normally I’m not near access to the server when it happens.
I just tried to force android to kill it but I opened up 20 other apps and when I switched back it was still active so I guess I’ll just have to wait.
Hmm. Perhaps. I’m just on stock Android, so I couldn’t even test further if I wanted to :( Sorry, mate.