Bluetooth, Sensors & Auto
ADVANCED › Emerging
Tests BLE GATT, the Android sensor framework, and Android Automotive OS versus Android Auto.
Hardware-integration questions reveal whether you can work with constrained, lifecycle-sensitive APIs without leaking battery or mishandling permissions. Interviewers probe BLE's GATT model and the Android 12 Bluetooth permission changes, correct sensor-listener lifecycle and rate selection, and the frequently-confused distinction between Android Auto and Android Automotive OS. Expect edge cases like neverForLocation scanning, background sensor restrictions, and driver-distraction template limits.
What this covers
- BLE GATT architecture: services, characteristics, descriptors, UUIDs, and central/peripheral vs client/server roles
- Android 12+ Bluetooth runtime permissions (SCAN/CONNECT/ADVERTISE) and the neverForLocation flag
- BLE flow: scanning, connectGatt + BluetoothGattCallback, service discovery, read/write/notify
- Sensor framework: SensorManager, registering/unregistering listeners, delays, and battery best practices
- Hardware vs composite sensors and the device coordinate system (remapCoordinateSystem)
- Android Automotive OS vs Android Auto and building car apps with the Car App Library templates
Study this topic
- Bluetooth, Sensors & Auto explained: the guided lesson
- 14 practice quiz questions
- 9 revision flashcards
- Bluetooth, Sensors & Auto interview questions and answers