Android Remote Connection problems to Roon Rock [Ticket In]

Roon Core Machine

Roon Rock build 1148, 1167 and 1169 running on an Intel NUC8I5BEK

Networking Gear & Setup Details

Roon Rock is connected with LAN cable. Android remote are working on WiFI (Orbit)

Connected Audio Devices

NA

Number of Tracks in Library

22000 tracks

Description of Issue

Since build 1148 I have all kind of connection problem from android remotes to Roon Rock. Running latest OS en Roon version with UEFI. I have this message on one Android device at this moment, while it is working on another. But this is completely random. If I try it a few times it will connect, but it won’t randomly when I try to start the app on the same device. Connect with “help” and IP address doesn’t work either. So completely lost with no android remotes working!

Using Roon Remote from Wiindows 11 is working fine at the same moment.

Just updated ROCK and all apps to 1167/69 and problem is still present unfortunately.
By the way I also had the issue with Roon Server Software not running, but solved this with removing the database on the NUC and restored everything from last night backup. I just noticed the workaround with removing the bits file, but solved it myself already. Restoring from backup also solved the issue for me.

This is now going on all android remotes. Only Windows remote is still working as it should. Why am I getting a red dot and can’t I connect from Android Remote app?

RoonARC is working as it should.

In logfile RoonServer_log.txt on NUC I can find below error message of the Android Remotes.

11/30 23:08:43 Trace: [raat] RAATServer discovered: RaatServer Pixel 7 @ 192.168.0.21:9200
11/30 23:08:43 Info: [raatserver] GOT SERVER 4f07a31c-7d3d-3694-b2e0-744170de1583::4f07a31c7d3d3694b2e0744170de1583 @ 192.168.0.21:9200 Pixel 7 PROTOVER=1 RAATVER=1.1.39 
11/30 23:08:43 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connecting (attempt 1)
11/30 23:08:43 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connected
11/30 23:08:43 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
11/30 23:08:43 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "default", "is_system_output": true, "type": "android", "name": "Default Output", "auto_name": "Pixel 7", "auto_enable": true}]}
11/30 23:08:43 Trace: [devicedb] [autodetect] No Match for DeviceAutodetectData[Type=Local Model=Default Output]
11/30 23:08:43 Info: [raatserver] GOT DEVICE 4f07a31c7d3d3694b2e0744170de1583::default Type=android Name=Default Output 
11/30 23:08:45 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48904=>192.168.0.6:9332] Connected
11/30 23:08:45 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48904=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:46 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48906=>192.168.0.6:9332] Connected
11/30 23:08:46 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48906=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:47 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48908=>192.168.0.6:9332] Connected
11/30 23:08:47 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48908=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()
11/30 23:08:49 Trace: [remoting/brokerserver] [initconn 192.168.0.21:48910=>192.168.0.6:9332] Connected
11/30 23:08:49 Warn: [remoting/brokerserver] [initconn 192.168.0.21:48910=>192.168.0.6:9332] failed: System.Exception: got unexpected broker id in REQ_HANDSHAKE: f17c95ab-a8bc-4abe-96f9-fbd2fd133441
   at Sooloos.Broker.Distributed.InitConnectionV2.Go()

I can see the Pixel 7 in the device overview but in a strange way and it is not connecting.

After a night sleep everything is back to normal at this moment. All remote clients, including Android, are working. Didn’t do anything. Is it possible Roon is doing some housekeeping on devices during the night / if idle?

So happy at this moment. Hope clients stay connected. Keep you posted.

1 Like

And after a few hours of usage issue is back on one of the Android devices.
Just made some calls and went back to the app on my phone. No connection.

Below log file for that exact moment. No clue why connection from the app isn’t made.
RoonServer finds the phone, but connection isn’t made on the app.

