Skip to content
colonelpanic8Public

About

Ring Tile Bluetooth trackers directly from a Wear OS watch

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Tile Wear

Tile Wear is a standalone Wear OS app that rings Tile Bluetooth trackers directly from a watch. A small Android phone companion signs in to Tile's cloud API, lets the user select trackers and favorites, and syncs each selected Tile ID and BLE authentication key to the watch through the Wear OS Data Layer.

The watch does not need the phone or Internet while ringing. It scans for Tile's 0xfeed BLE service, connects with timeouts, reads the stable Tile ID characteristic instead of trusting the rotating Bluetooth address, performs the TOA/MEP authentication handshake, verifies every channel MIC, and sends SONG play or stop commands.

This is an unofficial reverse-engineered client. It is not affiliated with or endorsed by Tile, Life360, or Google. Use it only with trackers and an account you are authorized to access.

The protocol implementation is a Kotlin port informed by Lesley De Keyser's MIT-licensed node-tile project; its copyright notice is retained in LICENSE.

Modules

  • shared: pure Kotlin/JVM Tile cloud client, sync codec, cryptography, framing, inbound MIC verification, and transport-independent protocol state machine.
  • mobile: minimal Compose phone companion for login, live/stale selection, favorites, and Data Layer sync. The password is held only long enough to log in and is never persisted.
  • wear: Compose for Wear app, BLE scanner/GATT transport, app-private key storage, and a ProtoLayout tile with up to two favorite shortcuts.

Tile's account response marks current trackers with visible: true. The phone selects visible, non-dead trackers by default and hides stale/replaced entries, while the Show hidden/replaced switch allows manual recovery of any account entry.

Build

The Nix shell supplies JDK 17 and Android SDK 36:

nix-shell --run './gradlew :shared:test :mobile:lintDebug :wear:lintDebug :mobile:assembleDebug :wear:assembleDebug'

Debug APKs are written to:

  • mobile/build/outputs/apk/debug/mobile-debug.apk
  • wear/build/outputs/apk/debug/wear-debug.apk

Known-answer protocol vectors can be regenerated from a checkout of node-tile at /tmp/node-tile:

node scripts/generate-node-tile-vectors.mjs

RealProTraceTest replays a captured Tile Pro 2024 authentication trace byte-for-byte. It runs when TILE_REAL_AUTH_KEY and TILE_REAL_TDT_CONFIG are supplied at test time and otherwise skips without weakening the portable known-answer tests.

Install and use

Phone and watch APKs must have the same application ID and signing certificate. For debug builds made by the same checkout:

adb -s PHONE_SERIAL install -r mobile/build/outputs/apk/debug/mobile-debug.apk
adb -s WATCH_SERIAL install -r wear/build/outputs/apk/debug/wear-debug.apk

Then:

  1. Open Tile Wear on the phone.
  2. Enter the Tile account email and password, then tap Log in and refresh.
  3. Review the live trackers. Use the checkbox to choose what reaches the watch and the star to select favorites. Enable Show hidden/replaced only when needed.
  4. Tap Re-sync selected Tiles. Data Layer persistence means the update is delivered when the watch reconnects.
  5. Open Tile Wear on the watch, grant nearby-device permissions, and tap a tracker. Connection and authentication commonly take 20–30 seconds, so the screen reports each phase.
  6. Tap Stop to stop the sound and close the GATT connection.

For one-tap access, add the Ring Tiles tile to the watch carousel. Its buttons open the activity and immediately start the selected favorite after permissions have been granted once.

Release signing

The release PKCS#12 is stored only in pass as tile-wear-android-release-keystore. Both APKs are signed by scripts/build-release.sh, which decodes the key into a temporary in-memory filesystem, verifies both certificates, and writes:

  • dist/tile-wear-phone.apk
  • dist/tile-wear-watch.apk
./scripts/build-release.sh

The release certificate SHA-256 is:

83b1c3b1c4f4feb78e32f82cd674a212403bab89517fcf0d162f4ce5cb61bd74

The proposed Wear Updater catalog change is committed as docs/wear-updater-tile-wear.patch; this project does not modify the separate wear-updater repository.

Publishing

Nothing in the normal build publishes or pushes. When the repository and GitHub secrets are ready, a release can be published manually with:

./scripts/publish-release.sh v0.1.0

Alternatively, push a vMAJOR.MINOR.PATCH tag after configuring these repository secrets from the pass entry:

  • ANDROID_KEYSTORE_BASE64
  • ANDROID_KEYSTORE_PASSWORD
  • ANDROID_KEY_ALIAS
  • ANDROID_KEY_PASSWORD

The release workflow builds and uploads tile-wear-phone.apk and tile-wear-watch.apk. The F-Droid Pages workflow publishes the phone companion after a GitHub release; see docs/fdroid.md. Apply the Wear Updater patch separately after the first GitHub release exists.

Protocol notes

Authentication follows the proven node-tile flow:

TDI discovery -> RandA/RandT -> channel open -> READY
    -> TDG / advertising interval / TCU setup
    -> optional TDT, time, and song-map setup
    -> authenticated SONG play/stop

Channel writes use an app nonce and direction 1. Channel notifications are accepted only when their four-byte MIC matches the derived session key, incremented Tile nonce, direction 0, payload length, and payload. TKA heartbeat checks are answered while the channel is open. Every scan, connect, service discovery, characteristic operation, authentication phase, and sound acknowledgement has a timeout; failures close the GATT instead of waiting for Android's BLE stack indefinitely.

The original research and desktop proof of concept remain under research/.

About

Ring Tile Bluetooth trackers directly from a Wear OS watch

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages