Related
Is there a way to lock the Dockbar, so when you swipe up while pressing on it, it doesn't disappear.
I checked the settings and didn't see anything to lock it down, but maybe I missed something.
Sent from my X10a using XDA App
System preferences/ swipe up actions.. you must have this set to show/ hide the dockbar.. also see this... http://forum.xda-developers.com/showpost.php?p=7135799&postcount=183
Thanks. I figured it out, I just needed to drag down while over where the dockbar was.
Sent from my X10a using XDA App
It would be nice though if there was an option to lockdown the dockbar.
Sent from my X10a using XDA App
RodneyBR said:
It would be nice though if there was an option to lockdown the dockbar.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Agree with you.
It needs to be lockable, and also being able to drag it up to open.
Isn't the author of this app an XDA member? maybe we should ping him to see what he thinks.
I thought the same as you two at first, being used to Helix Launcher and the default X10 Home where sliding the drawer up is key.
However, I've since changed a few settings - slide "Up" to enable/disable the Notification bar (because to me as the bar is at the top, sliding towards it to enable/disable seems logical), and slide "down" to enable/disable the dockbar.
When I first tried ADW I was constantly sliding the button by accident. Now I just press it. It took me about a day to get used to it. Now it's not a problem, because I know that even if I hide it by accident (with that initially-natural impulse to "slide the dockbar button up") I can get it back IMMEDIATELY with a quick slide-down on the screen.
I've also changed the drawer screens to one long vertical screen rather than the horizontal pages - this works MUCH better than the stock/Helix versions because it remembers the position you were in when you were last in the drawer. And it's much better than the crappy horizontal drawer where you have to be REALLY careful when flicking horizontally. I also think that - somehow - because the drawer works better this way, I am less inclined to "swipe" the button by accident when I want to activate the drawer.
So if anything I'd suggest -
1) Disable the dockbar hiding when accidentally swiping up on the button
2) Set "swipe up" & "swipe down" defaults as I mentioned above (as it seems more natural)
3) Set default drawer scroll to vertical rather than horizontal as it works sooooo much better.
Seriously, I know what you are both saying but once I had tweaked the settings it's not been an issue for me anymore. At all. And that surprises me as I was firmly in the "Helix Launcher FTW" camp for ages but now I love my ADW Launcher...
Hi.. rodney and aussie.. Are you taking about the dock bar or the action buttons? Sounds like your taking about the action buttons..
Ie.. The ones with the app drawer Button in the middle.
Think you can switch the dock bar off, which is "underneath" the action buttons, if you don't need it.
Sent from my X10i using XDA App
Well, I'm referring the actual Dockbar, not the icons within and and not about "swipe up" setting.
If you hold you finger on the Dockbar and swipe up it will disappear. That's fine, but for those that accidentally do it and don't want it to disappear, it just a nuisance. It would be great to be able to lock the Dockbar in place so it would not do this.
try this.. ADW settings, ui settings, [uncheck] Dockbar option...
Think this might solve your problem.
That seems to have worked, thx iceman
Sent from my X10a using XDA App
When you were swiping up before what you were actually doing was revealing the dockbar, which is hidden underneath the action buttons, however when you reveal it, it has no apps in it and so it looks like you've hidden your action buttons. If you want to try it.. Switch the dockbar back on, reveal it (by swiping up, as you know!) Then drag an icon down into what appears to be an empty space... That's your dockbar. To make it disappear and give you your action buttons back quickly touch the app icon and drag down.. Et voila..
Sent from my x10 using XDA and swype.
im_iceman said:
When you were swiping up before what you were actually doing was revealing the dockbar, which is hidden underneath the action buttons, however when you reveal it, it has no apps in it and so it looks like you've hidden your action buttons. If you want to try it.. Switch the dockbar back on, reveal it (by swiping up, as you know!) Then drag an icon down into what appears to be an empty space... That's your dockbar. To make it disappear and give you your action buttons back quickly touch the app icon and drag down.. Et voila..
Sent from my x10 using XDA and swype.
Click to expand...
Click to collapse
I actually figured out the drag up to make it disappear (LOL) and shortly after that the drag back down to make it reappear. But didn't try adding icons to what appears to be a dead space. Cool
ADW Launcher is amazing, but does have a lot of features, which takes a while to wrap your head around.
I set my home button to open and close the dockbar, I find that to be the fastest for me. I would really love if there was a back button binding as well, because when you are in the launcher the back doesn't really serve a purpose. I would totally put it to home screen. oh well.. still the best launcher I have seen.
I've set my home button to show me a "preview" of all 7 of my screens - felt a little odd at first, but I love it now.. 2 presses away from any screen.
Oh, is there a way to set whatever screen you want to be your home screen?
Sent from my X10a using XDA App
Yes - In Screen preferences - 3rd option down from the top - default screen..
Then you can change your home button binding (in system preferences) to "move to default desktop"
Yes - In Screen preferences - 3rd option down from the top - default screen..
Then you can change your home button binding (in system preferences) to "move to default desktop"
Worked perfectly, thx again Man, ADW is just amazing.
One feature I love is the ability to add more columns and rows. I set mine to 6 columns and 8 rows, using 3 screens. I just love having as many icons on one default screen as possible, then widgets on the others screens.
Sent from my X10a using XDA App
RodneyBR said:
Well, I'm referring the actual Dockbar, not the icons within and and not about "swipe up" setting.
If you hold you finger on the Dockbar and swipe up it will disappear. That's fine, but for those that accidentally do it and don't want it to disappear, it just a nuisance. It would be great to be able to lock the Dockbar in place so it would not do this.
Click to expand...
Click to collapse
*facepalm*
If you swipe it up it opens a drawer where you can put more icons, it doesn't disappear.
There's a new version of ADW out, but I can seem to download it via the marketplace. Anyone have a link to download it? Thx
Sent from my X10a using XDA App
I installed launcherpro and really it. when switching back and forth from twlauncher and launcherpro i accindently checked make twlauncher default when bottom home key is pressed. how do i undo that so it doesn't switch to twlauncher everytime I hit the home button at the bottom of the phone. Thanks
You must uninstall and re-install launcher pro.
Sent from my SGH-T959 using XDA App
You don't have to reinstall launcher pro. You can download an app called Home Switcher from the market. Its free
Sent from my SAMSUNG-SGH-I897 using XDA App
yes i have home switcher and it does not fix this problem. still everytime i press home (bottom row below the samsung). I should also note this is a froyo phone.
I have a question regarding LauncherPro also. To be safe, should I disable it, or uninstall it, before updating to JF7? I just got my new phone few days ago and still on JF6..
I switched mine to twlauncher just to be sure.
corrected by starting phone in recovery starting with vol buttons pressed and then deleted user data. had to set up phone again but oh well
technut963,
If this happens to you again, in Froyo all you have to do is click settings, applications, manage applications, on the top bar click All, then go down and click TwLauncher, then clear default. Then hit the home button and you should be asked what one you want to use and set it as default again.
I simply setup a shortcut that links to Activities -> TwLauncher and one for LauncherPro on the phone. As for adjusting the default see above.
mcx6 said:
technut963,
If this happens to you again, in Froyo all you have to do is click settings, applications, manage applications, on the top bar click All, then go down and click TwLauncher, then clear default. Then hit the home button and you should be asked what one you want to use and set it as default again.
Click to expand...
Click to collapse
thank you very much. works great. This site is the greatest,
i recently flashed prime 1.7 and the latest pcb theme - thanks to roach and scar for these kewl rom and theme -
One thing that seemed odd though, the home button aint workin, also, i dont have the slide function to unlock anymore.pressing the power button automatically wakes the tf. Havent noticed any1 mentioning this,so was wondering,is it just me or its the feature of these? This is my very first flashing of a rom and theme
any ides anyone?
I had the same issue this morning, I backed out to my home screen, then opened up tapatalk app. Then presses the recent apps button next to the home button and there was launcher in the list. After a picked launcher it started working again.
Sent from my HTC EVO 3D using Tapatalk
thanks for the response, but my issue seemed to be worst than what you had..guess i had a corrupted file or sumthin ..fixed it though by restoring to factory defs
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
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.