Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Bluetooth Locks up UI
#1
Hello,

I've experienced a problem several times where connecting a phone through bluetooth, disconnecting it and then connecting another phone through bluetooth leaves the UI frozen (other than the update spinner). You can continue to play music through bluetooth, but the UI never recovers. I've had to power off to get out of this state.

It's happened with other members of the family, so I can't say what the exact steps are to get this to happen at the moment.

Anyone else experienced this?

Best regards,
Nick
Reply
#2
Sorry to be so tedious but some data would be helpful. Makes/models of the phone(s) and the usual moOde log.

ETA - and which Bluetooth mode are you talking about? Are you using the "Local audio" mode (the phones stream to the moOde player) or the "Bluetooth speaker" mode (the moOde player streams to the phones)? I was assuming the later but you know what they say about "assume".

Regards,
Kent
Reply
#3
(06-17-2025, 02:35 PM)TheOldPresbyope Wrote: Sorry to be so tedious but some data would be helpful. Makes/models of the phone(s) and the usual moOde log.

ETA - and which Bluetooth mode are you talking about? Are you using the "Local audio" mode (the phones stream to the moOde player) or the "Bluetooth speaker" mode (the moOde player streams to the phones)? I was assuming the later but you know what they say about "assume".

Regards,
Kent

Oops, should know better!

RPi 4b
Moode v9.3.6
Bluetooth: Local Audio
Phone: Android Samsung S10

I'll get a log next time it happens.

Is there a "safe" way to disconnect the phone from moode? I think that we mostly just turn off bluetooth on the phone.

Best regards,
Nick
Reply
#4
(06-18-2025, 09:11 AM)TamedShrew Wrote:
(06-17-2025, 02:35 PM)TheOldPresbyope Wrote: Sorry to be so tedious but some data would be helpful. Makes/models of the phone(s) and the usual moOde log.

ETA - and which Bluetooth mode are you talking about? Are you using the "Local audio" mode (the phones stream to the moOde player) or the "Bluetooth speaker" mode (the moOde player streams to the phones)? I was assuming the later but you know what they say about "assume".

Regards,
Kent

Oops, should know better!

RPi 4b
Moode v9.3.6
Bluetooth: Local Audio
Phone: Android Samsung S10

I'll get a log next time it happens.

Is there a "safe" way to disconnect the phone from moode? I think that we mostly just turn off bluetooth on the phone.

Best regards,
Nick

I'll be out most of the day so can't try to replicate your problem for a while. I don't have any Samsung gear so can't comment on their Bluetooth implementation (they're known for customizing other parts of Android for their own purposes).

I have a Pixel 3A Android phone and an iPad mini in front of me at the moment. I connected the phone followed by the iPad to the moOde 9.3.6 player via Bluetooth (so both are connected). I initiated the pairing and connection processes from the phone/iPad. The "Bluetooth Active" showed up as soon as the first device connected.

The moOde player Bluetooth settings are pretty much stock: Enabled, Auto-disconnect disabled, but with resume MPD enabled.

I can start a track on my Pixel phone, Spotify say, and it plays thru moOde. I can stop the track (note: not disconnect Bluetooth), and start a track on my iPad, The Jazz Groove say, and after a brief delay it begins playing thru moOde. I can switch back and forth this way..

But: I disconnected just the phone while the iPad was playing a track and magically the output from moOde ceased and the moOde webUI popped up again. It seems fully functional. The iPhone thinks it's still connected. Curious that. If I reconnect the phone, the moOde player resumes the iPhone's output. Note sure what to make of this.

Anyway, I haven't yet gotten to your frozen screen problem. Later.

Regards,
Kent
Reply
#5
@TheOldPresbyope

Thanks for investigating. I've changed my settings to enable Resume MPD. I've got a feeling it's when a device is freshly paired. I'll continue trying to get it to happen.
Reply
#6
(06-18-2025, 02:35 PM)TamedShrew Wrote: @TheOldPresbyope

Thanks for investigating. I've changed my settings to enable Resume MPD. I've got a feeling it's when a device is freshly paired. I'll continue trying to get it to happen.

Before I do any more snooping, let's be sure I'm looking in the right place.

In your first post, you said

Quote:I've experienced a problem several times where connecting a phone through bluetooth, disconnecting it and then connecting another phone through bluetooth leaves the UI frozen (other than the update spinner). 
1. I'm taking this to mean you have several phones---let's call them A and B---and you connect phone A to your moOde player using phone A's Bluetooth settings. [On my systems, moOde player's webUI now displays the "Bluetooth Active" overlay (or modal or whatever it's called) rather than the normal playback screen. Only the "Bluetooth Control" and "Audio Info" buttons are active.] You can start and stop tracks in a music-playing app on phone A and the music is heard thru your moOde player.
2. Now you disconnect phone A from your moOde player, either by explicitly disconnecting in phone A's Bluetooth settings menu or by shutting off phone A's Bluetooth subsystem all together. [At this point on my systems, the moOde player's webUI reverts to the normal playback screen and is fully functional.]
3. Next you connect phone B the same way you connected phone A. Here's where I get befuddled. You said this leaves the "UI frozen (other than the update spinner)". On my systems the webUI again displays the "Bluetooth Active" overlay. There's no update spinner, only the expected two buttons. What are you seeing?
 
I'm also befuddled by your second observation
Quote:You can continue to play music through bluetooth, but the UI never recovers.

Which phone is now playing music through Bluetooth to your moOde player, A or B? And what do you mean by "the UI never recovers". Does this mean it never reverts to the normal webUI playback screen or it does revert but the webUI is not unresponsive?  Or something else?

Sorry for being so picky but recently I've several times been guilty of "jumping on my horse and riding off in all directions" because I misunderstand a user's question. I hope I'm zeroing in on the real problem!?!

Regards,
Kent
Reply
#7
@TheOldPresbyope

Hi Kent,

Sorry for the delay in getting back to you, things have been busy of late.

Sorry if I'm not being crystal clear on this, but I'm trying to piece this together from what other family members have said happens in the lead up to this. What I do know is:

1. The Bluetooth Control page is unresponsive (with the spinner going, but no UI elements working.)
2. Phone B cannot connect to bluetooth.
3. Phone A can reconnect to bluetooth and play music.
4. I think it was the first time phone B was used with moode and it was at the point of pairing (scanning) that things locked up.

I've not been able to reproduce this, try as I might.

Thanks,
Nick
Reply


Forum Jump: