Support and General Use > Hardware
Iriver H120: Volume knob on remote skipping directories
Mmmm:
My bitrate remote button gives 68
So just as an experiment here's an extreme version with the boundary between volup and bitrate at 67. It works fine on mine.
So to finally rule this out  Stigvig, could you test it and whether you still have the same problem when using volup, if so,  then I think we can safely(ish) say this isn't the problem.
Make sure you already have an up to date .rockbox folder and use the appropriate rockbox.iriver file  from below.. I don't know what type of IRiver you have so I've included an H1xx and a H3xx version.
(obviously make sure you remove the -Hxxx at the end of the filename)
EDIT: deleted old links
StigVig:
Hi there,
Ok I was perhaps jumping to hasty conclusions when I said that they change over time. What I meant was that I've seen other values for other buttons "flicker" between two or more values while pressing the button in question, so I supposed it was this behavior that was behind the dir skipping.
And yes, for the vol-button it's only while pressing volup.
I will install and test the new build (ps. the subject title might give a hint of my iriver version ;) but the builds might be useful for others :) )
Mmmm:
--- Quote from: StigVig on November 14, 2006, 03:14:04 PM ---And yes, for the vol-button it's only while pressing volup.
--- End quote ---
Ok, good, that makes sense so far then.
--- Quote ---I will install and test the new build (ps. the subject title might give a hint of my iriver version, but the builds might be useful for others )
--- End quote ---
:D ...oh yeah... I didn't notice that :D
If the new build works then we are going to have to embark on a long journey of gradually lowering the boundary until we find the cut off point... what fun... Â ;)
Multiplex:
HA! - so this is how the established devs keep new-commers off the credits list ! ;-)
My bitrate also gives 68
You could of course use the binary-chop method to get to the best cut-off...
Assuming that this build is OK the next build should set the boundary to halfway between 0x67 and 0x5a, then iterate ...
Mmmm:
--- Quote from: Multiplex on November 15, 2006, 04:50:25 AM ---HA! - so this is how the established devs keep new-commers off the credits list ! ;-)
My bitrate also gives 68
You could of course use the binary-chop method to get to the best cut-off...
Assuming that this build is OK the next build should set the boundary to halfway between 0x67 and 0x5a, then iterate ...
--- End quote ---
Indeed...
I'd be quite happy for you to do all the chopping if you like.. and I'm seriously considering your replaygain tag patch, so there may be some credit coming your way soon ! :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version