Installing ATV

[dumbthumbs]

I decided today to try to install ATV. I really want to be able to access more streaming services via Kodi.

I downloaded the latest nightly build from http://images.mynonpublic.com/openatv/c ... beyonwizv2

The downloaded file is openatv-6.4-beyonwizv2-20200522_recovery_emmc.zip.

I unzipped it into my USB drive and booted to update. I selected the recovery image from the menu. It downloads the image and does the recovery step. Then it goes to reboot. It just sits at boot on the display with the OPEN ATV banner on my screen and nothing.

If I choose the Multiboot selector option from the boot menu after flashing, it says "no image founded".

Am I missing something? I have rebooted and even re loaded the recovery image several times from two different USB drives on both of the USB ports on my V2. Same result. No errors, but it does not boot.

[MrQuade]

No, your not missing anything.

Unfortunately OpenATV is currently broken on all devices with the same chipset as the V2.

I believe it is the same with the current OpenVix release too.

I'm not sure what the status is for a fix. And I'm not sure at the moment of there is an older build available that you can download that will work.

[dumbthumbs]

Damn. Seems to be the story of my life.

Thanks for the quick reply. To save me from going through the motions. Should the latest Beyonwiz build restore back onto the devices OK? I backed up the config to my laptop fortunately, so if I can flash it back, I can put it to where it was until I can get a working OpenATV build.

[MrQuade]

Yep, you can safely and easily flash back to the wiz firmware.

You can then restore your settings backup and all will be back to how it was before (barring any plugins you may have installed). If you bit up for the first time with your original harddrive plugged in and the settings backup is still there, then you will be automatically asked if you want to restore your old settings.

I'll have a poker around to see if I can find a working openatv image. I usually only look in the nightly builds, bit they're just be an older stable build somewhere, even if I just pull an old one from my downloads folder .

[dumbthumbs]

Thanks Mr Quade.

I've restored it. I'll wait until the builds work again and have another bash.

Cheers

Mark

[dumbthumbs]

UPDATE: Just tried 20200527 and 20200530 builds. Still no go.

[MrQuade]

UPDATE: Just tried 20200527 and 20200530 builds. Still no go.

Thanks for checking. I had an idle thought to just try the latest image today to see if there was any change, but didn't get round to it. It might be more productive for me to try to get in close contact with the actual openatv community instead.

I do have an old image that should work if you are really keen for it.

[dumbthumbs]

Thank you. My end goal is to get Kodi 18 so I can use more streaming services, but I do have a Chromecast, so I can persevere. I'll download the latest. One would hope that if they are putting up new Beyonwiz V2 firmwares, at some point someone should be testing them.

[dumbthumbs]

OK. Latest update. I downloaded the latest build today which is today's build.

The loader is different now. It shows a dialogue with upload progress and flash progress. It downloads only as far as 87% then does the burn phase, then downloads the last 13% and burns this. This indicates to me that perhaps there may not be enough RAM to contain the later images. The upload completes fine, but when it reboots, it just gets stuck at the OPENATV splash screen with boot on the display and never goes further (same as before). Thinking that it can't read the image from flash just like it couldn't accept it from USB.

It also appears that whomever is uploading these images is clearly not testing them and has not for some time.

[MrQuade]

The loader is different now. It shows a dialogue with upload progress and flash progress. It downloads only as far as 87% then does the burn phase, then downloads the last 13% and burns this. This indicates to me that perhaps there may not be enough RAM to contain the later images.

That's quite normal behaviour. You also see this happen when you do an online image update.

t also appears that whomever is uploading these images is clearly not testing them and has not for some time.

No, they are aware they don't work. The V2 is one of many dozens of models they support or partially support. It just happens that the chipset that the V2 uses is not compatible with the new type of file structure they have switched over to using recently.

It is possible to get it to work in a multiboot setup according to prl, bit I haven't attempted that myself yet.

[Grumpy_Geoff]

one of many students of models

the Nigeria that user the cost that the V2 users are not compatible

Trevor, Trevor, is that you?

[dumbthumbs]

OK. I have it working!

For the benefit of anyone else who would like to do this.

It seems the issue is that the flash will not accept the ATV firmware. I suspect it may not have enough space. This is how I got it working.
Downloaded both recovery and update firmwares from the repository.
Extracted the recovery files to the boot of the USB and copied the update zip file.
I plugged a micro SD card into the slot. I only had a 32Gig card, but I suspect it could be much smaller.
Booted up with the OpenATV recovery files on the USB as normal and did a recovery. This installs the new boot environment, but not the firmware. I then booted to update and selected the SD card partition to partition and format my SD card.
Back to the main menu and chose (working from memory now) update to multiboot.
Selected the firmware (it's the only one on the stick), changed the destination to slot 5 (SDCARD) and ran the update.
Voila! It was now showing as up to date.
Back to main menu. Verify that the multiboot is selected on slot 5.
Unplugged USB, rebooted and setup the system.
All recordings were intact.
Added Kodi plugin. I found some new services, but now I have to see if there is a Netflix plugin for Kodi 18.7.

[MrQuade]

Trevor, Trevor, is that you?

Tapped that out inn the neck of a taxi after a week in site. Autocorrect checking was low priority

[Gully]

Tapped that out inn the neck of a taxi after a week in site. Autocorrect checking was low priority

Yeah not much space when you are in the neck.

[MrQuade]

Ungh. Going to bed!

[MrQuade]

Added Kodi plugin. I found some new services, but now I have to see if there is a Netflix plugin for Kodi 18.7.

I am still loathe to set my SD card up for boot images, so am still stuck on this.
Compounded by the fact that my OpenATV box is my pre-production Wiz that needs modified images in order to be hardware compatible.

However, while I was perusing previous threads I saw this.
The OpenATV image does have its own dedicated Netflix plugin that actually works! Though I haven't used it in the long term, you may find that it is easier to use than a Kodi plugin.

[MrQuade]

I finally got off my arse and registered on the OpenATV forums.

I jumped on an existing thread regarding the failure to boot from eMMC.

After a little bit of prodding, we now have a functioning OpenATV recovery image for the V2 again

It has gotten a version bump from 6.4 to 6.5, whatever that signifies.

From the speed of the fix, I expect there was something from the Octagon firmware that was fixed months ago that never made it into the Beyonwiz recovery.

Anyway, happy days, OpenATV is now running on my second V2 again .

Now I can look into potentially multibooting without needing to use the SD card .

[IanSav]

Hi MrQuade,

It has gotten a version bump from 6.4 to 6.5, whatever that signifies.

6.5 is OpenATV's development branch for Enigma2 using Python 3.

Regards,
Ian.

[MrQuade]

6.5 is OpenATV's development branch for Enigma2 using Python 3.

Neat thanks!

[MrQuade]

6.5 is OpenATV's development branch for Enigma2 using Python 3.

Dang, looks like they are still ironing out bugs too. From my limited reading it looks like they are still working on plugin compatibility in 6.5.

I immediately found that Kodi and Netflix were broken so braved the other parts of the OpenATV forums.

[prl]

See viewtopic.php?f=47&t=14150&p=188260#p188260

[prl]

When I try to shut down in 6.5.20200714, it hangs.

[MrQuade]

When I try to shut down in 6.5.20200714, it hangs.

Deep standby on my unit appears to be working. Accessed via long-POWER->"Deep Standby".

I'm using my pre-release unit, connected to Ethernet and AV composite.

[prl]

When I try to shut down in 6.5.20200714, it hangs.

Looks like the threading system is getting deadlocked at shutdown:

Code: Select all

File: "/usr/lib/python3.8/site-packages/twisted/internet/base.py", line 1064, in _stopThreadPool
  self.threadpool.stop()
File: "/usr/lib/python3.8/site-packages/twisted/python/threadpool.py", line 280, in stop
  thread.join()
File: "/usr/lib/python3.8/threading.py", line 1011, in join
  self._wait_for_tstate_lock()
File: "/usr/lib/python3.8/threading.py", line 1027, in _wait_for_tstate_lock
  elif lock.acquire(block, timeout):

[MrQuade]

My newer 6.5 thread at OpenATV was moved to the 6.5 forum which is probably good for visibility.

I haven't seen anything listed in the forum guidelines, but should I be trying to post in German, or do they tolerate filthy uni-linguists posting in English? I was content posting in English in the Beywonwiz area, but not so much out in the general population.

Google translate is doing its job, and I get a mostly readable presentation of the forum, but I am conscious of my posts maybe being out of place.

It's also hard to tell if I should be posting random stuff like the OpenWebIf terminal feature not working, and the timezone region not being configurable in the initial setup wizard.

[prl]

I've managed to flash the non-recovery V2 ATV 6.5.20200714 image to microSD using SB Multiboot Image Upgrade in the boot menu.

It runs fine, but enigma2 still hangs on its shutdown (i.e. even on GUI restart), though.

[prl]

I haven't seen anything listed in the forum guidelines, but should I be trying to post in German, or do they tolerate filthy uni-linguists posting in English? I was content posting in English in the Beywonwiz area, but not so much out in the general population.

When I worked in Zurich, some Swiss preferred to talk to me in English rather than in German (because I couldn't do much Swiss German), even when my German was fairly good. I worked with people who had Swiss German, German, Italian and Spanish as their first languages.

I've only ever written English on the European enigma2 forums, though I haven't posted there much anyway. The enigma2 community is pretty multilingual, anyway, so to some, German may in fact be harder than English.

Google translate is doing its job, and I get a mostly readable presentation of the forum, but I am conscious of my posts maybe being out of place.

From what I've read of Google translate output, it seems to manage fairly well. People will be tolerant, generally, anyway, whether you post in Google translated German or in English. Google probably does a better job of declension than I would - I never really got the hang of declining German adjectives, and I'm now pretty rusty on which case a lot of prepositions take.

I tend to write in German in private conversations with Captain, because it seems to work better that way, even with my German being pretty rusty now.

[prl]

in private conversations with Captain

Speaking of which, Captain has replied elsewhere saying that he saw my recent posts about the issues I mentioned with V2 ATV 6.5.20200714.

[IanSav]

Hi MrQuade,

I haven't seen anything listed in the forum guidelines, but should I be trying to post in German, or do they tolerate filthy uni-linguists posting in English? I was content posting in English in the Beywonwiz area, but not so much out in the general population.

Google translate is doing its job, and I get a mostly readable presentation of the forum, but I am conscious of my posts maybe being out of place.

Captain and Nick are pretty good with their English. Many others prefer to only communicate in German. I mostly communicate with OpenATV via private developer chat rooms rather than the forums.

In my recent discussions with Captain he indicated that he is not very sure of his English, even though I think he does a great job, he did indicate that he finds my discussions easier to follow because of my usually verbose (longer) posts where he can pick up the thoughts and intentions via the extra words and explanations. May I suggest that you adopt a simple English style, don't use slang or Aussie talk , and provide longer and easy to follow posts and you should be fine. I would stick to the English part of the forum but just follow Captain's lead of where he choses to move and respond to posts.

If you can't get a point across then let Prl or I know and we can try to help. (Prl, I hope you don't mind me dobbing you in. )

It's also hard to tell if I should be posting random stuff like the OpenWebIf terminal feature not working, and the timezone region not being configurable in the initial setup wizard.

You should tell me about the time zone problems as I wrote the previous code and I am reworking that code right now. I had a working version of the code but some trauma regarding the geolocation feature caused the code to be modified and broken. What is wrong with the time zone for you?

I have redesigned my code to avoid all the GDPR issues and will be implementing the new version soon. The new code should allow you to press the YELLOW button while in the time setting screen and a geolocation lookup should automatically set your time zone to a hopefully correct value.

I would post all issues regarding OpenWebif to the OpenWebif repository issues area. It is here.

Regards,
Ian.

[MrQuade]

You should tell me about the time zone problems as I wrote the previous code and I am reworking that code right now. I had a working version of the code but some trauma regarding the geolocation feature caused the code to be modified and broken. What is wrong with the time zone for you?

The time zone settings work fine once you are up and running.

The problem is only in the initial setup wizard. You are asked to set a timezone, but are only offered European options. There is no way to select your timezone region (ie. Australia).

[IanSav]

Hi MrQuade,

I can reproduce the problem. This is an issue in the wizard code. I am rewriting that code as well but it is far from ready. I will see if I can change the current code to address the problem.

Regards,
Ian.

[IanSav]

Hi MrQuade,

Problem fixed. I will commit the fix now and should go in when Captain wakes up.

Regards,
Ian.

[prl]

If you can't get a point across then let Prl or I know and we can try to help. (Prl, I hope you don't mind me dobbing you in. )

