Disconnect Block Drop calls Android 4 and above

The internet is littered with forum posts and articles that tell you it is impossible to block, drop disconnect an incoming or outgoing call using code starting Android version 4 Jelly Bean because Google placed strict restrictions on MODIFY_PHONE_STATE permission. Only the manufacturer signing certificate can grant you MODIFY_PHONE_STATE permission.

Please check my Udemy course:

https://www.udemy.com/course/appium-winappdriver-automation-testing/?referralCode=ED22C3A4CE5BB5E22E53

There are a lot of call blocker types scenarios in which we need to shield our user from a bad guy's or sour ex-girlfriend's telephone calls.
The good news is that you don't need MODIFY_PHONE_STATE permission to block, drop disconnect an incoming call on Google Android. The technique described here is available to drop block disconnect incoming calls without using the secretive infamous permission.

Time to disclose the secret sauce. A hint first:
Ever tried to dial a call using ADB(Android Debugger Bridge) shell?

If you've done that, it will be straightforward to disconnect or drop a call using a similar technique.
Time to spill the secret sauce on the internet.

Drop call on Android 4 Jelly Bean KitKat and above.

The exact Java code to drop, disconnect or reject an incoming call or an outgoing call on an Android 4 and above system is given below:

public int disconnectCallAndroid() { Runtime runtime = Runtime.getRuntime(); int nResp = 0; try { Log.d(Keys.LOGTAG, "service call phone 5 \n"); runtime.exec("service call phone 5 \n"); }catch(Exception exc) { Log.e(Keys.LOGTAG, exc.getMessage()); exc.printStackTrace(); } return nResp; }

UPDATE:
A reader has complained that the technique described here works through ADB Shell on their Nexus S Android smartphone, but it does nothing when tried through code.
The app I'm using this code is basically taking input over UDP/Bluetooth Sockets and performing disconnect call action in an IntentService. Please note that IntentService is running separately in its own thread.
Android version 4 Jelly Bean, which is API level 14 Android, blocks user apps from performing lengthy operations on the UI thread. In that case, you can use a SingleThreadExecutor and spin off a new thread to initiate run time to perform call disconnect/drop/block operation. The sample code is given below.

Executor eS = Executors.newSingleThreadExecutor(); eS.execute(new Runnable() { @Override public void run() { disconnectCall(); } });// code formatting with tohtml.com/java/

What about the permissions required to do this?
Well, the following Android permissions are needed to mess with calls:

UPDATED

<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.PROCESS_OUTGOING_CALLS" />

The disconnectCallAndroid method will effectively disconnect a telephone call in the following states:

1. Incoming call, which is in a ringing state
2. Outgoing calls, which might be ringing on the other end or not
3. Connected call, while you're talking, be it dialed by you or the other party

Nothing will happen if an active call in any of the aforementioned states is not on the phone.
I have tested my code on an Android 4.1.3 smartphone QMobile A50.
Update: I tested the call disconnect/reject/drop/cut on a friend's LG G2, which has Android KitKat 4.4 installed and worked like a charm.
Update: A friend tested the call disconnect/reject/drop/cut on a friend's Samsung Galaxy S 4 (SGS 4), which has got Android KitKat 4.4 installed. Call disconnect worked on it as well ;)

The call disconnect technique is tested on the following Android devices/versions.

1. Samsung Galaxy S4 Android KitKat Version 4.2.2
2. LG G2 Android KitKat 4.4
3. Sony Xperia Z Android 4.3 KitKat
4. Q Mobile A 50 Android 4.1 Jelly Bean
5. Nexus 5 Android 4.4.2
6. LG Optimus 4G LTE Tag Android 2.2 Froyo
7. Samsung Galaxy S3 Android 4.3 (Contributed by user Said Dami)
8. Samsung STARS Android 4.1 (Contributed by user Said Dami)

Older versions of Android

The commands are slightly different on older versions of Android.

To disconnect the reject drop call, I had to use 8 in place of 4 on an Android 2.2 smartphone, and the command became

runtime.exec("service call phone 8 \n");

Is that very simple? I hope the blog post is going to help a lot of troubled Android coders.

Be careful

The magic numbers 4 and 8 can be changed in any version of Android without notice. You'll only wake up when your clients cry and tell you, "Mommy, the app is broken."

I'm working as a freelance programmer through ODesk.com. You may hire me through following link:

https://www.odesk.com/users/~012d73aa92fad47188

List of supported Android devices based on User feedback

1. Samsung Galaxy S3 Android 4.3
2. Samsung STARS Android 4.1
3. Samsung Galaxy S2 with Android 4.3 (CyanogenMod), uses 6
4. Nexus 5 Android 4.4.4
5. Rooted Nexus 4 CyanogenMod 11 "service call phone 6." 
6. Samsung Galaxy Core Duos (I8262), running Jelly Bean 4.1.2.
7.  Xperia Mini Pro running Android 2.3.4 using 5
8. Moto G 4.4.4 

The list of supported devices is created based on user comments. Some told us the "magic number," and others didn't, but at least we know it works on these devices, and a little experimentation will be needed to figure out the exact call disconnection number.

Answering a call
I recently came across a stack overflow thread where someone has referred (many thanks) to this blog post for answering a call. As explained herein, the same technique used to disconnect a call can be reused to answer an incoming call as well. And yes, nothing makes you happier than someone positively referring to your blog post on a troubled SO thread. Here's the screenshot for reference(and self-indulgence)