AGPTEK Rocker

[wodz]

Running the latest git code (20bdfa82) and there are some issues.  My question is where I should report them -- in the forums (this thread?), In the flyspray tracker (no AGPTek Rocker entry there yet), the main mailing list, or where?

I think forum is the best for now.

* Wonky keymaps in some places

I am open to improvements suggestions. Ideally a patch.

* volume control steps are very gradual

Yes, steps are 0.5dB. Personally I find it usefull to have fine grained control but users seem to disagree.

* LCD doesn't seem to update when skipping or seeking tracks, but does when pausing/playing.

Interesting. I didn't spot this. Will check.

* Need to expose output gain selection (to select between HP and Line out)

I don't understand. AFAIK it only has HP output not line out.

[Markfm]

Would it maybe be possible to have volume step size a user-adjustable setting?  We've done things like that with VLC.

[wodz]

Rockbox has *a lot of* adjustable settings, way too much for average user. I am not saying it is impossible it is just very unlikely to go upstream.

[Milardo]

I asked this question on IRC but didn't get a reply yet. Is the dev builds page going to be updated soon to include agptek rocker?

[wodz]

I think I commited all needed changes however server admin needs to deploy this. I'll try to catch him.

[johnb]

Regarding the volume steps see http://gerrit.rockbox.org/r/#/c/1555/. I made the comment about the hack respectively missing a clean and global solution.

Regarding keymaps:
I would suggest two changes (and can create a patch):
- Currently there is no way to cancel when in "Recent Bookmarks" screen, i.e. you have to select one and only then can quit. I would assign Cancel to the Power button.
- Like on the clip+, when in any of the other menus, clicking Power twice takes you back to WPS.

Right now I don't have the tool chain compiled myself, only then I would create the patches, i.e. when I am able to test myself.

[wodz]

simulator is pretty convenient for testing keymaps.

[wodz]

Regarding the volume steps see http://gerrit.rockbox.org/r/#/c/1555/. I made the comment about the hack respectively missing a clean and global solution.

706e31b should fix this without hack.

[saratoga]

FWIW, we usually aim for a 1 dB step size in the audio drivers if the hardware is capable of it.  The rationale is that 1 dB is approximately the smallest step size that most people will notice without careful concentration. 

[speachy]

706e31b should fix this without hack.

I saw the commit and rebuilt it this morning, and I'm happy to say that the WPS volume control buttons now have an audible difference.

* LCD doesn't seem to update when skipping or seeking tracks, but does when pausing/playing.

Interesting. I didn't spot this. Will check.

I misspoke -- basically, while in the WPS, the screen doesn't update until/unless a button is pressed.

* Need to expose output gain selection (to select between HP and Line out)

I don't understand. AFAIK it only has HP output not line out.

The CS42L51 doesn't have a dedicated line out, but via the output gain setting you can mimic it fairly closely by controlling the peak-peak voltage range/swing.  (Se page 17 of its datasheet)  Basically, "consumer line level" expects a peak-peak swing of ~0.9V (vs "pro line level" of about ~3.5V).

Both of my vehicles' line (not AUX!) inputs seem to fall on the "consumer" side of that line, and dialing the gain down to '0' results in noticably better audio quality, with 0.97v p-p voltage, vs the ~1.25v p-p voltage of the previous setting of '2'.  It also presumably results in slightly better battery life.

As an aside, Benjie/AGPTek's not releasing their Linux kernel sources is quite annoying; it would be nice to be able to utilize more of the CS42L51's features, like the native bass/treble control.

(When I have some more time I intend to start poking around via adb)

[wodz]

FWIW, we usually aim for a 1 dB step size in the audio drivers if the hardware is capable of it.  The rationale is that 1 dB is approximately the smallest step size that most people will notice without careful concentration. 

While I agree that 1dB is about right step it was definitely a bug to not honor AUDIOHW_SETTING() declared step. Now it is up to developer what it defines as step (which usually reflects hardware capabilities).

I misspoke -- basically, while in the WPS, the screen doesn't update until/unless a button is pressed.

28cfeed4 should fix this.

[Milardo]

Hi wodz,

            Just downloaded the latest dev build, however for people that are new this rockbox port, it doesn't seem to include the update_rb.upt file which is supposed to be named update.upt? Is it still necessary to do this? Also is there a webpage for the agptek rocker which includes the instructions for upgrading to rockbox?

Found it:

https://www.rockbox.org/wiki/AgptekRocker

Doesn't seem to include instructions for rockbox installation or update?

[speachy]

I misspoke -- basically, while in the WPS, the screen doesn't update until/unless a button is pressed.

28cfeed4 should fix this.

Excellent, thank you!

BTW, one more for the bug/quirk list -- When audio playback starts (or resumes) there is sometimes an audible pop/click -- Several theories (codec automatically going into powersave mode?) but no way to really confirm anything since I still can't get ADB to work.  (Is there some trick involved beyond launching it via the bootloader?)

[wodz]

Just downloaded the latest dev build, however for people that are new this rockbox port, it doesn't seem to include the update_rb.upt file which is supposed to be named update.upt? Is it still necessary to do this? Also is there a webpage for the agptek rocker which includes the instructions for upgrading to rockbox?

Found it:

https://www.rockbox.org/wiki/AgptekRocker

Doesn't seem to include instructions for rockbox installation or update?

update_rb.upt is ONLY needed to install bootloader (usually ONLY once). We will not distribute patched original firmware images for legal reasons. I have plan to significantly simplify process of update_rb.upt generation but I don't have much time to work on this.

Once bootloader is installed you only need to unzip rockbox.zip (which is now directly available from dev build page) to the root of SD.

You know that this page you are referring to is WIKI, right? Feel free to contribute.

BTW, one more for the bug/quirk list -- When audio playback starts (or resumes) there is sometimes an audible pop/click -- Several theories (codec automatically going into powersave mode?) but no way to really confirm anything since I still can't get ADB to work.  (Is there some trick involved beyond launching it via the bootloader?)

I didn't spot this pop/click but I don't use Rocker daily. Anyway I am afraid there is nothing I can do about this.

There are reports that you need to use adb older than 1.0.37 on PC. Personally I use 1.0.32 without problems. Another thing is that you cannot use ADB and run original firmware. Hiby player seems to intentionally overwrite android usb gadget settings breaking adb.

[Dulus_No]

Hello!
On the latest dev. build (d64ff86) the display keeps working when backlight is off: https://imgur.com/ge7VyK6.gifv