Happy to help

[IanSav]

Hi MrQuade,

Time zone fix is merged and should be in the next build.

Regards,
Ian.

[prl]

The problem is only in the initial setup wizard. You are asked to set a timezone, but are only offered European options. There is no way to select your timezone region (ie. Australia).

What you're offered seems to depend on your initial state. When I started V2 ATV 6.5.20200714 from an oldish 6.4 settings backup, it initially selected Berlin time, and when I looked in the Time settings screen, it showed Australia as the country, but Berlin as the region, however, when I scrolled through the regions, it showed the correct Australian ones.

I think that Ian has fixed that, too.

[MrQuade]

If you can't get a point across then let Prl or I know and we can try to help. (Prl, I hope you don't mind me dobbing you in. )

Happy to help

Hehehe, I think my only issue so far was convincing Captain that there was an actual problem! Message got through in the end though

I'd been assuming all these months that the inability to boot from eMMC was a known problem with all PVRs on this chipset, and that the problem had not been solved.

prl's comments about his conversations with Tony gave me the impression it was being worked on. Too many assumptions by me!

I probably shouldn't have been so timid in my earlier replies to Captain on the Wiz forums.

[MrQuade]

What you're offered seems to depend on your initial state. When I started V2 ATV 6.5.20200714 from an oldish 6.4 settings backup, it initially selected Berlin time, and when I looked in the Time settings screen, it showed Australia as the country, but Berlin as the region, however, when I scrolled through the regions, it showed the correct Australian ones.

