> Given that the CallLog is I believe a public API, the manufacturer breaking > it makes it not CTS compatible and they need to fix it. You should very > much treat this as a bug with HTC's device and push to have that fixed. One > thing you could do is file a bug in the bug tracker with sample code showing > the problem. Even better would be to contribute a patch to CTS that ensures > the API is working correctly, so this won't break in the future.
Great! I'll look into that. > Are you talking about the API to intercept outgoing calls? If so, again > it's a public API that if broken makes the device not CTS compatible. I am > surprised about this one since Google Voice relies on it so it seems like I > would have already heard about any significant issue in this area. Yes, it's exactly the API to intercept outgoing calls. Although it works well on most devices, some have very strange issues. I found out that on Motorola devices, for example, it will work perfectly if you don't set a priority on the intent filter for the NEW_OUTGOING_CALL action. If you do set the priority the problem becomes intermittent (tried it with several different values). Some users will report it working well and others with the same exact device will report it not working at all (I had access to a device in which it didn't work and found no other software that could be causing a conflict). As for the HTC Desire with Android 2.2, it's a mystery to me. I had reports of older versions of my app working on it and then not working anymore after a reinstall. Newer versions didn't work at all. My app displays the number being dialed on a toast right before returning from the broadcast call. The number displayed on the toast is always the exact same as set on the call to setResultData() (I even declared the variable as final to make sure I wasn't changing it) and still the number won't change (even though returning null does cancel the call). I have no idea what to make of it and had to use a workaround in which I cancel the call and make a new call. I'd really like to be able to file a bug report on this but I have no idea what's causing it or how to reproduce the problem with 100% certainty on any device. As I said before it might not be a Sense UI specific problem (I have an HTC Hero and never had any issues with that). If I had a device that had this problem maybe I could dig a bit deeper. There are a few users willing to run some tests that I send them but I think I've already pushed their patience a little too much ;). -- 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
