Some of these assets may no longer be used. An other CL will remove these later.
Needed to remove warnings in new aapt version.
Change-Id: I84048d7fd237e6623b14810deeb7887dbe50ab73
Also add a new interface that items in AbsListView can implement to
adjust the bounds of the selection shown for them. This will allow
contacts to use list view's regular selection facility rather than
implementing something special in their item views.
Change-Id: I29cbdbc7122111ee97e47fe7d6ec55ff07be79cc
Lines were not drawing in Calendar because they were getting clipped
by the previous clip rectangle. This change simply updates the scissor
as needed. This change also reduces the number of state changes in GL.
Change-Id: I41ab13dca3a33cfa6d1a44371c48852ab418b04e
The file themes_extended is meant to be overridden per-device in an
overlay file. The overlay should include enhancements appropriate for
the device when hardware acceleration is requested by an app.
Change-Id: If2878b973845f1793a00651089bc0dd66952d916
In additional to adding the StringMode API for controling CloseGuard,
this checkin fixes several CloseGuard issues found booting a device.
Bug: 3041575
Change-Id: I4dffd184f49438d6d477ed81a1c2a2a5b56cc76b
IWindowManager now supports two new methods,
freezeRotation() and thawRotation(), that allow a caller to
temporarily stash the device's current rotation as the
default rotation (when no other constraints are present).
The system bar uses this to implement a user-accessible
rotation lock by calling freezeRotation() and then turning
off accelerometer-based display rotation; unless overridden
by an app, the display will continue to appear in the frozen
rotation until the rotation is unlocked by the user (either
via the rotation lock icon in the system bar or by checking
"rotate screen automatically" in Settings).
Bug: 2949639
Change-Id: Icd21c169d1053719590e72401f229424b254622f
If WebCore requests two (or more) alert/prompt/confirm dialogs
in quick succeession, we have a race that when the dialog is dismissed
the WebView does not have it's focus restored before the next dialog
is requested to be shown and we early out of displaying the dialog (i.e.
we do not show it).
Work around this by no longer verifying that the Activity has focus as
this check seems to be redundant anyway (see 3166409).
Bug: 3151825, 3166409
Change-Id: I7f650b066ee63da92bc9a620b8e190c91b306d3e
Part of the drawables for DpiTest is a nodpi directory, but the
LOCAL_AAPT_FLAGS didn't specify it.
Bug: 3165492
Change-Id: I989068d76f922db6048e6db7cc6822ab3234d36e
Bug:2460543
Bug:3094312
Bug:2692655
Bug:2710595
Use the NEXT flag when there is a following
textfield.
In TextView, treat the new variations like email and password
variations.
Requires a change in LatinIME so that these fields work propely:
https://android-git.corp.google.com/g/#change,77721
Change-Id: Id6517a016db7d50b77570ff77f2635027796da4a
The TYPE_TEXT_FLAG_MULTI_LINE was set directly, instead of calling
setSingleLine, which has some side effects, like correctly updating
the mSingleLine field.
Generalized the use of setSingleLine everywhere. This may change some
behavior, but is probably fixing more state inconsistencies.
Change-Id: I6b4da2e140a8dc75481cff9e44473daa6b3a83c4
* commit 'b20c2e7ca03f5ef2694b20ff9a7a10a7249eb936':
[3163098] Fix bug in angleChange funtion which caused the returned angle change to be zeroall the time. The fix is to use PrevR instead of computing the difference between R and R.