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
Related
anyone have a mod that does this?
sorry if this is in the wrong place. i'm new here.
I don't know of a patch for that yet, but I'm sure it's possible.
If we had CyanogenMod for the Charge, it would be baked into the ROM.
Someday ...
I would like to see this. possibly even disable the quick press options of the power button and reassign them to another combination. I hit the button all the time trying to do other things on the phone and then I get locked out and have to redo my pattern etc.
Widgetlocker app can do this for you.
Using Root Explorer or possibly Estrongs file explorer:
>Go to system>usr>keylayout>s3c-keypad.kl
>modify key 50 to look like this: HOME WAKE_DROPPED
>Then reoboot
Now home key wakes device!
UPDATE: Seems after it is asleep for a period of time it won't wake it anymore, have to work this out.
What application do we use to edit the value? A text editor? What do you suggest?
I use Root Explorer Long press open in text editor,
I think you can do the same with estrongs file explorer.
>DARKMAN< said:
I use Root Explorer Long press open in text editor,
I think you can do the same with estrongs file explorer.
Click to expand...
Click to collapse
Sorry for the unnecessary request. I see it is in the other post.
It seems as though the front keypad module is not active once it goes completely to sleep, there for won't wake it.
If someone can figure this out, it will work just fine.
>DARKMAN< said:
Using Root Explorer or possibly Estrongs file explorer:
>Go to system>usr>keylayout>s3c-keypad.kl
>modify key 50 to look like this: HOME WAKE_DROPPED
>Then reoboot
Now home key wakes device!
UPDATE: Seems after it is asleep for a period of time it won't wake it anymore, have to work this out.
Click to expand...
Click to collapse
Definite thanks for looking into it. I'll try the app that bill mentioned and see if it makes a difference. I haven't yet rooted so I don't think I can do your version yet even if it works.
billku said:
Widgetlocker app can do this for you.
Click to expand...
Click to collapse
Are suggesting this because you have this on your Droid Charge and it is currently working correctly?
The reason I ask, is I tried a couple weeks back and could not get it working correctly.
I have it on my Charge. It works intermittently. I found that if the phone is asleep for a little while it usually does not work... occasionally it does work but no consistent pattern.
I'm also looking for a better fix than the app.
Suggestions are greatly appreciated!
The same thing happens when you just modify the key mapping, it's because the front keypad module is off when the phone sleeps.
So if it could be activated at all times that would fix it, but I imagine it may have some side effects to battery life.
This will disable the lock screen for good. After you do this fix you can wake up the Droid by briefly pressing the power button and it will go immediately to the home screen without any lock screen madness.
Go to Dialer and enter *#83786633, then press the home key
Go back into the Dialer, clear those numbers, then *#22745927
Now a screen will appear asking for the SPC Code, enter 000000
Press the Hiddenmenu Enable radio button, then press home button
To disable the lock screen (and power down pop up), go back into the Dialer and use the code *#7594#, select Shutdown and press the Home button. This, I have confirmed, does work on the Charge.
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.
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,
This is a request for home button bug fix on the GS3 Verizon.
If there's no easy fix I'm going to have to go back to 4.04.
BUG: home button takes user to home screen instead of just turning the screen on.
Event: screen turns off, before phone locking, and user presses the home button to turn the screen back on. But user is taken to the home screen instead of just lighting the screen back up on existing app.
More evident on Nova launcher where if user presses home button after screen shuts off it takes them to screen selector.
This bug is annoying enough for me to go back to 4.04. I've just have about had it.
This Bug on the Jelly Bean OTA release is infected all of the custom roms.
Not sure if the fix is difficult.
I don't have that problem....
Sent from my SCH-I535 using Tapatalk 2
devilchrist said:
This is a request for home button bug fix on the GS3 Verizon.
If there's no easy fix I'm going to have to go back to 4.04.
BUG: home button takes user to home screen instead of just turning the screen on.
Event: screen turns off, before phone locking, and user presses the home button to turn the screen back on. But user is taken to the home screen instead of just lighting the screen back up on existing app.
More evident on Nova launcher where if user presses home button after screen shuts off it takes them to screen selector.
This bug is annoying enough for me to go back to 4.04. I've just have about had it.
This Bug on the Jelly Bean OTA release is infected all of the custom roms.
Not sure if the fix is difficult.
Click to expand...
Click to collapse
I'd be willing to bet that you don't have Svoice installed. I need more info. What ROM? Apps?
sent telepathically
jdub251 said:
I'd be willing to bet that you don't have Svoice installed. I need more info. What ROM? Apps?
sent telepathically
Click to expand...
Click to collapse
Like he said, install / push S-Voice. Fixes the issue.
BTW - this is probably the wrong place to post this question.
Been super busy at work but, i have OTA. Not any custom roms. So I do have SVoice installed.
if i'm the only one with this issue, then it may take a trip to Verizon store i guess to get a replacement.
devilchrist said:
if i'm the only one with this issue, then it may take a trip to Verizon store i guess to get a replacement.
Click to expand...
Click to collapse
go into s-voice.. press menu..
settings...
UN-tick "open via the home key"
problem fixed.
Please read forum rules before posting
Development is for developers to post threads
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
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.