Croatian V41 update
	modified:   res/values-hr/cr_strings.xml
Settings: NL translation

Change-Id: I8dea87f02ca87cabc8430331c131fc846183ed53
Merge pull request #108 from redrum781/cm-11.0

Croatian V41 update
Revert "[WIP] LockScreen: allow long-press actions from hardware keys (2/2)"

Conflicts with SlimROM hardware key rebinding.
Revert for now till I find a solution.

This reverts commit 12678175034d707de56236b5d3fc8b48db5a932f.

Conflicts:

	src/com/android/settings/cyanogenmod/LockscreenInterface.java
Add back lockscreen quick unlock
Automatically unlock the lockscreen when the correct pin/password is keyed.

Some settings were removed accidentally during adding of
Forward port CM Screen Security settings (2/2)
https://github.com/temasek/android_packages_apps_Settings/commit/b277c50c9bb8bb15e63dd517d135c1a2891a6697
Settings: Handle navbar heights correct on dpi changes + more (2/2)

Till now we set the height in px in the settings. Which is a problem
especially on multiDPI roms like we are when the user afterwards changes
the dpi due that it isn't calculated correct anymore on the new dpi.

This commit does
- save the dp value in provider and calculate the real px in fb
- clean up the settings stuff for it + do it a bit nicer (only settings part
  where we do not set the value for the listview)
- as well this commit disables movable navbar for tablets (we may will enable
  it in future but it needs a lot more work to have it on tablets correct working)
- add Converter class for common methods we always use....till now only px->dp
  and dp->px method

Change-Id: I7320ea0578a10806883a45369dd628f2c51958fa

Comments from Slim dev:-
just a small hint dirty flashers will have a huge navbar suddenly on bootup
(at least if you had before changed something on the navbar heights) :p
so reset it to default in settings with the reset button or clean install
one of both :D

Patchset: 1
https://gerrit.slimroms.net/#/c/2743/
Build V41.1-private
Fix build
Fix memory leak in ManageApplication

ApplicationsAdapter new a Session member and make it has a reference to
it self. If we don't release it explicitly, the cross reference will
cause memory leak.

Change-Id: Iecce35ae1d56d98cee6347e84d3a3ff57f3b15a5
Settings: Super advanced Custom Toggle (2/2)

If user sets up a custom tile with Chamber of Secrets
actions all of the same setting and each action only
has one value per tile-state we now set up an observer
for that setting. This means the tile will listen to
settings changes for the user and change states as
necessary.

EXAMPLE:
Custom Tile Settings:
State 1 > Chamber > "location_mode" > 3 > name: "GPS on"
State 2 > Chamber > "location_mode" > 2 > name: "GPS off"
Save.

User is informed their tile can now be observed and will change
states as necessary.  Ask them to add an icon and label if the
state isn't recognized (I.E. location_mode is set to 1).
Label set to "disabled" with [ICON].
GPS is changed via Settings>Location...
Another tile...etc.
Tile matches it's state or moves to unknown if setting != user
values in tile.

See Video:
https://www.youtube.com/watch?v=pw5Epcp0fq4

PSX:
Reverted to old build and dirty flashed.
Fixed potential FC's there.  This code can
probably stay since it's all Settings-side...
But if we'd like we can phase it out in a
couple months or something.  We don't want
SystemUI to take a dump when a user saves a tile
that has old code in it's settings.

Change-Id: I09034c76c3bc67179c6eaeb0b23a6d39415caf68

Conflicts:

	src/com/android/settings/temasek/quicksettings/QuickSettingsTiles.java
Merge branch 'cm-11.0' of https://github.com/temasek/android_packages_apps_Settings into cm-11.0

Conflicts:
	res/values/cr_strings.xml

Change-Id: I8800c7c610bb837cb35b840fa30aea581b6e5969