FiiO BTR3-The World' First Bluetooth Headphone Amplifier, SBC/AAC/aptX/aptX LL/aptX HD/LDAC/HWA (LHDC)
Aug 18, 2019 at 9:44 AM Post #1,486 of 1,870
Replace it there was something obviously wrong.

Just seen this after I replied to the other post so apols for double post. I think you're probably right, but a bit nervous as if I get one the same, Amazon will think I'm trying it on or something! If I have no problems with the UP2, I may try again in future as it was impressive minus that (fairly major) aspect.
 
Aug 19, 2019 at 1:34 AM Post #1,487 of 1,870
What is the sense of having balanced output on small bluetooth device BTR5?
Even the best LDAC codec does not have the quality when advantages of balanced would benefit. On the other hand device has to be much bigger and needs bigger battery without longer play time.
Without balance there would be or much longer playtime or smaller size or both. Sound quality the same.
The only reason may be current balanced headphone connector. But you can buy short 3.5-2.5 conversion cable and no problem.
 
Aug 21, 2019 at 4:00 PM Post #1,488 of 1,870
My Bluetooth combo :)

20190817-190214.jpg
Nice!

Where can I get a 3.5mm coupler just like that one?
 
Aug 21, 2019 at 7:30 PM Post #1,489 of 1,870
Nice!

Where can I get a 3.5mm coupler just like that one?

this one came with the fiio a5

just search "3.5mm jumper" on Amazon
 
Aug 22, 2019 at 6:33 AM Post #1,490 of 1,870
Ok a while back in this thread I tried to update the btr3 with a Mac unsuccessfully. I tried again so I could copy my terminal screen. Here is what I've done, maybe anyone can shed some light:

I'm on high Sierra
Installed dfu util following this link http://macappstore.org/dfu-util/

Put BTR3 in dfu mode successfully:

Computer:~ ****$ sudo dfu-util -l

Password:

dfu-util 0.9
(...)

Found Runtime: [0a12:ffff] ver=2520, devnum=5, cfg=1, intf=2, path="20-2.1", alt=0, name="UNKNOWN", serial="ABCDEF0123456789"

Then ran the update:

Computer:~ ****$ sudo dfu-util -d 0a12:ffff -v -D /BTR3-1.2-0531.dfu

dfu-util 0.9

(...)

DFU suffix version 100

Opening DFU capable USB device...

ID 0a12:ffff

Run-time device DFU version 0101

Claiming USB DFU Runtime Interface...

Determining device status: state = appIDLE, status = 0

Device really in Runtime Mode, send DFU detach request...

Resetting USB...

dfu-util: Lost device after RESET?

Computer:~ ****$


That's it.
Something goes wrong here, but I have no clue what..
 
Aug 22, 2019 at 6:49 AM Post #1,491 of 1,870
Ok a while back in this thread I tried to update the btr3 with a Mac unsuccessfully. I tried again so I could copy my terminal screen. Here is what I've done, maybe anyone can shed some light:

I'm on high Sierra
Installed dfu util following this link http://macappstore.org/dfu-util/

Put BTR3 in dfu mode successfully:

Computer:~ ****$ sudo dfu-util -l

Password:

dfu-util 0.9
(...)

Found Runtime: [0a12:ffff] ver=2520, devnum=5, cfg=1, intf=2, path="20-2.1", alt=0, name="UNKNOWN", serial="ABCDEF0123456789"

Then ran the update:

Computer:~ ****$ sudo dfu-util -d 0a12:ffff -v -D /BTR3-1.2-0531.dfu

dfu-util 0.9

(...)

DFU suffix version 100

Opening DFU capable USB device...

ID 0a12:ffff

Run-time device DFU version 0101

Claiming USB DFU Runtime Interface...

Determining device status: state = appIDLE, status = 0

Device really in Runtime Mode, send DFU detach request...

Resetting USB...

dfu-util: Lost device after RESET?

Computer:~ ****$


That's it.
Something goes wrong here, but I have no clue what..

Could be your usb ports, - perhaps you can try another one? Or if you are using a usb-hub, try directly without the hub?
(I have a Lenovo Thinkpad W541 where this occurs frequently on the usb3 ports, but never on the usb2 ports...)

Edit: You should also capture the last few lines of the command `dmesg` to get more information, or even just `grep USB /var/log/system.log` or `ioreg -b | grep USB` (all of those might require sudo). I'm not sure macos has anything similar to linux debugfs, but that could also shed some light on what happens with the usb device.
 
Last edited:
Aug 22, 2019 at 7:25 AM Post #1,492 of 1,870
Thanks for a quick reply. I tried different USB ports and also usb c directly ( I have a Macbook with only TB3/USB-c ports). These are the last (of many :wink:) lines after the dmesg command:

IOBluetoothHostControllerUARTTransport::SendUART mProvider->enqueueData() failed error=0xe00002d7
**** [IOBluetoothHostController][EnqueueRequestForController] -- SendHCIRequestToTransport failed, error (0xE00002D7) -- kIOReturnOffline
[IOBluetoothHostController][SendRawHCICommand] ### ERROR: EnqueueRequestForController failed (err=e00002d7)
(repeatedly)

012851.829824 dfu-util@: IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control (repeatedly)

012851.835508 FiiO BTR3@14200000: AppleUSBDevice::ResetDevice: <software attempt to RESET>

I'm not sure what this means other than I see a lot of 'failed'..

[EDIT]
I tried a second time, now the last lines are different:

Starting poll type 4
Restarting poll type 4
Command 0x2 completed. inCount: 2 data:0x4Command 0x1 completed. inCount: 2 data:0x1101Command 0x16 completed. inCount: 2 data:0xc0Command 0xa completed. inCount: 2 data:0xf7fdCommand 0xb completed. inCount: 2 data:0xf933Command 0x12 completed. inCount: 2 data:0x18Command 0x13 completed. inCount: 2 data:0xffffCommand 0xf completed. inCount: 2 data:0x2beCommand 0x10 completed. inCount: 2 data:0x1ac7SmartBattery: finished polling type 4


[EDIT2]
and a third time, but now right after I ran the update attempt. I guessed the dmesg command could be something that looks back in recent history of the ports ?

014372.179928 FiiO BTR3@14320000: AppleUSBDevice::ResetDevice: <software attempt to RESET>

Starting poll type 4
Restarting poll type 4
Command 0x2 completed. inCount: 2 data:0x5Command 0x1 completed. inCount: 2 data:0x1011Command 0x16 completed. inCount: 2 data:0x80Command 0xa completed. inCount: 2 data:0x1230Command 0xb completed. inCount: 2 data:0x10b5Command 0x12 completed. inCount: 2 data:0xffffCommand 0x13 completed. inCount: 2 data:0x9dCommand 0xf completed. inCount: 2 data:0x22bCommand 0x10 completed. inCount: 2 data:0x1acaSmartBattery: finished polling type 4
AGC:: WindowServer started pid 157 WS count 3
AGC:: [WindowServer pid:157 mux-aware] starting, non-mux-aware app count 0 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:1f power-state 0 4D idle HDA idle system-state 1 power-level 20:20 connect-change 0
AGC:: [WindowServer pid 157 mux-aware] exiting, non-mux-aware app count 0, runtime: 0:00:00.000
AGC:: WindowServer died pid 157 WS count 2


This last one looks a bit more informative although I have no clue what to do next

PS I tried on another macbook with native USB ports and El Capitan, but same issues. So it does not seem port / os version related.
 
