Locus Wear app not detecting Locus 3 Pro/Classic anymore

virtualdj shared this problem 29 hours ago
Not a Problem

Hi, I'm a long time user of Locus Map 3 Classic (now with v3.70.16 running on Android 13) and a Galaxy Watch 4 with Wear OS 5 (Android 14, One UI 6.0 Watch) and Locus Wear v1.6.0.

As I'm only using Locus sporadically and especially in the summer time to record hiking paths, I expected to do the same this year, too, but with my surprise yesterday after launching the Wear app this message appeared:

0fd33064aac98e1b093efa6dc2bdf3bf9c5e2411df7a4dc5a7639655746c8f8a

It says that Locus Map (i.e. the smartphone app) is not installed or not updated and suggest me to tap on the Update button. Unfortunately, this does not launch Locus 3 Classic but links to the Locus 4 app on the Play Store.

I never had any issue with Locus 3 Classic + Locus Wear Map in the previous "seasons", using the same smartphone and I used Locus Wear Map to pause and resume recording on the smartphone when it was recharging in my backpack. Now this is not possible anymore!

As the Wear Map version has not changed (it's still the v1.6.0 of the 3rd November 2023) I suspect the issue lies on the Locus 3 Classic app, which got updates. Maybe you removed the internal intent link to be recognized with the Wear app counterpart?

I'm starting to suspect this is due to this news:

https://www.locusmap.app/locus-map-classic-last-season/

but as other users there I don't like a subscription model very much and especially if features that worked perfectly like this one are cut down without any forewarning. Is this behaviour expected? I hope it is not...

Best Answer
photo

There is a newer beta version of Locus Map Classic available at our public repo at https://bit.ly/lmVersionsTest. Please test the issue with it. Thanks.

Replies (2)

photo
1

Hi,

we did not remove anything from Locus Map Classic. Please make sure the app has the system permission to access nearby devices and is excluded from all means of the battery optimization. More info: https://docs.locusmap.app/doku.php?id=manual:faq:bt_sleep_issues

photo
1

Hi, Locus Map on the smartphone was already excluded from battery optimizations and it's running as a service with a persistent notification. In fact the OS never killed it and recordings were already perfect.

I noticed that it was missing the Nearby Devices access permission, though: I enabled it from the app authorization settings but still the same error appears.

On the watch both the notification and sensor permissions are enabled. So it's still unresolved: tapping on the Update button the Play Store link is launched while I remember that previously the Locus app was launched instead.

photo
photo
1

There is a newer beta version of Locus Map Classic available at our public repo at https://bit.ly/lmVersionsTest. Please test the issue with it. Thanks.

photo
1

Sorry for the answer delay (I had personal issues)... I can confirm that with 3.70.16.1_1136_beta the Locus Wear app works perfectly as before! 👍

So it's definitely an issue of the current stable version.

photo
1

I forgot to add that with v3.70.16.1_1136_beta Locus Map for Wear OS works also with the Nearby Devices access permission disabled on the smartphone app.

photo
1

OK, thanks for the info.

photo
Leave a Comment
 
Attach a file