Fiio M3k

[speachy]

I'm just asking because I have no idea:  Would a change from 16-bit to 24 or 32-bit be a huge upheaval?  Would it be impossible to do without dropping support for 16-bit players? Technical query, not a feature request!

At minimum, we'd need to make the audio path variable-width at compile time, so 16-bit only devices don't incur any performance penalty.

A basic question is if we want to unconditionally use 24/32-bit audio on platform that support it, or switch back and forth at runtime.  Switching makes everything a lot more complicated, with multiple code paths and new APIs.

Meanwhile. Our DSP/EQ/effect engine doesn't support >16bit.  Additionally, we'd have to implement 16-24bit conversion for the various codecs/plugins that don't support >16bit audio (that said some of our targets only support 24/32-bit audio so that's already implemented, just not in a generic manner)

[Julian67]

I'm just asking because I have no idea:  Would a change from 16-bit to 24 or 32-bit be a huge upheaval?  Would it be impossible to do without dropping support for 16-bit players? Technical query, not a feature request!

At minimum....

Thank you for a really comprehensive answer.  Appreciated.

[mario69]

good morning, I have a problem, my fiio m3k player after two years of excellent functioning with rockbox, I get a message like this:panic -updating size on empty dir entry 4 (and also others Number) Simeone have a solution?thanks

[vitt13]

please repost Vortex's build here

I have only triple boot firmware with XVortex build, OF and native RB bootloader. It's outdated and can revert your latest RB bootloader version. To boot in XVrortex build just use Vol+ and Power.
https://www.mediafire.com/folder/8voqo1pdm6k3o/M3K_fw_XVortex_1.4.3_dualboot_native_rb
---
Found his original build (*.fw) and extracted Rockbox build (taken from *.fw)
https://www.mediafire.com/folder/izr547zpatrcx/Vortex-Rockbox
---
The theme from his build posted here https://forums.rockbox.org/index.php/topic,52917.msg248809.html#msg248809

[alex64]

Hello! In the DAC settings, there is save battery and sharp fiter. But it seems to discharge faster than on the official firmware. Is it possible to reduce the discharge somehow?

[amachronic]

I don't use the official firmware, so... I only have general advice. The DAC power setting has a marginal effect on battery life. I haven't measured it, but going by the datasheet it's roughly a 2 mA difference between "high" and "low" power. At any rate it's small enough to not be very noticeable. The backlight and button light can consume a lot of power, so you can try reducing the brightness.

The codec you use will also affect battery life. Eg. Opus is CPU-intensive and will consume more power, but lossless codecs can also do that because they keep the SD card busy more often.

You can check the debug menu to see how much power you're actually using: View HW info > Power stats. I_dchg is the battery discharge current.

[alex64]

Thank you for the answer.

[alex64]

In rockbox, the player charges very slowly. And when you turn on the charge numbers can jump. At first, for example 93, after a few seconds 76. Why is that?

[laxesandz]

I found one bug, however.  The left-right balance does not work for me. Volume in both headphones is turned down instead of just one side.

[Thew]

That's very odd as it works fine on mine. I've just checked and there's no problem. Actually I have two Rockboxed M3Ks and they both work as expected.

[SteveDave]

I found one bug, however.  The left-right balance does not work for me. Volume in both headphones is turned down instead of just one side.

That's very odd as it works fine on mine. I've just checked and there's no problem. Actually I have two Rockboxed M3Ks and they both work as expected.

May I ask what versions you guys are running?
Mine works ok but I haven't updated it since 2022 I think.
Ver: ab71b9e334-220428

[Thew]

May I ask what versions you guys are running?
Mine works ok but I haven't updated it since 2022 I think.
Ver: ab71b9e334-220428

I'm running:
ver. b309fae2bc-220317

[SteveDave]

I'm running:
ver. b309fae2bc-220317

Thanks for that, hopefully this info helps laxesandz rule out a version issue.

[ari]

Just came in to say THANKS to the devs that ported rockbox to the m3k. I bought a resale unit in aliexpress just to be able to return to rockbox. After the last of my clips died years ago, I tried the Fiio M5, same ingenic MPU, great format for jogging, great sound and battery life but terrible terrible terrible firmware, and unfortunately rockbox never made it to it.

The M3K took an hour to setup and now after many years I can now properly browse my 30000 song collection (.ogg, properly tagged to my liking), build and manage playlists easily.

Anyways, in case this helps someone, here's how I quickly got rockbox up and running and how I set it up, from a linux desktop.

  - Install the bootloader using a web tool - for this you can either deal with udev permissions to allow the browser to access the device via USB or you can take the express route I took, running chrome as root just for this; this assumes you are using Xorg (not wayland)
    > xhost +
    > sudo google-chrome --no-sandbox --user-data-dir
      browse to: https://amachronic.github.io/jztooljs/
      and follow the instructions.
    - once the bootloader is running in the device, with the device still tethered, select in the device "USB Mode" which will expose the M3K SDcard filesystem to the linux desktop. You can then just copy the latest M3K daily build (.rockbox directory), and your chosen theme/s
       M3K daily build: https://www.rockbox.org/dl.cgi?bin=fiiom3k
       Theme that works great in this device: nightpod: https://themes.rockbox.org/index.php?themeid=3399&target=fiiom3k

   > shutdown and power on the device, it should boot directly to rockbox.
   > Post-install tweaks:
      - Settings > Sound: limit volume to 0db
      - Settings > General Settings > Display > LCD Settings > Backlight Exemptions
        - set to Enabled (no need for any other change on Backlight exemption)
      - Settings > General Settings > Display > LCD Settings > Backlight On Lock
        - set to Off if you prefer to turn off the display when pressing the "lock" button (on/off button short-press)
      - Settings >General Settings >System >Advanced Keylock
        - set to Enabled; in Settings, turn on:
          - Autolock ON, Always Autolock, Disable Locked Reminders, Disable All Lock Notifications

[Julian67]

It really isn't as complex as you describe!  I've been using a Fiio M3K for a few years and Debian for decades.  Just follow the Rockbox docs to install Rockbox on the Fiio.  It's really easy and does not require special how-to posts or tweaks.