The values reported by the kernel are not correct, so ignore them.
This reverts commit 019e9814b3.
Change-Id: I101fd1087a38f14b667a2e35a90a8562d45fd976
If ZSL is enabled, the HAL might automatically force a lower fps
(depending on the current resolution). This causes problems if the
normal fps range is not restored before changing configuration
(e.g. changing resolution, enabling HDR, switching to video mode).
When this happens, the sensor gets stuck at low fps, the preview
becomes dark and an invalid fps preview range might get selected,
leading to a crash. Disable ZSL to prevent all these issues.
Change-Id: I0b00dd65a1ff88547d39874ec1c60fb9263335f7
Using titan blobs didn't work well, so partially switch to L blobs.
This fixes the issues with the camera such as poor performance in
low light conditions and broken exposure settings.
Change-Id: Ic04d2c8db52fcf391a4cd677ea8a827488e6d790
Our radio don't support RIL_REQUEST_GET_RADIO_CAPABILITY thus
we can't select non "GSM only" mode on msim variants.
Change-Id: I9622cc78b53876d6e8d29f6809fffc81c9a1a6ec
Swapping out PRI_MI2S_TX_Voip for SLIM_0_TX_Voip was forgotten in
commit: 519a08ad3d14b0add5b6baf2e74cf9f630642b48.
Change-Id: I4df2b215042abb8f20bb6ab1836c8990cca7e6ee
(cherry picked from commit affd6bbb1a59b070c46586a55a29c9c4aae430b0)
vold now manages external storage in a much more dynamic fashion,
so we no longer need to define FUSE daemons or mount points.
Bug: 19993667
Change-Id: If1ff24c62ee394afb02e223508aa5d768a3d041e
* peregrine has an external storage, while falcon who also shares the common ramdisk in msm8226-common, does not
Change-Id: I9c962445821f6d22bdfbf93f5a8e9142e649d5ce
Signed-off-by: Brandon McAnsh <brandon.mcansh@gmail.com>
With the new version, there was a modification to the modem layout.
Users on the older bootloader would have non-functioning radio in this case. Another issue would be the display flickering.
Add assert to alert user to update his bootloader (motoboot.img)
Change-Id: I73588865646da3a962fd98309ff5710cbdee085c
Mark cache and userdata as formattable partitions, so that init/fs_mgr
format them during powerup if they are blank.
Change-Id: I6368a667d6535cf4258f616848a19ddc34a4fba6
Titan doesn't have akmd sensor so akmd daemon keeps starting and
that results in logcat spam & unnecessary memory/cpu usage.
Logcat:
I/AKMD2 (10705): AK8963 for Android v20111216(Library: v1.0.0.809)
started.
I/AKMD2 (10705): Debug: OFF
I/AKMD2 (10705): Debug level: 0
I/AKMD2 (10705): Output to: LOGD
E/AKMD2 (10705): AKD_InitDevice:54 open Error (No such file or directory).
I/AKMD2 (10705): AK8963/B for Android end (-2).
Change-Id: I1666e12905f7497eb317fa7e51f00468a2773488
Provide 16K for footer region of data partition
/data should have 16K data for the encryption footer.
In "fstab.qcom" we specify this by adding
"encryptable=footer" option for the /data parition.
However after factory reset these paritions will
be wiped out and mounted using the parition tables
mentioned in "recovery.fstab".
In this case the /data should again leave the 16K for
the encryption footer. So "length=-16384" needs to be
added for the /data parition for the encryption to
work after factory reset is done. Similarly BoardConfig
is changed for userdata partition by reducing it by
16kb.
Change-ID I188ee4ea959bb8eb791b9387fc6adf299ffdc498
Change-Id: I0d58b350e96f1c57190759e2cd8c71aec99efdf2
Gabriele M