It's dangerous to go alone! Take us with you!

In this episode, we're joined by our very own Jon West and Nikhil Punathil at Esper to discuss a key part of what we do here — getting AOSP up and running on ARM and x86 hardware. If you want to port AOSP, it's not as easy as just compiling an image from Google's git repos and slapping it onto a device.

• 05:59 - What is a device bring-up? What are some of the challenges in doing a bring-up?
• 10:58 - How do AOSP developers deal with a lack of kernel source code?
• 18:16 - How did Project Treble affect building AOSP?
• 26:54 - How does Android on x86 differ from Android on ARM?
• 29:48 - What problem does the Generic Kernel Image try to solve?
• 35:22 - How long does Google support a particular AOSP release? What can AOSP developers do once support has ended?

Android Bytes is hosted by Mishaal Rahman, Senior Technical Editor, and David Ruddock, Editor in Chief, of Esper.

• Mishaal's Twitter
• David's Twitter

Esper enables next-gen device management for company-owned and managed tablets, kiosks, smart phones, IoT edge devices, and more.

For more about Esper:

• Esper Blog
• Mobile Device Management (MDM) Guide
• Android MDM Guide
• iOS MDM Guide
• MDM Solutions
• MDM APIs & SDK

New from the Esper blog:

• Edge AI
• Edge devices & edge computing

Our music is "19" by HOME and is licensed under CC BY 3.0.