One, understand the Framework layer
In fact, Framework can be simply understood as a warehouse of some APIs. Android developers implement some basic functions and provide them to the upper layer to call through interfaces. We can call them repeatedly. We can say that the Framework layer is really the layer implemented by the Java language. In this layer The defined API is written in Java language. But because it includes JNI methods, JNI uses C/C++ to write the interface, calls the underlying methods in the core library layer according to the function table query, and finally accesses the Linux kernel. Then there are two roles for the Framework layer.
1. Use the Java language to write some standardized modules and encapsulate them into a framework for APP layer developers to call and develop mobile applications with special services.
2. Use the Java Native Interface to call the native method of the core lib layer. The JNI library is loaded when the Dalvik virtual machine starts. Dalvik will directly address this JNI method and then call it.
2. Mastery of core content
Take a look at how much you have mastered the following distributed transaction knowledge points:
- Activity Framework structure and operation framework
- FrameWork startup process
- System Core Service (System Server)
- way of communication
- Kernel technology
- Abnormal principle
Most of the distributed tutorials on the debugging market are limited to theoretical knowledge explanations, and there are few specific implementation cases. Here I will share with you a note of "Android Framework Compiled Kernel Analysis" to take you through the Android Framework in 3 days For the core principle problems and solutions, friends who need this distributed transaction note can get a free way at the end of the article!Not much BB, look at the catalog and main content
Due to the excessive content of the document, in order to avoid affecting everyone's reading experience, only part of the content is shown in screenshots. There is a free way to obtain the detailed and complete version at the end of the article!
Due to space reasons, this note has been sorted into a PDF document. If you need a complete document of distributed transaction notes, please comment 666, just check my [ Github ]!
Direct collection link: [ Android Senior Architect ]
Cover of "Android Framework Compiled Kernel Analysis"
- 452 pages of PDF, 62150 words, 20 chapters covering all the knowledge points in the Android Framework, it can be said that it is the most systematic and comprehensive note on the entire network! It only took 2 months to organize it. It’s not just a random piece. Every chapter has been pointed out by Android experts, so the accuracy and rationality are beyond doubt!
"Android Framework Compiled Kernel Analysis" The
first chapter in-depth analysis of Binder
The second section of Binder Driver
Section 3 Binder Driver Revisited
Section 4 Binder starts ServiceManager
Section 5 Get ServiceManager
Section 6 Registration Service (addService)
Section 7 Get Service (getService)
Section 8 framework layer analysis
Section 9 How to Use Binder 
Section 10 How to Use AIDL 
Section 11 Binder Summary
Section 12 Binder Interview Questions Full Analysis
Chapter 2 In-depth analysis of Handler message mechanism
Section 1 Macro Theoretical Analysis and Message Source Code Analysis
Section 2 Source code analysis of MessageQueue 
Section 3 Looper’s source code analysis 
Section 4 Handler source code analysis 
Section 5 Summary of the realization principle of Handler mechanism
Due to space reasons, this note has been sorted into a PDF document. If you need a complete document of distributed transaction notes, please comment 666, just check my [ Github ]!
Direct collection link: [ Android Senior Architect ]