CHANGELOG FOR V9
FIXED - Google backup account missing bug in "Backup & reset"
smdk4412-common: [libhealthd] Proper battery paths
* 4.4 introduces a new daemon, healthd, that handles battery status
- resides in: /system/core/healthd
- BatteryMonitor.cpp iterates through all the *directories* under
/sys/class/power_supply looking for a file called 'type'
- if the type == Battery, it assumes this is the location for the
battery stats for the device. Only the first directory that matches
this criteria is used.
- on msm8660/d2/jf/s2 kernels, this search results in:
/sys/class/power_supply/fuelgauge.
- To determine capacity, healthd looks at the contents of the
'capacity' file under this discovered base path. This results
in /sys/class/power_supply/fuelgauge/capacity on msm8660/d2/jf/s2
kernels.
- Unfortunately, this is the wrong path. The capacity file at this
location returns a large negative number.
- Other paths like status, voltage_now, and present are also
incorrectly determined.
* For comparison, in 4.3 battery statistics gathering was handled by
frameworks/base/services/jni/com_android_server_BatteryService.cpp
- BatteryService does a similar search for a file called 'type' with
the contents of 'Battery'
- But the search logic is different here: it takes the *last* path that
matches the criteria.
- This results in the correct /sys/class/power_supply/battery
* This patch overrides the discovery mechanism for battery status completely.
smdk4412-common: [media_codecs] google vpx decoder 4.4 compatible
smdk4412-common: camera: fix EXIF attributes for S5C73M3 sensor - dhiru1602
- Ported from cm-10.2
- S5C73M3 sensor which is the back camera, doesn't return the EXIF attributes using V4L2 IOCTL. This sensor interleaves YUV and JPEG frames along with Metadata which contains the EXIF information.
- This patch does the following: Manually extract the EXIF information from the interleaved metadata and implement ISO, Flash, Exposure, Exposure Time and Exposure Bias EXIF attributes for S5C73M3. Fix incorrect Exposure EXIF attribute that was reporting as 1'.
vold: pass selinux context to ext4 mount (remount ro)
Add "Enable quick unlock"
- Automatically unlock the lockscreen when the correct pin/password is keyed.
fb: allow navring to show without assisten application - SlimROM
- this commit adresses two problems
- If the user does not install google now eg the navring does not show up anymore even when other targets are assigned. Due that we moved the disable/enable controll completley into searchpanelview which calls DelegateHelper to disable it we just can remove the check here in BaseStatusbar
- 2. On camera widget the navring is disabled and gets enabled afterwards. This is of course a problem if we do not have targets assigned at all. To fix it check for existend targets on the navigation ring.
fb: cleanup and let the navring stay and not dismiss on targetchange....user seems to like it more this way. - SlimROM
Add "Kill app back button" to dev options
- This is for hardware back key
Dialer: Update Icons to KitKat
Updated cm source - lots of it. Help yourself and read it in cm gerrit.
