When pressing "home" button, sometimes the "Complete Action Using..." screen comes up

[Rudementry]

Nothing a hard reset won't fix.

 

[joe003m2]

i think its the task switcher

So, I'm having the same problem. And, have noticed I can make my phone "forget" its default home by pressing and holding the home key until the task switcher pops up. Not sure yet though if that is the one and only culprit .

 

[Mustachio]

A Sprint tech support guy had me go through some updates and even made a slight tweak in the hidden settings screen (forget what the name is) and now my EVO never forgets the default home launcher. nice.

 

[Chinoo]

I was having this problem after installing Lock-Bot, i dont know if any of you guys installed this, but anyway it got fixed after unistalling Lock-Bot.

 

[kaivorb]

Unfortunately, my issue is still there, AND it was BEFORE I installed LockBot (which I use and enjoy). I would hate to have to uninstall that app just to fix this (especially since it existed BEFORE the app was there), but I might give it a try to see if it at least is a way of solving the problem (just not an ideal one).

I would definitely like to fix this annoying little pop up.

K--

 

[meyerweb#CB]

Try this:

Go into manage applications and find HTC Sense. Tap to open, then tap the "Clear Defaults" button. Now tap the home button again. It should ask you to select the action. Choose Sense.

It seems the default settings has gotten confused somewhere. This will hopefully reset it so that it's consistent.

 

[Disgustoid]

Unfortunately none of the advice in this thread worked for me.

I found a tip on Android Forums to remove the QIK update which seems to have fixed my "Complete Action Using" problem. Not a big deal considering I don't use QIK.

Hope this helps someone.

 

[Mughato]

+1

Just uninstalled the Qik update and now the Launcher default stays put.

http://forum.androidcentral.com/htc...-update-kills-launcher-default-selection.html

 

[Nate#AC]

I had this same issue and it was driving me nuts. It also turned out to be a Qik update that broke it for me... don't think I would have figured it out without this thread. Thanks