Posts by KiddaC

To be honest I never tested grouped categories.

I will have a look now.

But I had a similar issue with non grouped files ending up massive files because of an error in the code.

So i probably got the same issue with grouped.

This sorting bouquets at top lark is actually very difficult. I did actually hide that option ages ago, because of problems, I must have accidently shown it again in some release. Now people want that option again, which was the whole point of doing this release :(

Regarding version numbers... no idea.

Regarding catchup - catchup has always worked hasn't it?

This is jedi, not xstreamity

i changed the about us page?

self.credit = 'JediMakerXtream V6.09 (C) 2018/2019/2020 - KiddaC\n\n'

Jedi Maker Xtream V6.09

New File on post 1.

Fixed - position bouquets at top error ravstar

Removed &next_days=7 for shortlinks dsayers

Removed https xmltv address being changed to http. (now epg importer is working with the hack) dsayers

Reverted some of the settings pages code that was breaking dreambox. I knew those suggested amends on github were going to be trouble. seagen  michaelangelo

Changed the dependancy code to be less strict looking for python 3.8 folder.

OK test over.

My skins still work perfectly fine on pure2 with no crashes at all. All screens, all epgs, channel select etc.

Obviously FNC and pure2 only screens are not skinned and fallback to estuary with my sky font.

So carrspaints Things to check.

A usb drive will be required to save EPG data / timeshift data etc. Ideally turn off timeshift. It slows down your box.

EPG data needs to be set to save to external (especially if using IPTV - which most people are nowadays)

Also no harm in setting up a swap file on usb to help with memory load and also download and activate cacheflush.

If installing my skins, you need to install the shared component IPK first as found on all my skin threads. Then install the main skin file.

It shouldn't allow skin to be installed without the shared components anyway. Unless you uncompressed the ipk and manually copied it over.

In which case its going to crash when the infobar loads as its missing the custom components.

My job is done here. There doesn't seem to be a skin error, there doesn't seem to be pure2 error. (or there isn't on my vu zero 4k build)

We can all get back to what we were doing.

:29_002:

How to get out of your boot loop. Delete my skin folder /usr/share/enigma2/slyk-1080-r19

change skin back to estuary.
Fix any of the above things mentioned.
Re-install the slyk skin in the correct way via the IPK. Shared components, then the skin.

And if you still got issues, re-flash your box and try again. Because a correct setup, everything is working
And if you not to sure how to setup your box. I have an openatv guide here that can be used as reference for all oe-alliance builds including pure2. This is how I always setup my barebone builds. Just ignore the openatv install bit, and follow on from there.
OpenATV setup guide by KiddaC

Looking at the users crash log, personally I think he has ran out of memory/disk space until I can check further.

Maybe epg.dat is set to save internally and not external source.

Maybe user has no usb drive plugged in and therefore internal is being overwhelmed

Quote

not enough diskspace for timeshift! (less than 1GB)

<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!
<4>map_over_bad_blocks(): no more good blocks!

there isn't actually any skin error mentioned in that log.

Like you say Jensen, lots of UK users use either mine or chab's sky or virgin look skins.

I think I would have probably been informed by now if there was a massive crashing problem on a particular image.

But this conversation died as soon as my skin was noticed in the users log. It might not even be my skin that is the issue.

I don't know yet. We will see.

Well to get back on track about what this post was originally about, there is an issue somewhere with either my skins and compatibility with pure2 or there is an issue with the OP users setup on pure2.

I am off work today. So will have a quick play and report any observations where possible.

I am going to install the latest pure2 image for my vu zerok 4k today and see what peoples issues are with my skins and pure2 and see whether they are fixable my end.

gorski

Well thats the longest reply I have ever seen in my live.

No war here, just observations thats all.

Yes I offered to create you an alternative skin, I started, but your code seemed too embedded into estuary, so didn't have the time to look into it any further as like your team, I am a one man band doing a million things at once. I thought it would be a quick project it wasn't to be. Like you say, we are all very busy bees with various life and health issues. And I am aware from your previous posts how some of your team are now busy with other things in life.

They real question is though.. is your image built on the core of oa-alliance where existing plugins and skins work on it.

Or are you now just a splinter group doing your own separate thing. And I am not referring to all your great ideas for fnc plugins. Just talking generally.

You personally, constantly comment about dreambox being closed group and to quote you "NOT being open to the community can bite you in the arse..."

So basically all I am asking, is what direction is pure2 going. The dreambox way, or the oe-alliance community way.

Have a nice day, and keep up the good work ;)

seagen Just for clarity. This isn't my code. I just implemented a version of it into epgimporter.

The original https solution for twisted clients downloadpage function was by Athoik on the openpli forum (3 years ago). Credit were it's due.

If you haven't fixed this, give me a shout tomorrow evening and I will look into it for you.

Very strange you say this crashed during creating Jedi Bouquets. (unless your box ran out of memory)

I don't use wooshbuild but noticed lots of comments about bugs in it lately. So it could be a bug in that build also.

Your solution should be relatively simply.

Your box still loads, so you should be able to access it via ftp

Then it would just be a case of looking in the log files and seeing if the issue has been highlighted.

I did have a similar problem once for one of my friends on a zgemma h9s. Constant boot loop, no skin errors were being reported, nothing in the logs.

In the end I found out his bouquets files had got corrupted. This could well be the same problem you got if you say it crashed midway in making bouquets.

Deleting all bouquet files (not just jedi bouquets) brought the box back to life.

Then just a case of recreating the bouquets via autobouquet maker and jedi.

What is your skill level with enigma2?

Do you know your boxes ip address

Do you know how to ftp into your box

Has it got a telnet password set.

If you know what your doing,

just ftp into your box

First check your crash logs and see if it is reporting any obvious errors.

/home/root/logs/

Secondly if no errors you can try deleting all your bouquet files and rebooting your box.

/etc/enigma2/
delete all the files that have the extension .tv

@ kiddac in your response as I dont often notice posts in this section.

You can't. It's an android box.

Just like you can't install android on an enigma2 box (unless its purposely built as a hybrid)

When pure2 came out. It was interesting. It had fresh ideas.

Unfortuntalely I think you have gone the wrong way of late.

Making users have to use estuary skin is very draconion and preventing users from personalising there box. I even get bored of my own skins and use others now and again.

Just fobbing off any alternative oe-alliance skins is a bad way to work. Like you guys say, you dont use any other skins other than estuary, so you don't really care. I don't use pure2. But if I was informed why my skins have suddenly stopped working on your image I could probably fix it. But if you have made your image non oe-alliance compliant nowadays, then maybe I cant fix things.

I also think the way you have been speaking to people of late, especially noobs and people who are not clued up about these boxes or the various images, is also getting quite rude.

Just because you know, doesn't mean they know.

New file on post 1.

Fixed the hanging/crashing issue again.

Not bad for a throw-away plugin. Lasted nearly a year and half before it broke.

And only handful of tiny amends in the meantime.

I like plugins like that, write it, forget about it...unlike my jedi and xstreamity that need engraving on my grave stone. :zip it:

OK after hours of investigation I know why this program stopped working now.

Sky changed the behaviour of it's program listings json file.

If a program has no description they delete that field. Instead of keeping that shortDesc field as Null.

My plugin was looking for that field and the crash was happening in a thread so it wasn't being relayed back to the main screen or logs.

So for any one that used to use this plugin, I will finish updating it tomorrow. I have also now stripped out all the virgin and cable stuff too.

81fbfdf4d5b28.png

tbe  perfectium

What exactly is wrong with this plugin. I never use it myself.

Got some spare time tonight to have a look at it.

in your main epg settings, you need to save your epg.dat file to external media and not internal media.

Otherwise 1) your gonna run out of space, 2) you are probably going to lose it on a reboot.

It's been that long since I wrote Jedi I have forgot how it works :)

er...

28.2e txt file is a sub list of the rytec UK files. (sat only ,no cable). This gets cleared and updated everytime from the rytec source everytime you run bouquet creation.

The alias.txt file cross references the 28.2e file to get the id ref and service ref. This is then used to create the epgimporter files.

So to answer your question, this will only work on UK rytec, for UK bouquets.

There is no code for any other satellites.

It's not my fault my plugins are that good they get used worldwide. It was only ever meant to be for UK audience ;)

epg importer doesn't currently work with some https urls.

Here is hack I am currently working on

copy it over to

/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/

then reboot your gui