![]() |
[he is back] UI down when getting to the end of the playlist, while using bluetooth - Printable Version +- Moode Forum (https://moodeaudio.org/forum) +-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3) +--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7) +--- Thread: [he is back] UI down when getting to the end of the playlist, while using bluetooth (/showthread.php?tid=2136) |
[he is back] UI down when getting to the end of the playlist, while using bluetooth - Maitresinh - 01-29-2020 This is the sequel of classified but unsolved case. (http://moodeaudio.org/forum/showthread.php?tid=2099) As i have new leads, i think it can be of interest.And hopefully, eventually resolved. To summarize I use a PI3B+ with a DIGIamp DAC to listen music from my NAS (and old Dlink DNS320). Everything is fine when i'm using the DAC to send the music to speakers. But, when i'm using bluetooth (out, to send music to a bluetooth speaker), the front-end become eventually unavaialble (but no moode via SSH). So, here are the news 1- I've bought and try a 19V power supply. Nothing have changed. 2- I've noticed that there is no problem with bluetooth while i'l listening to radio. So it may be a NAS problem 3- thus, i've updated the NAS with the "last" (2014) Firware, to get a more recent version of Samba. Nothing have changed 4- However, there is here a non official firware. Maybe it's worth trying ? (https://sites.google.com/site/altfirmware/) 5- Last but not least, i've noticed a strange thing : usually the "freeze" happens when i reach the end of an album. So i've start an album, jumped to the last song, and listened the last few second. When it came to the end, the "freeze" happened. Just in that moment. Is that help ? (logs below) --------------------- pi@moode:~ $ egrep -i '(warn|error|fail)' /var/log/syslog Jan 29 00:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 01:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 02:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 03:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 04:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 05:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 06:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 07:12:51 moode rngd[340]: stats: FIPS 140-2 failures: 0 Jan 29 07:29:08 moode bluetoothd[1112]: Endpoint replied with an error: org.freedesktop.DBus.Error.NoReply Jan 29 07:30:36 moode bluealsa[1135]: /usr/bin/bluealsa: Couldn't release transport: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist Jan 29 07:30:36 moode systemd[1]: mpd.service: Failed with result 'timeout'. Jan 29 07:30:37 moode bluealsa[1135]: /usr/bin/bluealsa: Couldn't release transport: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist Jan 29 07:14:13 moode kernel: [ 0.739112] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = bad04000 dma = 0xfad04000 len=9024 Jan 29 07:14:13 moode kernel: [ 0.750874] WARN::hcd_init_fiq:457: FIQ on core 1 Jan 29 07:14:13 moode kernel: [ 0.752445] WARN::hcd_init_fiq:458: FIQ ASM at 8067e4c4 length 36 Jan 29 07:14:13 moode kernel: [ 0.753978] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000 Jan 29 07:14:13 moode kernel: [ 4.593593] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 07:14:13 moode kernel: [ 4.689895] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 07:14:13 moode kernel: [ 4.698322] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 07:14:13 moode kernel: [ 4.717661] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 07:14:13 moode kernel: [ 4.822893] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 07:14:13 moode kernel: [ 7.716397] random: 7 urandom warning(s) missed due to ratelimiting Jan 29 07:14:38 moode bluetoothd[1113]: Failed to set privacy: Rejected (0x0b) Jan 29 07:14:40 moode kernel: [ 34.403187] CIFS VFS: server 192.168.0.11 of type Samba 3.2.8 returned unexpected error on SMB posix open, disabling posix open support. Check if server update available. Jan 29 08:47:45 moode kernel: [ 0.739000] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = bad04000 dma = 0xfad04000 len=9024 Jan 29 08:47:45 moode kernel: [ 0.750775] WARN::hcd_init_fiq:457: FIQ on core 1 Jan 29 08:47:45 moode kernel: [ 0.752349] WARN::hcd_init_fiq:458: FIQ ASM at 8067e4c4 length 36 Jan 29 08:47:45 moode kernel: [ 0.753886] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000 Jan 29 08:47:45 moode kernel: [ 4.692632] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 4.891150] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 4.891154] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 4.918859] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 4.952334] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 4.954149] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 08:47:45 moode kernel: [ 7.908851] random: 7 urandom warning(s) missed due to ratelimiting Jan 29 08:48:09 moode bluetoothd[1110]: Failed to set privacy: Rejected (0x0b) Jan 29 08:48:11 moode kernel: [ 34.191756] CIFS VFS: server 192.168.0.11 of type Samba 3.2.8 returned unexpected error on SMB posix open, disabling posix open support. Check if server update available. Jan 29 09:51:59 moode rngd[339]: stats: FIPS 140-2 failures: 0 Jan 29 10:34:23 moode kernel: [ 0.738880] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = bad04000 dma = 0xfad04000 len=9024 Jan 29 10:34:23 moode kernel: [ 0.750656] WARN::hcd_init_fiq:457: FIQ on core 1 Jan 29 10:34:23 moode kernel: [ 0.752230] WARN::hcd_init_fiq:458: FIQ ASM at 8067e4c4 length 36 Jan 29 10:34:23 moode kernel: [ 0.753766] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000 Jan 29 10:34:23 moode kernel: [ 4.567376] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 4.697560] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 4.710720] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 4.729019] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 4.800190] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 4.815540] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Jan 29 10:34:23 moode kernel: [ 7.537216] random: 7 urandom warning(s) missed due to ratelimiting Jan 29 15:40:48 moode bluetoothd[1163]: Failed to set privacy: Rejected (0x0b) Jan 29 15:40:53 moode kernel: [ 45.117944] CIFS VFS: server 192.168.0.11 of type Samba 3.2.8 returned unexpected error on SMB posix open, disabling posix open support. Check if server update available. Jan 29 16:40:15 moode rngd[328]: stats: FIPS 140-2 failures: 0 RE: [he is back] - TheOldPresbyope - 01-29-2020 1. So, you have Bluez-alsa errors which I've never experienced. A little search-engine work turns up hits which suggest perhaps your Bluetooth speaker is powering off during playback. I can't say more. Maybe the Bluez-alsa maintainer can. As two datapoints, In a first test, I ran a moOde 6.4.1 player for 48 hours straight using a radio station as input and a powered Bluetooth speaker as output. In the current second test, it's been running for hours straight with my NAS as input and the same BT speaker as output. No errors. 2. That final syslog message Code: Jan 29 15:40:53 moode kernel: [ 45.117944] CIFS VFS: server 192.168.0.11 of type Samba 3.2.8 returned unexpected error on SMB posix open, disabling posix open support. Check if server update available. suggests your server is still behind the curve. In my case, my OpenMediaVault NAS is running Samba Version 4.5.16-Debian, compared to moOde running Samba Version 4.9.5-Debian. OTOH, I don't know if the old version is a contributing problem and I can't help further if it is. Sorry, but I don't know what more to contribute to this discussion. Regards, Kent RE: [he is back] - vinnn - 01-30-2020 It sounds to me that your Bluetooth speaker is doing something funky which is causing the Bluetooth adapter module to hang/crash or causing bluez-alsa to hang which in turn causes mpd to hang which stops the web interface from responding because it/nginx can't get status updates from mpd. As you state that a constant audio stream like radio is OK it is most likely that the speaker is not handling the break between streams of individual tracks well and the potential changes in sample rate between streams which is locking up the sending process. Maybe increasing the audio buffer in the mpd config screen might help, to something like 20MB (20480 KB), maybe not. The range isn't great with the Pi's Bluetooth adapter so that might be a contributing factor but ultimately this sounds like the root cause is a hardware problem not software, primarily the thing you're streaming to. Maybe you can get a better idea by inspecting the kernel logs as it happens, e.g. replicate the issue whilst running; Code: sudo journalctl -kef ...or run 'dmesg' after the event. If you get nothing there then the Pi's Bluetooth adapter is probably fine and you'd go on to do the same with the system journal. You could also make bluetoothd output log debug messages by editing the systemd unit file, e.g; Code: sudo nano /lib/systemd/system/bluetoothd.service Code: ExecStart=/usr/sbin/bluetoothd --noplugin=sap Code: ExecStart=/usr/sbin/bluetoothd -d --noplugin=sap Then replicate the issue whilst running.. Code: sudo journalctl -ef .. or give up on this Bluetooth speaker you're using for something better. RE: [he is back] - Maitresinh - 01-30-2020 Thanks for your friendly feedback (whatever i resolve the problem or not). @vinn just to be sure, regarding the "sudo journalctl -kef" thing, i would have to 1/ start running in bluetooth 2/ open a ssh session and enter "sudo journalctl -kef" 3/ Wait for the "event" (freeze) and then ? post the result ? It is the same runing "dmesg" after the event ? However, it's unlikely to be the bluetooth speaker, as i've been testing with another bluetooth device, and it's the same. Plus, the problem seems to happen only when reaching the end of an album WHILE using bluetooth. RE: [he is back] - TheOldPresbyope - 01-30-2020 Hold the phone! I just had what may be the same Bluetooth failure after several hours of continuous playback of tracks from NAS to Bluetooth speaker. This with the same system which had played a radio station for 48 hours straight: RPi3A+ moOde 6.4.1 onboard BT adapter JBL Flip2 (with external 5v power) OpenMediaVault NAS with SMB shares I've just spun up an RPi4B system to replicate the problem. I'm on my way out the door for a doctor's appointment. Will open a new thread with the specifics later this afternoon. Regards, Kent RE: [he is back] - vinnn - 01-31-2020 (01-30-2020, 10:20 AM)Maitresinh Wrote: @vinn just to be sure, regarding the "sudo journalctl -kef" thing, i would have to Yes, I'm not necessarily saying post all your logs here as it's unlikely to be an issue relating to the Moode project, just giving you some assistance on where to find more verbose information. The log you posted suggests at least some hardware related thing is causing this... Code: Jan 29 07:29:08 moode bluetoothd[1112]: Endpoint replied with an error: org.freedesktop.DBus.Error.NoReply The bluetooth endpoint errored (line 1), which made bluealsa hang ("Couldn't release transport" line 2) which made mpd hang/stop responding/fail (line 3) which would make the web interface hang too. How far away is this bluetooth speaker away from the Pi? What kind of case is fitted to the Pi? RE: [he is back] - Maitresinh - 02-01-2020 @TheOldPresbyope Great ! Please to hear i'm not the only one wiht this bug. Any news ? @vinnn i've tried before with the bluetooth speaker at the first floor (and Pi in the ground floor), and now i'm less than 1 meter away. Same thing. Same thing also with a bluetooth headphone: when listening to music on a NAS, at the end of an album (ie : when the last track is other), the Ui is down. It seems that if i do not listen the entire album, it keeps working. RE: [he is back] - CallMeMike - 02-02-2020 (02-01-2020, 05:33 PM)Maitresinh Wrote: @TheOldPresbyope Great ! Please to hear i'm not the only one wiht this bug. Any news ? As per @OldPresbyope statement in his last entry here << I'm on my way out the door for a doctor's appointment. Will open a new thread with the specifics later this afternoon >> he has actually done so: http://moodeaudio.org/forum/showthread.php?tid=2140 RE: [he is back] - vinnn - 02-04-2020 (02-01-2020, 05:33 PM)Maitresinh Wrote: @TheOldPresbyope Great ! Please to hear i'm not the only one wiht this bug. Any news ? I actually replied to this but somehow did it in the completely wrong thread mixed up with another issue! What an idiot ![]() So now I'm in the right thread... Was doing a bit of work in the garden so I took out my Jam Heavy Metal bluetooth speaker and played several albums over bluetooth from my Pi3 running Moode 6.4.1, haven't actually used Moode for this before but it works great. The listening room/den backs onto the garden so the speaker was about 4 meters away from the Pi max, my Pi is in a metal case so that may also effect potential range but had no issues/dropouts today. I made a point not to make a big queue of multiple albums but played an album, let it run out, stuck on another and so on so there's several minutes of idle time between each. Six albums in, no problems. Also tested switching off the Jam Heavy Metal whilst Moode was playing a couple of times, again no problem. I was able to switch the speaker back on and hit play in Moode and the music resumed. System info whilst connected to bluetooth... Code: S Y S T E M P A R A M E T E R S ... I couldn't reproduce your issue. RE: [he is back] - Maitresinh - 02-06-2020 damned. I am. i think i will try to change my nas. That's the only thing i see. |