| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
Change-Id: Ia85f5755acf9c88ac45f5ccf9dc9f49e5d130bd5
|
|
|
|
| |
* I don't know what I was thinking when I did this...
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Stock already do this: Better to finish all tasks and sleep soon
than to do everything in cpu0 and keep it active longer.
* Also, disable cpu1 could lead to system instability. See
sultanxda/android_kernel_oneplus_msm8996@8e35dcceaca5ecb4237bb1ea192ebbe01cc0d64a
|
| |
| |
| |
| |
| |
| |
| |
| | |
-dpmQmiMgr permissions are updated with radio group
to communicate with QMUXD socket.
CRs-Fixed: 2183993
Change-Id: I37195ffc6602d009ac4cace6c742484e70a768ec
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Added user and group tag for dpmQmiMgr
- Start the daemon with system privilege.
CRs-Fixed: 2080471
Change-Id: Id3a4a9f849d336e103c3c6897daf34465230b83a
|
| |
| |
| |
| |
| | |
* From ZUI 3.5.261 but keeping LineageOS/android_device_xiaomi_msm8996-common
work as reference.
|
| |
| |
| |
| |
| | |
Test: use usb
Change-Id: I4470ab479a49e04fdfec1969f31c72e221a3a3c5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This way the function can still connect even when the media
process has been killed for whatever reason.
Bug: 36801389
Bug: 34873000
Test: Connect mtp after process is killed
Change-Id: I7445a42d2fd0318d8f801d8ff73926c49acecf57
|
| |
| |
| |
| |
| |
| | |
Test: on device
Bug: 30976142
Change-Id: I51991bface547691f15b17db03d0d1fc1cdd0bb6
|
|/
|
|
|
|
|
|
|
|
| |
The patches to get ffs to work with multiple
functions expect the aliases to be written before
function mount in order to connect function instances
to mount instances.
Test: on device
Change-Id: I833adf451e870dd61327de6df16fc88eab29a188
|
|
|
|
| |
* We don't execute it.
|
|
|
|
|
|
|
|
| |
* Cleaner, and includes stuff from init.qcom.usb.sh without needing the script
msm8996-common: rootdir: Import back USB compositions from the old .rc
* Fixes ADB and MTP on z2_plus
|
| |
|
|
|
|
|
| |
* ext4 is the stock's default choice.
* f2fs support is highly dependent on which kernel you use.
|
|
|
|
|
|
|
|
|
|
| |
* Mounting /system and /vendor partitions is handled in kernel now,
however removing the entries from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
|
|
|
|
| |
* We don't ship blobs for them.
|
|
|
|
| |
Change-Id: I7e95baa01490ec76cf8ddfa051f01fc9b0bc5c7a
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Earlier, this used to be set from rmt_storage service with
sys_admin capability. But now, that capability is dropped
off and hence, set it here in init scripts.
Change-Id: Ie8a3895c2b63da35d78fb9e571d74b735c969520
|
|
|
|
|
|
|
|
|
|
|
|
| |
Grant capabilities and change file permissions to allow the sensors.qcom
daemon to start up as the system user/group, rather than running as
root.
Fixes: 63775281
Test: monitor logcat after reboot, confirm no file open errors. Run
QSensorTest, confirm all sensors provide sane data. Confirm that
IMU calibration can read + write its saved settings. Run sensors CTS.
Change-Id: Ib80ea21900d6af6cd34c82c4a63f50c7e0ac18ff
|
| |
|
|
|
|
|
|
|
|
| |
rmt_storage should not be automatically killed by Android during
shutdown since it is needed to actually process the peripheral
shutdown
Change-Id: I58a29fe86955f0abad944727bb4208dad89f495d
|
|
|
|
|
|
| |
* Dropped by Qualcomm in O.
Change-Id: Id1c6e9d475b59b41c0cc4e4633e2ce7faabd19ef
|
|
|
|
| |
* Disable on the kernel and we don't ship its blob.
|
|
|
|
|
|
|
|
| |
* This fixes these SELinux denials and it doesn't
break anything for now... :-P
avc: denied { create } for pid=1 comm=init name=firmware scontext=u:r:init:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir permissive=0
avc: denied { create } for pid=1 comm=init name=bt_firmware scontext=u:r:init:s0 tcontext=u:object_r:bt_firmware_file:s0 tclass=dir permissive=0
|
|
|
|
| |
* There is no init.target.rc or init.zuk.usb.rc
|
|
|
|
| |
* Qualcomm Wifi Direct, as far as I know, but we dont ship its blob.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* We need to set proper permissions earlier
otherwise users might be forced to reboot
as their sensors wouldn't work due to not
working sensors daemon.
Change-Id: Idbb5dd8a539a85c9b498e70b158569a2c9f37682
|
|
|
|
|
|
|
| |
Removing redundant creation and assignment of permission for
data/misc/bluetooth folder from init.qcom.rc file.
Change-Id: I941a53d01675b44fa6a5b59bcd2b72f9e6a11ab7
|
|
|
|
|
|
|
|
|
| |
These changes are to create folder to collect logs and
dump from Bluetooth HAL daemon.
CRs-Fixed: 2051034
Change-Id: Ib930a80aab1354ad1463a02febf71eba922e2df8
|
|
|
|
| |
Change-Id: I431fbcd9af56697dc0bc673b8c102579c208f620
|
|
|
|
|
|
|
|
|
| |
Modify permissions for /data/vendor/misc to 01771
from 0770 in order to enable audio module
to access the directory.
CRs-Fixed: 2074932
Change-Id: Ibc832cd0ec7c04a99b3fa1e9a554f919e11a149a
|
|
|
|
|
|
|
|
| |
Removing creation of /data/vendor with system
group access.
CRs-Fixed: 2055140
Change-Id: Ic9fb98ea1420769f2ffa5262fd6e1a82ad848941
|
|
|
|
|
|
| |
- for audio acdb and dump files create /data/vendor folder
Change-Id: If24a072d3686c3740ba36a3d6eb1849b4a769a3b
|
|
|
|
|
|
| |
* We mount /persist in fstab so this is useless.
Change-Id: I62cec54e22af6207114eca94c2c80275ece30443
|
|
|
|
| |
Change-Id: I910c9f574e842410e8a09c1c1d0d82be51d6026c
|
|
|
|
|
|
| |
This will enable quota feature for the data partition.
Change-Id: I45f54583d84a67c2097065a29fe67b1012dfcc12
|
|
|
|
|
|
|
| |
* Current code expects lenght to be the real partition size
> The footer is automatically added now
Change-Id: I47165062ae0b15c935c8b1c561b9788ff825c4f5
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Turn the partition /factory into something more
useful for us.
Change-Id: I32a3088ef7803d3db691b9031dda2dbe55565ba3
|