keyguard: fix layout for sw320dp devices

Squashed commits of the following:

commit fa06992ab7e49fe1e056787dd281384d92290be1
Author: Pawit Pornkitprasan <p.pawit@gmail.com>
Date:   2012-12-10 09:19:40 +0700

    keyguard: fix layout for sw320dp devices

    800x480px dpi devices have less screen space than the xhdpi devices
    Google designed the layout for and the layout needs adjustment.

    - Reduce the lockscreen security container size such that the clock
      widget has enough space to display its content.
    - In the SIM PIN/PUK view, Google put an empty widget on top, but
      we don't have space for that, increase its size such that the
      widget practically disappears.

    This should not have any effect on devices with larger screens.

    Ported from cm-10.2.
    * Removed invalid mdpi layout leftover from framework-res
    * Fix keyguard for mdpi devices too

    Change-Id: I9e811cfd312abae24a9cad189d19e73848f6c4c1

commit 9c9c6d17772f4fa4681f43bea11fb5074e24093a
Author: Lorenzo M <djmesias@yahoo.es>
Date:  2013-12-08 23:05:32 +0100

    keyguard: fix-fix layout for sw320dp devices

    Default values need to be defined in sw360dp or larger devices will
    pick up sw320dp values automatically.

    On the maguro device the keyguard isn't properly centered.

    - Before http://review.cyanogenmod.org/54758:
        http://i.imgur.com/F6sokhA.jpg
    - After http://review.cyanogenmod.org/54758:
        http://i.imgur.com/OdTkZLL.jpg
    - With this commit:
        http://i.imgur.com/TThq9da.jpg

    Change-Id: Idcc29ec79a12e61b26d2ad5070468e70a8ef39df

Change-Id: I84288c2bd02fd36a3db28a0050cbad052424b719
SystemUI: Fix screenshot animation not showing the picture properly

When taking the screenshot,the drop-in animation looks completely like a mess.
This patch fixes the problem and now the taken picture should be displayed
properly.

Change-Id: Iddb72e58a236d6a96048608ee140ce262053d5d2
Merge "keyguard: fix layout for sw320dp devices" into android-4.4
[1/2] Base: Quick swipe

add disable quick swipe while editMode enabled

Change-Id: I7629084dd19881d09fc69849ddad593c8a4aed35
Merge "SystemUI: Fix screenshot animation not showing the picture properly" into android-4.4
base: more recents circle memory indicator fixes

Set initial visibility after inflate

Change-Id: I1d24efdfca40869573ff4c8a2ec19870827fd33f
base: fix init of ringer/notification volume linking

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

on startup mLinkNotificationWithVolume must be set before updateStreamVolumeAlias

PS2
fixed missing getIntForUser usage for default volume setting

Change-Id: I582c2c544dfeddd8da1a1cb1be2fff6edc7d483c
Merge "[1/2] Base: Quick swipe" into android-4.4
SystemUI: temporary workaround for garbeled screenshot preview

The problem shows some underlying issues View.LAYER_TYPE_HARDWARE
so this is NOT a fix. Just since this issue is so obvious visible
it would save us from a lot of bug reports and questions for now :)

Change-Id: If188aa668c1024e857d931ccef4ad3e99edce348
Force disable hardware keyboard

Change-Id: I12ffa641186144b075292d103def4da34b7bbc7b
Turn off carrier provisioning by default

Whether or not to use carrier provisioning is a setting hidden to the
end user that is currently not set. Unfortunately, on some carriers that
may result in it being set to yes, or effectively set to yes, without
other accompanying changes that must occur, such as setting a tethering
apn and possibly having a carrier provisioning app, resulting in hitting
a paywall when a tethering plan exists, or, worse having nothing happen
at all when you try to tether since the data doesn't have an apn set.

Change-Id: I3b5b3cc86e3325302411f46e3fd5f7a7c1b9f57e
SystemUI: Forward port Statusbar Clock and Date actions

Port of http://review.cyanogenmod.org/#/c/27795/4

PS2: Cleanup and address comments
PS3: Remove unused variables

Begin old commit message-----------

Patch set 1-2: Initial port
Patch set 3  : Fixes date click action
Patch set 4  : Remove unused import

Includes:
- Add onClick action to notification clock and date
  In expanded StatusBar
  - clicking clock opens alarms
  - clicking date opens calendar - today selected
  Id: I850732dcca0e65af59ce009aaf9f7ba18bcaf915

- Add onLongClick action to notication clock and date
  - As discussed with ciwrl on google+, LongClick opens DateTimeSettings
  - Moved on-touch color change to superior xml solution, as suggested by
    Andrew Boren <preludedrew@gmail.com> here: http://review.evervolv.com/#/c/3676/"
  Id: I1fae71e347ffcb786227ba0b2651a66f2df35e27

