Settings: add back button in actionbar on Status settings

for more consistence. We add it as drawable due that we still have 3 other
places in settings where it is missing.

We will change later....after that we should have worked every inconsistence out.

Change-Id: If21d03b04d2356fa78349baa8ff2fb3b008dacbf
Settings: Update AppNotificationSettings if user resumes

Right now if a user resumes this activty (eg from recents) and did change in the
mean time settings which effects the visibility of preferences in AppNotificationSettings
(eg were removed) it does not get updated.

Fix it with simply reloading the content on onResume and decide to show the entries
on the current user settings situation.

Change-Id: I0b16ebf35604fdca1611f026c9b609427f3060c8
Settings: Do not allow to access quick settings on secure lockscreen - option (2/2)

We have a lot security guys as user due of using the phones as business phones...that
said a lot complains go into the direction of google how it is possible to have
access to quick settings on a secure lockscreen which is absolutely understandable
due that you are able to control Wifi BT AirplaneMode data etc.

This patch takes care on this problem and adds an option to control this behaviour.

ATTENTION: Due that this is really an UX derp for an average user this feature is
enabled by default now. User need to disable it explicit in settings to get on secure
locksreen the original android behaviour back.

PS2:
- fix derp

Change-Id: Iac8c181767a16d3d198672d16901670984b58f48

Conflicts:
	res/values/screwd_strings.xml
Prevent factory reset for short passwords in CryptKeeper

Since patterns and passwords can't be shorter than 4
elements, we shouldn't count them against attempts to unlock
the device.  If we do, we risk resetting the device
due to stray input.

Bug: 18211475
Bug: 18273380

Conflicts:
        src/com/android/settings/CryptKeeper.java

Conflicts:
        src/com/android/settings/CryptKeeper.java

Change-Id: Ib329cd3383471483cda68bfac4278b17d0c09c57