3.15 Install land operation errors Sansa 280

[Braverman]

Upgrading my Sansa e280's (v1 and v2) to 3.15 and have noticed some problems:

1. When installing from the utility it deletes your config.cfg AND most-recent.bmark files. Both of which I not not mention should not be touched.
2. When playing through a playlist and it comes to a file that no long exists, 3.14 would skip over it, 3.15 stops on it, informing the user that the filename is <root> and then sits - patiently - waiting.
3. Can't remember for the life of me what the third problem is.

And just a further question (excuse me the player just found another one of those files) ... In a V2 when you choose "files" from the menu you can see the internal memory and the external SDCard, on a V1 you can't - just a firmware change in the Sansa?
... 'cause I happen to LOVE being able to to that.

Thanks.

[saratoga]

Upgrading my Sansa e280's (v1 and v2) to 3.15 and have noticed some problems:

FWIW 3.15 is a 3 year old stable release meaning that it is not developed and we don't need to know what doesn't work since nothing will be fixed.  Rather than run old releases you should probably run the current build.

1. When installing from the utility it deletes your config.cfg AND most-recent.bmark files. Both of which I not not mention should not be touched.

I don't think this is correct.  The update process is designed to preserve settings and should not delete anything.

2. When playing through a playlist and it comes to a file that no long exists, 3.14 would skip over it, 3.15 stops on it, informing the user that the filename is <root> and then sits - patiently - waiting.

That didn't change.  Missing files are still skipped.

In a V2 when you choose "files" from the menu you can see the internal memory and the external SDCard, on a V1 you can't

The V1 and V2 (and all devices) work the same.  Could you clarify what you mean?  What can't you do?

[chris_s]

2. When playing through a playlist and it comes to a file that no long exists, 3.14 would skip over it, 3.15 stops on it, informing the user that the filename is <root> and then sits - patiently - waiting.

That didn't change.  Missing files are still skipped.

The behavior described by the OP is something I'd noticed myself. It was introduced about 4 years ago (so before the release of 3.15) by this commit: https://github.com/Rockbox/rockbox/commit/dfff938dff089667038041fcb66262c87c3186c2

There's a a patch on Gerrit that changes it back to how it had been previously (except that it now won't skip over the last entry of a playlist). I should remove the "WIP" label since it doesn't seem to have caused any problems testing it for the better part of a year now on my devices.

[saratoga]

Maybe I'm misunderstanding, but I just created a playlist, deleted a file in the middle of the playlist and played it. The playlist skipped the missing file as expected. Or does it work differently if it's m3u for the playlist?

[chris_s]

Maybe I'm misunderstanding, but I just created a playlist, deleted a file in the middle of the playlist and played it. The playlist skipped the missing file as expected. Or does it work differently if it's m3u for the playlist?

I'm not sure right now why we're seeing different behavior.    Would have expected you to see something like this when reaching a missing file:

[chris_s]

I guess if you're only playing a folder, the file would disappear from the playlist (and thus be skipped) after stopping/resuming playback, since the tracks would not be inserted into the playlist. That's the only thing I can think of right now.

[Braverman]

Before anything else, what is the "current stable" version and why doesn't the install utility designate it as such?

[bluebrother]

Before anything else, what is the "current stable" version and why doesn't the install utility designate it as such?

It's 3.15 and Rockbox Utility designates it as such.

[Bilgus]

I think some of those issues are already fixed in the dev version
Again we don't fix bugs in the older stuff it's already set in stone

Stable doesn't mean works perfectly and there hasn't been anyone testing these builds for your device
Clearly.
Best I can say is use a dev version so we are sure the bugs are still there and actually have a chance at finding and fixing them

The codebase is in much better shape now versus 3.14and 3.15 we have found  fixed alot of BAD
For instance A few months ago we fixed 100s of issues identified by coverity code analysis
From buffer overruns to just terrible code literally 100s left but we got the worst of it...

It's all a work in progress but old bugs from past releases dont push the bar closer to perfection

[Braverman]

I think some of those issues are already fixed in the dev version
Again we don't fix bugs in the older stuff it's already set in stone

Stable doesn't mean works perfectly and there hasn't been anyone testing these builds for your device
Clearly.
Best I can say is use a dev version so we are sure the bugs are still there and actually have a chance at finding and fixing them

The codebase is in much better shape now versus 3.14and 3.15 we have found  fixed alot of BAD
For instance A few months ago we fixed 100s of issues identified by coverity code analysis
From buffer overruns to just terrible code literally 100s left but we got the worst of it...

It's all a work in progress but old bugs from past releases dont push the bar closer to perfection

Bilgus, nice to see you again ...

Which dev version would be the one to "test/try out"?

[Bilgus]

We don't typically leave things knowingly broken so whatever the latest is unless someone says otherwise (if known issues present like the USB thing)

Dev builds get built nightly at the least

[Braverman]

We don't typically leave things knowingly broken so whatever the latest is unless someone says otherwise (if known issues present like the USB thing)

Dev builds get built nightly at the least

Is that what gets shown in the installer? Or placed somewhere else?

[Bilgus]

I don't use rbitil like at all so not the last word but yes I believe rbitil pulls the latest nightlies

[saratoga]

I guess if you're only playing a folder, the file would disappear from the playlist (and thus be skipped) after stopping/resuming playback, since the tracks would not be inserted into the playlist. That's the only thing I can think of right now.

You're right, I just tested it and M3U is handled differently.  I never noticed since I don't use M3U much.  I think that behavior should be reverted.

I'll comment on the gerrit task.

[Braverman]

I don't use rbitil like at all so not the last word but yes I believe rbitil pulls the latest nightlies

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.

Now then when can I see what the latest version is? 3.15 on 280v2 is causing a lot of problems - minor - but annoying, so ...

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 - perhaps that would be helpful,especially, when there are problems and the user has no idea what he put on it (I mention that as I am often guilty).

I'm going to install it today and see if the mentioned problems, as well as others are still plaguing me.

THANK YOU!

**************** UPdate *************
Attached is what happens when a playlist attempts to load a file that is either not there, or is mis-spelled etc.