What to do when other 'Home' app crashes? Reboot only?

by Kakyoin » Wed, 11 Mar 2009 14:00:53 GMT

Sponsored Links
 Hi. I should post this as a follow-up to my previous thread.

But I think this problem (may be) somewhat big so I create a new

1. If a user install an alternative to 'Home'. (I'll call it 2nd Home)

2. He set this 2nd Home to launch by default for 'Home' action.

3. Whenever this 2nd Home crashes, their only choice is to reboot the
system... ?

Because, after setting 2nd Home as default,  the 'chooser' will not
come out any more even if you press the 'Home' button.

In some case if this 2nd Home crashes in its initialization state,
user can go no where, can't even go to Settings -> Manage App -> Clear

Am I missing something?

Thank you in advance.


What to do when other 'Home' app crashes? Reboot only?

by Kakyoin » Wed, 11 Mar 2009 15:35:11 GMT

 Hi. Thank you that's cool and will help users escape this situation.

But I wonder if we can handle this by code? Somewhere in the 2nd Home

All I can think of is doing this when error occurs:

               Intent i = new Intent();
                Intent choose = Intent.createChooser(i, "Forced chooser");

This will create out own chooser containing 2 choices: 'Home' and '2nd

This work quite well but when 2nd Home is NOT the default, and user
press the Home button -> there'll be 2 choosers up on screen. Up to
this point it's not a serious(dead-lock) problem now. But it just
looks weird having 2 choosers on the screen, one on top of the other.

I wonder if there's any other solution?

any opinions are welcome.

Thank you in advance. =)

Sponsored Links

Other Threads

1. alsa support in android

Has anyone integrated alsa support in Android Eclair?

unsubscribe: android-porting+unsubscr...@googlegroups.com

2. apk: i Music Tao

file ini desember 2009.



3. read mail and get money

4. shootme FC mulu nih

5. Root itu apa dan perlu ngak? Baca disini:

6. apk: doodledroid *enwan ready*

7. apk: midomi