* 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
* Replace the LOCAL_PATH instances with a variable not prone to
getting stomped
* Replace all expanded values with the variable
Change-Id: I91ef536c038fb38d250633bfdad82c2a6537c1da
* 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
* All of the variants are close enough to each other that
carrying these in the device-specific trees doesn't
add much.
* Sizes picked by selecting the smallest value from each
of the device-specific trees for each variable.
Change-Id: Ibe024ec857db971ff1522d05cf55e8492816b7ec
* 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
* cmhw is dead, but we don't actually carry any local classes. Just
stop appending to the variable altogether
Change-Id: I075ad79ed99b0b85a21af594db0036136c984542
* This now matches the expected library name for Oreo and the scheduler
library is removed at the same time because it's not needed
Change-Id: Iec80b9fd871f82d4c34d54f70360eed77559f52f
* The updated audio HAL sources (for instance 8.0.0_r33) use
the formats directly through the pcm_format_from_audio_format
inline functions to resolve and validate provided formats,
however in our case the formats include values outside
of the allowed AUDIO_FORMAT_PCM_... values and fail
* Crash situation was happening upon 3.5 Jack plug only
Change-Id: I4b613c25ea7fd202a434c18c2fdd06e55a57c456
Signed-off-by: Adrian DC <radian.dc@gmail.com>
The current HIDL implementation needs BT_WAKE_VIA_PROC_NOTIFY_DEASSERT,
and PROC_BTWRITE_TIMER_TIMEOUT_MS = 0, same as angler.
Change-Id: I1b5d12788ab2689b3fb1779957d263c804def590
Test: Manual use of Camera, Movies, Photos and YouTube apps.
Test: With CtsMediaTestCases.apk installed,
adb shell am instrument -e size small -w
'android.media.cts/android.support.test.runner.AndroidJUnitRunner'
Bug: 31399200
Change-Id: Ib2d43fcfc7bbd00d47cf81a98b415d2be2e0e12a
Martin Bouchet
Kevin F. Haggerty
solk2
Paul Keith
Bruno Martins
Luca Stefani
Christopher R. Palmer
Ethan Chen
Ritesh Harjani
Daniel Rosenberg
Rashed Abdel-Tawab
Adrian DC
D. Andrei Măceș
Pawin Vongmasa