| /aosp14/frameworks/base/native/android/ |
| H A D | libandroid_net.map.txt | 8 # These functions have been part of the LL-NDK since API 24.
12 # These functions have been part of the LL-NDK since API 29.
17 # These functions have been part of the LL-NDK since API 31.
21 # These functions have been part of the LL-NDK since API 33.
|
| /aosp14/frameworks/base/core/proto/ |
| H A D | README.md | 13 * Inner messages whose containing messages have the `Proto` suffix do not
14 need to have a `Proto` suffix. E.g:
34 1. If the proto represents the structure of an object, it should have `Proto` as
|
| /aosp14/frameworks/base/packages/SystemUI/docs/ |
| H A D | physics-animation-testing.md | 2 …usly difficult to test, since they’re essentially small simulations. They have no set duration, an…
7 …reports that motion has slowed to an invisible level. For this reason, we have to actually run the…
9 …t**, a subclass of PhysicsAnimationLayout whose animation-related methods have been overridden to …
11 …hich call ```latch.countDown()```. Once all of the properties’ animations have completed, the latc…
|
| H A D | corestartable.md | 10 Unlike Activities, Services, and similar Android constructs, CoreStartables do not have unique
11 context, and have no lifecycle methods except for a singular `#start` method that is called once.
40 that doesn't have a clear initialization path in existing code, strongly consider defining a _new_
|
| H A D | executors.md | 11 threads or delaying the execution of a Runnable. We have an implementation of
62 We do not currently have support for creating an Executor on a new, virgin
131 Executors have no concept of message handling. This is an oft used feature of
174 If you feel that you have a use case that this does not cover, please reach out.
186 We have a [FakeExecutor][FakeExecutor] available. It implements
255 until none of them have ready work.
256 Useful if you have Executors that post
283 Here we have more fine-grained control:
300 One gotcha of direct-clock-advancement: If you have interleaved Runnables split
|
| H A D | dagger.md | 16 stubs have been added to Dependency to proxy any gets through to the instances
38 To have the single instance span all of SystemUI and be easily accessible for
59 If you have an interface class and an implementation class, Dagger needs to
72 If you have a class that you want to make injectable that has can not
106 Similarly, if you are working on a custom version of SystemUI and have code
|
| H A D | physics-animation-layout.md | 44 …translationY animations, and calls the provided callbacks only when both animations have completed.
52 …ction to call when the animations for every property (including chained animations) have completed.
71 …perties before the animation begins. Property methods like `translationX` have an overloaded varia…
72 …`, where the endAction is called when both translationX and translationY animations have completed.
73 …Action)`, which starts all of the animations and calls the end action when they have all completed.
76 …g, begin fading them out, and then remove them all from the parent once all bubbles have faded out:
104 …alfway down the left side of the screen). When the translation animations have finished following …
122 …roller will no longer be able to start animations. Attempts to do so will have no effect. This is …
|
| H A D | status-bar-data-pipeline.md | 22 Android U, **only the wifi icon and mobile icons have been implemented in the
43 define `Model` objects at this layer so that clients do not have to rely on
61 These have already been implemented and configured. ViewBinders replace the old
71 Putting that altogether, we have this overall architecture diagram for the
109 pipeline. As a general rule, any change that would have gone into
190 production classes, any changes made above will have to be implemented for demo
|
| /aosp14/frameworks/base/tools/dump-coverage/ |
| H A D | README.md | 3 …t designed to dump coverage information for a process, where the binaries have been instrumented b…
9 Note that these examples assume you have an instrumented build (userdebug_coverage). Here is, for e…
34 And you should have `coverage-file.ec` on your machine under the folder `~/path-on-your-computer`
|
| /aosp14/frameworks/base/apex/jobscheduler/service/java/com/android/server/tare/ |
| H A D | README.md | 21 actions have a higher price than less important actions and all actors have perfect information and
38 ARCs are required to perform any action while in the background. Some actions may have a fixed cost.
39 Others may be more dynamic (some may even allow apps to bid higher ARCs for some actions to have
40 them prioritized). If the app doesn't have enough ARCs, the action can't be performed. Apps are
57 will likely have a unique set of actions that apps can perform, and may choose to reward apps for
89 (allocated) that number among the installed apps, intending to have some left over that could be
99 and some apps may not have been able to perform work even though they otherwise should have been.
126 * Have a separate "account" for critical/special actions. In other words, have two accounts for each
128 actions such as expedited job execution. The second account would have a lower maximum than the
139 then have a small auction when the system needs to decide which app to perform the action for
|
| /aosp14/frameworks/base/libs/WindowManager/Shell/src/com/android/wm/shell/docs/ |
| H A D | changes.md | 21 pattern is to have a single `<Component name>Controller` that handles the initialization of the
31 from the Shell and vice versa. The current pattern is to have a parallel `Optional<Component name>`
35 In addition, because components accessible to SysUI injection are explicitly listed, you'll have to
53 - Create an implementation of the interface binder's `Stub` class within the controller, have it
56 - Make the controller implement `RemoteCallable<T>`, and have all incoming calls use one of
99 Launcher doesn't currently build against the Shell library, but needs to have access to some shared
|
| /aosp14/frameworks/base/ |
| H A D | OWNERS.md | 17 typically have more granularity than `core/java/`, since they can be refactored
21 * `services/` contains several system services that have been isolated from the
28 * Finally, some teams may have dedicated top-level directories:
|
| H A D | ProtoLibraries.bp | 100 // Protos have lots of MissingOverride and similar.
127 // Protos have lots of MissingOverride and similar.
154 // Protos have lots of MissingOverride and similar.
|
| /aosp14/frameworks/base/core/proto/android/server/ |
| H A D | biometrics.proto | 32 * Authentication either just called and we have not transitioned to the CALLED state, or
55 * passive modalities such as Face or Iris should have this state. Note that for passive
62 * Paused, but "try again" was pressed. Sensors have new cookies and we're now waiting for
168 // Total number of operations that have been handled, not including the current one if one
|
| /aosp14/frameworks/base/services/core/java/com/android/server/rollback/ |
| H A D | README.md | 70 native services have been affected by an update, *any* crashing native service
106 packages in the install session, including the parent session, have the
134 restored for all users, even for credential encrypted users that have not been
164 This allows the caller to retry the rollback if they have reason to believe it
206 For rollback of staged installs, you have to manually reboot the device for the
286 have rollback enabled for them.
289 necessary classes.dex or .so files used by the app. It must not have classes.dex
290 stripped or have the .so files extracted. If the system apk is not self
294 potential side effects that updating an app may have, such as changes to
|
| /aosp14/system/core/fs_mgr/ |
| H A D | README.overlayfs.md | 13 right-sized, and have been deduped at the block level to compress the content.
65 **/mnt/scratch/overlay** directory for A/B devices that have
87 permits legacy behavior for systems that do not have overlapping
117 space fastbootd, is not detected, thus a partition may have
120 we have made an architectural decision to not utilize
|
| H A D | Android.bp | 153 // It does not have a stable interface.
168 // It does not have a stable interface.
178 // It does not have a stable interface.
|
| /aosp14/frameworks/base/packages/CarrierDefaultApp/ |
| H A D | proguard.flags | 1 # Keep classes and methods that have the @JavascriptInterface annotation
|
| /aosp14/frameworks/base/test-mock/ |
| H A D | Android.bp | 34 // android.test.mock APIs references to. We need to have the classes in
35 // source code form to have access to the @hide comment which disappears
|
| /aosp14/system/core/janitors/ |
| H A D | OWNERS | 1 # OWNERS file for projects that don't really have owners so much as volunteer janitors.
|
| /aosp14/system/core/fs_mgr/libfiemap/ |
| H A D | README.md | 18 a large image may have to be split into multiple files. On Ext4 the limit is
59 on an FBE/unencrypted device we will have multiple loop devices. In this case,
60 we create a device-mapper device as well. For each loop device it will have one
|
| /aosp14/frameworks/base/services/tests/PackageManagerServiceTests/apks/ |
| H A D | Android.bp | 14 // Every package should have a native library
|
| /aosp14/frameworks/base/core/tests/coretests/apks/ |
| H A D | Android.bp | 14 // Every package should have a native library
|
| /aosp14/frameworks/base/wifi/ |
| H A D | MOVED.txt | 1 Source code and tests for Wifi module APIs have moved to
|
| /aosp14/frameworks/base/core/jni/ |
| H A D | android_view_InputEventReceiver.md | 13 7. The batched event is sent to the app, along with any of the other events that have come in.
19 …ndleEvent`. At this point, the app is expected to read in the events that have come in to the sock…
39 1. Even if events have been read by `InputConsumer`, `consume` will return `NULL` event with status…
|