Core: HU translation correction

Change-Id: I95d7149475ea4e42172df019186b18b5ee45a671
audio: Add overlay to fix analog docks.

Of particular interest to devices using libhardware_legacy and
affected by commit 5a484b753cc72d6a50c1dd3bbf68b3403c741a3a: http://goo.gl/rVR1Z
which restricted the routing of AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET
to docks using FORCE_ANALOG_DOCK cases. The EXTRA_DOCK_STATE_CAR case is
returning FORCE_BT_CAR_DOCK, preventing the dock audio from routing properly.

Add an overlay option for overriding to FORCE_ANALOG_DOCK.

Change-Id: Ib7d70c242aa6f537ea5d65098ceb2c591662d8bb
FrameworkBase: Add missing AF translations

Change-Id: I2f40a2bef27b83c54b94a4d705e580fddefb129f
PowerMenu : Profile entry fix

Always reinflate views
Jira : https://jira.cyanogenmod.org/browse/CYAN-1017

Change-Id: Ib348bb4c9a85b6433a86eeed1b0de9deff9d50bc
Send out a configuration change when screen size changes due to expanded
desktop.

This kills the status/nav bar hide/show animation, but it's required by
some apps to recalculate their content correctly.

Change-Id: I3f4844815005acab111853fa707cd461f83e2efe
SystemUI: Update brightness dialog, on updateResources()

The small dialog also deserves the chance to get updated
resources.

Thank you Jiangyi, for finding that one.

Patch Set 2: Unbreak things

(cherry picked from commit ffff58b2685bd29cbcc11c06bad87d18d448787d)
Original change:
  I6e9de7c35abff52c2fcc2952771bb42b406496ed
  http://review.cyanogenmod.org/36846

Change-Id: I946fa388f667a0343812172ca6f5802a63c27ce7
Merge "SystemUI: Update brightness dialog, on updateResources()" into cm-10.1-staging
core: EL translations

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: I002f18400ed300616739ea067dd051fdcc174c6b
Merge "core: EL translations" into cm-10.1-staging
Don't include flags in configuration change if their value hasn't changed.

This makes the check in updateFrom() match the logic in diff().

Change-Id: I3ab4e8460f7fbf985ef55b9514a8aa90d401d486
Fix up notification LED behaviour

- Commit 5713307e3d2eb457ba148df3683ad09733727506 (in ICS) attempted to
  fix the problem that the notification LED wasn't reenabled after
  turning off the screen again, but introduced another bug in the
  process: If another pending notification with LED at the time when the
  notification with the new magic flag introduced by that commit (which
  was used by phone and MMS apps) was active, the LED still wouldn't be
  turned on at screen off time. Also, this commit didn't handle locking
  correctly.
  This commit essentially reverts 5713307e and makes sure the LED is
  reevaluated when the screen is turned off again.

- This change also makes the assignment of the LED when multiple pending
  notifications want to use the LED more clear: The notification with
  highest priority gets the LED. If multiple notifications with same
  priority exist, the most recent one gets the LED.

JIRA:CYAN-652
Change-Id: I1df0b40cca2af7a08c240677d22d2a95097b7184
Allow applications to show the navigation bar in expanded desktop mode.

This is used by the settings app to show the navigation bar when editing
it.

Change-Id: Idc8fa5e49f31175dea603d7f1a1ef94ffab7249d
Merge "Fix up notification LED behaviour" into cm-10.1-staging
SystemUI: Clean up old H+ drawables causing issues on manta

These drawables seem to be adapted to fit the old combined
tablet status bar. They mistakenly gets used on manta with
an oversized H+ drawable as a result.

Change-Id: Iefc0e997e31508ea98f10e5b399ce6569a4a3a44
Merge "Allow applications to show the navigation bar in expanded desktop mode." into cm-10.1-staging
Merge "SystemUI: Clean up old H+ drawables causing issues on manta" into cm-10.1-staging
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
frameworks_base: SK Translations

cm-10.1 Change-Id: I16d9aebb6819ca3fbcda417343c8d2d895117f42

Change-Id: I149fbd4d2ea30e825ce475507182985550c85f78
Frameworks-base : FR translation

Translation from cm-10.1 branch

Change-Id: I052362bfcb098e94858aef39b7d184fe25a1635e
core: NL translations

Change-Id: I3e3cc274105e55798a3fe1ece4f5f236019b75ae