What's new
By:
Filters

SkyQ Skin

mrben333 said:
hi could someone advise me please i have mesed up my zgemma - i flashed wooshman build again came on ok then when i restored settings it reboots and gives me the open atv screens - is there a way to pick which setting restore to choose from as i have restored settings before and everything was ok with the slyk skin on-- thanks
Click to expand...
The skin will not bootloop your box. There must be something else. What settings are you trying to restore??

Sent from my GT-I9505 using Tapatalk
 
Just trying to restore my previous setting that worked fine with the slyk skin I tried putting q skin on the box but it was crashing after viewing a recording slyk skin was fine
 
mrben333 said:
Just trying to restore my previous setting that worked fine with the slyk skin I tried putting q skin on the box but it was crashing after viewing a recording slyk skin was fine
Click to expand...
I will have a look at the timeshift and pvr codings later so I would advice to use Slyk HD untill that problem is sorted.

Sent from my GT-I9505 using Tapatalk
 
Ok thanks will do q skin was great I could do everything as normal until I watched a recording then when I exit out of the recording and switch viewing channel that's when the box crashes and reboots
 
Morning all. Is there a way to have the line on the EPG that shows whereabouts you are with regards to the current time?


Sent from my iPhone using Tapatalk
 
This might be relevant to a few problems on this thread.
There is currently a bug doing the rounds on VIX, that is crashing timeshift if it has a progress bar. It may be effecting other screens that have a progress bar too.
This can be fixed by copying over openatv progress.py to your box. (This will supposedly be fixed in the next vix release)

View attachment Progress.zip

copy it to /usr/lib/enigma2/python/Components/Renderer and reboot your box.

** edit **
a py file is an uncompiled python file. When you reboot your box, it will be compiled and change to a pyo file. This will overwrite your existing Progress.pyo.
you can either delete the existing pyo file before rebooting or let it just overwrite it.
 
Last edited:
kiddac said:
This might be relevant to a few problems on this thread.
copying over openatv progress.py to your box. (This will supposedly be fixed in the next vix release)

copy it to /usr/lib/enigma2/python/Components/Renderer and reboot your box.
Click to expand...

I only have a file named Progress.pyo (Note capital & extension) can I simply change the file .ext?
 
Window said:
kiddac said:
This might be relevant to a few problems on this thread.
copying over openatv progress.py to your box. (This will supposedly be fixed in the next vix release)

copy it to /usr/lib/enigma2/python/Components/Renderer and reboot your box.
Click to expand...

I only have a file named Progress.pyo (Note capital & extension) can I simply change the file .ext?
Click to expand...
No you cant. Just delete the .pyo and ftp the .py file. After reboot enigma 2 will read the .py file and compile it to .pyo

Sent from my GT-I9505 using Tapatalk
 
great work

Hey Chabs
Thanks for your hard work, skin looks great. Not explored fully yet. Just one thing so far, when in epg some pages look crisp and HD then others the text look a little blurry. Just me??

Joe
 
Can you upload a crash log ftp home/root/logs and upload the latest one here zip it choose go advanced reply then you will see a paper clip click that and upload your log.

I'm no good with crash logs but someone maybe able to understand it
 
I've just repplicated - It's when you exit a recording and then press channel up.

Here is the relevant crash log entries

12:03:00.564 < > dvb/decoder.cpp:722 stop DEMUX_STOP - pcr - ok
12:03:00.564 < > dvb/decoder.cpp:424 stop DEMUX_STOP - video - ok
12:03:00.564 < > dvb/decoder.cpp:433 stop VIDEO_STOP - ok
12:03:00.566 < > dvb/decoder.cpp:158 stop AUDIO_STOP - ok
12:03:00.598 < > dvb/decoder.cpp:166 stop DEMUX_STOP - audio - ok
12:03:00.599 < > dvb/decoder.cpp:202 unfreeze AUDIO_CONTINUE - ok
12:03:00.599 < > dvb/decoder.cpp:799 stop DEMUX_STOP - ttx - ok
12:03:00.606 [ ] dvb/dvb.cpp:1278 DVBChannelStateChanged start release channel timer
12:03:00.608 { E } Components/config.py:1922 getResolvedKey getResolvedKey config.usage.remote_fallback failed !! (Typo??)
12:03:00.640 gui/ewidget.cpp:337 recalcClipRegionsWhenVisible gui/ewidget.cpp:337 ASSERTION t FAILED!

---------- Post Merged at 12:09 PM ----------

Looks like this has been gone over before in the thread - Chabs claims Vix and ATV are at fault, yet this only seems to happen running the SkyQ skin

---------- Post Merged at 12:52 PM ----------

The error relates to ewidget.cpp and something to do with redrawing the screen - Here is the section of ewidget.cpp that is causing the issue

Code: 
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]void eWidget::recalcClipRegionsWhenVisible()
[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]{[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]    eWidget *t = this;[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]    do[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]    {[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        if (!(t->m_vis & wVisShow))[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]            break;[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        if (t->m_desktop)[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        {[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]            t->m_desktop->recalcClipRegions(t);[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]            break;[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        }[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        t = t->m_parent;[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]        ASSERT(t);[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]    } while(1);[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
}

But it's obviously pulling information from the skin - I think someone will have to look at the differences between 1.4 and 1.5 to drive out the problem
 
ok so been navigating around my box with sky q skin most of the day now. looks great and nice to have a fresh look. Its been crashing when coming out of a plugin or when trying to exit right back out of settings and then i got a crash after playing about with timeshift. (ff and rw at diff speeds). then once my box has rebooted i have zero sky channels just fta so then have to do a restart and they all come back. So i think there are some glitches with it, but a work in progress i guess. good work so far
 
Chabs, I've indentified where the problem is in your skin.xml file that's causing the crash for users when they exit playback of recording. I don't know if there are more problems lurking as the line is question is similarly repeated a few times in the XML file. Anyway two things
1) I've got a working skin.xml if anyone wants to test it for SkyQ v1.5 - You can download it from my dropbox at the link below and replace the skin.xml in the SkyQ folder (perhaps people can feedback if they have any other crashes and what they were doing at the time)
2) It maybe something to do with one of the renderers you are using, but saying that, these seem to be consistent between 1.4 and 1.5 so maybe not.

Working skin.xml file can be found here: https://www.dropbox.com/s/whlnqkx887twloy/skin.xml?dl=0
 
You must log in or register to reply here.
Back
Top