jdrch Posted March 23, 2015 Report Share Posted March 23, 2015 Getting the following when resuming the Android (4.4.4) client (2.0.80.0) from idle: Syncing with Windows 64-bit 2.0.93 client on 3 other machines. I'm guessing the Android client may be choking because the folder contents were changed while the client wasn't running? Yet another issue the 1.4 client didn't have. Any ideas? Quote Link to comment Share on other sites More sharing options...
Helen Posted March 23, 2015 Report Share Posted March 23, 2015 I'm guessing the Android client may be choking because the folder contents were changed while the client wasn't running?Unlikely. was Sync shut down correctly? or was it a "force stop"? This error will appear because database got corrupted. And this may happen if Sync was not closed correctly (for example crashed) and was not able to save its database Quote Link to comment Share on other sites More sharing options...
jdrch Posted March 23, 2015 Author Report Share Posted March 23, 2015 Unlikely. was Sync shut down correctly? or was it a "force stop"? This error will appear because database got corrupted. And this may happen if Sync was not closed correctly (for example crashed) and was not able to save its databaseNo, it wasn't force closed. I have Battery Saver and Auto Sleep disabled; the client simply went to "idle" in the Android sense while in the notification tray. When I resumed it via tapping the notification, the errors appeared after the folders were loaded. As I said, 1.4 never had this issue. You could stop, idle, force close, and resume with no problem. So it would seem 2.0 is less robust for some reason. Quote Link to comment Share on other sites More sharing options...
klb3317 Posted March 24, 2015 Report Share Posted March 24, 2015 Same issue. Got it after adding file to sync folder on PC Win 7 x64.Sync v.2.0.93 PC and v.2.0.80.0 on Android 4.4. UPD: My folder was "1.4". I've deleted it and then created new one - it appeared with crown icon instead of "1.4".Now it synced ok. Quote Link to comment Share on other sites More sharing options...
Helen Posted March 25, 2015 Report Share Posted March 25, 2015 There were same database corruptions in Sync 1.4, but then syncing was not stopped. This might have lead to bad results with files corruption, incorrect syncing, etc, well because database is corrupted. Now, when db gets damaged, syncing stops and error message appears. @jdrchMany Android devices are known to kill Sync in background with "Force stop", which is not a good way to let an app finish its work and save its configs and database, so corruption appears. Quote Link to comment Share on other sites More sharing options...
jdrch Posted March 25, 2015 Author Report Share Posted March 25, 2015 There were same database corruptions in Sync 1.4, but then syncing was not stopped. This might have lead to bad results with files corruption, incorrect syncing, etc, well because database is corrupted. Now, when db gets damaged, syncing stops and error message appears. @jdrchMany Android devices are known to kill Sync in background with "Force stop", which is not a good way to let an app finish its work and save its configs and database, so corruption appears. Fair enough. FWIW since I disconnected and reconnected the trouble folders on phone all seems to be working. Quote Link to comment Share on other sites More sharing options...
rstarkov Posted July 24, 2015 Report Share Posted July 24, 2015 Got this too out of the blue. I don't run any task killers and the phone was just sitting doing nothing. It synced a few files yesterday night fine, today it says "Database error". I haven't even touched it since the last time it worked. Exiting and restarting sync doesn't help. Is there an official way to recover from this? Force closing shouldn't damage the database anyway. Don't you use sqlite transactions for this kind of thing? Quote Link to comment Share on other sites More sharing options...
pascal.desmet@telenet.be Posted September 22, 2015 Report Share Posted September 22, 2015 any news on this topic? I have the same problem here. Simple folder with 2 xls files. Android phone is configured dedicated for 1 application, so nothing else installed. no battery saving,. The 2 files involved that need to be synced are always open on the android phone and occasionally read by a windows system. Already tried a full reinstall of the system. After this we got the problem less frequently. (went well for 3 weeks). now the problem is back again. torrent sync version: 2.1.0 (327)android version: 4.1.2 very annoying... any suggestions are welcome. thanks Quote Link to comment Share on other sites More sharing options...
RomanZ Posted September 22, 2015 Report Share Posted September 22, 2015 @pascal.desmet@telenet.beSometimes Android itself kills Sync without any warning. Are your running Sync with notificaiton icon or you turned it off? Having an icon in notification area allows Sync to run in a different mode, with lesser chances to get killed by OS. Quote Link to comment Share on other sites More sharing options...
jdrch Posted September 23, 2015 Author Report Share Posted September 23, 2015 The 2 files involved that need to be synced are always open on the android phone and occasionally read by a windows system.I'm pretty sure this is your problem. Sync by its very nature doesn't support concurrent changes across multiple peers. Also, Sync won't detect a change in a file unless it's saved, and I suspect how that's implemented varies across OSes. Reasonably sure that if you start over from scratch with the folder and save the .XLS files between edits, you should be OK. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.