This is mainly for Wear devices that don't have speakers.
Bug: 37543478
Test: Manual:
1. Activate low power mode `adb shell dumpsys battery unplug && adb shell settings put global low_power 1`
2. Then see if Alarm/Timer will vibrate.
3. Send a Hangout Test notification, make sure it does NOT vibrate.
On phones there should be no change. Alarms will not vibrate.
Change-Id: Ia6dffa7e528886e7c84390dbb33b44f298c7afa4
A recent code change associated the SurfaceControl with the main
window owner id. However, it is possible for the an AppWindowToken to
not have a main window. This case is handled later in the method.
This CL restores the original behavior of using the calling uid in
the cases no main window is present.
Change-Id: I8255be9e0d68adc75fda0947c64f869b7eeb76c9
Fixes: 62096254
Test: go/wm-smoke
In ag/1460784 and ag/1551198, logic of
ActivityManagerService.updateConfigurationLocked
(now updateDisplayOverrideConfigurationLocked) was changed a bit:
before those CL's, with (changes == 0) we were still calling
mWindowManager.setNewConfiguration(mGlobalConfiguration)
(which is now mWindowManager.setNewDisplayOverrideConfiguration).
Now, when there was a call to Activity.setRequestedOrientation, the
window becomes frozen and waiting for configuration, which is never sent
since there are no changes detected (which we don't know in advance when
freezing the window). This is important for watches, since they have
"square" screens, and resources configuration for them doesn't change
after requesting landscape orientation, i.e. display rotates 90 degrees,
yet the layout stays portrait. As a result, device becomes frozen.
This CL only moves mWindowManager.setNewDisplayOverrideConfiguration
call outside of the (changes == 0) check to restore the old logic.
Bug: 37684680
Test: go/wm-smoke (on Pixel), manual (on Wear)
Change-Id: Idf1f5989173494d51437b9a66296b4cac82d15c2
No evidence so far that the screen-on latency bug hasn't been
fixed yet. Thus, we can remove the logspam.
Test: Inspect logs
Change-Id: I891077b3b8edaa68c748eeef8ecc6469c8eb4a90
Fixes: 62049093
- fuses url bar with activity header: url is now the subtitle
- url appears as text and not as editable content
- url only shows host name
- header style is the device default for Settings
- Material progress bar
- progress bar disappears at page load finished
- webview does not jump at page load finished
Bug: 62107381
Bug: 38197949
Test: tested by manually triggering the sign-in activity
Change-Id: Id75023acad04f444dbfc41de56814a09e70cc6f9
With my TimePickerDialog change to support keyboard based input I
accidentally broke TimePickerDialog#onClick as it was no longer being
called, instead it was calling TimeSetListener directly. This CL changes
the logic back to use onClick again.
Bug: 36042834
Test: Locally tested FitBit app.
Change-Id: I47d5563c99cc46eaaf2b1d4a96483d6825fc5805
Activity manager is notified asynchronously when new display is
created. Because of that someone may try to access or use it
before AM is aware of it, e.g. launch an activity to a just
create virtual display.
This CL guards the cases where we try to use a display by id in
AM and creates a new instance if needed.
Bug: 34262188
Test: android.server.cts.ActivityManagerDisplayTests
Test: #testImmediateLaunchOnNewDisplay
Test: go/wm-smoke
Change-Id: Iab0871708145aa80ff252a0c764beb6a3b5dc42d
On watches, multi-window is used to present essential system UI, and thus it
must be supported regardless of device memory characteristics.
Bug: 37482466
Test: Manually, on a watch
Change-Id: I7929a090b7fd46de019d237ce771c82a6d7fd3f3
This reverts commit 6db4d15d72.
Bug:62096254
Reason for revert: Breaking the build due to test references to class
Change-Id: I6021c802d04a3a55a19f54fc94389957c8152ed9
When collapsing directly from the expanded quicksettings
the shade would jump when there were no notifications.
Test: manual
Merged-In: I9a85cd57e2f96970ad4ea78a8c679145b58d563a
Change-Id: I9a85cd57e2f96970ad4ea78a8c679145b58d563a
Fixes: 35996906
In some cases, the path for a VolumeInfo may be null. The previous
implementation assumed it was always non-null, however. This backs out
of the calculation early if we cannot find the files.
Change-Id: Icfe265be738c5ccb16917ef339b2b872f2057f07
Fixes: 38308873
Test: No observed phone crashes with a flashed build.