[beyondlevi]

What

DroidBridge 0.2.0.

• Device choice: when several Android devices are on adb (e.g. phone and smart glasses), DroidBridge no longer picks the first one. The menu gets a Device item to choose; with a single device nothing changes.
• Rotation: the server tells the Mac when the screen turns, and the device's rectangle in Arrange Screens turns too, keeping the sides that touch displays. The input dispatcher reports pointer positions in unrotated (physical) coordinates; the server now turns them into rotated ones, so entering and returning through the edges works in every orientation.
• Foldables: when a Galaxy Z Fold closes, Android's main display becomes the cover screen. The device's rectangle takes that screen's shape (it keeps its longer side and its touching sides).
• Faster entry: the pointer reaches its spot along the edge in 0.1–0.2 s (it was up to 0.8 s far along a long edge). Moves are now bigger steps, and the gain of each axis is learned on earlier entries.
• Version 0.2.0, README and architecture notes.

Wi-Fi is not included. It stays on feature/wifi until it can be tested on a network that doesn't isolate devices.

Tested

• swift test: 32 unit tests, including reshaping in a corner between two displays and the cover screen's aspect.
• tools/devtest.py on a Galaxy Z Fold (Android 17), measuring entry accuracy (within ~25 px) and the return through the edge:
  • in rotations 0, 1 and 3;
  • on the cover screen, folded.
• By hand, with a Mac with two displays:
  • crossing and returning with the phone upright and lying down;
  • entering far along a long edge;
  • folded and unfolded;
  • the device chooser, with Rokid glasses plugged in at the same time (nothing was sent to the glasses).

Risks

• Positions come from parsing dumpsys input text. A future Android version that changes that text would break the return to the Mac. The hotkey ⌃⌥⌘B still works in that case.

🤖 Generated with Volund OS