FW: Updated czech translation

Change-Id: Ic98f996d996d9e9bc3cd141dc1ebb2bf9077c27d
Signed-off-by: kecinzer <kecinzer@gmail.com>
Add method to PowerManager that allows querying the lowest possible
brightness.

Used by the auto-brightness adjustment to adjust the sliders.

Change-Id: Idb58fd86dee1a053fe858291be6c9b3169ac4247
FW Ribbons Swipe ribbons seperated && logic adjust for navbar

If you have an enabled navbar weither by default or user seleted
the bottom ribbon has not been available. If the user manually
hides the navbar I will allwo them to use the bottom ribbon.
They can also long press the hidden navbar handle to get the
bottom ribbon.

This also makes the left right and bottom their own ribbons.

Change-Id: Icba9c4ec510149bef74382a3bf59fd79b3ef87c4
Update Japanese translation

Change-Id: I4cff44f0271ee6b5d943eecd06b6884dc73eb78b
Signed-off-by: rdgate <rdgate@gmail.com>
FW: settings: arrayList API rework

There is nothing wrong with the current implementation
it just requires some implicit knowledge about the internals
which should not be used for an API added at such a central
location

To reset the value back to "" you must know that setString
musst be used instead of providing just an empty list which
would be a more "logical" approach

With this the client code would also become easier cause
the check for size()>0 would not be longer required
e.g. in RibbonTargets

I would also suggest to change getArrayList so that it
returns an empty list for the case that the value is ""
instead of an list with size 1 and the single item ""

Allthough this would be a change in the API it would
make the API sync with the putArrayList and would also
be the more "logical" return value for this case

I think I have checked all current uses of getArrayList
and as far as I can see that change would have no impact
on the existing code. But please correct me if I am
wrong with this.

Change-Id: I58a34e1238fefbfe088252e785cfed3d8c3acf4b
Signed-off-by: maxwen <max.weninger@gmail.com>