First knowledge of Android 4.1-July 13

At the beginning of July 13, I read the following: 1Init has not changed much. We can see from init. rc that the rule has not changed, but init. rc has some new settings. It seems that it is more dependent on some information about the kernel. 2App_process has not changed much, that is, zygote has not changed. 3SystemServer has changed a lot, adding a few strange services, and some services start to be controlled by system attributes. For example, audioService is controlled by "system_init.startaudioservice ". 3.1Added the SchedulePolicyService mentioned yesterday to control the adjustment of media-related process scheduling policies. Note that it is a scheduling policy, not a priority. 3.2Added a DreamManagerService, which uses ScreenSaver and screen saver. By default, the AOSP version starts the com. google. android. javasclock/com. android. javasclock. Screensaver service. 3.3Added SerialService to support operations on devices on the serial port. 3.4CommonTimeManagementService is added, indicating that the configuration of the native Common Time service is managed. 3.5Added CertBlacklister, provides a simple mechanism for updating the platform blacklists for SSL certificate public keys and serial numbers. SSL blacklist 3.6New UpdateLockService: Provides update locks, Advisory wakelock-like mechanisms by which processes that shocould not be interrupted for OTA/update purposes can so advise the OS 3.7Added NsdService and Network Service Discovery Service Network service Search Service 3.8Added LockSettingsService, which is related to the security functions such as entering passwords and gestures on the screen lock page. The lock screen information of each user can be saved (Android has finally taken a solid step for multiple users. The UserManager of anyway and PackageManagerService has basically not changed. Maybe the functions supported by multiple users are not completed yet ?) 3.9The name of EntropyService is changed to EntropyMixer. I really don't know. How can I change my name for this stuff ?? 3.10Added InputManagerService. Previously, this elder brother was in WindowManagerService and is now independent. 4Input System Changes 4.1Independent InputManagerService 4.2The general process has not changed, and the main members are still there, such as InputHub and InputManager. They have added a mechanism to notify the java layer after detecting the input device at the underlying layer. If you understand the 4.0.4 input system, there is no problem. 5Description of newly added interfaces: 5.1Added the MediaRouter class. The APP can select the device from which the sound is sent (such as a USB speaker or headset ). In the past, this part of work was done by the system based on the write-down policy and can now be set by the APP. This function will surely lead to a bunch of audiopolicy brothers, especially when apps do not follow the rules (such as blind Voice routing, because the system currently does not fully support any sound routing of any device. The reason is that it has something to do with hardware) 5.2Added the MediaCodec class to support obtaining codec data directly from the native layer. Fuck. From this article, we can clearly see that java is more and more just a language tool on the android platform. To be a good thing, the status of professionals is highlighted! What do you mean? For example, can anyone who can speak English be really cool? English is only a tool for communication. It can be used for coding and decoding, graphic and image algorithms, and network development. Therefore, in this comparison, Speaking English is a fart. I hope that the students will learn their professional knowledge quickly. The other and other details are not seen. If you are familiar with android, you can perform an incremental analysis of the entire change in just two hours.