Frameworks: take  mPieScale into account to calculate estimated PIE width

if scaled size of the PIE is over or under the default size
the pie was either no using the whole screen space or
it was cutted off. To solve this take scale value
into account when calculating estimated width

greetings SlimRoms

Change-Id: Iccfc8362c0019e3b6ff4bd8066c313c67116c014
Frameworks: Allow smaller SlimPIE sizes + multiDpi fixes (1/2)

Due team, user and kanger wishes I needed to do again something :p
Hopefully now really the last thing :D Is now in full range as well usable
for higher dpi then our stock dpi

This commit does:
- allow bigger size range for SlimPIE layout
- icon are now resized on smaller sizes (only then) then default size
  which allows much smaller overall size
- slight better positiong of the icons in the button item
- Fix: reported issues custom Icons are sometimes to small
- Fix: reported issue that estimated container size took not PIE_SIZE
  into account (follows now on every dpi and size the activation point)
- Fix: Settings style seekbar resets sometimes to last setted value
- Settings: a bit code rearrangement (not needed but I was bored lol)

And now really finished :p

cheers

Change-Id: Ic3e69be4de0b0be8758d9d56ced6a65f104693c4
Frameworks: Remove observer

thanks to Jens....remove PieLayout observer
completly

cheers

Change-Id: Icb722495b2d14c91b630f638f790dbcb14bbcef9
Frameworks: SlimPIE optimize optimize optimize

- stop listening on TelephonyManager if pie is disabled
- reuse already constructed SnapPoints
- pass trough mPieTriggerMask and mPieTriggerSlots
- a bit code cleanup

cheers

Change-Id: Ieef66e8cd7abe89cd419f2f368ef06f09d4e40b4

Conflicts:
	core/java/android/provider/Settings.java
	packages/SystemUI/src/com/android/systemui/statusbar/BaseStatusBar.java
Frameworks: Small correction snappoints

I like easier and nicer code beside that it
respects the reuse of snappoints better

thanks jens

cheers

Change-Id: Iff4a1c107700b79c93df5463d524ef6e159ff387
Framworks: missed some stuff

tested it with right change but submitted wrong one
sorry

Change-Id: Ia50672d038348b11a8083317b40b162770436ed0
NavigationBar : Only inflate once

Thanks Danesh

Since the navbar now has updateResources(), there is no need to reinflate
it upon a theme change.

Change-Id: Ie4753a767a1cb45eb459ee692d16067f83cc7d23
Frameworks: Fix navigation bar recreate on new theme

A bug we have now since ages and never paid much attention on it.
Due our custom navbar the navbar was never recreated right
and only reboot showed the right theme.

On theme change recreate the navigationbar as well

cheers

Change-Id: I376b2765c3b53cb76868c485110fa63a20383053
Frameworks: recreate on theme change SlimPIE as well

like the navigation bar commit let us reconstruct pie
on theme change as well

Change-Id: I36d596dc1677dbc0cc5fb8ed8ad725f717698285
SystemUI: Clean up old H+ drawables causing issues on manta

These drawables seem to be adapted to fit the old combined
tablet status bar. They mistakenly gets used on manta with
an oversized H+ drawable as a result.

Change-Id: Iefc0e997e31508ea98f10e5b399ce6569a4a3a44
Don't include flags in configuration change if their value hasn't changed.

This makes the check in updateFrom() match the logic in diff().

Change-Id: I3ab4e8460f7fbf985ef55b9514a8aa90d401d486
Fix up notification LED behaviour

- Commit 5713307e3d2eb457ba148df3683ad09733727506 (in ICS) attempted to
  fix the problem that the notification LED wasn't reenabled after
  turning off the screen again, but introduced another bug in the
  process: If another pending notification with LED at the time when the
  notification with the new magic flag introduced by that commit (which
  was used by phone and MMS apps) was active, the LED still wouldn't be
  turned on at screen off time. Also, this commit didn't handle locking
  correctly.
  This commit essentially reverts 5713307e and makes sure the LED is
  reevaluated when the screen is turned off again.

- This change also makes the assignment of the LED when multiple pending
  notifications want to use the LED more clear: The notification with
  highest priority gets the LED. If multiple notifications with same
  priority exist, the most recent one gets the LED.

JIRA:CYAN-652
Change-Id: I1df0b40cca2af7a08c240677d22d2a95097b7184
Frameworks: push recents preload time a bit up

