Age | Commit message (Collapse) | Author |
|
* This config needs to be modified for legacy devices. As
there is no easy way to split it, import it into device
tree and bind mount it instead.
* Head at android-10.0.0_r2
(3ac371484399da6efbd0c835aa461d3326263ab1).
Change-Id: I8d5003d7cd3a471c569844aede4b5ea4c68ae36b
|
|
Change-Id: Ic434c18314838f845bcdca5e029a127db0500070
|
|
Change-Id: I3b5206f44fbe29a90f43e0bdda48b4bd26435fb2
|
|
Change-Id: Ic72c75a4efe964758b29e71bc4263ce1b191493d
|
|
Change-Id: I849c429d6b1fd57d6593f4b9a6152f31477c71a0
|
|
Change-Id: I13e6a6523f1ce6aec0a0ddce491cd90c54635f85
|
|
Change-Id: I5ae7f5db25bd44b64a014cb1cefc40065851ac43
|
|
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as its a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
Add CAP_SYS_BOOT capability for charger service so that it can
shutdown/reboot the system.
Change-Id: I17ccba74d5a3c38bd751c55bcf42fb3689d730a7
|
|
Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
|
|
charger binary is moved to /system/bin. Also the label got changed
to charger. Update it accordingly.
Change-Id: I78574238f9fc5ec028d10ab866676bfc0cd36370
|
|
Change-Id: Ia6f2ce370430e7329c5354cb16a84947e99e2542
|
|
Change-Id: Ifb8bb7161a04f17f93922d4df80fc50cb348d72c
|
|
Change-Id: Icdfdac046bc0bfc0ced4a2c1846579322f606153
|
|
Change-Id: I09d42c051f400840db25dcb558dc26e51bff554c
|
|
Disable backlight when blanked out.
Ref: CRACKLING-626
Change-Id: Ifc698c1470b086b0e1f083c3c234f272988d108c
|
|
* Otherwise adb will try to start and crash the device
while offmode charging at a computer.
Change-Id: I4752de69b765c4528cedf0ce58092a882bc584a3
|
|
Change-Id: I95d5f00b45c456f76b2adb3079144e8118b3ce69
|
|
Change-Id: I9db1bd8795e62f5f7cc60ea1f801b903e824d078
|
|
Change-Id: I1b2ac64116c056000bf482a613b0a4904f73b1ae
|
|
Change-Id: Ie3fe0d32000e03c56cd6a5998c81ce8cef84af10
|
|
Change-Id: I85db3526042ec91ba51ef82be5a666631a002457
|
|
Solves the following denial.
denied { write } for pid=548 comm="init" name="storage" dev="rootfs" ino=15996 scontext=u:r:vendor_init:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
Change-Id: If246f497bd8384f0fee81469d8d29dcb528d4d4e
|
|
* The core SELinux policies for vendor_init are being restricted as to
comply with Treble. Simply adding a local rule to allow creating
folders under rootfs would be enough, but at the same time defining
the extra root folders and making use of AID/fs configuration file
to set perms is more neat and clean.
* Furthermore, with System As Root / is a read-only filesystem
so we can't create our mountpoints from init script anymore
Change-Id: Idabd7ae72e4c4fd9daac5ba3be3e6236f79f251b
|
|
Change-Id: If3761cc54f925ce7646eee95f65b0d0aa8017554
|
|
Change-Id: I5056d8f1d3d33d72abeb0129ddfe3929e18163c2
|
|
This reverts commit 398f6cc16d50754a0d5b6bc1a7235c5766c076b6.
|
|
* Glove mode should be set from the touch HAL
* Move TFA9890 AMP and Double tap to wake to init.qcom.rc
|
|
|
|
This reverts commit 7c6eeb92c503a0da01d48ce3b61fa689e16ba390.
|
|
* Move qcamerasvr to main to it restarts on decryption
* Also trigger a qcamerasvr restart when media or all services restart,
since it needs to be properly restarted with cameraservice
Change-Id: I2361c5658359ed9f2fe937a0bd3329ca9c00e66e
|
|
* Remove entries created by init.rc
* Remove obsolete & unused entries
* Remove useless chmod when proper perms are set by mkdir
Change-Id: Ifb1a2d8c915de13438393e5a0cac7706d7decd7a
|
|
To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
|
|
Change permissions of AMR-NB device node and change owner
and group of AMR-WB node to fix failure in opening of these
nodes from OMX component.
CRs-Fixed: 2072938
Change-Id: I5508529726ce0a3b763ac1364960def32887c6a2
|
|
rmt_storage should not be automatically killed by Android during
shutdown since it is needed to actually process the peripheral
shutdown
Change-Id: I58a29fe86955f0abad944727bb4208dad89f495d
|
|
* Remove them all.
Change-Id: Iaabd720bbdd0d7120a1ac7c05ecb13e389bf74e4
|
|
|
|
* Match the new changes introduced in O
* Important sidenote: if the kernel doesn't support one of the capabilities,
that's enough for the whole capability set to fail for that particular
service. Previous to adding the full support for these capabilities into
the kernel, the following was printed in the dmesg:
init: init.variant.rc: 5: capability 'BLOCK_SUSPEND' not supported by the kernel
While checking rild's capabilities (`cat /proc/$$/status`, where $$ is the PID),
it could be seen that those were totally messed up:
Name: rild
...
Uid: 1001 1001 1001 1001
Gid: 1001 1001 1001 1001
...
Groups: 1005 1007 2001 2901 3003 3009 3010 9998
...
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: ffffffffffffffff
CapAmb: 0000000000000000
...
After adding CAP_BLOCK_SUSPEND support to the kernel, it changed to:
Name: rild
...
Uid: 1001 1001 1001 1001
Gid: 1001 1001 1001 1001
...
Groups: 1005 1007 2001 2901 3003 3009 3010 9998
...
CapInh: 0000001000003000
CapPrm: 0000001000003000
CapEff: 0000001000003000
CapBnd: fffffff000003000
CapAmb: 0000001000003000
...
In this particular case, messed up capabilities resulted in broken
mobile data.
Change-Id: I8e5888ebeb4bcf26eed85a2c4dca320faad8f7e0
|
|
The /vendor symlink is available as soon as /system
is mounted, just use /vendor.
Change-Id: I2e92ed2abe225f1366cac418b13763bb5617f704
|
|
The reason these files are moved to /vendor/etc/init/hw and
not /vendor/etc/init is because 'init' scans the /vendor/etc/init folder
for vendor service .rc fragments to import. That would either result
in duplicate imports or out-of-order imports of these hardware
specific .rc files and that *may* have unintended consequences.
In order to preserve the current import order for MTP, we move all
hardware specific .rc files to /vendor/etc/init/hw which is not
autoscanned by init BUT leave the init.${ro.hardware}.rc (i.e.
init.qcom.rc in this case) in root for 'init' to find.
Change-Id: I14531da05e2a3a256f734f8de96e1f1969c753f9
|
|
Change-Id: I460888519e447da8ab3800d62d60c5600b902da1
|
|
* Allows mpdecision to work properly on boot to restore selected power profile
Change-Id: Ib92f971f28ed875481170b056ac16aad05aadcfc
Signed-off-by: Arian <arian.kulmer@web.de>
|
|
* revert e80a06f8c2632df3036818685ac2bf9fc06556b2
* don't enable adb from here
|
|
|
|
|
|
|