[FiiO]

hi @FiiO I have an S8 (oreo, LDAC compatibility) Is the BTR3 configurable to work in LDAC as default? or is there a way to "tell it"

Let me explain why my question. I have the BT-RC cable, which every time i turn on, the S8 uses the APTX codec, which by bad circumstances like bad implementation of the BT in the RC-BT, my body and rf noise, in APTX mode the music shouts of like every second in direct sunlight and like every 5 secs anywhere else, and HAVE to change the codec in the S8 in developer options to AAC (less bandwidth).
Im hoping that since the BTR3 could be more in front of me, and potentially have better implementation, i could use it without a problem. NOW my issue is if the BTR3 will have like "default" codec to connect with.
BTW, you should make a dedicated BTR3 thread with the specs just like you did in the FH5 before its launching

Dear friend,

Yes! There will be RGB indicater showing the current Bluetooth Codec for the BTR3.

Best regards

 

[Marco Angel]

Dear friend,

Yes! There will be RGB indicater showing the current Bluetooth Codec for the BTR3.

Best regards

Thanks @FiiO but my question is:
Is there a way to choose a prefered codec in the BTR3 to connect?? Is really annoying the way im doing with the RC-BT since every time connects with a codec i dont want

 

[fe-lixx]

@Marco Angel You can not only view the codec that's being used at the moment, but also change it to a personal preference, if you have updated your S8 to Android 8.0. Since that version, you simply need to enable the Developer Options in the Settings. Bluetooth Codec is now a setting you can change there without the need of flashing any custom ROMs or other complicated stuff.

This should really be possibly with any Android smartphone running Oreo or higher. It's a part of android now, I haven't heard about a phone that has these settings removed from the Developer Options, I don't even think that's possible. And even with heavy modifications by the manufacturer, it's in their interest that developers can test their apps or third party hardware on all smartphones or tablets (and more exotic hardware like TV boxes etc.) running Android without much hassle, meaning it's in their own best interest to stay away from altering these options.

 

[Marco Angel]

@Marco Angel You can not only view the codec that's being used at the moment, but also change it to a personal preference, if you have updated your S8 to Android 8.0. Since that version, you simply need to enable the Developer Options in the Settings. Bluetooth Codec is now a setting you can change there without the need of flashing any custom ROMs or other complicated stuff.

This should really be possibly with any Android smartphone running Oreo or higher. It's a part of android now, I haven't heard about a phone that has these settings removed from the Developer Options, I don't even think that's possible. And even with heavy modifications by the manufacturer, it's in their interest that developers can test their apps or third party hardware on all smartphones or tablets (and more exotic hardware like TV boxes etc.) running Android without much hassle, meaning it's in their own best interest to stay away from altering these options.

Hi! @fe-lixx
thanks for your support but i explained that this solution you tell is the annoying thing i have to do every time i turn on the RC-BT.
Maybe i have to explain a little more:
In the S8 (OREO) the BT is always on as it connects to my watch.
About the RC-BT cable, since day one my music disconnects every second or so when having the S8 in my right pocket. I asked it in these tread and some one recommended the same as you.
Thats how i saw that every time i turn on the RC-BT, it connects at least to my S8 in APTX. @FiiO told me to change it to AAC as it uses less bitrate, and ive been doing this procedure at least 3 times a day to have a more stable connection (and it doesent btw). And its really annoying to have to do this 3-5 times a day.
I read the ES100 can be configured to connect every time with one codec as default. in my case i would use LDAC. So thats what im asking, if the BTR3 can be configured this way?

 

[JamesFiiO]

Hi! @fe-lixx
thanks for your support but i explained that this solution you tell is the annoying thing i have to do every time i turn on the RC-BT.
Maybe i have to explain a little more:
In the S8 (OREO) the BT is always on as it connects to my watch.
About the RC-BT cable, since day one my music disconnects every second or so when having the S8 in my right pocket. I asked it in these tread and some one recommended the same as you.
Thats how i saw that every time i turn on the RC-BT, it connects at least to my S8 in APTX. @FiiO told me to change it to AAC as it uses less bitrate, and ive been doing this procedure at least 3 times a day to have a more stable connection (and it doesent btw). And its really annoying to have to do this 3-5 times a day.
I read the ES100 can be configured to connect every time with one codec as default. in my case i would use LDAC. So thats what im asking, if the BTR3 can be configured this way?

