| 0ceb9e98ba7ba67346e0dab85384560a23740fd0 |
|
29-Sep-2015 |
Chris Banes <chrisbanes@google.com> |
Fix TwilightManager Location Permission handling
BUG: 24462356
Change-Id: Ia3ca1ffd46e5382b44af736f6d46fd10bb598e04
/frameworks/support/v7/appcompat/src/android/support/v7/app/TwilightManager.java
|
| f0ec407dc5fdb420550ed29f9556909bd9f635a9 |
|
22-Jun-2015 |
Chris Banes <chrisbanes@google.com> |
Stop spamming logcat with location permission denials
Currently we use isProviderEnabled() to check if we can
access a location provider, but this call also
requires the relevant location permission to be granted.
This CL adds an explicit permission check before we
call anything on LocationManager.
BUG: 21993901
Change-Id: I4de69df092e2d0704ccd704ea6c87824e57a7d82
/frameworks/support/v7/appcompat/src/android/support/v7/app/TwilightManager.java
|
| 15ad53853d367f5d593bb019d88fb613878fd8fc |
|
14-May-2015 |
Chris Banes <chrisbanes@google.com> |
Theme.AppCompat.DayNight working back to API v14
This CL enables the use of -night and -notnight resource
qualifiers, and thus allowing Theme.AppCompat.DayNight
to work on those API levels.
TwilightCalculator and TwilightManager are simplified versions
of those internally in the framework. Since we don't want to
force the use of location permissions, we have a fallback of
hardcoded 'night' time.
BUG: 21119724
Change-Id: I48ff5f0ea0c02ba60d3c2979aa9fa2997080de37
/frameworks/support/v7/appcompat/src/android/support/v7/app/TwilightManager.java
|