[Thunderbolt Themes and Apps] scottthreet32:
1st gingerbread update killed app

2nd update if I update will kill app

I emailed the developer

matth@everysoft.com

Sorry I can't give you a better answer, but I've been extremely busy over the past few weeks, and I just haven't had the time. The app is open source, so if you are a developer (or know a developer), feel free to try a fix. Matt

I sent him this a couple of weeks ago

Android Bridge ▼ T U E S D A Y , M A Y 1 7 , 2 0 1 1how to answer an incoming call in android 2.3 Today, I was researching on a how to answer incoming call in android 2.3 automatically. My first thought was using "ITelephony.aidl" and call the answerRingingCall(). When i looked into more details answerRingingCall() function all requires MODIFY_PHONE_STATE permission which is marked as a as "signatureOrSystem" which is mentioned here http://android.git.kernel.org/?p=platform/ frameworks/ base.git;a=commit;h=f4ece2086f3b7060edc4b93 a12f04c9af648867a and here http://code.google.com/p/android/issues/ detail?id=15031 bummer. Then thought of a another work-around and bluetooth headset popuped to my mind. In this all I had to do was to call start new intent with ACTION_UP. It worked! here is the soulution BroadcastReceiver PhoneState = new BroadcastReceiver() { @Override public void onReceive(Context context, Intent intent) { if (!intent.getAction().equals("android.intent.action .PHONE_STATE")) return; String state = intent.getStringExtra(TelephonyManager.EXTRA_ STATE); if (state.equals(TelephonyManager.EXTRA_STATE_ RINGING)) { String number = intent.getStringExtra(TelephonyManager.EXTRA_ INCOMING_NUMBER); Intent answer = new Intent(Intent.ACTION_MEDIA_BUTTON); answer.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_HEADSETHOOK)); sendOrderedBroadcast(answer, null); } return; }}; // Update on 2011-09-27 In Android 2.3.3 HTC Sensation this piece of code does not work. Reason is in 2.3.3 I found a HeadsetObserver listening for actual bluetooth plug-in event. So you need to send a Intent pretending there is a headset connected already. To fix this problem you need to send the ACTION_HEADSET_PLUG Intent before calling the above code. Intent buttonDown = new Intent(Intent.ACTION_MEDIA_BUTTON); buttonDown.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_DOWN, KeyEvent.KEYCODE_HEADSETHOOK)); context.sendOrderedBroadcast(buttonDown, "android.permission.CALL_PRIVILEGED"); // froyo and beyond trigger on buttonUp instead of buttonDown Intent buttonUp = new Intent(Intent.ACTION_MEDIA_BUTTON); buttonUp.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_HEADSETHOOK)); context.sendOrderedBroadcast(buttonUp, "android.permission.CALL_PRIVILEGED"); Intent headSetUnPluggedintent = new Intent(Intent.ACTION_HEADSET_PLUG); headSetUnPluggedintent.addFlags(Intent.FLAG_ RECEIVER_REGISTERED_ONLY); headSetUnPluggedintent.putExtra("state", 0); headSetUnPluggedintent.putExtra("name", "Headset"); // TODO: Should we require a permission? sendOrderedBroadcast(headSetUnPluggedinten t, null);

http://androidbridge.blogspot.com/2011/05/how-to-answer-incoming-call-in-android.html?m=1

I'm not a developer so how would you insert this fix

Bottomline can someone please take a crack at helping this guy out