This seemed to have fixed the problem stated in #142, but for some reason the encryption is done twice and the items appear twice afterwards. Then after a restart of the app, the app crashes with: java.lang.NullPointerException at encryption.EncryptionService.onStartCommand(EncryptionService.java:84)
Turned out to be a bit more difficult than expected, but along with the fix are a few automatic other fixes.
Changes:
- bootmanager now only boots once. Anything else that calls for the boot will just wait for the original call to be done. Or if the boot was already done, will be called back immediately.
- the encryption service listener in the content fragment gets set and unset as the app exits/starts
- the random file generator had a bug that it created a file with an empty filename. This caused several crashes with also the tap to lock, but also when the app starts or thumbnails get encrypted.
Refactored to follow standards
added weak reference to avoid memory leaks, and changed the boot strings
Merge branch 'master' of https://github.com/AlexKolpa/AndroidStealth into 142-tap-to-lock-crash
I am merging issue #131 and PR #132 into this PR. The changes in #132 became obsolete due to the changes in this branch. However, this simple modification fixed it. Closes #131
Now the working version of it :P
Merge branch 'master' of https://github.com/AlexKolpa/AndroidStealth into 142-tap-to-lock-crash
Merge pull request #144 from AlexKolpa/142-tap-to-lock-crash

Tap to lock crash & persistent selections

Closes #142