In any bluetooth system, the code is decided by the transmitter but not the receiver, so you still have to choose SBC/AAC/APTX in your smartphone. and there should be option for you to choose .

 

[fe-lixx]

Hi! @fe-lixx
thanks for your support but i explained that this solution you tell is the annoying thing i have to do every time i turn on the RC-BT.
Maybe i have to explain a little more:
In the S8 (OREO) the BT is always on as it connects to my watch.
About the RC-BT cable, since day one my music disconnects every second or so when having the S8 in my right pocket. I asked it in these tread and some one recommended the same as you.
Thats how i saw that every time i turn on the RC-BT, it connects at least to my S8 in APTX. @FiiO told me to change it to AAC as it uses less bitrate, and ive been doing this procedure at least 3 times a day to have a more stable connection (and it doesent btw). And its really annoying to have to do this 3-5 times a day.
I read the ES100 can be configured to connect every time with one codec as default. in my case i would use LDAC. So thats what im asking, if the BTR3 can be configured this way?

I see, sorrry that I didn't check your earlier posts.

I have the S8 myself and I'm using it with the BTR1. Luckily, I didn't have any issues with audio drop-outs so far. By default, a Bluetooth audio receiver tells the pairing device which codecs it "understands", and the pairing device/sender (S8 in our case) then decides based on this information (and unfortunately not dynamically also by available bandwidth, depending on range or distortion in the signal due to other devices, a bad microwave oven or whatever) which codec to use. For devices that support aptX, that's the codec the S8 will choose by default. You can override this selection or "decision" by selecting a different codec manually in the Developer Options. That selection is not being saved individually for every paired device or reset each time you connect a paired device. If you select SBC, the one codec that all A2DP-able Bluetooth devices need to know, that's the codec that will always be used for any device. If you select AAC, it should be exactly the same, and the S8 should use AAC for all devices using A2DP, or, if not supported, fall back to the codec it knows all devices support: SBC.

So it's not clear to me, why you have to change your selection back to AAC again each time you connect your device?! If you set it to AAC, it should stay at AAC, and in the worst case fall back to SBC. But I don't see a scenario where it should reset itself to use aptX...

I don't believe it's possible for third party apps to select the audio codec used for Bluetooth, even on rooted devices, so I doubt you're using something that messes with the settings.

Really strange, and I don't have an explanation for the behavior of your S8 right now. When I'm back home, I can do some testing with my S8 and the BTR1 to confirm what I said is really the case, but I'm pretty sure. Maybe someone else with an S8 (or really any Android device with Oreo or newer) can chime in in the meantime.

/edit: Whoops, didn't see FiiO's post. But they confirm the basis of what I mean: The transmitter (what I called sender) determines the codec that it uses to send the audio. The receiver can only say "Hello, I can understand SBC, AAC, aptX and aptX HD" or whatever during the connection process, but it can't force a transmitter to use a certain codec - unless it behaves in a non-standard way or doesn't transmit information about additional codecs, then always SBC will be used.

That's unrelated to the question, why your S8 doesn't save the setting to use AAC. It's possible, but I don't think that's how I've observed its behavior, that AAC is being used as long as you don't connect a device that doesn't support AAC. In theory, it could be (but I'm pretty sure it's not, as that would also make testing for developers very tedious) that every time you connect a BT device that doesn't support AAC, so your AAC setting and what the device is telling your S8 are in conflict, that the S8 defaults back to its "standard"-auto value and no specific codec, meaning that the next time you connect an aptX-cabable device, aptX will be automatically used again... But that's just a theory.

 

[rantrile]

Via what e-mail I could contact your head engineer?

You are referring to differences with how remote signalling is implemented in Android & iOS earphones, right?
Certainly the implementation I'm expecting should be to support both as it was done by 1more.
https://www.amazon.com/1MORE-Earphones-Headphones-Resolution-Fidelity/dp/B01A7G35S0

 

