yep, same…Fit test doesn’t work. I tried 4 different devices, everytime I got same screen.
LA2P and new Soundcore app
1 Like
On the one hand that’s not great but I’m a little relieved it’s not that my phone is too old or something (it’s not even that old anyway, a couple of years old).
If Support get several messages about it then hopefully they’ll look into it soon. Seems like it doesn’t affect everyone though so maybe it is certain Android versions.
Think I have managed to get the right fit now through trial and error though! I initially thought the medium ones it came with were fine but then my ears hurt after using them for a bit so I switched to the small and it actually feels like it sealed now! Have never tried any type of wireless ones before so a bit of a learning curve… 
Android app got updated to 2.6.0 here. But the fit test still hangs on my Lenovo Yoga Smart Tab while being fine on my Samsung Galaxy A71, both running Android 10.
This is odd, but only solution is to find between us what is same/different and eliminate it to a repeating common difference.
A specs search may be a hint as to the issue. The Smart Tab is showing as 4.2
The Samsung is BT 5
But then
Is BT 5 so, it’s not a BT version issue.
Look at Android App permissions on each device, see if both have all they have asked for enabled.
3 Likes
I already checked everything, and did permissions to all… my phone is up to date…I think it is app issue or some drivers from la2p
1 Like
Samsung Galaxy A71, Android 10, permissions: Mic only
Fit test works.
Lenovo Yoga Smart Tab, Android 10, Soundcore App permissions: Location, Mic, Storage, Phone
Fresh reboot. Fit test hangs.
My phone is an LG V30, Android 8 but Bluetooth 5 and the fit test hangs with one piece of music playing then silence and a full blue circle around the word testing from the start as others have described.
Checked permissions also and doesn’t make any difference (location was off but no change either way).
1 Like
Yes, that is where my non-fit-test-working device is hanging as well.
If it didn’t hang you would have an 1 second delay after the sound stopped playing and then see something like this:
1 Like
This is all the signature of its just buggy, no other hypothesis holds.
Is there a debug mode for the app to email Soundcore diagnostics so they can find which lines of code they wrote are broken?
Otherwise, that’s then a feature request, as otherwise as Soundcore makes more complex products, more bugs will just appear.
Used to be called an “instrumented” version or #DEBUG=1 in code.
Please note that this issue is caused by the compatible issue of Timer app on android phones. And it’s resolved by the upgrade version v2.6.1. Please have a try and see if there is any difference.
4 Likes
I am still on 2.5.9 version… refreshing playstore last 2 days… sad
I can understand a phased rollout of new features but not of new bugs.
If 2.6.1 fixes a bug you should not be holding it back. Are you aware it is being held back? I can get it to upgrade using a Google UK account but not a Google USA account, so may be geo versioned.
Screenshot from two Google accounts look at the what’s new. You’ve messed up your
https://support.google.com/googleplay/android-developer/answer/7550024?hl=en-GB
If anyone cannot wait for Soundcore, then create another google account some other country add that account to your phone then go to the Play app on phone, switch which account then update. When you do this then you will the latest version rolled out in any country. Useful for banking apps mostly which are not phased rolled out by country but only allowed to be installed in some countries, but it helps fix this while Soundcore fix their end.
1 Like
Is that Google Account tied to UK? You’d knew if you did as it defaults to where you were physically when created the account.
If its a UK account then what Soundcore did is (not tell Yimi) do a phased rollout deliberately. Phased rollout is a very common and good, but you it’s an error on their part in their Google Play account to delay a bug fix in a phased release, i.e. you are meant to have production and beta, in phased rollout and bug fix in beta rollout, so you’d have production and some beta1 replaced with some beta2 etc until betaX version is stable and then release it as production for everyone. What they seem to have done is a fail a basic CI/CD method of release 3 streams of different beta meaning there are 3 versions out there. Yikes.
https://support.google.com/googleplay/android-developer/answer/9845334
1 Like
Yes it’s a UK account automatically as I’m British and live in the UK. Google Play Store is up-to-date as well, just double-checked!
It says the last update they made was bug fixes but that was before I got the App. Literally just downloaded the App a couple of days ago when my LA2Ps arrived!
Yes, if they already knew about it then they should have sorted it if it’s ready to roll out. Surely they know it’s important for brand reputation… I know Anker but this is the first Soundcore product I’ve had so this is my first impression of them and there will be plenty of others like me.
Of course everything else is working but I’m still not 100% certain I have the right fit and I can’t check until they fix this! It affects the user experience a lot.
2 Likes
Best to wait for Soundcore to fix this.
There are workarounds to share latest APK but the risk in general in a public forum is not worthwhile. Just wait. Probably Soundcore will fix on Monday.
@The_Professor Yes, I’ll do that! With it being one of the products they’re pushing the most, they’ll probably sort it out soon. Thanks very much for your help though!
Going to check mine this weekend on Android device… phone and tablet… I’ll stop back I’m to reference all of the hints and help, and whether I meet the same fate…
I hope they will fix it asap. I have issue with the right bud, so need that feature to check.