* 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
* msm8974-common may end up going back and forth between legacy
and HIDL HALs, so let's be compatible with both for the time
being.
Change-Id: I5067fc474d7878a0f68e25c70b723de0e813d7c1
* The bulk of this policy isn't specific to klte, so let's move
it somewhere that allows the maintenace of it to help other
impacted devices.
Change-Id: I57b0d24d25e5871c5aa69d415b94ca21f89c1794
* Some idiot did a 'git push lineage HEAD;refs/for/lineage-15.1'
instead of a 'git push lineage HEAD:refs/for/lineage-15.1'.
Do you see the difference?
* Delete all of the old policy items and commented-out lines like
the previous commit promised.
Change-Id: I6cd8a8cffc76661b6de486e6b8550bafa83f5de9
* 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
* Checking numInts and numStrings for strict equality when
we're not looping is dumb, because Samsung is notorious
for sending extra information in their RIL (mostly VZW)
* Check if there's *enough* data rather than the *exact amount*
to fix a bunch of invalid response errors for Verizon
Change-Id: I14bc37240e5760b4629fcb74b64f25ad95d4fdfc
* Because of how structure alignment works,
adding these unused chars here is unneeded
* This makes this structure more understandable
when looking at the stock RIL java class
* Move Samsung call details as the 8 bytes before
the RIL_UUS_Info pointer, to match stock
Change-Id: I2e62be0b1774209c0165ece90588ecb7aeb042e3
* Sometimes, the modem is sending 1-2 extra fields with
the country mcc, which confuses ServiceStateTracker
* Drop the extra data here, instead of in our RIL class
[haggertk]: Forward port to ril-caf on lineage-15.
Change-Id: Ifbec67bb0dac271226bd8b5471deaf6a2ef33f2b
* mQANElements never made tremendous sense, the response strings
are not part of an object, just a text string making up a parcel.
* ro.ril.telephony.mqanelements -> ro.ril.telephony.qan_resp_strings
for consistency with some of the other new RIL props.
Change-Id: I6f941f5177852454a4d4b9494077329814d884f1
* For search, the number of strings returned for
RIL_REQUEST_QUERY_AVAILABLE_NETWORKS should be defined in the system
prop ro.ril.telephony.qan_resp_strings
Change-Id: Ie5bb8ba80c5ac93b7502da3b1bb3d2b4404ecd5e
* Samsung added an int to the end of the RIL_SMS_Response
struct in some of the variants (like vzw) but not all
* The presence of this field was discovered by examining
the stock RIL.java, which conditionally read an extra
int from the parcel, based on the device specific
CscFeature_RIL_SmsErrorClassRetry feature
* This causes SMS messages to show as "failed to send"
in the app, when they actually suceeded in sending
* Allow Samsung's custom struct and AOSP's to fix it
* Forward port to ril-caf on lineage-15.1
Change-Id: I6b3e545c2c42ab2de2ac11e93dfdf9546248080a
* Samsung added call_id as the second byte of index
* Split index to avoid a workaround in RIL subclass
* Add Samsung call detail fields, reorganize to fix
incorrect structure, to avoid hacks in RIL class
Change-Id: I023228c05165c0cef9b698846a96484a6d318092
* Changes in ril.cpp based off of hardware/samsung/libril
[haggertk]: Forward port to ril-caf on lineage-15.1 by
remapping all the samsung unsol responses
to NULL with the old response in a comment,
and all the samsung requests to NULL with
the old request mapping in a comment.
This is safe because nothing in AOSP knows
about any of Samsung's requests/responses
***** SIGNAL STRENGTH HACKS NOT PORTED YET *****
Change-Id: I59bad9925d141e6cefbc24d4eefdc0c79017852a
* 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
This reverts commit 6daa361afe.
* We're out of cmdline space and we don't even make use of the symlink
that this used to automatically create.
* If we ever want to use the bootdevice symlink, just create it
explicitly (without prop) in init.qcom.rc
Change-Id: I1c45c3ed3605f4020d824be2775639c04ba8b60d
* 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
* Configs and board/product makefiles are split into discrete
directories based on NFC chip. These chain to truly common
makefiles that add permissions and shared PRODUCT_PACKAGES.
* Relocate libpn547_fw under the nfc/pn547 directory.
Change-Id: Ie9e87fc0566eac76fc411b3e5669564c5fa54123
* 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
[haggertk]:
* During bring-up of O, GPS was exhibiting different behavior from
N -- an appropriate number of satellites would immediately lock,
but a fix would not resolve for 30-90 seconds. Digging up this
change from the L-era allows GPS to resolve a fix in a nominal
amount of time.
Change-Id: If9fd67483fedee915d46f7b9d2a7e0851400de3c
* kltesprsports doesn't have a fingerprint scanner, so variants
supporting one can include fingerprint/board.mk in BoardConfig.mk,
and fingerprint/product.mk in device.mk to avoid polluting the
kltesprsports build with fingerprint-related items.
Change-Id: I2fb1652d771740d05c3ec083054960fbe326bea4
Paul Keith
Kevin F. Haggerty
Michael Bestas
Martin Bouchet
solk2
Bruno Martins
Luca Stefani
Christopher R. Palmer