Add content to Settings and SettingsLib to add a checkbox for PBAP
client profile, and remove the box for PBAP server profile when the
client profile is enabled.
Bug: 27642222
Change-Id: I125559904a8e017a01ae90b1f6425129a87cbee3
* 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.
This fixes an issue with the stack scrolling upon resizing. We only
need to update the initial state if docking, or upon rotation.
Change-Id: Ie59ed72cb22c9b000289db3f04b1a71ad5f64816
- Make sure to remove the background from the DecorView while
resizing, so we don't draw it twice.
Bug: 27869246
Change-Id: I7f830e5c825749fdf2b5bbda7af92239702b70ad
... if it cannot connect to remote PrintDocumentAdapter. Then the state
will be set to destroyed and the print activity will be aborted via the
onDied callback.
Bug: 27899066
Change-Id: Ieb287b92ac21fc71a56b491a1035feaff6cd2837
Also ditch the header BG so the panel can feel like one surface, as
a result need to set some clip bounds on the QSPanel to avoid some
collisions between the header and QS.
Bug: 27881430
Change-Id: Ia78c5b8a7a90bd02b97fa448efa06fc056f624ef
Refactored ZenModePanel:
1. Button creation is split from onFinishInflate.
2. Added a method to query current Zen condition
3. Made mZenButtonsCallback protected.
Change-Id: I959fa2f7770ba1888af01eababe7c4512981332d
(cherry picked from commit 79df200108c5240c0d2a041d7d841f8d9d143ec0)
Fix the way NotificationPanelView checks the X bounds of QS intercepts
since the translation is now on the density container, it should be
the source of truth for x and width.
Bug: 27865453
Change-Id: Id698a63563ed99a509a68386f289e6f28302e1e2
Introduced RTL support for the KeyboardShortcutKeysLayout and
with another minor change to the dialog layout achived full
RTL support for the keyboard shortcuts UI.
Bug: 22776761
Bug: 27674152
Change-Id: I14e38dc4533208f6fd982a53a1d0305e003d926b
Previously MtpDocumentsProvider used pipes to transfer bytes from an
application to the provider when writing a document. The problem was
application could not ensure that the last chunk of bytes was
successfully written to MTP device, since pipes had been already closed
when the provider transferred bytes to MTP device. Though the provider
encountered an error, the provider could not report the error to an
application.
The CL switches the method to transfer bytes from pipes to AppFuse. Now
application can flush() bytes on the file descriptor, and flush will not
complete until the provider completes writing bytes to MTP device.
Fixed: 23093747
Change-Id: I4e28f8cbf19d6c97e591943349a7535241d768f7
