org.bluez...onization(5)

💖 NAME 💖

Okay bestie, welcome to org.bluez...onization(5) — that's the title, and it lives in the Linux System Administration manual. This page is the whole vibe for org.bluez.obex.Synchronization — the BlueZ D-Bus OBEX Synchronization API documentation. ✨

---

🦋 INTERFACE 🦋

Here's the roster, no cap:

• Service — org.bluez.obex
• Interface — org.bluez.obex.Synchronization1
• Object path — [Session object path]

---

✨ METHODS ✨

These are the actual moves. Keep the signatures exactly as written, bestie — character for character. 🫶

💅 SetLocation

void SetLocation(string location)

Sets the phonebook object store location for other operations. The page says it should be called before all the other operations — like, do this first, okay? 💖

Possible location:

• "int" ("internal" which is default) — store in the interval memory.
• "sim{#}" — store in sim card number #.

Possible errors:

• org.bluez.obex.Error.InvalidArguments

---

🎀 GetPhonebook

object, dict GetPhonebook(string targetfile)

Retrieves an entire Phonebook Object store from the remote device, and stores it in a local file. Iconic little fetch-and-save moment. 💾✨

If an empty target file is given, a name will be automatically calculated for the temporary file — so cute, it names itself. 🧚

The returned path represents the newly created transfer, which should be used to find out if the content has been successfully transferred or if the operation fails. That path is your transfer's main character energy — use it to check the vibe. 👑

The properties of this transfer are also returned along with the object path, to avoid a call to GetProperties, see org.bluez.obex.Transfer(5) for the possible list of properties. Convenient? Obsessed. 💅

Possible errors:

• org.bluez.obex.Error.InvalidArguments
• org.bluez.obex.Error.Failed

---

🌸 PutPhonebook

object, dict PutPhonebook(string sourcefile)

Sends an entire Phonebook Object store to the remote device. It's giving upload era. 📤💖

The returned path represents the newly created transfer, which should be used to find out if the content has been successfully transferred or if the operation fails. Same main character transfer path, different direction. 🔥

The properties of this transfer are also returned along with the object path, to avoid a call to GetProperties, see org.bluez.obex.Transfer(5) for the possible list of properties. No extra call needed, periodt. 🎀

Possible errors:

• org.bluez.obex.Error.InvalidArguments
• org.bluez.obex.Error.Failed

---

💖 That's the whole page, bestie. Source/version: BlueZ. Date: October 2023. Manual: org.bluez...onization(5). Bye! 🦋✨