Generalize vectorization of Bitmap operation

 * All NEON-capable processors can support this.

Change-Id: I13d448e5864ea804f66cd1bbb93360cb8c0f0806

Conflicts:
	core/jni/Android.mk
webkit: Manage video playing state properly when browser goes to background

Issue: Browser App Video streaming not pausing while pressing home Button

Fix : When the Browser goes to the background while the video is playing
      in the fullscreen, the fullscreen mode is exited. While exiting
      the full screen mode the video state is handled properly. So that
      there is no playback in the background.

CRs-Fixed: 509225

Change-Id: I32c306923d2638731d34d216cf006050ce4ad825
Add 2 APIs (suspend and resume) in MediaPlayer

- API:suspend() will just pause the player and release all the decoders
- instead of release the whole player
- API:resume() will just init the decoders again
- Add a check in onVideoEvent()
- to make sure the first seek operation will seek the next i-frame

Change-Id: Ia4716f7fb3a412eb19c6ded9c0f3056d0490546c

Implement the suspend/resume operation in VideoView

- Using the new APIs in Mediaplayer
  to implement the suspend/resume operation in VideoView
- Add a new status "SUSPENDED"

Change-Id: I00f9daa2d34b3b125b8c3b968bc581708ab2cdf4

HTML5 VideoView change to use the new APIs: suspend/resume

- While suspend and resume, using the new APIs in Mediaplayer

Change-Id: I8530b533501607f681145853d7923fdf2009150b
Frameworks: Fix navring keyguard + ehancementes for SlimAction in preperation

to allow SlimPie on lockscreen and the complete rewrite of custom
hardware key rebinding.

- fix for not launching applications from keyguard (was broken on 4.3)
- allow app execute only direct from unsecure lockscreen or if the
user put in the credentials from secure (on 4.2 already the apps/actions always
opened in background)
- do not allow actions which does not make sense on locscreen to execute
  differenciate secure and non secure
- close notification drawer on any action so that the action really shows in forground
- code cleanup
- keyguard integration in SlimActions is now the base to open SlimPie
for lockscreen as well the rewrite of hw key rebinding. So two things
on the TODO list now

cheers

Change-Id: I870d19a06bc1935f4356a1cf45b76b1511a11694
Fix default QS quantitiy behaviour

- fixes the wrong calc of tile per row if the user is on a fresh
intall (happens when flip to landcape and back)
- ignore duplicate tiles per row feature on tablets and all devices
which do not have flipsettings

Change-Id: Ic6aa8e51f50b9abf978a72580ea8c648e43614d4
Frameworks: TRDS new 4.3 png's

Change-Id: I1aab6a5d0e1c5e5f015a48060ead36a656c50941
card emulation patch port to JB

Patch Set 2: Added missing @hide statements and rebased

Change-Id: I73fe9aa30830951ea5b9d44e9a9bf83cb720e567

Conflicts:
	core/java/android/nfc/Tag.java
	core/java/android/nfc/tech/TagTechnology.java
fixed inconsistant define values with android_nfc.h

Change-Id: Idccd2de60caf7b72839d158b39d14e2cfcdd5fc7

Conflicts:
	core/java/android/nfc/tech/TagTechnology.java
Remove redundant click action from date & time container layout

Unlike AOSP, we  provide separate actions for both the clock
and date & time views in the expanded notification area. AOSP has a
single action for both views.

This commit removes the redundant AOSP click action completely. In
addition, the clock and date views are modified to occupy the entire
height of the layout to increase the clickable area.

Change-Id: I78f4353c9ae4646f14124a38ef94e44ab920a067
Merge "Generalize vectorization of Bitmap operation" into jb4.3
Merge "webkit: Manage video playing state properly when browser goes to background" into jb4.3
Merge "Add 2 APIs (suspend and resume) in MediaPlayer" into jb4.3
Frameworks: reenable all keyboard features for 3rd party keyboards

use like quickpeek statusbarservice for it.
Gives us as well for other future features more
flexibility

Change-Id: I1e9e2497212d27eacbbb63f64961361aaed9aee7
Frameworks: do not depend on quick_settings_num_columns value

the overlay handling from google does not really make sense
and brought us already on 4.2 on weird behaviours sometimes.
Due that we have included tiles per row and duplicate feature
it makes sens to only depend on the values which are programmatically
set. As well I did not find one device or theme which manipulates
the mentioned values.

So let us do it all programmatically and the weird behaviours are
a problem of the past

cheers

Change-Id: I4ce7c5e9c30377983e61880315f60bfbd886a8a4
Merge "card emulation patch port to JB" into jb4.3
Merge "fixed inconsistant define values with android_nfc.h" into jb4.3
Add seinfo parsing to PackageManagerService.

This patch set allows the PMS to parse the
mac_permissions.xml file which contains the
seinfo values. Each package that is installed
on the device will be assigned an seinfo value
based on policy. This seinfo value will help label
the app process and data directory. Modifications
also include, adjustments to ApplicationInfo.java
to store the seinfo tag per package, adjustments
to installd to communicate the seinfo tag to
libselinux, and finally a set of unit tests.

Signed-off-by: rpcraig <rpcraig@tycho.ncsc.mil>

Change-Id: I61ad1ea12fb6a9a6d0b108ec163bc4bf4c954b58
Added SELinux enforcing status and booleans keys to secure system settings.

Conflicts:
	core/java/android/provider/Settings.java

Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8474e
Add APIs to allow Device Admins to change SELinux settings

These calls, added to the Device Admin API, will allow Device Admin apps
to change various SELinux settings, including:
* Toggling SELinux enforcing and permissive modes
* Toggle SELinux booleans
* Load a new SELinux policy file (sepolicy)
* Load new SELinux context files ({property,file,seapp}_contexts)

In order to use these APIs, a Device Admin must first request
USES_POLICY_ENFORCE_SELINUX, then become a SELinux Admin by calling
setSELinuxAdmin(). All other set* calls relevant to SELinux are guarded
by a check against whether the admin is a SELinux Admin.

Otherwise, the style of the set* calls are very similar to the other
calls setting device policy in the Device Admin API. That is, these
calls change the Admin's internal state and then call a sync method to
update the device's state to the Admin's state.

Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8476e
Remove SELinux additions from public API

Change-Id: If2e076312b0e411145c1cd900f3ae20d998a0f24