· I just purchased a Hiby R6 iii DAP. It will Not connect to my Nucleus most of the time. If I reboot the server it may connect once then if I close the app it don’t reconnect. This DAP is a Android’s based device and I use the app that I downloaded from the Google site. My iPhone and all the rest of my stuff connects with no issues.
Tell us about your home network
· Synology WRX 560 router. Netgear switches. I’ve tried typing in the IP address of the Hiby. It worked once and then it reverted back to not finding the server
Thanks for the report. Since your iPhone and the rest of your devices connect without issues, the server and network side look healthy - so let’s focus on the DAP itself.
First, an important note: the HiBy R6 III is not a Roon Ready or Roon Tested device, so we can’t guarantee stable operation with it. DAPs like this typically run modified Android builds, which can behave quite differently from standard phones and tablets.
Could you clarify how exactly you’re using it with Roon - are you running the Roon app from Google Play directly on the DAP and using the R6 III itself as the playback zone? You also mentioned typing in an IP address - could you tell us where exactly you entered it, and whose IP it was (the Nucleus or the HiBy)?
In the meantime, a couple of things worth checking on the DAP, since Android power management is the usual suspect in this pattern: in the Android settings, exclude the Roon app from battery optimization, and make sure WiFi stays active during sleep - aggressive power saving on DAPs often drops the connection to the server the moment the screen goes off. Also, confirm the DAP is connected to the same WiFi network as the Nucleus (main SSID, not a guest one).
If the problem persists after that, it may also be worth raising this with HiBy support - as an uncertified device, its Android build is unfortunately outside what we can debug from our side.
I’ll try to attach two screenshots. Roon ARC works fine on the HIBY. If I reboot the server the regular Roon app works fine until I close it out. It will not reconnect most of the time without another reboot of the Nucleus.
Thank you - that’s a genuinely useful data point. ARC working fine on the HiBy tells us the DAP’s WiFi and network path are healthy: ARC connects directly to the server’s address, while the regular Roon app has to discover the server via multicast broadcasts. It’s that discovery step that’s failing.
To narrow down where it breaks, the next time the HiBy won’t reconnect, please try these in order - and note which one (if any) fixes it, without rebooting the Nucleus:
Check your iPhone at that same moment - does it still see and connect to the server? (If yes, the server is announcing itself fine.)
On the HiBy, force-stop the Roon app (Android Settings > Apps > Roon > Force stop) and reopen it.
Toggle WiFi off and on on the HiBy, then open Roon again.
Knowing which step restores the connection will tell us whether the stale state lives in the app, in the DAP’s network stack, or elsewhere. Please also grab the exact date and local time of a failed reconnect attempt - we’ll match it against the server diagnostics.
It looks like the screenshots didn’t come through in your last post, by the way - could you try attaching them again?
One more check worth doing once: in the HiBy’s Android settings, confirm Roon is excluded from battery optimization - DAP Android builds are often aggressive about killing background network connections, which can leave the app in exactly this half-connected state.
Ok, here is what I found. By turning off WiFi in the Hiby and then turning it back on enables the Roon app to start every time after closing it out normally. Your other two selections (battery optimization and force quit) seem to have no affect on the issue, however if I don’t close out Roon and just stop playing something and leave it running, I guess, in the background while I use another app I can use it when I bring it up.
I emailed Hiby and informed them of the issue and they said they have no future plans to make my DAP Roon ready but will inform there staff for the future.
The Roon app seems to be working well now. I’ve run into the Android issue with the downsampling to 48khz now. I was reading about this on the internet with the Android operating system. I guess I’ll just hope that Hiby gets on board with Roon concerning my model.
On the 48kHz cap: this is a known limitation of Roon on Android rather than a setting you’re missing. When playing through “System Output,” Roon locks output to 48kHz regardless of source rate, a compatibility decision on Roon’s side that’s been an open issue for years. HiBy’s own app avoids it because HiBy built a proprietary Android audio path that Roon doesn’t use.
Two things worth trying:
One, if you’re on Roon ARC, there’s a beta “Enable USB driver” toggle at the bottom of Settings. It’s built for external USB DACs rather than internal ones, so it likely won’t help with the R6 III’s internal DAC, but it costs nothing to test.
Two, if full native-rate playback matters more than using Roon directly on the DAP, HiBy’s own app or a USB DAC connected to the R6 III (bypassing System Output) will get you there.
There’s an open feature request for proper DAP support here if you’d like to add your vote:
. No timeline from Roon on it, but it’s on their radar.
Sorry that’s not a cleaner answer, at least the connection issue itself is sorted.
