summaryrefslogtreecommitdiffstats
path: root/CleanSpec.mk
Commit message (Collapse)AuthorAgeFilesLines
...
* Change PacProcessor to Android ServiceJason Monk2013-08-201-0/+1
| | | | | | | | | | This switches the PacProcessor over to an Android Service. The service is bound and unbound by the PacManager, which also adds it to the ServiceManager, allowing for Context-Free access by the PacProxySelector in all DVMs. bug:10182711 Change-Id: Id1ff7660be56e8976cdcccd76e041feb47a17a61
* Add missing cleanspecBen Murdoch2013-08-121-0/+2
| | | | Change-Id: I92d6329e3c404249876e707048f6808f35fb019b
* Refinement of the print service APIs.Svetoslav Ganov2013-08-111-0/+1
| | | | | | | | | | | | | | | | 1. Factored out the printer discovery APIs of a print service in a dedicated session object that is created by the print service on demand. This ensures that added/removed/updated printers from one session do not interfere with another session. 2. Updated the app facing APIs to pass in a document info along with a printed file. Also exposed the print file adapter so apps that create a temporary file for printing can intercept when it is read by the system so the file can be deleted. 3. Updated the print service documentation. Change-Id: I3473d586c26d8bda1cf7e2bdacb441aa9df982ed
* Add missing cleanspec.Ben Murdoch2013-07-311-0/+1
| | | | Change-Id: Ida9f3c7335a84b126f67535ff658b056a59247a9
* Update cleanspecSelim Gurun2013-07-301-0/+1
| | | | | | Fix build break in master-chromium branch due to a forgotten cleanspec. Change-Id: If377c53bf3a82bff775f968ad8eb270e3c666837
* Use correct variables for the directories in CleanSpecJP Abgrall2013-07-251-2/+2
| | | | | | | | The comments in the file say what vars to use. "out" can change and should be replaced with $(OUT_DIR) Bug: 7183057 Change-Id: I3355d0e044f86709eee12873f47d7491b3f359b6
* add static dependency on liblogColin Cross2013-07-231-0/+1
| | | | Change-Id: I8056aa744b37ef0c31229329a0de79c58c5955ea
* Add a clean spec rule due to renamed *.aidlSvetoslav2013-07-161-0/+1
| | | | Change-Id: I87bfd02b8c4f3ceb43594a91ac8f501a867ccfe6
* Headphones volume warning disabled by defaultEric Laurent2013-07-031-0/+1
| | | | | | | | | Enable headphone volume limitation explicitely for countries where EN60950 is applicable. Bug: 8877359. Change-Id: Ida9e6678ee451350b826492f0085726003f0d39d
* Update cleanspec.Selim Gurun2013-06-241-0/+1
| | | | | | Update cleanspec to handle rename in I0df438e45ef540cc42c9ee5baafc816ebafa1c7b. Change-Id: Ifc5abe794017d1dbc4a49c645751b71e3b08c0ef
* Allow carrier provisioning to turn toggle radio power.Wink Saville2013-06-101-0/+1
| | | | | | | | Previously CarrierProvisioning toggle airplane mode, but now that's available only by the system. Bug: 9356811 Change-Id: I5167f8614c07bafb688983a360a008f76403b2b8
* New NotificationListenerService.Daniel Sandler2013-04-051-0/+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-0/+2
| | | | | | | | | | | | | | | | | | | 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
* 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
* Cleanstep for SmsRawData.Wink Saville2013-02-031-1/+1
| | | | Change-Id: Ic3ae3a501a733508808866494b3bca0fcc819f3e
* Delete frameworks/base/voip use voip-common from frameworks/opt/net/voipWink Saville2013-01-281-0/+5
| | | | Change-Id: Ieaba759a0f69b45c4b8839cbed1fe757cdf190c5
* Refactoring of the screen magnification feature.Svetoslav Ganov2012-12-141-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Refactoring of the screen magnification feature.Svetoslav Ganov2012-12-031-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* am 98a09c64: am 43174b7d: am 718fb9f1: Fix sample code issuesJason Sams2012-11-301-0/+1
|\ | | | | | | | | * commit '98a09c64d52aa1166a09ab071049bc3536def1cd': Fix sample code issues
| * Fix sample code issuesJason Sams2012-11-301-0/+1
| | | | | | | | | | | | | | Correct min SDK. Correct file extension on mandelbrot Change-Id: I508c22c382f1a930b27d8c5f4414cac3a990a332
* | resolved conflicts for merge of 9cd8c711 to masterMakoto Onuki2012-11-301-0/+2
|\ \ | |/ | | | | Change-Id: I5e2d13c44f6a0589648e5934c8c36790da85e828
| * Remove unused IExtendedNetworkServiceMakoto Onuki2012-11-291-0/+2
| | | | | | | | | | | | | | | | It was used in the cupcake era for docomo. Is not used anymore. Bug 7633569 Change-Id: I2ec826fc9a70d261a340957a937ed4c9f8e67c5c
* | Audio assets at 48000 HzGlenn Kasten2012-10-231-0/+1
|/ | | | | Bug: 7397767 Change-Id: If62c2219adf61f0c1b2115a83b7394d76829c028
* Port ImageProcessing to Filterscript.Stephen Hines2012-10-121-0/+1
| | | | | | | This enables testing of the Filterscript front-end for llvm-rs-cc. Bug: 7166741 Change-Id: I90bda9d2710c6652336a8c112b5654c5da3d14e4
* Update compatibility library testsJason Sams2012-10-101-0/+1
| | | | | | bug 7327728 Change-Id: If3f85fb8944d7217a4d5c035f522d1ecc7af3a07
* add cleanspec.Jason Sams2012-09-201-0/+1
| | | | Change-Id: I5aa58efa7c48809d1f05c8ad48332508597b9869
* Update cleanspecWink Saville2012-07-121-0/+1
| | | | | | mms and telephony have been moved remove the framework_intermediates. Change-Id: I49c2128ebaddfdae6cfa91913b739900d0f8d91b
* Remove Disco video from builds.Eino-Ville Talvala2012-06-131-0/+1
| | | | | Bug: 6294985 Change-Id: Idde6148b94a55a27740f3b4f82c2038272f06628
* Removing default accessibility gesture handling.Svetoslav Ganov2012-05-131-0/+3
| | | | | | | | | | | | | | | 1. The initial design was to have some accessibility gestures being handled by the system if the gesture handling access service does not consume the gesture. However, we are not sure what a good default is and once we add a default handler we cannot remove it since people may rely on it. Thus, we take the simples approach and let the accessibility service handle the gestures. If no gestures are handled the system will work in explore by touch as before. bug:5932640 Change-Id: I865a83549fa03b0141d27ce9713e9b7bb45a57b4
* Add missing clean steps.Dianne Hackborn2012-04-161-0/+3
| | | | Change-Id: Iecb3ff4d6658e581e51414bdfc397953189e66cb
* Moving libRSAlex Sakhartchouk2012-03-281-0/+7
| | | | Change-Id: I1e42204e862585b9c2f7818b615890c60f08faf6
* Rename CancellationSignal using preferred spelling.Jeff Brown2012-02-021-0/+2
| | | | | Bug: 5943637 Change-Id: I12a339f285f4db58e79acb5fd8ec2fc1acda5265
* Resolved conflicts for merge of 83cf0313 to masterJustin Ho2011-10-101-0/+1
|\ | | | | | | Change-Id: Ib66ee7e34d0c4d845004bce635ee1ef300d3b344
| * Ensuring previous sounds are named correctlyJustin Ho2011-10-101-0/+1
| | | | | | | | | | | | Bug: 5416299 Change-Id: I0f2cd229be02908553368d6ff19977a0ebd3e613
* | Make symlinks for DroidSans.ttf and DroidSans-Bold.ttfYing Wang2011-10-061-0/+1
| | | | | | | | | | | | | | | | | | | | Bug: 5420351 Make the following symlinks: /system/fonts/DroidSans.ttf -> Roboto-Regular.ttf /system/fonts/DroidSans-Bold.ttf -> Roboto-Bold.ttf Change-Id: If9a74ef4ac2386cdb46d125fed8ce5771e872310
* | Resolve conflicts for merge 121e805a to masterJustin Ho2011-10-031-0/+1
|\ \ | |/ | | | | | | | | | | Conflicts: CleanSpec.mk Change-Id: I750218dbd78e15c1ae3324b3bcfbcd28a4da2676
| * Adding additional variety to sound set 7Justin Ho2011-10-031-0/+1
| | | | | | | | Change-Id: I3f8c806258e47dc3b78ce81fd582722753573b54
* | Correction the use of SMALLER_FONT_FOOTPRINTYing Wang2011-09-291-0/+1
|/ | | | | | | SMALLER_FONT_FOOTPRINT is a BoardConfig variable that's only available in Android.mks but not product config makefiles. Change-Id: I1784b6e8c744ffcca1538e76d338f5800f150e72
* Updated key and effect soundsJustin Ho2011-09-261-0/+1
| | | | Change-Id: Ia7c771ed59bf1803ed7ff25d338a412906cf59c0
* Replaced Lohit_Hindi with Lohit-DevanagariRussell Brenner2011-09-231-0/+1
| | | | | | | | | Lohit-Devanagari is now provided by external/lohit-fonts, replacing Lohit_Hindi from here. Removed font from fonts.mk and renamed in fallback_fonts.xml. Bug: 5364436 Change-Id: I0b8f65dbfdbec1802fba526209d7f88d2cf64fc4
* Adding missing cleanspec for audio file cleanupJustin Ho2011-09-201-0/+1
| | | | Change-Id: I469601a2112994c466281a4959806a4179ffe245
* Unhide wifi p2p APIIrfan Sheriff2011-09-131-0/+1
| | | | | Bug: 5247957 Change-Id: Id93e30c0cb60f361ba13a840de8f843415777336
* Rename WpsConfiguration to WpsIrfan Sheriff2011-09-061-0/+1
| | | | | | | | For the purpose of exposing the class as a storage for Wps info with p2p, it is better to just call it Wps Bug: 5247957 Change-Id: Iaebef958dd8f08fdbeb4b9d7fa5ad5527400710d
* Improve NDEF push APINick Pelly2011-08-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce setNdefPushMessage() setNdefPushMessageCallback() setNdefPushCompleteCallback() Deprecate public API enableForegroundNdefPush() disableForegroundNdefPush() Hide & Deprecate staged (public but never released) API enableForegroundNdefPushCallback() The new API's do not require the application to explicitly call enable()/disable() in onPause()/onResume(), we use a Fragment behind the scenes to manager this automatically. NDEF Push can be disabled by using a null parameter, so each enable()/disable() pair is collapsed to a single set() call. Application code should now look something like: public void onCreate() { NfcAdapter adapter = NfcAdapter.getDefaultAdapter(this); if (adapter != null) { // check that NFC is available on this device adapter.setNdefPushMessage(myNdefMessage, this); } } And that's it - no need to explicitly hook into onPause() and onResume() events. Also - introduce a generic NfcEvent class that is provided as a parameter on all NFC callbacks. Right now it just provides the NfcAdapter, but using the wrapper classes allows us to add more fields later without changing the callback signature. (i'm thinking Bluetooth). Change-Id: I371dcb026b535b8199225c1262eca64ce644458a
* Updated phone soundsJustin Ho2011-08-241-0/+1
| | | | Change-Id: I88df6ad7ca8e96f163d968540420fd1cde410008
* Bug 5045498 New implementation of remote control APIJean-Michel Trivi2011-08-231-0/+1
| | | | | | | | | | | | | | | | | Remote control displays expose an IRemoteControlDisplay interface which they register through AudioManager. Remote control clients create a RemoteControlClient object, which implicitely exposes an IRemoteControlClient interface registered in AudioService through AudioManager. AudioService tells all clients and displays when a new client is the one that should be displayed. A client's data gets sent to the display when it is valid, or it sets new data (while being valid). The implementation for setting metadata and album art is temporary, and will migrate to the MetadataEditor API in future CLs. Change-Id: Ibab6ea1d94c68f32482c760c6ae269541f885548
* Bug 5045498 RemoteControlClient interfaceJean-Michel Trivi2011-08-171-0/+1
| | | | | | | Define a RemoteControlClient interface that applications must implement and register to be displayed on the lockscreen. Change-Id: I67276ae653f203e76727432231f1d76535c31942
* Fixed cleanspec.Daniel Sandler2011-08-121-0/+109
| | | | Change-Id: I3125487d2ffbe389f141537f5a974366e7ce5a91
* New RSSI cluster in status bar.Christian Robertson2011-08-121-107/+0
| | | | Bug: 5147463
generated by cgit v1.1 at 2025-01-08 17:32:08 +0000