Change Details

Add a plugin to KDE Connect which supports reading the Android contacts databases and exporting that data over DBus - Currently supports getting contact names, email addresses, and phone numbers - All contacts are associated with a unique ID - After getting a valid uID, more information about that contact can be requested by sending that uID as part of an argument to the DBus methods - Phone number and email address entries are stored as a triple of the phone number or email address, an integer representing the type, and a label, if defined - Phone number and email address types are currently not defined, but happen to match the types defined by Android's contacts databases BUG: 367999

Add a plugin to KDE Connect which supports exporting the Android contacts databases to vcards on the desktop When the devices are connected, the plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, possibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999

Add a plugin to KDE Connect which supports readingexporting the Android contacts databases and exporting that data over DBus - Currently supports getting contact names, email addresses, and phone numbers - All contacts are associated with a unique ID - After getting a valid uIDto vcards on the desktop When the devices are connected, more information about that contact can be requested by sending that uID as part of an argument to the DBus methods - Phone number and email address entries are stored as a triple of the phone number or email addressthe plugin sends a request for all timestamps and IDs When a packet with timestamps and IDs is received, an integer representing the type,it verifies it has vcards for each ID and that the timestamps match and deletes any vcards for IDs which were not reported. and a label, if defined It then sends a request for all vcards which were missing or need updating When a packet with vcards is received they are unconditionally written to disk, - Phone number and email address types are currently not defined, but happen to match the types defined by Android's contacts databasepossibly overwriting existing vcards Provides one dbus method: contacts/synchronizeRemoteWithLocal which triggers the request for all timestamps and IDs BUG: 367999