App on Samsung Smart Watch (tizen) "No response from Locus map"

Wolfhard Huwendiek shared this problem 24 days ago
Solved

Get above message after installation. Read already that solution for gear S3 "On your phone go to system Settings > Applications > Samsung Accessory Service and clear the data&cache for this Samsung application."

But I'm afraid, I'll loose a lot of important data and didn't try to do so. Is there another solotion or circumvention possible?

Regards, Wolfhard

Comments (19)

photo
1

Hello,

I can't guarantee you that such operation is safe but no one has complained yet about having lost any data. The Samsung Accessory Service should be just a middle man for communication between Android Apps and Gear/Galaxy watch.

But alternatively you can also reinstall Locus Map Pro on your phone (this seems to force and update of Locus Map communication parameters inside Samsung Accessory Service).

No other solution is known to me at the moment.

Best regards

Milan

photo
1

Hello,

first of all: Thanks for quick information and ==> it's running!

I choosed the "clear" solution as te simpliest and quickest method and can't find any trouble or impact in other wearable apps like: Samsung health, HERE WeGo, Navigation and Komoot.

Best regards, Wolfhard

photo
1

Tried both steps several times on my galaxy note 4 and they really don't help. Keep receiving this message for most of the time, which makes the application not functional. Please diagnose the root cause of why the watch has issue to communicate with the phone and provide us with a fix.

Regards, Slawek

photo
1

Hello,

if you have already managed to get some data between the Locus Map and the Locus Map Watch add-on (got map on the watch or some valid track recording data), then this is some completely unrelated issue. The issue described here has been caused by a metadata/manifest change during update of LM 3.34 to 3.35 and a bug in Samsung Accessory Service application, which ignored those changes in our updated manifest for some reason - therefore clearing the cache of Accessory application once or reinstalling Locus Map with version 3.35+ forces the manifest refresh and resolves the issue for good.

You seem to have genuine communication issues if the connection appears to be working sometimes. Fist of all, please just try to restart both phone and the watch if you haven't done so already. Then start Locus Map on your phone, after that run Locus Map Watch and try to display a map for example. Right after that capture a debug log on your phone and send it to me please so I could look if there some problems or indications what could be the cause.

Thank you,

Milan

photo
1

Milan,

I tried to capture a debug log according to the instructions above, but for some reason I'm not receiving a notification about the report on my phone. Instead, I connected to phone with adb and collected logcat to enable analysis (attached). Please let me know if you see any problems reported there.

Thank you,

Slawek

photo
1

The application on my watch can show and zoom in/out a map fluently when running standalone. It starts to have connection issues and doesn't want to refresh the map once I run Lotus application on my phone. The Lotus application itself shows pop-up at each start that it cannot add some maps (*.sqlitedb). You should be able to find some evidence in the logcat. This started to manifest after an unsuccessful installation of osmapa.pl classic+*relief* maps. For some reason the next attempts to download the relief version of this map were also unsuccessful. This problem is persistent, even though I tried to re-install the application, clean data&cache in both the application and Android system. I'm not sure if it can have something to do with the reported issue.

photo
1

Hello Slawomir,

problems with the data/map download is also interesting. It would be really helpful if you could also attempt this failing donwload before acquiring the log. I did not get any log from you and I don't see it included in here also. Could you please reupload or send it to me via email?

Thank you,

Milan

photo
1

Sent logcats for both scenarios to your email. Thanks, Slawek.

photo
1

Thanks Slawek, I got the emails, I will look into it. By the way what version of Android are you using? Is it rooted? Custom ROM?

photo
1

Android 6.0.1 - original latest version for Samsung Galaxy Note 4 (not rooted)

photo
1

Good day Slawomir,

Milan send me logs from You related to problems with loading of maps. It really should have anything with problems with Gear, maps are completely independent. Anyway, in your logs, I see "unknown problem" when the app tries to add the following three maps:

  • /sdcard/Locus/maps/Gdańsk.sqlitedb
  • /sdcard/Locus/maps/osmapa classic relief.sqlitedb
  • /sdcard/Locus/maps/Gdynia.sqlitedb

Maybe you may check manually if these files have at least few megabytes and if so, best should be if you may share these maps with us so I can test them and fix the possible problem? If you do not care about these three maps, the best should be to simply delete them.

photo
1

OK, probably those file appeared to be broken (24kB only). After removing them from sdcard manually, the pop-up with the warning doesn't show anymore at the application start. Thanks.

I don't know why the relief version of osmapa.pl couldn't be downloaded from the server successfully.

photo
1

For the primary issue, I still keep receiving the message "No response from Locus map" on my watch for most of the time. Although there are shorts moments when the communication is established and the map gets refreshed.

photo
1

Hello Slawek,

Honestly, I have no solution for such behaviour, this just seems like genuine communication issues for some unknown reason. I don't see any Gear related errors in the log. I would check if all Samsung applications are updated (Galaxy Wearable, Samsung Accessory Service and Gear Plugin) a try to reset BT connection or the phone and the wach.

I am sorry for the troubles you have with the add-on :(

photo
1

Hi Milan,

I see no new updates available for the Samsung applications on my Galaxy Note 4 phone.

Can you provide me with a list of phones that this application has successfully been tested on?

Thanks,

Slawek

photo
1

Well, the add-on has been tested by me on Xiaomi Redmi 4A and Samsung Galaxy S7. The application has also been manually validated and tested by Samsung employees with Samsung phones against Gear S2/S3/Sport and Galaxy Watch. The Galaxy note 4 - Gear S3 is formally marked as a supported combination in the Samsung's Galaxy apps administrative interface.

photo
1

Can you provide me with the add-on versions that work fine on your Samsung Galaxy S7?

Is there any version pack that is recommended by Samsung engineers?

Can you test the application in the configuration Galaxy Note 4 - Galaxy Watch?

And report the issue back to Samsung employees for investigations?

photo
1

Hello,

current add-on version is the only stable one and is in production for weeks now already.

As for Samsung there is practically no talking to them, I have even reported a bug in their library which even other developer confirmed and it really didn't lead anywhere, we are just too small to reguest anything more other than standard "processes" and testing from Samsung really.

I don't have Galaxy Note 4 at my disposal so I cannot test or replicate unfortunately.

Since you are seemingly the only one to report such issues after weeks of stable production and the behaviour is so erratic I will postpone attemts to solve this issue until some else confirms similar problems. I could not find anything out of ordinary in the log and I would have to create custom debug version with extended logging. And with such low incidence rate until anything more is confirmed, it could be some very specific HW or SW anomaly which I might not be able to solve anyway.

We normally provide a full refund in such a case, but since Locus Map Watch is currently provided free of charge for all users to evaluate and/or use with even the LM Free version I cannot really provide any compensation at the moment.

I am really sorry for the incovenience :(

Milan

photo
1

I see and I'm too small to request anything more from Lotus other than logcat analysis, even no testing really.

Not at all :(

Slawek

photo