Development shortcuts (1/2)

Change-Id: Id585483d2ec00f2b5bf929bf2b5e8948a5aae510
Revert "more black"

This reverts commit 6e37e212d626b56d828376bedda042c369de53ef.

Change-Id: I48a774bc8603869b766d182345a4d4bf7c959b13
Move back to Gradient

Change-Id: I8aa7a35fe39d52a90bb5df66608e6bf10074792b
Peek: configurable pickup timeout (1/2)

Change-Id: Ic6f1e2f22df6420b2649300372db8084006d987d
Calculate date as well to not overlap icons using stock or center clock options

MerkMod already calculate clock but if we do not calculate date, when a user set it, overlap will happens

Change-Id: I6da36acc4695a28e6ff953779a8cb37bb7d7f0af
EdgeGesture Service

(credits Kyrylo Mikos Sorry I dont know his email address)

Change-Id: I1527900261ac98c6d6916958c1926b97fe2528d9
Merge "Calculate date as well to not overlap icons using stock or center clock options" into android-4.4
Solve a possible NPE in the Documents provider

This commit follows an internal bug report to fix a NPE that would be
thrown in specific situations on specific devices. All callers should
be able to handle the returned null value but if they don't, we can
worry about that later down the line. This null value should not be
returned under normal circumstances anyway.

Change-Id: I274844bf07733643923d5729259f1d9d9cf75e54
Base: Fix crash of SystemUI

Change-Id: Ie18faac4dce45eb2fe9ca07d628bed7cd0eafaab
Fix layout of MultiWaveView and GlowPadView.

If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
  smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
  the right

Fix that by not using width in the calculation, as the inset size
already takes it into consideration.

JIRA:CYAN-829
Change-Id: Ifc2a93214f812f554a8fed3243eed66aec9f00c9
Add idmap

Change-Id: I749ba2d4c2f92a37e1e95a0d1da497af0be87209
ActivityManagerService: Penalise large apps going to background

Large applications (PSS more than a given threshold) when closed are
penalised with higher ADJ. Now, they will be more prone to be killed by
lowmemorykiller during memory pressure levels. This ensures better app
concurrency and improved subsequent latencies as it leaves some more room
for other smaller bg apps to be alive

Change-Id: I448fa12f55370949b22075595cd75b9c29e5d4b5
[ActivityManager] Prevent provider creating twice.

Root Cause:
If a process which contains provider is starting by not
from accessing provider, e.g. service/activity/receiver,
its providers' will be created during handleBindApplication.
And before the process complete publish provider to
ActivityManagerService, if there is an access to its provider,
these providers will be created again (there will have 2nd onCreate).

Solution:
Check if provider record is existed, do not schedule install provider,
becuase it is already creating and will be published later.

Change-Id: Ic200ceae042c014c86e7edee0acd013b513af334
Optimize drawBitmapMesh using TRIANGLE_STRIP

Draw BitmapMesh using STRIP instead of TRIANGLES.
Depending on where the bottleneck is located in the pipeline,
there is a potential for saving two-thirds of the time spent rendering.
The speedup is due to avoiding redundant operations,
i.e., mapping each vertex four times to texture and color attribute,
sending each vertex twice to the GPU, vertex processing of GPU ...

In this patch:
1. Refactoring mesh using Strip.
2. Batch triangles by adding extra vertexs at the start and end of rows.
3. Optimize computing positions of texture and color attribute.

Benchmark: Drawing Bitmap(1152x768 px) with 200x200 meshes
Performance: ~46% improvements (from 26.4 fps to 38.7 fps)
Memory: Reduce 80800 vertices with xy, uv, rgba data.

Change-Id: I08c5c20d981d88528ce7b02012feefae468d6ec4
Signed-off-by: kui.zheng <kui.zheng@arm.com>
base: add support for timelapse qualities for 4k sizes

Fix check in MediaRecorder to include all timelapse profiles

Change-Id: I32b00c5d05da0b1e440e9b0f50d0981e6afaf648
base: add roaming for Lycamobile USA

LycaMobile USA (MCC-311 MNC-96) can roam on T-Mobile USA (MCC-310 MNC-26)

http://jira.omnirom.org/browse/OMNI-1086

Change-Id: Ie9201cb7bb9efc4e455f1009a7c9a84336f3a8ad
Squashed search panel view commits and


SystemUI: NavbarEditor: Fix saveKeys logic

In landscape, the keys are saved backwards in the for-loop, but it would crash out due from
an IndexOutOfBounds error since it's subtracting i from the array length while i = 0.

Change-Id: I405c5d962d8c575cfee57b09a7e55a8a6efc2d24

SystemUI: Rework SearchPanelView calculations

Make isScreenLarge calculations match how the system calculates where to put the navigation
bar. This fixes certain cases where the quick launch buttons on the glowpad of the
navigation bar is improperly oriented.

Change-Id: I5703578b4d49a6eeab100bb23167abd5cf9a326d

SystemUI: Fix SearchPanelView miscalculation

The SystemUI declares the navbar to be movable to the side in landscape when the short
side's DP calculation equals to less than 600. This means that the nav bar will be at the
bottom/the screen is considered "large" if it's greater OR EQUAL to 600, not just greater.

Fixes OMNI-1129 and OMNI-1130.

Change-Id: I90322e40ebf0c4bb94146e28eb2d9b8f8a4444f8

SystemUI: SearchPanelView: Optimize calculations

Only calculate if the screen is large once on initialization rather than every
time updateSettings() is called.

Change-Id: Ib54b6ef0ad6a987e75d6d98b5b269fc6e8f5104c
MountService:  Support for alternative LVM storage list configuration

To facilitate allowing a different storage_list to be used when LVM partition alteration
is detected on a device, add a new storage_list_lvm.xml - This will be chosen when the
property ro.lvm_storage is set to 1 or true

The init scripts will set this property when an alternate storage configuration is
detected.  If the property is not set, the system will simply use the standard
storage list configuration

Change-Id: I4c3b636afad8b3343df83d97c7febaafd5d22f25
Merge branch 'android-4.4' of https://github.com/MerkMod/android_frameworks_base into armv6-4.4