Question About Auto Answer/Hangup Functionality

[phaze3131]

Hey guys, I am a past iPhone user, and I used an app called Mcleaner which was able to instantly answer and hangup on phone calls based on certain criteria.

I am seeing if anyone knows the actual process a call goes though from beginning to the point of getting instantly hung up on by the app Mcleaner. Call it the lifespan of the call or the datapath.

Then I'd ask why is this not possible (as of yet) on an Android phone. All the android apps that try and do this the call will always get to the phone and ring once (usually) and then get instantly hung up on.

Yes we are not the iPhone but my question lies in the differences in how calls are handled and I am really curious how the two os's differ in this aspect.

Thanks all and no I'd never think twice about going back to Apple

Travis

[phaze3131]

maybe someone knows someone who I could ask this question to?

[compywiz]

You actually want it to answer then hang up? Not just reject the call?

[SixStringTheory]

From what I know there's a class (TelephonyManager) that monitors changes in the phone state.

TelephonyManager | Android Developers

Any app that would do anything involving phone calls would need to request permission (.READ_PHONE_STATE) to access the class, and then set up a receiver that registers a listener object to monitor the class for those flags being changed (ACTION_PHONE_STATE_CHANGED, i think).

I don't see why you couldn't have an app to monitor for CALL_STATE_RINGING, check the EXTRA_INCOMING_NUMBER and compare to your blacklist and then do whatever you want.

I've never written anything using the dialer or radios so not 100% sure.