I am almost reluctant to report any alleviation of these crashes since they nearly always come back (and when they do they’re vengeful).
However with the latest update to 918 I have not had any crashes. Unfortunately I can’t locate my prior logging - if it mattered —this many days later.
I suppose the frustrating thing for Roon users continues to be any immediate fix ends up not truly being stable across their user base. I have had the same problem since the outset - for years. That such a fundamental problem should continue to persist as among the most consistently reported issues in your forums is concerning. It’s akin to a piece of hardware switching off on its own all of the time —and certainly no one would tolerate that occurring.
…and yet despite this dogged problem I have continued to pour money into the product because on a good day -when it’s all working - there is nothing that comes close to competing with it.
I want nothing more than for this product to succeed. However, being able to listen to music supersedes my desire for this product to succeed and therefore I find myself increasingly —however imperfect the interface might be - using the native Lumin app - which never has issues.
Even Volumio with its fiddly open source nature is more stable for longer periods than Roon.
Despite my statement just a day ago - as if like clockwork - 923 has reintroduced my instability and stage. The crashes are back - and so bad there’s barely an opportunity to click on anything.
I uploaded two separate logs from today (for all the good it will do).
So incredibly frustrating.
Back to Lumin until I can hear what more Roon has done to “fix” or “much improve”
I used to have my share of iOS crashes but now it seems fine. Can you detail your network structure please? All my problems were network related and never thought a single minute that was. Stay tuned!
Amplifi alien + 1 mesh
Wifi (mixed)
M1 Mac mini (core)
IPv4 (6 is disabled)
Qnap NAS for local files and backup
No separate hardware firewall
I used to run a NUC (rock) but anecdotally it seemed to run less stable so I switched to Mac mini. The instability is so dogged it drives one ultimately to just try anything. I kicked the Nuc down to secondary Volumio node duty and shocker - it really never has issues.
My network is really pretty basic and while I like the Amplifi solution it’s UI is not especially powerful. In other words, there is a not a ton of user control on offer sufficient to implement any especially more sophisticated setup.
Same issues here. Latest core, latest iOS app, latest version of iOS on a 12 Pro. The Roon iOS app crashes in less than 5 seconds every time I try to use it.
I have moved to a dedicated M1 Mac Mini connected directly to router and have been without crashes for several days. Sadly right when I was started to grow accustomed to Roon not crashing inside of 30 seconds - the crashing has returned.
Nothing - no combination of miracles ever truly resolves this hideous instability. I will upload logs again for all the good it will do.
At this point the instability is comically bad. It feels as if Roon just want to punish and drive away iPhone users.
The guy from lumin adds in his final suggestion “use android device.” This entirely defeats the point and I countless users are making.
I’m not saying Android is better and I’m not telling people to use it.
My philosophy in problem diagnosis is to try everything, thereby gradually narrowing down the culprit.
If both iOS and Android apps crash in the same way, it may be your network or Core. In this case, the next step is to use a wired client (with some hassle even iPad can be wired), if on a wired network it does not crash you’ll know it’s the WiFi. Alternatively, move the Core to Windows.
Anyway, if my offering of suggestions is not appreciated I’ll amicably leave this thread.
I have done nearly everything there is to do (including as you mention having a windows core). In the case of the mini it’s literally brand new with nothing else running on it. I removed everything there is to remove.
I appreciate the feedback but the key feedback I want - we all want - is feedback from Roon. This is a remarkably tedious way to obtain support.
Getting something like this to just simply run in a stable manner on about as common a mobile device as exists on planet earth should be the entry level - base requirement for such solutions.
I uploaded logs but for what? Is anyone analyzing them and offering feedback against what they found? Nope. All I continue to get is anecdotal try this and try that. It’s fumbling and non specific and painfully ineffective.
Thanks for letting us know of those updates. We have looked over logs, yes, but we have been unable to locate any crashes contained in the logs.
Also, it looks like your iOS devices are not communicating with our diagnostic servers which is strange. While running the Mac Mini as a Core, have you noticed any crashes on the Mac Mini Roon app itself or only on iOS?
I just uploaded another log file. The app crashes on my iPhone now in about 5 seconds. I have futilely reinstalled, rebooted several times.
It’s only iOS devices. I have not really had any
core crashes.
Its always been iOS issues that have plagued me for the years I have hung in there with Roon. Note this problem occurs on multiple iPhones.
I have not had much interest in iPad because the last time I checked I could not do basic page orientation - a feature available to even the most basic apps.
Let me know if the latest log i sent reveals anything interesting.
Any luck with my most recent log data? The latest version of Roon might actually have the worst instability I have experienced on iOS
I feel at this point like I am talking into a void. Oddly given the fits and starts responses from Roon via this “community” support model - I almost wish for a more traditional support scheme. I never thought I would lust after old school creating a support ticket and having someone work it to completion.
Thank you for sending those logs and for your patience while we’ve had a chance to review them. It looks like your Roon app might be crashing due to running out of memory, but the reason for the memory issue is not clear. Can you confirm if you are still able to reproduce the issue on our latest release, build 933?