MediaControlView2's setTimeout API is removed and MCV2's visibility
handling logic is moved into VideoView2.
Test: build
Change-Id: I149119148f159c78e86c5061d247f0a434310719
This stops calling
MediaController2.ControllerCallback.onPlaybackStateChanged() when the
controller is connected.
This is the preliminary step towards sending session's current values
to a controller when it's connected.
Bug: 72547163
Test: Run all tests once
Change-Id: I4b5b2ec008500cc71679883792b0ef44f1c24aad
This includes two changes.
- Change all methods in MediaSession2.BuilderBase signatures from
public to package private.
- Subclasses of MediaSession2.BuilderBase (MediaSession2.Builder,
MediaLibraryService2.MediaLibrarySessionBuilder) now inherit all
methods from its super class and change method signatures to public
Changes are needed to workaround and fix following issues.
- Hidden super class's methods aren't shown in the Javadoc and 3rd
party apps cannot use them.
- Public generic methods in the super classes are shown in the Javadoc
with the generic types (e.g. 'U setSessionCallback()' instead of
'Builder setSessionCallback()')
- Stub classes for tests are automatically generated, but it somehow
fails to generate stub for the BuilderBase (seems like a bug)
Test: 'm update-api' and checked generated javadoc
Change-Id: I6f635624ef806578ab79d080424f11cb637d7984
* changes:
MediaSession2: Rename BrowserRoot to LibraryRoot and move to updatable
MediaSession2: Move MediaSession2.CommandButton to updatable
MediaSession2: Move MediaSessionService2.MediaNotification to updatable
There are several places across the OS where Java code is simply
copying data between two points, which requires bringing that data
out into userspace before going back into the kernel. (That's pretty
lame.) The patches for the recent Meltdown/Spectre security issues
have made this overhead even worse, so it's finally time to move this
copying directly into the kernel.
This change adds a couple new FileUtils.copy() methods which inspect
the given streams/FDs, and attempt to do as much optimization as
possible before falling back to a slower userspace-based copy.
Benchmarks are showing typical improvements of 44% for 32KB files,
50% for 32MB files, and 35% for 32MB pipes.
Plenty of tests are included, and there's a simple kill-switch that
can be used to enable/disable the feature if it starts causing any
trouble. (A future CL will enable the optimizations.)
Test: bit FrameworksCoreTests:android.os.FileUtilsTest
Test: vogar --mode app_process --benchmark frameworks/base/core/tests/benchmarks/src/android/os/FileUtilsBenchmark.java
Bug: 71932978
Change-Id: I52518d529da5d961610998b9f61399064d8025cd
This is the preliminary step toward permission check.
Bug: 72618604
Test: Run all MediaComponents test once
Change-Id: I64679dce0c70fd322fa7819e4ba15ba52601d021
Added more explanations for onFftDataCapture method.
Fixed some syntax errors.
Bug: 65673222
Test: make docs
Change-Id: Ia793e90061de9bf78ba2774102ceccc766c74e27