Frameworks: Quiet Hours Automatic Switch (1/2)

Change-Id: I3e09891a60ffc5a11f5b5fabef8e06fb02dc9f5d
Frameworks: Lockscreen Rotation Optional (1/2)

PS2: Change method to allow disable, enable
	portrait, landscape rotation.

PS3: Just clean up...same code.  Different
	style.

Change-Id: I164d31b8980562eb5df68dcb2846410d932a4e73
Framework: disable keyguard widget frame (1/2)

And another user request.  But...I can understand
	it now that I see it without.  They actually
	look quite nice this way.

Change-Id: Id0222140a41eec9e5cd27b769cf860ac62ede1c0
Keyguard: Fix Pin-Layout (squashed commits)

Squashed commits of the following:

commit fa06992ab7e49fe1e056787dd281384d92290be1
Author: Pawit Pornkitprasan <p.pawit@gmail.com>
Date:   2012-12-10 09:19:40 +0700

    keyguard: fix layout for sw320dp 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.

    Ported from cm-10.2.
    * Removed invalid mdpi layout leftover from framework-res
    * Fix keyguard for mdpi devices too

commit 9c9c6d17772f4fa4681f43bea11fb5074e24093a
Author: Lorenzo M <djmesias@yahoo.es>
Date:  2013-12-08 23:05:32 +0100

    keyguard: fix-fix layout for sw320dp devices

    Default values need to be defined in sw360dp or larger devices will
    pick up sw320dp values automatically.

    On the maguro device the keyguard isn't properly centered.

    - Before http://review.cyanogenmod.org/54758:
        http://i.imgur.com/F6sokhA.jpg
    - After http://review.cyanogenmod.org/54758:
        http://i.imgur.com/OdTkZLL.jpg
    - With this commit:
        http://i.imgur.com/TThq9da.jpg

Keyguard: Fix PIN layout on sw320dp-mdpi devices

Commit: 294d0867079d21c0bcfb704315cdbb68a150dba4
Author: Michael Bestas <mikeioannina@gmail.com>
Date Jan 15, 2014 5:21 AM
    Fix a long standing lockscreen layout problem that
    was introduced in 4.2

    Before: http://i.imgur.com/9sVKHRR.png
    After: http://i.imgur.com/DLY4DRu.png

Change-Id: I3001e5678bc10ea7f287548c7d189fe0c45210ec
Input: Fix Palm Rejection

A "bad merge" appears to have broken 'Palm Rejection' for devices
that use a stylus. This commit:

https://gerrit.slimroms.net/#/c/62/

appears to have only implemented half of the necessary changes in
InputReader.cpp for 'Palm Rejection' to work properly. This commit
adds in the missing pieces.

PS2: whitespace derp

Change-Id: I402df6ed45b53cf02299f0b6588c763c3cb3de48
Frameworks: Fix possible ANR and navigation bar freeze

Big thanks to ralpheboyo which provided us the first time a usable
anr trace where we can see what the actual problem is.

The random ANR is caused due of to much work on the navigationBarCanMove
feature. We call way to often the provider value even though it is only
needed on initiliazing or on update of the value. Currently we call it on every
possible navigation bar change and this multiple times.

To fix it just call it on init and on contentobserver changes and pass
the new value to the navigation bar view and the search panel view

PS:
- remove another call
PS
- add one security check just to be sure
PS
- get one step further and put out the navigation ring config as well
  and reduce it to just one call.

Change-Id: Ica6116289d5bc50e9bedcd34b4b165062fa3468d
Frameworks: notify arrayadapter early that data has changed on clear all

Recent clear all. Current behaviour is that we do not update the array adapter at all
due that it gets rebuild on next reload. But in very rare cases it happens that getView
want to update shortly after all is cleared althought the view is not visible anymore.

Whatever just call notifyDataSetChanged after List is cleared to work against it.

Change-Id: I61ca25358ebe164336ba349565459537861c5495
Frameworks: do not kill favorite recent apps

Due of a lot user requests and I basically like the idea (not a fan of clear all apps at all
due that it does not make sense android wise) we ehance the favorite recent apps feature.

This commit basically does not remove the apps from the task list which were marked from the user
as favorite.

3 possibilities:

- No favorites are in the task list - clear all behaves like it was before - all tasks cleared and panel closes

- favorites and non favorites are in the task list - clear all removes all non favorite tasks and favorite tasks stay.
  Yes without fancy animations....we want to be fast ;) - panel stays open

- only favorites are in the list - pinch to zoom out is blocked due that nothing is there to clear all.

single clear of a task with swipe behaves in all cases normal like it was before this change

Change-Id: Ia05562e0f59dfb023aa65ec3a40dd951594dc88e
Frameworks: fix possible NPE + and missing expandable panel correction

Thanks Jorge for pointing it out. This version is way nicer.

Change-Id: I7a65a05ef533c90cbfc68d4de996eae7a0ff66b7
Fix LTE tile (1/2)

thanks CM for the final fix.

Change-Id: I229551f17f530dac900c2c5dd55263d96f36a277
Framework: Add Landscape layout for ECA

Maintainers!!!
Please test on your devices.
MAYBE google did this for a reason =P

PS2: Whitespace

Change-Id: I22829c6e5f8badf78336e5c14d3c507426da32b9
SlimPie: turn on HA on highEndGfx devices

for smoother experience

Change-Id: Ie2a052e1071a8ab7ea303b6a8d21e245658bec2b
Add support for QC's time_daemon

Enabled by BOARD_USES_QC_TIME_SERVICES=true, it requires the device
to provide its own time_daemon executable and libtime_genoff.so
proprietaries. The library should be copied by the device's setup
config to $OUT/obj/lib for linkage (and pushed to the final build,
obviously)

Change-Id: Ie6964dbe2692dc33fc04093a5b89b6922d8443c8
SystemUI: Remove broadcast from QH toggles

Obsolete per this patch:
	https://gerrit.slimroms.net/#/c/5814/2

PS2: Forgot one

Change-Id: Iaf591304a8993710920149a77d15d29b22514211
Frameworks: add a bunch of national roaming providers

Change-Id: I506bb2d50f8c0493e9f33ed45984627e60132399
Volumes in Settings/Sound is slow to start

There is a delay after pressing volume menu item
there is a delay until the Volume popup is shown.

The reason for this is that the initialization of
the different seekbars is slow and run in the main
thread. More specifically the call to get the
ringtone from the RingtoneManager is causing this
delay.

Moving the call to the ringtone manager to the
handler thread used to play ringtones to make
the launch of the volume dialog a bit snappier.

Change-Id: I76da0226592468debd542d67164b37b2b59897c7
Base: Check ProcessesReady before broadcast

Most of the time testIsSystemReady is used to know if we are allowed to broadcast intents.
But in broadcast intent method we check mProcessesReady flag (not mSystemReady).
If we broadcast after systemReady flag but before ProcessesReady flag, system will crash

Adding condition to check if system & processes are ready fix that race condition
Signed-off-by: Fabien DUVOUX <fabien.duvoux@gmail.com>

Change-Id: I2eec1c4f280daf29f4741919a7636b02da341e32
Don't confuse stat and stat64.

Bug: 11865851
Change-Id: I45e65036d86c58943b9c273777f3f8be79a6966f
Insufficient ProcessRecord cleanup when persistent process is killed

When persistent process with Service restarts, ActivityManagerService
does not reset ProcessRecord#hasClientActivites to false
(because ProcessRecord of persistent process is continued using
after killing).

It disturbs updating LRU list in ActivityManagerService, and then,
when new process calls ActivityManagerProxy#publishContentProviders,
SecurityException happens because of no entry in the list.

Bug: 13517358

Change-Id: I46b064f71a4f7025ade1bf117801352a7ab22e6a
AudioService: Fix absolute volume for AVRCP

Avrcp.java uses max volume obtained by getStreamMaxVolume() when
converting to AVRCP levels and it returns non-scaled volume index.
For this reason volume index needs to be dispatched to Avrcp before
scaling as otherwise Avrcp will convert volume level incorrectly,
i.e. max volume index for music stream is 15 and any volume index
>1 (>10 after scaling) will result in setting *MAXIMUM* volume level
on headset which is not safe for listener.

Change-Id: Ia799eec578ed2326ec18b69f2ee4f2a60c664514