PowerWidgetUtil: Remove flashlight as a default button

Remove BUTTON_FLASHLIGHT as a default button in
PowerWidgetUtil::getCurrentButtons so as to remain in sync with the
defaults used by PowerWidget (SystemUI).

Otherwise the power widget will only contain four buttons on first boot
(five including WiMAX), but the flashlight will "mysteriously appear" if
any other button is toggled in the "Widget buttons" settings.
German: Update translation

Patch set 1 - Add missing strings for:
              * widget behavior
              * SMS security limit
              * CMCircleBattery
Patch set 2 - Fixed some strings and dedupe
Patch set 3 - Add strings for home button unlock
Patch set 4 - Minor changes
              * replaced '+' with '&'
              * shortened some strings
              * changed wording

Change-Id: I1047714db03d911320a96d57d6ba05862d8539af
App manager: Enable fast thumb scrolling

Change-Id: I018344b5f62b306e96841d6c36c84534956466d1
Settings: Dutch translations

Change-Id: I947c955d3fb04f72b45a4e2b342a09893092fced
Merge "App manager: Enable fast thumb scrolling" into jellybean
Allow airplane and silent power toggle (1/2)

Based upon the system already in place by DvTonder

Change-Id: I8d23ee78bc5d455d10b6cd0a221f12a13f3f64dc
Merge "PowerWidgetUtil: Remove flashlight as a default button" into jellybean
Call to equals() comparing different types

FindBugs description:

Call to String.equals(DataUsageSummary$AppItem)
at DataUsageSummary.java [line 1173]
in method updateDetailData()

This method calls equals(Object) on two references of
different class types with no common subclasses.
Therefore, the objects being compared are unlikely to
be members of the same class at runtime (unless some
application classes were not analyzed, or dynamic
class loading can occur at runtime).
According to the contract of equals(), objects of different
classes should always compare as unequal;
therefore, according to the contract defined
by java.lang.Object.equals(Object), the result of
this comparison will always be false at runtime.

Bug kind and pattern: EC - EC_UNRELATED_TYPES

Change-Id: I8d3d9239b2f296a89968e20381f82e499f43f5d6
Merge "Call to equals() comparing different types" into jellybean
Changed the way that date format selector is shown

Changed the way that date format selector is shown excluding ambiguity when day and month have same value.
- i.e. 01/01/2012 (mm-DD-YYYY) and 01/01/2012 (DD-mm-YYYY)
Now it displays 31/12/2012 for DD-mm-YYYY and 12/31/2012 for mm-DD-YYYY.

Change-Id: Ie165d055da47015267bffcf1cd6d333d89041b2e
Changed the way that date format selector is shown (revision)

Changed the way that date format selector is shown excluding ambiguity when day and month have same value.
- i.e. 01/01/2012 (mm-DD-YYYY) and 01/01/2012 (DD-mm-YYYY)
Now it displays 31/12/2012 for DD-mm-YYYY and 12/31/2012 for mm-DD-YYYY.

This revision of previous code will also prevents on some timezones to display 1st january of next year instead 31th december of current year.

Change-Id: I9071341753e3da34da590bfef049ddbb2d635293
Merge remote-tracking branch 'upstream/jellybean' into jellybean

Conflicts:
	res/values/strings.xml
	src/com/android/settings/cyanogenmod/PowerMenu.java

Change-Id: Iebfeec9f0114996dc5ea0f9334f9f44039f5a2c1