Just had a report a few days ago from a user on HTC Desire (2.2) that
says a previous version of my app worked fine. This is confirmed since
I sent him a previous version and it worked. It might be just this one
case since I've had another user say it didn't work with the same
previous version.

I'm trying to find out exactly which change made the difference (both
versions do essentially the same thing with subtle differences) so I
sent him a changed version to test it. If I find out anything I'll
post it here, but don't hold your breath.. he's not very responsive.

The workaround placing a new Intent seems reasonable in these cases. I
think I'll add an option in my app for people having this issue though
it's awful that I even have to think about doing that. One would think
a company like HTC would test the whole API before releasing a new ROM
(after all they sure take their time to do it).

On Aug 27, 5:48 am, billas <[email protected]> wrote:
> As it seems the HTC Desire (2.2) responds to "setResultData(null)"
> wich will stop the out dial. Then you can place a new intent
> (Action.CALL) to call the new number.
> Not so nice workaround, but as a user you hardly notice it.
>
> On 26 Aug, 14:42, billas <[email protected]> wrote:
>
>
>
>
>
>
>
> > Here to. Exact same problem. Tested onHTCDesire2.2 (not working).
> > It seems like it ignoring the resultData from the broadcastreceiver.
> > Earlier tested onHTCHero build 2.73.405.x (android 1.5) where the
> > "Dialer" application doesn't even send a broadcast!!
> > Current build onHTCHero (android 2.1) works perfectly.
>
> > I'm getting a bit desperate for a good workaround....
>
> > ./tobias
>
> > On 18 Aug, 21:31, Denis Souza <[email protected]> wrote:
>
> > > I'm getting the exact same problem.
> > > I have an app that changes the number being dialed.
> > > It works on everything except theHTCDesirewith Android 2.2. Works
> > > withDesireon 2.1 and with any other device I tested with 2.2. There
> > > are reports from several of my users using 2.2 devices and it works on
> > > all of them except for theHTCDesire.
>
> > > I'm think it might be a bug introduced byHTC.
>
> > > If you find a workaround let me know.. I'm still looking...
>
> > > Denis Souza
>
> > > On Aug 18, 10:20 am, Nicolas Zerr <[email protected]> wrote:
>
> > > > Hello,
>
> > > > I'm having troubles with intercepting outgoing calls. In fact, it
> > > > works perfectly on emulator 2.1 and 2.2, and was running also
> > > > perfectly on myHTCDesirewhen i was in 2.1 version.
>
> > > > Here is some source code :
>
> > > > package com.testcallcatch.test;
>
> > > > import android.content.BroadcastReceiver;
> > > > import android.content.Context;
> > > > import android.content.Intent;
> > > > import android.util.Log;
>
> > > > public class OutgoingCallReceiver extends BroadcastReceiver {
> > > >     @Override
> > > >     public void onReceive(Context context, Intent intent) {
> > > >         Log.d("LOOK HERE", "->" + getResultData());
> > > >         setResultData("0123456789");
> > > >         Log.d("LOOK HERE", "Setting to 0123456789");
> > > >     }
>
> > > > }
>
> > > > And the manifest :
>
> > > > <?xml version="1.0" encoding="utf-8"?>
> > > > <manifest xmlns:android="http://schemas.android.com/apk/res/android";
> > > >         package="com.testcallcatch.test" android:versionCode="1"
> > > >         android:versionName="1.0">
> > > >         <application android:icon="@drawable/icon" 
> > > > android:label="@string/
> > > > app_name">
>
> > > >                 <activity android:name=".TestCallCatch" 
> > > > android:label="@string/
> > > > app_name">
> > > >                         <intent-filter>
> > > >                                 <action 
> > > > android:name="android.intent.action.MAIN" />
> > > >                                 <category 
> > > > android:name="android.intent.category.LAUNCHER" />
> > > >                         </intent-filter>
> > > >                 </activity>
>
> > > >                 <receiver android:name=".OutgoingCallReceiver">
> > > >                         <intent-filter android:priority="2147483646">
> > > >                                 <action 
> > > > android:name="android.intent.action.NEW_OUTGOING_CALL" />
> > > >                         </intent-filter>
> > > >                 </receiver>
> > > >         </application>
>
> > > >         <uses-sdk android:minSdkVersion="7" />
>
> > > >         <uses-permission
> > > > android:name="android.permission.PROCESS_OUTGOING_CALLS"></uses-
> > > > permission>
> > > > </manifest>
>
> > > > As you can see, it is a very simple sample, but it's not working on
> > > >HTCDesireunder 2.2 . I suspect this comes fromHTC, but I wonder if
> > > > there are other devices with this bug.
>
> > > > The app replaces each called number by 01232456789. Don't forget to
> > > > uninstall the application once done ;)
>
> > > > So I'm searching people for testing this little app :
>
> > > > - People who haveHTC2.2 device
> > > > - People who have other devices that run 2.2 android version.
>
> > > > Maybe someone has already solved this problem?
>
> > > > Thanks a lot in advance,
>
> > > > Nicolas

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to