CoreELEC 21.0-Omega Amlogic-ne Discussion

Portisch · 6 April 2024 20:28

Amlogic-ne

Please use this thread for general CoreELEC 21.0-Omega Amlogic-ne discussion

Before posting an error please follow these troubleshooting steps.

Ter0n · 7 April 2024 02:12

Does this version has player led fix ?

Is it only works with NG version ?

fr24 · 8 April 2024 23:52

black screen same as in this thread

m-sundman · 8 April 2024 15:21

I set the update channel to Omega. Now the available versions list shows:

21.0-Omeg
21.0-Omega-rc2
21.0-Omega-rc1
21.0-Omega-beta3
21.0-Omega-beta2
…

If I choose the top one it installs some alpha version instead. Maybe related to the fact it says “Omeg” instead of “Omega” there? Is there some workaround without doing a reinstall?

(If it matters, I’m using Amlogic-ne.aarch64)

m-sundman · 8 April 2024 15:23

Selecting this one works just fine. It’s just the top one (“21.0-Omeg”) that doesn’t work.

PurplePlayer · 8 April 2024 20:09

I was able to manually update it by doing a wget against the github link of the generic Amlogic-ng tarball, for what it’s worth. Then sticking it in /storage/.update (more specifically running wget within that directory).

Portisch · 9 April 2024 06:23

It looks like the name Omega did trigger a Python bug.
There is a split(‘.tar’) to remove the file ending but it looks like it remove the ending a as well.

Not sure yet how to solve it…

MauriceW67 · 9 April 2024 06:46

Do the NE builds have the fixes for “true tv-led” Dolby Vision incorporated yet that are already present in the NG builds?

ast261 · 9 April 2024 07:36

Same problem for me.
Unfortunately, coreelec didnt boot after update.

m-sundman · 9 April 2024 11:29

Maybe I could help. Did you find the problematic place in the source code? I tried to find it, but couldn’t.

m-sundman · 9 April 2024 11:31

Now the available versions list shows:

21.0-Omeg
21.0-Omeg
21.0-Omega-rc2
21.0-Omega-rc1
21.0-Omega-beta3
21.0-Omega-beta2
…

Did anyone confirm if either one of those “21.0-Omeg” works?

Portisch · 9 April 2024 11:38

As written like here coreelec:updates [CoreELEC Wiki] it’s not possible to update by this method and will never be.

m-sundman · 9 April 2024 11:50

Oh, it’s this one, right?

github.com

CoreELEC/service.coreelec.settings/blob/7e0bf1901978837f14ac0d3b231824d87884c81f/src/resources/lib/modules/updates.py#L535


      
          build = None
          if not self.update_json is None:
              if channel != '':
                  if channel in self.update_json:
                      regex = re.compile(self.update_json[channel]['prettyname_regex'])
                      if self.oe.ARCHITECTURE in self.update_json[channel]['project']:
                          tagstrip = []
                          for i in sorted(self.update_json[channel]['project'][self.oe.ARCHITECTURE]['releases'], key=int, reverse=True):
                              if shortname is None:
                                  tagname = regex.findall(self.update_json[channel]['project'][self.oe.ARCHITECTURE]['releases'][i]['file']['name'])[0]
                                  if tagname != tagname.strip('.tar'):
                                      tagstrip.append(tagname.strip('.tar'))
                                  update_files.append(tagname)
                              else:
                                  build = self.update_json[channel]['project'][self.oe.ARCHITECTURE]['releases'][i]['file']['name']
                                  if build.startswith(shortname + '/'):
                                      break
          
                          for tag in tagstrip:
                              update_files = [i for i in update_files if i != tag]
                              self.oe.dbg_log('updates::get_available_builds', 'removed tag name "%s" from list' % (tag))

It’s not a bug in python. You’re using strip() incorrectly. The str.strip(chars) function strips away all characters in chars from the start and end of str. That’s not what you want to do there. Instead you want to remove the ‘.tar’ suffix if it exists, right?

The code should look like:

    if tagname.endswith('.tar'):
        tagstrip.append(tagname[:-4])

vpeter · 9 April 2024 11:53

You are already looking a solution to the problem.

Portisch · 9 April 2024 11:59

The “bug” was added by edit4ever committed on Dec 5, 2018 . So all releases with this changes till 21.0-Omega are affected.

m-sundman · 9 April 2024 12:03

As a workaround you could make a release named something like 21.0-Omega-hotfix, because that ends with ‘x’ which is none of ‘.’, ‘t’, ‘a’, or ‘r’.
Or 21.0-Omega-final. Or 21.0-Omega!.

Portisch · 9 April 2024 12:07

No, it’s not recommended to perform a “update” against major release versions anyway. A clean fresh install and by restore a backup is preferred.

vpeter · 9 April 2024 12:10

You should look more carefully code around and not just one line. And also code before changes and also whole update mechanism to understand. But this would took more than 2 minutes!

But thanks for suggestion.

No more discussion is needed.

m-sundman · 9 April 2024 12:19

I replied to Portisch’s message saying there’s a python bug related to “a split(‘.tar’) to remove the file ending” (which should’ve said strip instead of split, but whatever). I pointed out that it wasn’t a python bug, but a bug in the CE code, where the programmer had thought the strip function worked differently than it does. And I provided code that works like the programmer clearly had intended. At no point did I comment on the surrounding code, or the general methods used etc.

What 2 minutes? What are you talking about? Who said anything about 2 minutes?

Are you referring to the 2 minutes it might take for someone to add the version number to the update dialog text? If so, that’s a completely different issue (in a different topic in a different forum category), as has been made exceedingly clear.

vpeter · 9 April 2024 12:26

You commented code above which works exactly like it should.

And yes, it is not a bug in python but at time of writing it was not clear what is going on.

Now that all this issue is already resolved as best we could there is really no need to discuss this anymore or delete key will be in use