In the case of moves, we can use the existing ABIs from settings because
a move will not result in an ABI change. For new installs, we can just
use the ABI we deduced for compiling (dex2oat) the package.
bug: 21144503
Change-Id: I35e2e8abd47f547b6252271fc6b41d30719c4298
* commit '906a91b4e794015bb2609ded232bb50d4478c3c7':
Add video for families page. Add Studio version reqts and beta notice for data binding lib. Add new gps video.
* commit '08710f1b69e2188a439b54f1ae59a574f71681d0':
Add video for families page. Add Studio version reqts and beta notice for data binding lib. Add new gps video.
- Migrate the existing calendar attribute in the event condition
from a long calendar id to the calendar account name. More
portable across a backup/restore.
- Also skip restoring transient state (like the current condition
state) from restored automatic rules.
Bug: 17755700
Change-Id: I9bdb421d2209e3ce90873008665c254d67c788d2
Fix is quick and the misspelling was embarassing (spelled channel as
"chanel" three times) so I'm just going to +2 this myself.
Change-Id: Icc4dcd5f47ba2337db29cc81b6afe426e6986e95
This CL checks for the return value for Rect.intersect() for whether
there is actually an intersection before taking the return intersected
rect. In the case of no intersection (Rect.intersect() returns false),
an empty rect will be used as the intersection.
bug: 7368679
Change-Id: Ib874345210c8f62550627544d717e958d46cfe13
Adds a few attributes that were missing from either theme, ensures all
the attributes match up so that it's easier to scan through for errors.
Bug: 21490615
Change-Id: Iabfed8f61a7bc121e618164dee4121c41e82db09
TextLine used to use getTextRunAdvances on a substring to compute a
cursor position, but this had a number of problems, especially when
the substring is a wider than the full string (as can happen in
certain Tamil ligatures).
This patch changes the implementation to use getRunAdvance, which was
explicitly designed for this use case.
We should also change Layout.getHorizontal to use the dual
getOffsetForAdvance, but that's basically a performance optimization,
the functionality should be basically equivalent.
Bug: 21125816
Change-Id: I669b85eaecfbf6f7aa6c6a9dddbf1a210eb94571
In the following scenario, the system continues keeping the previous
IME's inset in the display until the new IME shows its window.
1. an IME shows its software keyboard with reporting non-empty inset.
2. the user switches to another IME, which does not show the software
keyboard when it is selected (e.g., because the physical keyboard
is connected.)
This CL tries to address above situation by introducing a new state
flag IMMS#mShouldClearInsetOfPreviousIme to clear the previous IME's
inset when necessary.
Bug: 15922840
Change-Id: Ib04967f39b2529251e4835c42e9f99dba2cf43f2
