It's a kind of touch panel so does look like it's going to end up being that at fault - just logging a ticket now
Mega strange it was fine with OpenATV and OpenHDF for as long as it was and always tripped up when I went back to ViX - I'll go back to OpenATV as there's a chance the prodding of the panel causes it to start going haywire when each flash is done.
Saying that the front panel never gets used so it starting to turn itself down I guess is the sign of it slowly starting to fail. It's certainly been a random one!
Do the front panel buttons actually change the volume in OpenATV when you press them?
When you press them yes they work fine and log the same as the remote button press.
I noticed the latest OpenViX versions are using a newer kernel than OpenATV.
OpenViX 5.0.016 - Linux xpeedlx3 3.14.2 #1 SMP Sat Apr 22 16:21:03 BST 2017 mips GNU/Linux
OpenATV 6 - Linux xpeedlx3 3.14.2 #1 SMP Tue Feb 14 03:48:43 CET 2017 mips GNU/Linux
They show as the same version but with a different build date.
OpenViX & Egami both started turning the volume down while in the setup wizard screens and so far nothing on ATV again so far.
I've tried pressing volume up and down on the front panel to see if it will start triggering the automatic volume down to kick in.
Finally - after much fiddling it's doing it in OpenATV now too - looks like it is the front panel on the way out then so a warranty job.
From the OpenATV debug logs:
I guess me flashing images and pressing the up button was doing something to the panel which is why sometimes it would be ok post flash and other times not - it was just pure coincidence it was ok with OpenATV and OpenHDF.Code:11:45:49.8547 [ ] driver/rcinput.cpp:38 handleCode 1 72 1 11:45:49.8565 { } Screens/InfoBarGenerics.py:208 actionA KEY: 114 0 KEY_VOLUMEDOWN 11:45:49.8571 { } Components/ActionMap.py:46 action action -> GlobalActions volumeDown 11:45:49.8576 [ ] dvb/volume.cpp:152 setVolume Setvolume: 98 98 (raw) 11:45:49.8578 [ ] dvb/volume.cpp:158 setVolume [AUDIO_SET_MIXER] Setvolume left: 2 right: 2 (-1db) 11:45:49.8582 { } Screens/Screen.py:151 show [SCREENNAME] Volume 11:45:49.8599 { } Screens/Volume.py:13 setValue setValue 98 11:45:49.8604 [ ] driver/rcinput.cpp:38 handleCode 0 72 1 11:45:49.8624 { } Screens/InfoBarGenerics.py:208 actionA KEY: 114 1 KEY_VOLUMEDOWN
Thanks for the help guys but at least now it's looking a bit clearer what the issue is
On the plus side I know how to fully configure a lot more images now!