Address book only partly shareable to Android

Taking over from TJC:
https://together.jolla.com/question/210604/share-only-specific-contacts-group-to-android-secondary-address-book/

Please allow us to define/control/select the contacts we share to the Android side.

Either by creating groups (share to Android) or tags or even a second DB which can only be seen by Sailfish.

7 Likes

This is something I’m missing badly as well.

I even tried to install a simple address book for Android to have a parallel world for AD apps. But that was of course a stupid idea as the phone book is somehow hard linked from AD to the SFOS one. :flushed:

[workaround]
valid if you need it for WA:

I am using OpenContacts from f-droid.
It is a simple completely independent address book. It is even independent to the default addeess book inside the Android world.
It is quite nice, lightweight, handy and it enables you to have nanes and numbers in one place.
WA is not capable of adding a new contact/chat if you do not have it in address book. But this tool enables you to search for names and open WA.

As said it does not interfere with default contacts but is independent. So no deal if you want to use it for Android apps.

And it is definitely not a replacement for the requested feature.
[/workaround]

Bringing this up once more (4.1.0 released).

Even knowing that this is in full contrast to e.g.


But I would like to not have the Android side giving full access to my phonebook!
For me Sailfish should still (and hopefully stay, see those teeny-weeny-buttonizing) different to Android.

3 Likes

I totally agree.
I was surprised that in a privacy oriented environment, contacts (pictures…) are shared
fully or not at all.
In that case, most people will say “well, no choice” and tick “allow” without to search further, fastly turning their situation to the same as under Android where they share everything all the time.

ATM I ticked “refuse” and did nothing with WA (chance I have the choice).
I was (naively?) thinking of renaming the contacts db before to launch WA.
Would that work as workaround?