12/01 11:59:23 Trace: [raat] RAATServer discovered: RaatServer Pixel 7 @ 192.168.0.21:9200
12/01 11:59:23 Info: [raatserver] GOT SERVER 4f07a31c-7d3d-3694-b2e0-744170de1583::4f07a31c7d3d3694b2e0744170de1583 @ 192.168.0.21:9200 Pixel 7 PROTOVER=1 RAATVER=1.1.39 
12/01 11:59:23 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connecting (attempt 1)
12/01 11:59:23 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.21:9200] connected
12/01 11:59:23 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
12/01 11:59:23 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"auto_name": "Pixel 7", "device_id": "default", "type": "android", "name": "Default Output", "config": {"external_config": {"is_private": true, "product_override": null}, "volume": {"device": "default", "type": "android"}, "output": {"device": "default", "type": "android", "name": "Default Output"}, "unique_id": "68986c22-b3bb-b0db-219c-e6d9fefb7371"}, "is_system_output": true, "auto_enable": true}]}
12/01 11:59:23 Info: [raatserver] GOT DEVICE 4f07a31c7d3d3694b2e0744170de1583::default Type=android Name=Default Output 
12/01 11:59:23 Trace: [rnet/RnetJsonClient] SENT {"request":"enable_device","device_id":"default","subscription_id":"17"}
12/01 11:59:23 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "DeviceChanged", "device": {"auto_name": "Pixel 7", "device_id": "default", "type": "android", "discovery_data": {"version": "N/A", "tcp_port": 33731, "unique_id": "68986c22-b3bb-b0db-219c-e6d9fefb7371", "model": "N/A", "protocol_version": "3", "raat_version": "1.1.39", "vendor": "N/A"}, "name": "Default Output", "config": {"external_config": {"is_private": true, "product_override": null}, "volume": {"device": "default", "type": "android"}, "output": {"device": "default", "type": "android", "name": "Default Output"}, "unique_id": "68986c22-b3bb-b0db-219c-e6d9fefb7371"}, "is_system_output": true, "auto_enable": true}}
12/01 11:59:23 Info: [raatserver] [Default Output] connecting (attempt 1)
12/01 11:59:23 Trace: [Default Output] [raatclient] Initializing RAAT session
12/01 11:59:23 Trace: [Default Output] [raatclient] Loading script raat.dat:base.lua as module base [1088 chars]
12/01 11:59:23 Trace: [Default Output] [raatclient] Loading script raat.dat:dkjson.lua as module dkjson [22416 chars]
12/01 11:59:23 Trace: [Default Output] [raatclient] Loading script raat.dat:protocol.lua as module protocol [2045 chars]
12/01 11:59:23 Trace: [Default Output] [raatclient] Loading script raat.dat:roon_tcp.lua [43548 chars]
12/01 11:59:23 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success"}
12/01 11:59:23 Trace: [Default Output] [raatclient] RAAT Session initialized in 580ms
12/01 11:59:23 Trace: [Default Output] [raatclient] SENT [2]{"request":"info"}
12/01 11:59:23 Trace: [Default Output] [raatclient] SENT [3]{"request":"set_client_type","client_type":"Roon"}
12/01 11:59:23 Trace: [Default Output] [raatclient] GOT [2] {"source_selection":{"is_supported":false,"info":[]},"output":{"info":{"refresh_supported_formats_before_playback":true},"supported_formats":"48000/16/1|2,48000/24/1|2"},"info":{"unique_id":"68986c22-b3bb-b0db-219c-e6d9fefb7371","vendor":"N/A","model":"N/A","raat_version":"1.1.39","version":"N/A","protocol_version":"3"},"platform":{"uname":{"release":"5.10.107-android13-4-00004-g6522bf85d262-ab8935228","nodename":"localhost","sysname":"Linux","version":"#1 SMP PREEMPT Thu Aug 11 01:17:17 UTC 2022","machine":"aarch64"},"os":"android"},"flags":{"has_write_chmap":true},"transport":{"is_supported":true,"info":{"config":{}},"is_update_status_supported":true,"is_update_artwork_supported":true},"status":"Success","volume":{"is_supported":true,"info":{}}}
12/01 11:59:23 Trace: [raatserver] [Default Output] connected
12/01 11:59:23 Info: [transport] creating endpoint for raat device 68986c22-b3bb-b0db-219c-e6d9fefb7371
12/01 11:59:23 Trace: [Default Output] [raatclient] SENT [4]{"request":"subscribe_transport"}
12/01 11:59:23 Trace: [Default Output] [raatclient] SENT [5]{"request":"subscribe_controls","controller_id":"442e312a-59a4-4667-ae51-26ece70809d2"}
12/01 11:59:23 Trace: [dspengine] created new dsp config {"version":3,"items":[{"type":"bs2b","enabled":false},{"type":"parametric_equalizer","enabled":false},{"type":"audeze_presets","enabled":false}]}
12/01 11:59:23 Trace: [transport/audeze] picking preset lowlatency 
12/01 11:59:23 Trace: [transport/audeze] picked null preset!
12/01 11:59:23 Trace: [zone Pixel 7 Olaf] Loading from /roon/data/RoonServer/Database/Core/b0669cfd552b4514a84287d62cb61978/transport/zone_1601226c9868bbb3dbb0219ce6d9fefb7371.db
12/01 11:59:23 Trace: [Default Output] [raatclient] GOT [3] {"status":"Success"}
12/01 11:59:23 Trace: [zone Pixel 7 Olaf] Suspend
12/01 11:59:23 Info: [zone Pixel 7 Olaf] Canceling Pending Sleep
12/01 11:59:23 Trace: [Pixel 7 Olaf] [zoneplayer/raat] Endpoint Default Output Initial State: Idle
12/01 11:59:23 Info: [transport] created zone Pixel 7 Olaf
12/01 11:59:23 Info: [transport]     with endpoint Default Output (23:1:68986c22-b3bb-b0db-219c-e6d9fefb7371) [IsAvailable=True]
12/01 11:59:23 Trace: [Pixel 7 Olaf] [HighQuality, 24/44 QOBUZ FLAC => 24/48] [100% buf] [STOPPED @ 0:00] 
12/01 11:59:23 Trace: [Default Output] [raatclient] GOT [5] {"action":"Changed","status":"Success","controls":{"volume":{"min":0.0,"value":10,"max":25.0,"info":{},"step":1.0,"type":"number","mute":false}}}
12/01 11:59:23 Trace: [zone Pixel 7 Olaf] Loaded Queue=75 Tracks Swim=Inactive AutoSwim=True Loop=Disabled Shuffle=False
12/01 11:59:23 Trace: [Pixel 7 Olaf] [HighQuality, 24/44 QOBUZ FLAC => 24/48] [100% buf] [PAUSED @ 0:52/4:56] Happy Birthday - Lenny Kravitz

