bluetooth dropouts and streaming issues with mu-so

Posted by: Tom_W on 26 January 2015

Bluetooth streaming to my mu-so is pretty much unusable due to constant stuttering and dropouts. Has anyone else experienced this?

 

Behaviour is the same whether i connect over bluetooth from either of my 2 android phones (both support AptX, running Android 4.4.4 and 4.2.2), or my fairly new Win 7 laptop. I'm only 3m from the mu-so and there are no obstructions.

I have tried streaming locally stored files as well as internet sources. Both are the same.

I thought there may be interference from the other wireless networks in my area, so i've tried changing the wireless channel to 1, 6 and 11, but no difference. My wireless network is 2.4ghz.

 

Additionally there is some weird interaction with the Naim app going on. The music stops completely after a while (the devices are still connected via bluetooth) and I have to press play/pause on the app, which then makes music play for a second before actually pausing. Pressing play/pause again resumes music.

 

You shouldn't even need to use the Naim app to connect via bluetooth, so the fact there is this strange interaction makes me wonder what the hell is going on here.

 

Oh, one more thing. My PC wouldn't even find the mu-so over bluetooth until I had turned off bluetooth on all other devices first.

 

I have none of these issues with my cheapo portable bluetooth speaker.

Any ideas?

Posted on: 26 January 2015 by Bert Schurink

Haven't experienced any of this - didn't yet do Bluetooth. So the only issue I see is the lack of gapless replay. I hope you get your issues sorted soon

Posted on: 10 February 2015 by Tom_W

Just thought I'd update on my issues. Turns out the bluetooth receiver on my new mu-so was faulty.

Customer services told me to test what the reception was like when my phone was placed directly on the top left of the unit. Reception was fine at distances up to about 90 cm, but didn't work beyond that.

Naim replaced the whole unit once they had received and tested it. Rather disappointing and inconvenient but it is now fixed.

Incidentally I asked them to respond to this post for the benefit of other forum members, but they didn't want to.