abu baniaz
i know you have said you have done this now
sky uk guide is really easy to get the full size image
Click a channel icon to open the channel modal.
pasted-from-clipboard.png
right click the icon on the pop up modal.
open image in a new tab
i.e https://d2n0069hmnqmmx.cloudfr…gos/100/40/skychb1009.png
change the values 100/40 to 0/0
you can do that with any of the channel icons on https://www.sky.com/tv-guide/
I will get back to these skin updates very shortly.
It's just a very busy time for me the last few weeks. 21sts, 50ths, mums 80th, stag doos, weddings. Just not a lot of spare time at the moment. Plus it was too dam hot in my little enigma2 work office.
Normal service will resume next week. (when its meant to be even hotter)
That is very kind of you kari
But for the time being, my box seems to functioning correctly.
I am always tempted to try the AX61 uhd. But its a big box. Compared to my tiny dinobot 4k and vu zero 4k its like a giant.
And as they are all quad core with Hisilicon HI3798MV200 I think I prefer my little boxes.
If anything changes in the near future I will drop you a line. Thanks buddy.
And thanks to all the other people who have offered me spare boxes in my hour of need. No need to be greedy and just accept them when I no longer need them.
But one day I might 
That all depends which skin you are using.
Main graphics for the spinner live here
/usr/share/enigma2/spinner/
any other skins probably live in
/usr/share/enigma2/[skin]/spinner/
they are separate png graphics. Not animated gifs.
Display More
Do you want these removed?
E2Piconizer
Codepkg_postrm:${PN} () { #!/bin/sh echo "Removing E2Piconizer Plugin from the system ..." rm -r /usr/lib/enigma2/python/Plugins/Extensions/E2Piconizer > /dev/null 2>&1 rm -r /etc/enigma2/E2Piconizer > /dev/null 2>&1 exit 0 }
JediMakerXtream
Codepkg_postrm:${PN} () { #!/bin/sh rm -rf /etc/enigma2/jediplaylists/playlist_all.json > /dev/null 2>&1 rm -rf /usr/lib/enigma2/python/Plugins/Extensions/JediMakerXtream > /dev/null 2>&1 rm -rf /etc/enigma2/*jmx*.* > /dev/null 2>&1 rm -rf /etc/epgimport/*jmx*.* > /dev/null 2>&1 sed -i '/jmx/d' /etc/enigma2/bouquets.tv echo "Restart GUI to finish uninstall!" }
jediepgxtream
Codepkg_postrm:${PN} () { #!/bin/sh rm -rf /etc/enigma2/jediepgxtream > /dev/null 2>&1 echo "Restart GUI to finish uninstall!" }
Yeah we can remove the postrm. With that nature of some of my plugins saving user files in the etc folder. Not everybody wants a post uninstall clean up. Especially the etc folders. The other postrm was just to remove any compiled files left overs.
Delete them all. And if they exist in my local files I will remove them too.
I hate opening a thread I have not read for a week and seeing a full conversation :)
OK I will get reading.
Damon Chaplin these skins were designed several years ago, when boxes were slow. Oh the joys of my zgemma S2 :). So at the time they were optimised.
Which is why the code was all templated. At the time all the pngs were compressed.
The JPGs were considerably smaller than PNGs so for memory size this is why they were used for some backgrounds.
Since then, all the image teams builds have nearly doubled in size. Bloat, bloat and more bloat.
Also since then we have moved on to python 3, which despite its claims, was never as fast as python 2 builds.
We also have 1080 skins now as the norm (which doubled all the size of the graphics), and now also UHD screens for dreamboxes.
So everything is getting larger and bulkier and using more memory.
All my skins have very little tweaks over the last few years as my primary focus switched to my plugins and not skins.
But I am giving them a once over at the moment. No harm making suggestions and improvements. But any improvements or tweaks have to work on all oe-alliance images. And tweaks have to be in the skin files, not the enigma2 core components. That isn't my issue.
I am moving lots of files around on github, abu is busy trying to shadow me and keep things running.
Don't expect all feeds to sync up yet. There will be a period of times when things might not work correctly from feeds.
There has also been a discussion on oe-alliance github about rogue postrm files that they have never removed. So that should be resolved soon.
Also future releases should only be my files as we have changed the way they are now tagged and released.
i'll add them to my to do list, thanks.
sorry, late to the party.
I have never seen anyone type out the full address of an ipk to install it. 
I am in the same boat as everyone else. And to clarify I do the same.
Copy all the ipk's I want to install into to tmp folder. Making sure any old stragglers are removed from there.
opkg install /tmp/*.ipk
and if we got version issues, you just use
opkg install --force-reinstall /tmp/*.ipk
and qatar2030 if I remember correctly without me checking. I am sure there is full instructions in all my plugin threads of how to install with the above methods.
Enigma2 KiddaC
If you are refering to the ipks of my plugins. They all live in the first posts of my plugin threads
All instructions are in the threads.
I don't skin a lot of 3rd party plugins. Especially not dreambox plugins. As I don't have a dreambox. Sorry
its empty because I not amended it yet
lets try again. All fixed. I will reupload both slyk q and onyx again.
i know what I have done now. grrr.
I have copied new slyk onyx onto slyk q vix file.
Therefore they are both now wrong.
and the o-vix.xml file is not my amended one. So I mustn't have saved that correctly either.
I will compare it with my slyk-q file as its meant to pretty much echo the same structure as that.
I am going to have to check all the onyx files again now. To see where I went wrong. Hopefully just a handful of mistakes. Doh.
OK I will fix skin.xml on onyx. Thought I had done that. Probably didn't save it after editting it.
Some of these screens might have list alignment issues as mentioned. I will probably fix them later. As I need to remember all the big changes I am making for all the skins. Then we can tweak the minor things.
dsayers
Just to let people know, I am it a bit of transition with all my skins. Which means I am moving about a lot of stuff about on github.
While this is happening, I presume the feed versions will not be updated until I have finished faffing.
So for latest version, you might have to rely on the ipks until I have finished the process, and we get everything synced up again.
Pete29871 er... a lot of screens you can press menu to enter the settings and increase the font size.
To do it globally (although this will probably break layouts due to how the screens were designed to fit this font size with English text), you can amend the font values in skin.xml
usr/share/enigma2/[skin name]/skin.xml
<font name="Regular" filename="fonts/slyk-regular.ttf" scale="100"/>
change to scale factor.
If you just want to do it on a particular screen, send me a screenshot of that screen, and I will tell you where that value lives.
