EDIT: Unfortunately, I rebooted and saw all my contacts in Android again. So, at the moment, the following trick seems not to survive reboot or not to work at all as I perhaps had a false positive.
I started using Android App Support (AAS, Alien Dalvik) a bit more recently.
Android apps seem greedy of personal data.
In case an app refuses to work if one doesn’t accept to share e.g. contacts, then the address book privacy is lost.
It is not possible in the settings to disable synchronization between the SFOS address book and Android’s one.
This didn’t suit me, so, here is the way I found to prevent this situation.
Please be tolerant and provide remarks/improvements as I have zero knowledge in databases not in Android App Support mechanics.
Try at your own risks.
On SFOS, contacts are stored in a database which is
/home/defaultuser/.local/share/system/privileged/Contacts/qtcontacts-sqlite/contacts.db and in temp files along this db in the same directory.
On the Android side, contacts are stored in
It seems that the contacts are copied from SFOS db to AAS db during AAS startup.
Nulling the SFOS db file rights at the beginning of AAS startup and set these rights back at the end of the startup seems to correctly prevent the contacts from being imported.
(Changing the ownership to root doesn’t seem to work anymore.)
Here is how I do:
Stop Android App Support.
# License: Jolla Proprietary
Insert this line:
chmod 000 /home/defaultuser/.local/share/system/privileged/Contacts/qtcontacts-sqlite/contacts.db*
At the same place like above, insert:
chmod 644 /home/defaultuser/.local/share/system/privileged/Contacts/qtcontacts-sqlite/contacts.db*
Delete the Android address book /home/.android/data/data/com.android.providers.contacts/databases/contacts2.db
Start Android App Support and verify that the address book is empty.