Dropsync is a must-have Dropbox add-on for Android to sync files with remote folders. Since v2.4.6 though I’ve been tracking an apparent bug on my Barnes & Noble Nook eReader, which runs Android 2.1 (the bug is not reproduced on my Android 4.1 phone). The developer is strangely silent, despite my having supplied reproduction steps and logcat extracts, so I’m beginning to wonder whether it’s just me!
The bug is as follows:
If an eBook is removed from a Dropbox folder on a remote device, whilst Dropsync correctly deletes the local eBook file it does not delete the entry from /data/data/com.android.providers.media/databases/internal.db.
The two tables where eBooks get stored in that database are ‘products’ (for purchased eBooks) and ‘docs’ (for sideloaded eBooks). In my testing I am only using sideloaded content.
Anyone experiencing similar or can offer any suggestions I’m all ears.
by tomasz86
01 Jan 2014 at 07:13
I’ve got the same Nook Touch with Android 2.1. I haven’t used it recently but as you probably know Dropsync some time ago stopped supporting versions of Android below 2.3.3. Unfortunately I don’t remember which version of Dropsync was the last one to officially support Android 2.1 :(
I’m going to try to contact the developer and ask for more info as I’d like to use the Nook more again, and need Dropsync for synchronisation.
by admin
01 Jan 2014 at 16:52
I hadn’t noticed that support for Android 2.1 had been dropped (thanks for bringing it to my attention!) but this bug has been present for a long time now. The bug apart, Dropsync works flawlessly even at the version I currently have installed (v2.5.3), using ‘Download mirror’ for sideloaded files in /sdcard/My Files/Books and ‘Upload Mirror for B&N books stored in /sdcard/B&N Downloads (I have put a hard link from the standard location to the sdcard so as to benefit from increased storage space); hope that helps you out somewhat.