Fiio M3k

[amachronic]

Hi all. It's been a while since I've made any major user visible improvements, but I've got one to announce today. Tomorrow's daily build will bring improved USB performance and reliability to the M3K (and Q1 / ErosQ native ports). The performance isn't yet on par with the OF, but I'm hoping to close that gap with an improved USB storage driver (based on the UASP protocol).

Also, there was a bug in the low-level timer setup code which I fixed. This shouldn't be a noticeable change, except for slightly shorter boot times, but it's possible some units might experience issues (possibly intermittently or at random). If anybody does start seeing buggy behavior after today's build I'd appreciate if they can report it, since it will likely be caused by this timer bugfix and only need a quick patch to fix.

[7o9]

amachronic, after upgrading the M3k to the build with your USB changes (rockbox-fiiom3k-20211017.zip), it shows the message 'Battery empty! RECHARGE!' immediately after start and shuts down.

The device charge, it runs the OF fine and shows a full battery icon.

Going back to the previous daily build (rockbox-fiiom3k-20211016.zip) makes it work fine.

This problem does not happen on the Shanling Q1 (rockbox-shanlingq1-20211017.zip) which boots fine.

[lubatur]

Here too: rockbox-fiiom3k-20211017.zip > it shows the message 'Battery empty! RECHARGE!' immediately after start and shuts down, but battery is full charged.
Starting  rockbox over bootloader or bootmenue is ok.

[amachronic]

lubatur, 7o9 sounds like it's getting a false battery reading after boot, so could you test these builds, reboot a few times with each of them and let me know the first one that works reliably?

• 20ms - https://drive.google.com/file/d/147FRA2P8VY3kuH1xXroR9r8Prza7Uq7_/view?usp=sharing
• 40ms - https://drive.google.com/file/d/1zdEOYOk5VjxVPJwafpa_AUJunV4OUETt/view?usp=sharing
• 80ms - https://drive.google.com/file/d/15JaQij7J7hhGmQ-wG5KNE3PEC5gFExZY/view?usp=sharing
• 160ms - https://drive.google.com/file/d/14kcgMoMq5Rh7cfFYEcFjIbFl_lADFmlz/view?usp=sharing

Each build adds a delay of 20ms, 40ms, etc. to the boot so we're just trying to find the shortest delay that gets past the initial flaky voltage readings. In theory 80ms should be guaranteed to work but I added a 160ms build just in case. For some reason my unit is working fine with the now-current 5ms delay... I guess I just got lucky.

Thanks for the help!

[7o9]

20ms en 40ms do not work. 80ms works. did not test 160ms.

[lubatur]

20ms and 40ms don't work.
80ms and 160ms work.
And amachronic thank you for your work!

[amachronic]

Thanks! 80ms patch is now merged and should make it into tonight's daily build.

[Julian67]

On my device the 80ms build didn't work, nor did the daily build rockbox-fiiom3k-20211018.zip.  The 160ms build works fine.

[amachronic]

Julian67 I've pushed a 200ms build and as of now the dev build should be fixed. You'll have to wait for 20211019 if using the daily build. If anyone is still experiencing this issue with the latest dev build, here's another build to try -- let me know if it fixes it.

400ms build - https://drive.google.com/file/d/10SSqteHAQbOuF6_OUyNHpbL6FCD_kBy-/view?usp=sharing

[Julian67]

Daily build of 19th works fine, thanks.

[vitt13]

What happened with menu voicing? It sounds very glitchy like stereotypical robot. But it plays phrase 'invalid voice' clearly (right after player starts) if I use old (incompatible) voice file.

[amachronic]

What happened with menu voicing? It sounds very glitchy like stereotypical robot. But it plays phrase 'invalid voice' clearly (right after player starts) if I use old (incompatible) voice file.

I tested a build & voice file (en-us) from 2021-10-15 and one from 2021-10-21, both of them sound the same, low quality and robotic. So it should be unrelated to my recent changes. The RB servers were migrated to a VPS instance recently, so perhaps whatever voice was being used before is missing from the VPS? I don't use voice so I have no clue what it originally sounded like.

[diegopau]

I finally decided to migrate from the Vortex build to the new native builds.

Took me initially a few minutes to get used to the new button mapping, which is quite different, but I am not happier than with the previous button configuration. Other than that works great, no bugs, really happy with it. Thank you @amachronic and all other contributors for your work on this. Without RockBox it would be much harder for me to sleep at nights, i use it all the time for audiobook and podcasts at night.

Suggestion: I noticed than the touch buttons up and down (top and bottom of the touch bar) are not assigned to anything in the WPS, what do you think of assigning them to volume + and volume -? i know it is redundant, but using touch buttons prevents wearing the physical buttons too much, the volume buttons are the first thing that stopped failing in my Sansa Clip Zip. Or if there is a way for me to select a function for those 2 buttons while in WPS tweaking some config files please let me know

Thanks again.

[chris_s]

Really amazing job, amachronic! As for the discussion about keymaps (@cereal_killer and @diegopau), here's what works well for me. My main expectations/requirements were (iirc):

• Be able to stop playback by long pressing the power button from anywhere
• Get back to WPS by pressing Play/Pause
• Be able to scroll menus to the left/right to quickly see longer text strings that get cut off (not supported by the current keymap)
• See current playlist from WPS with single button press
• And be able to change volume by touch
• Return to browser from WPS with single button press
• Consistent activation of context menu in WPS/tree context

I left the Repeat-AB-Start/End button mapping and pretty much everything else unchanged at the moment. If anyone's interested in seeing the keymap, I can put it up on Gerrit. It only requires pretty minor adjustments compared to the current one though..

[7o9]

Please put it on Gerrit, chris_s, I would like to try that. It looks good.