K3 USB issues

attitude427

Now worst... windows says the device malfunctioned and cannot recognize it at all.

attitude427

Can someone from fiio reply? I cant use it now.

Anyone else faces this issue? Or issit just mine that is faulty?

Object_Voice

[ My K3 is just the same, it's enough of a problem with my Windows 10 PC as to make it basically useless - red LEDS, not getting detected and also arbitrary cut outs where it just goes dead for a couple of seconds. It's a real headache. I wish I hadn't sold my E10k which was excellent and totally unproblematic. I can't even really sell it because I wouldn't be able to sell it as 'in working order'.]

Actually, scratch this. I need to go back and read the manual and understand how the thing is supposed to function before I start saying it's not working. I had it totally wrong about the function of the red led for a start.                                       

attitude427

I have tried every possible way for it to work on my windows 10. None worked for me.

Anyone from Fiio, could you please give us some reply??? My first dac and this is very disappointing.

FiiO

Dear friend,

Have you ever tried to use another usb cables and ports? And can the K3 work fine in other computer instead? Please send email to support@fiio.com with your receipt attached.

Best regards

urba1n

Also same problem with MacBook Pro 13" 2018 on MacOS X (Mojave 10.14.4) - K3 doesn't output anything until being reconnected after even short standby. Tried different USB ports - didn't help as well.

FiiO

urba1n replied at 2019-5-21 16:26
Also same problem with MacBook Pro 13" 2018 on MacOS X (Mojave 10.14.4) - K3 doesn't output anything ...

Dear friend,

You could turn off the K3 using the volume button first, then turn it on again after restart your PC to see if it helps?

Best regards

urba1n

FiiO replied at 2019-5-22 17:47
Dear friend,

You could turn off the K3 using the volume button first, then turn it on again after ...

That definitely helps, but it is less convenient.

FiiO

urba1n replied at 2019-6-25 18:50
That definitely helps, but it is less convenient.

allx

Is there a possibility of firmware update that will solve this issue? If not I probably will buy some other DAC that does not require switching it on every day.

Stanzilla

I have the same issues here, after every Windows restart, I have to unplug and and replug for Windows to see the K3

Siesta410

I have this same issue. I've had it since I purchased back in January and I always got around it by turning it off and on and it would resolve the issue but it is an inconvenience and can't possibly be that hard to fix.

It's especially frustrating because if I forget to do it and start up a game I have to close out of the game, turn the amp off and on, and start the game again.  

Stanzilla

Any help here, @FiiO?

12characters

I managed to solve my K3 USB2 mode disconnect / dropping out problem on macOS.

On my MBP 2015, I moved the K3 to the right side USB 3 port which then worked great.
Left side USB3 port did not offer a stable enough connection. It appears it's a clock related problem.

On my Mac mini I tried moving the K3 around on different USB 3 posts but same problem all the time.
Until I connected it to my monitor which have an built in USB2 hub.
Then the K3 is running perfect for ever.

If you have a USB2 hub, connect it and try running the K3 over it.

jjf5

Hello,

I also encountered this issue with K3. There is definitely problem in its USB module/firmware.
However I partially resolved it with this script, that I scheduled to run after every wakeup (by windows task scheduler). It searches for USB Fiio and if not found resets the hub (USB port) where it runs.

@echo off
devcon status "USB\VID_2972&PID_0047" | find "running"
if errorlevel 1 goto Restart
echo Fiio USB Device already working
goto End

:restart
devcon disable "USB\VID_05E3&PID_0608"
nircmdc wait 1000
devcon enable "USB\VID_05E3&PID_0608"

:end

Your device ID can be different.

But yes, Fiio ought to fix the firmware, as this is the only USB DAC exhibiting this behaviour that I had.

Zadak

Incredible this is not being fixed, i just bought the Fiio K3 thinking it's gonna be great.

Having to turn it off and on again EVERY TIME i reboot is insane! I will have to return this sadly

Stanzilla

Yeah I guess this is the last time i bought something from fioo

FiiO

Dear friend,

According to the feedback from the engineer, this problem is related to some of the computer. They will try to check again for this problem.

Best regards

jjf5

Hello,

I also noticed the situation gets better when I disable selective suspend. And use this script after wakeup. Difference to previous script is that it searches for Fiio device and only when it is not running it restarts the USB port where it is connected, and repeats the process if the first restart is not successful.

Script needs nircmdc and devcon, both can be downloaded for free.

This way it works in majority of cases.

@echo off
devcon status "USB\VID_2972&PID_0047" | find "running"
if errorlevel 1 goto Restart
echo Fiio USB Device already working
goto End

:restart
devcon restart "USB\VID_05E3&PID_0608"  
nircmdc wait 1000
devcon status "USB\VID_2972&PID_0047" | find "running"
if errorlevel 1 goto Restart2
goto end
:restart2
nircmdc wait 1500
devcon restart "USB\VID_05E3&PID_0608"  
:end

12characters

On macOS I was first forced to repetedly use the right side USB port on my MacBook Pro 2015.

But it seems that after a reboot or shutdown, the K3 always get audio driver clock timing errors and sound halts. But it always works after I swop USB port. It does not matter which port I swop from or to.
Swopping ports help me.

As so many of us are suffering from the same type or kind of problems - simply putting the blame on the computer feels a bit sad.
What makes the K3 so special that no other DAC suffers these kind of trouble?