I’ve RC3 0.9.9 installed, which seems to have fixed the auto update feature in that updates now download automatically. But they still don’t seem to install automatically despite settings being configured to do so. Is this still broken, or is it just me?
I don’t believe we offer completely automated updates. At least I hope we no longer do
S
If the update requires a kodi exit or a reboot you will still be prompted to do this.
would be great if this could become a new feature 
Install updates that require a reboot [when Vero is idle / at a specific time / etc]
do you see any chance to integrate that?
This is easy to do, but I don’t think it’s a good idea. An update could break your system and you’d be none-the-wiser that an update had been performed.
A lot of people did not like Raspbmc’s auto-update feature, so I’ve been careful to avoid that same mistake.
Sam
Update setup on my Vero includes five options: prompt for all actions, display icon only, download and prompt, download and display icon and download and automatically install. I’ve chosen the last one, but it only does download and prompt instead.
Hi Sam,
thanks for your feedback.
To avoid such problem the feature could be disabled by default.
Also the “update icon” could be extended to improve the visibility of installed updates -> Updated installed.
To be honest, if an update is available, I always install it. Currently this requires extra clicking.
Of course some people are more careful with updates than others, but if the feature is optional I think nobody can complain.
What do you think?
Regards
Unfortunately people will if something goes bad! We also want users to be aware of when OSMC is receiving updates so they are more inclined to check the blog and receive a breakdown of what’s new, what’s fixed, and what’s coming soon. I think, they’re then more likely to take full advantage of their OSMC install.
Sam
1 Like
An update could break your system and you’d be none-the-wiser that an update had been performed.
Not sure I understand the logic here. You won’t know whether an update will do something bad until it’s installed. So you’re going to install an update anyway. As for knowing that an update has been installed, that could easily be handled with a notifier prompt -------- “An Update has been Installed, -Details- -Dismiss-.”
1 Like
But if you installed and update and your system immediately broke, you could say, “I just installed an update today and XYZ is broken”. If you’re not even sure an update was just installed (sure we can display a notification, but what if you can’t even open Kodi afterwards), then it’s a lot trickier.
We got a lot of flack from Raspbmc’s update system, so I am reluctant to have this feature added.
Sam
Of course the people will complain if somethings goes wrong, but it makes no difference if the update is installed manually or automatically.
I understand that you are carefull and I don’t want to convice you. I am just thinking that there different types of “update religions” out there and it would be great if the user could have the choice what is the best for him.
And to be honest, currently the “small updates” are also installed automatically and without notice, so we already have two routes.
I am looking at changing this behaviour, because it’s inconsistent anyway
Sam
It only prompts if installing the updates will require a reboot or kodi exit. With this setting for updates that require neither an exit or reboot the updates will be installed without prompting.
thanks for the explanation. I thought all updates needed a reboot or kodi exit.
what I did in SickRage (fork of sickbeard) was create a function that backups everything before doing an update. So If one user want to auto update then SR will force a backup so he can restore if anything goes wrong. Also I prevent auto-update If there’s a new DB version (user won’t be able to restore without loosing the new data)
Maybe this can be applied in OSMC too. Force auto backup when doing a big changes (kodi, FS, kernel or something else). And prevent auto install with critical updates (new kodi version for example and in the future the nightly builds)
It’s just my 2 cents.
Sorry If I can’t help in OSMC. I already have a lot of work with SickRage.
No not at all. Updates to Kodi, the OSMC settings addon and the OSMC skin require a Kodi exit but not a reboot. Updates to the Kernel, Pi firmware and a couple of other packages require a reboot. The remainder of the packages including most debian system packages don’t require a reboot or exit.
Hi Sam
Recently I had a evening’s worth of recordings fail and when I checked the Pi it was asking if I wanted to reboot for an update. I had it set to download updates, then prompt. In this mode does it do some updates before prompting and so effectively kill the Pi until it is rebooted?
What I would like to be able to do is just be notified that there are updates and then I would like to backup the SD card before applying the updates.
Thank you very much for your time
Keith
Not sure why the recordings didn’t go through. The log may help here. I’d suggest a new thread to look at the problem
S
@sam_nazarko you mentioned that the automatic update feature will dissappear in the future and OSMC will only base on final kodi releases. is there a plan to implement channels (like in chrome)? would be great if i could switch between the release and the beta channel and get the newest version after the update check.
There is already an ‘unstable’ version (staging repository) which has the latest and greatest but we don’t recommend it for users.
Sam
wasn’t aware of this. am i able to install that version with the build-in updater?