Commit Graph

7 Commits

Author SHA1 Message Date
Paul Keith c453c83a25 klte-common: Update ril.h to be inline with msm8974-common
Change-Id: I736f34d0acd1428bb7a78417c4c35bf5bccc5cec
2018-02-08 03:57:56 +01:00
Kevin F. Haggerty 8153e77961 klte-common: Drop libril
* We're going to use the shared version from msm8974-common now

Change-Id: Ie4e6336209a5fb6881cd52807082ea2acffd1c8c
2018-02-05 21:30:06 -07:00
Paul Keith ae4dd1ba1a klte-common: Fixup RIL_Call structure
* 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
2018-01-19 16:07:35 -07:00
Kevin F. Haggerty 345ceb6a2c klte-common: libril: Fix SMS on certain variants
* 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
2018-01-19 16:07:35 -07:00
solk2 613d3fdea2 klte-common: libril: Fix RIL_Call structure
* 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
2018-01-19 16:07:35 -07:00
Paul Keith 1bafc74e01 [DO NOT MERGE] klte-common: libril: Add Samsung changes
* 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
2018-01-19 16:07:35 -07:00
Kevin F. Haggerty bcc9a6c694 [DO NOT MERGE] klte-common: import libril from hardware/ril-caf
* Branch LineageOS/android_hardware_ril@55fb07ad (staging/lineage-15.1-caf)
  + https://review.lineageos.org/#/c/199884/

Change-Id: Ic2095f4da30a599cf25a51e286a5b9ce9096dc82
2018-01-19 16:07:35 -07:00