summaryrefslogtreecommitdiffstats
path: root/Android.mk
Commit message (Collapse)AuthorAgeFilesLines
* Generate SDK docs for v7 support library packages.Jeff Brown2013-04-261-13/+22
| | | | | | | | | | | | This change required fixing some bugs in how AAPT handles qualified symbols such as "android:layout_height" when generating JavaDoc links. The links were being generated using the package name of the generated R file rather than the package name of the referenced symbol. These broken links caused the JavaDoc build to fail. Bug: 8175766 Change-Id: I52fbef27825a25abca960cb44b59c2132267e9d6
* Add ContentValues & CursorWindow to framework.aidlNick Pelly2013-04-231-1/+3
| | | | | | | | | | | | | | | | By adding these stubs, they will be automatically added to framework.aidl in sdk builds. This makes it easier for unbundled apps to pass these objects across AIDL calls. ContentValues & CursorWindow are already public Parcelables. It is an oversight that they were not already in framework.aidl. There are a lot of other public Parcelables that are missing from framework.aidl. This just fixes two commonly requested ones. Change-Id: If61e19b1206da1680413d9ea03de87a90b6d233e
* Hardware geofence API changes.Jaikumar Ganesh2013-04-171-0/+1
| | | | | | | | | | | | | b/8631678 1.GeofenceRequest object created. 2.MonitorState moved to a new callback 3.getTypeAndStatus separated to 2 calls. 4.Binder death implemented 5.geofenceChange callback name changed. 6.Parameters rearranged in some calls. Change-Id: I8fe9621186aeb49efeb0eef1821a2556afe03cfc
* add api level 18 to javadoc 'since' tagsScott Main2013-04-111-0/+1
| | | | Change-Id: Iea2e13ef2fad47d6a19d380b5655aeeda0414930
* GPS Hardware geofencing.Jaikumar Ganesh2013-04-101-0/+4
| | | | | | Add support for doing geofencing in hardware. Change-Id: I6d5015190e8d84e1f4beb1010ed977a71c1622d0
* New NotificationListenerService.Daniel Sandler2013-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | This is the best and only way for apps to listen for notifications: create a NotificationListenerService, wait for the NoMan to bind to you (as a result of the user checking a box somewhere in Settings and agreeing to a scary dialog box), and you'll start receiving notification posted and dismissed callbacks. Your service, while enabled, will also be able to clear one or all notifications. Use this power wisely. This change moves StatusBarNotification out of com.android.internal into android.service.notification. [Internal customers, including System UI and early users of the system-only listener binder API, will need to be updated.] Bug: 8199624 Change-Id: I1be46f823d4b3ddc901109ec1e085cd6deb740c2
* Use input transport for communications between app and IME.Jeff Brown2013-03-261-2/+0
| | | | | | | | | | | | | | | | | | | The input method manager service now supplies an input channel for communication while creating an IME session on behalf of the application. This change significanly reduces the overhead of IME event dispatch by using a standard input channel to send input events rather than using binder. This results in fewer thread context switches and fewer object allocations. What's more, the IME may perform additional batching of the motion events that it receives which may help it catch up if it is getting behind while processing them. Bug: 7984576 Bug: 8473020 Change-Id: Ibe26311edd0060cdcae80194f1753482e635786f
* Separate sessionCreated and finishedEvents callbacksMichael Wright2013-03-211-0/+1
| | | | | Bug: 8276952 Change-Id: If7051086c060fcce5d1e958ebbddec0784c851da
* DO NOT MERGE - Full backup/restore now handles OBBs sensiblyChristopher Tate2013-03-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | OBB backup/ restore is no longer handled within the target app process. This is done to avoid having to require that OBB-using apps have full read/write permission for external storage. The new OBB backup service is a new component running in the same app as the already-existing shared storage backup agent. The backup infrastructure delegates backup/restore of apps' OBB contents to this component (because the system process may not itself read/write external storage). From the command line, OBB backup is enabled by using new -obb / -noobb flags with adb backup. The default is noobb. Finally, a couple of nit fixes: - buffer-size mismatch between the writer and reader of chunked file data has been corrected; now the reading side won't be issuing an extra pipe read per chunk. - bu now explicitly closes the transport socket fd after adopting it. This was benign but triggered a logged warning about leaked fds. (Cherrypicked) Change-Id: I471f6348abcccb7bf1e1710b7beda9f23de53e14
* Add new WindowId for cross-process monitoring of focus.Dianne Hackborn2013-03-051-1/+3
| | | | | | | This is a class representing a window and providing limited interaction with it, which can be handed across processes. Change-Id: I22885f2064a9cc8c68d690a5858c2e28bbb6a0f3
* Initial version of BLE support for BluedroidGanesh Ganapathi Batta2013-02-271-0/+3
| | | | | | The API classes are hidden for now. Will unhide after API console approval. Change-Id: I8283dd562fd6189fdd15c866ef2efb8bbdbc4109
* New INotificationListener interface.Daniel Sandler2013-02-191-0/+1
| | | | | | | Use with INotificationManager.registerListener(). Limited to system only right now. Change-Id: I65b6a8778267022cdc5e58eb75ae607a54b1cc52
* Remove the unnecessary framework-res-package-targetYing Wang2013-02-121-6/+0
| | | | | | | Now the dependency should be correctly established by framework_docs_LOCAL_JAVA_LIBRARIES. Change-Id: I4c0ed2d3fb2855539027c7a0eb663f5747ae3ebd
* am e47033f9: am 4d9aa17a: am 87db373a: am 2328a779: am 9eb66b2d: Merge ↵Robert Ly2013-02-121-27/+0
|\ | | | | | | | | | | | | | | "Revert "makefile changes for gcm javadocs"" into jb-mr1-dev # Via Android Git Automerger (4) and Android (Google) Code Review (2) * commit 'e47033f9294056ab54c63608ab0a46de995fae63': Revert "makefile changes for gcm javadocs"
| * am 9eb66b2d: Merge "Revert "makefile changes for gcm javadocs"" into jb-mr1-devRobert Ly2013-02-121-27/+0
| |\ | | | | | | | | | | | | | | | # Via Android (Google) Code Review * commit '9eb66b2db4724da7a2d6575fee29840004f1a5df': Revert "makefile changes for gcm javadocs"
| | * Revert "makefile changes for gcm javadocs"Robert Ly2013-02-121-27/+0
| | | | | | | | | | | | | | | | | | This reverts commit 5f9922d7c3bce158e4c7a58929d4075e7c91e32e Change-Id: I310f27b231c6d64d6d407ae451b189a6ecf6b34f
* | | resolved conflicts for merge of 6db87978 to masterRobert Ly2013-02-121-23/+1
|\ \ \ | |/ / | | | | | | Change-Id: If439f5730e32fb2044a1e464fab0f6afb6bf1d08
| * | am dc8ee206: Merge "Revert "makefile changes for s.a.c"" into jb-mr1-devRobert Ly2013-02-121-23/+1
| |\ \ | | | | | | | | | | | | | | | | | | | | # Via Android (Google) Code Review * commit 'dc8ee2066a45adc6a57157c550e65317c8650ca0': Revert "makefile changes for s.a.c"
| | * | Revert "makefile changes for s.a.c"Robert Ly2013-02-121-23/+1
| | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 4c01047ec7b06aabeeae273c7871caa6c3029b84 Change-Id: I4465cfa678717ff7c202347ae6ad36d12d5393bc
* | | | remove sac make target to fix buildRobert Ly2013-02-111-21/+21
| | | | | | | | | | | | | | | | Change-Id: I44c51e12225cd0b1d82bfb70129fefa8ba66e8b4
* | | | am a578ade2: am 1c4311cc: am 4af36f4e: am 96b1b403: am 4c01047e: makefile ↵Robert Ly2013-02-111-1/+23
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | changes for s.a.c # Via Android Git Automerger (4) and Robert Ly (1) * commit 'a578ade219c07a04f7e8374939734de6ca7cc478': makefile changes for s.a.c
| * | | am 4c01047e: makefile changes for s.a.cRobert Ly2013-02-111-1/+23
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | # Via Robert Ly * commit '4c01047ec7b06aabeeae273c7871caa6c3029b84': makefile changes for s.a.c
| | * | makefile changes for s.a.cRobert Ly2013-02-111-1/+23
| | |/ | | | | | | | | | Change-Id: I501cc140994b2822c3df1f00639076f17765f256
* | | am 74e8693d: am ddc0a7bd: am 11fa4460: am 9da9a7cd: am e60b6023: Merge ↵Robert Ly2013-02-071-0/+27
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | "makefile changes for gcm javadocs" into jb-mr1-dev # Via Android Git Automerger (4) and others * commit '74e8693d310d75e98c5cf62340612d474f6f197b': makefile changes for gcm javadocs
| * | am e60b6023: Merge "makefile changes for gcm javadocs" into jb-mr1-devRobert Ly2013-02-071-0/+27
| |\ \ | | |/ | | | | | | | | | | | | # Via Android (Google) Code Review (1) and Robert Ly (1) * commit 'e60b6023ae4fdea932d0effc553dddc38117d235': makefile changes for gcm javadocs
| | * makefile changes for gcm javadocsRobert Ly2013-02-071-0/+27
| | | | | | | | | | | | Change-Id: I5653eb710f13f0a097cb1cf447469c4da7342fe2
* | | Merge "Move a few files from frameworks/opt/telephony to frameworks/base."Wink Saville2013-02-081-0/+1
|\ \ \
| * | | Move a few files from frameworks/opt/telephony to frameworks/base.Wink Saville2013-02-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because ISms.aidl imports PendingIntent we couldn't easily make opt/telephony part of the PDK. So this change moves ISms.aidl and SmsRawData.*, which ISms.aidl also imports, back to frameworks/base. Change-Id: Ia64c6e771d5a292d9bfebb413a43f3745df55c85
* | | | App ops: track system windows, monitoring changes.Dianne Hackborn2013-02-061-0/+1
|/ / / | | | | | | | | | Change-Id: I273e82bdad66ada3bf0f7ec9176bc304b9ee1ee8
* | | am 25f97435: am 5fca0efa: am 6cb87b08: am 65fd9811: am 2aa47b33: Merge "Doc ↵Dirk Dougherty2013-02-041-1/+2
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | change: remove htmlified samples from docs build for now. Samples are still downloadable thorugh SDK Manager." into jb-mr1-dev # Via Android Git Automerger (4) and others * commit '25f97435302d8468afeb4ade9f00d5243b393082': Doc change: remove htmlified samples from docs build for now. Samples are still downloadable thorugh SDK Manager.
| * | am 2aa47b33: Merge "Doc change: remove htmlified samples from docs build for ↵Dirk Dougherty2013-02-011-1/+2
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | now. Samples are still downloadable thorugh SDK Manager." into jb-mr1-dev # Via Android (Google) Code Review (1) and Dirk Dougherty (1) * commit '2aa47b336227a5d2bd1ee91f8fb4bd84be7e97f0': Doc change: remove htmlified samples from docs build for now. Samples are still downloadable thorugh SDK Manager.
| | * Merge "Doc change: remove htmlified samples from docs build for now. Samples ↵Dirk Dougherty2013-01-291-1/+2
| | |\ | | | | | | | | | | | | are still downloadable thorugh SDK Manager." into jb-mr1-dev
| | | * Doc change: remove htmlified samples from docs build for now. Samples are ↵Dirk Dougherty2013-01-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | still downloadable thorugh SDK Manager. Change-Id: I9cfa53e605f476daf6cf914f256df600e1d77f89
* | | | am 9dbf2479: am 960deffd: am 78bf7c9c: am 1e7e1104: am 4b7161cb: docs: ↵Scott Main2013-02-041-1/+1
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | switch devsite doc build to use templates-sdk # Via Android Git Automerger (4) and Scott Main (1) * commit '9dbf24797b82f4c70a75051050f32e53d1c35fe6': docs: switch devsite doc build to use templates-sdk
| * | | am 4b7161cb: docs: switch devsite doc build to use templates-sdkScott Main2013-02-011-1/+1
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | # Via Scott Main * commit '4b7161cbd44f64537d2c661e87868ea2689dd126': docs: switch devsite doc build to use templates-sdk
| | * | docs: switch devsite doc build to use templates-sdkScott Main2013-01-291-1/+1
| | |/ | | | | | | | | | Change-Id: I933cbafa0712de47b4bcf72d2a7c4f99bf18f930
* | | am 0dd75034: am d4f5ce03: am 6dfb4d0a: am 5c37151c: am e75cd4bf: docs: add ↵Scott Main2013-02-041-1/+2
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | hdf bool for deviste, used to change aspects of the templates # Via Android Git Automerger (4) and Scott Main (1) * commit '0dd750349004579ca3356a155eb8a86994a45df2': docs: add hdf bool for deviste, used to change aspects of the templates
| * | am e75cd4bf: docs: add hdf bool for deviste, used to change aspects of the ↵Scott Main2013-02-011-1/+2
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | templates # Via Scott Main * commit 'e75cd4bfd176fbb1483ec5e17edfbd993adce40f': docs: add hdf bool for deviste, used to change aspects of the templates
| | * docs: add hdf bool for deviste, used to change aspects of the templatesScott Main2013-01-291-1/+2
| | | | | | | | | | | | Change-Id: I6ad24252f10211a88d1f98e356bc9da97442f91c
* | | am 61101eee: am e27f64b0: am 1417357e: am f8a9c509: am 7b32d32b: Merge "Add ↵Dirk Dougherty2013-02-041-1/+31
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | build rule for ds (devsite) online docs." into jb-mr1-dev # Via Android Git Automerger (4) and others * commit '61101eee367be6f3bae5974b05c4c3ae912bddaa': Add build rule for ds (devsite) online docs.
| * | am 7b32d32b: Merge "Add build rule for ds (devsite) online docs." into ↵Dirk Dougherty2013-02-011-1/+31
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | jb-mr1-dev # Via Android (Google) Code Review (1) and Dirk Dougherty (1) * commit '7b32d32bd38b423dd141e7ead89205b9b7929497': Add build rule for ds (devsite) online docs.
| | * Add build rule for ds (devsite) online docs.Dirk Dougherty2013-01-281-1/+31
| | | | | | | | | | | | Change-Id: I4f1d099995402613f58401a506ba272abfb563ba
* | | Merge "Adding UI test automation APIs."Svetoslav Ganov2013-01-291-1/+2
|\ \ \
| * | | Adding UI test automation APIs.Svetoslav Ganov2013-01-221-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds APIs support for implementing UI tests. Such tests do not rely on internal application structure and can span across application boundaries. UI automation APIs are encapsulated in the UiAutomation object that is provided by an Instrumentation object. It is initialized by the system and can be used for both introspecting the screen and performing interactions simulating a user. UI test are normal instrumentation tests and are executed on the device. UiAutomation uses the accessibility APIs to introspect the screen and a special delegate object to perform privileged operations such as injecting input events. Since instrumentation tests are invoked by a shell command, the shell program launching the tests creates a delegate object and passes it as an argument to started instrumentation. This delegate allows the APK that runs the tests to access some privileged operations protected by a signature level permissions which are explicitly granted to the shell user. The UiAutomation object also supports running tests in the legacy way where the tests are run as a Java shell program. This enables existing UiAutomator tests to keep working while the new ones should be implemented using the new APIs. The UiAutomation object exposes lower level APIs which allow simulation of arbitrary user interactions and writing complete UI test cases. Clients, such as UiAutomator, are encouraged to implement higher- level APIs which minimize development effort and can be used as a helper library by the test developer. The benefit of this change is decoupling UiAutomator from the system since the former was calling hidden APIs which required that it is bundled in the system image. This prevented UiAutomator from being evolved separately from the system. Also UiAutomator was creating additional API surface in the system image. Another benefit of the new design is that now test cases have access to a context and can use public platform APIs in addition to the UiAutomator ones. Further, third-parties can develop their own higher level test APIs on top of the lower level ones exposes by UiAutomation. bug:8028258 Also this change adds the fully qualified resource name of the view's id in the emitted AccessibilityNodeInfo if a special flag is set while configuring the accessibility service. Also added is API for looking up node infos by this id. The id resource name is relatively more stable compared to the generaed id number which may change from one build to another. This API facilitate reuing the already defined ids for UI automation. bug:7678973 Change-Id: I589ad14790320dec8a33095953926c2a2dd0228b
* | | | Delete frameworks/base/voip use voip-common from frameworks/opt/net/voipWink Saville2013-01-281-4/+4
|/ / / | | | | | | | | | Change-Id: Ieaba759a0f69b45c4b8839cbed1fe757cdf190c5
* | | Removed Throttle Manager as obsoleteSasha Levitskiy2013-01-141-1/+0
| | | | | | | | | | | | Change-Id: I63e8514f34c880d0badaab33a347f54a80c84da6
* | | New "app ops" service.Dianne Hackborn2013-01-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Initial implementation, tracking use of the vibrator, GPS, and location reports. Also includes an update to battery stats to also keep track of vibrator usage (since I had to be in the vibrator code anyway to instrument it). The service itself is only half-done. Currently no API to retrieve the data (which once there will allow us to show you which apps are currently causing the GPS to run and who has recently accessed your location), it doesn't persist its data like it should, and no way to tell it to reject app requests for various operations. But hey, it's a start! Change-Id: I05b8d76cc4a4f7f37bc758c1701f51f9e0550e15
* | | Refactoring of the screen magnification feature.Svetoslav Ganov2012-12-141-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. This patch takes care of the case where a magnified window is covering an unmagnigied one. One example is a dialog that covers the IME window. bug:7634430 2. Ensuring that the UI automator tool can connect and correctly dump the screen. bug:7694696 3. Removed the partial implementation for multi display magnification. It adds unnecessary complexity since it cannot be implemented without support for input from multiple screens. We will revisit when necessary. 4. Moved the magnified border window as a surface in the window manager. 5. Moved the mediator APIs on the window manager and the policy methods on the WindowManagerPolicy. 6. Implemented batch event processing for the accessibility input filter. Change-Id: I4ebf68b94fb07201e124794f69611ece388ec116
* | | Move numeric api files from frameworks/base to prebuilts/sdkYing Wang2012-12-041-17/+17
| | | | | | | | | | | | | | | | | | | | | | | | So they can be used in unbundled builds. Bug: 7296240 Change-Id: Ib0ba88387cb45ff795a4e8e3a836cf670d5016b7
* | | Refactoring of the screen magnification feature.Svetoslav Ganov2012-12-031-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. The screen magnification feature was implemented entirely as a part of the accessibility manager. To achieve that the window manager had to implement a bunch of hooks for an external client to observe its internal state. This was problematic since it dilutes the window manager interface and allows code that is deeply coupled with the window manager to reside outside of it. Also the observer callbacks were IPCs which cannot be called with the window manager's lock held. To avoid that the window manager had to post messages requesting notification of interested parties which makes the code consuming the callbacks to run asynchronously of the window manager. This causes timing issues and adds unnecessary complexity. Now the magnification logic is split in two halves. The first half that is responsible to track the magnified portion of the screen and serve as a policy which windows can be magnified and it is a part of the window manager. This part exposes higher level APIs allowing interested parties with the right permissions to control the magnification of a given display. The APIs also allow a client to be registered for callbacks on interesting changes such as resize of the magnified region, etc. This part servers as a mediator between magnification controllers and the window manager. The second half is a controller that is responsible to drive the magnification state based on touch interactions. It also presents a highlight when magnified to suggest the magnified potion of the screen. The controller is responsible for auto zooming out in case the user context changes - rotation, new actitivity. The controller also auto pans if a dialog appears and it does not interesect the magnified frame. bug:7410464 2. By design screen magnification and touch exploration work separately and together. If magnification is enabled the user sees a larger version of the widgets and a sub section of the screen content. Accessibility services use the introspection APIs to "see" what is on the screen so they can speak it, navigate to the next item in response to a gesture, etc. Hence, the information returned to accessibility services has to reflect what a sighted user would see on the screen. Therefore, if the screen is magnified we need to adjust the bounds and position of the infos describing views in a magnified window such that the info bounds are equivalent to what the user sees. To improve performance we keep accessibility node info caches in the client process. However, when magnification state changes we have to clear these caches since the bounds of the cached infos no longer reflect the screen content which just got smaller or larger. This patch propagates not only the window scale as before but also the X/Y pan and the bounds of the magnified portion of the screen to the introspected app. This information is used to adjust the bounds of the node infos coming from this window such that the reported bounds are the same as the user sees not as the app thinks they are. Note that if magnification is enabled we zoom the content and pan it along the X and Y axis. Also recomputed is the isVisibleToUser property of the reported info since in a magnified state the user sees a subset of the window content and the views not in the magnified viewport should be reported as not visible to the user. bug:7344059 Change-Id: I6f7832c7a6a65c5368b390eb1f1518d0c7afd7d2
generated by cgit v1.1 at 2025-03-21 12:54:22 +0000