Last edited:
Aug 23, 2019 at 10:06 AM Post #1,493 of 1,870
Ok I also tried to run windows XP in a virtual box, but even that one does not work. I was able to see the btr3 as an usb device, and install the driver. But when I run the wizard it cannot find the blue core model (/ in use by another software). I know a windows pc would fix this, but no friend, colleague or family member has a windows pc, and on the ones that do I cannot install the driver or connect any unknown usb devices for security reasons.. This update thing has taken too much of my time ;-(. Imo Fiio should clearly state on it's website that it cannot be updated with a Mac.
 
Aug 23, 2019 at 4:42 PM Post #1,494 of 1,870
Thanks for a quick reply. I tried different USB ports and also usb c directly ( I have a Macbook with only TB3/USB-c ports). These are the last (of many :wink:) lines after the dmesg command:

IOBluetoothHostControllerUARTTransport::SendUART mProvider->enqueueData() failed error=0xe00002d7
**** [IOBluetoothHostController][EnqueueRequestForController] -- SendHCIRequestToTransport failed, error (0xE00002D7) -- kIOReturnOffline
[IOBluetoothHostController][SendRawHCICommand] ### ERROR: EnqueueRequestForController failed (err=e00002d7)
(repeatedly)

012851.829824 dfu-util@: IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control (repeatedly)

012851.835508 FiiO BTR3@14200000: AppleUSBDevice::ResetDevice: <software attempt to RESET>

I'm not sure what this means other than I see a lot of 'failed'..

[EDIT]
I tried a second time, now the last lines are different:

Starting poll type 4
Restarting poll type 4
Command 0x2 completed. inCount: 2 data:0x4Command 0x1 completed. inCount: 2 data:0x1101Command 0x16 completed. inCount: 2 data:0xc0Command 0xa completed. inCount: 2 data:0xf7fdCommand 0xb completed. inCount: 2 data:0xf933Command 0x12 completed. inCount: 2 data:0x18Command 0x13 completed. inCount: 2 data:0xffffCommand 0xf completed. inCount: 2 data:0x2beCommand 0x10 completed. inCount: 2 data:0x1ac7SmartBattery: finished polling type 4


[EDIT2]
and a third time, but now right after I ran the update attempt. I guessed the dmesg command could be something that looks back in recent history of the ports ?

014372.179928 FiiO BTR3@14320000: AppleUSBDevice::ResetDevice: <software attempt to RESET>

Starting poll type 4
Restarting poll type 4
Command 0x2 completed. inCount: 2 data:0x5Command 0x1 completed. inCount: 2 data:0x1011Command 0x16 completed. inCount: 2 data:0x80Command 0xa completed. inCount: 2 data:0x1230Command 0xb completed. inCount: 2 data:0x10b5Command 0x12 completed. inCount: 2 data:0xffffCommand 0x13 completed. inCount: 2 data:0x9dCommand 0xf completed. inCount: 2 data:0x22bCommand 0x10 completed. inCount: 2 data:0x1acaSmartBattery: finished polling type 4
AGC:: WindowServer started pid 157 WS count 3
AGC:: [WindowServer pid:157 mux-aware] starting, non-mux-aware app count 0 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:1f power-state 0 4D idle HDA idle system-state 1 power-level 20:20 connect-change 0
AGC:: [WindowServer pid 157 mux-aware] exiting, non-mux-aware app count 0, runtime: 0:00:00.000
AGC:: WindowServer died pid 157 WS count 2


This last one looks a bit more informative although I have no clue what to do next

PS I tried on another macbook with native USB ports and El Capitan, but same issues. So it does not seem port / os version related.

Ah, the computer I use most often for firmware upgrades is a Lenovo T480s, and it has 2 usb-c ports, one with thunderbolt support.
- The thunderbolt port never works properly, - I have to plug it into the other port to get things to work (also applies to some external usb storage, it just keeps resetting the connection...)

As far as I know the FiiO BTR3 has a usb-c physical connector, but only supports USB2 over that port, so that might be the issue (mind you, the usb3.0 port I connected it to for my fw upgrade worked fine, but the driver detected a usb2 compatible device, not usb3).
Do you have access to something with good old fashioned usb2 ports you can try it on? (sorry, last time I had a macbook was 2012 so I'm a bit in the dark about OS versions and what actual ports the various versions ship with)
 
Aug 23, 2019 at 4:43 PM Post #1,495 of 1,870
Ok I also tried to run windows XP in a virtual box, but even that one does not work. I was able to see the btr3 as an usb device, and install the driver. But when I run the wizard it cannot find the blue core model (/ in use by another software). I know a windows pc would fix this, but no friend, colleague or family member has a windows pc, and on the ones that do I cannot install the driver or connect any unknown usb devices for security reasons.. This update thing has taken too much of my time ;-(. Imo Fiio should clearly state on it's website that it cannot be updated with a Mac.

To be fair they only state they support windows, right? So if we can get it working unofficially with other platforms that's just a bonus for us, but not something we can expect...
 
Aug 24, 2019 at 9:54 PM Post #1,497 of 1,870
Don’t put this in your pockets with a coin.

Yeah, mine is pretty scratched/worn from very gentle storage(no coins) in my pocket when it's not in use... :/
Then again, I only need the blinking colour codes to see it turns off properly, or to identify the codec, so it's not that big of a deal in practical terms, but ofc sucks from an aesthetic point of view...
 
Aug 27, 2019 at 3:34 AM Post #1,498 of 1,870
FiiO Stay updated on FiiO at their sponsor profile on Head-Fi.
 
https://www.facebook.com/FiiOAUDIO https://twitter.com/FiiO_official https://www.instagram.com/fiioofficial/ https://www.fiio.com support@fiio.com
Aug 27, 2019 at 5:39 PM Post #1,499 of 1,870
Anyone having issues with hwa not working with Huawei mate 20 pro.
Updated mine to the latest a few weeks back, and only now noticed i can only select LDAC from developer options.

Edit - Just seen the btr5 ok now I'm in love.
 
Last edited:
Aug 28, 2019 at 4:36 AM Post #1,500 of 1,870
Anyone having issues with hwa not working with Huawei mate 20 pro.
Updated mine to the latest a few weeks back, and only now noticed i can only select LDAC from developer options.

Edit - Just seen the btr5 ok now I'm in love.

Yes, same issue with P20 Pro, was working fine until the new f/w then it broke. Switched to a Shanling UP2 and have no issues.
 

Users who are viewing this thread

Back
Top