YAKA310/studio

Bluetooth Shortcut Keyboard guide

Back up shortcut decks locally or with Google Drive

Keep a copy of your shortcut buttons, text and profiles. Local JSON export and optional Google Drive backup have different scopes. Check the copy before replacing the receiving phone’s setup.

These guides describe the prepared 2.46 source. Its Google Play publication is not confirmed. The Store link opens the current public release, whose controls and available features may differ. Device and host compatibility vary.

What to know

  • Export backup creates a local JSON file with the deck, saved profiles and appearance preferences, not every app setting.
  • Optional Drive sync carries the deck, profiles, appearance and selected settings, including Presenter notes and computer bindings.
  • Import and restore are replacement operations, not automatic merging. Export the current setup before proceeding.

Before you start

Keep a separate copy of the deck and profiles you want to retain. Do not uninstall the app or clear its data to solve backup problems.

Review macro text, URLs and notes before sharing. Recipients and the storage service you choose can read the exported content.

How to do it

  1. Export a local copy

    Open Settings → Backup & sync → Export backup. Save the JSON through the system share sheet, then check the destination contains the file. Opening the chooser is not proof of a saved copy. Export includes the deck, profiles and appearance, not every app setting.

  2. Review a local import before replacing

    Choose Import deck and read Replace your deck? before choosing the JSON file. Check Review imported deck and leave the option to keep webhooks enabled off unless you trust their destinations. Import replaces the live deck, and a bundle can replace saved profiles. Export your current copy first. The app cancels if its required safety snapshot cannot be saved.

  3. Connect Drive only if you want it

    Choose Connect Google Drive in Backup & sync. Read Sync to Google Drive?, then continue through Google’s account and permission screens if you accept. Drive sign-in is optional and separate from Bluetooth pairing.

  4. Check a Drive backup result

    Choose Back up to Drive and check the result. Relevant changes can queue automatic backups once connected. Review Last sync and errors; signing in or queueing a change does not confirm an upload.

  5. Restore and verify on the destination

    Before Restore from Drive, export any setup on the receiving phone that you need to keep. Read the replacement confirmation, then choose Restore only for the intended account and copy. Check the deck, saved profiles and relevant settings, then test harmless input after pairing the destination phone.

What travels in each copy

CopyScope
Local JSON exportDeck, saved profiles and appearance preferences; not the broader set of synced app settings.
Google DriveDeck and profiles plus appearance and selected settings, including typed macro text, private Presenter notes and host bindings recorded by Bluetooth address.
Not carried by a deck or Drive backupPro entitlement and Google sign-in are separate account states. Screen-on, performance, rotation, Air Mouse tuning and volume-button mappings stay specific to the phone.

Drive is a separate privacy choice

Drive requests your Google account email and access to its private app-data area. The copy goes to your Google account, not a developer sync server. Carried data includes macros, private notes and host bindings. Do not store passwords in them.

Disconnect ends the app’s Drive connection; it is not proof that cloud copies were deleted. A local export also leaves the phone when you send it through email or another service. Choose its destination deliberately.

Handle old or incomplete data carefully

A local bundle with profiles can replace the profile list. A legacy bare deck or an empty incoming profile list can preserve existing profiles, so do not assume every file has the same scope. Check the actual restored result before removing your earlier backup.

If this app version cannot read part of a deck, both automatic and manual Drive backup can pause to protect the more complete cloud copy. Keep the original file, update the app and restore the complete copy before uploads resume. Do not repeatedly overwrite Drive to resolve unreadable content.

Limits to keep in mind

  • Restoring the Drive copy replaces the carried deck, profiles and selected settings; changes that were never backed up can be lost.
  • Backup status must be checked. A connection, queued change or old Last sync timestamp does not confirm the latest data is safely uploaded.

Questions and answers

Does JSON restore merge the buttons with my current deck?

No. Import replaces the live deck and can replace saved profiles from the bundle. Export the current setup first and review the confirmation.

Does a Drive backup transfer Pro?

No. Pro entitlement comes from Google Play, not from a deck or settings archive. Check the purchase account and the app’s Pro options separately.

Does a backup pair the destination phone automatically?

No. Restoring computer bindings is not the same as establishing an operating-system Bluetooth pairing. Pair and verify the destination phone’s connection separately.