Hi Graham,
You couldn’t really pre-cache in that way … we are obviously aware of this thread and that the “Lost Connection” message is causing issues with some people (oddly I don’t get that problem even if I let my devices sleep, by the time my phones or tablets have woken up they’ve reconnected) so we’ll definitely look into what can be done.
Phil
Hi Pete, I’m not sure which post that was directed at but I use an iPad (not computer/USB) and I have a Melco N1Z with Minimserver 2 installed.
Cheers,
Mike.
I too use a Melco with my Vivaldi and there is no recurring problem with the connection ( discovery).
I know from the past that some have difficulty in maintaining connections given the settings in the software of their router or network switch. This may have bearing on the matter but it needs the input of one of our network experts like @Anupc.
I have the same issue with my Ipad and dcs rossini player, 80% of the time when picking up the Ipad there is the message of lost connection, it takes 2 to 5 seconds to re-connect, tried a new Ipad, exactly the same. Although annoying I have learned to live with it.
It is strange that on the same Ipads there is no problem with the Aurender conductor app, which is alway immediatly available
This has been one of my biggest frustrations of moving to dCS so if someone can find a solution it would certainly enhance my appreciation of the brand. I have to look at that swirling icon about 80% of the times I pick up my iPad and look at Mosaic. Having little experience of such software I assumed it was inherent in all streaming type packages and was a significant factor when I upgraded from Bartok to Rossini, I went for the Rossini Player so I could avoid using Mosaic or any network if I choose to; just and old style CD and remote control - excellent.
It’s also interesting that the dealer had no idea how to deal with it and as usual blamed my internet service despite the fact that I also run TV, iPhones, iMac, iPads, printer etc. etc. on the same network without any problems. But in my experience, whenever anything which uses a network has a problem the blame is always laid on the network because basically the electronics/software is beyond the capability of customer facing businesses.
So it’s intriguing that this thread has appeared recently. I’m not the only one.
From previously looking at the Packet flows, the issue is not really caused by an iDevice/iOS or Android device per se, it’s due the nature of Mosaic’s architecture; in how dCS Mosaic Control on your iDevice/Android works with dCS Mosaic Processor on the Streaming board in the dCS hardware.
It is the way it is by design. Normally, such query/response won’t take more than a few milliseconds, making it “invisible” to the User experience, but the amount of state information update required in some cases seems to drag it out into seconds (not to mention some less than ideal home network setups causing it to go beyond just 1 or 2 seconds).
Something like the Aurender Conductor I’m sure has a very different (and possibly older and processor intensive) architecture. Mosaic, as a whole, actually has quite a modern REST-based architecture.
ps:
By the way, just as a reminder to folks reading this thread. Mosaic Control is a control point that has absolutely no impact on the sound quality.
The dCS hardware is responsible for directly pulling down music streams, locally via UPnP or RAAT, or remotely via HTTP, completely separately from Mosaic Control. So, none of this discussion has anything to do with sound quality. 
my annoyance indeed has nothing to do with SQ, I do think my network is working well (I am not an IT specialist), the only “hick up” there is is with the Mosaic app. As said before I have learned to live with it, listening to music is relexation for me. (it makes me pick up my Ipad less and listen to full albums, like with records in the past)
@Anupc Like others have mentioned, I too experience the ‘Lost Connection’ message, but it’s not a big deal. In your reply you mention that Mosaic operates in a stateless fashion, which makes sense and that iOS loses the DAC’s state info once the device goes to sleep or Mosaic is no longer the app in focus. Does the same apply if using the Android version of Mosaic?
Yup, the software architecture remains the same even with Android as the host OS for Mosaic Control. However, similar to how preventing auto-lock/sleep on iOS/iDevice helps reduce the instances, Android may have a similar operating modes.
I rarely use my Android device with Mosaic Control, but maybe someone else who uses Android frequently can post about their experiences?
Or if you’re a tech sort of person, all my devices get a reserved address assigned by the DHCP server in my dedicated router - the ISP can make all the changes they want, my home network will never see them.
Interestingly, I’ve actually noticed this happening a lot more than it used to as well. I’ve been running Mosaic on a dedicated Android tablet for over a year now and recently when I wake it up it will work fine for maybe 30 seconds then freeze and need to reconnect. This has also started happening if I say queue up an album, go to the play queue and select “Play from here” on a specific track.
I figured this was some intermittent network issue or something at first, but it’s happening basically every time I use Moasic now. It’s hard to explain what might have changed though. I’ve been on the latest firmware and Mosaic build for a while, and haven’t made any major updates to the tablet or routers. Maybe something on the Qobuz side? Anyway, will keep an eye on it.
Yep happens on Android and has nothing to do with device going to sleep in my system - I suspect that’s a red herring. My n/w is stable and only Mosaic appears to demonstrate this behaviour compared to Naim’s which is used for most of the day in my other system and very rarely hangs. I would respectfully suggest dCS people sort this out as, whilst not mission critical, does look somewhat amateur and kind of annoying as others have noted.
Hi David,
I have both the Naim and dCS apps in use on my iOS and Android devices at home too and don’t have any issues with either but happy to escalate any issues that can be recreated to the dev team … what exactly is the issue that you are seeing with the Android version?
Easiest for us to track and respond if you could send details over to [email protected] then it gets into our ticketing system and it won’t get lost or buried in forum threads…
Best
Phil Harris
Thanks for coming back on this Phil. I just wanted to corroborate what others have said in this thread. Basically, Mosaic seems to lose connection with my Rossini player from time to time and then re-establish connection after a few seconds by itself without any user action. Mosaic 1.3.0 (132) is installed on my Samsung Galaxy S7 phone with Android 8.0. My Rossini was recently upgraded to APEX. The connection dropping seems to be intermittent, random and not very frequent. It is not to do with phone sleep or timeout settings. My network is stable and also as stated the Naim App never has a connection problem with my Naim devices. Nothing more to add really but I did not raise a support ticket as this is annoying but not a huge issue for me. However, as others also seem to be experiencing the same issue, there is clearly something general amiss. Happy to provide full details if dCS support wishes to follow up.
Hi Phil, you did say back in July (in this thread) that DCS were aware of this thread and were looking into what could be done to resolve the issue?
Thanks, Mike.
Anup explained this issue already in this thread
Hi Mike,
We are aware that the app comes up with a message that says that it has lost communication whilst it re-establishes the link.
I wanted to get details from David as to exactly what the issue that he was seeing was as often these threads do get quite loaded with “I have issues too” but they’re not necessarily the same issue.
As per Anup’s earlier breakdown of it, the time it takes to reconnect the app to a unit will vary dependent on the network and the amount of status information being pulled back from the device so I believe that the app authors are changing the text that is displayed whilst the app is reconnecting.
Phil
Im wondering if the size of the network or the number of access points between the mosaic control device ( whatever it is) and the hard wired vivaldi could effect this time
Hi Barry,
Very likely - and also depends on what “source” you’re listening to at the time too as the amount of data required to be sent to give Mosaic the correct status will also vary.
Phil
Exactly. Specifically, the number of hops between Mosaic on an iDevice/Android and the dCS unit.
In most cases, it’s at least 2 hops; a Wifi Access Point that the iDevice/Android is connected to, and a main Ethernet Switch that the dCS unit is connected to. The mDNS query/response through those hops for Mosaic to rediscover the dCS unit and then to get a fresh status update takes a split second or two.
As Phil indicates, it also depends on the source material album, length, cover art, etc., that contributes to the total time an update can take. And also on what else the iDevice/Android is doing, it’s not just sleep. Google Android especially, does all kinds of funky stuff in the background that often causes Mosaic to require an update from the dCS unit.