[Marco Angel]

I see, sorrry that I didn't check your earlier posts.

I have the S8 myself and I'm using it with the BTR1. Luckily, I didn't have any issues with audio drop-outs so far. By default, a Bluetooth audio receiver tells the pairing device which codecs it "understands", and the pairing device/sender (S8 in our case) then decides based on this information (and unfortunately not dynamically also by available bandwidth, depending on range or distortion in the signal due to other devices, a bad microwave oven or whatever) which codec to use. For devices that support aptX, that's the codec the S8 will choose by default. You can override this selection or "decision" by selecting a different codec manually in the Developer Options. That selection is not being saved individually for every paired device or reset each time you connect a paired device. If you select SBC, the one codec that all A2DP-able Bluetooth devices need to know, that's the codec that will always be used for any device. If you select AAC, it should be exactly the same, and the S8 should use AAC for all devices using A2DP, or, if not supported, fall back to the codec it knows all devices support: SBC.

So it's not clear to me, why you have to change your selection back to AAC again each time you connect your device?! If you set it to AAC, it should stay at AAC, and in the worst case fall back to SBC. But I don't see a scenario where it should reset itself to use aptX...

I don't believe it's possible for third party apps to select the audio codec used for Bluetooth, even on rooted devices, so I doubt you're using something that messes with the settings.

Really strange, and I don't have an explanation for the behavior of your S8 right now. When I'm back home, I can do some testing with my S8 and the BTR1 to confirm what I said is really the case, but I'm pretty sure. Maybe someone else with an S8 (or really any Android device with Oreo or newer) can chime in in the meantime.

I was playing with my S8 in dev options, just to see the changes, and indeed, by just turning off the RC_BT and turn on again, the ACC codec goes to aptx as it connects. (wish i could have another cellphone to film it).

Good to know you dont have any issues (if not i would stay with aptx at least). Where do you wear your btr1?

 

[Amber Rain]

@FiiO

From the few available pictures of the BTR3 it seems that the headphone socket is on the bottom of the unit. Could you confirm if this is correct?

I would be disappointed if it is, as this would make it inconvenient to use.

 

[FiiO]

@FiiO

From the few available pictures of the BTR3 it seems that the headphone socket is on the bottom of the unit. Could you confirm if this is correct?

I would be disappointed if it is, as this would make it inconvenient to use.

Dear friend,

Yes, the headphone jack of the BTR3 is on the bottom of the unit. Why would you consider it as inconvenient?

Best regards

 

[Amber Rain]

Dear friend,

Yes, the headphone jack of the BTR3 is on the bottom of the unit. Why would you consider it as inconvenient?

Best regards

Because I am likely to clip the BTR3 to my shirt or shirt pocket and I usually use (your) straight cable which means that the cable travels down and then back up which means that BTr3 won't be as secure or comfortable as the btr1.

 

[FiiO]

Because I am likely to clip the BTR3 to my shirt or shirt pocket and I usually use (your) straight cable which means that the cable travels down and then back up which means that BTr3 won't be as secure or comfortable as the btr1.

Dear friend,

When the USB port and the headphone port are both in the same side, there would be larger space for the battery with bigger capicity. Beside, the Bluetooth design require that as well. For clipping the product in the gusset，the headphone port in bottom would be more suitable as well.

Best regards

 

[caprimulgus]

FYI, for those that were asking earlier, Fiio tech support responded to me on the Fiio forums saying that BTR3 will support both AptX-LL and LDAC (in addition to AptX, AptX-HD, AAC, SBC, etc).

http://www.fiio.me/forum.php?mod=viewthread&tid=43236&extra=page=1

I know AptX-LL is probably not important for most people mainly using it to listen to music, but for those of us that will use it for TV & gaming, this is good news!

(Not sure why the official Fiio account has not confirmed this information here)

 

[Koolpep]

This is great news for us indeed!

 

[Arasthel]

@FiiO

Will the BTR3 support USB Audio Class 1 or 2?
Thank you