Issues again… and again… and again since 2.0 launch. It has been working for the past years without issues, didn’t change a thing on my network. Also no response from support. Come on Roon you should do better for the premium price you are asking!

12/02 18:23:53 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] lost client connection. Retrying
12/02 18:23:53 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 1)
12/02 18:23:53 Info: [remoting/serverconnectionv2] Client disconnected: 192.168.0.30:39092
12/02 18:23:53 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
12/02 18:23:53 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 500ms
12/02 18:23:53 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 2)
12/02 18:23:54 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
12/02 18:23:55 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 3)
12/02 18:23:55 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
12/02 18:23:55 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 1125ms
12/02 18:23:55 Info: [stats] 27746mb Virtual, 2296mb Physical, 1373mb Managed, 359 Handles, 107 Threads
12/02 18:23:56 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 4)
12/02 18:23:56 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
2/02 18:23:57 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 5)
12/02 18:23:58 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
12/02 18:23:58 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Giving up
12/02 18:23:58 Trace: [raat] [sood] Refreshing device list

And suddenly a connection is there.
12/02 18:24:46 Trace: [remoting/brokerserver] [initconn 192.168.0.30:39228=>192.168.0.6:9332] Connected
12/02 18:24:47 Trace: [remoting/brokerserver] [initconn 192.168.0.30:39228=>192.168.0.6:9332] Initialized Fresh Session
12/02 18:24:47 Trace: [remoting/brokerserver] killing old client from 1c84acff-3f83-44d5-b1c1-4a78cd26ca84 because we have a new one
12/02 18:24:47 Info: [remoting/serverconnectionv2] Client connected: 192.168.0.30:39228
12/02 18:24:47 Trace: [raat] [sood] Refreshing device list

And again

