search

jancona / android-on-freerunner

Automatically exported from code.google.com/p/android-on-freerunner
1 stars 1 forks source link

Should properly display unsolicited USSD messages #12

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. USSD 
(http://en.wikipedia.org/wiki/Unstructured_Supplementary_Service_Data) is 
the way GSM phones query and report status information, like prepaid 
balances.
2. Currently USSD messages are displayed as a string of hex digits in a 
dialog box.

What is the expected output? What do you see instead?
They should be properly decoded into readable text.

Original issue reported on code.google.com by scarhill on 23 Sep 2009 at 3:47

GoogleCodeExporter commented 9 years ago 
I think the the decoding is done by the upper layer, is there any error message 
in
the logcat? I don't have way to test USSD :(. Any log or comment are welcome.

Original comment by michaelt...@gmail.com on 23 Sep 2009 at 3:44

GoogleCodeExporter commented 9 years ago 
I would guess that if the upper layer was supposed to decode this it would 
already
work, since the message is getting there, but in the wrong format.

I can reproduce this, since I have a prepaid account that uses these for balance
notifications. I don't see any errors using a plain adb logcat. Should I try the
radio log? If I wanted to add some logging in the RIL code, where should it go?

Original comment by scarhill on 23 Sep 2009 at 4:19

GoogleCodeExporter commented 9 years ago 
----
We can try to request the format output

static void  requestSendUSSD(void *data, size_t datalen, RIL_Token t)
{
    ATResponse   *p_response = NULL;
    const char *ussdRequest;
    int err;
    char *cmd;

    ussdRequest = (char *)(data);

    asprintf(&cmd, "AT+CUSD=1,\"%s\", 72", ussdRequest); <--- 72
---------------
If this doen't work try 15

Michael

Original comment by michaelt...@gmail.com on 24 Sep 2009 at 2:39

GoogleCodeExporter commented 9 years ago 
I get 'Connection problem or invalid MMI code' with my local provider.  Will 
try to
obtain the log.

Original comment by alex.shu...@gmail.com on 24 Sep 2009 at 8:23

GoogleCodeExporter commented 9 years ago 
I've made Alex's comment into a separate bug [Issue 19
http://code.google.com/p/android-on-freerunner/issues/detail?id=19]

Original comment by scarhill on 25 Sep 2009 at 3:04

GoogleCodeExporter commented 9 years ago 
Decode the message as hex-encoded default GSM alphabet, then re-encode as 
UTF-8. Ugh! 
Note that this is the unsolicited message bug only. I'll go after issue 19 next.

Original comment by scarhill on 27 Sep 2009 at 11:58