Unable to sync with one particular device

Viajero Perdido shared this problem 8 months ago
Solved

(Brought over from the forum...)

I have a tablet (Android 7), main phone (9), and backup phone (6). Sync seems to be working (slowly, with duplicates, but working) between tablet and backup phone. But, I've never been able to get a manual sync started, nor any automatic sync, on my main phone. It always reports "Process unsuccessful" after a few minutes, never reaching 1%.

This phone has never (I don't think) run pre-release versions of LM4 (I used a separate older device for testing, and never looked at Sync before release). Nothing seems to help: clearing temporary data in Locus, clearing storage and cache in Android, reinstalling, even deleting 3 Sync* files I found while snooping around. I can't find any logs, nor any config setting that might enable logs, nor any help text (didn't look too hard) about how to use this feature.

It seems suspicious that the User ID (reported next to the Locus version) on the troublesome phone is 40 hex digits long, but 10 digits long on the two devices where it does work. (The erratic appearance of the "GOLD" caption I reported on the forum now seems unrelated.)

Before experimenting with Sync, all 3 of my devices were full of geocache waypoints, many unnecessary (I've since deleted some folders), all *roughly* the same data across the devices but imperfectly so. (My backup phone has been stuck at 5% overnight and this morning, trying to sync the deleted folders, but that may be a separate issue. It has thrown errors 14199, -1, and 10103 at various times. But I don't care about that phone.)

My main phone can create a plan (see attached), but it can't execute.

I *may* be able to fix this by backing up the (very little) data I actually want to keep, deleting everything, then trying a full download. But I'll wait, in case I can offer any assistance (logs etc.) in debugging.

Replies (1)

photo
1

Hello Viajero,

thanks for writing to us with such a complex description of your problem. Weird...

Where to start. May you please create a log by this known method right after you start to sync and it finishes with any error message? There is a big chance that in the log will be more info. My colleague Ondřej meanwhile check what exactly happens on the server on your account.

Thanks and sorry for the complications that sync cause you. Btw. you have a backup on your primary device before you started the sync right?

Menion

photo
1

Done, sent, a file with BV9900Pro in title. Thanks for looking into this; I hope the log helps.

Yes, I made several backups, no worries, and most of my data is disposable, just mountains of caches from GPX imports. And I'm not relying on Sync just yet, mostly just curious and I enjoy trying to solve problems. Cheers.

photo
1

Thanks! Hope you will have a little patience with me. Seems there does not happen and clearly visible error so it will need a version that print even a basic messages. I just created one for Michael Bechtold a moment ago, so if you can, please install this Locus Map 4 Beta version APK over your existing app. It is version already prepared for publishing to Google Play so it should work without any problems. It will print a lot more info into log. Or if you know "Expert settings", you may directly enable "Log to file" there before sync. App will then print all logs into Locus/logs directory. Thanks!

photo
1

Glad to help. I loaded the .apk (couldn't find expert settings), re-ran the dump immediately after "Process unsuccessful". File slightly bigger; hope the answer is in there. Good luck. :)

EDIT: found the expert settings. Give me a moment; I'll send that log too.

EDIT: ah yes, I see some clues in there. No rush, not on my part. I understand it's night time in Europe. :)

photo
1

BTW, I noticed a usability glitch in the test version you gave me (only). I have all panels set to auto-hide, and the zoom buttons always visible. With the panels hidden, tap on a zoom button un-hides the panels, and moves the zoom buttons up. Meaning, if you tap the buttons a bunch of times, all taps except the first are on something else by mistake.

Regular 4.0.0 doesn't do this; hopefully 4.0.1 won't either. :)

photo
1

Thanks for logs, mainly log created directly by the Locus Map is extremly useful.

Two issues detected. Mainly the one: you already have so many points on the web, so many in the device that it took more then a minute to primare what app should do and result (the plan) is so big, that app was not able to store it into own internal storage.

New version available under same link as before, so please give it a try.

Just warning: because it is your primary device and on the web are already data from your two devices, I'm worried that result will be really mess. Do you want to risk it? Then try it.

Otherwise better should be clearing existing data on our server (we may do it manually in such case), removing databases on two secondary devices and then making sync on your primary device.

Let me know.

Jiří M, aka Menion

photo
1

Thanks for the quick overnight service. :)

I'm willing to risk a data mess; 99% of it is caches which I can simply reload. It think it's more useful to run a torture test of the sync system under messy conditions.

Right now, it's syncing! It's at 1%, uploading points, which is farther than it's ever gotten before.

I hadn't changed any data on any of the devices, loaded the new .apk, turned on logging, and started a manual sync. After the usual 2 minute delay, it said PAUSED. Hmm, un-pause, same result, and again for a total of three tries. Log mentions "sorry this is not possible".

Restarted Locus, new log file. Saw a new expert option, delete data on server, did that. After several minutes of "Loading..." I tapped the top-left arrow to see the notification window back at PAUSED; not sure if the data-delete actually happened, but will assume it did. Log file not growing, so I looked inside; near the end was an exception about malformed JSON.

Finally, I tried a manual sync again. And it seems to be working! Now at 2%, sure is slow.

I'll update this post after I know how well it worked. It may take hours. :) Let me know if you'd like the log files. Cheers. 3%

EDIT: Argh, error 10601 after maybe 5%, and I'd already turned off the log. Will try again. It's continuing... 8%

photo
1

Ah damn, you got my version where is quite secret private feature "Delete server data" :D.

This operation may takes in your case close to 30 minutes, but should be doing exactly what I offered : clearing synced data on the server.

Oki, give it a try. If it finish, please do not sync your secondary device immediately but really, manually delete whole Locus/data/database and then start a sync! Then all should be fine. Secondary devices should only download data from the server.

Error 10601 means "Manually canceled", weird.

photo
1

Sync finished sooner than expected on the phone, and the tablet started an automatic sync. I'm going to let it run and see what happens. :)

I know I didn't let it sit 30 minutes after "delete server data". What's the worst that could happen?

I haven't found anything on how to use this feature properly. "Secondary devices", hmm, guess I need to nominate a primary; they both struggle for control in my life. I'll keep looking for the instructions. For now, it looks good, thanks!

EDIT: Paused the tablet, which turned into a 10601. I think I'll nominate the tablet as the "secondary" device, back up the (very little) important data, and follow your advice above.

photo
1

Cleared server data. Checked plan, verified nothing on server to pull. Finished sync on phone. Emptied tablet, sync.

Boom! 14199. No data, just empty folders on tablet.

Plan suggests plenty of data is waiting to be pulled.

Oh wait, maybe I need the test .APK on the tablet too. I'll try that... Nope, didn't help. The message suggests you already have the details, but in case not, the log says "plan too big to save into database". Let me know if you need the log.


Good thing I don't need that data anytime soon, and have a backup ... and a sense of adventure. :)

photo
1

Today's beta didn't change things. Also couldn't sync a new route from the web planner into the phone. Decided to delete all geocaches from phone ("primary") leaving very little essential data, sync (working at 4%), and hope it reaches the empty tablet.

EDIT: phone upload of deleted points succeeded, but failed on download of single track from web planner, argh. Tablet sync download failed as before. Now (sigh) deleting all server data via beta on tablet, trying again from phone...

photo
1

With a dramatically reduced data set (1500 points, 60 tracks) in one device and nothing in the other, I finally managed to get sync working between the two. (I needed to clean out those thousands of old geocaches anyway.) Points seem to be syncing smoothly.

Next I'll try loading 5000 caches from GPXs. EDIT: Loaded 6600 points from GPX according to progress indicator. Sync uploaded 4687 points, then threw a -1 error at 99%.

Possibly significant: 4687 is the total of the caches in the PQ, not including child waypoints (parking etc.). Will check shortly to see if those are missing from the other device. YES: child waypoints are missing, also logs, anything geocache-specific!

This is not useful if geocaches turn into simple points.

Weird: I'm sure I saw an info panel for a specific geocache that was missing everything cache-specific. Then after updating this post, it and other caches appear to have full info! Either I'm on drugs, or there's a slight delay as things straighten themselves out. ?!?!?

While fussing with one cache on both devices, I turned on display of all 5 child waypoints. Sending device showed all 5. Receiving device showed only 1, even when zoomed out just enough to show all, then after a bit more fussing, finally showed all 5. So hmm, maybe point/geocache sync is working fine after all, but the display might need a forced refresh.


Still having some trouble with tracks too. Maybe I'll start a new topic if it doesn't go away by itself.

photo
1

Hello Viajero,

it starts to be a too much info, too big mess on me to be true.

So firstly, at night I've found one big issue with syncing a track and new version 4.0.2 should be already available for download from the Google Play for you.

I'm no longer sure how far are you with your testing. Probably best I may suggest: use test version and trigger one more clear of content on the server. Wait and hour and try it again. Second time, it should be finisher with success message withing a few seconds = confirmation that server is really empty. Then update to new 4.0.2 and use it for sync even with your huge dataset. It simply have to work without any problems. If not, best should be if you may share with me your databases, because we are currently not aware of any other remaning problem and simulation on own device seems to be currently best option.

I appriciate your patience with it. Not sure how may I repay you for this :).

photo
1

Hi Menion.

I'm happy to report, with 4.0.2 on both my main devices, it's working perfectly now. Points, tracks, all directions including to/from the web planner, working smoothly. Many thanks!

I followed your advice (most recent post above) already yesterday, and this fixed the points. Then the 4.0.2 update took care of the tracks.

Still occasionally I see a geocache without some of its cache "magic", but that goes away by itself. I'll watch for it.

I'm a software developer too (retired), so I know what kind of bug reports devs like - detailed. Sorry if it was an avalanche of info.

I'll load up my main phone with fresh PQs over the next few days, and will report back if this thread is still open. Thanks again!

photo
1

Hello,

uff, perfect.

Well detailed ... yes or no, you know :).

Problematic caches may happen, but only for a second, then full detail should appear. I'll be watching it as well.

Have a nice weekend!

photo
1

Confirmed, everything's running smooth as silk, now with ~20,000 points mostly from PQs.

Hope you enjoyed the weekend off-duty. :)

photo
Leave a Comment
 
Attach a file