base: EL translations

Change-Id: Ie904f785ba0aac356369a47a723573d23fd50ccc
Keyguard: RU translation

Change-Id: Ia746d3f8166b768a45cc3a4285f8073b1969399d

Conflicts:

	packages/Keyguard/res/values-ru/strings.xml
base: LT translations

Minor fixes
PS: 8. Keyguard translated, changed quotation marks to match AOSP strings, improved translations, minor fixes
*Fixed quatation marks
*Improved translations
Change-Id: Ib5051ed5787ecf096a3a39b70ef5450cb3c96d5b
SystemUI: AF Translations

Change-Id: I2e641bb6d8ac4550adc2631193602128c315855c
MediaFocusControl: Deny audio focus if notification stream is 0

Previously audio focus would be granted regardless of notification
volume, meaning that if notifications are muted the media stream would
still be dimished for focus. By checking if STREAM_NOTIFICATION is 0 and
if a notification stream is requesting focus, this is no longer an issue.

Change-Id: Ie10a64e58ce77174a3bbdeaa936646d40c24404f
Signed-off-by: Evan Anderson <evan1124@gmail.com>
Set Settings.Global.WIFI_SCAN_ALWAYS_AVAILABLE default value

To be able to customize the "WiFi scan always available"
setting we need to set a default value.

Change-Id: I3673f2613ab9b6a947aed7e29d4cc876140c2180
fb: finally fix carrier lable shows on first boot sometimes

Issue:
- boot up
- directly open via fast QS pulldown QS
- sometimes carrier label is shown

Expected behaviour: should not show

Fix: Visibility is directly set when the settings observer is registered first time.
If no update was done on the carrier label before the user pulled QS down the first time
it showed up. Vary rare case that this can happen
but should be handled. To fix it do not set the visibility directly and call the
updateCarrierAndWifiLabelVisibility(boolean) method to handle the correct visibility.

As well last cleanup on notification shorcuts...move the check if it is
active or not to the visbility method itself. Way cleaner

And remove the previous attempt to fix the above described issue due
it did not fix it at all

Change-Id: I901beb987c21fe0cdb7a5d9f16f850f4297c15f4

Patchset: 7
https://gerrit.slimroms.net/#/c/2435/
Revert "Update TRDS with google UI changes for 4.4"

This reverts commit 618234c53dca4356efa6ce1acf00a3b0d471742e.
Revert "Frameworks: TRDS goes Slim"

This reverts commit 1eab574edd568c85927c4423d70f2574d26a680d.
fb: TRDS 3.0 and new theme engine preparation (1/4)

For the one who do not know this feature see as reference
the first two versions here:

https://github.com/SlimRoms/frameworks_base/commit/b330fde28306286572ba390e451a72539c0c3576

https://github.com/SlimRoms/frameworks_base/commit/3194015737b7944b4185fca007b8d167a0675cd8

we got now over a year now a lot experience how to handle the qualifier fallback
as well how to theme it and how to handle other apps. Based on this knowledge we
redid some parts of TRDS engine with following new features/additions and fixes
to have now a final perfect working TRDS

- compared to the old versions where it was needed on some apps to restart them
  in background this is not needed any more. All is handled about the internal
  AOSP resource handling and on qualifier change the caches are cleared
  and the apps get an onconfigurationchanged to restart the activity
  like it is doing on orientation change eg
- inverted folder is now depreciated and the new folders are holodark
  and hololight which allows on the one hand a dark theme (at least
  how TRDS started) and a light based theme hololight
- This name change is mainly because of the new theme engine which
  will come which uses this as base to add 2 external themes at the same
  time and give the user the ability to switch between them. But this is
  still in early stages and this commit is just the preparation for it
- Two new automodes are now integrated. User can enable the twilight modus
  which enables/disables holodark/hololight depending on the daytime...means
  on the evening it switches to holodark on normal day it is hololight.
  The other automode is based on light conditions....means that if it is
  dark outside it switches to holodark....if we have bright light conditions
  it switches immediatelly to hololight. Due of the resource cache handling now
  this happens immediatelly for the user and feels completly system integrated
  and happens without delay. A bit comparable to some navigation tool for cars
  which can switch automatically from dark to light and back
