Quick Settings: Use scaled font size (1/2)

Set the font size for quick settings tiles to match the design docs
for 'Text size micro'.

Change-Id: I83e8f7eae65d5f40dd7aeb2b663bc1fc3d5324d2
Nav bar 3 dots button fix. Now it's working again.

Change-Id: Id87c1ee4185e5e15657590c5f7a01062675672d3
Frameworks: Add new configuration qualifier for UI change on the fly (1/3)

last night I got an idea after 5 weeks of breaking stuff and
doing to much complicated things. Together with mnazim we tried
today to realize this idea. So another absolut new unique SlimBean
feature is born.

The aim we wanted at the end was to give a simple and resource friendly
way to change the complete UI of a rom on the fly. So why not use
the great fallback mechanism of AOSP and change/add a new
qualifier into the AOSP core. To explain how it works.....if you want
to add a new UI just add in /res folder of any app or framework you want
folders with the qualifier "inverted". Eg. drawable-inverted-xhdpi
or values-inverted or layout-port-inverted or whatever you want. Put in
only the files you want to modify thats it.

All qualifier in AOSP are following strict rules. You can read here.
Do not forget the order of qualifier is important. The new "inverted"
qualifier we added to the UIMode qualifier. To get more information
about read here

http://developer.android.com/guide/topics/resources/providing-resources.html

So what this commit does:

- add new qualifier "inverted"
- support for API level 13 and higher
- change the custom UI on the fly
- control default UI Mode over config.xml
- working for all apps. They just need to include folders
  with the new qualifier name
- resource friendly....no resource wasting either programmticaly
  then source blow, because you just need to put in the files you
  want to change
- cause of the qualifier structure compatible with every phone,
  language or whatever qualifier you want to use on top
- 100% compatible to theme manager. If a theme misses drawables
  they are replaced with them from the current UIMode which is set.

What is the benefit why not use just a theme? We started half year
ago TRDS which was inverted gapps system base themed....means we
morphed directly the changes into the framework. This methoed was
on of the reasons why trds got so popular. Points for that are easy
first the system is themed, means each theme you activate over
theme engine works on top the themed system. So you have a base
style and can modify more if you want. The other reason is easy
a lot faster and resource friendly. Now this idea went to the
rom to provide two core system based themes and user
can do on top what they want or not without, like you have
to roms in one.

This commit just adds the support for this

cheers

mnazim and kufikugel

Change-Id: I1ef843a42d17246373eb17b4e1ec1aa9bc20d8d4

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java

Conflicts:
	api/13.xml
	api/14.txt
	api/15.txt
	api/16.txt
	api/17.txt
	core/java/android/provider/Settings.java
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
Frameworks: TRDS goes Slim

add trds changed files to provide new UI mode engine

Change-Id: I67f8a26320c9971258eb0106c0574b5af9b4261c
Frameworks: TRDS new qualifier push up qualifier number (1/2)

Hey guys,

after this feature is working really well and a lot roms kanged
it we got a hint to change one thing which is indeed a good
idea to have less problems on AOSP updates and tools like
Apktool can provide us better without doing major changes every
AOSP update.

We pushed the number up to 69.....should be enough for
next years.

Please note for the one who are using our gapps at the moment
this will break actuall gapps till we published the new one
which will be end this week as usual.

After that we will begin to publish the apktool after we had
now enough tests....and who knows maybe the "official" Apktool
will provide us all now. So all in all a good time to change
the qualifier now before it is getting more and more
popular (we saw that first themes are providing us)

cheers

Lars

Change-Id: I7abcd87642050c4b43829ab77b20748692becd0e
Fix broken TRDS "multi-select" actionbar on hdpi devices

Change-Id: I0253ecc057e0e66174149694ff300de7c277b1b9
Frameworks: TRDS 2.0 (1/3)

After testing with huge success we discovered here
and there small problems (like NFC beam animation is broken,
TRDS was disabled on cardock etc) which mainly was caused
due that we used the already from AOSP introduced uiModes
qualifier which could cause in special conditions this
conflicts. Beside that we want a bit more flexibility.

Result: This commit introduces the inverted qualifier as
complete own qualifier undependent of the already AOSP
used ones.

Beside that it fixes all known issues......features:

- it is now completly working over the AOSP Configuration classes
  Means every app get notice of a change trough onConfiguratioChange
  and restarts it's activity if change was detected.
- app can disable that like some other configuration values
  over AndroidMainfest.xml
- beside "inverted" folder another "notinverted" folder is introduced
  for another themeing (eg white)
