I just ran into this issue after finally getting my hands on a Cliq.
My workaround for now was the following:
// if blur contacts exist, kill process to avoid force close in 1.5,
// assuming its fixed in non 1.5 update
if((Integer.parseInt(Build.VERSION.SDK))==3){
try {
// checks to see if package exists, caught and ignored if not
blur
getPackageManager().getPackageInfo("com.motorola.blur.contacts", 0);
((ActivityManager)getSystemService
(Context.ACTIVITY_SERVICE)).restartPackage
("com.motorola.blur.contacts");
} catch (NameNotFoundException e) {
} catch (Exception e){
}
}
Probably not the best solution but I didn't put much effort into it
given the low volume of Cliqs I've seen download my apps. Btw, I also
love (not) the non-standard Android behavior... but that's for another
thread.
Oh yeah and it seems to recover well:
01-30 16:08:25.093: INFO/ActivityManager(95): Start proc
com.motorola.blur.friendfeed for service
com.motorola.blur.friendfeed/.FeedReceiverService: pid=16306 uid=10007
gids={3003, 1006}
01-30 16:08:25.273: INFO/ActivityManager(95): Start proc
com.motorola.blur.news for service
com.motorola.blur.news/.NewsRetrievalService: pid=16309 uid=10007 gids=
{3003, 1006}
On Dec 29 2009, 6:24 pm, "jak." <[email protected]> wrote:
> Hello Suzanne,
>
> I'm glad to hear that there is a fix in the works for this bug.
> Are you aware that there is also a bug when using the create intent?
>
> Intent(Intent.ACTION_INSERT,Contacts.People.CONTENT_URI);
>
> This does allow me to create a new contact, but the result it sends
> back to my onActivityResult callback is useless.
>
> >> protected void onActivityResult(int requestCode, int resultCode, Intent
> >> data) {}
>
> Whenever the user is done creating a contact, I get a call to my on
> activity result with resultCode set to 0 (AKA: RESULT_CANCELED), and
> data is null;
> Even though the contact creation was successful!
>
> This is not the default Android behavior.
> When a user uses this intent to create a new contact, the
> onActivityResult should pass a -1 for the result (AKA: RESULT_OK).
> And the Intent data should contain a Uri to the newly created contact,
> accessible via data.getData().
>
> Since Motorola's implementation of contacts sends back RESULT_CANCELED
> for any contact insert, there's no way for our App that started the
> Intent to know when we have a valid result to act on.
>
> If Motorola completely re-implements parts of the Android OS, I really
> wish they would be careful not break the programmer interfaces.
> It makes us developers look bad when our Apps don't work on your
> devices when It really isn't even our fault.
>
> Thanks for your help.
>
> On Dec 2, 1:19 pm, "suzanne.alexandra"
>
> <[email protected]> wrote:
> > I'm happy to say this bug has been fixed and is expected to be
> > released toCLIQusers in an upcoming OTA upgrade. I would anticipate
> > early next year for this.
>
> > --
> > Suzanne Alexandra
> > Motorolahttp://developer.motorola.com
--
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