- currently the auto modes as well the manual mode switches between holodark
  and hololight. Due that we do not have currently anything hololight themed
  in the source hololight = stock theme. We will give the user the ability
  later when done to choose between which modes the user want to switch
  (stock/holodark/hololight). But this does not make sense at the moment.
  As soon as we have done the light theme or theme engine (lets see what
  comes first) we will open the ability to choose it. This is only a small code change
- a lot small tweaks and fixes went as well into the new version

Whatever this commit as usual adds the support for it. The themeing is done in the
other commits by kroz which is as well way more extended then on the older versions

cheers

PatchSets:
- minor code cleanup

PatchSet5:
- use one value for auto modes

PatchSet6:
- kill resource caches on configuration change

PatchSet7:
- register settings observer lol

PatchSet8:
- fix not assigment of config mode change (typo lol)

PatchsSet 9 -11:
- playing around aosp qualifier is not that flexible then I thought
whatever back in most parts to original implementation handling

PatchSet 12:
- now no restarts of any application needed any more like it was on 4.3...yeaaah
- fix wrong shifting in native adapter
- fix wrong call of twilightmode
- disable debug
- cleanup

PatchSet 13:
- fix lightsensor

Patchset 14:
- no need currently to recreate the navbar we can do if a theme needs it

Patchset 16:
- synchronize on sending config change
- only send if system is ready
- fire first update when system is ready

-rebase

Change-Id: I12f0900090f1ec3ed002d63d4260a8080aec077e

Conflicts:

	core/res/res/values/pac_symbols.xml
	packages/SystemUI/src/com/android/systemui/DockBatteryMeterView.java
	packages/SystemUI/src/com/android/systemui/quicksettings/UserTile.java
QS: add theme switcher tile (TRDS) 1/2

this adds a theme switcher tile

normal click: turn on/off dark/light theme
longpress: switch between the auto modes (manual/light sensor/twilight)

Change-Id: I62b8e11b5714c179ccbf1c1e341b47c84da0fb56

Conflicts:

	core/java/com/android/internal/util/temasek/QSConstants.java
	packages/SystemUI/res/values/cr_strings.xml
	packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java
fb: TRDS dark base theme

Change-Id: Ie25abfbf5258ac479ca8bc91033f6892bbbc6741
trds:[framework] dark images adjustments

Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
fb: lock statusbar recreation and release after ticker is done

In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead

Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7

Conflicts:

	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
TRDS: Dark DocumentsUI

for Downloads app

PS:
- fix settings

Change-Id: I87d49e97b8a0a67bd4d85f0137eb0960155428cb
fb: add theme switch (TRDS) to navbar and navring

and show toast if a mode is running wich does not support
lightsensors

- rebase

Change-Id: Ie89589e1e0343e734728f0db00171a4e137370bb

Conflicts:

	core/res/res/values/slim_strings.xml
	core/res/res/values/slim_symbols.xml
fb: TRDS some tweaks and fixes (1/2)

some smaller issues fixed and optimizations:

- fix twilightmode was wrong assigned to wrong value
- ligtsensor mode after first immediattely switch it does
  not allow for 5sec to switch again....after the 5sec it switches
  to current state if the sensor changed its state in this time.
  This prevends on the one hand on bad light conditions a permanent
  switch between dark/light as well it does not bring the system into
  troubles due of to much configuration changes at the same time
- get rid completly of the observe for the UI_THEME_MODE value and
  handle all over the UIModeManager
- adapt slimActions and settings to this new behaviour/method
- some cleanup and minor fixes

Change-Id: I4b2401bf7bef992ad3112ae5ccc852cd29b46bd0

Conflicts:

	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
trds: improve dialogs and menu popups

Change-Id: I54da4ac0236dfe16ee964ccb070944206d0544e2
trds: consistent glow for menu dropdown and popup

Change-Id: I248872cbd67471495f8b95036d995f25e2ca4459
Fix build