[felix3650]

Has anyone noticed the storage case discharging when the FW5 is not in use?
Like charge the case (with the IEMs inside), leave it a couple days without use and when you open the case, only 3 lights are on.

Or am I missing something?

 

[helmutcheese]

I highly doubt that even with the FW5 quirks for now.

Not saying I did not like that sound, but it is heavily shaped and if you listen to lower quality music on the FW5 it will sound worse, as they are purer.

1More sound like 1More (very dynamic) I had the older 1MORE True Wireless ANC (bellow) then the Piston Buds but no way I would even try the EVO's with the feedback on Amazon UK/US.

The SQ will be more about the actual speakers etc inside not the codecs.

 

[helmutcheese]

Has anyone noticed the storage case discharging when the FW5 is not in use?
Like charge the case (with the IEMs inside), leave it a couple days without use and when you open the case, only 3 lights are on.

Or am I missing something?

I will keep an eye on it, as it uses the LID as the power switch it so should not happen, this happen to my SoundPeats H1 Premiums, takes like 5 days and dead.

 

[helmutcheese]

 

[felix3650]

I will keep an eye on it, as it uses the LID as the power switch it so should not happen, this happen to my SoundPeats H1 Premiums, takes like 5 days and dead.

Seems like it's working fine now. I did reset the IEMs, placed them in their box (2 leds on) and since the last time I posted (2 days ago), it still shows 2 leds on. Oh well

 

[SynaestheticA]

Alright first issue and it's a weird one:-

My entire phone has lost the ability to transmit codecs above SBC through the FW5.

I spotted the codec part of the app and deselected the AAC option

Doing this disabled all codecs other than SBC and changed the codec displayed at the top of the app to SBC

Messing around in the codec section that was listed as aptX Adaptive or some derivative of aptX

Now even in my Bluetooth settings I don't see aptX audio show up as you can see I get with the ZE8000.

When I connect the FW5 I get a "connected" message then straight after a "Disconnected" message however, the bud remains connected and capable of playing music. Also when I originally changed the codec options in the app I got the same "Disconnected" message and then the change of codec.

If I go to phone setting to select any other codec after I leave the setting page it defaults back to SBC.

Anyone else @FiiO @FiiO Willson any suggestions? I've reset the app and restarted my phone.

 

[helmutcheese]

I have had some similar weird issues.

If latest App/FW do a factory reset for the earbuds in the App then for good measure do the same on the actual earbuds (power off and then hold both RAISED buttons for 5 secs) and kill your phones BT remove the FW5's and then clear the BT cache/reboot and then re-pair

 

[SynaestheticA]

I have had some similar weird issues.

If latest App/FW do a factory reset the earbuds in the App then for good measure do the same on the actual earbuds (power off and then hold both RAISED buttons for 5 secs) and kill your phones BT remove the FW5's and in clear the BT cache/reboot and then repair

Booya ty

 

[FiiO Willson]

Alright first issue and it's a weird one:-

My entire phone has lost the ability to transmit codecs above SBC through the FW5.

I spotted the codec part of the app and deselected the AAC option



Doing this disabled all codecs other than SBC and changed the codec displayed at the top of the app to SBC


Messing around in the codec section that was listed as aptX Adaptive or some derivative of aptX

Now even in my Bluetooth settings I don't see aptX audio show up as you can see I get with the ZE8000.



When I connect the FW5 I get a "connected" message then straight after a "Disconnected" message however, the bud remains connected and capable of playing music. Also when I originally changed the codec options in the app I got the same "Disconnected" message and then the change of codec.

If I go to phone setting to select any other codec after I leave the setting page it defaults back to SBC.

Anyone else @FiiO @FiiO Willson any suggestions? I've reset the app and restarted my phone.

Hello,
The software settings of FW5 are self-adapted according to the priority format of the phone.
If you have two devices connected to your phone, the phone will adapt to all of them, and in the same Bluetooth format.
That means if you have a Bluetooth headset that only supports AAC and another that only supports SBC, the phone will automatically jump to SBC.

Can you fix the output format of the phone via developer mode? Or confirm if you have more than one device connected?

Also, if you have an Android phone, it would be better to use LHDC

 

[helmutcheese]

Since when do most Android phones have LHDC?

And your wrong about the Codec in Multipoint, it connects to my phone via aptX and my Creative BT-W4 Dongle via aptX Adaptive at same time, the FiiO App and the Dongle App/ onboard LED all confirm this.

 

[lordearl]

Since when do most Android phones have LHDC?

They don't...but they should, and the revolution is coming!

 

[SynaestheticA]

Hello,
The software settings of FW5 are self-adapted according to the priority format of the phone.
If you have two devices connected to your phone, the phone will adapt to all of them, and in the same Bluetooth format.
That means if you have a Bluetooth headset that only supports AAC and another that only supports SBC, the phone will automatically jump to SBC.

Can you fix the output format of the phone via developer mode? Or confirm if you have more than one device connected?

Also, if you have an Android phone, it would be better to use LHDC

Hey no multipoint beinf used. Issue was resolved with instructions provided by Helmutcheese above.

I can change the output format on the android, currently set to default (determined by device)

I'm happy with aptX tbh. Can try lhdc but just can't control from app.

 

[helmutcheese]

They don't...but they should, and the revolution is coming!

That does not change his statement being a moot point for 99% of users now.

 

[felix3650]

They don't...but they should, and the revolution is coming!

That "revolution" should've come quite some time ago lol..
Only some mfgs support LHDC (Xiaomi, Oppo and their sub-brands like Redmi, Oneplus, Vivo etc) and not all their models do.. even then the support is kinda sketchy..
Big brands like Sony push for LDAC, Samsung for SSC so I don't see LHDC getting much traction. Plus you have LC3/LC3plus HR in the mix now..

 

[helmutcheese]

EarFun just released a pair of earbuds with LC3 (I posted in main TWS thread).