Android Sonos App (latest version, 80.14.06) startup time is very long on my phone (xPeria J9210, Android 11), even after I wipe out all cache/data, reinstall the app, and start it with phone IN FLIGHT MODE, i.e. no WIFI, no access whatsoever to my players.
It takes about 2 minutes for the app to finally tell me that I need to enable the Wifi to find my system.
And after enabling Wifi, it takes only a few seconds for the app to really find my system and be ready to roll. So the startup time issue can not be related to the players configuration, interference, or wifi/router setup.
This is also confirmed by the fact that the same app version on a separate (Android 14) tablet starts and finds the system in a few seconds.
So I tried to understand what could cause this massive startup delay and traced the android system activity during the startup phase using common Android debug tools (perfetto trace).
What I found is that OkHttp Dispatch thread of the com.sonos2.acr2 app experiences a “Lock contention on a monitor lock” stalling app progress during 1mn 46sec. This seems related to runtime library loading in Java.
I know by having worked in hardware monitors design that such livelocks can indeed happen, with long durations.
I expect that this is a possible root cause for many of the large startup app delays that are unexplained by the more common network-related causes - I know that I am not alone facing similar startup times. They can also happen randomly when reactivating the app from the background, even if it has not been closed.
There is most probably a way to fix these issues in the sonos app code.I have a bit more detail to report (I could send the trace for example), but I think that only Sonos engineering can really analyze what’s going on, and I have not found any way to contact sonos engineering, or even human support, directly.
Can anyone direct me to the proper channel to report these findings ?
