I try to check tomorrow. Currently I'm not at home.
skin displayfor et8500 not works
Started by Dimitrij, 20 Dec 2015 14:23
30 replies to this topic
Re: skin displayfor et8500 not works #21
-
- PLi® Core member
- 7,185 posts
+323
Excellent
Posted 24 December 2015 - 12:45
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04
Re: skin displayfor et8500 not works #22
-
- PLi® Core member
- 46,960 posts
+541
Excellent
Posted 24 December 2015 - 18:49
Yes you're on holiday!!! 
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: skin displayfor et8500 not works #23
-
- Senior Member
- 4,795 posts
+15
Neutral
Posted 25 December 2015 - 11:14
Not sure if this is related, but lcd4linux on the et8500 is currently non-functional, it always shows the video signal on the lcd.
Re: skin displayfor et8500 not works #24
-
- PLi® Core member
- 10,039 posts
+339
Excellent
Posted 25 December 2015 - 11:41
maybe...
configure.ac
AC_ARG_WITH(fbdev, AC_HELP_STRING([--with-fbdev=devicename], [use devicename for framebuffer device, e.g. /dev/fb0 ]), [[with_fbdev=$withval]], [[with_fbdev=no]] ) if test x"$with_fbdev" != xno ; then AC_DEFINE_UNQUOTED(FB_DEV, "$withval", [Defines which device to use for main framebuffer (e.g. /dev/fb0)]) fi AC_ARG_WITH(lcddev, AC_HELP_STRING([--with-lcddev=devicename], [use devicename for lcd framebuffer device, e.g. /dev/fb1 ]), - [[with_fbdev=$withval]], - [[with_fbdev=no]] + [[with_lcddev=$withval]], + [[with_lcddev=no]] ) if test x"$with_lcddev" != xno ; then AC_DEFINE_UNQUOTED(LCD_DEV, "$withval", [Defines which device to use for lcd (e.g. /dev/fb1)]) fi
Edited by Dimitrij, 25 December 2015 - 11:42.
GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K
Re: skin displayfor et8500 not works #25
-
- PLi® Core member
- 7,185 posts
+323
Excellent
Posted 25 December 2015 - 11:47
Yes, that is the error. And fix looks good.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04
Re: skin displayfor et8500 not works #26
-
- Forum Moderator
PLi® Core member - 7,599 posts
+62
Good
Posted 25 December 2015 - 15:54
yes, my bad. merged.
Geen wonder... Had slechts een dm7000, maar wel ook een rotor. eigenlijk al een tijdje ook een dm600 en dm7025. Maar nu kijkend met een et9000 en vuduo
Re: skin displayfor et8500 not works #27
-
- Forum Moderator
PLi® Core member - 14,661 posts
+460
Excellent
Posted 26 December 2015 - 14:23
I just checked the ET8500, the display 'problem' is solved 
Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....
On the edge of the abyss, a step forward is not always progress....
Re: skin displayfor et8500 not works #28
-
- Senior Member
- 4,795 posts
+15
Neutral
Posted 26 December 2015 - 14:45
I just checked the ET8500, the display 'problem' is solved
The lcd is functioning again here as well, however the skin_display.xml seems to work only partially. Menu listings (detail) and filebrowser are visible, but other screens remain blank. Does anyone else experience this?
Re: skin displayfor et8500 not works #29
-
- PLi® Core member
- 10,039 posts
+339
Excellent
Posted 26 December 2015 - 15:45
I just checked the ET8500, the display 'problem' is solved
The lcd is functioning again here as well, however the skin_display.xml seems to work only partially. Menu listings (detail) and filebrowser are visible, but other screens remain blank. Does anyone else experience this?
So it was before.
GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K
Re: skin displayfor et8500 not works #30
-
- Senior Member
- 4,795 posts
+15
Neutral
Posted 26 December 2015 - 16:11
So it was before.
Ah i see, what is the rationale behind this? Is it a work in progress, or are there other reasons for it to function like this?
Edited by litemotiv, 26 December 2015 - 16:11.
Re: skin displayfor et8500 not works #31
-
- Senior Member
- 4,795 posts
+15
Neutral
Posted 26 December 2015 - 17:33
So it was before.
Ah i see, what is the rationale behind this? Is it a work in progress, or are there other reasons for it to function like this?
To answer my own question: i needed to copy /usr/share/enigma2/skin_display.xml to /etc/enigma2/skin_user.xml.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
