RomanZ, From a user's perspective the file was not saved or altered so the modified time should not have changed. That being said, I can't speak for anything that the KeePassDroid app actually did in the background when the database was open. It could very well have updated some meta data or re-saved the entire database without my knowledge. The problem hasn't arisen again since, however, I have only used it twice on my phone since the issue originally occurred. I've checked the modified time in ES File Explorer and it is dated to before the times I've accessed it. Also, from my previous tests I wasn't able to reproduce the same error state where the old KeePass database was being pushed to the swarm so if it is KeePass updating the database in the background, which it is feeling more and more likely considering jsbeddow's confirmation of the issue being related to KeePass, it isn't doing it consistently which is more then a little bit of a pain as far as debugging goes. I'll keep poking it on my phone and checking the modified time to see if I can catch KeePassDroid fiddling with the file behind my back and keep you posted. Bradley