Thoughts on Android technology insider-system volume

Chapter 1 kernel mechanism and structure analysis of Android is full of "very simple" and there is no need to introduce it if it is simple. Besides, these simpleCode, Called manyProgramIt may not be well written.

Chapter 2: Analysis of Several CPP files later in Android IPC Mechanism-binder, you can consider the class diagram structure of C ++ or UML diagram. Code and text are everywhere, making people unable to see it at all. Even if you look at the source code, it is estimated that it is enough.

In Chapter 4th "Power Management", 4.3 (Android power management mechanism), most of them are introducing state migration. You can consider drawing a state machine diagram. For an introduction to the state machine, consider the chapter in Mr. Li xianjing's "System Programmer growth plan". At least I can see his chapter more clearly than this chapter. The following wake-lock theme also has the same problem. No picture, no truth.

Chapter 4 describes the driver and describes each driver clearly. Basically impossible, there are still too few images, full of kernel-driven code. Ai .......

Chapter 6th is the same as Chapter 5th. In fact, a WebKit can write a lot of content, among which WebKit is written in C ++, or draw more class diagrams. It is estimated that people who have not read c ++ primer several times have many problems with C ++ code.

I have read the last three chapters and I feel like Dalvik is still allArticle.

In general, the four words "very simple" have appeared countless times. You need to know that Google has spent a lot of effort to write so much code, the four words are too general. No one in China can do this now !! It is helpful for the heroes who want to enter the android underlying layer. Android involves a lot of things.