fix padding for stock icons in nav bar
Signed-off-by: AK <apkellar@gmail.com>

Change-Id: I6bcb931e89e7bbfa1239a0b9f4162eb7a39f7203
SystemUI: fix data toggle

- required double tap to work previously

- also changed the long press intent to open
    network settings instead of general wireless
    settings, as it is more appropriate for this
    toggle

Change-Id: I808bd886e11de217cee1a37193ac1ff529856468
Lockscreen clean up octo layout

Since We reduced the icon sizes we can now drop the carrier text back down,
so it doesn't look so awkward.

Pics
http://dl.dropbox.com/u/31932935/Screenshot_2012-06-01-08-23-42.png
http://dl.dropbox.com/u/31932935/Screenshot_2012-06-01-08-23-56.png
http://dl.dropbox.com/u/31932935/Screenshot_2012-06-01-08-24-18.png

Change-Id: Id48720f5230b94f26f87e8fa0a93b6796f8a2538
stagefright: Turn off verbose logging in LPAPlayer

Change-Id: I3e90fad0b93b594fda4357a8b7094d94a3b22469
Add OMAP_COMPAT and OMAP_ENHANCEMENT frameworks flags

OMAP_ENHANCEMENT is for omapzoom stuff, if required...

OMAP_COMPAT will be required soon to use the specific
wlan and omap3 codecs. (Same as CM7)

PS: We already use omap3-compat as hardware/ti/omap3
    on the defy ics version since months...

Change-Id: I7e9d9abd39b8bf5b62fa5583241eb0fcfffaba01
Input: Fix some Applications ANR issue in monkey test

Issue Description:
When do monkey test on some applications, there is big probability get ANR issue. one example is as following:
    adb shell monkey -p com.google.android.street -v 500000

Root Cause:
situation 1. InputDispatcher Thread calls findTouchedWindowTargetsLocked routine, there is a AMOTION_EVENT_ACTION_DOWN event
             and it can find a splittable touched window for this event , then mTouchState.split set to true.

situation 2. WMS Thread calls setInputWindows routine and all TouchedWindows associated with mTouchState are removed ,
             mTouchState.split status still keep true.

situation 3. InputDispatcher Thread calls findTouchedWindowTargetsLocked routine, there is a AMOTION_EVENT_ACTION_POINTER_DOWN event
             and it can find found touched window, exit window loop in following code :
                  if (windowInfo->visible) {
                    if (! (flags & InputWindowInfo::FLAG_NOT_TOUCHABLE)) {
                        isTouchModal = (flags & (InputWindowInfo::FLAG_NOT_FOCUSABLE
                                | InputWindowInfo::FLAG_NOT_TOUCH_MODAL)) == 0;
                        if (isTouchModal || windowInfo->touchableRegionContainsPoint(x, y)) {
                            if (! screenWasOff
                                    || (flags & InputWindowInfo::FLAG_TOUCHABLE_WHEN_WAKING)) {
                                newTouchedWindowHandle = windowHandle;
                            }
                            break; // found touched window, exit window loop
                        }
                    }

situation 4. The following code will have problem after situation 3 in below conditions:
             newTouchedWindowHandle doesn't support split , isSplit is true ( last time touched window is splittable )
             mTempTouchState.getFirstForegroundWindowHandle will always return NULL due to situation 2

            // Figure out whether splitting will be allowed for this window.
            if (newTouchedWindowHandle != NULL
                    && newTouchedWindowHandle->getInfo()->supportsSplitTouch()) {
                // New window supports splitting.
                isSplit = true;
            } else if (isSplit) {
                // New window does not support splitting but we have already split events.
                // Assign the pointer to the first foreground window we find.
                // (May be NULL which is why we put this code block before the next check.)
                newTouchedWindowHandle = mTempTouchState.getFirstForegroundWindowHandle();
            }

            The window says it does not want to support splitting, so the touches should go to one of the previously split windows except
            that there are none, which result to "goto Unresponsive" in findtouchedWindowTargetsLocked routine.
            This is not the correct behavior because the user did actually touch something.

situation 5. InputDispatcher Thread will call dispatchOnce repeated to try to dispatch this AMOTION_EVENT_ACTION_POINTER_DOWN event,
             then ANR timeout ( 5000ms ) will be exceeded after several times "goto Unresponsive"in findtouchedWindowTargetsLocked routine.

Solution:
In situation 4 we should drop the touch. If the newly touched window was splittable then we wouldn't drop the touch.
It's only when the newly touched window was not splittable where we will drop the touch.

Change-Id: Iab2c06ce0597ac77eb886ccd9d84646c86723bdb
Author: Jeffrey Brown <jeffbrown@android.com>
Author: Erjun Ding <erjunx.ding@intel.com>
Author: Zhenghua Wang <zhenghua.wang@intel.com>
Author: Jack Ren <jack.ren@intel.com>
Author: Bruce Beare <bruce.j.beare@intel.com>

Conflicts:

	services/input/InputDispatcher.cpp
Base: Added czech translation

Czech transaltion of power menu.

Change-Id: Iae8e3653a47021de92474ed68acdc222e7e17f32
Signed-off-by: kecinzer <kecinzer@gmail.com>
Merge "fix padding for stock icons in nav bar Signed-off-by: AK <apkellar@gmail.com>" into ics
Merge "Lockscreen clean up octo layout" into ics
ime switcher notification: remove reboot requirement (1/2)

patch set 2: fix uri, remove old comment, add handler

Change-Id: Ie21fed15c2cc865ae2d164fa485cc44d69ef5452
Merge "SystemUI: fix data toggle" into ics
Merge "ime switcher notification: remove reboot requirement (1/2)" into ics
swiping navbar widgets (1/2)

Change-Id: I45e6254bbe20afdd8d367e01b4bd7855206a6a04
Merge remote-tracking branch 'upstream/ics' into v880