Gigabeat F20 erratic behavior with headphones plugged in.

[BarkusMasta]

I recently updated to the latest and greatest version of RockBox on my F20 via the RockBox Install Utility.  For some reason, whenever I have headphones plugged in, my F20 will play for a few seconds then pause.  Without headphones plugged in it will seemingly operate normally but alas, when you plug headphones in it does the pause thing again. 

Previously, it was doing this and I tried downgrading the firmware and that only got me even more odd behavior (the second I would plug headphones in it would start popping in and out of menus and going all over the place).  I then opened it up and looked for maybe spots in the buttons or the headphone jack that might be shorting out but found no issue.  Since I had the casing open I pulled the hard drive and battery then re-installed them both.  That seemed to take care of the odd stuff but it still does the pause thing with headphones.

At this point I have a working F20 on the older firmware but it refuses to play with headphones plugged in.  For some reason I now powered the F20 up with headphones already plugged in and got the white PANIC screen saying something about "Stack Overflow".  I started poking around on this site and saw that this issue was addressed so I again updated to the latest version. 

So now, I have an F20 that doesn't panic with headphones already plugged in but still... it won't continue to play with headphones plugged in.  I've already went into the settings and shut off the option to pause on headphone unplug maybe thinking that might be screwing me up but it made no difference in the issue what so ever.

Any ideas?

[Chronon]

Do you have Rockbox configured to pause when headphones get unplugged?  Maybe your headphone jack has a flaky connection.

edit:  I didn't read carefully enough.  You have already turned off that option.  Maybe the sleeve connection used for the remote is experiencing a flaky connection that is being interpreted as button presses from the remote.  Maybe there's something obvious related to that pin/trace.  .. 

Does playback through the cradle work as expected?