My reasons why I want to detect Sense UI (+ actually also other custom UI's) is that they have not implemented all of the nice shiny features that contact sync provides. They are not displaying the presence information in their default contacts app (People) and also are totally ignoring custom data rows there. As the app I'm developing relies heavily on these two features, there's no point in giving the end-users something that's half-working. I'd rather disable some features for all Sense UI devices (+ also other hacked-quickly-together OEM customizations).
Tauno On Tue, Nov 2, 2010 at 2:50 AM, Dianne Hackborn <[email protected]> wrote: > On Mon, Oct 4, 2010 at 7:24 AM, Denis Souza <[email protected]> wrote: >> >> 1) The call log won't allow updates. It strangely allows inserts but >> even though it lets you insert the phone number dialed it won't allow >> you to also insert the display name (if you do it stays as "unknown" >> and looks really awkward). I opened a discussion about this a while >> back and didn't realize back then that it only happened on Sense UI >> phones. Some people argued that you shouldn't touch the call log (even >> though there's nothing about that in the documentation). On the >> emulator and on non-Sense UI devices it works flawlessly (at leas on >> all of those that I've tested so far). My app need this to keep the >> original dialed number in the call log. In this case, when running >> Sense UI it's better not to touch the call log that to touch it and >> have it look awkward. > > 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. > >> >> 2) In particular HTC Desire with Android 2.2 won't allow you to change >> the number being dialed. >> (see thread: >> >> http://groups.google.com/group/android-developers/browse_thread/thread/1e23230cfaae5038/3fd980598e78c479?lnk=gst&q=desire+2.2) >> I do admit that in this case I'm not completely sure it's a Sense UI >> problem (I've seen it happen on Motorola devices but it was an easy >> fix, removing the priority setting from the Intent). I also had >> reports from Desire 2.2 users that had this working and one day, it >> just stopped to never work again. > > 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. > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- > 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 -- 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
