fix NullPoint bug in lockscreen

Change-Id: Ibe0c970f0344fb9c02867a97592783f695565f15
SystemUI: unlock keyguard to open nav ring apps

Should not launch apps if it's secured with a pin/password/pattern.

Change-Id: I52fd604a15982e9eed465e005425b93ffb2a6e82
Signed-off-by: Roman Birg <romanbirg@gmail.com>
Fix autorotation sensor loop being reactivated even when off

The sensor loop was reactivated even if turned off after a wake up
=> consider it disabled also if !mEnabled
+ turn debug mode on in case there's another issue.

Since the current autorotation sensor loop is generating 3-4% cpu eating,
we really need a way to turn it off for good for the moment.
System_server now seems to stay at 0.0% cpu with this change & autorotation off on TF101

Change-Id: I5ed3c95809f6d789222819466dacc625ac2d9f1d
Decrease lag generated by autorotation on

There are different issues from what I understand:

1) Discarding of events too close to each others is broken
as mAccelerationTimestampNanos is conditionned by isAccelerating()
on TF101 no events are discarded anymore, and so it creates an update every ~50ms
filing up the android notification message queue quite a bit for nothing and so generating lag.
2) isAccelerating seems incorrect to me too, the code means more that it's accelerating "out of range" and should be discarded in that case.

=> Discard the sample if outOfRange and don't condition the update of mAccelerationTimestampNanos that way next time we come back "too soon"
the sample will be properly discarded.

3) with events being discarded properly on the WindowOrientationListener
the SensorManager can now update every 20ms instead of 50ms
but that is definitely overkill.
=> add SystemProperty sensor.loop.minms with a default value of 50ms to throttle the notifications.
That way the thread sleeps properly instead of sending events as fast as it can.

(increasing up to 100ms can be ok depending if you want faster response or not.)
This can be positionned on a per device prop too.

4) Add 2 SystemProperties:
one on the SystemSensor side: sensor.magnitude.threshold with a default 0 value(doesn't change the behavior)
one on the WindowOrientationListener: orientation.magnitude.threshold with a 200 (0.2G) default value
These allows to discard the sample if it is too close to STANDARD_GRAVITY (ie not accelerating much)
These can be set on a per device or use the default values.
On the TF101 200 works most of the time. But weirdly when docked the reported gravity seems to have an additionnal offsert of -0.2
maybe some magnetic interference from the dock...

For the moment the 0.2G threshold is positionned on the Orientation code.
Once the cpp sensor poll crazy loop is solved it could be better to use the sensor.magnitude.threshold instead.

That should take care of most of the lag generated by autorotation.

PatchSet2: position default SystemProperties values to do nothing.

Change-Id: I093227f539050a6bad8e6e8d9f533eff7bddd0d6
Resize DateView text for Tablet ui mode

Change-Id: I0bec11ce4f3642408f910f68f1ed2ff3bfab1ec8
keyguard: fix layout for 320dp devices

800x480px dpi devices have less screen space than the xhdpi devices
Google designed the layout for and the layout needs adjustment.

- Reduce the lockscreen security container size such that the clock
  widget has enough space to display its content.
- In the SIM PIN/PUK view, Google put an empty widget on top, but
  we don't have space for that, increase its size such that the
  widget practically disappears.

This should not have any effect on devices with larger screens.

Change-Id: I9e811cfd312abae24a9cad189d19e73848f6c4c1
Maximum Statusbar notification icon (1/2)

Change-Id: I1603c6c54ea74588a5dc1ae787e780cbf247ca90
Mms auto-retrieval (1/3): framework

Change-Id: I9b2f76d8cf9d67eddddfdf7737a948eea680329f

It's only porting this http://review.cyanogenmod.org/#/c/26166/
Part 1 of 3
TelephonyProperties: Alpha ID fix for OPEN_CHANNEL and other p-commands (1/2)

p-cmds that support the below mentioned scenarios:
- SETUP CALL
- OPEN CHANNEL
- SEND DTMF
- SEND SMS
- SEND SS
- SEND USSD
- LAUNCH BROWSER
- PLAY TONE
- SELECT ITEM

Senarios handled :
- NO ALPHA ID : Introduce a new configurable sys prop
  "persist.atel.noalpha.usrcnf".
   --  Allow display of default UI confirmation if prop is set to true
   --  No UI confirmation to be show if prop is set to false
- NULL ALPHA ID (len = 0 ) :
   -- NO UI confirmation to be displayed

Cherry-picked from CAF commit 5ea0d64186ca08abc0857aae1f83de969393be3b
Without this SimToolkit will pop up asking for user response instead
of recieveing response from framework.

Change-Id: I012707285ee3a93119c2e2956ec599d631db10d5
Signed-off-by: dhacker29 <davidhackerdvm@gmail.com>

Conflicts:

	telephony/java/com/android/internal/telephony/TelephonyProperties.java
Lockscreen: enable longpress on expand challenge handle (1/2)

If enabled it will be possible to longpress the little lock icon.

If it is an unsecure screen lock then the longpress will unlock the device.
If it is secure then the widget will fade into the background and you need
to enter the pattern, pin, password or whatever.

Change-Id: I901424c8c54d59298d6d77c10154f5410a636b01
Signed-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>

Conflicts:
	policy/src/com/android/internal/policy/impl/keyguard/KeyguardHostView.java
QuickSettings: enable theming of user label

Change-Id: I2c5a7693516c890077e5f4f8050a6196bdcbf3f5
Signed-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>
Increase themeability of Clock, Signal, Wifi in statusbar

Now fixed negative numbers

Patch-set 2: Forgot cleanup log.

Patch-set 5: Compatibility with alt. signal layout

Change-Id: I6458998c37e7d9c07d389d851647bb98a15797f9
Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:
	packages/SystemUI/res/values/styles.xml
Lockscreen: provide haptic feedback on longpress unlock

Change-Id: Ie7e32a0e3d410da26095bfce1a8e5ba94f0b5eaf
Signed-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>
Hide Navbar Patchset 5

Change-Id: I025b0d550ef2eefd7fe20bed477f3715cf3c0d42