* starting rtpd on bootup without waiting for DATA_DAEMON
prop and restarting when property is set
Change-Id: If121089334ef2c0b335320bb561a553163042ba3
Starting imsrcsd on bootup without waiting for DATAD property
which will load libimsrcsbaseimpl and register HAL services
Change-Id: I17c1891583ea99baa31efec0e8ba316e4fbf25f3
hvdcp_opti daemon stores some parameters in
/mnt/vendor/persist/hvdcp_opti directory. Create the directory.
Change-Id: I0cf17467792cc294e6ce1a7f35a356cc0e960e86
Explicitly specify firmware image files legacy /firmware/image/*
as system:system and new /vendor/firmware_mnt/image/* as root:system
For normal boot, this is a no-op as /firmware|/vendor/firmware_mnt
is a mount point. This change is only for development when
firmware is read-writable and allows changes via "adb push". This
match the underlying FAT fs mount ownership of system:system or
root:system so adb push's chown will not error out.
Change-Id: I90e7528bcd21cca449cc5637d20af8dc9ccf7d3c
Change fstab to mount dsp and firmware to /vendor/dsp and
/vendor/firmware_mnt.
Add classpath for firmware loading /vendor/firmware_mnt/image in
kernel command line.
Change-Id: I2dd2e7ea6334fb979ad8ff8c755648748de93ab4
Start loc_launcher as gps user and set uid/gid of loc_launcher
to gps and enable SETUID and SETGID caps for loc_launcher, so
that we can start loc_launcher as gps user instead of root and
still have capabilities for SETUID and SETGID. Also remove not
required permissions groups for loc_launcher.
Change-Id: Ie9f1506874b3c3148f9170c8d5db9afd1e70025c
CRs-Fixed: 2192881
To support ODL to read data from QDSS, create a custom group
and set permission of byte-cntr device. And also set
permission to coresight-tmc-etr/block_size to enable
byte-cntr feature.
Change-Id: Ic80156667dd7511392d5970ddcbd0fdc43ffffca
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
Changing permission for IOP from 0770 to 0700. This is to restrict the
access for iop database file.
Change-Id: Ic3325595521d4e433d0ce9bada564fc599cf858c
Move persist entry to fstab and mount at /mnt/vendor/persist
Apply required user, group and permissions once persist
folder is created through __mount and parititon is mounted.
Run restorecon on /mnt/vendor/persist.
Change-Id: I20a16f3669bc7abf9844525c6ba0db1521a5a8e2
New name is config_dozeAfterScreenOffByDefault
Bug: 73178121
Change-Id: Icf2123d45b2b4727092103632d1bd6f024161c8a
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
As stated in https://android.googlesource.com/platform/build/+/418258c
this is required in O-MR1 since sepolicy now prevents system server from
loading anything from /data making our system extremely slow and janky.
Change-Id: I215ec7ebe95981ef0b953fe938e12b83675795ab
* Otherwise, it resulted in Doze service not being activated
when enabling one of the features for the first time after
a clean installation.
Change-Id: I625d9109fb85c970f0e59b1cbcabba7d4375d2f3
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
* To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in go/treble-sysprop-compatibility documents.
Test: succeeded building and tested on a sailfish device.
Bug: 36796459
Change-Id: I48e6ee0ae3fe401e39efb273256d991fac676357
This sets below flag to true:
config_wifi_softap_acs_supported
config_wifi_softap_ieee80211ac_supported
Change-Id: Ie8192caaabfea2853f8f7e9a3644be836bba37ab
CRs-Fixed: 2244800
Required because the lights need to be turned off late in boot
(e.x. during fsck for disk health), and before, blank_screen
accessing light encountered a race condition where if it didn't
get scheduled before all of the processes which were getting
shutdown were getting killed, the screen wouldn't blank.
Bug: 74976325
Test: adjusting brightness continues to work
Test: screen blanks during shutdown at the correct time
including when an artificial 5s delay is inserted when
the phone normally fscks (which can also be quick)
Change-Id: I57ebc11d7ecf57ee327c681455712f4b53de6fd3
