Take a long time to make call

by Zhe » Fri, 04 Sep 2009 07:41:25 GMT


Sponsored Links
 Hi
    I am using GV by Evan Charlton(amazing app). But I found that it
is really slow to make a call when unchecking "route all the calls
through GV" and choose "dial out" instead of "call back". I check the
source code and found that he use following code to make a call.

        Intent intent = new Intent(Intent.ACTION_CALL);
        intent.setData(Uri.parse("tel:"+yourphoneNumber));
        activity.startActivity(intent);

The problem is, when you use above and the phone number is really long
( google voice number, 2, actually phone number), it took a long time
to make the call (40 seconds until it connects).
Funny thing is that, if I choose "route all the calls through GV",
then it connects reall fast (10 seconds).

Can any one tell me is there another way to make the call efficiently?
Thank you.

--~--~---------~--~----~------------~-------~--~----~



Take a long time to make call

by Roman ( T-Mobile USA) » Fri, 04 Sep 2009 13:29:35 GMT


 I have to check out this app :-) ...

If you have the source code try to find out how long it actual takes
from switching from ringing to connected. I could imagine that the
phone does the processing in time but the backend processing might be
pretty slow for the case you described.

Any ideas how many messages are send between the phone and the backend
to support GV?

--
Roman Baumgaertner
Sr. SW Engineer-OSDC
T  Mobile stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of T-Mobile USA, Inc.



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. tab problem

hello everyone,

i have an application that uses 3 tabs, and fills each with a intent.
the problem is when I start the application, only the first intent has
content, when I leave it and reopen it, all tabs have the content they
should have. It is always the first tab that is displayed correctly.
Project is open source, so you can take  a quick look at the tabhost:

http://code.google.com/p/androidmashup/source/browse/trunk/MashupOrganizer/src/com/androidMashup/Organizer/Ui/MashupOrganizer.java

the activities in the tabs are the other classes in the folder

http://code.google.com/p/androidmashup/source/browse/trunk#trunk/MashupOrganizer/src/com/androidMashup/Organizer/Ui

the MashupOrganizerTestApp is only for testing purposes, but it
produces the same problem.

I believe Im missing to give the activity a special attribute, but i
couldnt find out what exactly i am missing.

hopefully someone here can help me.

thx

falko

--~--~---------~--~----~------------~-------~--~----~

2. InstrumentationTestRunner not specified ??

Today Eclipse is telling me

"ERROR: Application does not specify a
android.test.InstrumentationTestRunner instrumentation or does not
declare uses-library android.test.runner"

whenever I select the Run choice of the Run menu.

What does this mean?

The AVD manager is listing the target avd. The avd will launch with
the emulator command.

I have issued the Run->Run command a many times before w/out this
happening.

Can anyone help me understand what this mens and how to correct it?

Thank you!
--~--~---------~--~----~------------~-------~--~----~

3. New ADC2 submission: "Tesla" PC remote control

4. Anyone know a lightweight geotagging library

5. Invalid routing action. Node A2DP does not exist.

6. external flash app?

7. IPsec Stac