This piece of article from Http://blog.csdn.net/andywuchuanlong, reproduced please explain the source, thank you!
Before the colleague asked some of the questions, can remember I will write it, for beginners reference. The problem is as follows:
1, four components all end destruction, why is the application still running in the background? Why can't I really quit the app?
2, the service in Android is running in the background services, it seems that the thread is also in the background asynchronous execution, why the service can not be replaced by the thread?
3, when using view.inflate (context, resource, root) to load the layout file, if root is null, why does the layout file's root node set properties such as margin, height, etc. do not work?
4, when the network request, we all need to open the thread, then use Asynctask or use Thread+handler mode?
5, why ScrollView nested in the Viewpager, Viewpager height problems and sliding failure?
6, in the project art general to us to cut a few sets of pictures, to be able to fit the Android fragmented terminal?
7, Bitmap memory recovery problem
8, the Java language is platform-independent, in order to ensure that some fixed data or algorithm security, we generally use JNI technology to write it in C, but the JNI is related to the specific platform, then this way is not against the Java language cross-platform characteristics?
9. What is the Convertview multiplexing process in the ListView, which is bound to be reused?
10. What is the relationship between the IPC mechanism and the AIDL mechanism in Android? Under what circumstances will aidl be used in the project?
11. What is the connection between service, Binder and Aidl?
The above questions I will be in the form of a separate article to write out, welcome to come to spray water exchange.
I asked my colleague.