HW FDE keys would be tied to keymaster so that if someone changes
Root of Trust (ROT), encrypted data can't be used. Cryptfs_hw module
is exposing a new API so that caller can determine whether to create
dependency between HW FDE keys and keymaster.
Change-Id: I85c85ffd9086f6c060032e4ae701b10363d88529
The 3rd launcher app may have same permission with launcher2, it will
lead the packagemanager throw the exception and can't install successful.
remove the launcher2, use trebuchet as default launcher.
Change-Id: I9a7291b2cacced50be58285fedfc8d63521b02c3
CRs-fixed: 885109
678eb850ea ("common: find dtb files in qcom subdirectories when
generating dt.img") failed to take into account that order matters
in the possible_dtb_dirs list of directories. More specific paths
must be listed first, since the first path that exists will be used.
Fix this by re-ordering the list so that the entries with
'/dts/qcom/' come before those that don't.
Change-Id: I82e948c0a20605f051a60fdfaae9679e1fa6555e
Modem interface is using serial transport as char_bridge. Due to using
"cdev" as serial transport name with DPL based composition, DPL based
composition switch is failing. Hence fix this issue by using
"char_bridge" as serial transport name.
Change-Id: I092df985f8f5302d0f5c4299cd2dbdc5e5b3dd1c
Fix CTS failure(UsbDebuggingTest).The test expects
the property value set to 1 for secure
adb debugging.
Change-Id: I801fc2986975ddb262b8ac133370d54dca45a050
CRs-Fixed: 829570
This is needed to match the new convention in the msm-3.18 kernel.
The old search paths are left intact for backward-compatibility.
Change-Id: Iba7fd603df33e3dee44a3d1ff0fd5bd120a60ed4
Because of an open file on /data by this module,
encryption was failing as /data unmounting failed,
so changing this to main class to make encryption successful
Change-Id: I52a1f0f8abb51234f54be0ddbcc4016df52c466e
To store subsystem ramdumps on persistent storage, /data/ramdump
folder is created on persist.sys.ssr.enable_ramdumps property set
Change-Id: I9aba35e09656c36f1056fc2255f75e094916fafa
CRs-Fixed: 838055
LK now requires recovery image to be signed. This
is a new change to ensure that only signed images
are used
Change-Id: I25fef9c311370e3f26d2d09b577575cd2a16f880
On an encrypted device, mkdir in /data partition must be moved from
"boot" trigger to "post-fs-data" as the /data partition is remouned
after giving passkey by the user. Hence some folders are not created
as they were created already on boot but could not be found after
remounting the /data partition. Consequently some functionality broken
Change-Id: I25e6c208d4cc036b34f818c683a3219d3431d67a
There is a dependency in the display HAL where a flag(VENUS_COLOR_FORMAT)
is only defined for boards in the video target list. Without this flag
compilation of the display HAL fails.
Change-Id: I280199777b2b688f965194c9772429e3d7cca533
On encrypted device init.qcom.class_core.sh script is unable to write
fake_batt_capacity to /sys/class/power_supply/battery/capacity file
due to unknown reason. Moving this logic to init.class_main.sh script
is working fine
Change-Id: I4c7cc7893314302f4749628d57343be1903e7e1c
There is a race observed between ffs_func_bind() and ffs_ep0_open()
while doing composition switch from any composition which supports adb
to any other adb supporting composition.
Below are the steps executed on switching to rndis,none,adb composition:
1. On doing stop adbd ffs_ep0_release is called which releases all the
descriptors.
2. Write 0 to /sys/class/android_usb/android0/enable which calls unbind of
all functions of the existing composition.
3. Write 1 to /sys/class/android_usb/android0/enable which calls bind of
rndis and ffs function drivers.
4. start adbd which calls ffs_ep0_open().
bind of rndis function driver completes successfully.
Below is the race observed where ffs_do_functionfs_bind() returns -ENODEV
since the descriptors are not ready, due to ffs_ep0_open() called after
bind call and hence the descriptors are not ready.
enable_store ffs_ep0_open
| |
android_enable ffs_ep0_write
| |
android_bind_config __ffs_data_got_descs
| |
android_bind_enabled_functions ffs_ep0_write
| |
ffs_function_bind_config __ffs_data_got_strings
| |
usb_add_function ffs_epfiles_create
| |
ffs_func_bind ffs_ready
| (descriptors are ready)
ffs_do_functionfs_bind
(check if descriptors are
ready)
|
functionfs_bind
stop adbd releases the descriptors and then again start adbd in the
same composition switch, rewrites these descriptors.
adb daemon is always running, even when the composition does not support
adb. So doing a stop/start of the adb daemon is not needed. Hence, fix this
issue by not doing stop adbd in all compositions which support adb.
Change-Id: Ib65b3f99eaa136f6cd10c64bc37e0951f6a0567c
1)Config determines whether to update phone object
when voice registration state changes.
2)Voice radio tech change will always trigger an
update of phone object irrespective of this config.
Change-Id: Id6fc26a8665cfda744cae7ffab1a8670664df71f
CRs-Fixed: 764153
Add org.codeaurora.camera package to LOCOL_MODULES.
It helps us to build org.codeaurora.camera.jar file.
Change-Id: I727fc8c2c14b7bd50d8aa87d7d5df43c9926b805