frameworks-base

Fork

Android 4.3.1 Release 1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAlJS/+AACgkQ6K0/gZqxDnghQQCcC8+IyovjieVlJcozysRFSXwf
DpoAn1pFT480phcau2lMwi3YuvSlm+hW
=zGvh
-----END PGP SIGNATURE-----

Merge tag 'android-4.3.1_r1' into jb-x86

Android 4.3.1 Release 1

Merge branch 'android-ia3' into jb-x86

MediaFile: support more media types

CaptivePortalTracker.java: add Intent.FLAG_RECEIVER_REGISTERED_ONLY_BEFORE_BOOT

Add the Intent.FLAG_RECEIVER_REGISTERED_ONLY_BEFORE_BOOT for
ConnectivityManager.ACTION_CAPTIVE_PORTAL_TEST_COMPLETED) action, so
that we will not have the "FATAL EXCEPTION IN SYSTEM PROCESS:
CaptivePortalTracker" error which will cause many services died

Change-Id: I028c51384ee5bb93db6a0b904a4dfe974bf20fa5
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>

Volume: Enable "Volume mute" key on HSW

Fix:
Android doesn't use master stream by default (config_useMasterVolume=false),
it cause AudioManager doesn't handle VOLUME_MUTE event. Modify AudioManager
to deal with this event, which make "Volume mute" key work.

There are 3 kind of behavior for "Volume mute" key, "Mute master stream",
"Mute activity stream" and "Mute all affected streams". Selecting the
first one as its behavior. The reasons are:

1. Mute activity stream, other streams still work. Once the activity stream
swith out, it is not easy to unmute it for user, and this behavior is different with
other desktop system usage habit, like windows.
2. For "Mute all affected streams", If the streams have different original status, some are
muted, the others are not muted, How can we define the behavior once "Volume mute" key
pressing down, mute the unmuted streams or unmute the muted streams?

Issue: AXIA-2773
Change-Id: I87179ab1ef58ca9973b6f4421039ec492fb417a7
Signed-off-by: Xiaobing Feng <xiaobing.feng@windriver.com>

Set PS2 Keyboard controller as not a ketboard type

The Eventhub detects the platforms built-in PS/2 keyboard controller
as a physical keyboard. So the system will not display the software
keyboard by default. Modify it device type in Keyboard-less tablets,
so that ActivityManager will not ignore the PS/2 controller.

Issue: AXIA-1875

Change-Id: Ia5b7592e82aaf1970066bab5e9ca5f46ac83ab1c
Signed-off-by: juntingwang <Junting.Wang@windriver.com>

Make "windows" key to act as "home" key

Issue: AXIA-1893
Change-Id: I7b2b19f7e34ec8a1867e8e6ce522e65133e5267f
Signed-off-by: juntingwang <Junting.Wang@windriver.com>

GLSurfaceView: Be less picky about EGLConfig alpha sizes

EGLChooseConfig returns a "best match" set of visuals meeting or
exceeding the required r/g/b/a component depths. But GLSurfaceView
oddly requires that the returned visual be an exact match. Add to
that that the (rarely used outside of CTS) default request specifies
zero alpha bits and that not all drivers expose a zero-alpha
EGLConfig, and the default configuration will fail needlessly.

