- 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
If user has static wallpaper on lock screen and live wallpaper
on home screen, when screen is locked, wallpaper will not be an
obscuring window. In this case, if there is a non-obscured app
window behind the lock screen which has FLAG_KEEP_SCREEN_ON set,
it will not allow to turn screen off automatically, although it
is not really visible behind lock screen.
This CL restricts holding screen windows to only ones that can be
seen. Same applies for screen and button brightness and user
activity timeout settings.
Bug: 30359386
Change-Id: I46de831211c943d8077282e3274b2df180739239
We were not calling setActiveAdmin before calling setDeviceOwner or
setProfileOwner in these tests. They were passing because the admins
were not being properly removed in the first place. The admin is
actually removed from the admin list inside onReceive of the receiver
passed in sendOrderedBroadcastForUser, which was not overridden to call
onReceive in DpmMockContext.
Bug: 30726135
Change-Id: I08cab5821228738196b229a8f885f7488aaafa34
We don't want to scale the actual size of the surface as we
were doing prior to ag/1101405 but we do need to adjust the top
and left corners so that the content will be at the same position
despite the inset area being scaled up.
Bug: 30399709
Change-Id: I30df4d3ef593d4f2869fdf378ee9bc3469619d5d
We now correctly:
- avoid backing up stale lock-wallpaper imagery when it is
present but unused,
- restore system+lock wallpaper state when that was the
source device's situation
Bug 30274136
Change-Id: Ib34f635f9d840c64f96cc7fdb67279ce5f6422fc
This change rolls back functionality added in ag/747748.
The idea was to restore accessibility focus on
configuration changes, but the restoration was happening
too early, which caused ViewRootImpl and the View to
disagree about accessibility focus. This confusion makes
some views unreachable by swiping after a configuration
change.
Bug: 30042251
Change-Id: Iae32b5425a1e7de9a8f5be965feb912fd2d9a0bb
When a package in updated, it may redefine a permisson group [specify a
new icon, text, etc...]. Udate our internal structures to the new package.
Bug: 30347537
Change-Id: I9fbaf7c68a4de658489cfd1c728473032dded98b
Controls whether to notify Connections of the fact that a handover of a VT
call from LTE to WIFI failed.
Bug: 30697460
Change-Id: I0cbff2dfb67c7c1f995f1ddf38e9525796501c09
Originally when I wrote backup & restore for ShortcutManager,
there was no manifest shortcuts, so there was no need to
handle preintalled apps specially.
However, now we have manifest shortcuts, which are published
when the user is unlocked, by the time restore happens preinstalled
apps may already have manifest shortcuts, which will be overwritten
by the restored shortcuts.
So we need to re-publish manifest shortcuts after restore.
Bug 30746028
Change-Id: I6afbae7790c9ed38483637f33c381ecb6f854677
