BubbleUPnP App drains the entire battery charge

[gg12...@googlemail.com]

Hello,

in the last few weeks I have tried to listen to local (via minimserver) or qobuz music twice when I could not sleep. Usually after the playllist is finished playback stops and after a while the bubbleUpnP app stops running, too.

But these two times after I woke app again, the phone had shut down because the battery was at 0%. So it seems that the BubbleUPnP app consumes all the battery charge. This was not the case in earlier version. Is this a known issue?

Pixel 8

Android 16 (all up to date)

BubbleUPnP app 4.6.2.1

[Michael Pujos]

Hi,

Difficult to tell exactly and battery use issue can be difficult to troubleshoot.

- I am assuming you where playing to your Pixel 8 acting as renderer ?

- do you have 'More > Settings > Battery saving mode' enabled ?

- did you ever notice if your phone was abnormally hot to the touch when the app is running ?

Can you do this test (with the phone not plugged to power):

- for good measure and for this test, disable 'More > Settings > Battery saving mode' 

- in More > Settings > Control, set 'Kill on inactivity' to '5 minutes' (default is 15 but that's to make that test faster)

- populate the Playlist tab with a few tracks as you normally would (maybe only starts with 3 or 4 tracks) and play first track

- let it play until the end with screen off (as you would at night when you noticed this issue)

- after playback has stopped, wait for at least 5 minutes and check if BubbleUPnP is still running (look if its notification is still present

in the notification drawer, in which case it is running). Normally it should have killed itself

[Gert Brinkmann]

Hello Michael,

On 12/14/25 18:34, Michael Pujos wrote:

Hi,

Difficult to tell exactly and battery use issue can be difficult to troubleshoot.

- I am assuming you where playing to your Pixel 8 acting as renderer ?

yes, correct.

via bluetooth in-ears Sennheiser Momentum True Wireless 4. Maybe they or the bluetooth connection can be the culprit, too?

- do you have 'More > Settings > Battery saving mode' enabled ?

Yes, this is enabled

- did you ever notice if your phone was abnormally hot to the touch when the app is running ?

No, I did not notice this.

Can you do this test (with the phone not plugged to power):

- for good measure and for this test, disable 'More > Settings > Battery saving mode' 

- in More > Settings > Control, set 'Kill on inactivity' to '5 minutes' (default is 15 but that's to make that test faster)

- populate the Playlist tab with a few tracks as you normally would (maybe only starts with 3 or 4 tracks) and play first track

- let it play until the end with screen off (as you would at night when you noticed this issue)

- after playback has stopped, wait for at least 5 minutes and check if BubbleUPnP is still running (look if its notification is still present

in the notification drawer, in which case it is running). Normally it should have killed itself

I have tried this now twice.

First I only played one track and did wait after this for twenty minutes (because I did forget to reduce the kill time from 15 to 5 minutes). BubbleUPnP had exited fine when I checked it.

Then I reduced kill time to 5 minutes and activated the no-disturbe-night-mode in Android that I have activated at night. Playing 4 tracks of 20 minutes and waited 10 minutes before checking the phone. => Everything ok. BubbleUPnP did exit.

Now I wonder what the problem could be. In both problematic cases I had about 30-40% SoC left. But the next morning the phone was powered off with 0% battery charge left. Usually it should have >>20% left. This is annoying because the alarm clock is not working anymore in this case, too.

(And the other choice that I have to listen via the qobuz app has another problem: Even if the auto-play-feature is turned off, the playlist automatically is filled with new tracks. So music never ends. This is not what I want when I listen to music to better fall asleep.)

Greetings
Gert

On Sunday, December 14, 2025 at 11:33:16 AM UTC+1 gg12...@googlemail.com wrote:

Hello,

in the last few weeks I have tried to listen to local (via minimserver) or qobuz music twice when I could not sleep. Usually after the playllist is finished playback stops and after a while the bubbleUpnP app stops running, too.

But these two times after I woke app again, the phone had shut down because the battery was at 0%. So it seems that the BubbleUPnP app consumes all the battery charge. This was not the case in earlier version. Is this a known issue?

Pixel 8

Android 16 (all up to date)

BubbleUPnP app 4.6.2.1

--
You received this message because you are subscribed to the Google Groups "BubbleUPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bubbleupnp+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bubbleupnp/caea3904-f6dd-4eb6-8e67-1691710db8a7n%40googlegroups.com.

[Michael Pujos]

Thank you for the detailed answer. My comments below.

On Monday, December 15, 2025 at 2:20:00 PM UTC+1 Gert Brinkmann wrote:

- I am assuming you where playing to your Pixel 8 acting as renderer ?

yes, correct.

via bluetooth in-ears Sennheiser Momentum True Wireless 4. Maybe they or the bluetooth connection can be the culprit, too?

Normally BT should not cause that issue. From the POV of the app, it is not different than playing to the phone speakers or wired headphones.

 

- do you have 'More > Settings > Battery saving mode' enabled ?

Yes, this is enabled

OK. This setting should not cause this issue. And when it is enabled, even if BubbleUPnP was running for hours in the background

not actively doing something (controlling a renderer, serving content....) the battery should not abnormally drain. Which makes your report of battery drain even more

surprising.

 

- did you ever notice if your phone was abnormally hot to the touch when the app is running ?

No, I did not notice this.

OK. if you ever notice this, let me know. It could be rare but if the app was stuck in a loop using 100% CPU, it would drain the battery quickly (and make the device hot).

Not saying this is what happened while you slept and not the most probable, but it is a possibility.

 

Can you do this test (with the phone not plugged to power):

- for good measure and for this test, disable 'More > Settings > Battery saving mode' 

- in More > Settings > Control, set 'Kill on inactivity' to '5 minutes' (default is 15 but that's to make that test faster)

- populate the Playlist tab with a few tracks as you normally would (maybe only starts with 3 or 4 tracks) and play first track

- let it play until the end with screen off (as you would at night when you noticed this issue)

- after playback has stopped, wait for at least 5 minutes and check if BubbleUPnP is still running (look if its notification is still present

in the notification drawer, in which case it is running). Normally it should have killed itself

I have tried this now twice.

First I only played one track and did wait after this for twenty minutes (because I did forget to reduce the kill time from 15 to 5 minutes). BubbleUPnP had exited fine when I checked it.

Then I reduced kill time to 5 minutes and activated the no-disturbe-night-mode in Android that I have activated at night. Playing 4 tracks of 20 minutes and waited 10 minutes before checking the phone. => Everything ok. BubbleUPnP did exit.

Now I wonder what the problem could be. In both problematic cases I had about 30-40% SoC left. But the next morning the phone was powered off with 0% battery charge left. Usually it should have >>20% left. This is annoying because the alarm clock is not working anymore in this case, too.

I have a Pixel 8 Pro and MinimServer and doing some tests to check if I can reproduce it.

A few questions:

- do you have 'More > Settings > Local Renderer > Gapless playback' enabled ?

- what was the nature of tracks being played when you observed this issue: mp3, FLAC ?

If I had to make guess, it might be that 'Kill on inactivity' is not triggering for an unknown reason. But again, with 'Battery saving mode' enabled, it should not drain the battery (although I will make some new tests to verify that).

Thanks again for helping me trying to troubleshoot this issue. And this is the kind of issue that is frustrating to fix due to the difficulty to reproduce it.

[Gert Brinkmann]

Am 15. Dezember 2025 14:54:55 MEZ schrieb Michael Pujos <pujos....@gmail.com>:


>A few questions:
>
>- do you have 'More > Settings > Local Renderer > Gapless playback' enabled
>?

Yes, this is enabled.

>- what was the nature of tracks being played when you observed this issue:
>mp3, FLAC ?

I cannot remember which album I did listen to via minimserver. It certainly was flac, but I am not sure if CD quality or more hires.

Qobuz is set to maximum quality via wifi. And this is the EP I did listen to:
<https://open.qobuz.com/album/pt0gt1sz3w82b>

>If I had to make guess, it might be that 'Kill on inactivity' is not
>triggering for an unknown reason. But again, with 'Battery saving mode'
>enabled, it should not drain the battery (although I will make some new
>tests to verify that).
>
>Thanks again for helping me trying to troubleshoot this issue. And this is
>the kind of issue that is frustrating to fix due to the difficulty to
>reproduce it.

If I can offer some more information, please let me know.

[Michael Pujos]

Thank you for the additional details.

Gapless control is more complicated with more possible issues. 

It only triggers when playing consecutive tracks of the same album (whether that album is actually gapless or not).

I will try to replicate the issue with it.