ActionBar: Compute required items prior to optional items

When computing if a item should be shown in the action bar, required items need to be compute prior
to optional ones. Otherwise, in some cases (when the optional menu goes to the left of required
items then the algorithm could determine that optional has space to be shown and force the show of
required items, causing the required items to not be shown).
A concrete case is in the Email app. In the message_view_fragment_option.xml are defined 5 menus,
that when are all shown (xe: in Exchange mailbox account type) the bar is complete filled. But if
the overflow button is forced to be shown (the device has no permanent menu key) the overflow button
overlaps the older button, because space of 'ifRoom' items are wrong computed.

Change-Id: I6fc8e3e202d76f9704d7ec2383c7ee6f7b05ba76
Japanese: update translation.

  - Add missing translation entries.

Change-Id: I076e396c065b642d9bf342452eacea4588a5525f
Update korean translation

Change-Id: Ic6c85c8253d81079316e38a58e7e852e44be5a73
Framework/SystemUI: Update Greek translations

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

Change-Id: I2a9978b20ce0d70621e88913841758553721e6a8
QuickSettings: Fix Swedish translations

The translation of "Bluetooth Off" to "Inaktivera Bluetooth"
(which means "Disable Bluetooth") causes confusion as the string
is meant to show the status, not what would happen if you tapped it.

The translation for "WiFi Off" is valid but it doesn't fit. Changed
to "WiFi Av" to match the change above. This one can be discussed.

The translation of "WiFi Display" translates the word "display"
as a verb which made no sense in this context. There is currently
no proper Swedish name for the WiFi Display standard so the English
name is used instead. It's what people actually use anyway. "WiFi visas"
means "WiFi is displayed" which is clearly wrong in this context.

Change-Id: I6013421242ee1dea6bbc2bc6adbf83581b4c6de2
SystemUI: Dutch translations

Change-Id: Ib367b7ab489110138aed156dedb17adda6e5d9df
Merge "QuickSettings: Fix Swedish translations" into cm-10.1
Merge "Framework/SystemUI: Update Greek translations" into cm-10.1
Fix HTC headset handling.

HTC's headset driver adds additional bits to the switch state, which
we're unable to deal with. Fix that by masking out those bits and
keeping only the valid ones.

Change-Id: I29f0de9520ebb56d61acbc9a6dfcfc73e1f297d8
Merge "Fix HTC headset handling." into cm-10.1
Adds ability to answer call with hardware HOME button (preparation to winter time)

Change-Id: Ic11449acf87c6b4d932142b74158af7441658b3d

Patch set 1 : Upload the change
Patch set 2 : Only change the real Author
Patch set 3 : Bugfix:
              Add register for the ContentObserver (Settings.Secure.RING_HOME_BUTTON_BEHAVIOR) in PhoneWindowManager,
              and correcting the logging functions and deleting some unneeded comments
Add config_hasRemovableLid

If a device features a dock with a removable lid, lidOpenRotation
overrides the rotation even if it was undocked (technically the lid is
still open).

This setting tells the framework whether to apply lidOpenRotation to
undocked devices.

Change-Id: I1051278a45875b2139b75db28467f9b8de2936d6
Correcting hungarian translation

Change-Id: I7f68a801dd680c4c2f4f2f528f1f0079c8cdabb7
Merge "Japanese: update translation." into cm-10.1
Merge "Update korean translation" into cm-10.1
Merge "Correcting hungarian translation" into cm-10.1
Revert "Japanese: update translation."

This breaks the build!

This reverts commit 3cad9a750319aec8dd4ec73dd89f6baf0ef566e7

Change-Id: I5449e1af55230e927d8f06a8f7bb58595d132c41
Merge "Revert "Japanese: update translation."" into cm-10.1
Revert "Revert "Japanese: update translation.""

Fixing build error introduced with original patch set.

This reverts commit e58d55180a8fb7997845ea31a7e2a4621a7faa62.

Change-Id: I623af1c083f45121f784d0a772c5c02d03240386
GlobalActions: Fix possible race condition when showing dialog.

Depending on the presence of a previous dialog, the newly generated one
gets either immediately displayed (no old dialog) or shortly delayed
(after dismissal of the existing one).
If a new show event happens (by rapid fire of the power key, for instance,
using a keyboard with fast-repeating events) during that delay, a new
dialog will be immediately displayed, and when the delayed show triggers
it'll conflict with it (and bring everything down).

This moves the creation of the new Dialog object to _before_ showing
it (delayed or not), instead of the show method itself, to ensure the
object isn't clobbered by competing/sequential calls to handleShow()

Change-Id: Ie4d9a8507ebaf59da31869c38b98c3c98a74468e