Default Bypass for Android Auto Speed Restrictions (Movement Lock)

[dogukanishere]

Problem: Currently AABrowser is flagged by Android Auto's safety protocols as soon as the car starts moving resulting in the "Restricted while driving" overlay. While external tools like KingInstaller or AAAD attempt to fix this by spoofing the Installer ID, it often fails due to signature conflicts or OS-level updates.

Suggested Technical Improvements: To provide a seamless experience without requiring external patchers, I suggest implementing the following changes into the app's core architecture:

App Category Masking: Instead of declaring the app under the Browser category in the AndroidManifest.xml, consider re-classifying it as a Media or Navigation template. Android Auto allows media apps to remain interactive during motion (for playlist scrolling, etc.), which is how apps like Fermata Auto bypass the lock.

Internal Installer ID Spoofing: Hardcode or simulate the com.android.vending (Google Play Store) installer ID within the app logic. This would ensure that the system recognizes the app as a "trusted" source by default, bypassing most "Unknown Sources" restrictions.

Intercepting Driving Status Callbacks: Implement logic to ignore or override driving_status or car_speed callbacks from the Android Auto API at the UI level. By preventing the UI from reacting to the "driving" state, the browser interface can remain active regardless of the vehicle's speed.

These changes would significantly improve usability for passengers and parked-to-driving transitions.

[kododake]

Hi @dogukanishere

1. Installer ID Spoofing
   Installer IDs are managed by the OS Package Manager. An app cannot spoof its own ID via internal code. "Unknown Sources" can already be enabled via Android Auto Developer Settings to bypass this.

2. System-Level Overlay
   The "Restricted while driving" overlay is enforced by the Android Auto host (Google Play Services), not the app's UI. Overriding callbacks in the app does not prevent the system from forcibly covering the screen.

3. Category & Store Review
   To run on a head unit without developer mode, the app must be signed and distributed by the Play Store. Since Android Auto does not officially support browsers, the app would be rejected during the mandatory review process regardless of its category.

Conclusion
If you have a working solution for these limitations, please implement the code, test it on a physical head unit to verify it works, and submit a Pull Request.

[dogukanishere]

Thank you for the detailed explanation. I think there’s been a slight misunderstanding; I am not a developer. I was simply sharing these as suggestions and feature requests from a user's perspective. I appreciate the technical context you provided, as it helps me better understand the current limitations.

[kododake]

Thank you for the clarification. I appreciate your feedback from a user's perspective, as it’s always helpful to hear different ideas.
​Actually, I am currently experimenting with some other workarounds. It might take a long time to find a stable solution, so I would appreciate your patience. Thank you for your support and cooperation!