your receiver encountered a software problem and needs to be restarted

do a clean flash, don't restore any settings,see if that helps

File "/home/oe1/atv62/build-enviroment/builds/openatv/release/8100s/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/enigma2-plugin-skins-metrix-atv/2.1+gitAUTOINC+3622c4bd70-r7/git/usr/lib/enigma2/python/Components/Renderer/MetrixHDXPicon.py", line 80, in changed

14:18:15.1775 { D } File "/usr/lib/enigma2/python/Components/config.py", line 1846, in __getattr__

14:18:15.1777 { D } KeyError: 'MyMetrixLiteOther'

14:18:15.1778 [ E ] python/python.cpp:209 call [ePyObject] (PyObject_CallObject(<bound method Navigation.dispatchEvent of <Navigation.Navigation instance at 0xb1b48468>>,(0,)) failed)

By the looks of that your mymetrixlite is missing.

This mymetrixlite plugin is used to enable you to customise the default metrix skin.

You can always try manually deleting the metrix skin from your box.

The folder lives in usr/lib/enigma2/python/plugins/extensions.

Delete the mymetrix folder via ftp or samba and reboot your box.

** edit - I was nearly right their was an error in mymetrixlite settings screen. This has now been corrected on openatv github - see later posts below **

Coincidentally, I think this broke, because iPKay of openatv seemed to have put in a picon resizing amend into todays openatv release.

This actual amend is based around my picon code I was experimenting with yesterday on openatv github.
Looking on github he has tried making a config option for it to appear in mymetrixlite.

Something has obviously not be implemented correctly.

You just downloaded the openatv image at complete the wrong time. Yesterday would have been fine. This evening would have been fine (I think)

59aa2be0015221.png

change to any other image

Well as for the last 2 days we have been experimenting with more picon related stuff. Expect another dodgy release soon. ha :)

Yes. Anywhere that calls the picon code will be resized smoothly. Especially useful for 1080 skins that are not necessarily calling in the picons at the original sizes. It also means you can just download 1 picon set, i.e 400x240 or 220x132 and this will work nicely everywhere. In my skins this would be on the infobars, eventview, movie eventview and at the top of my channel select and top of epgs. It will not resize smoothly picons that appear in lists such as in the channel select list, epg list or history zap. That is a completely different code.

Openatv are just experimenting and implementing this as an optional MetrixHD skin setting at the moment. But I have written a seperate renderer so it will be used by all my skins as standard. When I have released my updated skins, I will make available my new picon.py code that can replace the picon.py file on your box for anyone that wishes to use it for anything other than my skins.
Resizing 32bit pngs was easy, we ran in to problems with 8bit indexed pngs that had been compressed due to the transparency not always being picked up correctly. I have now found a solution to this after hours and hours of searching. So the code will now work with all types of picons, whether 32bit or 8bit.
We just need the brains behind enigma2 to possible edit the multicontent graphics code now (lists). But I wouldn't hold your breathe on that one.