18-Oct-2021, 03:13
Minor update: I discovered the Phantom web server via this thread. Logged in, and noticed that on the wifi page, there was no entry for my 5GHz network, only the 2GHz one. Setting the password for the 2GHz network from the web server failed to fix anything. But I was able to get both Phantoms registered via the Android app, by specifically choosing the 2GHz network. This doesn't seem like a complete fix, because my DOS 1.0 experience has been that a 2GHz connection results in audio dropouts and is generally not usable.
Of course, as soon as I managed to get them both working, the Devialet app hit me with "new update available", which I tried, and of course it failed. After which, one of the Phantoms was undiscoverable. Several power cycles, long-press resets, app restarts & reinstalls ensued. The missing Phantom would sporadically take several minutes to boot up (the other about 30sec).
I eventually got both re-registered (again via the Android version of the app), and ran system update successfully. Interestingly, the firmware version after the update showed exactly the same version number as before. But various issues continued: at one point, the optical input to the left Phantom (which is my only audio source) would not play, nor would it auto-switch when turned on. Both versions of the app will periodically fail to see either of the now-registered devices
I'd hoped to have a secret sauce to post, once I'd gotten everything working. But at this point, I'm about where JD is: just keep resetting everything, power cycling, restarting/reinstalling the app, etc. The only piece of advice I have is to try 2GHz, if 5Ghz doesn't work.
It remains to be seen if the setup is any more stable under DOS 2.0. But I guess at least now the Dialog is out of the picture. My DOS 1.0 setup would consistently break every 1-2 days, and I'd have to power-cycle the Dialog. I suspect there will be more updates to this thread, though I'm really hoping not.
Of course, as soon as I managed to get them both working, the Devialet app hit me with "new update available", which I tried, and of course it failed. After which, one of the Phantoms was undiscoverable. Several power cycles, long-press resets, app restarts & reinstalls ensued. The missing Phantom would sporadically take several minutes to boot up (the other about 30sec).
I eventually got both re-registered (again via the Android version of the app), and ran system update successfully. Interestingly, the firmware version after the update showed exactly the same version number as before. But various issues continued: at one point, the optical input to the left Phantom (which is my only audio source) would not play, nor would it auto-switch when turned on. Both versions of the app will periodically fail to see either of the now-registered devices
I'd hoped to have a secret sauce to post, once I'd gotten everything working. But at this point, I'm about where JD is: just keep resetting everything, power cycling, restarting/reinstalling the app, etc. The only piece of advice I have is to try 2GHz, if 5Ghz doesn't work.
It remains to be seen if the setup is any more stable under DOS 2.0. But I guess at least now the Dialog is out of the picture. My DOS 1.0 setup would consistently break every 1-2 days, and I'd have to power-cycle the Dialog. I suspect there will be more updates to this thread, though I'm really hoping not.
