This reverts commit 25c80c8cca.
Reason for revert: This frequency range is still unstable, needs to be validated before it can be used.
Bug: 223739586
Change-Id: Id3853b1041d441f80b19965f5875040f2aabb8ab
Make pattern vibrate on a higher frequency range to increase the overall
vibration intensity and make the notification vibration more noisy when
the phone is on a solid surface, to address user feedback.
Bug: 210535717
Test: manual
Change-Id: Ic7d97d35e271b23e34dde8afb92dfcee29e7563a
This CL updates resource overlay of
rounded_corner_content_padding
for raven/oriole so that the same device-specific value can be seen
from both the Framework code and the SysUI.
With my previous CL [1], the SysUI continues to see the same value
even after this migration.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: presubmit
Change-Id: Id95b8c063ece7eb43d91f96afe21b4fb01e8b489
Add the PWLE vibration pattern to the config.xml overlays for Pixel 2021
devices that support frequency control.
The patterns use the amplitude and frequency hand-designed for both
raven and oriole devices. The amplitude is using the maximum supported
value of 0.4, to allow scaling based on user settings.
Bug: 212366218
Test: manual
Change-Id: I73a2f3e50901b80aef299f4c8e9807a551170bbc
Merged-In: I73a2f3e50901b80aef299f4c8e9807a551170bbc
Add the PWLE vibration pattern to the config.xml overlays for Pixel 2021
devices that support frequency control.
The patterns use the amplitude and frequency hand-designed for both
raven and oriole devices. The amplitude is using the maximum supported
value of 0.4, to allow scaling based on user settings.
Bug: 212366218
Test: manual
Change-Id: I73a2f3e50901b80aef299f4c8e9807a551170bbc
Bug: 211649038
Test: Manual. Modify the enable_ons_auto_provisioning flag to true in config.xml, build, flash and adb log should not have ERR_AUTO_PROVISIONING_DISABLED
Change-Id: Ia684e5b55fd69cbb15cfbcc0f511d01baa955c5a
With the new added APIs, we don't need to overlay status_bar_height that
contains cutout size and quick_qs_offset_height anymore.
Bug: 186604541
Test: make
Change-Id: Ib2ebacbc3250a1c2a2ad2b26f92eda6651fec37a
Moving forward, binned brightness will not
use prox. Let's get rid of this unnecessary config.
Test: manual
Bug: 194151347
Change-Id: I3352a3007138232c32aeb43ce4ec3ce97dad239d
Update the e-label of GF5KQ and add the e-labels for GLU0G and G8V0U.
Fixes: 187846268
Test: visual
Change-Id: I76bf53297abf4d00051beda670d847477444f7b6
There's still 2px offset when transitioning from
KeyguardStatusBarView to PhoneStatusBarView.
To make the visual perfect, we can adjust more 0.5dp.
Test: Visual
Test: atest SystemUITests
Bug: 195670442
Change-Id: I84d10f2dad665fcbdb01665f5056d08b3c20e0d7
The statement
```
include $(PHONE_CAR_BOARD_CONFIG)
```
is difficult to translate to the Starlark configuration file. Fortunately,
all the potential values of this variable have have similar structure, so
```
PHONE_CAR_BOARD_CONFIG := device/google_car/foo/BoardConfig.mk
....
include $(PHONE_CARD_BOARD_CONFIG)
```
can be changed to
```
PHONE_CAR_BOARD_PRODUCT := foo
....
include device/google_car/$(PHONE_CAR_BOARD_PRODUCT)/BoardConfig.mk
```
Bug: 190051051
Test: treehugger
Change-Id: I3b6e8e1aabfb373ab84c756c109b04893d2e8481
Adjust the system_icons_keyguard_padding_end for O6/R4
Consider below scenario:
1. Enable/Disable multi-user: This case must have x-asix shift due to
home StatusBar did not designed to show avator icon
2. Keyguard/Home StatusBar alignment
3. w/ & w/o privacy dot
4. w/ & w/o plug-in USB cable
5. w/ & w/o show battery percentage
Test: build and check the visual
Bug: 195670442
Change-Id: I783c026e46d7cc01839a4e56fed9fdb89ca6b194
This should not scale with density size increases b/c the
sensor size is fixed.
Test: manual
Change-Id: I84cd73992b657ee292873fd7ba4bf6e73fc6b349
Fixes: 195564809
