The information tab is a welcome one…and also I can confirm the non LCD units don’t display the Display tab 
Yeah. That was also what I thought. The tab will stay though, but the user interface will show a warning:
“You’ve made changes that require a reboot to take effect. Click here to reboot”
Something like that. Stay tuned.
So for a new installation, two reboots will still be required?
First select HAT. Then need to reboot before you can rotate the screen and setup the Roon zone, then another reboot?
For now it is, but that will change.
Ah cool 
@spockfish Harry is it possible to move to the beta channel from a command line update? My RPi on one setup is using 4.9.39-1-SPCKFSH is it possible to get it the l;latest build without loading up a new image? I tried the update command line you gave me some time back and it returns
*** RoPieee: checking for updates...
** run-updates: attempt 1 **
:: Synchronizing package databases...
ropieee is up to date
core is up to date
extra is up to date
community is up to date
alarm is up to date
aur is up to date
:: Starting full system upgrade...
there is nothing to do
ok…
but this is gonna be tricky, so you’re on your own 
- edit the file ‘/etc/ropieee.conf’; change the variable ‘rp_repo’ from ‘stable’ to ‘beta’.
- run the following command: /opt/RoPieee/sbin/configure
- reboot
4 pray 
Once I got my brain around vi (a quick google for commands) it took only a few seconds and its all updating now…fingers crossed…no need to pray 
My dad’s DigiOne setup auto updated to 0.4.0
And Roon could no longer see his DigiOne. When I go to the settings webpage, if I change the HAT to ‘none’ and reboot, it reboots and shows the DigiOne again. I also noticed it is on the ‘stable’ channel, whereas when I did my clean install with my own touchscreen, it stayed on beta.
If I change his to beta, it reboots and still shows stable after the reboot.
Sigh, this is why I really want the 24 hourly reboot off, as an option.
When I leave his place I really want the music to play non stop until I next visit him - then I can do a manual update if necessary.
But at the same time I do understand we are in the beta phase and this feedback can help Harry. So not a complaint - just feedback lol
I’ll do a clean install for his DigiOne and DAC+ Pro setups
Did a clean install on dads DigiOne and it’s working fine on 0.4.0 now.
I had the black artwork come up after an hour of Tidal streaming but then the next track, different album, cover art came back.
So it self corrected, the first time I’ve ever seen this.
Edit: after the earlier self correction, no the black cover art is definitely still here with 0.4.0. It’s been black for a few different albums now.
Dad’s DAC+ Pro is failing to pull the latest update.
Is there an issue at your end with infrastructure Harry?
It only pulled 0.3.5
Not that I’m aware of. Can take a while though.
hmmm… ok. I had my hopes that it was gone. In my scenario I really need to change albums like an idiot to reproduce it. Bummer.
Well, my holiday started today, so I know what to do 
In the holiday I’ll merge the screen support to stable. And ‘stable’ is treated highly conservative (it receives updates only when needed), so as soon as that’s in place you can switch your dad’s setup to ‘stable’.
Regards Harry
Cheers Harry. I was at dad’s place and had a Tidal playlist playing (so each song is a different album).
I am an idiot in general, but we never touched the ‘next track’ button. We just let Tidal play and we still got the black artwork.
But that issue is low on my care-factor list, compared to Roon losing his DigiOne after the self update to 0.4.0 - which was fixed with a clean install. Because that meant the music couldn’t play.
Thanks for the support Harry.
Been away for a few days but main unit has failed to upate to latest version 0.4.0. Any suggesttions rather than disassemble the whole thing to reflash the card?
I was successful editing the config file per Harry’s suggestion, and then my system upgraded over night (despite my trying a few reboots to force the issue).
`[quote=“spockfish, post:248, topic:27888”]
ok…
but this is gonna be tricky, so you’re on your own 
edit the file ‘/etc/ropieee.conf’; change the variable ‘rp_repo’ from ‘stable’ to ‘beta’.
run the following command: /opt/RoPieee/sbin/configure
reboot
[/quote]
Thanks but with what editor as vi does not seem to work?
Ooh, vi was fine for me—so /usr/bin/vi doesn’t exist?