Absolutely! All those post-deployment setup steps can be fully automated using ADB commands, which integrates seamlessly with your existing APK deployment workflow. Let’s walk through each task with concrete, tested commands:

First, you’ll need the package name and main launchable activity of your target app. You can extract this directly from the APK file using aapt (part of the Android SDK):

aapt dump badging /path/to/your/app.apk | grep launchable-activity

This will output something like:

launchable-activity: name='com.yourcompany.yourapp.MainActivity' label='' icon=''

Once you have those values, run these ADB commands to skip the manual selection prompt and set your app as the default home screen:

# Clear any existing default home app
adb shell cmd package clear-home

# Set your app as the new default home screen
adb shell cmd package set-home-activity com.yourcompany.yourapp/com.yourcompany.yourapp.MainActivity

This bypasses the "Always/Just Once" dialog entirely by directly configuring the system default.

You don’t need to simulate tapping the version number repeatedly—you can toggle these settings directly via ADB:

# Enable Developer Mode globally
adb shell settings put global development_settings_enabled 1

# Enable Stay Awake (keeps screen on while charging, which is standard for head units)
# Value options: 1=AC charging, 2=USB charging, 3=all charging states
adb shell settings put global stay_on_while_plugged_in 3

The stay_on_while_plugged_in setting maps directly to the "Stay Awake" toggle in Developer Options, so this will enable it without navigating the system UI.

First, confirm the package name and service class for Google TTS (it’s almost always com.google.android.tts for standard builds). Then run:

# Set Google TTS as the default engine
adb shell settings put secure default_tts_engine com.google.android.tts/com.google.android.tts.service.GoogleTTSService

# Optional: Verify the setting (should return the Google TTS package)
adb shell settings get secure default_tts_engine

This will override any existing TTS engine without requiring manual selection in the system settings.

Integrating into Your Deployment Script #

Just append these commands to your existing loop. Here’s an example of how the full script might look:

apk_files="/path/to/apks/*.apk"
target_package="com.yourcompany.yourapp"
target_activity="com.yourcompany.yourapp.MainActivity"

for apk in ${apk_files}; do
    adb install -r ${apk}
done

# Post-deployment setup
adb shell cmd package clear-home
adb shell cmd package set-home-activity ${target_package}/${target_activity}
adb shell settings put global development_settings_enabled 1
adb shell settings put global stay_on_while_plugged_in 3
adb shell settings put secure default_tts_engine com.google.android.tts/com.google.android.tts.service.GoogleTTSService

Notes for Edge Cases #

• Android Version Differences: Most commands work on Android 8.0+. For older versions, you might need to adjust settings commands (e.g., using system instead of global for some keys).
• OEM Customizations: Some car head units have modified Android builds—test these commands on your specific test benches first to ensure compatibility.
• Google TTS Availability: Make sure Google TTS is pre-installed or included in your APK set; if not, add an adb install command for the Google TTS APK first.

内容的提问来源于stack exchange，提问作者evadeflow