Just to rule another thing out (in case it was a bug with the update process from extension 0.2.0 to 0.2.1) I wiped my SD card and did a clean install of Ropieee.
But I get the same frozen screen when Roon is already playing to an endpoint and I then power the Pi up.
And just like I reported yesterday, rebooting from the ropieee.local page (while Roon is still playing to the endpoint) fixes the issue.
Off beta topic now. I am having issues with volume and my hifiberry amp+. As Ropppie reboots everynight it resets the volume back to 100 every time. Is there a way to make it stick at the last level you set. I could do this when using PiCorePlayer. Remembering to turn it down is always forgotten until it’s too late and my speakers and ears are not thanking me and expecting my kids and partner remember will never happen.
Never shut mine down unless updating it. It uses so little power and I like the convenience. Unlike PiCorePlayer Ropppie actually turns the display off. 
so no need to power it off.
Just found another possible but with touchscreen beta. When a playlist or any track reaches the end I get Connection Failure on the screen. This happens in both zones. Only happens when no leave anything to finish paying on its own.
Confirmed. I’ll try to fix this one tonight.
Just for my sanity, could someone advise how to force an update.
There’s no need to force anything. RoPieee will update by checking automatically. Right now that’s about 15 minutes after boot up.
Why do you suspect not to have the latest version?
Hi Harry
So I’ve yet to see any album art on my display. Currently I see unknown unknown etc on the screen and the controls don’t work. It’s playing fine. In theory it updated at 3 in the morning, but I can’t tell whether it did or not. Given others have seen album art I’m don’t know where I am. ROON has the extension version as being0.2.1, but I have nothing on the config screen via the IP address that allows any changes to the display.
So you’re saying that on the web page you can’t configure the rotation and default zone?
Correct. I thought at first it might a cache problem, but having cleared it I’m still not anything new. For some reason too. Ropieee.local doesn’t return anything either
That does’nt sound too good. Maybe you’re SD card is fried…
Hi Ian, when you say it’s playing fine, do you have a HAT on the Pi or using the USB audio from Pi to a USB DAC? Or just using the Touchscreen as a display/remote?
Strange that you can see the extension 0.2.1 in Roon but can’t access the Ropieee.local page 
AHi Sean
No, no Hat, USB only. I couldn’t get an install to work with the HAT on
, despite trying a couple of different memory card. I got a couple of new cards last night so I’ll give one of them a go. Fixed the .local issue though. I’d renamed the ropieees because I’ve got three of them. Ropieee3.local works fine, but I still don’t see any LCD config options.
I should add that I installed the LCD code manually using the instructions gave half well up the thread.
How can you use ropieee without a hat. Surely ROON doesn’t recognise the endpoint without something a hat or USB DAC attached ?
I’ll try a fresh install today.
Just to be sure: you’re using the beta build right? Only the beta build supports the touchscreen.
Guys,
I’ve pushed out an update to the beta channel yesterday evening. This update has a few ‘under the hood’ improvements to the touchscreen handling. The biggest notice is probably that I fixed the bug reported by @Simon_Arnold3 when playing stops because your queue is empty.
Just a heads up: I’ll be off for a few days, so during this weekend not that much activity will take place. I’ll try to create a new beta image tonight with the latest software (even though that RoPieee updates during install) for convenience reasons.
I’m working on something where you guys can send me log files etc. with a simple click on the web page. This can help in figuring out the more difficult bugs like the after-shutdown-and-power-on-the-screen-does-not-come-alive thing.
Regards,
My touchscreen finally arrived so I burnt the SD card and booted. Eventually I was able to browse to the Pis IP address and configured. Sound plays but the extension is not showing in Roon. Is there something I need to do to get it to show? Obviously nothing on the touchscreen when playing music.
Dear Harry
Good idea. Go take a break. We’re all very grateful for all your efforts. We can tell this touchscreen stuff is frustrating for you, given the success of ropieee so far, but stick with it. Given it still plays the rest can wait.
I hope so. The image file I’m using is ropieee-beta-20170605
Ian
I like the more spaced out buttons Harry. It’s looking better with each beta release 
I really hope you can consider having the artwork at maximum possible size (keeping aspect ratio) to make more use of the big 7"screen (bigger than SBT screen anyway). But that’s for much later of course.
Enjoy your break mate and try not to think about the after-shutdown-and-power-on-the-screen-does-not-come-alive thing.
One other future request Harry - can we disable the auto update, in the future?
I have setup Ropieee with my dad’s HiFiBerry DAC+ PRO and it works great.
But if it auto-updates itself in the future and there is a bug with that new update that results in not being able to play the unit, then he won’t be able to use the unit until I next visit him (could be days, or a weeks). He wouldn’t have a clue how to reload an image or even reload the fixed image, for example.
At least if a particular version is working for him, then it should stay working for him until I visit next time and update his unit to the latest myself.
I do love the auto update feature for my own use (because I am lazy but it’s also really easy for me to repload a new version) but I just wonder if there are others in a similar position that maybe want to do an update in their own time, for their own different personal reasons.
Another scenario, if someone is using it as an endpoint, then 15 minutes after powering up if it automatically fetches the latest version and reboot’s itself, then music playback is interrupted. In certain situations, the end user may not want that, maybe?
This is only for when you get back. Enjoy your mini break !!