This issue also happens on fajita, though the issue template will not let me fill that in
The phone is connected to the car using a USB cable, car initiates the connection and Android Auto is triggered on the phone.
Current Behavior
** This also affects fajita **
The phone is connected to the car using a USB cable, the car only sees a MTP device, and Android Auto is never triggered or detected. With USB debugging on, the phone reports that a device is connected for USB debugging.
Head Unit Reloaded, a third party implementation of the Android Auto head unit works sometimes, we got it to work on the 6T, but the 7T Pro has the same behavior as plugged into a real car.
Works on both phones using official LineageOS with the full NikGapps package.
Tested with two Ford Focus Mk 4 cars, running Ford Sync 3.
Possible Solution
Maybe a protocol/default app association is not set correctly somewhere?
Steps to Reproduce
1. Plug USB cable into USB port in a car
2. Start up the car so it's ready for Android Auto connections
3 .Connect USB cable to phone
4. Phone does not respond
5. consider making your bot a bit less stringent about issue templates
Build date
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce
/device hotdog /version eleven_plus