| 875d45aabb11b92b12959d2d952d5324208cad59 |
|
26-Nov-2015 |
Michael Wright <michaelwr@google.com> |
Show error message when pairing fails in SUW.
Also, prevent multiple dialogs from coming up, dismiss the dialog
when the device goes back into tablet mode and prevent a SysUI crash
when we attempt to stop a scan after the bluetooth adapter turns off.
Bug: 25662777
Change-Id: Ib99eaecb0b60388e1f1efb89199ac4ffdb281536
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|
| c0d7058b14c24cd07912f5629c26b39b7b4673d5 |
|
29-Jan-2016 |
Winson <winsonc@google.com> |
Referencing static interpolators.
Change-Id: I5d2292016e869ed533f5873e373a1eccce651fc5
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|
| 365bf06a72aca38e1b6a57cf4d29686d0a0f01f6 |
|
06-Nov-2015 |
Dmitry Torokhov <dtor@google.com> |
SystemUI: implement bluetooth scan timeout
When we dock with Pixel C keyboard we normally expect to find it, and so
we perform a low latency scan (which uses highest duty cycle). But if
keyboard is not charged or if tablet mode trigger misfires (because
there was a magnetic object in proximity?) we may not find the keyboard
and will continue scanning indefinitely, impacting WiFi performance and
draining battery. To avoid this scenario let's stop scan if we do not
find "our" device in 30 seconds.
Also remove STATE_WAITING_FOR_STATE_PAIRED as it was unused.
Change-Id: I4bf1a9a163d3165eaa5e8f1cc2d2938465d454af
(cherry picked from commit 6c12c3a6538591b5fa6e11cb4f583aa494e0ce5c)
Signed-off-by: David Riley <davidriley@google.com>
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|
| 8ce2a538d9b94a0d8e1543c4ee4620a8af525276 |
|
26-Nov-2015 |
Yohei Yukawa <yukawa@google.com> |
Use Context.getSystemService(Class<T>) for InputManager.
This is a mechanical replacement of Context.getSystemService(String)
with Context.getSystemService(Class<T>) when retrieving InputManager.
Note those are bundled code. Hence we don't need to make sure
Build.VERSION.SDK_INT >= 23.
Change-Id: Iee47e374e1349720e3100bab33ed139e1f47c169
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|
| 79f00cf06f5e70047d73b48d20910b967353b075 |
|
22-Oct-2015 |
Dmitry Torokhov <dtor@google.com> |
SystemUI: fix automatic pairing of BT keyboards
After reset (docking) Pixel C Keyboard that was previously paired with
a device goes into so-called non-discoverable mode, where it will
establish connection only with device that it has connected before. When
scanning for available devices we need to wait till the keyboard starts
advertising itself as discoverable, and only then try to pair.
Also, let's flush the device cache when we attach the base to make sure
the device that we seen before and cached again in the right state after
reset.
Bug: 24915541
Change-Id: I136c1c4235080a25529b4b1c2b1da9bc18508811
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|
| 9209c9cd9a6f779d0d9d86f9b2e368df564fa6bb |
|
03-Sep-2015 |
Michael Wright <michaelwr@google.com> |
Add SystemUI component to watch for keyboard attachment.
Add a new SystemUI component to watch for keyboard attachment /
detachment. If the config specifies the name of a keyboard that is
packaged with the device, then SystemUI will ask the user if they
would like to enable BT (if disabled) and then attempt to pair to the
device.
Bug: 22876536
Change-Id: I786db35524d49706d5e61d8b8bc71194d50113f3
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/KeyboardUI.java
|