Locus Wear app not detecting Locus 3 Pro/Classic again

virtualdj shared this question 2 months ago
Answered

Hi, I have the same issue that I've posted HERE a year ago: the Wear app doesn't detect the smartphone app to remote control it.

This time I'm using Locus Map Classic v3.70.17 on the smartphone (with Android 13) and v1.6.0 on Wear OS. The beta version links at https://bit.ly/lmVersionsTest doesn't seem to contain v3.70.x anymore , so how can I have the watch to detect the Locus app on the smartphone like I did before?

Thanks.

Best Answer
photo

Hi, do you also have Locus Map Watch installed on the phone? It is necessary as a mediator app between the watch app and Locus Map on the phone.

This comment is in trash! Restore

Replies (3)

photo
1

do you have the beta?
i cant download it

This comment is in trash! Restore
photo
1

I have the the 2 versions listed above, but the app doesn't say "beta" so I think it's not a beta.

But the one above doesn't provide v3.x versions like it did previously.

This comment is in trash! Restore
photo
photo
1

Why has the question marked as answered? There's no solution at the moment...

This comment is in trash! Restore
photo
2

Hi,

We no longer produce beta versions of Locus Classic. We only produce production versions that are available on https://bit.ly/lmVersions. The latest version available is 3.70.20.

This comment is in trash! Restore
photo
1

Hi Michael , thanks, actually I didn't really need the beta, but whatever version that is detected by the Wear OS app to remote control Locus Maps Classic.

The file

ClassicGooglePlay_3.70.20_1140_release.apk
available in the link you provided worked perfectly!

I don't know why the Google Play Store didn't provide an update to my version v3.70.17, but anyway upgrading to v3.70.20 manually worked.

Thanks again!

This comment is in trash! Restore
photo
1

Version 3.70.17 is the last approved by Google Play. The newer versions are not so they can only be distributed from our own storage.

This comment is in trash! Restore
photo
1

Ah, OK, I was right then. Good to know, thank you!

This comment is in trash! Restore
photo
1

Hi Michael, it seems v3.70.21 is not detected by the Wear OS Locus app (again). Should I open a new ticket here?

This comment is in trash! Restore
photo
1

Hi, that's not necessary. I asked the devs if anything changed in v. 21.

This comment is in trash! Restore
photo
1

> I asked the devs if anything changed in v. 21.

Something has to be changed, because the Wear OS app doesn't want to talk with the smartphone counterpart (it doesn't see it as installed).

2ba31d27878bb71e3207eec0ff800cc2caacde1644b981a0dc2b2e7af0b558eb

This comment is in trash! Restore
photo
1

Hi,

according to the devs, Locus Classic 3.70.21 and Locus Map Watch 1.6.0. for both the mobile and the watch haven't been altered regarding their mutual connectivity. The problem should be elsewhere. Please make sure both apps are excluded from battery optimization and have all required system permissions, especially access to nearby devices.

This comment is in trash! Restore
photo
1

Mm, weird! I just upgraded the smartphone app version due to the issue of the backup, but it was working with the previous 3.70.x.


I'll try to reinstall the watch APK and let you know if it solves, but I didn't change anything: permissions were already granted and battery optimisation has been excluded both on the smartphone and watch for Locus apps.

This comment is in trash! Restore
photo
1

Hi Michal, I've uninstalled Locus Map Watch and started from scratch... Nothing changed!

See the attached video: the Wear app doesn't even ask for any permissions after install, it just doesn't detect the Locus app on the smartphone and stops there, even though I was running Locus on the smartphone when taking this screen recording.

0b182f1c7ef3988f393efbffa644775250b95cb4ccfee59567e8501a31d27f4e

Notice I never had any issue with the two, apart when you pushed a new version that didn't detect the counterpart. I didn't upgrade my smartphone OS (I'm on Android 13) and battery optimizations have alwayes been turned off. Please ask your developers again, because something has to have changed comparing to the previous version.

I've tried running logcat on the watch and the only line that seems interesting is this one:

10-31 14:28:21.979 32632 32632 D LocusWearActivity: verifyConnection(), API connected: false, isNodeConnected: true, deviceAppInstalled: TRUE
10-31 14:28:22.042 32632 32632 D WearCommService: onConnected(null)
... don't know if it helps.

This comment is in trash! Restore
photo
2

Hi, do you also have Locus Map Watch installed on the phone? It is necessary as a mediator app between the watch app and Locus Map on the phone.

This comment is in trash! Restore
photo
1

Yes, I had it, not in the drawer but listed in the installed apps.

85e1b85ed23f86ab6fbd964ed45d099116b7f30f5648f250b772b1a896fe88d5

However, when I said I reinstalled the Wear OS app in the previous post, as you might have seen from the video I used the Play Store on the watch directly. I didn't touch the Wear for Locus Map app on the smartphone, which was already installed (screenshot above).

So I've just tried uninstalling Wear for Locus Map as well and ensure that it installed the version for Wear OS again. Apparently this eventually worked!

This is the new adb log:

11-02 18:35:26.682 10462 10511 D LocusWearActivity: verifyConnection(), API connected: true, isNodeConnected: true, deviceAppInstalled: TRUE
11-02 18:35:26.682 10462 10511 D LocusWearActivity: verifyConnection(), result: false, isMakeHandshakeOnStart: true, isHandShakeReceived: true, isInitialRequestReceived: false
11-02 18:35:26.685 10462 10511 D LocusWearActivity: verifyConnection(), API connected: true, isNodeConnected: true, deviceAppInstalled: TRUE
11-02 18:35:26.685 10462 10511 D LocusWearActivity: verifyConnection(), result: true, isMakeHandshakeOnStart: true, isHandShakeReceived: true, isInitialRequestReceived: true
So even though I don't understand why it broke without me doing anything... it's working now, following your advice, so thank you very much!

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!