| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
| |
Bug: 36409349
Signed off by: Nolen Johnson <johnsonnolen@gmail.com>
Change-Id: I1df0bd7878c7d67d3695ad1644c6b928cee0e323
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
|
|
|
|
|
| |
Test: builds and boots
Bug: 35173320
Change-Id: I9f060904174103a6a145a83cbb4c100728ff6df6
|
|
|
|
|
|
|
|
|
| |
Bug: 30118894
Signed off by: Nolen Johnson <johnsonnolen@gmail.com>
Change-Id: If84764e3ce51f467b2dfa867ce28e1e396422d45
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Changes the prefix of mbn_copy_completed to ro.vendor.ril
as there a permission error with current prefix. and due
to this MBN OTA is failed.
Change-Id: I31a0032aba79177680b7b91363d1d9be97dd9c90
CRs-Fixed: 2261501
|
|
|
|
|
|
|
|
|
|
|
|
| |
DAC_OVERRIDE is disabled for all the vendor init scripts
in Android P. This change will grant "group root" the write
permission temporarily for deleting/copying operations.
System user could not access the MBN files in data partition
no longer. Only radio user and root group have read permission
after boot up.
Change-Id: I9f184da2253dc5896b145c0e52fc3b42da15d9f7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Using "chmod -h" instead of "chmod"
2) Using "mkdir -m" instread of 2 seperate commands
for creating directory and change permission
3) Using "write" command in RC file instead of "echo ...>"
in bash
4) Create "data/vendor/modem_config" for storing MBNs, which
is read only
5) Remove qcril.db copying in sh file, since this logic is
not used anymore
Change-Id: Ib9a9e0d32ae529dab3dc0c164062d2887dff4439
|
|
|
|
|
|
|
| |
init.qcom.sh accesses files owned by groups radio, system and hence
the groups have been added.
Change-Id: I535eeaf42f38532ec6de46eb57f3cc0e1d959a47
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Solves the following denial.
denied { add_name } for comm="init" name="tombstones" scontext=u:r:vendor_init:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
Change-Id: Iff7d85d6f13f8fa0efc4a594bfcefdbb9d8ee3ed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
https://android.googlesource.com/platform/frameworks/base/+/c78a463e875d91eae2cf256042fd99d130217c38
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
|
|
|
|
| |
Change-Id: I96b2f52d7cf97d9b5794422bb57d6e151917d7a9
|
|
|
|
| |
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
The kernel does not support aio with ffs.
Set the property so adb/mtp know to use the compatible
functions, and the same while in recovery.
Bug: 37916658
Test: Use adb
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
|
|
| |
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
|
|
|
|
| |
* Matches rild.legacy.rc from Pie's RIL
Change-Id: Icdb0a3e4859bc0a4011e34fdd483cef2ca3b8a7f
|
|
|
|
|
|
|
|
| |
* The creation of /data/misc/wifi and /data/misc/dhcp was moved long ago
to the core init.rc script. Moreover, /data/misc/wifi is deprecated
since wpa_supplicant now relies on /data/vendor/wifi.
Change-Id: Ic0a33af44ffe163d3dd06cebdc1e192dc9bcb11f
|
|
|
|
|
|
|
|
|
|
| |
Framework will now add interface to supplicant (via HIDL) when it
needs to control an interface, so don't specify them in the startup
params.
Bug: 69426063
Test: Device boots up and able to connect to wifi.
Change-Id: I817d28093f8b982e3806c212babd888c0f5eb7c0
|
|
|
|
|
|
|
| |
Bug: 72394251
Test: Able to start supplicant from framework using
ISupplicant.getService()
Change-Id: I19b8434e7241b9028e7dc86316ec9d5512affcca
|
|
|
|
|
|
|
|
|
|
|
|
| |
Treble compliance.
Bug: 70228425
Bug: 70393317
Test: complete wifi test in b/70393317
Test: Test wifi on Taimen and Sailfish
Test: verify sockets exist in /data/vendor/wifi/wpa/sockets
Change-Id: I0bfc3a351419f0a03498e79664949f353369bf1b
|
|
|
|
|
|
| |
* Not needed, system treats it as a raw block device
Change-Id: Ieff8b1888c22d49974bfeb60cfc62f3bb2d424c7
|
| |
|
|
|
|
|
|
|
| |
SELinux blocks the loading of the newer firmware and
I do not know how to fix it, for now.
This reverts commit 13c9609710f05a79d119636ec2b9640259dd67c2.
|
|
|
|
| |
* From google/marlin/marlin:9/PPR1.180610.009/4898911:user/release-keys.
|
| |
|
|
|
|
|
|
|
|
| |
* I just don't understand why we have 16 frequencies (from 307 to 1593MHz) on
our power cluster and libqti-perfd just wants to force the highest every time
I touch the screen...
Why implement cpu frequency scaling and then use only two?
|
|
|
|
|
|
|
| |
* Without group perms our bluetooth HAL is unable to access
file with bluetooth address.
Change-Id: Idf00d5d31be34ec1aaf66ddfaf3646d913d63687
|
|
|
|
|
|
|
|
|
|
|
|
| |
Wpa_supplicant's random pool is not necessary on Android. Randomness
is already provided by the entropymixer service which ensures
sufficient entropy is maintained across reboots. Commit b410eb1913
'Initialize /dev/urandom earlier in boot' seeds /dev/urandom with
that entropy before either wpa_supplicant or hostapd are run.
Bug: 34980020
Test: Use wifi and wifi tethering on Taimen
Change-Id: Ib5caf362bc939911b357db186a274957d3fbf186
|
| |
|
|
|
|
|
|
|
|
|
| |
We don't need aggressive load balancing during boot, only after boot has
been completed.
bug 30040263
Change-Id: Id22ac312751983f774208399b1673459e2351b93
|
|
|
|
| |
* And use our cpuset for the camera daemon.
|
|
|
|
|
|
| |
* Match the new changes introduced in O
Change-Id: I43c6fa60214ce91d6a149f15416a9f3170abfdd5
|
| |
|
|
|
|
| |
Change-Id: I142e2842a3a88852d0e0e3598b00cd219259e6a0
|
|
|
|
| |
* Use Xiaomi's LOS work as main base.
|
|
|
|
|
|
|
|
| |
* libqti-perfd for some reason wants to write
"0:1593600 1:1593600 2:2342400 3:2342400" to it.
* Preventing that lets us use full max freq on 8996pro devices.
Change-Id: I081de2e8fc2ade7e6de4e971c29b8c53dd0a598c
|
|
|
|
|
|
|
| |
Bug: 64072712
Bug: 64022845
Test: boot from charger and check last kmsg
Change-Id: I8c890c55c9b578ae9e43be7f041dc2cbd4c80c15
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
SystemServer_start : 6.5916 0.14159
SystemUi_start : 9.646 0.11627
system_server_ready : 10.341 0.16571
After:
SystemServer_start : 6.5465 0.17295
SystemUi_start : 9.5017 0.13355
system_server_ready : 10.13 0.17956
Bug: 63644084
Test: 10 boot with packages/services/Car/tools/bootanalyze/bootanalyze.py
Change-Id: I5509629bba6cddb35bb72d0f48283e2bf51cebd3
|
|
|
|
|
|
|
|
|
| |
efficiency curve
Bug: 28560172
Change-Id: I2974a6dc43ecc51603df4acb942ffcb04091e653
Signed-off-by: martin_liu <martin_liu@htc.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Low level shutdown is triggered after SystemServer is
cleaned up. sys.shutdown.requested is private to SystemServer
and is used to syncrhonize the shutdown process if SystemServer
crashes before hardware reboot is complete.
Native daemons must use low level shutdown indication from
powermanager for their graceful shutdown, if they wish to stop
before init terminates the process.
Change-Id: Ia583f7dce6f1927d9b766fdc132f082b409f4d67
|
|
|
|
| |
Change-Id: I1e243b057ed24a2bc50a206de7b6c5c8bd702617
|
|
|
|
|
|
|
|
| |
Cpuset foreground boost is departed since
https://android.googlesource.com/platform/frameworks/base/+/a712d4058f6f85268838
Change-Id: Iab1834dbb8cce15480b5e11968bcfff7cc80177e
Signed-off-by: Lennart Wieboldt <lennart.1997@gmx.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enough RAM.
* My device has 6GB of RAM so I didn't notice any issue. However devices with 3GB or
less become unusable with THP enabled, according to @YaroST12
* Also, for devices with enough RAM, we'll restrict THP to madvise regions as
suggested by the kernel documentation:
"Embedded systems should enable hugepages only inside madvise regions
to eliminate any risk of wasting any precious byte of memory and to
only run faster." [1]
[1] https://www.kernel.org/doc/Documentation/vm/transhuge.txt
|
|
|
|
|
|
|
|
| |
* The atfwd daemon is responsible for handling AT command
forward requests from modem and should be enabled
for all targets except sda, apq, qcs.
Change-Id: I886b616565f81da10ad4a7b52baf8854a0b26f52
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* We renamed 'factory' as 'vendor' on our partition table:
z2_row: sgdisk_static --change-name=9:vendor /dev/block/sda
z2_plus: sgdisk_static --change-name=46:vendor /dev/block/mmcblk0
Note that partition number for z2_plus may not be the same if you came from Indian's stock
or from Chinese's stock.
Check first the output of 'ls -l /dev/block/bootdevice/by-name/factory'
* Thanks to @cryscript for the idea and his work for z2_plus.
|
| |
|
|
|
|
|
|
|
|
| |
Remove this redundant mechanism of copying DB.
QCRIL Daemon already takes care of the copying
at runtime
Change-Id: I2213c2a8a1c9717c92f3cf5e7873c0ee9e65da35
|
|
|
|
|
| |
* Imported from ZUI 3.5.315 removing everything that is not
useful for our msm8996.
|
|
|
|
|
| |
* Partial revert of 6552f3fed81aa21b6db408765a588cd08f51370c with
some comments.
|
|
|
|
|
|
|
| |
* The path should have the same length as the
previous one: /data/misc/camera/cam_socket
* Also make the directory for the socket.
|