3.15 Install land operation errors Sansa 280

[saratoga]

The util shows: b14df9077f - OOPS just saw the note next to it, so this point is moot (never saw it before), but brings up humble suggestion. In the info within the player you note when it was installed but not the version

Both the boot screen and System -> Rockbox Info show the version and build date that is installed.  Rockbox utility will also show you the version you have installed, at least if you're using it to install.

[Frankenpod]

I see that point differently; you as a developer wouldn't use it for obvious reasons, but - this is only a guess - but I'm thinking 75% of the people who buy a player and hear about Rockbox WILL use The util, which makes it pretty important to either not have developers versions list or to do so with a warning.

Don't know about your original issue, but I disagree with this point - RButil seems to me to be quite clear about giving you the choice of the most recent 'point release' (aka 'stable' version) or the latest dev version, and almost always I install the latest dev version (usually after checking the list of recent changes shown on here - sometimes there's recent relevant ones that makes the latest dev version desirable to me).

Also Rockbox itself, and RButil, both, as far as I remember it, list the build-date of the relevant dev version.  (Hence I sometimes look at some of my less-used devices and think 'gosh, this one's using a build from over a year ago')

[bluebrother]

I see that point differently; you as a developer wouldn't use it for obvious reasons, but - this is only a guess - but I'm thinking 75% of the people who buy a player and hear about Rockbox WILL use The util, which makes it pretty important to either not have developers versions list or to do so with a warning.
I use it (didn't when I was testing the other versions), as I can never remember which version of the player I've connected.

I don't understand what you're complaining about. Can you be more specific?

Rockbox Utility defaults to "Stable Release" if it hasn't been used before, and the build type used in the previous install if it has been used before (since it's likely you'd want that build type on the next install again -- especially if you installed a development build.) The build type is clearly shown in the version dropdown. It allows you to install the most recent development version too, and it's indicated as "Development Version". Next to the dropdown is a short explanation. If the player you're trying to install to doesn't have a released version it will fallback to selecting the development version. This usually happens when no new release has been made, but it has been updated to already support it (f.e.: right now this includes the AGPTek Rocker, since no release has been made for that player yet, and only if you use a development version of Rockbox Utility.)

When installing using Rockbox Utility it will also create a log file that will allow to identify the installed version of all files. This is shown on the Info tab, and shows the installed version. For development versions there isn't a version number like for releases, so it uses the git hash instead. This allows to find outdated files (f.e. files that have been removed at some point, or renamed). Unsurprisingly this only works if you installed using Rockbox Utility -- if you unzipped the build yourself the log file doesn't know about this (unsurprisingly.)

How do you think this could get improved?

So for those 75% users you mentioned (though I'd expect that to be more than 75%) would connect the player, run Rockbox Utility, default to latest release, install, and are done, and if it's one of the older players, likely won't touch it again. What else could they want?

[Braverman]

I see that point differently; you as a developer wouldn't use it for obvious reasons, but - this is only a guess - but I'm thinking 75% of the people who buy a player and hear about Rockbox WILL use The util, which makes it pretty important to either not have developers versions list or to do so with a warning.

Don't know about your original issue, but I disagree with this point - RButil seems to me to be quite clear about giving you the choice of the most recent 'point release' (aka 'stable' version) or the latest dev version, and almost always I install the latest dev version (usually after checking the list of recent changes shown on here - sometimes there's recent relevant ones that makes the latest dev version desirable to me).

It does and I stand corrected. I looked at 3 different units before I posted that AND put the latest dev version on, as I wanted to be able to keep track, but just didn't see it - sorry.

Also Rockbox itself, and RButil, both, as far as I remember it, list the build-date of the relevant dev version.  (Hence I sometimes look at some of my less-used devices and think 'gosh, this one's using a build from over a year ago')

Again I totally missed it. I had asked Bilgus about where the versions were as I did not see the date listed next to them in the utll - I swear I REALLY need to pay more attention. I'm not accustomed to posting obvious or irrelevant questions or comments.

[Braverman]

I see that point differently; you as a developer wouldn't use it for obvious reasons, but - this is only a guess - but I'm thinking 75% of the people who buy a player and hear about Rockbox WILL use The util, which makes it pretty important to either not have developers versions list or to do so with a warning.
I use it (didn't when I was testing the other versions), as I can never remember which version of the player I've connected.

I don't understand what you're complaining about. Can you be more specific? 

I'm not complaining, I whine often, but refrain from complaining.

I got the impression from a post by Bilgus that he didn't think the util was useful or should be used, I was commenting on the reason why I thought it should be paid attention to.

Rockbox Utility defaults to "Stable Release" if it hasn't been used before, and the build type used in the previous install if it has been used before (since it's likely you'd want that build type on the next install again -- especially if you installed a development build.) The build type is clearly shown in the version dropdown. It allows you to install the most recent development version too, and it's indicated as "Development Version". Next to the dropdown is a short explanation. If the player you're trying to install to doesn't have a released version it will fallback to selecting the development version. This usually happens when no new release has been made, but it has been updated to already support it (f.e.: right now this includes the AGPTek Rocker, since no release has been made for that player yet, and only if you use a development version of Rockbox Utility.)

Much ado about nothing, it was simply that I had commented the date of the dev release should be noted - as I didn't/couldn't/refused/didn't look/etc. to see it. I've seen the error of my ways and and retract that comment.

When installing using Rockbox Utility it will also create a log file that will allow to identify the installed version of all files. This is shown on the Info tab, and shows the installed version. For development versions there isn't a version number like for releases, so it uses the git hash instead. This allows to find outdated files (f.e. files that have been removed at some point, or renamed). Unsurprisingly this only works if you installed using Rockbox Utility -- if you unzipped the build yourself the log file doesn't know about this (unsurprisingly.)

Thanks for that info.

How do you think this could get improved?

No, quite functional - when the user pays attention.