smdk4412-common: camera: properly enable touch to focus mode

Touch to focus is not properly enforced unless the focus mode
is set to FOCUS_MODE_TOUCH.

https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/blob/cm-11.0/drivers/media/video/s5c73m3.c#L1857

Change-Id: I67236ae7ae687fbc0b7450102d744472a81def99
Merge "smdk4412-common: camera: properly enable touch to focus mode" into cm-11.0
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.

Change-Id: I4579c92bba5596eef4dac67b8c0687be50a1d2f5
smdk4412-common: camera: Don't set focus to FOCUS_MODE_TOUCH after taking a picture

After picture has been taken in stock camera app, FocusAreas is resetted to the center
of the preview screen, causing the HAL to detect the non (0,0,0,0,0) as a tap in the
screen.

Change-Id: Id41d108c6bb59a05a0a98efbaef51d14f50741fd
Merge remote-tracking branch 'cm/cm-11.0' into HEAD