Update cm_strings.xml
(cherry picked from commit 692a9a8aef31d24d168a26f7b38abc5bc722cdbf)
Update cr_strings.xml
(cherry picked from commit 678980313d27cd023cba3867165ffe8c268e6c8d)
Update cr_strings.xml

v94 update, corrections
(cherry picked from commit ea86a38bfa78d5e2e778c8087f3c31761ce2d562)
Fix listview animations

(cherry picked from commit 5ccdedf1ee35bab6e776192a1e86f3ef23c8ed44)
make seconds clock dependent on status bar clock

Change-Id: Ifa1104d429e5f209c5bd2bb96f3d80b7b6257a23
(cherry picked from commit 150b64c7ca648cbe4bab98b7c1eb46e844c227aa)
Settings: Add MCPS Switch

Change-Id: I4553c23850a681a56de03efdf32f18253f2dbc20
(cherry picked from commit 9eeeddd0558f44f73edbfd795238a7b297c098d1)
[2/2] OmniGears: Add unlock icons for Gmail and Snapchat

Change-Id: I8e7ac95be9e523477d3f05397374b265179f003e
(cherry picked from commit 03d3cb35e55912e31a3afdc698b88689e678c361)
settings: performance: Update get current values in Processor view

Some users have been complaining about min/max frequency being
set incorrectly on some CM builds.

One way that they could be seeing this is by using the Processor
Performance information in Settings which seems to load the values
for min/max frequency and governor once and then never reloads
them unless you change the actual setting.

This is easy to see by changing the values yourself by modifying
the /sys files directly.

With this commit, changing the /sys files will cause the
Performance view to show the correct values, not the cache values.

Change-Id: I96719e4f40081cb8d2c9b1fd63a32332823cf77d
(cherry picked from commit 22b79bd236faa9e0e66147b4f44d1f89bdde2eba)