Gearslip: phone-side Android Auto client

gearslip/src/main/res/xml/accessory_filter.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+  Must match the strings the head unit sends during the AOAP switch. aasdk pins
+  src/USB/AccessoryModeQueryFactory.cpp:43-51 as manufacturer "Android", model "Android Auto" -
+  confirmed against the real 2018 Uconnect. Google's own desktop-head-unit reference tool
+  reports a different model string ("Android Open Automotive Protocol", confirmed via logcat
+  on 2026-09-17), so both are listed here. `version` is deliberately omitted: head units differ
+  on what they send, and a mismatch fails the filter silently.
+-->
+<resources>
+    <usb-accessory manufacturer="Android" model="Android Auto" />
+    <usb-accessory manufacturer="Android" model="Android Open Automotive Protocol" />
+</resources>

gearslip/src/main/res/xml/touch_relay.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+  Gearslip never reads screen content: it only needs canPerformGestures, which is what lets
+  dispatchGesture replay a head-unit touch onto whatever app is mirrored. No event types are
+  requested, so the service is notified of nothing.
+-->
+<accessibility-service xmlns:android="http://schemas.android.com/apk/res/android"
+    android:accessibilityFeedbackType="feedbackGeneric"
+    android:canPerformGestures="true"
+    android:description="@string/touch_relay_description"
+    android:notificationTimeout="0" />