I'm not sure how it happened but now when I press the home button it sends me to the wrong home screen. Instead of returning me to the center home screen it returns me to the screen to the right of what is supposed to be the center home screen. I can be on the center home screen and hit the home button and it sends me to the one just to the right. Any ideas? It started doing this after I let a friend of mine play with the phone and they have no idea how they did it. I'm downloading the instructions as we speak.
It depends on how many home screens you have. If you have 4 or less, then it always tries to send you to the farthest right one. Its annoying and an android thing, not a galaxy thing.
You have to reset what you want the default home screen to be.
Sent from my SAMSUNG-SGH-I897 using XDA App
MendedEagle said:
You have to reset what you want the default home screen to be.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
In TouchWiz I don't think there is an option for setting the default home screen (otherwise there wouldn't be a mod for it in which you have to root). I know this topic has been dead for a while, but if there is some way to set the default, that would be great to know. Otherwise I'm sticking with LauncherPro.
http://forum.xda-developers.com/showthread.php?t=734151
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
This also seems to send home key to the device. e.g. you have browser open and turn off. Then wake up with home. This also goes to the home page and browser is not active anymore.
Is there anyway around this?
ECrispy said:
This also seems to send home key to the device. e.g. you have browser open and turn off. Then wake up with home. This also goes to the home page and browser is not active anymore.
Is there anyway around this?
Click to expand...
Click to collapse
I just opened browser, pressed power button, used home key to turn back on and it opened to browser.
CleanROM
ECrispy said:
This also seems to send home key to the device. e.g. you have browser open and turn off. Then wake up with home. This also goes to the home page and browser is not active anymore.
Is there anyway around this?
Click to expand...
Click to collapse
Yeah, it's pretty annoying. Do you have s voice disabled? If you do, enable it and go into the settings. Click the option that says "open via the home button". That said work.
Sent from my SCH-I535 using xda app-developers app
I don't want to enable S-Voice since it causes home button lag. So I guess this is not fixable?
andybones said:
I just opened browser, pressed power button, used home key to turn back on and it opened to browser.
CleanROM
Click to expand...
Click to collapse
Did you have to unlock first? If you lock and try it quickly, so the lock screen doesn't come up, then you can see this.
ECrispy said:
Did you have to unlock first? If you lock and try it quickly, so the lock screen doesn't come up, then you can see this.
Click to expand...
Click to collapse
If you don't mind flashing roms, any aosp rom will fix the issue, but i think most touchwiz roms will have it. You should also ty checking the option to open via the home button in s voice then making google the default app that opens on double click.
andybones said:
I just opened browser, pressed power button, used home key to turn back on and it opened to browser.
CleanROM
Click to expand...
Click to collapse
I use old CleanROM (v2.1) and it works like your explanation. But when I upgrade it to lastest CleanROM (v5.6), the Home button will work just like the OP said. It will NOT only wake the phone up, but also close/minimize the browser (so I rollback to the old CleanROM) ...
I've noticed the same behavior in CR 5.5.1 and 5.6. If I go to Settings>Lock Screen and set 'Lock Automatically' to any time X, if my screen goes off and I hit the home button before X time passes, the screen will wake and will go to the home screen. I always have SVoice off but I'll try messing with the settings mentioned above...
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Last night, my AT&T HOX discharged completely. I'm thinking it might have reset and went into a constant bootloop, but I'm only guessing. So I plugged up to the charger and let it get charged about 10% before really messing with it. So rebooting the phone led me to a "frozen" screen. At first I thought it was the Picture Password Lockscreen app so I uninstalled it. No change.
I then realized it wasn't a frozen screen (although the slow start up continue after each reboot, but the home key would not function. Menu button will function, so would the back button. Only problem was that despite having the haptic response from the keys, I couldn't get to the home screen. It was just a white screen at and the notification bar at the top. The only way I was able to get a launcher to open was due to the Play Store notification that allowed me to open my ADW launcher from the app list. I installed a home switcher, but still, could not get the home button to work. The hepatic response was back, but it would not yield going directly to ADW as my default launcher, nor select one once I cleared defaults. So I dirty flashed my ROM (Venom XL 3.2.6) and again got the slow start and the inability fort he home key to bring me to the homescreen (or the option to select). I then thought the perhaps it was an issue with the kernel, but still the same thing occurs after flashing the stock kernel. I get the haptic response and the screen does a quick flash. Nothing else.
Has anyone encountered this before or have any idea what controls this function and how to fix it?
From launcher, check your hone button settings, preferences-gesture settings. Check Home key - it should say that it is set to Show home screen. If that doesnt work check to see if in pocket detection is enabled. If it is, try disabling.
Sent from my HTC One X using xda premium
Venomtester said:
From launcher, check your hone button settings, preferences-gesture settings. Check Home key - it should say that it is set to Show home screen. If that doesnt work check to see if in pocket detection is enabled. If it is, try disabling.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the tip, but I couldn't get it to work. Had to end up wiping data. Thanks anyway.