[iFi audio]

Also whoever writing the marketing words for iFi clearly read this thread, or a damn good engineer

We have our eyes everywhere

 

[FiiO]

@FiiO , your UTWS5 with 1.5 firmware keeps connecting to my phones while it is placed inside its case. After cleaning the pins, the same is still happening. I have my UTWS5 paired with two phones. My Xiaomi POCO F2 Pro and my Samsung Galaxy S23 Ultra. Today, without taking the UTWS5 out of the case at all, it connected to my Samsung phone. Will you do something to fix this issue?

Dear friend,

We will report to the engineer for checking about that. But I am afraid that it may not be a firmware issue. If you don't mind, you could downgrade the firmware for check as well.

Best regards

 

[Altes]

Oh damn the new iFi GO Pod is gonna eat FiiO's lunch. Same hardware (some may see it as better) as UTWS5 but with proper LHDC and LDAC support. If FiiO dont act quick UTWS5 is dead

I don't see what FiiO can do. The GO pod is capable of providing an output voltage of 4V into high-impedance loads, which is many times more than the FiiO UTWS5. In addition, the ifi GO pod claims to have "a silent background with high-sensitivity IEMs".

Really the only thing that can affect purchasing decisions is the price.

 

[MariusAB]

Dear forum members. Has anyone used or is using utws5 with oneplus phones?. I am interested if oneplus really suports lhdc in latest models such as 10 pro or 11. I checked with 10 pro (with android 12 in it) but could not connect with lhdc codec as it constantly was switching to aptx adaptive or without hd soud - to sbc. In developer option even if i checked lhdc codec still going out and back it always was switching to aptx adaptive. So for me seems like oneplus isn't supporting lhdc. Perhaps with newer oneplus 11 and android 13 it possibly was fixed but don't have possibility to check. Perhaps someone has other device that uses lhdc and was able to conect to oneplus 11.

 

[O11111]

Dear forum members. Has anyone used or is using utws5 with oneplus phones?

Rename UTWS5 to something like "Oppo" or "OnePlus". BBK are limiting LHDC to their headphones only based on Bluetooth device name.
I haven't checked that on 10 Pro, but on my 7 Pro that did the trick.

 

[MariusAB]

Rename UTWS5 to something like "Oppo" or "OnePlus". BBK are limiting LHDC to their headphones only based on Bluetooth device name.
I haven't checked that on 10 Pro, but on my 7 Pro that did the trick.

nice trick thanks, i will try this. Really oneplus is playing such games? It isn't very professional looking. So you have to check lhdc in developer options after this renaming or you see from bluetooth menu lhdc?

 

[O11111]

So you have to check lhdc in developer options after this renaming or you see from bluetooth menu lhdc?

Both will work. It's recommended to do pairing once again after renaming just as Android usually caches available codecs

 

[eswng679]

I don't see what FiiO can do. The GO pod is capable of providing an output voltage of 4V into high-impedance loads, which is many times more than the FiiO UTWS5. In addition, the ifi GO pod claims to have "a silent background with high-sensitivity IEMs".

Really the only thing that can affect purchasing decisions is the price.

Does the new ifi product give the option to EQ? if so, that might be deal-breaker for me. I would move on from the @FiiO product line in a heartbeat.

 

[SmitherineBoss]

Does the new ifi product give the option to EQ? if so, that might be deal-breaker for me. I would move on from the @FiiO product line in a heartbeat.

especially since the utws5 had really bad pairing issues when I was using it. I had to go back to the utws3 it got so bad. If there is another option I'd take it in an instant since fiio cant seem to get it under control.

 

[Nick24JJ]

Dear friend,

We will report to the engineer for checking about that. But I am afraid that it may not be a firmware issue. If you don't mind, you could downgrade the firmware for check as well.

Best regards

Not a firmware issue? Do you mean that it can be a hardware issue? :/

 

[O11111]

Not a firmware issue? Do you mean that it can be a hardware issue? :/

It most likely is. What else could it be? State detection (in case/in ear/etc) is the most basic TWS feature one could imagine. And it's certainly one of the parts of firmware which are only touched by Qualcomm (unless vendor wants to mess it up). Bad contact is a well-known problem of pogo pins and there's no solution (except not to use it). BTW are your IEMs big? Maybe they barely fit, therefore UTWS5 are having bad contact to the case. Besides, any pogo pins wear a lot, so it may be the problem as well.

 

[FiiO]

Not a firmware issue? Do you mean that it can be a hardware issue? :/

Dear friend,

Yes, but if you don't mind, you could try again with the older firmware.

Best regards

 

[Ati1979]

I also lost my EQ profile during the night. I didn't charge the case. I put my earphones in and when I took that out my EQ profile has gone. Latest firmware installed.

 

[stephenk1982]

My right UTws5 just stopped working...
Sending them back now...
They lasted one month.

 

[Ati1979]

Also I set the EQ to rap. Once it is ok when I take out the earphones from the case EQ is on and it is set to rap properly as I left those . On other occasions EQ is off. I have to log in the app and turn on manually and set it. So inconsistent.
I would not even try to set and use my own EQ profile until a related firmware upgrade realeased.