seems to be that older hw key devices need a bit more
time to preload the recents because sometimes it ends
up in an empty recents screen. Time delay was
a bit to optimistic. Set it to android default
value for short press.

cheers

Change-Id: I40343a351ea968ae7dc663f2f36dbfef9dde93f5
Frameworks: move emergency call above power widget

AOSP has it always on top (without PW and as well on QS)
so put it on top as well when PW is active so that it
does not jump on animation is consistent

Change-Id: I7524a43f9ea5d45b1af94c677ad365cfcf72f89c
Framework: Always show settings button option for notification drawer (1/2)

This also fixes a bug where the settings button was not showing the proper pressed drawable
and fixes the transparency on the ic_notify_settings_normal drawable to match the rest of the
notification drawer assets.

Also removes longpress PW toggle setting since it now defaults to this.

Change-Id: I1b7624fd3278504a07c79daab00babcb5f7b37d1

Conflicts:
	core/java/android/provider/Settings.java
Framework: Option to force keyboard to show enter key (1/2)

Original SlimRoms feature!  Not everyone likes emoticons :-(

Change-Id: Idc093d8fa14633ccf2817fadcfb09d32768445b0

Conflicts:
	core/java/android/provider/Settings.java
Remove opaque check in GLRenderer when preparing dirty region.

Since preserved swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage to be present from the previous process in the color buffer.

CRs-Fixed: 391492, 403067, 405916

Change-Id: I1f72a3dee2f5d58a984f4cd367c9f7bf08ab9d6a

Conflicts:

	libs/hwui/OpenGLRenderer.cpp

[PATCH] Remove opaque check in preparing dirty region

Since preserved swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new rocess. This prevents
garbage to be present from the previous process in the color buffer.

(cherry picked from commit 2b5e584e2615852b68a69bb529c6926190246b64)

Change-Id: I92a4fa35e0746f12fcd736e21fd30d9c4b644a8a
CRs-Fixed: 391492, 403067, 405916

Conflicts:

	libs/hwui/OpenGLRenderer.cpp

Enable scissor when preparing dirty rect that is opaque

Now enabling scissor before setting it in the opaque case, previously was not doing so.

Change-Id: I1ea904cf01603096e423556090564291ab712d36
CRs-Fixed: 465346
Depends-on: 278453

Remove opaque check in preparing dirty region

Since preserve swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage being present from the previous process in the color buffer.

CRs-Fixed: 465346
Change-Id: I98f2009748244751c4b56af8afbdfeb645c13230
Fix layout of MultiWaveView and GlowPadView.

If the calculated size of the rings is much smaller than the measured
size (which is happening e.g. on mdpi 600x1024 tablets), the glow pad
appeared shifted to the right.
This happened due to the insets being calculated as difference of
available and needed size, and later on being added to the available
size. Example numbers (Nexus 4 with density forced to 160):
- computed size in onMeasure: 768x505
- scaled size in onMeasure: 505x505
- thus, insets are calculated as 131/0
- in onLayout, placementWidth (364) and max target width (108) are much
  smaller than width (768)
- thus, center is calculated as 131 + (768 / 2) = 515, thus shifted to
  the right

Fix that by not using width in the calculation, as the inset size
already takes it into consideration.

JIRA:CYAN-829
Change-Id: Ifc2a93214f812f554a8fed3243eed66aec9f00c9
Frameworks & SystemUI - additional DC-HSPAP support

This commit adds some more informations about Dual-Carrier HSPAP
It allows displaying a "DC" icon on status bar for compatible devices
and add a "DCHSPAP" value in state phone
patch 1: add TelephonyManager to fix build
patch 2: modify ServiceState
patch 3: switch to cm_strings
patch 4: fix a mistake
patch 5: upload a new set of icons, a bit prettier than previous
patch 6: update icons (more opacity to match colors)
patch 7: removed drawable-sw*

here is a screenshot for example: http://imgur.com/mQ2du3l,PSyHoqC

Change-Id: I77d05e23c8ad3efdfeb19cf06ed92e7c57105ebe

Conflicts:
	packages/SystemUI/res/values/cm_strings.xml
TelephonyManager: hide NETWORK_TYPE_DCHSPAP

Change-Id: I77e6d537d5ebbe67bac26c6ef6d0dda498640ca0