Related
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
When I turn the screen on to check notifications and i expand a notification: text, facebook message, etc..
Even while my finger is touching the screen the screen turns off. This occurs both in power save mode and with power save mode turned off.
Its quite annoying, especially if i just want to read real quick what an email says.
Anyone else getting this?
Nope. Try doing a hard reset
Tried a second s6 and resetting the device. I get the same thing. I also have the unlock effect turned off.
My phone is also giving me problems on the lockscreen. I don't have an unlock effect either so I'm thinking be the problem. I notice when I turn on any other option my problem goes away. It just darkens my wallpaper to almost black. Did a hard reset as well.
I also noticed a huge lag when i tap a notification and then try to unlock. I'm also unable to double tap a notification on lock screen to open that specific app.
I tried using the buble unlock affect and still get the same problem. turn on screen->expand notification of given app while still holding my finger on the screen, then seconds later screen turns black
tlxxxsracer said:
I also noticed a huge lag when i tap a notification and then try to unlock. I'm also unable to double tap a notification on lock screen to open that specific app.
I tried using the buble unlock affect and still get the same problem. turn on screen->expand notification of given app while still holding my finger on the screen, then seconds later screen turns black
Click to expand...
Click to collapse
I see what you're saying about holding the finger on the screen and it still times out. Is it not like this on other lollipop phones, this is my first go with lollipop so I don't know? ...No lag for me, and I can tap then unlock and I'm in the app asap.
Sent from my SM-G900T using AllianceR(●)m
tenxo said:
I see what you're saying about holding the finger on the screen and it still times out. Is it not like this on other lollipop phones, this is my first go with lollipop so I don't know? ...No lag for me, and I can tap then unlock and I'm in the app asap.
Sent from my SM-G900T using AllianceR(●)m
Click to expand...
Click to collapse
Well maybe its cause i came from an AOSP rom on my Lg g2 but i would think if your finger it touching the screen it should stay on anyways.
I wish i could just double tap the notification and it opens the app versus tapping the notification and then having to swipe to unlock.
the lag when trying to unlock after tapping the notification is a little, its not instant like how it would when tapping on a heads-up notification
tlxxxsracer said:
Well maybe its cause i came from an AOSP rom on my Lg g2 but i would think if your finger it touching the screen it should stay on anyways.
I wish i could just double tap the notification and it opens the app versus tapping the notification and then having to swipe to unlock.
the lag when trying to unlock after tapping the notification is a little, its not instant like how it would when tapping on a heads-up notification
Click to expand...
Click to collapse
I just tried again...If you swipe down on the notification to read it, it should go up to like another screen (not literally) but the notification slides up basically were the clock and weather would be. There it doesn't time out until the screen time out you have set under display is reached, and you can read the other notifications too. What you are doing is pulling down the notification without letting go then it times out. Swipe the notification and let go of the screen.
Sent from my SM-G900T using AllianceR(●)m
Hi everyone! I have a Sprint HTC One A9. The quick settings (swiping down on the screen with two fingers or swiping down twice from the status bar) all of a sudden disappeared. I can still see the notifications panel when I swipe down, but just can't see or edit the quick settings. The button in the top right (which I believe originally let you edit the quick settings) does not do anything when I press it. I have no idea how/why this happened, and there does not seem to be another way to get to a quick settings editing option/menu. Any ideas? Thanks in advance!
We have never been able to edit the quick settings on our A9. That top right button simply just toggles the quick setting on and off (does the same thing as swiping up and down).
Newcron said:
We have never been able to edit the quick settings on our A9. That top right button simply just toggles the quick setting on and off (does the same thing as swiping up and down).
Click to expand...
Click to collapse
Newcron, thanks for your response! Here's the thing: the top right button, when I press it, it does nothing -- there's no reaction or toggling of the quick settings. It doesn't look like some of the pictures I've seen (it looks like a gear over the three lines, whereas I think others just see three lines?). When I press it, and try to swipe down to see the quick settings, it doesn't work. I've tried everything -- my quick settings just up and disappeared! It's been driving me crazy because I have to go into the settings to turn wifi, bluetooth, location, etc. on/off each time. If anyone has any ideas what I might have done or what to do, please do let me know. Thanks very much!
frankfrank12 said:
Newcron, thanks for your response! Here's the thing: the top right button, when I press it, it does nothing -- there's no reaction or toggling of the quick settings. It doesn't look like some of the pictures I've seen (it looks like a gear over the three lines, whereas I think others just see three lines?). When I press it, and try to swipe down to see the quick settings, it doesn't work. I've tried everything -- my quick settings just up and disappeared! It's been driving me crazy because I have to go into the settings to turn wifi, bluetooth, location, etc. on/off each time. If anyone has any ideas what I might have done or what to do, please do let me know. Thanks very much!
Click to expand...
Click to collapse
And I just realized that I have lost all notifications too -- no notifications show up in the notifications panel/drawer (even when I'm receiving notifications). It just says "no notifications." Ack, I have no idea what I did. Should I just reset the phone?
frankfrank12 said:
Newcron, thanks for your response! Here's the thing: the top right button, when I press it, it does nothing -- there's no reaction or toggling of the quick settings. It doesn't look like some of the pictures I've seen (it looks like a gear over the three lines, whereas I think others just see three lines?). When I press it, and try to swipe down to see the quick settings, it doesn't work. I've tried everything -- my quick settings just up and disappeared! It's been driving me crazy because I have to go into the settings to turn wifi, bluetooth, location, etc. on/off each time. If anyone has any ideas what I might have done or what to do, please do let me know. Thanks very much!
Click to expand...
Click to collapse
Well that is a little weird. The icon is correct, though. If I swipe once, it shows all my notifications, with the icon picture is a gear over the three lines. If I tap on that icon, it's the exact same thing as if I swipe down, the quick setting now shows up, and the icon changed to just three lines. If I tap on the three lines icon, then quick setting goes back up (and out of view), showing me my notifications again.
I'm not sure what happened to your phone, but that's pretty strange!
frankfrank12 said:
And I just realized that I have lost all notifications too -- no notifications show up in the notifications panel/drawer (even when I'm receiving notifications). It just says "no notifications." Ack, I have no idea what I did. Should I just reset the phone?
Click to expand...
Click to collapse
My A9 is now doing the same thing. Did you ever find a fix?
I'm not really sure what my question is related to, but I'm sure it's a stupid one. This is my first phone with softbuttons. My previous phones were Samsungs, which had capacitive buttons. My last phone was a Note 3, which was still on Lollipop. I had always assumed that softbuttons were simply an on-screen version of what I was used to, but the behavior is different. Not sure if that's related to the newer OS, or what. The left capacitive button brought up the menu in the app, which was often redundant to an on-screen menu option within the app, but not always. For example, in Facebook, clicking the left button would bring up several options, logging out being one of them. On the Mate 9, there's a back button, which does the same thing as the back capacitive did, there's a home button, which does the same thing the main home button did, but the square button brings up the recent app list. On my Samsung, that was done by holding the home button. So there doesn't seem to be an equivalent to the menu button I had on the Samsung.
So the short question is: how do I bring up that short blue menu in Facebook with the option to log out?
There is no button menu,you have to logout from fb menu.
So, the little quick menu in Facebook that has Logout, Settings, About, and Report a Problem is only available on phones that have capacitive buttons? You have to wade through the much longer list of options within the Facebook app to find those things? It seems odd there isn't a softbutton equivalent. Or at least an option to add one.
For some reason Google thinks the menu buttom was useless and they got removed. Even Samsung phones now doesn't have it.
On the Mate 9 you have option for Back, Home, Recents, Notifications (optional).
Swiping left/right will turn on 'reachability' mode. Holding Home brings up Google Now/screen search. Holding Recents will activate split screen mode.
Sent from my MHA-L29 using XDA Labs
Even exist a floating button with home , recents,block and back options. You can activate it from quicksettings
Enviado desde mi MHA-L29
Ah yes the floating dock.
Sent from my MHA-L29 using XDA Labs
Lodix said:
For some reason Google thinks the menu buttom was useless and they got removed. Even Samsung phones now doesn't have it.
Click to expand...
Click to collapse
Ah, ok, so this is really an issue of me being used to Lollipop, and moving to Nougat. I wasn't sure what the cause was. Thanks!
dscline said:
Ah, ok, so this is really an issue of me being used to Lollipop, and moving to Nougat. I wasn't sure what the cause was. Thanks!
Click to expand...
Click to collapse
Well Google never implemented the menu buttom in the software-ones, just home/back/multitasking.
Looking for HELP with a feature. Im comming from the s10 plus. I always used the function TAP to Swipe feature which is used for tapping to answer phone calls instead of sliding to answer. Its an option in the assistant menu. If you go to settings> accessibility> interaction and dexterity> assistant menu on> single tap to swipe… it can be turned on. But the problem is you cant get rid of the menu completly. On the s10 plus we was able to do this and hide it. Only option to hide it is slightly as an edge option.
Anyone know how to get rid of it completly while still allowing tap to swipe for answering phone calls?
I read your question over and over and looked at your screenshots and I really cannot work out what you mean.
.
apprentice said:
I read your question over and over and looked at your screenshots and I really cannot work out what you mean.
.
Click to expand...
Click to collapse
Instead of swiping to answer phone calls you can just tap the answer button. Its activated thru the assisted menu. But when you activate it… it leaves a circle menu on the screen that you can put anywhere on the screen. There is an option to move it to the edge panel. You can see it on the picturr here i have it in the top right corner. On my s10 plus you can completly hide it while still being able to tap amd answer phone calls instead of sliding it to answer. Its called SINGLE TAP TO SWIPE.
OK, I am with you now.
I just checked on my Note 10+ and it's the same.
You can however hide the panel by dragging it to the top of the screen to the X that appears, this places the menu in the notification area, so although it cannot be hidden completely at least it no longer blocks your screen.
Once in the notification area, if you tap and hold the notification and then the gear icon, you can minimise it further there.
Hope this helps somewhat!
.
apprentice said:
OK, I am with you now.
I just checked on my Note 10+ and it's the same.
You can however hide the panel by dragging it to the top of the screen to the X that appears, this places the menu in the notification area, so although it cannot be hidden completely at least it no longer blocks your screen.
Once in the notification area, if you tap and hold the notification and then the gear icon, you can minimise it further there.
Hope this helps somewhat!
.
Click to expand...
Click to collapse
Its the same on the s10 plus which is what i am comming from. Youll get a accessability notification in the pull down bar but that can also be illiminated. On the note 20 ultra however when you hold down on the panel… there is no hide option. The only option im seeing is to put it on the edge panel… which is better but you can still see it.
I have the Note 10+ and use the Assistant Menu button to use single tap to answer calls. I could hide the button by holding and dragging it to the top of the home screen and releasing it when I see the X. Worked great. I recently updated my phone and it now has One UI 2.5. I cannot now hide the Assistant Menu button when I drag it to the top. Looks like the hide function has been removed. I don't like this at all. I don't like having to move the button around the screen to avoid interference with text, graphics, games, etc. Samsung needs to correct this ASAP!
You can either purchase "package disabler pro" and disable the accessibility app. Or you can go to settings>apps>all apps> scroll to accessibility then force stop the app and clear cache. It will stay hidden until you restart the phone. Make sure you have the single tap setting enabled first before you do this
black96ss said:
You can either purchase "package disabler pro" and disable the accessibility app. Or you can go to settings>apps>all apps> scroll to accessibility then force stop the app and clear cache. It will stay hidden until you restart the phone. Make sure you have the single tap setting enabled first before you do this
Click to expand...
Click to collapse
Bro i cant thank you enough. I have package dissabler already and it worked. U are the man. Appreciate it very much.
Now i just need to get the ok google ding sound when you wake google by voice.