Rockbox Ports are now being developed for various digital audio players!
The Hold button seems to be recognized, but isn't working as expected: if hold is on the lock-icon on the status bar is flashing (together with the backlight) sometimes if I press a key / scroll the wheel.
Ah so it's at least recognized. That's different from what domonoky reported when he tried this code first.
if (queue_empty(&button_queue) && ++counter >= 4)
if (queue_empty(&button_queue) && ++counter >= 8)
I've also found that in rockpaint, oscilloscope, mandelbrot, and plasma that putting the hold switch on turns the screen off while switching it off turns the screen back on.
Try printing/logging the values DBOP_DIN gives.
I also just tried this patch again.For me the wheel reading is very unreliable, you have to be very lucky that rockbox recognises a wheel event. strangely, as others noted, it seems to work better in the time & date screen.
Quite weird.I've looked a bit at the patch.Sko:I noticed you changed the WHEELCLICKS_PER_ROTATION #define. Be careful with that define. It's directly connected to scrollwheel acceleration. And scrollwheel acceleration is problematic with the Fuze, possibly with the e200v2 too (as we're not using an interrupt handler [yet]).
int_btn &= ~(BUTTON_REC|BUTTON_POWER); in get_button_from_dbob??You changed BUTTON_HOLD to BUTTON_REC, why that?Resetting the hold button is vital for it to work properly. It might be that this change causes your weirdness.Other than that, I can't explain that pressing >>| after the wheel causes scrolling etc.
Well I counted the wheelclicks, and it clicks just 24 times, I thought the Fuze has maybe more wheelclicks.
Don't confuse wheel clicks with the physical clicks the wheel appears to do (the symbol should probably renamed, it confused me too).
Also those readings with the pressed buttons are not reliable, it sometimes finds scrollwheel and hold/rec and sometimes not. This is why we see the hold button flickering on and off.
Also the bits i can reliable read from the dbop are all below bit12, all higher bits are nearly always 0, so there must be something wrong with our dbop setup ? *speculating*
Page created in 0.321 seconds with 26 queries.