Ok, This is with 3b7.

This is kind of hard to properly explain, but here goes, and don't get too confused.

I get in my car, start a new playlist up, listen to it for a bit, turn off the car, pull the player out. When I get back in, and start up the player, I get the playlist that was previously running before I started that new playlist, but the position in the playlist is the spot in the new playlist.

One thing that does seem to help keep it from forgeting is if I either manually put it into sleep mode for about 30 seconds, or turn the car off and let it go into sleep for a bit.

The current playlist data is written to the scratch partition when you select it. The position within the playlist is written to flash memory when you power off. Clearly, the latter is happening but not the former.

Does it seem to happen mostly when you select a new playlist very shortly before pulling the player? For instance, you select a new playlist and listen for only a few seconds before yanking the player. I think that the scratch partition stuff may perhaps be deferred-write in 3a7.

This happens to me also. Not everytime, but enough to make it annoying. Why would the write be deferred? The disks are spun up anyway to read the new tracks. I don't think that the time before yanking is relevant - I've had this happen 20 minutes or so after selecting a new playlist.
I suspect that the player attempts to write the information, sometimes fails for some unknown reason and then forgets to retry. Whether this write failure is due to a new bug in an intentional change in the code or whether it's an existing race hazard that was previously unencountered due to other reasons is unknown.

Nope, it'll happen when I've been in the car for 45 minutes after starting the playlist, and it be playing the whole time...Also the songs that were played didn't get their playcount advanced.

For record I am experiencing the same issues. Quite annoying when you're half way through a new playlist and restart the car only to find it's forgotten it. (Not quite as annoying as the random marking of tracks though)

Seems to be a 3a7 thing - it never happened before.

(Not quite as annoying as the random marking of tracks though)

Hmm. I wonder if the 2 bugs are related...