Sending text data via USSD in Android

by sacred03 » Thu, 12 May 2011 08:59:27 GMT


Sponsored Links
 Is there a possibility to send text data via USSD in android?

The only way I found was to invoke an android.intent.action.CALL
intent and append the text data after as follows

tel:#(short code)(bookmark)(number of pages)(page number)
(MSISDN)*(text data)# e.g. tel:#161*129*1*1*5555*(text data)#

But once I append text data & start the ACTION_CALL but the text data
will be converted into keypad codes.

That is ACL = 225.

Is there any other way to piggy back text data on an USSD call without
getting the text converted into keypad codes?

-- 



Other Threads

1. Efficient fifo queue for primitive types?

I am trying to find an efficient fifo queue for primitive types. I
need this for processing recorded samples with AudioRecord class. My
problem is that I need to process the samples in excactly 5000 chunks.
But the buffer size gained by getMinBufferSize is different on each
devices and more over the amounts of samples read are also different
in each while iteration. For example on my phone the buffer size is
sth over 8000 but one time the samples are read in a about 2500
package, another time it's 6000 and another it's  almost 8000. So I am
putting my samples in a ConcurrentLinkedQueue fifo queue and if I
cross 5000 I take the first chunk and do the processing. However this
queue class can only accept non primitive type (so I must use Short
not short). And this is a major problem, because when I looked at
traceview I saw that a huge amount of time is taken by functions like
'ValueOf' (well if I have 5000 elements it's nothing surprising...).
In fact this is slowing down so much that, my recording process is
corrupted and the sound is broken.

Can any one advice some other fifo container I can use for working
with primitive types? I was thinking about ShortBuffer but this is
more like a lifo queue, and I need the samples in exact fifo order.

-- 

2. No space for this sql statement.

I'm seeing this

Reached MAX size for compiled-sql statement cache for database "";
i.e., NO space for this sql statement in cache:

Please change your sql statements to use '?' for bindargs, instead of
using actual values

I would follow that advice, except for one simple fact, which I noted
a year ago:

IT DOESN'T WORK WITH FLOATING POINT.

I can and have proved it. You can set up a query with '?' and floating
point, and the same query with good old fashioned string
concatenation. They both return an answer, but the answer for the
bindargs one is *wrong*.  The float columns are analyzed using a
string comparison. I can't necessarily say this is a bug in
SQliteDatabase.query because it does say 'The values will be bound as
Strings'.

So here's my question.

Is there anything I can do to prevent the above error? Since there is
no use for caching this statement given the bindings don't work, can I
stop it from caching the statement in the first place?

What adverse effects do I expect with the error? It doesn't crash
right away, but it doesn't sound good.

Nathan

-- 

3. emulator: android_hw_control_init: hw-control qemud handler initialized

4. Serious problem on Android 2.3 and XmlSerializer

5. Need help refresh different activity's when updating the database

6. how to render video YUV frame?

7. error in compiling GingerBread for Sholes