- Add SET_ALARM permission for SystemUI
  If one or more third-party alarm clock app is installed, clicking clock should
  open an app chooser for the alarm clock. However, permission for
  com.android.alarm.permission.SET_ALARM is required to make this behaviour
  work properly.

Change-Id: I8006e57a953fe0c4be480e0aa27a4c28c672f982
Suppress String resources build warnings

warnings suppressed are:
aapt: warning: **** string '%s' has no default or required localization for
aapt: warning: string '%s' has no default translation in

Patch Set 2: move ifdef and only suppress warnings for packages that
             define NO_DEFAULT_TRANSLATION_WARNINGS and/or
             NO_LOCALIZATION_WARNING

Patch Set 3: by default do not show warnings unless
             SHOW_DEFAULT_TRANSLATION_WARNINGS and/or
             SHOW_LOCALIZATION_WARNINGS

Change-Id: I50ef2a623959a1cc53053b446328df8e34cc99e8
Base: Cleanup translations to get rid of compiler warnings

Squashed of 4 commits by kufikugel:

commit 1612533cffda5b3c3d76c4daa1c3d9938391da2a
Author: Lars Greiss <kufikugel@googlemail.com>
Date:   Wed Dec 11 18:57:28 2013 +0100

    DocumentsUI: google please cleanup your translations....DocumentsUI cleanup

    it is really at the moment a nightmare to see compile errors when
    getting 100000 of warnings. Whatever we removed already on some
    packages the warnings....but still a lot are there

    Change-Id: I51682d5b74f76cb5e14d0a51d7694ee7235236be

commit 36b4bf5727947b3b1a93298e32c85d95c36b8080
Author: Lars Greiss <kufikugel@googlemail.com>
Date:   Wed Dec 11 18:48:34 2013 +0100

    Keyguard: google please cleanup your translations....Keyguard cleanup

    it is really at the moment a nightmare to see compile errors when
    getting 100000 of warnings. Whatever we removed already on some
    packages the warnings....

    this package is the best.......nearly every language has left
    overs where not one string is used at all and one string
    which is used does not exist in system language

    whatever remove and add it like it should

    we are now warning free

    Change-Id: I06a3a3d15560aa04abd8c6c4981ac12c6dbc0c90

commit 3cd5da20b444731251c84ad4bd8422d03d76f28c
Author: Lars Greiss <kufikugel@googlemail.com>
Date:   Wed Dec 11 17:54:47 2013 +0100

    fb: google please cleanup your translations....fb cleanup

    it is really at the moment a nightmare to see compile errors when
    getting 100000 of warnings. Whatever we removed already on some
    packages the warnings....but still a lot are there

    Change-Id: I1cc3abee5b4820d9c56b89056f1ea7e4d798947b

commit 2454e3718c7cb32fa700d1ac2b6afc2383dec1f4
Author: Lars Greiss <kufikugel@googlemail.com>
Date:   Wed Dec 11 00:30:54 2013 +0100

    fb: google please cleanup your translations.....systemUI cleanup

    it is really at the moment a nightmare to see compile errors when
    getting 100000 of warnings. Whatever we removed already on some
    packages the warnings....but still a lot are there

    This commit cleans up SystemUI

    Change-Id: I4e246e1cfc13bb18eb75624510e53731821ff553

Change-Id: I5f2bcd7f4a1acb7a28643c1c1203a886db10cc92
services: don't clear wallpaper when SystemUI
disconnects.

When we restart SystemUI (or the user), sometimes
the wallpaper would get cleared. This patch just
captures its originating component and
if that is our SystemUI component, ignore the event.

Change-Id: I3e159dc2c013e7d7e552e3c0cef55e3ab970ca87
Signed-off-by: Roman Birg <romanbirg@gmail.com>
fw/base: update volume control to white to match 4.4 icons

PS3:updated drawables.  Screenshot: http://bit.ly/19vZLCO

Change-Id: Ib30b796d1aeccaa32d5223d36aed6e18a2dc1062
Signed-off-by: Aaron Klein <aaklein@gmail.com>
Change Quick Pulldown from 70-85%

Change-Id: I9d6c291a5d16460fe5353fe60c5c78045bb26e96
Camera: add ISO mode support

Change-Id: Ied2075f950269990d836fc768b2c6c36088d494f
Camera: add additional ISO modes (2/2)

Change-Id: I3460c3de4cbef467430673146a9ddb2fdc8f5032
Fix Photosphere/Camera FCs

Photosphere is setting a few parameters "blindly"
while the API says it should check the device capabilities first.

On TF101 (and probably other devices) the camera HAL doesn't handle
FLASH_MODE & SCENE_MODE and so it sends the required RuntimeException
for these, which makes Photosphere FC the Camera app.

=> Fix: check device capabilities & ignore these 2 parameters if the device doesn't support them.

Fix based on following Team EOS patch: https://review.teameos.org/#/c/1598/

Change-Id: Idd80299802e9213a3c40414ace3d516d39f47783