This gerrit adds error codes for messages related
to SMS and set_mute, get_mute requests
Bug: 27038563
Change-Id: I4991e4a38c81501c39e91cfd5df90d8288f542ad
wakelock.
+ New type is added as ack from RIL java should be sent only for unsolicited mesgs
which hold wakelock in ril.cpp.
Bug: 22127517
Change-Id: Ib7e920d168ab92665283f80476bad3f5ede033e4
Modify condition to use SimRefreshResponse struct in
all RIL Versions greater than 7.
BUG=21075857
Change-Id: Ifde00434bfcaecf3b4c32392fc4964fe3b43f6b5
+ Added documentation for new RIL versioning format.
+ Changes associated to new RIl versioning format.
Bug: 25779475
Change-Id: I4e53c6125995064b8ac0cdfc9376ef2cefe69ec8
* These workarounds were introduced before http://review.cyanogenmod.org/#/c/159520/
and are no longer needed because the framework now has dynamic QAN element support.
Setting the ro.ril.telephony.mqanelements to a proper value should fix the operator
search on all the devices and these workarounds are no longer required.
* http://review.cyanogenmod.org/#/c/100398/ discards every 5th QAN element which breaks
devices with libsec-ril that returns more than 5 QAN elements. zeroflte and noblelte
return 6 QAN elements and the 5th element was being discarded instead of 6th.
* The code assumes 5 QAN elements per operator which doesn't hold true for all devices.
* In case of devices with 6 QAN elements, the size of the string array was a multiple
of 6, but since we are discarding the 5th element, the contents of the string pertaining
to each operator is a multiple of 5 following by trailing null strings in the array,
which caused issues in the framework while trying to read the strings, since we are
expecting 6 strings per operator and with a discarded string, we only receive 5.
Thanks to Javi Ferrer for diagnosing the issue on zeroflte
Change-Id: I2e99291f3438998a253755a19a063d15a19d63e0
Copying headers makes fixing compile errors hard, and breaks dependency
restrictions. Move ril_ex.h to an exported include directory instead of
copying it.
Bug: 18903857
Change-Id: I4b59a01e442db0d3198def69a5a5ff17b2a41c66
There is a buffer overflow which causing rild crash. For
appendPrintBuf, "sprintf" is replaced with "snprintf" for
the safe copy operation.
Bug:23289936
Change-Id: I25430a5c6f2a8b19a3271235323499b6ee802746
If someone needs this, it has to be fixed to read
TARGET_OUT_HEADERS (notice the extra 's').
We are only getting away with it right now because M ignores empty
include paths, but N will barf on this.
Change-Id: I7f010398a40ebaf6811a58a121590944445fbcba
xmm7260 on SLTE doesn't have this flag anymore. Devices which need it
should specify the flag.
Change-Id: I166f579274667919756d3bb90e0b182165525975
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
This is not part of the standard API, so remove it.
Samsung devices almost always use the RIL_REQUEST_DIAL_EMERGENCY_CALL
hook, so devices should implement that in their specific RIL subclass.
Change-Id: I2cf9eee00a4b5b02e998d8efcbefa87a9ca7b7b4
The modems used in recent Samsung devices use different paths
than older devices apparently.
These values were extracted from hexdumps at the correct data
positions from the device specific libsecril-client.so blobs.
Change-Id: I0547cb1de40130843fee3f1310e1e6aed95195c7
frameworks/opt/telephony is using a slightly different named property
to check for the QANElements count.
Align the check here to the frameworks one to avoid redundancies.
Change-Id: I22f7cf070953026798d0ae4759e3c9845dba767c
Newer RIL versions have more QAN elements so we need a way
to adjust them to the correct value.
This needs to be set to same value as mQANElements in the RIL Telephony
class.
Change-Id: Icfad9c0acf1b95f63c232b6c4c49ed52bd4e3aa4
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
Several things are redundent except for the fact
messages are reaching rilc. Left in in case we need to debug
the layer, but blocked out with #if VDBG
Reduces startup logging to radio buffer by 20%
Change-Id: I95099457ea365ee108e7da8e1f81434531b6b9f0
Added new socket connection for communication between the SAP module
in Telephony and User Identity Module with DSDA support.
New classes added are:
RilSocket
---------
Base class(virtual) for any type of socket. Has listen
and commands callbacks similar to that of the existing
telephony->rild socket.
RilSapSocket
------------
Derived class for socket for communication between BT SAP
and the sim module in the modem. It initialises
socket, calls Sap_Uim_Init to get the handles and
starts the socket thread.
rilSocketQueue
--------------
Queue for managing socket requests.
Change-Id: I8828173941d6ae76f1f9cc0d567efaf41a77d175
for debugging
- Add more logging using ALOGD(..) for function dispatchSmsWrite,
dispatchDial, dispatchSIM_IO, dispatchSIM_APDU, dispatchCallForward,
dispatchRaw and dispatchCdmaSmsAck. To make it easier for debugging.
- Remove commented log message inside wakeTimeoutCallback () function
and remove the else clause as it's dead not used for anything.
- Modify log message inside removeFromList and removeWatch using +
and - to make it consistent with the other log message.
Change-Id: Ife0212e6a4724d8b06a1dd767484bfdf98b8e1a6
Signed-off-by: Nanik Tolaram <nanikjava@gmail.com>
New version of Samsung RIL do not use RIL_UNSOL_WB_AMR_STATE anymore.
There is a Sound Manager (SND-MGR) which has its own response base
(20000). So to be able to register a handler for
RIL_UNSOL_SNDMGR_WB_AMR_REPORT
with libsecril-client we need to know about it. This allows us to
register a callback in the audio HAL to turn WB support on.
WB_AMR_REPORT report 0x00, 0x01 or 0x02. I guess 0x01 is WB ON and
0x02 is WB + NS ON.
Change-Id: I403c86781551fc3b08354187322e8443402d56f6
The M7450 modem used in the Galaxy Note 4 (N910C variant) uses a libril
implementation similar to the one employed for Intel XMM* modems by Samsung.
This probably needs future adjustments, but so far fixes basic call functions
and signal strength is displayed correctly.
Change-Id: I2d070102ad11746902527da3c2c7f49485c7d7f1
This lines should drop every 5th element (#5,#10,#15,...).
At the moment it is dropping elements #6, #11, #16, as it start from 0
and the list start from 1. So let's match it up.
Thanks to Tobias Heinemann for the idea.
Change-Id: Idc2904040119716e666ea0fe320cde1d45869ee5