I feel your pain ..... The only way to be more precised in reflecting
call states is to look in the framework/platform code and expose this
information to the higher level (framework code changed needed :-( )
The Android Telephony on SDK level has no concept of a Call or
Connection as other existing TAPI implementations which makes it very
difficult to write a good Telephony application on SDK level ....
I hope things are changing in the future
--
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.
On Oct 13, 11:42 pm, SGAdrian <sven.wastl...@gmail.com> wrote:
> Hi,
>
> I can see that we can get a phonestate via the PhoneStateListener,
>
> /**
> * The phone state. One of the following:<p>
> * <ul>
> * <li>IDLE = no phone activity</li>
> * <li>RINGING = a phone call is ringing or call waiting.
> * In the latter case, another call is active as well</li>
> * <li>OFFHOOK = The phone is off hook. At least one call
> * exists that is dialing, active or holding and no calls are
> * ringing or waiting.</li>
> * </ul>
> */
> enum State {
> IDLE, RINGING, OFFHOOK;
> };
>
> but there is no way of telling the state of the call. OFFHOOK is a
> number of states combined into one.
>
> Is there a particular reason for this? Are we not allowed to see the
> correct state of a call?
>
> BR,
> SGAdrian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
