Age | Commit message (Collapse) | Author |
|
This change uses new binder api changes to bring down mute status from
TeleService. mute state routed through AudioModeProvider.
bug:10395427
Change-Id: Ie15efcc780e99072363188de2a954a1888eec9dd
|
|
prox sensor bugs often come randomly and it's good to have logs in
place.
bug:10516724
Change-Id: I453f2a6904fec48f2a4e6acac13da111c60b2e2a
|
|
Change-Id: I0a0ae18bca3575d10e5b3d113b1e3d878e5c34e0
|
|
Many of these changes are verbatim code copies from what used to exist
in services/Telephony. The rest of them are straight logic copies that
should do the exact same things.
New class ProximitySensor manages the proximity behavior. It receives
device state from InCallPresenter, AudioModeProvider, CallButtonPresenter,
and AcceleromterListener, the last of which is a transplanted class from
services/Telephony.
ProximitySensor listens for the following events:
1. Change in the call state
2. Change in the audio mode
3. Change in the device orientation (from AccelerometerListener)
4. Change in the dialpad visibility
5. Change in hard keyboard open/close events.
6. Change in foreground position of InCall UI app.
It uses these to figure out when to enable/disable proximity sensor.
CL that removes code from TeleService: I77e0d15ad1a8f5a090c1368db98edaa246dbcd72
bug: 10366512
Change-Id: I5c2ea6daa9443e7ad77c67f272bc0bafdb060e5e
|