When i thought it couldn’t get worst, it really did.
Unable to use the Core because it keeps interrupting playback, now i can’t listen to internet radio with the muso.
Unbelievable…
1 Like
This is exactly what is happening to my unit. Are you using an android device? This started about month ago for me.
No I am IOS, however, I think I may have found the cause…a couple of tests to do tomorrow.
1 Like
I did everything you can do. My unit when fully powered up and only connected to power and ethernet plays music for random times then resets exactly like yours. That eliminates my AVM and cables. The only thing left is power and ethernet network. Power is fine because nothing else plugged into the surge suppressor is resetting. My unit never fails when i control it from one of my smart TVs or my Oppo Blu Ray Player. It functions fine as long as it is working via my ethernet network. If i use the Naim App in full power mode it resets.
My-so 2nd Gen not playing radio stations in the uk. Tidal works fine - have completed full reset without success. Everything reloaded but no radio streaming. Any ideas before I fire this thing out the window!
Hi and welcome to the Community –
The issue you have with your Mu-so is almost certainly due to the recent outage of the iRadio service the past few days (you may wish to read around the forum and catch up on that)…
Certainly nothing to do with the Core, which is what this thread is about….
The radio service is gradually being restored, though may be patchy for some, in some regions….I restart (power recycle) may help your Mu-so along….
SC
I also met the same problem. Uniti Core switches off and reboots randomly. I am not sure whether I found the universal decision or not but it helped me. I switched off bluetooth connection permission for Naim App on my iPad. Of course It is also possible to do the same thing for Android App. Simply Turn off the permission to “Scan for nearby devices” for Naim App on Android Device. It seems that Naim App is periodically trying to initiate the connection procedure with Uniti Core via bluetooth like it’s doing during primary setup and this causes reboot.
Same problem here. I will try your suggestion. But have you tried the latest software upgrade? 2.5.6.
Interestingly I am still having that same problem, I thought I had worked out was causing it (linked to meaningful changes to music database whilst playing material) but wasn’t the case. Was hopeful that the latest upgrade would do the trick, but no…No pattern to it, i.e could happen after a couple of songs or a couple of albums…so it appears at least 3 of us have the same (software?) problem.
2.5.6 update didn’t help. There was a really brilliant idea in this thread from Rcsm to close the App while listening the music. This really works, but it’s not very convenient. I’ve thought that the problem is inside the device but it seems that the main problem is in the Naim App. So I hope switching off the bluetooth connection permission in the Naim App could be a solution.
Did you do anything else after the latest update?
Did you do a reset of the Core or reset router/switch?
Asking only becauae my Core still wakes up and stops during playback.
Of course the main way that the Naim app connects to the Core is WiFi, not Bluetooth. The Core doesn’t have WiFi or Bluetooth so the phone talks to your network with WiFi and the network talks to the Core with Ethernet.
Hi,
I find it incredible (BAD) how Naim can’t fix this.
I still have around 700 CDs to rip, and most of the time i have to send the Core to Deep sleep, restart it again so that i can eject the CD and put it on again and be successful with the rip.
Sometimes i can rip two consecutive CDs.
Regarding playback, i am having this pattern.
Whenever i play a CD for the first time, since the instalation of the last firmware update, playback is interrupted after a few minutes.
From then on, whenever i play this CD, playback is not interrupted.
I am finally recovering (improving) from “temporomandibular disorder” that affected my earing; i sold my previous system during the last years because i couldn’t listen to music (i bought a Muso to keep listening at low volumes), and now was determined to buy another system (222+300+250).
Experiencing these issues was an eye opener.
No way i am buying a naim system based on streaming+core.
Better be quiet tha bored with bad products (yes, despite the fantastic sound, they are bad because the software is crap).
Time for another Deep Sleep…
Regards
Rui
This is only my assumption but I think that a bluetooth connection is used during the initial pairing of a mobile device with a new Uniti Core.
It is possible that the mobile device transfers primary local network ethernet configuration data to Uniti Core via bluetooth.
It’s interesting but if you switch off bluetooth on the mobile device you are not able to find and configure a new Uniti Core device.
But I should admit that stwitching off bluetooth on Naim App didn’t solve the problem. Spontaneous reboots became more rare but did not stop entirely.
Just the usual ‘Restart’ after the update was applied, which I believe is advised after any firmware update on the Core. Nothing else.
As I’ve previously said, the update totally fixed the issue for me, not one blip since (fingers crossed!)….One of the rare instances of a software update, of any OS kind, directly nailing an issue.
You’ve confirmed your Core is on 2.5.6 ?
I’m surprised you are still having the issue if so, if indeed it was the very same issue cause….
If it keeps exhibiting the issue, and you have tried a number of remedies to solve, you will perhaps have to start taking up with Naim Support….
There seems to a couple of other threads at present possibly suggesting a bug issue with the Naim App…I don’t have any direct experience, but I do suspect there’s something slight around Bluetooth….as I often get the Bluetooth disconnection warning icon in the App when I put a device into Standby, which is irrelevant and unnecessary really, as I’ve put the device into Standby…!
SC
No really, the Core does not have Bluetooth connectivity at all. So whatever you are seeing is nothing to do with that. Also you never have to pair a Core with a new device. I don’t think you understand how the Core works.
This is related to the Focal Bathys headphones. Unlike Naim units, the app does control the Bathys with Bluetooth and the warning is just the app telling you that it doesn’t have a Bluetooth connection to anything. Whether you have any Focal Bathys set up or not is totally irrelevant. You don’t need to put a Naim device into standby to see this - you can just go to the Rooms screen at any time. When we discussed this annoying and unnecessary warning message during beta testing of the app, we were told that there is a delay in the Apple device telling the app whether Bluetooth is on or not, so you get the warning. It goes away on its own if you leave it alone and it’s about Bluetooth being on in the Apple device, not any Naim or indeed Focal device.
1 Like
I do actually have Bathys…but as you point out, it seems irrelevant if you do or do not…
Yes, I knew the iOS was slightly slow re Bluetooth info, so I guess this makes sense re what is happening in the App – makes sense now that you’ve pointed this out…….though I do think, with a bit of a tweak, the App could just pause and wait until it flashed up the icon and thus give it more relevance when it does do so….
SC
1 Like
Ok the final fix was a firmware update. App developers are denying they did anything that would have caused the firmware to be updated. But the app was updated in Mid-November and that’s when my trouble started. If it wasn’t the App then why did a bunch of Uniti Cores all the sudden require a firmware update? I know what my conclusion is feel free to draw your own. Thank you for all your help, it was here that I found out what was wrong first.
A very dangerous response that may need a Public Inquiry.
I think everyone already knows that this was caused by a Rovi metadata lookup change which meant that many metadata tasks were queued by the Core and occasionally it needed restarting to get them all back in order. This was interpreted by some people as the Core “waking up”, which it wasn’t of course.
It was nothing to do with the app anyway.