Book Image

Android System Programming

By : Roger Ye, Shen Liu
Book Image

Android System Programming

By: Roger Ye, Shen Liu

Overview of this book

Android system programming involves both hardware and software knowledge to work on system level programming. The developers need to use various techniques to debug the different components in the target devices. With all the challenges, you usually have a deep learning curve to master relevant knowledge in this area. This book will not only give you the key knowledge you need to understand Android system programming, but will also prepare you as you get hands-on with projects and gain debugging skills that you can use in your future projects. You will start by exploring the basic setup of AOSP, and building and testing an emulator image. In the first project, you will learn how to customize and extend the Android emulator. Then you’ll move on to the real challenge—building your own Android system on VirtualBox. You’ll see how to debug the init process, resolve the bootloader issue, and enable various hardware interfaces. When you have a complete system, you will learn how to patch and upgrade it through recovery. Throughout the book, you will get to know useful tips on how to integrate and reuse existing open source projects such as LineageOS (CyanogenMod), Android-x86, Xposed, and GApps in your own system.
Table of Contents (15 chapters)

Build variants

When building for a particular product, it's often useful to have minor variations on what is ultimately the final release build. By using different build variants, it can help the different parties in the product development cycle. There are primarily three kinds of build variant in the AOSP so far. The engineering build is the default one and is suitable for development work. In this type of build, the product security policy is not fully enforced and the debugging mechanisms are turned on. It is easy for engineers to test and fix issues with an engineering build.

The second flavor is user build, which is used for the final release. All debugging mechanisms are turned off and the product security policy is fully enforced. The third flavor is userdebug, which is in between the engineering build and user build. This type of build can be used in the field test, which is also used by the end users...