Related
I installed launcherpro and really it. when switching back and forth from twlauncher and launcherpro i accindently checked make twlauncher default when bottom home key is pressed. how do i undo that so it doesn't switch to twlauncher everytime I hit the home button at the bottom of the phone. Thanks
You must uninstall and re-install launcher pro.
Sent from my SGH-T959 using XDA App
You don't have to reinstall launcher pro. You can download an app called Home Switcher from the market. Its free
Sent from my SAMSUNG-SGH-I897 using XDA App
yes i have home switcher and it does not fix this problem. still everytime i press home (bottom row below the samsung). I should also note this is a froyo phone.
I have a question regarding LauncherPro also. To be safe, should I disable it, or uninstall it, before updating to JF7? I just got my new phone few days ago and still on JF6..
I switched mine to twlauncher just to be sure.
corrected by starting phone in recovery starting with vol buttons pressed and then deleted user data. had to set up phone again but oh well
technut963,
If this happens to you again, in Froyo all you have to do is click settings, applications, manage applications, on the top bar click All, then go down and click TwLauncher, then clear default. Then hit the home button and you should be asked what one you want to use and set it as default again.
I simply setup a shortcut that links to Activities -> TwLauncher and one for LauncherPro on the phone. As for adjusting the default see above.
mcx6 said:
technut963,
If this happens to you again, in Froyo all you have to do is click settings, applications, manage applications, on the top bar click All, then go down and click TwLauncher, then clear default. Then hit the home button and you should be asked what one you want to use and set it as default again.
Click to expand...
Click to collapse
thank you very much. works great. This site is the greatest,
It runs fine but if I hit the home button, it bypasses the lock screen and just goes to my home screen. The power button works, its just the home button issue. Can anyone share their settings for widget locker or let me know what I'm doing wrong.
Sent from my Nexus 7 using xda app-developers app
I've only been using Widget Locker for a couple of days but try this:
Go to the WidgetLocker app - Press the settings Icon on top right corner - Select Buttons & Inputs - Uncheck Allow Home Button.
See if that works.
I also have a question if anyone can help. How do I get Google now on the Jelly Bean Themed slider. I can get Google Now by setting the app in the unlock screen, but how do I make it look like the stock Google Now app?
Thanks
iPhoneSlayer said:
I've only been using Widget Locker for a couple of days but try this:
Go to the WidgetLocker app - Press the settings Icon on top right corner - Select Buttons & Inputs - Uncheck Allow Home Button.
See if that works.
I also have a question if anyone can help. How do I get Google now on the Jelly Bean Themed slider. I can get Google Now by setting the app in the unlock screen, but how do I make it look like the stock Google Now app?
Thanks
Click to expand...
Click to collapse
That worked thanks!
What's the jelly bean themed slider? If I can find it I can see if I can figure out your answer.
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
That worked thanks!
What's the jelly bean themed slider? If I can find it I can see if I can figure out your answer.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Glad I could help.
The slider I talking about is the slider to unlock the phone. You can chose from a list of slider like honeycomb, ICS, Jellybean, Sense, etc. I want it to look like my N7 tablet where if I slide it up, it goes to Google Now. I can still get Google now by adding the shortcut to google search, but I want the icon to look like the stock look. It's kinda hard to explain, sorry.
iPhoneSlayer said:
Glad I could help.
The slider I talking about is the slider to unlock the phone. You can chose from a list of slider like honeycomb, ICS, Jellybean, Sense, etc. I want it to look like my N7 tablet where if I slide it up, it goes to Google Now. I can still get Google now by adding the shortcut to google search, but I want the icon to look like the stock look. It's kinda hard to explain, sorry.
Click to expand...
Click to collapse
Oh okay yeah. I'm using the JB slider now. Mine has the stock looking "Google" for Google now. It just doesn't have the circle around the word " Google". I can post picture if you want.
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Oh okay yeah. I'm using the JB slider now. Mine has the stock looking "Google" for Google now. It just doesn't have the circle around the word " Google". I can post picture if you want.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Nevermind, I'm dumb. I've been trying to add it as a shortcut, but I should have used WidgetLocker Actions to choose google. Now it's all good.
Thanks
Oh alright good.
Ugh its not working now. Can you go into advance an go to home helper. What do you have there? I think that's regarding the home button. Its weird. Its off an on with it working.
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
Oh alright good.
Ugh its not working now. Can you go into advance an go to home helper. What do you have there? I think that's regarding the home button. Its weird. Its off an on with it working.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think Home helper is for some launcher settings.
If you uncheck Allow Home Button under the Buttons and Inputs, then it should work, however it may be a bug that sometimes causes it not to work. I've noticed that widget locker acts weird if the phone is charging. I have only been using it for a few days so I'm sorry if I wasn't more helpful.
tu3218 said:
It runs fine but if I hit the home button, it bypasses the lock screen and just goes to my home screen. The power button works, its just the home button issue. Can anyone share their settings for widget locker or let me know what I'm doing wrong.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem the other day. Particularly after I updated to 4.1.1. The lockscreen would unlock (once awake) by pressing home.
I solved it by using HomeHelper (widgetlocker settings -> advanced -> homehelper).
1) tick the "HomeHelper component" and choose "WL HomeHelper" as the default.
2) tap "HomeHelper's Launcher" and choose your default launcher (Touchwiz, Nova, AWG, Launcher Pro, etc.)
3) Make sure "HomeHelper Block Home" is checked.
4) (Optional) You can also choice "Block Home in other apps" to return to the lockscreen after opening apps from the notification bar or shortcuts.
HomeHelper worked fine for me, but I got the feeling it was slowing down my system a tiny bit. Most notably, the wallpaper would quickly blink every time I hit the home button (what is effectively happening is that the home button activates HomeHelper, that then activates the launcher). It was not a major deal but I personally found it annoying.
However, I may have stumbled upon the culprit behind all this: S-Voice. Once I upgraded to 4.1.1 I turned off the option to activate s-voice through pressing home twice (S-voice -> menu button -> Settings) because I was happy to use Google Now (aka Voice Search) instead. That is when I had the problem with widgetlocker's lock screen unlocking with the home button. After not liking HomeHelper's performance, I reluctantly went back to the default Touchwiz lockscreen (I maintained my custom launcher though, and reset the home button to default to it).
After Google Now failed embarrassingly to call the right people from my contacts list (most of whose names are foreign), I decided to go back to using S-voice. I reactivated the "press home twice" option. However, I still hated the "slide anywhere to unlock" Touchwiz lockscreen, as well as its inability to silence the ringer in one slide (you have to either hold the power button or open the notification bar first). So I went crawling back to widgetlocker for forgiveness. I activated widgetlocker (I did not meddle with the HomeHelper settings assuming those were already set), and later noticed that the lockscreen was not being unlocked with the home button, while the homescreen wallpaper was no longer blinking. I went into the homehelper settings and made sure it was turned off, and also made sure that the home button was by default linked to the custom launcher (not HomeHelper). I confirmed my theory by deactivating S-voice's double-press home option, and the problem above came back.
tl;dr. I theorize that the problem is caused by turning off S-Voice's quick-access option (double-press home). You can also use Widgetlocker's HomeHelper if you don't want to turn S-Voice back on. I hope my experience is not simply coincidence and someone could confirm this theory.
Found this thread because I was having basically the same problem. Widget locker's lock screen would be bypassed coming from sleep by single pressing home (power button from sleep continued to work normally). I could not fix this using any method mentioned here so far, except for enabling S Voice via double tapping home. I emailed the dev and hope it gets fixed, because I'd like to avoid the lag added to the home button by having double tap for S Voice enabled.
Anyone else have an alternate solution?
netter123 said:
Found this thread because I was having basically the same problem. Widget locker's lock screen would be bypassed coming from sleep by single pressing home (power button from sleep continued to work normally). I could not fix this using any method mentioned here so far, except for enabling S Voice via double tapping home. I emailed the dev and hope it gets fixed, because I'd like to avoid the lag added to the home button by having double tap for S Voice enabled.
Click to expand...
Click to collapse
Oddly enough this fixed it for me too. I had disabled S-Voice yesterday and today noticed that using the home button bypassed Widget locker. I re-enabled S-Voice and all is back to normal. Hopefully the dev will be able to give us an answer soon.
Agh ...I was so excited to get back to WidgetLocker I got used to from my pevious phone, only to find out this little anoying thing. Are there any news, some reply from the dev ?
So I am using widgetlocker, and my home button only wakes to my widgetlocker screen (never see the touchwiz lockscreen). I have s-voice/double-tap disabled.
In widgetlocker settings, under "advanced" I have root checker checked, homehelper component checked, "select system home" is widgetlocker, and "homehelper's launcher" is the launcher I use (nova in my case).
Does that not fix the problem for you all?
(On CleanRom 5.6)
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Does your launcher blink every time you press home button while in the launcher itself ? If yes, then you know why it does not work for us.
JustSomeDude said:
So I am using widgetlocker, and my home button only wakes to my widgetlocker screen (never see the touchwiz lockscreen). I have s-voice/double-tap disabled.
In widgetlocker settings, under "advanced" I have root checker checked, homehelper component checked, "select system home" is widgetlocker, and "homehelper's launcher" is the launcher I use (nova in my case).
Does that not fix the problem for you all?
(On CleanRom 5.6)
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No, these settings don't solve the problem for me. I messed with various combinations of the settings your talking about as well, but no matter what I still bypass the lock screen (and also experience a quick blink every time home is pressed, which would be a secondary concern). I'm also on the latest Cleanrom and use Nova.
netter123 said:
No, these settings don't solve the problem for me. I messed with various combinations of the settings your talking about as well, but no matter what I still bypass the lock screen (and also experience a quick blink every time home is pressed, which would be a secondary concern). I'm also on the latest Cleanrom and use Nova.
Click to expand...
Click to collapse
Hmm, strange... One more setting I have: do you also have "appear on boot" checked under Behavior? Otherwise I'm stumped as to why it works for me and not you.
As for the quick blink, yeah, I have that too - I assume from widgetlocker being assigned as home, thus registering that before going to nova - but I hit home so rarely that I barely notice it.
Sent from my SCH-I535 using Xparent BlueTapatalk 2
JustSomeDude said:
Hmm, strange... One more setting I have: do you also have "appear on boot" checked under Behavior? Otherwise I'm stumped as to why it works for me and not you.
As for the quick blink, yeah, I have that too - I assume from widgetlocker being assigned as home, thus registering that before going to nova - but I hit home so rarely that I barely notice it.
Sent from my SCH-I535 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yeah have that checked too. Must be some setting slightly different somewhere though. Not that big of a deal, I've just been living with the slight lag on home press and sounds like otherwise I'd have to get used to the quick blink.
Btw never got a response from the developer so that's kind of disappointing..
It's working for me but I get the annoying flicker when hitting the home button as well. It's a drag for sure. Go Launcher is my launcher. Shoulda did my homework before paying for this one. Love what the lockscreen can do but has issues with the home button for sure
Dothgar said:
I had the same problem the other day. Particularly after I updated to 4.1.1. The lockscreen would unlock (once awake) by pressing home.
I solved it by using HomeHelper (widgetlocker settings -> advanced -> homehelper).
1) tick the "HomeHelper component" and choose "WL HomeHelper" as the default.
2) tap "HomeHelper's Launcher" and choose your default launcher (Touchwiz, Nova, AWG, Launcher Pro, etc.)
3) Make sure "HomeHelper Block Home" is checked.
4) (Optional) You can also choice "Block Home in other apps" to return to the lockscreen after opening apps from the notification bar or shortcuts.
HomeHelper worked fine for me, but I got the feeling it was slowing down my system a tiny bit. Most notably, the wallpaper would quickly blink every time I hit the home button (what is effectively happening is that the home button activates HomeHelper, that then activates the launcher). It was not a major deal but I personally found it annoying.
However, I may have stumbled upon the culprit behind all this: S-Voice. Once I upgraded to 4.1.1 I turned off the option to activate s-voice through pressing home twice (S-voice -> menu button -> Settings) because I was happy to use Google Now (aka Voice Search) instead. That is when I had the problem with widgetlocker's lock screen unlocking with the home button. After not liking HomeHelper's performance, I reluctantly went back to the default Touchwiz lockscreen (I maintained my custom launcher though, and reset the home button to default to it).
After Google Now failed embarrassingly to call the right people from my contacts list (most of whose names are foreign), I decided to go back to using S-voice. I reactivated the "press home twice" option. However, I still hated the "slide anywhere to unlock" Touchwiz lockscreen, as well as its inability to silence the ringer in one slide (you have to either hold the power button or open the notification bar first). So I went crawling back to widgetlocker for forgiveness. I activated widgetlocker (I did not meddle with the HomeHelper settings assuming those were already set), and later noticed that the lockscreen was not being unlocked with the home button, while the homescreen wallpaper was no longer blinking. I went into the homehelper settings and made sure it was turned off, and also made sure that the home button was by default linked to the custom launcher (not HomeHelper). I confirmed my theory by deactivating S-voice's double-press home option, and the problem above came back.
tl;dr. I theorize that the problem is caused by turning off S-Voice's quick-access option (double-press home). You can also use Widgetlocker's HomeHelper if you don't want to turn S-Voice back on. I hope my experience is not simply coincidence and someone could confirm this theory.
Click to expand...
Click to collapse
Thank you. It is what i want
I have noticed since yesterday's Jelly Bean update (4.1.1) that if you have an app open (say a browser for example) and you let your screen timeout, when you press the home button it will turn the screen on screen up and take you back to your home screen. Used to with ICS it would just turn the screen on and you could continue in the app. Now it takes you all the way back home and you have to re-open the app to continue in it.
I was wondering if everyone is getting this same result or if it is just me.
Thanks!
I just tried it with Google Now and it returned to the app. I tried the Android browser and it returned the app as well. You might want to power down, pull the battery, then restart. Updates can sometimes act a little wonky at first. Occasionally (and unfortunately) a hard reset can FINALLY make an update work correctly.
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Yea, that fixed it. I don't like S-Voice so I had that option turned off. Apparently it works different with this update then it did with ICS.
I've actually went in there and enabled that option then went into Application Management and disabled S-Voice. Now, if I accidently double tap my home button it just goes to a black screen for a second then back to the home screen. (Better than opening up S-Voice)
Thanks for your help!
I've found if you use a pattern password the home button "feature", to go back home works like how it used to
Sent from my SCH-I535 using xda app-developers app
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
I find the lag to be to annoying when s-voice is enabled. A fast press of the power button will wake up the phone without closing the app you are using and you can keep s-voice turned off.
SlimSnoopOS said:
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
grr, I couldnt agree more. I turned off that feature to reduce home button lag in ICS, now it closes any app open. Hopefully theres a fix
We'll find out. I dislike these small, unnecessary changes that Samsung has implemented. Horizontal pinch to expand notifications is another unnecessary change on VRBLK3.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
aromig said:
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
lv2bsilly said:
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
Click to expand...
Click to collapse
I feel your pain i also suffer from this same problem i had ics stock rom upgraded to hpyer drive rl14 and after that my home button only wakes up to a long press nothing seems to work i even reassigned soft keys functions so home would do back option and same thing,
Has anyone else run into this? When I swipe up from the home button anywhere on the device, the shortcut for google now isn't working. I've been seeing this happen since Dev Preview 3 and now in the official release.
kevdawg said:
Has anyone else run into this? When I swipe up from the home button anywhere on the device, the shortcut for google now isn't working. I've been seeing this happen since Dev Preview 3 and now in the official release.
Click to expand...
Click to collapse
If I'm not mistaken "On Tap" has replaced the swipe up motion on Android 6.0. So have to hold the home button
jdawg0024 said:
If I'm not mistaken "On Tap" has replaced the swipe up motion on Android 6.0. So have to hold the home button
Click to expand...
Click to collapse
OH! Got it! Thanks. That was driving me nuts. You're right. I just confirmed it.
kevdawg said:
OH! Got it! Thanks. That was driving me nuts. You're right. I just confirmed it.
Click to expand...
Click to collapse
I can't get it to work. For me whether I hold down or swipe up it opens Now on tap. Only time holding home opens google is when Im on the launcher.
How can I get holding home to get me to google now anywhere?
thekalby said:
I can't get it to work. For me whether I hold down or swipe up it opens Now on tap. Only time holding home opens google is when Im on the launcher.
How can I get holding home to get me to google now anywhere?
Click to expand...
Click to collapse
+1
thechamp007 said:
+1
Click to expand...
Click to collapse
That isn't an option anymore, you have to launch "On Tap" then you will notice the google logo you can touch that and it will take you to google now
Ron Amadeo pointed it out here: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/3/
One of the downsides to Google Now on Tap is that the opening gesture—long pressing the home screen—used to belong to Google Now. There's no way to quickly open Google Now from any screen anymore. You have to go to the home screen and swipe left. The gesture also once allowed you to have a third-party home screen and still easily access Google Now, but you can't do that anymore, either. One option is to disable Now on Tap completely, and then the old Google Now gesture will work.
Click to expand...
Click to collapse
I hate this new feature, I want "swipe up" back . I used before swipe up to lock phone and hibernate apps (greenify ). Now I need to use again button. So oldscool
Not sure if this is related but when I say "OK Google" from the home screen, Google Now appears instead of the voice input. Is there a way to fix this?
Thanks
jdawg0024 said:
If I'm not mistaken "On Tap" has replaced the swipe up motion on Android 6.0. So have to hold the home button
Click to expand...
Click to collapse
And I'm hating every minute of it. I like to read the stories and open hidden apps from the google now and is annoying to do it that way. I guess that in their perfect universe everyone uses the google now launcher and it had no utility...
I'm glad I'm not the only one that hates it
Sent from my Nexus 6 using XDA Free mobile app
It's also kinda wonky for me because I'm using Nova Launcher. I've compared by switching to the Google Now launcher and the long press home actions act differently. Sometimes on Nova it's smooth but on the home page, it just kinda freaks out and either gives you options or just goes directly to my Google Now cards. I also preferred that swipe up action, seemed easier and made more sense.
I also liked the swipe up gesture for Google Now. I wonder if custom ROM's that allow customization of the swipe up short cuts will still have it in their builds.
Sent from my Nexus 5 using Tapatalk
I can't get down with the swipe to the left for now and love Nova launcher. For a few minutes after setting it up I was going crazy trying to figure out why swipe up wasn't working.
I just installed ota of Android M and used to have a Tasker job run when dragging up the home button. This would allow me to lock the screen as if I hit the power button. Was a good way to eliminate a button press. Is there anyway to get similar functionality?
Sent from my Nexus 5 using Tapatalk
dbldown768 said:
I just installed ota of Android M and used to have a Tasker job run when dragging up the home button. This would allow me to lock the screen as if I hit the power button. Was a good way to eliminate a button press. Is there anyway to get similar functionality?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah it's gone for me too. Found a bunch of subreddits, and everyone says theirs is gone too.
But Nova Launcher has a gestures feature, you can assign swipe up to anything you want, but it only works on the home screen.