All Projects

IDProjectTask TypeCategorySeveritySummaryOpened
6041RockboxPatchesDriversLowH10 Scrollpad2006-09-21172 Task Description

The scrollpad on the H10 (20gb, not sure about 5/10gb) has always bothered me with being jumpy, inaccurate, and unintuitive. At the moment (in rockbox) it seems as though it is working as a simple two button device (up/down), with no real dragging capabilities. I am wondering if this is a limitation of the hardware or current software implementation.

The original firmware seemed to work as follows:
split slider into upper and lower field. Tapping in either upper or lower half would create click-type event for up/down. Dragging in upper half would produce scroll up, draggin in lower half would produce scroll down events. The problem was that upper and lower halves are really kinda arbitrary and not easily distinguishable.

What I think would work nicely:
Tapping top and bottom, as before. Remove upper and lower restrictions for dragging, i.e. if dragging down (anywhere on the scrollpad) create scroll down event, if dragging up (again, anywhere) create scroll up event. Drag and hold will scroll in desired direction proportional to the drag speed (as in pushing a puck on ice). Hold (just hold, no tap or drag) on the touchpad creates a sliding value that can be used as a coordinate for different types of continuous input.

To implement this, we’d need some kind of knowledge about what signals the actual hardware provides, what resolution the pad has, i.e. what the physical and logical implementations of the device are. I am not sure how the Ipod scrollwheel works, but it seems that some of that code could be re-purposed, maybe?

 6040 RockboxBugsOperating System/DriversHigh CPU Timing/Boost on H10 2006-09-215 Task Description

As far as I can remember, the CPU boost feature has been disabled on the H10 because it could cause the system to hang. It would really be useful to get this to work properly, because otherwise the playback will be interupted by anything from scrolling through long lists to using most of the plugins.

I am wondering if the original problem was an incorrect setting for the CPU speed (this was addressed in a later fix, I think). For example, currently zbox runs at about 40% speed, and the speed-boost option (in zbox, not rockbox) pushes that speed to 200%. These kind of strange numbers (it seems normal mode for zbox should be 100%, not 40%), makes me think that either rockbox is reporting an incorrect clock speed, or zbox is computing something incorrectly.

As a general idea (not having looked at the code in detail) I am wondering if it would be possible to boost CPU not by default, but on a need-to-boost basis. As in: If the play buffer gets below x1 percent, fill the play buffer in normal CPU mode. If it gets below x2(<x1), fill it in CPU-boost mode. Shouldn’t add much more code and might save some battery, particularly on powerful CPUs.

 5962 RockboxBugsUser InterfaceHigh H10 Bookmark: Buttons not responsive when selecting boo ...2006-09-091 Task Description

When selecting a bookmark (manually or when prompted by the system after playing a previously bookmarked title) none of the buttons seem to be responsive (up and down seem to work when several bookmarks are available), but I cannot: exit the screen or play the title. Only a long exit (system shutdown) helps to get out of this one.

Possible reason: button-defs not yet changed to work with H10 buttons

Showing tasks 1 - 3 of 3 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing