| cc2801296dd1829196fcaa7b4018e372121e36e5 |
|
30-Nov-2016 |
Christine Franks <christyfranks@google.com> |
TwilightService: Ignore (0,0) coordinate location updates
Location providers may erroneously return (0.0, 0.0) when they
fail to determine the device's location. These location updates
can be safely ignored since the chance of a user actually being
at these coordinates is quite low.
Bug: 31009261
Test: added TwilightServiceTest; both tests pass
Change-Id: Ie9d7d10f81ade9b0be10f98ed74978539efaa658
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| ec8837ae2670fbca115c566f8871e66bfa72917b |
|
23-Aug-2016 |
Justin Klaassen <justinklaassen@google.com> |
Improve logging for NightDisplayService/TwilightService
Bug: 31037341
Change-Id: Id6e5ea55f2fed93f1afdd0f61028e3329c8a43c3
(cherry picked from commit 7fba39209065eeee8fc8e8e98c44c5fcc1ca275d)
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 908b86c796443ba4ec55c669e8a0297fc80574a6 |
|
08-Aug-2016 |
Justin Klaassen <justinklaassen@google.com> |
TwilightService v2.0
- Switched to using CalendarAstronomer for more accurate sunrise/sunset
times.
- Exposed sunrise/sunset times via TwilightState so that clients can
track the current twilight period and perform their own
interpolations.
- Adopted LocationRequest API for fused location updates:
(low power, min 1h, max 10m).
- TwilightService is now only activated when a listener is registered,
minimizing impact to system health on platforms / configurations
where twilight state is not needed.
Bug: 28588307
Bug: 30190450
Bug: 30282370
Bug: 30650316
Change-Id: Ic5c94d8608e8bb3a3d895e623676a1468d4abdcd
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 6384878d69d3deb4a7c314f611ee62a634f21411 |
|
12-Jul-2016 |
Justin Klaassen <justinklaassen@google.com> |
Cleanup TwilightService
TwilightService now just reports the current twilight state, it's up to
clients to provide their own locking mechanism (e.g. always day or
night).
Bug: 29620105
Change-Id: I2a8bb544eab0f44d269c59f36a53fbdf842b423a
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 911e88939cbe5a8607c230e061ba1da5f187cf69 |
|
22-Jun-2016 |
Justin Klaassen <justinklaassen@google.com> |
Add Night display feature
Bug: 28615069
Tints the display at night automatically according to your schedule or
using the sunrise/sunset corresponding to your current location.
Change-Id: Ie56b4eed88cc2fcbae88002492b1edad5820b6b1
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 63c6f506b48fcd9b366c8c784c73d0eaebb5d732 |
|
24-Feb-2016 |
Jason Monk <jmonk@google.com> |
Fix bootloops in TwilightService
Bug: 27336023
Change-Id: I983f05bd69fd27bb3e3ae121d19fc9d006c95ffb
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 5dbd4aad809e6fec51df62280bcc1bfe05cc7df5 |
|
07-Feb-2016 |
Jason Monk <jmonk@google.com> |
SysUI Tuner: Night mode v3
TwilightService:
- Add support for locking on/off twilight globally
- Change twilight state to have float amount rather than
having clients calculate it using the sunrise/set values
- State controlled through secure setting
- Override mode which locks to a state for a couple hours then
resets
- Add broadcast for SysUI to listen to
Brightness/Power:
- Updates to handle TwilightService changes
- Added secure setting to control whether or not to use
twilight when calculating brightness.
Tuner:
- UI Overhall
- NightModeController will set the values of the custom color matrix
taking into account the current twilight service state and any
custom calibration set by the user.
- Probably other stuff.
Change-Id: I213f1f76a143e711c507b2ba7d784f581bfc32b4
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| b880d880c6cd989eacc28c365fc9a41d31900da1 |
|
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Make SystemService constructor take a Context.
This change simplifies the process of initializing a SystemService
by folding the onCreate() step back into the constructor. It removes
some ambuiguity about what work should happen in the constructor and
should make it possible for services to retain most of their final
fields after refactoring into the new pattern.
Change-Id: I25f41af0321bc01898658ab44b369f9c5d16800b
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|
| 9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories
Refactored the directory structure so that services can be optionally
excluded. This is step 1. Will be followed by another change that makes
it possible to remove services from the build.
Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/twilight/TwilightService.java
|