Posts by Poida

Quote from SSC_Jarod

What point could speak against to a install to internal on official AND community builds?

Most probably the risk of bricking your device during Internal install vs. no risk when installed to external memory

There are plenty out there that read all the warnings, go ahead anyhow, and then complain "this build bricked my device".

Thankfully, we don't seem to see them too often now (whether that is because most heed the warnings and run from external, or the installtointernal process is evolving, remains to be seen) but the risk is still there when installing to internal

Quote from Kick4U

I just updated after factory resetting from 8.2.1 and have noticed the link to 'Install from zip file' on the Add-ons homepage doesn't work.

That's an Estuary skin bug, not really a build issue.

BTW the other 2 ways to reach the Install from zip file link both work

1. Click settings (the cog) from the main home-screen

From there choose Add-ons (the open box)

The third option listed is what you want.

2. Click Add-ons from the tabs on the left side of the main home-screen

Click the open box icon at the top left and, once again

The third option listed is what you want.

Quote from blakey

but Multi CH PCM with that dtb is sizzling under original sound,

perhaps hissing would be a better description?

Quote from trohn_javolta

Are there news on whether we can update to adamg 's Leia build somehow?

You can, just like @kszaq's builds, but just take a breath for a minute, latest doesn't always = best

Quote from Fenderman

Would it feel "snappier"?

Haven't seen any noticeable improvement on any of my boxes

@kszaq Thanks for the confirmation

Quote from kostaman

The TX7 was using 8.2.2.2 whilst switched on overnight.

When i turned it back on , it found the new 8.2.2.3 image and proceeded to update.

So it looks like the update downloaded without a reboot or power off.

It looks more like the supply to the box was interrupted overnight and you didn't see the update notice.

Perhaps kszaq will let us know if any changes have been made that might result in this forced update?

Quote from snoopyjoe

it seems the LibreElec config addon is timing out trying to connect to the auto update server.

That rings true. Perhaps a longer time-out or multiple checks will be added eventually

Quote from snoopyjoe

it looks like the auto update may be suspended until the transition to the Leia builds are complete.

It looks that way, we'll just have to wait for now. Thanks for posting your findings

Quote from kostaman

Might be of interest to you and others.

Thanks for that glimmer of hope but no, the issue with auto-update remains exactly the same. (Must be harder to fix than it seems )

Quote from kostaman

I think this may be skin related.

It isn't skin related it is intro video related.

If I disable the intro video the update works fine with the same skin.

The reason you have had no issues is because you do not use the intro video.

Without changing skin, if I prevent the network from connecting until after the intro video has completed, the auto update works as expected.

OR

Again, without changing skin, if I go to LE settings and click on the auto setting this starts the update check again and the update works.

So nothing to do with the skin, most probably to do with the fact that the update check is timing out while the intro is playing.

Since we can't alter when the start-up video plays (it'd be a bit pointless playing any later than at start-up), the next simplest thing to do would be delay the update check but, as has already been mentioned that's a bit above my station and not on the list of priorities for kszaq.

I had a similar situation years ago with an original G-Box that didn't have a 'wait for network' option and always missed the time update. Not being a dev myself, it took me weeks of trial and error to come up with a start-up script that waited a few seconds to take eth0 down and up again but, sadly I deleted that years back.

I'll keep slugging away at it but if anyone can save my pain, I'd appreciate it. In the meantime, it's quicker for me to update the four boxes I have manually from one download than it is to wait for the auto-update to kick in so no real loss, it would just be nice to see the notification of a new update

EDIT

It makes no difference which skin is bein used, same result.

Intro enabled = no notification / update OR Intro disabled = notification / update works

Quote from Menion

What is "intro video"?

You would be aware of a start-up intro video playing at Kodi start-up if it were enabled, so I'd presume that's not your problem.

Quote from Menion

. . . if go in Libreelec settings, and I check for update, I get the notification popup . . .

When automatic updates in LE settings is set to auto, there is no option to check for updates available.

Are you sure yours is not set to manual ?

It seems that more work is needed for auto-update to function for all users

Quote from kszaq

Auto update is working since 8.2.1.2

Providing you have disabled intro video or you will not get the update notification unless you go to LE configuration and click on the auto-update setting which will then force a re-check for updates (sort of manual auto-update)

Quote from Daz

what do i have to do to boot back up to LE after the firmware update without having to do a clean install thanks.

Just reboot using toothpick (or dummy zip via android update) method.

Quote from bubblegum57

I didn't see anything on the screen.

OK. Different issue then

Quote from bubblegum57

I gave my box enough time to download, but it didn't update on next boot, so I updated it manually

When you box rebooted, did the update start and fail with a "Archive corrupt" notice (or something similar) ?

The updates can be r e a l l y s l o w sometimes. I've had the update finish downloading and trigger the second prompt in about 2 minutes (the last update). But this update, after forcing the first prompt to appear (by switching back and forth between auto and manual updating), the download had not completed after 12 minutes. On reboot I got the above failed attempt, due to incomplete file I guess

Quote from RayW

Poida why not just disable the intro video, far easier

Yeah I do realise that I could switch off the bits that don't work with the latest builds but we wouldn't have come this far if we'd all done that in the past eh? Thanks for the suggestion though.

I can't imagine it would be that difficult for a dev to fix but, not being one, it takes me forever to read up on the programming / script lingo, compare code that deals with similar issues and then hack it about until it does what I want.

I like the intro screen so I'll be keeping it. It's been an included option for ages so it just seems wrong to have to just disregard it.

No, I'll just update manually until a proper fix is found. After all, I've only had auto update work ONCE in the progression of LE for these boxes so I won't really be missing out

I'm confident kszaq will attend to it eventually

Has anyone else noticed that the auto update function doesn't seem to work with the intro video enabled?

For me, with it enabled, the update notification never appears. Once disabled, it works as expected.

@kszaq Does the auto update only check at kodi startup for updates and, if so, could the intro video playing be causing it to

"miss" the available update?

Could the check be delayed for a few seconds or maybe performed at intervals to overcome this issue?

If you need logs I will upload them but it's real easy to replicate. Just use a skin with the video intro option and, when enabled, the update notice will never appear (I'm using Aeon Nox Silvo, I will try some other skins to check it is not just this particular skin)

EDIT:

It looks like I just need to delay the network from initialising until after the intro (or reset it).

I'm sure there's something that could be added to autostart.sh . . .

Preventing the network establishing until after the intro video has finished does indeed allow the auto update to work as expected.

Sadly, it was sooooo long ago that I had to meddle with startup scripts and can't remember how to reset eth0 from there so, I guess it's auto-update OFF until someone clever sorts it out

Quote from mbake5

I get the notification that the update is available but not the notification that the download has completed.

I had that with one of the boxes so, after the first notice, I changed the auto setting to manual in the LE configuration settings and back again to auto. This seemed to start the whole process again with the update notification re-appearing and the download completed notification showed after about 2 minutes (worth a try)

@mbake5 see above (the update can take a few minutes to download)