| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Bug: 183609798
Test: manual
Change-Id: Id2f3262142817a6eccad902913d69bcf2c3f6c60
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a system with a new key attempts to connect to adb adbd passes the
key to the system_server which then launches an activity to prompt the
user to allow the key; adbd then waits for a response from the
system_server. For adb over usb if the user disconnects the usb cable
before responding to the prompt the system_server will not send a
response to adbd requiring a restart of adbd before a new connection
can be established. This commit notifies the adb service when the usb
cable is disconnected or when the activity is stopped through some other
means (back, home, or recent apps buttons); the system_server then sends
a response to adbd to deny the connection which allows subsequent
connections to succeed.
Fixes: 156323450
Test: Disconnected usb cable, used back, home, and recent buttons to
stop app and verified subsequent connections displayed a prompt
and adb sessions were successful when allowed.
Change-Id: I50d5ce3a4a1fbdc2caa843b85e2905260a37a7e9
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit e34087b1b3a84d49cc42af9bff276f7ad97e4ae5.
Reason for revert: Restoring UsbDisconnectedReceiver to allow dialog
in the background to be closed and redisplayed in the foreground by
reseating the usb cable.
Bug: 156323450
Test: Removed usb cable, verified dialog was closed
Change-Id: I84a636ba3c9f7e35beb0769ae80aa6c6df0c2f2c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
adbd expects a reply from system_server for authorization: normally
there's a reply of "OK" or "NO", but when the prompt is dismissed
because of USB disconnect, no response is sent, and we can't prompt for
user authorization until system_server or adbd is restarted.
Dismissing the authorization prompt on USB disconnect is also wrong: the
request might not be coming in over USB.
Bug: http://b/145814587
Test: unplugged a device with authorization dialog open
Change-Id: I5a9925b917a7169213256daa557637b770583058
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL migrates most of the remaining classes to use
BroadcastDispatcher. Some classes left are Views or created before the
BroadcastDispatcher can be injected.
Adds docs for instructions on using the BroadcastDispatcher.
Using the broadcast dispatcher, the time system_server spends
dispatching common intents to SystemUI like SCREEN_OFF and SCREEN_ON can
be seen to decrease from ~70-150ms (in a Q build) to ~2-4ms.
Additionally, once a broadcast is received by the dispatcher, time
until it is fully dispatched inside SystemUI is not impacted greatly.
Most broadcasts are fully dispatched after ~20ms with a few of them
taking ~100ms.
Test: atest SystemUITests no regressions
Test: build and boot
Test: tried some random broadcasts and they are properly dispatched
Test: BroadcastDispatch dump
Test: adb shell dumpsys activity broadcasts
Bug: 134566046
Change-Id: I26a592be66b053f25669b5481b58bf7f07bfd0da
|
| |
|
| |
Change-Id: I5d2292016e869ed533f5873e373a1eccce651fc5
|
| |
|
|
|
| |
BUG:19913735
Change-Id: Iefdf8a12f1622650bb0d61e7ffb73040e4b8d498
|
|
|
Bug: 12785423
Change-Id: If7f60899cfdaca7bdad560bd59a78f5be74c24be
|
