I got to borrow a HTC desire 2.2 today and I tested my application on
that device for first time.
I obviously found the same problem.
I can confirm that setting the priority to 0, 1 or removing it doesn't
effect the outcome for me.
Current solution fix I have in place is the one Billias wrote. Just
cancel the broadcast and launch a new Intent.
This however doesn't feel right and could likely screw some other
applications over that also react to outgoing calls.
If this indeed is HTC's fault, I guess there will be no fix done to it
for a very long time, if ever.
A flag to enable the cancel broadcast+starting new Intent might be the
only way to go in this case
On Oct 1, 4:10 am, Denis Souza <denis.so...@gmail.com> wrote:
> Anyone had any progress or ideas with this?
>
> It's a bit hard to test it when you don't have the device.
> Anyway, I got two reports from Motorola users with the same problem...
> but the interesting thing is they only started having any problems
> after upgrading to my app's latest version.
> It occurred to me that the phone might have a limit to the time it
> waits for a response from the app (since my latest version does a few
> extra things before dialing) but I wrote a special super fast test
> version for one of the users and it still didn't work. Also I tried it
> on my HTC Hero making the phone wait 10 seconds but it worked fine,
> which means that's probably not the problem.
>
> Nicholas, you said you had the Desire with 2.2. Have you tried playing
> with the intent filter's priority values? Maybe using 1 or 0 or even
> removing the priority parameter altogether? That would be my next
> hunch.
>
> On Aug 27, 11:28 am, Denis Souza <denis.so...@gmail.com> wrote:
>
> > Just had a report a few days ago from a user on HTCDesire(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 <tobias.bil...@gmail.com> wrote:
>
> > > As it seems the HTCDesire(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 <tobias.bil...@gmail.com> 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 <denis.so...@gmail.com> wrote:
>
> > > > > I'm getting the exact same problem.
> > > > > I have an app that changes the number being dialed.
> > > > > It works on everything except theHTCDesirewith Android2.2. Works
> > > > > withDesireon 2.1 and with any other device I tested with2.2. There
> > > > > are reports from several of my users using2.2devices 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 <nicolas.z...@gmail.com> wrote:
>
> > > > > > Hello,
>
> > > > > > I'm having troubles with intercepting outgoing calls. In fact, it
> > > > > > works perfectly on emulator 2.1 and2.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
> > > > > >HTCDesireunder2.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 run2.2android 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
