This article comes from I share within the company of a training content, because 100% is AOSP open source content, so should be able to share out to everyone.
The Android L was launched at the Google I/O developer conference this June 2014, which includes a number of improvements, including the new material design interaction, a card-style notification bar, support for 64-bit and art, etc. This article focuses on some of the new multimedia-related features.
Since the release of Android L only half a year, regardless of domestic or foreign related information is scarce, a lot of content I can only be in the Android developer website on the L version of the text of the words on the basis of the introduction, to delve into the Android system source code, open source community, and a variety of foreign forums to collate information, and then integrate some of their own understanding. Some of the details may not be exactly right, but please forgive me.
Because the training ppt is written in English, so a sentence translation, direct mapping bar.
First, MediaBrowser API
Second, using Mediaprojection to screen video
III. notification of new types of Mediastyle (Notification)
Iv. Mediasession and Mediacontroller
V. Native support h.265 Soft decoder
Six, audio and video "tunnel" playback mode (tunneled Playback mode)
Low-latency audio input (LO latency audio inputs)
Eight, audio sampling of floating-point support
Nine, 7.1 channel audio stream mix
X. On the improvement of speech synthesis
Xi. Opus Audio Decoder
12. USB Audio
13. Summary
Finally about the Android L upgrade, Google signal is what, a simple talk about my own understanding. From the previous mentioned USB audio, multichannel mixing, low-latency audio and other feature can feel that Google began to pay more attention to the professional audio market, by improving the performance of audio performance, add more professional-grade features to meet the needs of audio processing professionals and enthusiasts, Android is not limited to the positioning of portable device operating systems.
In addition, Google is carefully prepared to meet the popularity of 4K images and the next generation of video compression format h.265, but on the other hand, is also actively developing their own free audio and video solutions, including VP9 and Opus. Google is also working to improve the video playback framework for 4k video playback, such as the tunneled playback mode, which is designed to reduce power consumption.
In video recording, Google allows apps to record screens without root privileges, which will inspire more applications to develop features like remote XXX.
From the speed of development of various APIs, Google will continue to evolve the front-end UI design, class-level refactoring will continue, so the application should not attempt to invoke the hidden API through reflection, which will reduce the device compatibility of the app.
my understanding of Android compatibility is that both app developers, handset makers, and chip makers are involved in the AOSP Open source project, and as members of the open source community are obliged to strive to maintain the compatibility of the entire Android ecosystem, Adhere to the basic open source cooperation guidelines, rather than go through a variety of hack, unconventional technical means to achieve some "cool" function, which not only broken the overall compatibility of the Android ecosystem, but also hurt others and become the eyes of other manufacturers "pig-like teammates", in other words, in the open source project to have " Environmental awareness ".
A brief analysis of new multimedia-related features in Android 5.0