12/04 08:49:57 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 500ms
12/04 08:49:58 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 2)
12/04 08:50:08 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 750ms
12/04 08:50:08 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 3)
12/04 08:50:11 Info: [stats] 27964mb Virtual, 1988mb Physical, 770mb Managed, 366 Handles, 91 Threads
12/04 08:50:18 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 1125ms
12/04 08:50:19 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 4)
12/04 08:50:26 Info: [stats] 27924mb Virtual, 1991mb Physical, 775mb Managed, 343 Handles, 90 Threads
12/04 08:50:29 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Retrying in 1687ms
12/04 08:50:31 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 5)

But for another device it is working right away. What is the difference?

12/04 08:50:36 Trace: [raat] RAATServer discovered: RaatServer Pixel 4a (5G) @ 192.168.0.23:9200
12/04 08:50:36 Info: [raatserver] GOT SERVER 0692aa36-ec61-bbf8-05eb-25cab00f05c8::0692aa36ec61bbf805eb25cab00f05c8 @ 192.168.0.23:9200 Pixel 4a (5G) PROTOVER=1 RAATVER=1.1.39 
12/04 08:50:36 Trace: [raatserver] [RaatServer Pixel 4a (5G) @ 192.168.0.23:9200] connecting (attempt 1)
12/04 08:50:36 Trace: [raatserver] [RaatServer Pixel 4a (5G) @ 192.168.0.23:9200] connected

But for my phone it isn’t

12/04 08:50:41 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] client connection failed. Giving up
12/04 08:50:41 Trace: [raat] [sood] Refreshing device list

And the log says the remote is connected, but it actually isn’t at that moment.
What is going on?

12/04 09:16:40 Trace: [raat] RAATServer discovered: RaatServer Pixel 7 @ 192.168.0.30:9200
12/04 09:16:40 Info: [raatserver] GOT SERVER 4f07a31c-7d3d-3694-b2e0-744170de1583::4f07a31c7d3d3694b2e0744170de1583 @ 192.168.0.30:9200 Pixel 7 PROTOVER=1 RAATVER=1.1.39 
12/04 09:16:40 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 1)
12/04 09:16:40 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connected

Still says the remote is connected… but it isn’t, same screen as previous message.

12/04 09:29:37 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connecting (attempt 1)
12/04 09:29:37 Trace: [raatserver] [RaatServer Pixel 7 @ 192.168.0.30:9200] connected
12/04 09:29:37 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
12/04 09:29:37 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"is_system_output": true, "device_id": "default", "type": "android", "name": "Default Output", "auto_enable": true, "auto_name": "Pixel 7"}]}
12/04 09:29:37 Info: [raatserver] GOT DEVICE 4f07a31c7d3d3694b2e0744170de1583::default Type=android Name=Default Output

No one from support to help with this?

1 Like

I’m experiencing a similar issue.

I find my android remote frequently needs to be reconnected.

I play an album and my phone eventually sleeps. I wake the phone at the end of the playlist and am asked to select my Roon core. It doesn’t list any to connect to until I :
Uninstall and reinstall the app.
Or
Reboot

Hopefully someone can get you some help.

Hi @Olaf_Jungen ,

Thanks for the report here! There is a similar ticket in our tracking system already, so I will link your report to the ticket. This issue can happen when you restore from backup, and the manual solution for it is to reboot the Core and/or Roon Remote. I can’t comment on a timeline for when the ticket will be resolved, but we are working on this. Thanks!

Any updates on this issue? I upgraded to a NUC ROCK today and had many struggles after initial easy success. Restoring from backup was a disaster. Now I have everything working across Windows 11, iMac and iPad, but alas Android on Pixel 5a (two instances) does not work. Rebooting the NUC Core, Android device, or clearing app data/cache or reinstalling app does not solve this problem for me. Thank you.

Update: Today, both Android devices connected immediately to the ROCK core that I configured yesterday.

1 Like

Yes it’s time this annoying bug is solved soon indeed!
I am getting complaints from the family we need to go back to the old school CD’s.

Come on Roon it’s time to release software with less bugs!

1 Like

Hi @David_Bartle & @Olaf_Jungen ,

The ticket is in the queue and I’ve sent the team a reminder on this one, but I cannot share a timeline of when it will be addressed. We are aware of the issue when restoring from a backup, and we are working on it, thanks in advance for your patience!

Hi,
With latest release (1193) I haven’t had connection issues to Rock from Android client anymore.
Has this issue been solved with this release?

Regards, Olaf.