- qualifier order is direct before the official uiMode qualifiers
  (see AOSP docs)
- All usual Configuration actions can be used with the inverted
  qualifiers....like BroadcastChange, direct read out from every
  app etc. etc. Note: Only system can change the uiInvertedMode

So as you see a real own qualifier now

NOTE: Apktool as well aapt need to be changed to fit the "new
qualifier"....which means that we need to recompile our gapps
that they react as well on this new behaviour. Think we will get them ready
next 2 or 3 days.

Patchset:
increase support from SDK_HONEYCOMB_MR2
to FROYO to have better compatibillity
to some gapps.

Change-Id: I851740010198c400266d7ca9995eb08dbf7782bc

Conflicts:
	packages/SystemUI/src/com/android/systemui/recent/InterestingConfigChanges.java
	packages/SystemUI/src/com/android/systemui/statusbar/WidgetView.java
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java

Conflicts:
	api/10.xml
	api/11.xml
	api/12.xml
	api/13.xml
	api/14.txt
	api/15.txt
	api/16.txt
	api/17.txt
	api/8.xml
	api/9.xml
	core/java/android/content/res/Configuration.java
	core/java/android/provider/Settings.java
	core/res/res/values/config.xml
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
Fix missing variable in TRDS implementation

Change-Id: Iadf883a75965dc99487bb4399faa25669a59825e
Fix empty page being activated if music controls are disabled and music
is playing.

Change-Id: I76e00e4c58dc86ce0bf4e88c0e6be551950b6969
Bring back two-line layout for status bar date.

Change-Id: I4bf7ce61b22da89b3b8c1a3f00e077461061f7b9
Fix brightness dialog layout.

This reverts part of change I83e8f7eae65d5f40dd7aeb2b663bc1fc3d5324d2.

Change-Id: I1f685357776dcac9c93e592e274acdf0497f4161
Framework: Add Recents Ram Bar
Patchsets
 cleanup whitespace

Patchset 8:
- fixed gapp between recents apps and bottom
- add click action to running processes
- minor changes

cheers

Change-Id: Ib47c6fc3964fbe96bdc00c7294622ec30b5808d1
Framework: Recents RAM bar (1/2)
due that the old rambar was resource consuming and as the settings rambar not really
right in showing the truth of real RAM usage in android, I decided to go new ways.

This commit changes our rambar (or better add a total new one) in following points:

- we do not use any longer ther permanent observed RunningState machine
- instead we read out /proc/meminfo (thanks steven for that idea)
- rambar shows now the real memory usage
- ppl have the possibility to show applications, cache and other ram usage as they like
- deeper explanations I add how android mem managment works.
- color picker for all rambar states
- reset to default
- updates only on actions on recents so that it is making sense
- and a lot other

Inside as well:
Fix Ram Bar calculating
seem realy my fever last days made me to a bad programmer lol
fix for wrong calculated other value
fixes also sometimes weird negative views

Recents set nicer intent flags for rambar click action

---------------------------------------------------------

cheers

Conflicts:
	core/java/android/provider/Settings.java
	packages/SystemUI/res/values/strings.xml
	packages/SystemUI/src/com/android/systemui/recent/RecentsPanelView.java

Change-Id: I47451cf6fa451d6760e2d42fcb649b27397ccee4
Fixes in Ram bar implementation

Change-Id: I6968f03c2e80c55eb5aa6fd87f4667696106ec74
Move clear recents button to top|right

Change-Id: I893343bd45d8cad21a5910a99b8aad8f00c3c3ec
BroadcastReceiver : Get sender of broadcasts

Add internal api for receiving the sender of a broadcast

Change-Id: I28ae614ef92101ab6b9beadc3c965d16b1f393f6
Remove obsolete installd

installd is now in frameworks/native

Change-Id: I308b2dbfcc3103262b16d1680630ca744c1a0877
Merge "core: fix cpu variant board flag" into cm-10.2
Clean up lockscreen target configuration code (1/2)

Get rid of a lot of duplicated code.

Change-Id: I80fb0b0cd9b5f7d79a5760f8fa6ae338d9ca7205
Bluetooth: Disable bluetooth only if BT Sevice is connected

Bluetooth service is imidiately disconnected from the adapter
after SSR OR if any bluetooth services is crashed OR framework
is crashed. As Bluetooth  service is not connected OR Bluetooth
is not enabled, So BT disable should be ignored & bluetooth
persist setting should not be changed.

CRs-Fixed: 499116

Change-Id: I19de939346d014cdf918e11711f2d6066e55d054