Related
I'm usually one who doesn't like to sit and wait around having to hold a button to get something to work, and I don't usually have a heavy hand so I prefer a very short press and hold period. Is there any way to modify how long we have to hold down the home button to see the recent apps?
I changed the home button action in nova launcher so that it first goes to my main home screen. If it is already there a single press of the home button opens the recent apps list.
Sent from my SCH-I535 using xda premium
But what about if you aren't already at your launcher? Say... you're using Chrome and want to go to recent apps, right now it takes a press an hold of around 2 seconds or so. I would like to know how to change this to reduce it to a second or perhaps less.
In that case I hold it until the recent apps shows up. So I guess nova launcher settings only help if you're not in an app.
Sent from my SCH-I535 using xda premium
But that's exactly my point, is that right now you just hold it until recent apps shows up, which is like two seconds. To me personally, this is too long. I usually have quick hands and do everything really quickly, the long press I use for Swiftkey is set to 200ms. This is why I think it would be nice to change the recent apps to maybe a second or so, I'm just not sure how to go about doing this.
noingwhat said:
But that's exactly my point, is that right now you just hold it until recent apps shows up, which is like two seconds. To me personally, this is too long. I usually have quick hands and do everything really quickly, the long press I use for Swiftkey is set to 200ms. This is why I think it would be nice to change the recent apps to maybe a second or so, I'm just not sure how to go about doing this.
Click to expand...
Click to collapse
I was thinking of the same sort of thing before discovering Sheffy007's nav bar thread. I now think the nav bar is a more elegant solution.
If you're not a fan of the Nav Bar, you could study the changes he made to the key files and possibly swap home and recent apps (pressing home brings up recent apps, holding home brings up the home screen).
http://forum.xda-developers.com/showthread.php?p=30048716
Sent from my SCH-I535 using xda premium
Would a launcher help this issue?
Couldn't you set the double click assigned to the siri like Samsung voice to go to recent apps instead? That would be much faster...
Sent from my SCH-I535 using xda app-developers app
On cm10 I have my recent apps set to long press menu, it's less annoying than holding the physical home button just my. 02
Sent from my SCH-I535 using xda app-developers app
I'm fine with the use of the long press home button for recent apps, I just wish I didn't have to hold it for so long, although a double press wouldn't be bad either.
It seems like this should be an easy fix though, if we can just figure out where the file is that says to wait 2000ms before bringing up the recent apps, it should be as simple as changing that to a smaller number, shouldn't it?
noingwhat said:
I'm fine with the use of the long press home button for recent apps, I just wish I didn't have to hold it for so long, although a double press wouldn't be bad either.
It seems like this should be an easy fix though, if we can just figure out where the file is that says to wait 2000ms before bringing up the recent apps, it should be as simple as changing that to a smaller number, shouldn't it?
Click to expand...
Click to collapse
I looked through the SQL Lite DB on my device (TW based ROM), /system/usr/keylayouts and decompiled framework-res.apk, twframework-res.apk, and SystemUI.apk. I briefly looked through everything and the closest thing I could find was in framework-res/res/values/integers.xml
<integer name="config_longPressOnHomeBehavior">2</integer>
I don't think that's it, but it's worth a shot (nandroid first). Anyone else know where button duration is set?
I think this closely relates to what mybook already found, but I found this in framework-res/res/values/public.xml:
Code:
7946 | <public type="integer" name="config_longPressOnHomeBehavior" id="0x010e001d" />
Still has nothing to do with the duration, but it might be able to lead us to the duration.
I've noticed since flashing CM10 that the long press seems to much quicker, around a second or so, meaning this must be possible somehow.
I was searching for the exact functionality when i got to this thread, and I was disappointed. Surely someone in XDA can accomplish something like this?
I was hoping there would be a file somewhere in the root dir that holds the settings to this long press duration in an integer. Something like the sys/class/leds/led-backlight/brightness file that sets the softkey brightness to zero, effectively turning it off, which is really useful for night reading.
Has still nobody figured it out? :crying:
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 all, I've just flashed JB.
I've seen some things I didn't expect (probably they depend on the phablet interface) which I don't like so much.
1 - long press the home button doesn't open mini task manager anymore
2 - the useful customizable soft button (you could use it to take screenshots, access the drawer and so on) has gone
3 - long press the recent apps soft button doesn't open the drawer anymore
Any ideas? Is JB really better than ICS?
Thanks
Try going into your settings, and look for system launcher i think... I don't remember what it is called. But in the settings, under the device section, it should be there i think. If you do find it, look for system options and softtouch keys. There you can set your own buttons and have what they do if you hold it. Sorry for bad instructions. I don't have a device to see where its located at.
IMO, Jelly Bean is better than ICS. Because Jelly Bean has project butter, making everything so smooth and clean.
I tried to look everywhere, but there's nothing about soft keys.
Thanks anyway.
Sent from my GT-P3100 using xda app-developers app
Anyone found a solution? Maybe some app?
I really miss the mini task manager of the home button (now it opens Google Now, which I really don't care about).
Sent from my GT-P3100 using xda app-developers app
the task manager soft button is not a big deal. you can get it from the Quick Launch (far right arrow)
Maybe someone knows how to edit homescreens now? There's no menu button on the homescreen
deejayzee said:
Maybe someone knows how to edit homescreens now? There's no menu button on the homescreen
Click to expand...
Click to collapse
tap and hold homescreen...
If I want to delete a homescreen, what should I do?
Pinch screen and then you can delete unneeded
syazmie97 said:
the task manager soft button is not a big deal. you can get it from the Quick Launch (far right arrow)
Click to expand...
Click to collapse
Yes, I know, but with ICS it was easier (1 tap less). I could use the quick launch anyway.
Same thing for the drawer, I could keep pressed the recent activities button to acces it directly; now (when I'm not in a homescreen) I have to press the home button and, then, the app button in the dock.
Usually I suppose that a more recent OS release has some improvement, not a drawback.
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,
I just flashed my One X to Carbon ROM, like it alot so far but having an issue, in some apps the action overflow button pops up on the screen (the three little stacked dots) but on others it does not and i have no way to get to the settings. i.e. i have autoguide app. you need the menu or action over flow button (which ever you chose to call it) to open a search to search specific forums and threads, ALSO i have photobucket app, you need the button so that you can select different albums. is this a rom issue or am i missing a settings button somewhere?
You need to remap the recent apps button to be the menu button, go to Settings/Carbon Fiber/Interface/Buttons. I think that's the right location anyway.
Sent from my Evita
Thanks I found this option shortly after posting, any idea why some apps pop up with the 3 buttons and some don't?
Sent from my One X using Tapatalk
It depends on the coding per app. Some apps have the overflow button even when there's a physical menu button, but on other apps it disappears when it detects a physical menu button.
Sent from my Evita