[FiiO]

Hey

Hey Fiio is there a chance to get the equalizer work under Ldac whit the new update and firmware. It works great whit every other codec. But don't whit Ldac .

Dear friend,

We have reported your feedback to the engineer. They will try to assess about that.

Best regards

 

[hoekeat]

Dear friend,

Are the codecs be turned off in the APP:


Best regards

that is the screen, Q5S will be disconnected once "Confirm" is pressed. I need to remove the device, then pair a new device again.

This is what I have now, can't even select the codec.

 

[KopaneDePooj]

Dear friend,

For the CL06,

Best regards

Yes, that's what I wanted to point out to others - that message an no.3 - it seems I read it on my CL-06 package not on FiiO web pages.
Thanks!

 

[FiiO]

that is the screen, Q5S will be disconnected once "Confirm" is pressed. I need to remove the device, then pair a new device again.

This is what I have now, can't even select the codec.

Dear friend,

Try to reset the Q5s by poking the reset button and reconnect?

Best regards

 

[hongky]

Is there any way to check which firmware version installed on Q5S ?

Thanks

 

[happytorch]

Is there any way to check which firmware version installed on Q5S ?

Thanks

In the driver panel Windows indicates the firmware version. It was discussed here some time ago.

 

[Cevisi]

I think there is just one firmware ?

 

[newtophones07]

I think there is just one firmware ?

0.37 is the latest.

 

[micgao]

Dear friend,

For the CL06,

Best regards

Despite what this picture says, there is definitely back-charging going on when I use the CL06 cable with my devices (Hiby R6, Hidiz AP80, Huawei phone). I'm not talking about the device showing a notification that there is back-charging, the battery drain just happens noticeably faster.

Also, I would like to corroborate what a previous user said about the Hidiz AP80 not detecting the Q5s in Bluetooth pairing mode. Yes, I am doing everything correctly (laptop, phone, and R6 all can detect the Q5s), but the AP80 simply refuses to discover the device regardless of what I do.

It would really be great if these kinks were ironed out for such an expensive device.

 

[Sonic Defender]

Despite what this picture says, there is definitely back-charging going on when I use the CL06 cable with my devices (Hiby R6, Hidiz AP80, Huawei phone). I'm not talking about the device showing a notification that there is back-charging, the battery drain just happens noticeably faster.

Also, I would like to corroborate what a previous user said about the Hidiz AP80 not detecting the Q5s in Bluetooth pairing mode. Yes, I am doing everything correctly (laptop, phone, and R6 all can detect the Q5s), but the AP80 simply refuses to discover the device regardless of what I do.

It would really be great if these kinks were ironed out for such an expensive device.

I wonder if the issue lies with the AP80? I am not sure that we should just assume the fault lies with FiiO. Perhaps the transmitter chip and/or implementation in the AP80 is fundamentally incapable of pairing. That is a possibility as the Bluetooth chip in the Q5s is a very current Qualcomm.

 

[LoveMusicEveryday]

Despite what this picture says, there is definitely back-charging going on when I use the CL06 cable with my devices (Hiby R6, Hidiz AP80, Huawei phone). I'm not talking about the device showing a notification that there is back-charging, the battery drain just happens noticeably faster.

Also, I would like to corroborate what a previous user said about the Hidiz AP80 not detecting the Q5s in Bluetooth pairing mode. Yes, I am doing everything correctly (laptop, phone, and R6 all can detect the Q5s), but the AP80 simply refuses to discover the device regardless of what I do.

It would really be great if these kinks were ironed out for such an expensive device.

Based on the specs, the AP80 supports Bluetooth 4.0. I am wondering if Q5s' Bluetooth 5.0 might not be interacting well with a Bluetooth 4.0 device. I am curious if you have been successful in paring your AP80 with a Bluetooth 5.0 based device before the Q5s.

 

[happytorch]

0.37 is the latest.

I asked fiio twice about the latest firmware. Which at the moment the firmware version is the latest and stable dear fiio did not answer.

 

[Cevisi]

I got 0.32 where to get 0.37

 

[tolis626]

@hoekeat
To change bluetooth codecs, you need to go into developer settings. In the Fiio app, you can enable and disable codecs. Whatever you have active in there (Be it just one or all of them) is just available to use. But to change the codec that's actively used, you have to go into developer settings on your phone (You have to have the codec enabled in the app first, though!). So try this. Reset your Q5s, pair it with your phone, check with the Fiio app that the codecs you want to use are ticked on (or just leave them all enabled, as it is by default), then exit the Fiio app (if you change anything, restart your Q5s just to be sure), go to your phone settings, under developer settings and find the option for the bluetooth codec. There, among others, you should have LDAC. Choose it, see if it works. It should just cut off for a second, then come back on with LDAC active. If not, then I don't know what's up.

To make things clear though, this is probably not Fiio's fault. Android's audio stack is a mess. Always has been. If it's anything but headphones plugged directly into your phone, you may get weird behavior. But it's an Android thing most of the time, and how it handles bluetooth codec selection is no exception. For example, my OnePlus 3 defaults to LDAC 32/96 for whatever reason (thought LDAC's maximum bit depth was 24?). Sometimes, however, I may get crackling and heavy stuttering. If I turn bluetooth off and on again, it's a flip of a coin whether it will default to LDAC again or go to SBC, but even if it's the latter and I manually switch to LDAC, it will work no problems after that. I also can't get it to default to 24/96. Android is weird like that. I hope Google sorts things out because it's frustrating to use sometimes.

 

[happytorch]

I got 0.32 where to get 0.37

Several pages ago I uploaded firmware 0.37