[ccrys]

How is the microphone quality especially in noisy medium ?
I'm using for calls wf-1000xm3 and the mic quality is very bad in noisy environment.

 

[ken1109]

Is there any plan for future Bluetooth hooks after UTWS5?

 

[Lobaba]

I bought fiio fh5 to use with utws5. FH5 both sides with cable works. However, right side FH5 doesn't work with either sides of utws5. Left side FH5 works with both sides of UTWS5.

It is the right side that is too loose and I have no idea how to rectify it. Please advise thank you

 

[potix]

Use the Fiio app to verify that right earhook is connected, if it is not try to reset. Place both earhooks in the case, make sure they are both charging and push the center button for 12 seconds.
I must say it: the audio quality is good but the product quality is a PITA.

 

[emlin]

Use the Fiio app to verify that right earhook is connected, if it is not try to reset. Place both earhooks in the case, make sure they are both charging and push the center button for 12 seconds.
I must say it: the audio quality is good but the product quality is a PITA.

Read what was said. Then try again.

 

[potix]

Read what was said. Then try again.

True. I had deleted my message righ before your reply

 

[Lobaba]

Use the Fiio app to verify that right earhook is connected, if it is not try to reset. Place both earhooks in the case, make sure they are both charging and push the center button for 12 seconds.
I must say it: the audio quality is good but the product quality is a PITA.

Yes connected as right earhook can play music using left FH5.

Reset is done.

This seems to be more of a physical connection issue rather than software.

 

[Spektykles]

Yep, there is some issue with the physical connnection with the earhooks and the case. I had to sometimes put the earhook in the case 2-3 times to make it recognize by the case, or shake it.
I returned my defective UTWS5 to the local distributor and they said they will RMA it back to FiiO. That will take a month. That sucks because they cant exchange me a new one immediately, they said it's FiiO decision to replace me with a new one or not.

 

[dknight12115]

Hello, anyone using the utws5 with samsung smartphone? Since it not support aptx hd/adaptive/ and no LHDC also, so i wonder if it good enough with just aptx or any solution for Samsung smartphone to utilise the utws5? (Shame to SS though, since i use flagship s22 ultra but still struggle with bluetooth codec). Or do we have plan to implement LDAC to the utws5?

 

[C_Lindbergh]

Yes, I also hope we get a new version soon! Hopefully with the latest qualcomm SoC (aptx Lossless/LC3).

Personally id love a much smaller and portable case as well. So it can compete with TWS on portability.

 

[Gulatikirat0]

Hi everyone, I have never owned custom Iems and I am planning to get the Mest mk2 customs. Will custom iems fit the utsw5 case? I am having hard time figuring that out. Thank you in advance for help!

 

[Gulatikirat0]

I just bought this utws5 for my mest mk2.

Does anyone know a carry case with hook for it to attach on belt?
Its abit too big to fit into jean pocket

Hi! Is this the custom version of Mest mk2? I am wondering if the customs will fit the case? I have never owned custom iems. Thank you in advance

 

[charleski]

I got my UTSW5 last week and was excited to see that Xiaomi had added LHDC (listed as 'LHDC_v3' in dev options) to my Pocophone F1 before they abandoned it. I use my earphones almost solely when out walking the dog, with the phone in my right pocket next to my leg.

LHDC worked fine for the first couple of days, but then I started to notice odd dropouts - I would get bizarre tonal shifts, as if certain frequency bands were being lost, or I would find that some parts of the spectrum were distorted (especially the treble). Troubleshooting was complicated by the fact that everything is going through Wavelet (which is an essential game-changer), but I was able to verify that Wavelet wasn't causing the problem. Switching sameplerate and bitdepth in dev options seemed to make things a bit better, but I would still get the problem (I left bitrate on auto). I found a BT signal strength meter app and discovered that the signal drops by over 30dB when I put the phone down next to my leg. So it seems that this is a simple result of physical limitations - you can only squeeze so many bits into the signal when over half the power is being absorbed by my body. I turned LHDC off to drop back to AptX and all the problems went away, and that's what I'll use from now on. I'm not too fussed about AptX Adaptive, as I suspect that for my use case it'll simply 'adapt' the bitrate down to the level I'm getting from AptX now.

If I can move the phone away from my body then LHDC works perfectly. I'm listening using it now with the phone just sitting on my desk and range seems fine. I've never tried LDAC or AptX HD, but I suspect they're subject to the same physical limitations, though it's possible they might fail more gracefully.

I note that Fiio's LHDC implementation is listed as 'beta' in the changelog. Maybe it would be worth making the switch down to the lower bitrate more aggressive. It would certainly be nice if you could force transmission to be limited to 48kHz/16 bits, as 96/24 over bluetooth is just a fantasy outside lab conditions (and a waste of time anyway).

 

[potix]

I got my UTSW5 last week and was excited to see that Xiaomi had added LHDC (listed as 'LHDC_v3' in dev options) to my Pocophone F1 before they abandoned it. I use my earphones almost solely when out walking the dog, with the phone in my right pocket next to my leg.

LHDC worked fine for the first couple of days, but then I started to notice odd dropouts - I would get bizarre tonal shifts, as if certain frequency bands were being lost, or I would find that some parts of the spectrum were distorted (especially the treble). Troubleshooting was complicated by the fact that everything is going through Wavelet (which is an essential game-changer), but I was able to verify that Wavelet wasn't causing the problem. Switching sameplerate and bitdepth in dev options seemed to make things a bit better, but I would still get the problem (I left bitrate on auto). I found a BT signal strength meter app and discovered that the signal drops by over 30dB when I put the phone down next to my leg. So it seems that this is a simple result of physical limitations - you can only squeeze so many bits into the signal when over half the power is being absorbed by my body. I turned LHDC off to drop back to AptX and all the problems went away, and that's what I'll use from now on. I'm not too fussed about AptX Adaptive, as I suspect that for my use case it'll simply 'adapt' the bitrate down to the level I'm getting from AptX now.

If I can move the phone away from my body then LHDC works perfectly. I'm listening using it now with the phone just sitting on my desk and range seems fine. I've never tried LDAC or AptX HD, but I suspect they're subject to the same physical limitations, though it's possible they might fail more gracefully.

I note that Fiio's LHDC implementation is listed as 'beta' in the changelog. Maybe it would be worth making the switch down to the lower bitrate more aggressive. It would certainly be nice if you could force transmission to be limited to 48kHz/16 bits, as 96/24 over bluetooth is just a fantasy outside lab conditions (and a waste of time anyway).

LHDC is working fine in my case (with whatever bitrate/samplerate), even better than LDAC on XM4. I get only occasional dropouts or disconnections.
I think it might be related to your phone or your utws5 sample.

 

[charleski]

LHDC is working fine in my case (with whatever bitrate/samplerate), even better than LDAC on XM4. I get only occasional dropouts or disconnections.
I think it might be related to your phone or your utws5 sample.

Walking around with your phone in your pants right next to your leg? As I said, it works fine as long as I can move the phone away from my body.