View Full Version : [ET10x00] small text size in one menu page
Xtrend ET10000, SkinVix-Night-1080
I have my box configured that when I press the EPG button on my remote I first get a screen where I can first select the bouquet.
Configuration:
Open the epg grid screen and press menu on the remote and in the configuration menu that appears - select “Show bouquet on launch = yes”
I’ve just performed a software upgrade from 6.0.003 to 6.0.006
In 6.0.003 the text to select the bouquet was a “normal” size
In 6.0.006 the text size has shrunk to barely readable.
63195
All other menu screens seem to have the same text size as set in 6.0.003.
Hello, I have the same problem in CCcam info page, small text and no space between rows, not a big problem for me, but might be related.
Looks ok on my ET10K on 6.0.006 (flash and restore settings) using the simple_1080 skin...
63196
Changed the skin to Vix-Night-1080, wish I hadn't, it's stuck on live tv with the info bar, remote doesn't do anything, and I had switched off debug logs as I was also trying out something else.:(
Can't even capture a screenshot, OpenWebif just displays its spinner.
Got rid of the ViX-Night-1080 folder and now ok again. (Had to reboot, init 4 did nothing, nor did init 3.)
Nothing obvious in the debug logs, no spinner.
12:32:38.3354 [Skin] Error: [Skin] {ViX-Night-1080/skin.xml}: Pixmap file 'ViX-1080-Common/buttons/FocusBar_H45.png' not found! Please contact the skin's author!
Line 270: 12:32:29.8928 [Skin] Warning: Skin file 'skin_user.xml' does not exist!
Line 477: 12:32:38.6555 [Screen] Warning: Skin is missing element 'state' in <class 'Screens.PVRState.TimeshiftState'>.
Line 479: 12:32:38.7596 [Screen] Warning: Skin is missing element 'message' in <class 'Screens.SubtitleDisplay.SubtitleDisplay'>.
Line 486: 12:32:39.1676 [Screen] Warning: Skin is missing element 'VolumeText' in <class 'Screens.Volume.Volume'>.
Changed the skin to Vix-Night-1080, wish I hadn't, it's stuck on live tv with the info bar, remote doesn't do anything, and I had switched off debug logs as I was also trying out something else.:(
Can't even capture a screenshot, OpenWebif just displays its spinner.
Got rid of the ViX-Night-1080 folder and now ok again. (Had to reboot, init 4 did nothing, nor did init 3.)
Nothing obvious in the debug logs, no spinner.
12:32:38.3354 [Skin] Error: [Skin] {ViX-Night-1080/skin.xml}: Pixmap file 'ViX-1080-Common/buttons/FocusBar_H45.png' not found! Please contact the skin's author!
Line 270: 12:32:29.8928 [Skin] Warning: Skin file 'skin_user.xml' does not exist!
Line 477: 12:32:38.6555 [Screen] Warning: Skin is missing element 'state' in <class 'Screens.PVRState.TimeshiftState'>.
Line 479: 12:32:38.7596 [Screen] Warning: Skin is missing element 'message' in <class 'Screens.SubtitleDisplay.SubtitleDisplay'>.
Line 486: 12:32:39.1676 [Screen] Warning: Skin is missing element 'VolumeText' in <class 'Screens.Volume.Volume'>.
Snap
My et10000 comes out of deep standby and displays the last channel selected before going into deep standby but the remote has no response at all (Skin Vix-Night-1080). The info bar remains on the screen.
The only way out of this is to switch off the box via the mains.
It looks like 6.0.006 and the Vix-Night-1080 skin is completely broken for me on my ET10000
It was all working for 6.0.003. I didn't upgrade to 6.0.004 or 6.0.005
My Ultimo4k works ok running 6.0.007.002 (Dev), Vix-Night-1080, (same skin warnings as the et10k).
Also ok running 6.0.006 (Rel).
Oddly, this message appears when using Vix-Night-1080 on the vu, it's been mentioned in another thread.
[gSurface] ERROR: accelAlloc failed
ET10K, flashed 6.0.006 with no settings or plugins restored, just a tuner up and running.
First time I pressed ok on the infobar it hung, after a reboot it's working ok.
Really weird, I tried again from scratch and its working ok. :confused:
ET10K, flashed 6.0.006 with no settings or plugins restored, just a tuner up and running.
First time I pressed ok on the infobar it hung, after a reboot it's working ok.
Really weird, I tried again from scratch and its working ok. :confused:
The complete freeze seems to be an intermittent problem. I've seen it a couple of times after the box has been in deep standby for hours. Put the box into deep standby and put it back working a short time later and there is no problem with the box freezing (remote having no effect but live TV working on one channel and the info bar remaining on the screen)
Unfortunately I have other priorities over the next few days so I've now just reverted back back to my backup copy of 6.0.003 which is working OK.
... yes, I've been wondering whether my Ultimo4k just happened to work when I tried it out.
ET10K debug log switching from simple_1080 to Vix-Night-1080, froze the first time I tried this morning (and every time since).....
Noticed this in dmesg, it only appears when I change the skin to ViX-Night-1080...
[ 552.495000] Trap instruction in kernel code[#1]:
[ 552.495000] CPU: 1 PID: 844 Comm: enigma2 Tainted: GF O 4.10.6 #1
[ 552.495000] task: cd966f80 task.stack: ce506000
[ 552.495000] $ 0 : 00000000 10008b00 00000001 00000000
[ 552.495000] $ 4 : 00000035 00000023 00000000 00040000
[ 552.495000] $ 8 : 00008000 e14873e0 00000010 00000010
[ 552.495000] $12 : 00000000 00000000 00000000 73e4978c
[ 552.495000] $16 : cf5f025c cf5f0368 007030d0 0000003e
[ 552.495000] $20 : e0d70000 e0d70000 e0d70000 e0c90000
[ 552.495000] $24 : 00000000 800716a0
[ 552.495000] $28 : ce506000 ce507528 e0d90000 e0c942e0
[ 552.495000] Hi : 00000001
[ 552.495000] Lo : 00000003
[ 552.496000] epc : e0c943f0 __bb11f9+0x774/0xbd8 [dvb]
[ 552.497000] ra : e0c942e0 __bb11f9+0x664/0xbd8 [dvb]
[ 552.497000] Status: 10008b03 KERNEL EXL IE
[ 552.497000] Cause : 00800034 (ExcCode 0d)
[ 552.497000] PrId : 00025a11 (Broadcom BMIPS5000)
[ 552.497000] Modules linked in: ipv6 rtl8192cu rtl_usb rtl8192c_common rtlwifi mac80211 enigma(FO) xfs(F) libcrc32c(F) dvb(FO) modloader2(FO) modloader(FO) tpm(FO)
[ 552.497000] Process enigma2 (pid: 844, threadinfo=ce506000, task=cd966f80, tls=73e518d0)
[ 552.497000] Stack : 6c7fbdfd fffffbfb 67ff5fff fcdffc7e dfcffdff fffff3bd fffffeee 5332d8be
[ 552.497000] 850d1000 00702fd8 00000040 7fe5f7ff fadcff7f ff7f7dbb ffff79f7 00000013
[ 552.497000] 00000013 04380780 0000000c 00001e00 850d1000 86381d80 00000000 00000000
[ 552.497000] 00000000 00000000 00000000 00000000 cefd3500 00000000 03870551 00350001
[ 552.497000] 00000001 00000001 00000000 00000000 00000000 00000000 00000000 00000000
[ 552.497000] ...
[ 552.497000] Call Trace:
[ 552.498000] [<e0c943f0>] __bb11f9+0x774/0xbd8 [dvb]
[ 552.499000] [<804271d4>] do_fb_ioctl+0xc0/0x6ac
[ 552.499000] [<801513c0>] do_vfs_ioctl+0x420/0x838
[ 552.499000] [<8015182c>] SyS_ioctl+0x54/0xb8
[ 552.499000] [<80014ef4>] syscall_common+0x34/0x58
[ 552.499000] Code: 97a200e0 97a300c8 0043001b <006001f4> 00003812 2ce60010 50c00022 8e420000 00a4001b
[ 552.499000]
[ 552.499000] ---[ end trace 4442a84bdc2b8292 ]---
root@et10000:~#
Also hangs in 6.0.004, so that narrows it down a bit if anyone is interested....
[ 130.285000] Trap instruction in kernel code[#1]:
[ 130.285000] CPU: 1 PID: 827 Comm: enigma2 Tainted: GF O 4.10.6 #1
[ 130.285000] task: cef63380 task.stack: ceeac000
[ 130.285000] $ 0 : 00000000 10008b00 00000001 00000000
[ 130.285000] $ 4 : 00000035 00000023 00000000 00040000
[ 130.285000] $ 8 : 00008000 e14873e0 00000010 00000010
[ 130.285000] $12 : 00000000 00000000 00000000 7476778c
[ 130.285000] $16 : cf0d8a5c cf0d8b68 00702ca0 0000003e
[ 130.285000] $20 : e0d70000 e0d70000 e0d70000 e0c90000
[ 130.285000] $24 : 00000000 800716a0
[ 130.285000] $28 : ceeac000 ceead528 e0d90000 e0c942e0
[ 130.285000] Hi : 00000001
[ 130.285000] Lo : 00000003
[ 130.286000] epc : e0c943f0 __bb11f9+0x774/0xbd8 [dvb]
[ 130.286000] ra : e0c942e0 __bb11f9+0x664/0xbd8 [dvb]
[ 130.286000] Status: 10008b03 KERNEL EXL IE
[ 130.286000] Cause : 00800034 (ExcCode 0d)
[ 130.286000] PrId : 00025a11 (Broadcom BMIPS5000)
[ 130.286000] Modules linked in: ipv6 enigma(FO) xfs(F) libcrc32c(F) dvb(FO) modloader2(FO) modloader(FO) tpm(FO)
[ 130.286000] Process enigma2 (pid: 827, threadinfo=ceeac000, task=cef63380, tls=7476f8d0)
[ 130.286000] Stack : cf009ef4 e0f8a990 287e4b4f 00000000 00000f00 0000000b ceead56c ceead568
[ 130.286000] 850d1000 00702ba8 00000040 e25cd964 87b20224 00000000 07ff0000 00000013
[ 130.286000] 00000013 04380780 0000000c 00001e00 850d1000 86381d80 00000000 00000000
[ 130.286000] 00000000 00000000 00000000 00000000 ce44a100 00000000 038703f6 00350001
[ 130.286000] 00000001 00000001 00000000 00000000 00000000 00000000 00000000 00000000
[ 130.286000] ...
[ 130.286000] Call Trace:
[ 130.287000] [<e0c943f0>] __bb11f9+0x774/0xbd8 [dvb]
[ 130.288000] [<804271d4>] do_fb_ioctl+0xc0/0x6ac
[ 130.288000] [<801513c0>] do_vfs_ioctl+0x420/0x838
[ 130.288000] [<8015182c>] SyS_ioctl+0x54/0xb8
[ 130.288000] [<80014ef4>] syscall_common+0x34/0x58
[ 130.288000] Code: 97a200e0 97a300c8 0043001b <006001f4> 00003812 2ce60010 50c00022 8e420000 00a4001b
[ 130.288000]
[ 130.288000] ---[ end trace 43ad70d04e6c7b82 ]---
root@et10000:~#
(I removed a wifi dongle earlier as it showed up in the first dmesg I'd posted.)
Are there some images in that skin the drivers can't handle?
Are there some images in that skin the drivers can't handle?
What has changed in the skin between 6.0.003 which works without problems and the same skin in later versions of 6.0.00x? I don't believe there are new drivers for an older Xtrend ET10K box.
What has changed in the skin between 6.0.003 which works without problems and the same skin in later versions of 6.0.00x? I don't believe there are new drivers for an older Xtrend ET10K box.Have you loaded the ViX-1080-Common skin from 003 into your 006 image?
Have you loaded the ViX-1080-Common skin from 003 into your 006 image?
What is the Vix_1080_Common skin?
All I did was a software update from 6.0.003 to 6.0.006 and almost immediately found the small text problem (in only one menu) and then having put my box into deep standby and switching it back on the next day finding that the box hung with a live TV picture but with the info bar stuck on the screen and the remote being ignored by the box. A reboot solved the freeze problem but after another night in deep standby the box froze again at switch on.
As I cannot have the box hanging coming out of deep standby to, say, perform a recording I've reverted back to 6.0.003 which is has again been working as it was previously.
What is the Vix_1080_Common skin?It is the part of the skin that is shared by ViX-Day and ViX-Night.
@ccs, can you load skins load ViX-Night-1080 and ViX-1080-common from 003 and see if you still have the problem. Just retrieve them complete from your 003 image.
003 has ViX-Night-HD and ViX-Common, do you want me to copy their contents to ViX-Night-1080 and ViX-1080-Common (in 006)?
003 has ViX-Night-HD and ViX-Common, do you want me to copy their contents to ViX-Night-1080 and ViX-1080-Common (in 006)?
That's what I've done, and so far so good, even coming out of deep standby is ok.
And make sure the old ViX-Night and ViX-Common folders are not present.
@adm, switch to ViX-Night-HD as that is what you were using in 003. Download from the feeds. Please report back.
@adm, switch to ViX-Night-HD as that is what you were using in 003. Download from the feeds. Please report back.
On 6.0.003 I installed and changed to the simple_ten_eighty skin. I then uninstalled all other skins except the default.
Via the image manager I downloaded 6.0.006 and flashed the same – restored settings from .003. From the plug-in menu downloaded the skin and changed to it.
The small text in the first post has gone – its now “normal size”.
Any lock-up/freeze may not be seen until I have put the box into standby for a number of hours.
Fingers crossed its working – thank you.
Rob van der Does
17-01-22, 13:51
Xtrend ET10000, SkinVix-Night-1080
I have my box configured that when I press the EPG button on my remote I first get a screen where I can first select the bouquet.
Configuration:
Open the epg grid screen and press menu on the remote and in the configuration menu that appears - select “Show bouquet on launch = yes”
I’ve just performed a software upgrade from 6.0.003 to 6.0.006
In 6.0.003 the text to select the bouquet was a “normal” size
In 6.0.006 the text size has shrunk to barely readable.
63195
All other menu screens seem to have the same text size as set in 6.0.003.
Thanks for reporting: will be fixed in next update.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.