It's not incorrect to have alpha bits you didn't request: the only way
to produce divergent behavior is for a fragment shader to write out
explicit alpha values (into the channel it didn't want to begin with!)
with values other than 1.0 and then rely on them being ignored and
treated as 1.0.

For: AXIA-1448
Change-Id: I2f64995d7b9de1ae082aa47822af525390102083
Signed-off-by: Andy Ross <andy.ross@windriver.com>

framework: add neon white list mechanism for applications installed with ABI2

BZ: 76964

add neon white list mechanism for applications installed with ABI2.

Change-Id: I1f900ae63252f1443086ceb06a0e07a89ca42965
Signed-off-by: llin4 <ling.lin@intel.com>
Reviewed-on: http://android.intel.com:8080/84166
Reviewed-by: Wang, Zhenghua <zhenghua.wang@intel.com>
Tested-by: Li, XiaojingX <xiaojingx.li@intel.com>
Reviewed-by: cactus <cactus@intel.com>
Tested-by: cactus <cactus@intel.com>

Add power off button to quick settings dropdown box

Add an option to power off the device in the quick settings
drop-down dialog. It is necessary for devices which the power
button does not function as Android expected. For example,
the hardware only sends button down event but no button up
event, or there is not long press event emitted what-so-ever.
Clicking on this button asks user for confirmation, and fires
the shutdown intent.

Issue: AXIA-1271
Change-Id: I12c3af70d39d45a2974f8fca03eb332e68017e15
Original-Change-Id: Iba14b10d12e788f9df6038e20aa98384838531e0
Original-Change-Id: Ic973ebf43b79b436a9e872613b8572a7c77ce0c3
Signed-off-by: Daniel Leung <daniel.leung@intel.com>
Signed-off-by: Anton Cherkashyn <antonx.t.cherkashyn@intel.com>

framework: houdini hook and native activity hook rebase on MR1

BZ: 71657

houdini hook and native activity hook rebase on MR1

Change-Id: Iffa9793530cb30f7dd0cc8d083235f7713f65905
Signed-off-by: llin4 <ling.lin@intel.com>
Reviewed-on: http://android.intel.com:8080/77611
Reviewed-by: Yao, Yong <yong.yao@intel.com>
Reviewed-by: Li, XiaojingX <xiaojingx.li@intel.com>
Tested-by: Li, XiaojingX <xiaojingx.li@intel.com>
Reviewed-by: cactus <cactus@intel.com>
Tested-by: cactus <cactus@intel.com>

ImageWallpaper: don't throw-up when EGL init fails

Just fall back to non-GL path instead.

Change-Id: Icabee5b7cadd49942e9c920a7ff49a54fc8bea9f
For: AXIA-991
Signed-off-by: Matt Gumbel <matthew.k.gumbel@linux.intel.com>

Prevent EventHub from adding input device twice

When Android first starts up, it scans /dev/input for input devices.
In some rare instances, the EventHub gets another notification that
some device nodes are created. It then proceeds to add the same
input device again. This causes the system to get two events per
touch or key stroke.

This adds a check to prevent adding the same device if the operation
is triggerd by inotify.

Issue: AXIA-858
Change-Id: I68b02594f1c7f14067611735db0b3763378ec7ea
Signed-off-by: Daniel Leung <daniel.leung@intel.com>

Clear any stale errors before allocating layer

Symptom: On first boot, the "Make yourself at home" dialog
was not drawn, but was actually present. This prevented
swiping the home screen until you happened to click on the
invisible "OK" button or take some other action that caused
the screen to get redrawn.

Cause: GL errors remain within GL until they are cleared by
retrieving them. The createLayer function was affected by a
stale error leftover from some previous code sequence. When
it retrieved GL error status to check for success/fail of an
operation it got one of these "stale" errors and erroneously
concluded that the operation had failed.

This change clears any stale errors before embarking the
operation sequence that it wants to check for success/fail.

Issue: AXIA-425
Change-Id: I30b7fe1fbc354d3fea5e1d8cefa1be363fc68f8c
Signed-off-by: Paul Drews <paul.drews@intel.com>

Fixes Camera Panorama mode save panorama issue

Sometimes, Panorama mode of the Camera app was not able to save
the picture taken.
Issue was caused by a memory leak. Captured panorama is converted to
compressed JPEG. After compress, memory used in the process was not
freed. Compressor must free memory explicitly.

Change-Id: I892fe99826f40cbddad44a00ba74616f17066b49
Original-Change-Id: I1b2d00bf54866b9ff55843cdeed93cd92d4f89d6
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>

libandroid_runtime: determine whether to use OpenGL renderer at runtime

BatteryService: improve battery status support for x86

Only set charge level if data is read correctly.
In some cases the battery path may just disappear a while.
Do not set 0 in such cases to avoid shutdown suddenly.

Update the battery status every 30 seconds.

Add more messages for debugging.

BatteryService: fix logic errors

(!String8_instance) doesn't mean an empty string. The object is
implicitly casted to const char *. Therefore it just means
(!String8_instance.string()) which is always false.

camera: fix NullPointerException

EventHub: load a default .idc if no other .idc found for touchscreen

The patch moves loadConfigurationLocked to later stage that may cause issues
if upstream changes. Needs to review it on rebasing.

Added option to disable touchscreen pressure sensitivity from idc files

Support old single-touch touchscreens with BTN_LEFT

skip non Android VT events

The patch is modified for ICS from

http://git.alwaysinnovating.com/cgit.cgi/ai.android/tree/preprocess/froyo/patches/noinput.patch

disables hardware acceleration if debug.egl.hw=0

wifi: get interface name from wlan.interface

Do not always call setIsConnectedToProvisioningNetwork(false)

Previously I was calling setIsConnectedToProvisioningNetwork(false) always,
but all MDST's receive every broadcast. Thus we could over write an MDST's
mNetworkInfo.mIsConnectedToProvisioningNetwork to false, unless the MDST
that was set to true was last, i.e the code was order dependent.

If the provisioning networks value was false instead of true
when handleMobileProvisioningAction was called we wouldn't invoke
mdst.enableMobileProvisioning because network info would be null.

Thus the provisioning network would never transition to CONNECTED and
a default route wouldn't get setup and the browser couldn't access the
website.

Now setIsConnectedToProvisioningNetwork is only set to false when the
apnType matches and we won't indiscriminately change it and are not
order dependent.

Bug: 10853805
Change-Id: I68a4f9bdf5dc18d90f4cdef7a60811f57be67261

Do not change NetworkInfo.DetailedState.

I'd changed DetailedState to force ConnectivityService to treat
provisioning apn's specially. In particular so that they wouldn't
be identified they were fully connected until the provisioning
actually started. The problem is that DetailedState is a public enum
that has a CTS test and just changing the CTS to allow for the new
state (CONNECTED_TO_PROVISIONING_NETWORK) was inappropriate.

Instead I've added a new mIsConnectedToProvisioningNetwork variable
and used the DetailedState.SUSPENDED as the intermediate state.

Bug: 10620248
Change-Id: Id4a842398cad67455541ce629959351c27d83639

Add support for handling mobile provisioning networks.

When a sim is new or it has expired it needs to be provisioned
with the carrier. Basically provisioning is associating a sim with
a user account. When a sim isn't provisioned then operators will
restrict access to the network and only allow certain addresses
or services to be used.

This set of changes allows two types of provisioning networks to be
recognized. The first is a network that causes all DNS lookups to be
redirected to a different address than was intended. This is exemplified
by how T-Mobile works.

The second technique uses a special apn for provisioning. An example is
AT&T where lwaactivate is the provisioning apn and broadband is the
normal apn. We first try broadband and if we are unable to connect we
try lwaactivate. When we see the activate we identify it as special and
the ApnContext.isProvisioningApn will return true.

In the future our plan is to create a new network type that can be added
to the apn list, but for now it identified by name.

Here is a list of significant changes:

- CaptivePortalTracker now only test WiFi networks instead of all networks
- checkMobileProvisioning checks for provisioning networks and doesn't
try to ping.
- IConnectivityManager.aidl changes:
* getProvisioningOrActiveNetworkInfo was added to and used by Manage
mobile plan in WirelessSettings so even when there is no active
network it will still allow provisioning. Otherwise it would report
no internet connection.
* setSignInErrorNotificationVisible is used by both
CaptiviePortalTracker and checkMobileProvisioning so they use the
same code for the notifications.
* checkMobileProvisioning was simplified to have only a timeout as
returning the result is now harder as we abort simultaneous call
otherwise we'd could get into loops because we now check every time
we connect to mobile.
- Enhanced MDST to handle the provisioning network.
- Added CONNECTED_TO_PROVISIONING_NETWORK to NetworkInfo to make a new
state so we don't announce to the world we're connected.
- TelephonyIntents.ACTION_DATA_CONNECTION_CONNECTED_TO_PROVISIONING_APN
is sent by the low level data connection code to notify Connectivity
Service that a provisioning apn has connected. This allows CS to
handle the connection differently than a normal connection.

Bug: 10328264
Change-Id: I3925004011bb1243793c4c1b963d923dc2b00cb5

DO NOT MERGE: MDST is not ready until connected to DcTracker.

When the system becomes loaded the PhoneApp can be delayed
significantly and a call to setEnableFailFastMobileData may not
occur because the channel between the MobileDataStateTracker (MDST)
and DcTracker (DCT) is not connected.

Solution: Add a isReady to MDST and isMobileDataStateTrackerReady to
ConnectivityService and call it from isMobileOk.

Bug: 10351868
Change-Id: I92f9d58121b88186b636cd71c2fd2ef9a28f7cf6

In isMobileOk don't execute finally if mobile data is not supported.

Move the early return outside the try {} finally so we don't call
setEnableFailFastMobileData(DctContants.DISABLED). Otherwise
referencing counting is wrong and an exception is thrown in DcTrackerBase.

Bug: 10304904
Change-Id: I5ba5121e473bada9f3daa8d6f3d3577cec8212fc