Strange behaviour of my h120

[LAfant]

Hi Everybody,

since some days I notice some strange behaviour of my iriver h120. Somehow it reacts slow, when I load a track it often skips at the beginning, and sometimes false ID3 information is displayed (for example from another track). Sometimes I can't even skip tracks at all...

As I didn't drop my player I wanted to know if someone knows what the problem could be. Maybe it's because I left it in the car at minus degrees.

I'm into getting a Gigabeat anyway, but somehow I don't want to loose my iRiver since it offers quite some stuff which the Gigabeat doesn't.

Thanks in advance, any help is appreciated.

[LambdaCalculus]

You could try a couple of things:

1) Try checking your iriver's hard drive for errors. You can use CHKDSK /f in Windows, or fsck in Linux.

2) Update your build. (And let us know which build you're using, too! )

3) I'm figuring you're using MP3s, so check the ID3 tags for erros.

[Justurfing]

Thanks Gnostic for your post.
I am having the issue since early December when I installed a build around the first week. My boot loader version is 6; Rockbox version: r15969-071224. And I still have one of the builds from the last week of December. The problem keeps coming up when transitioning from MP3 to OGG mainly and sometimes when going from OGG to MP3, but this latter not frequent. I never get ID3 errors though. I always use Shuffle with Crossfade. I haven't done the CHKDSK yet but seems the origin of the issue came from updating to one of the builds during late November and early December. So I am still worried about what may be happening. I will give it a try to the CHKDSK as well.

[LAfant]

First of all I wanted to say thanks for the help, although I don't think these threads should be merged together, as I had this problem with all files, not only ogg.
Updating to a current build seems to have solved the problem, although I did not do any intensive testing...

Thanks again, you guys have been really helpful.

[NicolasP]

This issue seems to be the same one as described in FS#8260. It seems to have been introduced by r15444 (confirmation welcome). Increasing the default chunksize has helped in some cases, but not solved the problem. It is belied that the issue is in the thread scheduling and priority, but by attempts to fix it have been unsuccessful so far.