I think that Ian has fixed that, too.

I did notice that my restored settings had defaulted to Berlin as well. I'd just chalked that up to an inter-version settings re organisation.

Good to hear!

Time zone fix is merged and should be in the next build.

Excellent!

[prl]

Hehehe, I think my only issue so far was convincing Captain that there was an actual problem! Message got through in the end though

I'd been assuming all these months that the inability to boot from eMMC was a known problem with all PVRs on this chipset, and that the problem had not been solved.

prl's comments about his conversations with Tony gave me the impression it was being worked on. Too many assumptions by me!

I probably shouldn't have been so timid in my earlier replies to Captain on the Wiz forums.

I don't think that you're too far off about multiboot. As soon as I found the problem with V2 ATV not booting from microSD, I told Captain about it (with a serial debug log). That now seems to have been fixed.

The problem with 6.5.20200714 crashing in a couple of the multiboot management screens in ATV is a one-liner to fix (a two-liner if it's also to be backward-compatible with Python2).

There's still an issue that I haven't been able to test in 20200714 because of that crash: whenever I used Online Flash in ATV Setup it would write to the first flash partition, no matter which one I asked it to flash to.

I'm not sure how hard the hang on shutting enigma2 down is, but I don't think that it's related to multiboot.

What I'd really like is to be able to have multiboot in the Beyonwiz image. Then I'd feel free to be able to repartition the flash to give me more multiboots and not have to futz about with the /boot files whenever I have to reinstall the Beyonwiz image from USB (whenever I do that, ViX enigma2 keeps crashing on startup until I fix up /boot

Maybe in 20.3...

[MrQuade]

Geez, they're not bad.

The latest recovery (18072020) has fixed Kodi, Netflix and the OPenWebIf terminal. I also assume that IanSav's date fix was included too (didn't run through the wizard, just restored settings).

Seems the box is working nicely now!

[IanSav]

Hi MrQuade,

There is a lot of work going on in the background to fix as many issues as quickly as possible. Things are cropping up everywhere. As we change code we find cases where this were not done well and these are all being sorted out as well. The automated Python 2 to 3 conversions also seem to be creating a number of issues as well.

The full new implementation of my new time zone setting code is not yet in any public code. It is still being tested internally. When the new Setup code is made public then I will arrange for it to go into all images and then I can add the new time zone code. (It is all tested on my test machines and seems ready to go.) This will also be the start os a significant number of other code refactors and improvements. Recordings.py and Timeshift.py are already done and will also be released soon.

Regards,
Ian.

[MrQuade]

If anyone has installed the 18072020 image, you may want to stay on that one for now.

Just keeping an eye on each of the alpha builds, and both Kodi and Netflix have broken again in 19072020. No subsequent images have been built yet.

The silver lining on the Kodi breakage is that it looks like they are upgrading Kodi to v19 to take advantage of the Kodi project's move to Python 3 as well. That will make things *very* up to date!

Not sure why Netflix broke again though. Maybe an unrelated knockon effect?

[Dazzla_1]

G/day could somone advise me if ATV and all the other will install on a U4 thanks Dazzla_1

[MrQuade]

G/day could somone advise me if ATV and all the other will install on a U4 thanks Dazzla_1

There is an image available for it on the OpenATV site, but I have never tried it myself. I don't know of a reason why it wouldn't work since the U4 hardware will be similar to other supported PVRs.

I don't believe that the OpenATV firmware alone will allow you to run Kodi or Netflix though if that's what you are after.

You will have access to more skins and potentially a wider range of supported plugins for other services though.

What is it you are looking for? Or just a change?

[Dazzla_1]

Thanks Mr Quade it's all good' I was just curious re plugins and stuff, I will not venture there yet I have Google Chromcast that came in a package with Netflix, trouble is Netflix is only Australian content and it seems all the good programs are all dubbed there is the occasional good series or movie, luckly my wife enjoys the European program's so we have enough for now,
"thank's for your helpMr Quade, regards Dazzler_1