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
Hi,
I'm currently using Nova Launcher which has a settings to remap the home button when on the homescreen.
You can map it to a Nova settings, an app or a shortcut.
I currently have it mapped to a Secure Settings shortcut that lock my phone.
The issue I'm having with this settings, it's that it does not respect the delay locking option I have set on my security settings (5 min).
I'm looking for a way to map the home button to something that would shutdown the screen but respect the locking delay like the real power button does.
Any suggestions ?
Thanks.
Its because you're locking the phone in secure settings. Power button turns of the screen. So its a different action.
Which are you using by the way? Dev admin action > lock device or root actions > power button lock?
Not sure how different they are. Essentially you need to look to turn off screen not lock device
Sent from my Nexus 5 using Tapatalk
rootSU said:
Its because you're locking the phone in secure settings. Power button turns of the screen. So its a different action.
Which are you using by the way? Dev admin action > lock device or root actions > power button lock?
Not sure how different they are. Essentially you need to look to turn off screen not lock device
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi haven't payed for the Pro Upgrade so Power button lock is not available to me.
I know it's because I'm using the Lock Device feature, that because I cannot find another option that simply simulates the power button press.
Can someone confirm to me that "Power button lock" in Secure Settings would provide me with the right feature ?
Thanks.
I don't have pro. You're rooted though I guess? Dalvik or ART?
Can use xposed + gravitybox in nova as a shortcut to set device to sleep. This allows the delay to work
Sent from my Nexus 5 using Tapatalk
rootSU said:
I don't have pro. You're rooted though I guess? Dalvik or ART?
Can use xposed + gravitybox in nova as a shortcut to set device to sleep. This allows the delay to work
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes ! Thanks a lot !
Hi,
I'm looking for a way to power off the One without using the power button (I don't want to wear it out!). I expected there to be a tile I could add to quick settings but I can't find one.
I've tried installing a shutdown/reboot app but as I'm using quick boot, these apps do a 'full' shutdown which is not what I want.
Have I missed something or is this functionality missing?
Thanks.
You could use terminal emulator or tasker to make a script/task to shutdown and make a shortcut on your home screen.
Sent from my One Plus One
Double tapping the notification bar will turn the screen off. Don't know if that's what your wanting thought .
Sent from my A0001
Quick boot is a setting in dev options that is sort of like hibernate. When you power off the phone, it can be booted back up in 2 seconds.
Sent from my A0001 using XDA Free mobile app
If I knew what the command was to put the device into quick boot hibernation then yes I could write a script.
Yes I know about double tapping the notification bar to put it to sleep (turn off the screen), and yes I also have the double tap to wake. But I'm still having to press the power button to 'power off' (I realise most people don't do this very often!).
Thanks...
pda1ey said:
If I knew what the command was to put the device into quick boot hibernation then yes I could write a script.
Yes I know about double tapping the notification bar to put it to sleep (turn off the screen), and yes I also have the double tap to wake. But I'm still having to press the power button to 'power off' (I realise most people don't do this very often!).
Thanks...
Click to expand...
Click to collapse
Which ROM are you one? Im using liquid smooth and I have that option if I long press on the go to sleep tile
sent from my amazingly awesome OnePlus One
don't forget to hit thanks!
abhi08638 said:
Which ROM are you one? Im using liquid smooth and I have that option if I long press on the go to sleep tile
sent from my amazingly awesome OnePlus One
don't forget to hit thanks!
Click to expand...
Click to collapse
I'm using the standard CM11S. I tried adding that sleep tile but long pressing it just takes me to the display settings page. I'd have been happy if that had worked!
Thanks anyway.
I use nova launcher. I use a gesture. double tap associated with screenoff app to turn off the screen. Double tap wake double tap in the home turn off the screen.
Hi All,
So I have a very odd issue. I have googled and searched the threads, but I cannot find any mention of the same issue from anyone else. Here is my problem:
When the screen is completely off (I have "Always On" turned off), sometimes when I push the power button the lock screen does not come up. Instead, I can barely make out tiny white text at the very bottom of the display that is half cut off. Obviously I cannot take a screenshot to show you. So I push the power button a couple of times and then it works.
Anybody have a clue what is going on?
Thanks in advance!
Dave
dmmoroney said:
Hi All,
So I have a very odd issue. I have googled and searched the threads, but I cannot find any mention of the same issue from anyone else. Here is my problem:
When the screen is completely off (I have "Always On" turned off), sometimes when I push the power button the lock screen does not come up. Instead, I can barely make out tiny white text at the very bottom of the display that is half cut off. Obviously I cannot take a screenshot to show you. So I push the power button a couple of times and then it works.
Anybody have a clue what is going on?
Thanks in advance!
Dave
Click to expand...
Click to collapse
Do u use greenify?
Sent from my Samsung SM-G955U using XDA Labs
I do! What setting can I change to resolve this?
dmmoroney said:
I do! What setting can I change to resolve this?
Click to expand...
Click to collapse
Auto hibernate. Just make a home screen shortcut and tap it B4 u lock your device
Sent from my Samsung SM-G955U using XDA Labs
I must be an idiot. Can you clarify? That sounds like an annoying extra step to have to tap an app prior to each time I lock my phone. Maybe I'm misunderstanding?
that text is greenify is working sign ..
when you press power button when it's working, you won't get screen wake. Need to wait until it's finished,
or press power once (to stop greenify process) then wait a little while until text disappears.
dmmoroney said:
I must be an idiot. Can you clarify? That sounds like an annoying extra step to have to tap an app prior to each time I lock my phone. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
No it's a hibernate shortcut you don't actually open the app. just tap it and it'll put everything to sleep then just lock your phone. I don't use auto hide unless I have root. On nonrooted phones it takes forever to do it when you go to lock your phone and in my case it would take forever for me to be able to unlock my phone so I find it easier to just tap the shortcut then lock
Note the lil icon in the bottom right. It just puts stuff to sleep, doesn't open the app
Sent from my Samsung SM-G955U using XDA Labs
crayonyes said:
that text is greenify is working sign ..
when you press power button when it's working, you won't get screen wake. Need to wait until it's finished,
or press power once (to stop greenify process) then wait a little while until text disappears.
Click to expand...
Click to collapse
Also what he said, it's normal but slow
Sent from my Samsung SM-G955U using XDA Labs
buttsak said:
No it's a hibernate shortcut you don't actually open the app. just tap it and it'll put everything to sleep then just lock your phone. I don't use auto hide unless I have root. On nonrooted phones it takes forever to do it when you go to lock your phone and in my case it would take forever for me to be able to unlock my phone so I find it easier to just tap the shortcut then lock
Note the lil icon in the bottom right. It just puts stuff to sleep, doesn't open the app
Sent from my Samsung SM-G955U using XDA Labs
Click to expand...
Click to collapse
this!
I'm also using the hibernate&sleep shortcut widget,
and disable auto hibernate because of this long wait time.