summaryrefslogtreecommitdiffstats
path: root/packages
Commit message (Collapse)AuthorAgeFilesLines
* Rename UserId to UserHandle.Dianne Hackborn2012-08-166-14/+14
| | | | | | This is the start of turning this into a formal public API. Change-Id: I5786d2c320f1de41a06ed5d0f65adb68967287a0
* resolved conflicts for merge of 80c904df to jb-mr1-devSvetoslav Ganov2012-08-161-9/+63
|\ | | | | | | Change-Id: Ic2f8d64cd716d04a533ca0685d1fb0d5e2a21933
| * am 8631701b: Allow enabled accessibility service to toggle tocuh exploration ↵Svetoslav Ganov2012-08-161-5/+61
| |\ | | | | | | | | | | | | | | | | | | after an upgrade to JellyBean. * commit '8631701bb770f3a4e3b2a139dc282f2244fe86e6': Allow enabled accessibility service to toggle tocuh exploration after an upgrade to JellyBean.
| | * Allow enabled accessibility service to toggle tocuh exploration after an ↵Svetoslav Ganov2012-08-151-5/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | upgrade to JellyBean. 1. Before JellyBean touch exploration was a global setting controlled by the user via the UI. However, if the enabled accessibility services do not handle touch exploration mode, enabling it makes no sense. Therefore, in JellyBean the services request touch exploration mode and the user is presented with a dialog to allow that and if she does we store that in the database. As a result of the above change a user that has enabled accessibility, touch exploration, and some accessibility services running a pre-JellyBean system version may lose touch exploration state, thus rendering the device useless unless sighted help is provided, since the enabled service(s) are not in the list of services to which the user granted a permission to put the device in touch explore mode. The fix is during a database upgrade to allow allow all enabled accessibility services to toggle touch exploration provided accessibility and touch exploration are enabled and no services can toggle touch exploration. Note that the user has already manually enabled the services and touch exploration which means the she has given consent to have these services work in touch exploration mode bug:6996354 Change-Id: I0af2dc578cc4fbcc90043341035163b876978ab2
| | * show 3G icon for CDMA/1xRTTMadan Ankapura2012-08-141-11/+19
| | | | | | | | | | | | | | | | | | | | | when config_showMin3G is enabled to true in a CDMA device Change-Id: I79a4fa200dc406fc7f9f4527165046541961ef69 Signed-off-by: Madan Ankapura <mankapur@sta.samsung.com>
* | | Fix status bar disabling.Daniel Sandler2012-08-163-4/+13
| | | | | | | | | | | | | | | Bug: 6998403 Change-Id: I8a47e694f2f3914ef5cf0d180b0309783148c627
* | | Merge "Multiuser support for notifications, take 1." into jb-mr1-devDaniel Sandler2012-08-155-9/+99
|\ \ \
| * | | Multiuser support for notifications, take 1.Daniel Sandler2012-08-155-9/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Notifications for background users are hidden from the panel and status bar. Still need to add a concept of "any user" notifications (for things coming from the system) and notification visibility controls (for access to icons + possibly masked text of a background user's notifications). Change-Id: Iba121f35a6c25c2e1c44db029d776a5a59a6a008
* | | | Confine the quick settings trigger to the right third of the status bar.Daniel Sandler2012-08-156-11/+71
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | Pulling down anywhere on the status bar when a panel is already showing will switch to the other panel. Also adjust gesture recorder output to track the settings panel and annotate it separately. Change-Id: I0ca3b395b5f2c6c8767237126bce26d0e8c9b8c0
* | | Fix situations where the panel wouldn't descend.Daniel Sandler2012-08-152-12/+54
| | | | | | | | | | | | Change-Id: I41c1d6a973b2693487062f3a5fbf922ff2025897
* | | Merge "Turn off chatty logging for everyone." into jb-mr1-devDaniel Sandler2012-08-152-2/+2
|\ \ \
| * | | Turn off chatty logging for everyone.Daniel Sandler2012-08-152-2/+2
| | | | | | | | | | | | | | | | Change-Id: I6c6f48012df8a551ae4f2b2a9cd2713184234763
* | | | Merge "Power manager rewrite." into jb-mr1-devJeff Brown2012-08-152-8/+13
|\ \ \ \ | |/ / / |/| | |
| * | | Power manager rewrite.Jeff Brown2012-08-152-8/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The major goal of this rewrite is to make it easier to implement power management policies correctly. According, the new implementation primarily uses state-based rather than event-based triggers for applying changes to the current power state. For example, when an application requests that the proximity sensor be used to manage the screen state (by way of a wake lock), the power manager makes note of the fact that the set of wake locks changed. Then it executes a common update function that recalculates the entire state, first looking at wake locks, then considering user activity, and eventually determining whether the screen should be turned on or off. At this point it may make a request to a component called the DisplayPowerController to asynchronously update the display's powe state. Likewise, DisplayPowerController makes note of the updated power request and schedules its own update function to figure out what needs to be changed. The big benefit of this approach is that it's easy to mutate multiple properties of the power state simultaneously then apply their joint effects together all at once. Transitions between states are detected and resolved by the update in a consistent manner. The new power manager service has is implemented as a set of loosely coupled components. For the most part, information only flows one way through these components (by issuing a request to that component) although some components support sending a message back to indicate when the work has been completed. For example, the DisplayPowerController posts a callback runnable asynchronously to tell the PowerManagerService when the display is ready. An important feature of this approach is that each component neatly encapsulates its state and maintains its own invariants. Moreover, we do not need to worry about deadlocks or awkward mutual exclusion semantics because most of the requests are asynchronous. The benefits of this design are especially apparent in the implementation of the screen on / off and brightness control animations which are able to take advantage of framework features like properties, ObjectAnimator and Choreographer. The screen on / off animation is now the responsibility of the power manager (instead of surface flinger). This change makes it much easier to ensure that the animation is properly coordinated with other power state changes and eliminates the cause of race conditions in the older implementation. The because of the userActivity() function has been changed so that it never wakes the device from sleep. This change removes ambiguity around forcing or disabling user activity for various purposes. To wake the device, use wakeUp(). To put it to sleep, use goToSleep(). Simple. The power manager service interface and API has been significantly simplified and consolidated. Also fixed some inconsistencies related to how the minimum and maximum screen brightness setting was presented in brightness control widgets and enforced behind the scenes. At present the following features are implemented: - Wake locks. - User activity. - Wake up / go to sleep. - Power state broadcasts. - Battery stats and event log notifications. - Dreams. - Proximity screen off. - Animated screen on / off transitions. - Auto-dimming. - Auto-brightness control for the screen backlight with different timeouts for ramping up versus ramping down. - Auto-on when plugged or unplugged. - Stay on when plugged. - Device administration maximum user activity timeout. - Application controlled brightness via window manager. The following features are not yet implemented: - Reduced user activity timeout for the key guard. - Reduced user activity timeout for the phone application. - Coordinating screen on barriers with the window manager. - Preventing auto-rotation during power state changes. - Auto-brightness adjustment setting (feature was disabled in previous version of the power manager service pending an improved UI design so leaving it out for now). - Interpolated brightness control (a proposed new scheme for more compactly specifying auto-brightness levels in config.xml). - Button / keyboard backlight control. - Change window manager to associated WorkSource with KEEP_SCREEN_ON_FLAG wake lock instead of talking directly to the battery stats service. - Optionally support animating screen brightness when turning on/off instead of playing electron beam animation (config_animateScreenLights). Change-Id: I1d7a52e98f0449f76d70bf421f6a7f245957d1d7
* | | | Quick settings come to all Android devices.Daniel Sandler2012-08-1510-23/+108
|/ / / | | | | | | | | | | | | | | | I mean, real soon now. Change-Id: I9a15b49f271e7ae06eb48a402f58270d8adccbf4
* | | Merge "Launch ASSIST intent on the current user" into jb-mr1-devAmith Yamasani2012-08-141-4/+8
|\ \ \
| * | | Launch ASSIST intent on the current userAmith Yamasani2012-08-141-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lockscreen and statusbar now launch the intent on the current user. Make sure that the intent resolution is made to the package manager for the specific user, as the app could have been disabled for that user or may have an alternative app installed. Change-Id: I93b0f972d6c7e8880b146da83dc3d08a68fe7e51
* | | | Merge "Use a color resource to specify the dim behind panels." into jb-mr1-devDaniel Sandler2012-08-143-3/+13
|\ \ \ \
| * | | | Use a color resource to specify the dim behind panels.Daniel Sandler2012-08-143-3/+13
| | | | | | | | | | | | | | | | | | | | Change-Id: I551d9969dc1f4032f26fd94cf9719f07873abb5e
* | | | | Fix bug with swipe-to-dismiss.Daniel Sandler2012-08-142-15/+12
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | (Clearing all notifications prevents notifications from being subsequently swiped away.) Change-Id: Ia15704c390d95f16675e2eea6040379099f44430
* | | | Merge "New status bar capable of multiple sliding panels." into jb-mr1-devDaniel Sandler2012-08-1411-646/+633
|\ \ \ \
| * | | | New status bar capable of multiple sliding panels.Daniel Sandler2012-08-1311-646/+633
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | There are some visual glitches but almost everything should be put back pretty much where it was. Change-Id: I2f9b0591d44599b07bd83f03c4e09e6dd98e1448
* | | | Import translations. DO NOT MERGEBaligh Uddin2012-08-133-0/+69
|/ / / | | | | | | | | | | | | Change-Id: I95bed23285699c68b623ae0e36600ec5e813db8c Auto-generated-cl: translation import
* | | User Manager service to manage users and query user detailsAmith Yamasani2012-08-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moved a bunch of methods from PackageManager to UserManager. Fix launching of activities from recents to correct user. Guest creation APIs Change-Id: I0733405e6eb2829675665e225c759d6baa2b708f
* | | Merge "Fix a couple of bugs from the location overhaul." into jb-mr1-devNick Pelly2012-08-102-4/+4
|\ \ \
| * | | Fix a couple of bugs from the location overhaul.Nick Pelly2012-08-102-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Marshall LocationRequest array correctly. Observe reportLocation from FusionEngine. Actually deliver the setRequest message to fusion engine. Change-Id: Iff64596fdd42f9fb06e563591dda9fbe0241533a
* | | | Merge "Import translations. DO NOT MERGE" into jb-mr1-devBaligh Uddin2012-08-1030-0/+690
|\ \ \ \ | |/ / / |/| | |
| * | | Import translations. DO NOT MERGEBaligh Uddin2012-08-1030-0/+690
| | | | | | | | | | | | | | | | | | | | Change-Id: I8948cd5b0992133db9dc8e676b5d43b54d672e85 Auto-generated-cl: translation import
* | | | Location overhaul, major commit.Nick Pelly2012-08-108-0/+790
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Themes: Fused Location, Geofencing, LocationRequest. API changes o Fused location is always returned when asking for location by Criteria. o Fused location is never returned as a LocationProvider object, nor returned as a provider String. This wouldn't make sense because the current API design assumes that LocationProvider's have fixed properties (accuracy, power etc). o The fused location engine will tune itself based on the criteria passed by applications. o Deprecate LocationProvider. Apps should use fused location (via Criteria class), instead of enumerating through LocationProvider objects. It is also over-engineered: designed for a world with a plethora of location providers that never materialized. o The Criteria class is also over-engineered, with many methods that aren't currently used, but for now we won't deprecate them since they may have value in the future. It is now used to tune the fused location engine. o Deprecate getBestProvider() and getProvider(). o Add getLastKnownLocation(Criteria), so we can return last known fused locations. o Apps with only ACCESS_COARSE_LOCATION _can_ now use the GPS, but the location they receive will be fudged to a 1km radius. They can also use NETWORK and fused locatoins, which are fudged in the same way if necessary. o Totally deprecate Criteria, in favor of LocationRequest. Criteria was designed to map QOS to a location provider. What we really need is to map QOS to _locations_. The death knell was the conflicting ACCURACY_ constants on Criteria, with values 1, 2, 3, 1, 2. Yes not a typo. o Totally deprecate LocationProvider. o Deprecate test/mock provider support. They require a named provider, which is a concept we are moving away from. We do not yet have a replacement, but I think its ok to deprecate since you also need to have 'allow mock locations' checked in developer settings. They will continue to work. o Deprecate event codes associated with provider status. The fused provider is _always_ available. o Introduce Geofence data object to provide an easier path fowards for polygons etc. Implementation changes o Fused implementation: incoming (GPS and NLP) location fixes are given a weight, that exponentially decays with respect to age and accuracy. The half-life of age is ~60 seconds, and the half-life of accuracy is ~20 meters. The fixes are weighted and combined to output a fused location. o Move Fused Location impl into frameworks/base/packages/FusedLocation o Refactor Fused Location behind the IProvider AIDL interface. This allow us to distribute newer versions of Fused Location in a new APK, at run-time. o Introduce ServiceWatcher.java, to refactor code used for run-time upgrades of Fused Location, and the NLP. o Fused Location is by default run in the system server (but can be moved to any process or pacakge, even at run-time). o Plumb the Criteria requirements through to the Fused Location provider via ILocation.sendExtraCommand(). I re-used this interface to avoid modifying the ILocation interface, which would have broken run-time upgradability of the NLP. o Switch the geofence manager to using fused location. o Clean up 'adb shell dumpsys location' output. o Introduce config_locationProviderPackageNames and config_overlay_locationProviderPackageNames to configure the default and overlay package names for Geocoder, NLP and FLP. o Lots of misc cleanup. o Improve location fudging. Apply random vector then quantize. o Hide internal POJO's from clients of com.android.location.provider.jar (NLP and FLP). Introduce wrappers ProviderRequestUnbundled and ProviderPropertiesUnbundled. o Introduce ProviderProperties to collapse all the provider accuracy/ bearing/altitude/power plumbing (that is deprecated anyway). o DELETE lots of code: DummyLocationProvider, o Rename the (internal) LocationProvider to LocationProviderBase. o Plumb pid, uid and packageName throughout LocationManagerService#Receiver to support future features. TODO: The FLP and Geofencer have a lot of room to be more intelligent TODO: Documentation TODO: test test test Change-Id: Iacefd2f176ed40ce1e23b090a164792aa8819c55
* | | | Capture orientation change data in the gesture log.Daniel Sandler2012-08-101-0/+3
|/ / / | | | | | | | | | Change-Id: I19719f82f1b6b6563b33edc85b4a8a259d04ba0c
* | | Merge "More termination conditions for Dreams." into jb-mr1-devDaniel Sandler2012-08-101-0/+17
|\ \ \
| * | | More termination conditions for Dreams.Daniel Sandler2012-08-101-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Default implementation of Dreams will finish() on KEYCODE_BACK. PhoneStatusBar will awaken() from any Dream when the Home key is pressed. Change-Id: I55e2a5d533a7fb93debc4c54514dba3b9098f009
* | | | Import translations. DO NOT MERGEBaligh Uddin2012-08-0915-0/+345
|/ / / | | | | | | | | | | | | Change-Id: I813d5cfc5f5b60e98f635dc62e9935299c903171 Auto-generated-cl: translation import
* | | Load default Dream settings into a clean db.John Spurlock2012-08-091-0/+7
| | | | | | | | | | | | | | | | | | | | | Set the Dream defaults during onCreate, not only onUpgrade. Bug: 6959513 Change-Id: Ia93097edaf1150813c75b6be809db9c97987868f
* | | Start the correct settings from the status bar.Amith Yamasani2012-08-084-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added a new method to Context: startActivityAsUser() requiring the INTERACT_ACROSS_USERS_FULL permission. Show the correct Recents list, based on current user. Added a getRecentTasksForUser() in ActivityManager. Hidden and requires the INTERACT_ACROSS_USERS_FULL permission. Change-Id: If5b56465efdd3ead36601a3b51ed4af157bbf35c
* | | Merge "Migrate Dreams default settings to DatabaseHelper." into jb-mr1-devDaniel Sandler2012-08-082-1/+33
|\ \ \
| * | | Migrate Dreams default settings to DatabaseHelper.Daniel Sandler2012-08-082-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | Also switch Dreams on for all charging devices by default. Change-Id: Iccbcc2906d55214320b2f467e88ba9cb188f4886
* | | | Merge "Add an empty stub status bar service implementation" into jb-mr1-devJason Simmons2012-08-072-0/+164
|\ \ \ \
| * | | | Add an empty stub status bar service implementationChristopher Tate2012-08-062-0/+164
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For kiosk-type devices that do not present any navigation UI. This allows for clean selection of the implementation based on resource overlays, without the need for the tablet or phone status bar implementations to accomodate the desired behaviors. Bug 5824373 Change-Id: Idcec70eef437904edda452b69e5eb7a3cc7094f7 (cherry picked from commit 5717f80927944c141f059162ecd69649488f8049 in ics-aah) Signed-off-by: Mike J. Chen <mjchen@google.com>
* | | | | Merge "Explicitly export content providers" into jb-mr1-devNick Kralevich2012-08-071-0/+1
|\ \ \ \ \ | |_|/ / / |/| | | |
| * | | | Explicitly export content providersNick Kralevich2012-08-061-0/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In a future version of Android, the default value for <provider android:exported> will change from true to false. Explicitly set android:exported="true" Bug: 3306452 Change-Id: Iffe4dca4fefc92bb9f89698f149a87c16a7ce3c5
* | | | Move lots of layout-port/ resources to layout/ .Daniel Sandler2012-08-069-84/+20
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | The framework is no longer letting us skate by without a default (unqualified) for of each resource; in particular, the land/port aspect of the configuration appears to be binding much later than it used to. Bug: 6937365 Change-Id: I6bf72c76e707548168fefa9466dc196ffde33ab3
* | | am 1971df5d: am e20a19cb: Merge "show 3G icon for CDMA/1xRTT"Wink Saville2012-08-041-11/+19
|\ \ \ | |/ / | | | | | | | | | * commit '1971df5d4296f077cccff704201057a32b733235': show 3G icon for CDMA/1xRTT
| * | am e20a19cb: Merge "show 3G icon for CDMA/1xRTT"Wink Saville2012-08-041-11/+19
| |\ \ | | | | | | | | | | | | | | | | * commit 'e20a19cb541f8621f04be0f3d3501f2fc51a0e82': show 3G icon for CDMA/1xRTT
| | * | show 3G icon for CDMA/1xRTTMadan Ankapura2012-08-021-11/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | when config_showMin3G is enabled to true in a CDMA device Change-Id: I79a4fa200dc406fc7f9f4527165046541961ef69 Signed-off-by: Madan Ankapura <mankapur@sta.samsung.com>
| | * | Create telephony-common and mms-common - DO NOT MERGEWink Saville2012-07-178-47/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These have been created to reduce the size and complexity of frameworks/base. mms-common was created by moving all of frameworks/base/core/java/com/google/android/mms to: frameworks/opt/mms telephony-common was created by moving some of frameworks/base/telephony to: frameworks/opt/telephony Change-Id: If6cb3c6ff952767fc10210f923dc0e4b343cd4ad
* | | | Merge "Don't allow the status bar to collapse things we're touching." into ↵Chris Wren2012-08-035-15/+57
|\ \ \ \ | | | | | | | | | | | | | | | jb-mr1-dev
| * | | | Don't allow the status bar to collapse things we're touching.Chris Wren2012-08-025-15/+57
| | | | | | | | | | | | | | | | | | | | | | | | | Bug: 6538918 Change-Id: Ie4e79aa593ac2097d0e6402f84816df934160687
* | | | | am e1c47324: am 9a59f6e0: Merge "Notification panel on tablet does not ↵Svetoslav Ganov2012-08-021-1/+22
|\ \ \ \ \ | |/ / / / |/| / / / | |/ / / | | | | | | | | | | | | handle back and home key events." into jb-dev * commit 'e1c47324fc22f86f378cb6ccc51e4554eec5156b': Notification panel on tablet does not handle back and home key events.
| * | | am 9a59f6e0: Merge "Notification panel on tablet does not handle back and ↵Svetoslav Ganov2012-08-021-1/+22
| |\ \ \ | | | |/ | | |/| | | | | | | | | | | | | | | | | home key events." into jb-dev * commit '9a59f6e02fdcabbf2debd5b836b01f7b22a4b21a': Notification panel on tablet does not handle back and home key events.
generated by cgit v1.1 at 2024-09-24 02:14:04 +0000