Makes it possible to use the new quick settings api from:
I82b6bebb0b21a5c9eb926cb1a761cac340a293df
Change-Id: I053bb2b28284c4f49d67339b617ef72ede1f2843
When activity was launched from recents and started at the same time, we
would first try resuming activities and then focus on the started
activity. That is wrong odering, as the previously focused activity will
be resumed (in this case recents). We need to first focus on the start
activity and then request resuming.
The CL also flag protects some logging that is being very frequently
printed from activity manager.
Bug: 25823213
Change-Id: I5311fb2bf316ce3d298b30fa90fb257978bacdca
Basically anything Parcelable needs to go since it might be
quite large. Note that this includes additional extras such as
those contributed by WearableExtender.
Bug: 26038546
Change-Id: I85a20173158717c866a36dacd6a04391c2a33376
1. Entering DhcpBoundState cancels the renew alarm, but at that
point the renew alarm is guaranteed not to have been scheduled.
This is harmless, but results in an "unknown listener" message
in the AlarmManager logs.
2. We don't cancel the renew alarm when exiting DhcpBoundState.
This is also harmless, because that alarm does nothing except
in DhcpBoundState, and we cancel it whenever we enter
DhcpBoundState. But canceling it on exit is more correct.
Change-Id: I60dfcf00f243253b81b8906540e0a6218a7a489c
This is a mechanical refactoring to apply Java 7 diamond operators in
InputMethodSubtypeSwitchingController.java.
Bug: 22859862
Change-Id: If80df0bcf0b1485c43d55ff51cab69c8ae211eb2
This is a mechanical refactoring that removes an unnecessary parameter
that is always specified to 'true'.
No behavior change is intended.
Bug: 22859862
Change-Id: If3aef8209a355af1432ca2600bcc3a0027a6c24c
The logic was in TextView, but it's only for Editor.
Move it to Editor and have constants for the state.
Bug: 19544351
Change-Id: I391f66753aa5cbb26fbefcba5b4e7e3d917454e2
- Detect triple click in TextView#onTouchEvent.
- Select paragraph on triple click.
- Extend drag accelerator to support paragraph based
selection.
Bug: 19544351
Change-Id: I0a6752a0642a2c569b69a1fc2c0f49169a72844a
Now, the handles will be shown at the proper positions in
Editor#startSelectionActionMode. No need to call
HandleView#showAtLocation.
Change-Id: I5a7fb7bc4419a49234584bd06db5acc3d23168b8
- Remove mouse selection related logic from
ArrowKeyMovementMethod and Touch.
- Extend drag accelerator to support character based
selection by dragging and use it for mouse drag selection.
- Enable word based drag accelerator even if the clicked
position is not on a word.
- Disable y-coordinate adjustment for word based drag
accelerator when the user is using a mouse.
Bug: 19544351
Change-Id: I1b29a65be3d321ac472f8c5b70ab6fee4e895964
Previously on 24: when a BUGREPORT_FINISHED was received,
BugreportProgressService would remove the watched BugreportInfo from its
map and if there was no info left, it would stop self and send the
SEND_MULTIPLE_ACTION intent.
Soon we're going to allow the user to enter more details (like a title
and description) for the bugreport, but if the service is stopped while
the user is still entering data, that window will be killed.
Hence, although this refactoring doesn't change the current logic, it
paves the way for such new feature.
BUG: 25794470
Change-Id: Ic5283ddc3e07d88ba2a9a925f9534426857e7606
Turns out there are known use cases for it, in particular to avoid
interfering with doze/idle type optimizations. In addition, it is
not reliably possible to aim for a specific *wall-clock* trigger time
when posting work to a Handler, since the time base used there is
uptime rather than elapsed.
Bug 26114467
Change-Id: I7cede733fc7e09704b63dfe3e98b00365bbdff35
* changes:
Fixed a bug where the heads up had the wrong size
Adapted the appear animation for notification children
Added darkmode for notification groups
And suddenly notification children appeared
It was assumed that when a UID had either rx or tx bytes/packets that it would
have the other as well.
Bug:25706750
Change-Id: Iefac59a6bd02876aed9a0bac218d187b81807a95
Commit 187a6aeb112ecbf85387a21ea75cf6beb3f9fc76 replaced atoll() with
fscanf("%ld"). Though unlikely, there could theoretically be 32-bit
devices with >2GB zram where the type difference matters.
Bug: 25951511
Change-Id: I902e27a214038fea1396185ef9a521316b0009f9
Signed-off-by: Greg Hackmann <ghackmann@google.com>
We don't allows apps white-listed to write to system
settings to change settings that aren't a part of the
public APIs. Now that we made VIBRATE_WHEN_RINGING it
should be moved from the list of private settings to
the public list which apps can modify.
bug:25941020
Change-Id: Ice91f782aeca4785fa0aed300b22d9ecdbb51bd3
