am: f0f919f
* commit 'f0f919f19a6b442648048837c2ff3517f89853da':
Improve handling of AlertDialog padding between title and content
Change-Id: Ia506c800dbdbdd3214f80a9f75fb78bfbc4c4847
am: ac4dfec1
* commit 'ac4dfec1c6d684b7d0d8ce09a5cba8fa9003e3a4':
BatteryStats: Add ble scans to checkin data and start global ble scan timer
Change-Id: I70c38df715190c58809732d03835286ab18a2e27
am: 740a5f0
* commit '740a5f023eea7b2fdb3e31efe8b8d5ac18aa8302':
Add the print service recommendation service
Change-Id: Ie58ade9356f591781496581259b6d8a876780ac9
am: ac94586
* commit 'ac945867145c571506a211ccb0a87a3402c4d745':
Refactor usages of Picture In Picture and Multi Window (1/4)
Change-Id: I34a274c3eca15546d7be85fbb30ac072ff03db7f
- While explicitly bound, the package for a single pre-installed
VrListenerService will be granted permission to access
notification policy, be bound as a notification listener service,
and draw system overlays.
Bug: 22855417
Change-Id: I568d5d9c032e0926e47c8ef4b46e3910b6bdf766
Very slight improvements all-around. There is now greater separation
between the list's top edge and the title and less separation between
the list's bottom edge and the buttons.
Bug: 27535708
Change-Id: Ia0d0dfa5ea6d34597104885dd2c773144dcf446e
This service connects through the print manager to the print spooler:
PrintSpooler.AddPrintersActivity <-> PrintManager <-> PrintManagerService <-> UserState <-> RemotePrintServiceRecommendationService <-> PrintRecommendationService <-> PrintRecommendationServiceImpl
Hence there is a lot of mindless plumming.
The actual changes are only in the AddPrintersActivity which is extended
to show another list of services: The recommended services.
The PrintServiceRecommendationService is based on the experimenal print
service stubs provider. This provider was contributed the Android by
Mopria. As this services uses Android own network discovery service most
code from the experimental provider goes away. In fact the only logic
left over is the selections of mdns-txt fields to look at and the
printer vendor configuration.
This relies on the Android MDNS to get fixed (Bug: 27696905). This also
does not deal with how to update the recommendation service.
Bug: 24533249
Change-Id: I6edc6e25fc08a50d478b61c71bb8ea158b08624c
am: 620a84c
* commit '620a84c76aa3b0180fa214328cd200645de9008d':
LUTInterpolator needs to have 2 frame at minimal
Change-Id: I21005de68c66524ce471e423baaaccd6adb21e62
It turns out that BaseInputConnection has still depended on a private
API named BaseInputConnection#reportFinish(), which was introduced
4 years ago to work around a UI freeze due to an unbalanced batch edit
count [1]. Note that such an unbalanced batch edit count cannot always
be avoidable. It can easily occur in the following situations.
- The current IME crashed during batch edit.
- The user changed the View focus during batch edit.
- The current IME called IMM#switchToNextInputMethod() during batch
edit.
The remaining problem is that #reportFinish() is still an internal API
and only subclasses of BaseInputConnection can implement it, and IMM
calls it when and only when the current InputConnection is
BaseInputConnection or its subclass. InputConnectionWrapper and any
other InputConnection implementations will never receive such a callback
to clean up InputConnection#{begin, end}BatchEdit(), which is considered
to be a major contributor to UI freeze.
To address the above issue, we unhide BaseInputConnection#reportFinish()
as InputConnection#closeConnection() so that application developers can
receive an appropriate callback to clean up internal state including
unfinished batch edit.
[1] I5525d776916f0c42d5e6d4a4282aed590d7f0e9a
9d69ecbf61
Bug: 24688781
Bug: 25332806
Change-Id: I234309c5880c9fe0b299b8bd0f8862796d4dda0d
am: fe1886f
* commit 'fe1886f8b82330315a62e10d6dd27b0aa7c045cb':
Should not update initial state at all on resize.
Adding logging to track down bitmap issues.
Moving the background to the window.
Adding clear-all button.
Change-Id: I18865c7e916863138a3e8ab36b5e594ed92bc666
* changes:
Should not update initial state at all on resize.
Adding logging to track down bitmap issues.
Moving the background to the window.
Adding clear-all button.
- Make sure to remove the background from the DecorView while
resizing, so we don't draw it twice.
Bug: 27869246
Change-Id: I7f830e5c825749fdf2b5bbda7af92239702b70ad
For StandardMenuPopup, if user opens a submenu, the ondismiss listener is no
longer called. Instead, it is called when the submenu (which is now open in
the top level menu's place) is dismissed.
Bug: 27877103
Change-Id: I069388fd173142620c667fa8d1cb21e88d5266fe
am: f25ea2f
* commit 'f25ea2fece6dfe3c63cd063e5342e0102ee6d1f3':
Use default implementation for onForwardingStopped() in action menu
Change-Id: I884e15fce160a4cdefbad3418bfe6213f1977a1e
am: 09d83b0
* commit '09d83b032e5f456750f2f3149aa4932836643957':
Clean up a couple of bugs about transport init staging
Change-Id: I0c32b31bf82b1d3ed798263816ca789c3a7305d8
- Cache shouldAlwaysConsumeNavbar so it doesn't get reset when
insets == null
- Remove logic with frame comparison when determining whether to
consume nav bar. Not sure how that ever worked.
- Make sure shouldAlwaysConsumeNavBar survives when consuming
insets.
Bug: 27157904
Change-Id: I35f209ab27cc12240038da7efa9e79c95f70c6ce
