* Wrong value of user_debug in cmdline prevented to try to boot in offline charging mode
* For charger, tell that we don't have a LED and to disable init blank (with this flag, charging mode showed animation, but didn't allow to show it another time when pressing power button to turn on the screen)
* Set a brightness value for charger. In this way, when power button is pressed, device turns on and shows battery icon correctly.
Conflicts:
BoardConfigCommon.mk
This allows us to deprecate the dt fstab dependency.
Additional info for matisse device on Lineage:
Needed to make Magisk work, since it doesn't work with
the fake dt fstab thing.
Change-Id: I9c2a8c140ed64faecee0d66e00033fdffa398a4b
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.
Signed-off-by: Joshua Primero <jprimero155@gmail.com>
Newer AOSP deprecates LOCAL_MODULE_TAGS := eng debug.
We now remove that and instead add the package to
PRODUCT_PACKAGES_ENG or PRODUCT_PACKAGES_DEBUG as applicable.
To ensure that we don't miss out on any package during this switch,
we add these explicitly, even though it might have been already
added under PRODUCT_PACKAGES at some other location.
Change-Id: Id1f94f34e100d616d91292efe514c201f7d24642
As of now, this is causing issues with system and apps
not being able to create files and folders in data.
Change-Id: Ie4798ae98e0dd4e4e42011a2940e1a73627f8f3f
* Rename klte-common -> s3ve3g-common
* Drop fingerprint related blobs
* Drop camera shim, we do not need it
* Drop CameraWrapper to msm8226-common, as all msm8226 devices uses it
* Drop broadcom NFC
* Add buildable libpn547_fw.c, libpn547_fw_pku.c, libpn547_fw_platform.c dumped from stock S III Neo sources
* Update audio configs with stock S III Neo ones
* Update power_ext for S III Neo
* Drop broadcom WIFI for Qualcomm WIFI as we got a Qualcomm WIFI chip
* Drop broadcom bluetooth as we goot a Qualcomm bluetooth chip
* Update partitions for S III Neo
* Update rootdir for S III Neo
* Update overlay for S III Neo
* Update liblights path for S III Neo
* Update deviceperms for S III Neo
* Drop consumerir as we do not got an IR blaster
* Update TWRP files for S III Neo
* Samsung loads the firmware through the front door. Pie init
runs faster than previously, so we need to wait to change
the ownership until some point later, after the firmware has
time to load, else the load gets blocked by a dac_override.
[haggertk: 15.1 backport - I noticed this now happening here too]
Change-Id: I37be9e22b49735388ce1f5b922132dbfd20e2dc3
* Mounting /system partition is handled in kernel now,
however removing the entry 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're messing with ownership and permissions here, so let's go
ahead and fix the context of this near worthless thing.
* The kernel will create it, we also write it here which will create
if it doesn't exist, so this is more manageable than chasing the
type_transition path
* The file is already labeled as a wifi_data_file, so fix this to
eliminate the below denial
avc: denied { read } for name=".wifiver.info" dev="mmcblk0p26"
ino=12 scontext=u:r:hal_wifi_default:s0
tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0
Change-Id: Ie736b68f7d4d8559237b5cce072c6bf26f7ac4e7
* In particular, the RIL on CDMA variants seems to only work reliably
on first boot after flash, when things are all slowed down while
dexopting. After that first boot, it's hit and miss whether a
particular boot will have function RIL
* Slow things down by limiting ourselves to a single CPU on boot,
bringing the rest online when boot has completed
Change-Id: Ie194740cf0487268dc0dbd3377bbb790cdd1b04d
* Importing this in init.qcom.rc, especially when not all builds
have it is hacky. We'll have those devices install the script
into vendor/etc/init and let init handle it automatically, just
like the primary rild.rc script.
* Update the package name to align with the new name of the script.
Change-Id: I8eaf76c5c4f0aa590ebb1a396afa837597ebc26d
* Yes, I could do the sepolicy that lets this run correctly, but why?
Even if the phone takes 0.5s longer to boot, will you really even
notice? We are going to disable the deferred initcalls in the
kernel and let it do its thing the more "normal" way.
Change-Id: I2a9c50f12f4309923f3cdf6e646cad8edf717560
* O split charger and healthd into different processes, with healthd
running only in an full Android environment and charger running in
charge-only and recovery. It also updated the healthd sepolicy and
created a separate charger one.
* We've been using the charger symlink for ages, but the healthd
domain is no longer appropriate.
* See for details:
LineageOS/android_system_sepolicy@dc08245cLineageOS/android_system_core@526f8cf3
Change-Id: I6f528ffdcb7b14f9a51fd4246770ceecf8fb968b
* klte-common has to support both single- and dual-SIM devices, and
there are multiple devices of each kind. It makes most sense to
provide fragments in the -common tree that these devices can inherit
to configure HIDL manifest, system properties, audio support, and
any additional services necessary for MSIM support.
Change-Id: Ic3b04fa500615c33cef9b0f0a999209150969123
* Currently, config.fs doesn't give the ability to add AIDs to Android
init such that they can actually be used in the init scripts.
* Replace all instances of qcom_diag, rfs and rfs_shared with the
appropriate IDs (2950, 2951, 2952).
Change-Id: Ie983fd582d4f81c17d730df17363417f87249837
* This removes /system entry from fstab, since this partition
is now early-mounted and the fstab entry is specified in device tree.
* At the same time, also include a fully populated fstab, in order to avoid
build breakage while generating recovery updater scripts.
Change-Id: I8e558458b984e97a45a920c3751a6b7c3f2ebc5c
This reverts commit b7f109ed9f.
* So, that was 100% my derp. The cpufreq directories come and go as
cores go on- and off-line.
* Now, I wish I had notes as to whether I made this change in the
first place because of an error in a log or just based on manual
inspection.
Change-Id: I2782fefa80560bf9e20001e72ad378553d787ac0
* Don't do this, it destroys performance!
* Android uses memory cgroups to manage ZRAM. Memcg allows you to
view stats as well as set options like swappiness on a per-cg
basis. In the main init.rc, the background cgroup already has it's
swappiness set to 100. This patch sets it globally, which will
aggressively swap even foreground tasks into ZRAM which has a huge
amount of overhead.
Change-Id: I9f39b830e5817f796a42c377696864aec9bf2f22
This will let the wifi hal run as wifi user and not need root
permissions to access this path for firmware reloads.
Change-Id: I2fcd62b1dd6cbe292d89cf97085c9549bf69ba23
