* 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
* 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
* 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
* Get inline with the lack of CameraParametersExtra.h
support in AOSP, avoid using device header to inject
additional parameters, especially with the introduction
of Android.bp compilation for libcamera_client
which ignores the device headers override
Change-Id: I754116f55ed32d54d1b1ad44407993137a07fb69
* The previous path worked only because of
failsafe methods in the lights HAL.
* Point the define to our actual max brightness path.
Change-Id: Ic80ecaf4f26859a597f4fc29cd6f7143d4daac6a
Signed-off-by: Paul Keith <javelinanddart@gmail.com>
