SamsungQualcommUiccRIL: use signalstrength value instead of # of bars

  * Math error in GSM level calculation gave high probability that 4
    Samsung bars would be shown as 3 AOSP bars.
  * Samsung sends # of bars in the signalstrength field of GSM and LTE,
    indexes 0 and 7. But this is on a 0-5 scale where AOSP uses 0-4 scale.
    The cutoff points for the bins are also different. Because of this
    confusion, just pass the measured signalstrength to the framework
    instead of computing signalstrength based on # of Samsung bars.
  * For debug and experimentation, Samsung's bar method can be enabled
    by setting telephony.sends_barcount=true

Change-Id: I8238af83f3a597b32eb99f42c71cbc263ad5bc82
Tablet powerwidget improvements (1/2)

Removes a lot of unecessary code, and does not limit toggles by 6 but dinamically adds the views to layout

patchset 2: remove tab

Change-Id: Id125605791d2de353e7466c4dfe135c32fb80df6
fix automatic timezone failing on some GSM networks

in the code that parses the NITZ string, someone made the assumption that if
any data follows the DST flag, it must be be the android emulator appending
an actual timezone string in "Area!Location" format.  However, it seems that
some carriers or perhaps in some locations, the carrier sends an additional
field in the NITZ string.  For example, this is a string from AT&T:

12/07/01,09:37:43-16,01,310

The extra field is "310" above.  This patch will only assume that the field
in question is a textual timezone if and only if it contains an exclamation
point.  Otherwise, the extra field is ignored and the timezone is parsed
as it should be.

Change-Id: I6cc4278027a6de5545d76b803f5359923e60878a
Signed-off-by: Gary Dezern <garyd9@gmail.com>
Disable touch while using the stylus (Galaxy Note)

Android 4.0 cannot form multitouch events from multiple input
devices. So it is not possible to report one touchpoint from the
stylus position and, at the same time, another touchpoint from a
finger touch. Instead, when a new input device starts up the currently
active input is cancelled. This is highly undesirable while writing
with the pen.

The easiest solution is to ignore non-stylus touch events while the
stylus is within range (hovering) of the touchscreen. For example,
N-trig digitizers implement this in hardware. But wacom digitizers do
report pen data simultaneously with touch data. This patch disables
(non-stylus) touch input within 50ms of stylus data. On my Galaxy
Note this is necessary to make stylus input usable.

Change-Id: I9f458d85d8bf83d6cf03b467d46ce066fd55b7e0
PT-BR: SystemUI Screen timeout translation

Change-Id: I9fe94cc036c15cdba0eccd3c5778687a3c6eee98
camera: fix samsung/qcom conflict

hello ifdef hell

Change-Id: I76bede141dfd4fd4f32b5a5aa8987fb255c207a5
Merge "SamsungQualcommUiccRIL: use signalstrength value instead of # of bars" into ics
Merge "fix automatic timezone failing on some GSM networks" into ics
Externalize symbol picker options to resources

Having the symbol picker options in resources allows a change to be made for
a specific device, and even for a specific locale (change in overlay).

Change-Id: If39eafc7d0766d28ef6bee0ff61bf234a6654f38
Merge "Tablet powerwidget improvements (1/2)" into ics
Merge "Disable touch while using the stylus (Galaxy Note)" into ics
Merge "PT-BR: SystemUI Screen timeout translation" into ics