Liberty 3 Pro issues from retail unit

Hi
Just got my 3 Pro and found a few issues

  1. Firmware 03.36 showing as latest in app but didn’t allow me to enable LDAC so stuck with aac
  2. Hear ID took 2 or 3 goes before i could complete. Sometimes didn’t play sound or got stuck
  3. ANC test took several goes as that just locked up the app or disconnected the buds from my phone. Crash maybe?

My unit is from Amazon UK so this is retail
Thanks

My phone is Samsung galaxy s21 ultra running latest firmware on Android 11. Latest soundcore app from play store

Fastest is put in email service@soundcore.com

In email including proof of purchase and email. Never put either of those here as it’s Internet readable.

They read email far faster than here. Their email response <24 hours their community response < 4 days. Friday now so email is critical for a quick reply.

And yes, the fact they link in their app to community they do not read, is an issue to the side. Marketing and support banging heads.

You have something unique going on as reviews show LDAC enabled. e.g.

Agree with @The_Professor. Although @winfred does roam around.

We do not have as we wait for the kinks to be worked out first.

If similar to other buds, I think Ldac is located on the cog wheel of the BT area for those earbuds

This is the Liberty air 2 pro. A guess on that question

Nope – for the Liberty 2Pro+ you had to do it in the soundcore app – just never showed the option in bluetooth until you did.


This is a video of trying to enable it in the app – i’m tapping the little radio button next to the LDAC option and it just pops up saying you need to update software but there’s no update

And for reference i’ve asked Soundcore via:
Twitter, Instagram, facebook, this forum, email

Tying these together

Support is on it, known issue.

1 Like

@Duane_Lester Sorry for the inconvenience. Please note that we’ll contact our related team to double confirm the issue for you at our earliest.

Hello, we appreciate your support on Soundcore Liberty 3 Pro. In this case, please open the Soundcore APP, and download the latest firmware version directly to see how it works.

If it doesn’t help, no worry, please reach out to "service@soundcore.com" by detailing the issue, our technical support will help you further. We always stand behind your product and are ready for help.

Hi
Yeah. Issue is resolved in that area with the update
Still a slight issue in the 2 hearing tests. Tend to have to do that 2 times to get it to complete

2 Likes

Glad your issue solved.

Received my L3P’s yesterday…so far, I have run into a couple issues:

  1. Transferring between devices when using multipoint. It seems to be a bit clunky as there is a delay in the audio after switching to a device.

  2. For some reason, I can successfully pair them to my laptop (Dell Precision 3551), but I’m not getting any audio from the laptop.

Do you think it is like this?

1 Like

You nailed it!!! Thank you so much…I’ve wanted so much for them to be perfect and now they are. Multipoint functionality was the only issue I was having, now it’s working seamlessly.

So after reading your Q30 review, I went back and un-paired/re-paired my L3P’s with my laptop and iPhone 11 Pro Max. As suggested in your review, when re-pairing, this time I paired my laptop 1st, then my phone…worked immediately! I can now switch back and forth with no issues, even taking calls while connected to my laptop. Hopefully, Soundcore can possibly address this with future updates, or like you stated in your review, this may just be the hand we’re dealt in having to follow this process in order to get the different BT versions to work together. Thanks again!!

1 Like

I figured they used similar hardware within.

To do multipoint between different bluetooth versions you must either:

  • use an older bluetooth version chipset so every connection is always the older version, or
  • use a chipset which is more expensive capable of running two versions concurrently.

They don’t appear to have done either for these hence why the suggestion.

Good it worked out for you but as you move around, you may find the connection sequence gets swapped so you may have to disconnect from both, turn buds off / on and connect to the oldest first again to make it work again.

I do not think you need to delete pairings once it’s working, you may just need to disconnect, off/on , connect in sequence.

1 Like

After using the multipoint connection feature on my L3P’s for over a week now, I’ve found that it works fine until I get a phone call. After ending a call, I lose audio on both my phone and my laptop. Each device still shows connected, but no audio from either device. Only way it is resolved is if put them back in the case, turn off, turn on BT on PC 1st , then phone after PC makes connection. This has gotten pretty annoying. Hopefully, they can resolve this issue.

Sounds like our old friend BT version. Your phone is BT 5 and your laptop is 4.2?

Yep……BT 5.2, laptop 4.2

So I am guessing but it’s an educated guess.

What I suspect is happening is your connection swap from headphone to headset when the call is made so your headphones then connect in headset profile at BT 5.2. It is then stuck at that and cannot connect back to 4.2, so you have to do exactly what you said of off/on.

I can’t think of a clever workaround for this, it relies on a firmware update to fix it. I’d just ensure email to support so it’s added to their to-do list.

Ironically an older bud on BT 4.2 would not suffer this problem.

I suggest the issue is Soundcore is not testing adequately, it’s like they only test using two BT 5 products not trying different sequences of 4.2 5 5.2 so it’s not detected until you’ve bought it and reported it.

If you didn’t want to wait I suspect if you bought a BT 5.2 bluetooth dongle for your laptop so it keeps on 5.2 the whole time it would then work seamlessly.

BTW what I’m doing is keeping my buds on the oldest version - I’m still using old buds which work as then they always connect at the same version - an old one. I can’t make Soundcore test products properly but I can avoid the causes of their inadequate testing. I also offer myself to do testing, I’d certainly be on this exact issue more than those who connected to their phone and said “sounds great”.

1 Like

Multipoint issue seems to have been resolved with the latest firmware update. :+1::+1: