Database Info

[KERNEL] Slide to Unlock

So I came across this in the EVO 3D forums. How hard do you think it will be to port this to our device?
http://forum.xda-developers.com/showthread.php?t=1346760

It is in development already. See bricked kernel thread for more info.
Sent from my Sensation

Anyway to enable this?

http://forum.xda-developers.com/showthread.php?t=1269247

And gnex has it

Both Bricked and TamCore have this feature.
Bricked: http://forum.xda-developers.com/showthread.php?t=1269247
TamCore: http://files.tamcore.eu/android/?dir=tamcore-kernel
Bricked gives you an option to enable it during installation, while TamCore requires you to flash a zip to enable it, which you can get on the same page, under the name "sweep2wake_enable.zip".

A few kernels already have it.

I am already using it... :angel:

Already using it on bricked!
It's nice because you don't have to constantly use your power button to turn on device ! I really love it! It's so easy.
Sent from my HTC Sensation 4G using xda premium

Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!

Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Sometimes it will pull up the power window, it will go back, back out of an app...instead of posting here...post in show-p threads.

It's a good feature, the bricked & faux kernels have it as far as I know!
Sent from my HTC Sensation Z710e using xda app-developers app

Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)

kgs1992 said:
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)
Click to expand...
Click to collapse
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.

Louer Adun said:
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.
Click to expand...
Click to collapse
There's a thanks button.
However, I don't see how this is practical much. I only lock using sweep because it's a good shortcut to exit current app, go to home & luck.

[Q] Pyr-O-Ice 1.1.3, Security lock

I would have posted this in that one help thread for pyroice, but it's about a month since anyone used it...
I just have a quick question. Since i believe 1.1.1 or 1.1.2 when i press the back button to wake it up, it now goes straight to the pattern unlock.
This used to happen with the menu button wake, and back would go to the slide to camera or pattern. Basically, now i don't have that basic lockscreen at all, whichever way i wake up the device.
any thoughts?
thanks!

anitgandhi said:
I would have posted this in that one help thread for pyroice, but it's about a month since anyone used it...
I just have a quick question. Since i believe 1.1.1 or 1.1.2 when i press the back button to wake it up, it now goes straight to the pattern unlock.
This used to happen with the menu button wake, and back would go to the slide to camera or pattern. Basically, now i don't have that basic lockscreen at all, whichever way i wake up the device.
any thoughts?
thanks!
Click to expand...
Click to collapse
Its just how it is. Menu/Back is a instant unlock. Using Menu when the phone is locked unlocks it(If screens on). I belive using the Lock Button will unlock to the Ring. But basic lockscreen is lost when using any protection. Just how ICS is.
It's Always Sunny in XDA

That's how Android has always been.
Posted from Spaceball One

Interesting... i just could have sworn that back in an earlier version of 1.1 i could press the back button, then slide and it would ask me for my pattern. regardless, thank you!

anitgandhi said:
I would have posted this in that one help thread for pyroice, but it's about a month since anyone used it...
I just have a quick question. Since i believe 1.1.1 or 1.1.2 when i press the back button to wake it up, it now goes straight to the pattern unlock.
This used to happen with the menu button wake, and back would go to the slide to camera or pattern. Basically, now i don't have that basic lockscreen at all, whichever way i wake up the device.
any thoughts?
thanks!
Click to expand...
Click to collapse
The menu button unlock was taken out in 113 on purpose. Phone would unlock in your pocket.

Anyone get widget locker to work with SGS3?

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

Galaxy S3 - Jelly Bean Update - Home Button Bug

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,

Waking the phone with home button

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