Fast boot and SecureBoot together: QuickBoot's approach to speed without security compromise

The specific challenges of Android on IoT hardware

Android's rich UI framework, broad driver ecosystem, and built-in OTA infrastructure make it an attractive embedded OS choice. But applying QuickBoot's snapshot approach to Android introduces a specific challenge: what happens to app installations, updates, and configuration changes that occur after the snapshot was captured?

Regenerating the snapshot after every change is impractical at scale. Managing the delta between snapshot state and current runtime state is the core implementation challenge -- and it's exactly what Android Pack solves.

What Android Pack enables

• Package-level Android app install, update, and uninstall after QuickBoot restore
• Persistence of language settings, volume, and other Android configuration values
• Over-the-Air (OTA) update support
• Factory reset support

Android Pack 3.0: two operation modes

Normal mode is ideal for dedicated embedded devices where maximum boot speed is the primary requirement. Support mode suits general-purpose Android devices — tablets, consumer smart devices — where broad application compatibility matters more.

How Android Static Mode Plus works

After a QuickBoot restore, Android Pack 3.0 detects settings and state changes that occurred after snapshot capture, and reflects them according to the selected operation mode. This maintains the speed advantage of snapshot-based boot while preserving the flexibility of the Android ecosystem.

Verified SoC platforms

• Telechips TCC8050 EVB (Android 13)
• MediaTek MT2712 EVB (Android 10)
• NXP i.MX 8M EVK (Linux)
• STMicroelectronics STM32MP1 EV1 (Linux)

Implementation note: hardware layer as open source

QuickBoot's hardware-dependent layer is distributed as open source, dramatically reducing porting effort to new Android SoC platforms. This provides a practical starting point and reduces porting risk for teams building on common IoT SoC families.