kstamm wrote:
Android was promised to be open entirely
It is.
and I assumed it was going to allow creative use of the device
Android is not a device. Android is an operating system. The T-Mobile G1
is a device.
Perhaps in 2.0 we will actually have an open telephone platform
You have an
Thanks for your response, I apologize for my attitude.
In academia we theorize all these wonderful new systems and then go
assume they will be implementable on real world hardware.
Do you think in any version of Android we will be able to reprogram
the part of the phone that displays the
Is this the same for outgoing calls? They also cannot be interecepted
in 1.0?
If so, what is the purpose of ACTION_NEW_OUTGOING_CALL?
this is from the documentation:
It is perfectly acceptable for multiple receivers to process the
outgoing call in turn: for example, a parental control application
On Oct 2, 12:17 am, legerb [EMAIL PROTECTED] wrote:
Is this the same for outgoing calls? They also cannot be interecepted
in 1.0?
No, you can intercept outgoing calls, as you quoted from the
documentation.
--~--~-~--~~~---~--~~
You received this message because
You should call abortBroadcast() in your BroadCastReceiver, after catching
the *ACTION_NEW_OUTGOING_CALL intent.*
On Thu, Oct 2, 2008 at 12:19 PM, e [EMAIL PROTECTED] wrote:
could u help me out ...how do manag with abortBroadcast()??
On Oct 2, 12:50 pm, legerb [EMAIL PROTECTED] wrote:
how to get *ACTION_NEW_OUTGOING_CALL intent.*???
On Oct 2, 4:26 pm, Rimma Sukhovsky [EMAIL PROTECTED] wrote:
You should call abortBroadcast() in your BroadCastReceiver, after catching
the *ACTION_NEW_OUTGOING_CALL intent.*
On Thu, Oct 2, 2008 at 12:19 PM, e [EMAIL PROTECTED] wrote:
could
how to do catch *ACTION_NEW_OUTGOING_CALL intent.* ?
On Oct 2, 4:26 pm, Rimma Sukhovsky [EMAIL PROTECTED] wrote:
You should call abortBroadcast() in your BroadCastReceiver, after catching
the *ACTION_NEW_OUTGOING_CALL intent.*
On Thu, Oct 2, 2008 at 12:19 PM, e [EMAIL PROTECTED] wrote:
I'd like to expand the logic of when to send a call directly to
voicemail. I believe that there would need to be a hook somewhere to
intercept the incoming call and determine whether or not to accept
it.
An example use case would be to prevent drunk dialing. There could
be a setting in Android
Sorry, intercepting incoming calls is not supported in 1.0.
On Oct 1, 9:20 am, Trey Ethridge [EMAIL PROTECTED] wrote:
I'd like to expand the logic of when to send a call directly to
voicemail. I believe that there would need to be a hook somewhere to
intercept the incoming call and
On Sep 27, 1:27 pm, Eric B [EMAIL PROTECTED] wrote:
One of the best apps I've every bought for my Treo 600/650 is an app
that lets you assign specific ring tones (really mp3 files) to
specific contacts or groups of contacts. I especially like the
ability to turn off the ringer and vibrator
Anyone trythen plz tel me
On Sep 25, 8:37 pm, legerb [EMAIL PROTECTED] wrote:
How about: ACTION_NEW_OUTGOING_CALL?
According to SDK documentation it gives the possibility to intercept
the call.
Has anyone tried to use it?
On Sep 17, 9:41 pm, friedger [EMAIL PROTECTED] wrote:
I
One of the best apps I've every bought for my Treo 600/650 is an app
that lets you assign specific ring tones (really mp3 files) to
specific contacts or groups of contacts. I especially like the
ability to turn off the ringer and vibrator for calls with no caller
id.
I don't think this kind of
How about: ACTION_NEW_OUTGOING_CALL?
According to SDK documentation it gives the possibility to intercept
the call.
Has anyone tried to use it?
On Sep 17, 9:41 pm, friedger [EMAIL PROTECTED] wrote:
I could imagine an application that accepts acallwhen the user
presses a button like I am
Good point Mark. I was speaking in terms of using the API to develop
an application. Those delivering their own platform all the way to
firmware probably will, and certainly should, have access to all of
that.
In terms of the now now type comments (@kstamm), yes, it will be
open source all the
I would agree that that sounds like a good call. ;)
That still would not interrupt the dialer screen if already in a call,
and could be configured based on permissions, good idea.
On Sep 17, 2:41 pm, friedger [EMAIL PROTECTED] wrote:
I could imagine an application that accepts a call when the
I wonder if this will be possible on real devices? It should be
according to the All applications are equal statement but has anyone
further info regarding this?
On Sep 17, 8:01 am, Megha Joshi [EMAIL PROTECTED] wrote:
Unfortunately, you cannot intercept incoming calls in the sdk.
2008/9/16
I would disagree with the statement that this should be possible.
User's expect a call to work like a call which works like a call and
that would be sort of like a call ;).
I think the idea is that certain key functions of the phone - calling,
and going to the home screen - usurp other
I think the idea is that certain key functions of the phone - calling,
and going to the home screen - usurp other functions. All non built-in
key functions, e.g. applications, are still equal, but yes a few key
functions have a higher priority
I suspect there will be two tiers of development
Now now, we were told the Android was the first open source phone all
the way down to the hardware. I expect call reception capability!
It's the only thing that sets it apart from other smartphones.
On Sep 17, 10:35 am, Charlie Collins [EMAIL PROTECTED]
wrote:
I would disagree with the
This was to be the cornerstone of the application I've been working
on. I had assumed that this would be supported because, Android does
not differentiate between the phone's basic and third-party
applications -- even the dialer or home screen can be replaced.
Apparently, that applied to all
This was to be the cornerstone of the application I've been working
on. I had assumed that this would be supported because, Android does
not differentiate between the phone's basic and third-party
applications -- even the dialer or home screen can be replaced.
Apparently, that applied to all
I don't agree that changing the in call screen/incoming call screen/
outgoing call screen should be only available to handset manufacturers/
operators. A phone could do SO much more when applications could
somehow hook into these screens (or even control the voice streams).
Imagine an
That sucks. That was to be the cornerstone of the application I've
been working on. I had assumed this would be supported because,
Android does not differentiate between the phone's basic and third-
party applications -- even the dialer or home screen can be
replaced. I guess that's true
That sucks. This was to be the cornerstone of the application I've
been working on. I had assumed that this would be supported because,
Android does not differentiate between the phone's basic and third-
party applications -- even the dialer or home screen can be
replaced. Apparently, that
2008/9/17 friedger [EMAIL PROTECTED]
I could imagine an application that accepts a call when the user
presses a button like I am rushing out of the meeting, hang on
another second. Instead of me wispering into the phone, the caller
gets a proper response.
So there is no way to do that,
I don't agree that changing the in call screen/incoming call screen/
outgoing call screen should be only available to handset manufacturers/
operators. A phone could do SO much more when applications could
somehow hook into these screens (or even control the voice streams).
I'm not
Unfortunately, you cannot intercept incoming calls in the sdk.
2008/9/16 sectrean [EMAIL PROTECTED]
Hi,
I'm trying to figure out how to intercept an incoming call, but I'm
not able to find much documentation on how I would do this.
I would like to be able to display a custom dialog to
27 matches
Mail list logo
