Age | Commit message (Collapse) | Author |
|
Change-Id: I9f225f027bd8bf36ab6324fb5eddaeb866f4803f
|
|
This help to save ~50ms in boot time and bootanim shown time
Bug: 62957152
Test: marlin boot and swap look normal after boot
Change-Id: Icabec31aa677bd606ca8735fe9d2acb54e88bd75
|
|
* Set page-cluster to 0 as the incremental cost of reading 1 page at a
time is negligible for zram
Change-Id: Ia73d08904551dfc8d57268fc4da3f9f34d10e277
|
|
* suntrold is a oneshot service and spawns a subprocess which is required
for the rear camera. Since [1] oneshot services' process groups are
killed which prevents suntrold from working correctly.
* To work this issue around create a non-oneshot service, suntrold.sh, which
never exits, so that suntrold can be started from it and it's subprocesses
will not be killed.
[1] https://github.com/aosp-mirror/platform_system_core/commit/d89ed132a0ee1a57046286b83e64a35b71774952
[Idea of this is from LuK1337]
Co-authored-by: LuK1337 <priv.luk@gmail.com>
Change-Id: Id9c4f56648168f0ffe19b2bb31c591750afe6f97
|
|
Bug: 138790309
Test: boot and wifi function is ok
Change-Id: I35cf3e03566443e20799623045eacd423fd7f5c4
|
|
On hard resets the sensors daemon starts before the decryption is
done causing sensors to not work until a soft reset.
Move sensors to class main to avoid this issue.
Change-Id: Ibb123c40ab22a8d9bb956072597bd8f71edd57a2
|
|
This reverts commit a188d6267d2ee4e10ccf7b28e13d85493fbaebec.
Change-Id: Id5f6115f4f8a1f47a23f24f61b3e7a7314735a2b
|
|
Change-Id: If615758376413b16fcc80addd03a9ba5cd388e8a
|
|
* Sensors service is failing after fmwk restart on encrypted
devices.
* Moving it to main make it fail on each fmwk restart because it start
too early and storage is not fully avaiable.
* So place it late_start to ensure encrypted devices are fully working.
Change-Id: Ic2af7967478b3860d7028ea61d55912334bfad13
Signed-off-by: nailyk-fr <nailyk_git@nailyk.fr>
|
|
* This is unused since we use the stock Audio HAL
Change-Id: I05c9a6119f55f4ba2550a4b336eb6a61350a7f1d
|
|
* Just bind mount gps.conf to gps_debug.conf
We can't directly build gps_debug.conf because it's a common target
and we're not allowed to override targets anymore.
Change-Id: Ia3c96665b50b0fe478e44186d1c65be723acbf5a
|
|
* 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
|
|
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: Icdfdac046bc0bfc0ced4a2c1846579322f606153
|
|
Disable backlight when blanked out.
Ref: CRACKLING-626
Change-Id: Ifc698c1470b086b0e1f083c3c234f272988d108c
|
|
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
|
|
Change-Id: If3761cc54f925ce7646eee95f65b0d0aa8017554
|
|
Change-Id: I5056d8f1d3d33d72abeb0129ddfe3929e18163c2
|
|
* 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.
|
|
* Remove entries created by init.rc
* Remove obsolete & unused entries
* Remove useless chmod when proper perms are set by mkdir
Change-Id: Ifb1a2d8c915de13438393e5a0cac7706d7decd7a
|
|
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
|
|
|