That’s the most plausible theory I have heard so far!
Like @Suedkiez I have a very simple network and would also welcome some input from Roon technical/development staff.
My friend is coming over tomorrow with his Android phone which is a different make to mine. We can run side-by-side tests and maybe get tech support to look at logs?
Be interesting to see what happens!
Hey gents, I realize that none of you want to hear that the issue is due to your network, but your logs are revealing that as the cause.
@J.A here’s a trace from your logs showing rapid droputs at a killed stream to your Android SM-T580
08/04 06:55:13 Trace: [SM-T580] [HighQuality, 16/44 FLAC => 24/48] [100% buf] [PLAYING @ 0:01/6:01] The Night - xPropaganda
08/04 06:55:16 Trace: [Default Output] [raatclient] GOT [15] {"samples":240,"status":"Dropout"}
08/04 06:55:17 Trace: [Default Output] [raatclient] GOT [15] {"samples":25060,"status":"Dropout"}
08/04 06:55:17 Trace: [Default Output] [raatclient] GOT [15] {"samples":24860,"status":"Dropout"}
08/04 06:55:18 Trace: [Default Output] [raatclient] GOT [15] {"samples":23040,"status":"Dropout"}
08/04 06:55:18 Trace: [Default Output] [raatclient] GOT [15] {"samples":23040,"status":"Dropout"}
08/04 06:55:19 Trace: [Default Output] [raatclient] GOT [15] {"samples":25260,"status":"Dropout"}
08/04 06:55:19 Trace: [Default Output] [raatclient] GOT [15] {"samples":24660,"status":"Dropout"}
08/04 06:55:19 Warn: [SM-T580] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
08/04 06:55:19 Trace: [SM-T580] [zoneplayer/raat] too many dropouts. stopping stream
@Suedkiez your issue is being caused by network dropouts and slow network response to your Zone named Moto (Moto G8 Power)
08/06 17:40:37 Warn: [Moto] [zoneplayer/raat] long rtt sync Default Output: realtime=16068532034 rtt=176000us offset=-13310467us delta=-58376us drift=-166236us in 9.105s (-18257.739ppm, -65727.861ms/hr)
08/06 17:40:38 Trace: [Default Output] [raatclient] GOT [32] {"samples":1812,"status":"Dropout"}
08/06 17:40:38 Trace: [Default Output] [raatclient] GOT [32] {"samples":23040,"status":"Dropout"}
08/06 17:40:39 Trace: [Default Output] [raatclient] GOT [32] {"samples":26716,"status":"Dropout"}
08/06 17:40:39 Trace: [Default Output] [raatclient] GOT [32] {"samples":23204,"status":"Dropout"}
08/06 17:40:39 Trace: [Default Output] [raatclient] GOT [32] {"samples":23040,"status":"Dropout"}
08/06 17:40:40 Trace: [Default Output] [raatclient] GOT [32] {"samples":23040,"status":"Dropout"}
08/06 17:40:41 Warn: [Moto] [zoneplayer/raat] long rtt sync Default Output: realtime=19339319220 rtt=166000us offset=-13287680us delta=-155585us drift=-143449us in 12.6345s (-11353.796ppm, -40873.664ms/hr)
08/06 17:40:41 Trace: [Default Output] [raatclient] GOT [32] {"samples":24960,"status":"Dropout"}
08/06 17:40:41 Warn: [Moto] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
08/06 17:40:41 Trace: [Moto] [zoneplayer/raat] too many dropouts. stopping stream
08/06 17:40:41 Info: [audio/env] [zoneplayer] All streams were disposed
08/06 17:40:41 Trace: [Moto] [zoneplayer/raat] Endpoint Default Output State Changed: Playing => Prepared
08/06 17:40:41 Info: [audio/env] [zoneplayer -> stream] All streams were disposed
08/06 17:40:41 Trace: [Default Output] [raatclient] SENT [41]{"request":"end_stream"}
08/06 17:40:41 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
08/06 17:40:41 Debug: [raat/tcpaudiosource] disconnecting
08/06 17:40:41 Warn: [raat/tcpaudiosource] send failed: Object reference not set to an instance of an object.
08/06 17:40:41 Warn: [raat/tcpaudiosource] disconnecting + retrying
08/06 17:40:41 Warn: [zone Moto] Track Stopped Due to Slow Media
Ian, unfortunately, your tests don’t rule out network issues. They may prove that non-Android devices are less affected but don’t indicate anything about your network. I attempted to pull another logs set from your devices. Our servers can’t connect to your network at all. Either your Core is powered off or network issues are still to blame.
Thanks much. At least I know, and maybe the wifi is broken on both my phone and tabled, but anyway in this case unfortunately Roon is unusable for me over a 5 meters wifi distance with 2 different mobiles and I have to use the Qobuz app when using headphones, which has no such problems 
@jamie Thanks for your long-awaited reply.
… and your network logs also do not prove the cause of the connection dropping which could be that the remote client is unable to handle the datastream. Other contributors to this thread are saying the same thing - see below:
Yes, my Core was powered off when you attempted to pull the logs - nothing to do with the network which is working fine as usual.
Yesterday, I did manage to do the test I mentioned a few days ago. A friend came over with her Samsung A52 phone running Android 12. We installed Roon Remote on her phone and connected to my Core, streamed a track and it worked perfectly. I then tried to stream the same track on my Moto G4 phone seconds later and it failed, as it always does after a few seconds.
@jamie I will leave my Core powered on. Please check the logs for 08/08/22 at around 15:30 UTC and you will see these two tests - proof beyond reasonable doubt that there is nothing wrong with my network.
I eagerly await your response.
Hi @Ian_Pickering. For the record, we informed you 30 days ago that this is a local network issue.
The trace below, from the logs you uploaded, indicates that it remains a local network issue. No networking changes were made in Build 970.
08/08 17:14:19 Trace: [Default Output] [raatclient] GOT [13] {"samples":126,"status":"Dropout"}
08/08 17:14:20 Trace: [Default Output] [raatclient] GOT [13] {"samples":24354,"status":"Dropout"}
08/08 17:14:20 Trace: [Default Output] [raatclient] GOT [13] {"samples":23040,"status":"Dropout"}
08/08 17:14:21 Trace: [Default Output] [raatclient] GOT [13] {"samples":25642,"status":"Dropout"}
08/08 17:14:21 Trace: [Default Output] [raatclient] GOT [13] {"samples":24278,"status":"Dropout"}
08/08 17:14:22 Trace: [Default Output] [raatclient] GOT [13] {"samples":23040,"status":"Dropout"}
08/08 17:14:22 Trace: [Default Output] [raatclient] GOT [13] {"samples":23040,"status":"Dropout"}
08/08 17:14:23 Trace: [moto g(6)] [HighQuality 21.5x, 24/96 QOBUZ FLAC => 24/48] [100% buf] [PLAYING @ 0:05/4:50] He's Funny That Way - Andrea Motis / Neil Moret / Richard A. Whiting
08/08 17:14:23 Debug: FTMSI-B qo/B3140848 download status: FirstBlockRetrieved accessTimeout:False openFiles:1 prev:(FirstBlockRetrieved,True,1)
08/08 17:14:23 Trace: [Default Output] [raatclient] GOT [13] {"samples":25742,"status":"Dropout"}
08/08 17:14:23 Warn: [moto g(6)] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
08/08 17:14:23 Trace: [moto g(6)] [zoneplayer/raat] too many dropouts. stopping stream
08/08 17:14:23 Warn: [zone moto g(6)] Track Stopped Due to Slow Media
You can try refreshing your RAAT Server to see if that helps. You can do that by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Thanks for getting back to me so quickly
For the record, this is incorrect. If you look back through this thread, my initial post was 45 days ago. You did reply 29 days ago asking if there was still a problem, but didn’t reply again until another 11 days later (a total of 27 days after my initial post) when you informed me about the log files indicating a network problem.
If I may say so, you have been very selective with this data. Yesterday, I mentioned that I had streamed successfully over my network only seconds before this instance using my friend’s Samsung phone. Could you please post that part of the log file from just before this time showing that there were no dropouts.
Thanks for this advice, I’ll give that a try. But again, if you read back through this thread, you will see that I already did a test by installing a completely fresh Roon Core on my desktop PC and I got exactly the same problem streaming from that Core, so I’m not sure how this would yield any different outcome. FYI, here’s that post, from 14 days ago:
Well, I think that points to your old (yes) devices. Aren’t both of them running Android 10? If so, can you update them?
One of them is Android 9 (Motorola phone), the other is 11 (Samsung Tablet). Unfortunately, when I go to the Updates screen they both say that they are running the latest version. So you’re probably right - going to have to get a new phone.
Mine are both 10, from 2020. Doesn’t really seem too old, but luckily I dropped my phone 3 times in the past 10 days, there must be something subconscious going on
Customer is experiencing networking and device issues due to using an underpowered Android phone on Android 9 as an endpoint. This thread has descended into a refusal to accept the diagnosis and has been closed.