I'm currently running the latest version of widgetlocker on my nexus s 4g and it works like a dream only problem I'm having is if I'm at my home screen & i press the home button, then immediately the sleep button, then the sleep button again immediately to unlock my phone; widget locker doesn't load and i go directly to my home screen and this message box pops up:
"widgetlocker delayed by android due to recent home button press"
anyone know what could be happening? if i press the home button, press my sleep button, wait a few seconds, then press it again to unlock it works fine...
seems like if i try to unlock my phone too soon after i press the home button i get the error..
UPDATE:
i emailed the app developer about this and i just received the response... i followed his instructions and my problem is fixed.. here is his official response:
Android does not allow a background app to come to the foreground within 5 seconds of the Home button being pressed. If you are rooted you can enable WL Settings > Advanced > Root Helper to bypass this. Otherwise just don't press home, off, on, all within 5 seconds.
-Kevin
That, I believe, is being caused by the Android 5 second rule. If you look in the setting for WidgetLocker there is a way around that, but you will be setting WL to be the homescreen and WL will call forth your launcher. There is also a root method too, if you are rooted.
LudoGris said:
That, I believe, is being caused by the Android 5 second rule. If you look in the setting for WidgetLocker there is a way around that, but you will be setting WL to be the homescreen and WL will call forth your launcher. There is also a root method too, if you are rooted.
Click to expand...
Click to collapse
i emailed the app developer about this and i just received the response... i followed his instructions and my problem is fixed.. here is his official response:
Android does not allow a background app to come to the foreground within 5 seconds of the Home button being pressed. If you are rooted you can enable WL Settings > Advanced > Root Helper to bypass this. Otherwise just don't press home, off, on, all within 5 seconds.
-Kevin
LudoGris said:
That, I believe, is being caused by the Android 5 second rule. If you look in the setting for WidgetLocker there is a way around that, but you will be setting WL to be the homescreen and WL will call forth your launcher. There is also a root method too, if you are rooted.
Click to expand...
Click to collapse
What is the method of doing it if your phone is not rooted? (i.e. what do I have to press after selecting Settings?
Malonies said:
What is the method of doing it if your phone is not rooted? (i.e. what do I have to press after selecting Settings?
Click to expand...
Click to collapse
I would also like to know this.
widgerlocker home helper
The setting is in the advanced section it is called home helper.
You make home helper default home and then select witch launcher you want home helper to use.
Related
First off I'm new to the Gtab. I'm currently running Vegan 5.1. Everytime I hit my hard home button it takes me to a switchboard with four buttons. In order to get go my actual home screen I have to select the home icon. This is becoming extremely annoying hitting two buttons every time to get home. Is this normal or am I missing a setting?
What launcher are you using? There is usually a tab in the settings menu for what tapping the home key does.
I'm currently using the VLT launcher just released, but it does the same thing for stock launcher and launcher pro. I scoured the settings and can't find the home button setting. Saw it in Launcher pro but it didn't change anything. Not sure what else to try at this point.
The screen it sends me to appears to be the screen you see when you would place your phone on the dock. It has the alarm clock button, music, home, and gallery button on the bottom with only the time showing.
Button savior works correctly. Unfortunately I'm not a button savior fan. This its the only bug on my tab and its driving me nuts.
Just wanted to update. I read a lot of other Vegan users having this same issue. I ended up freezing the Clock app using Titanium and that corrected the issue. Not sure what other adverse effects that will cause but it worked for me.
Anybody have any other ideas how to fix this? I'm using TNT Lite 4.4 with Launcher Pro. I've set the home button to "Do nothing" in Launcher Pro preferences, and also checked the option that says "Home key to default screen" but neither one of those seems to have had an effect. Thanks!
Help!!!!!. How do I get out of full screen zeam?
I found the flag and set and now I now longer have the battery and navigation screen on the bottom so I can no longer go back to preferences and turn full screen off. I have button savior turned on but zeam does not recognize the menu button so I am stuck. I am running on a NC version 1.1.0 with Autonooter 3.0. Please Help. I find it pretty stupid that you can't access a menu to turn off full screen.
I usually assign an up swipe to show/hide the notification bar. Can you long press on the desktop and get a preferences menu?
Nope, I assume by upswipe, you mean swiping from the bottom up but that didn't work. Tried swiping right to left and tried the long press. Nothing happens. I guess I may have to restore the data file from titanium but I was hoping to find another way to this.
Long pressing on one of your home screens should bring up a menu that has 3 options: "Add Item", "Set Wallpaper", and "Preferences". Selecting "Preferences" should bring you to the Zeam Preference menu.
late,
Coz
cozboogie said:
Long pressing on one of your home screens should bring up a menu that has 3 options: "Add Item", "Set Wallpaper", and "Preferences". Selecting "Preferences" should bring you to the Zeam Preference menu.
late,
Coz
Click to expand...
Click to collapse
Thank you. I tried the long press on the main home screen and nothing happened. I had to go to the third page and then do the long press. I guess because I have some apps and widgets running on the main screen. Anyway I got it back. Thank you for your help.
I installed WidgetLocker (which I used on my old hacked HTC HD2). I've found one issue that disturbs me. If I turn on the SII with the Home button and press the same button a second time, the phone unlocks. I don't want the phone to unlock without a very deliberate action on my part. Does anyone know how to disable the Home button unlock "feature"?
Thanks.
-Bob-
Widgetlocker settings > Buttons & inputs > Allow menu button. Untick that option and i think it should do what you want.
Yep
Settings>Buttons & Inputs>scroll down and uncheck 'allow home button'
That should do it
Sp1tfire said:
Widgetlocker settings > Buttons & inputs > Allow menu button. Untick that option and i think it should do what you want.
Click to expand...
Click to collapse
Nope. Didn't work.
troffers said:
Yep
Settings>Buttons & Inputs>scroll down and uncheck 'allow home button'
That should do it
Click to expand...
Click to collapse
Nope. Didn't work.
Go to setting --> Advanced --> HomeHelper
Use HomeHelper and set the HomeHelper launcher to whatever home launcher you prefer. Then check HomeHelper Block Home. This ensures that it won't unlock if you click the home button again. Remember to use WL HomeHelper as your default Home Launcher.
If you want to return to lockscreen after you're done with an app (that you launched from WL, then check "Block Home in other app" aswell.
sorry if i am posting this in the wrong section
what i am looking for is a dev to write an app for me that would make it so whenever you tried to go to the home screen you needed to enter a password
Before it's closed... enable a lockscreen lock feature in the settings menu.
Questions go in the Q&A section - not the Dev section
it's not a question im asking a developer to write a small app for me and elegos im looking for when i exit the app not turn the device on
Bray90820 said:
it's not a question im asking a developer to write a small app for me and elegos im looking for when i exit the app not turn the device on
Click to expand...
Click to collapse
As the user above said you can enable the lock screen to have a pattern or pin to unlock it and set it to lock immediately after screen off via power button . So when your done browsing or using your tab you just push the power button to turn the screen off and it will lock automatically. So when you hit the power button to turn the screen on to use the tab again you'll be prompted for a pin/pattern. No need for a special app.
but i never said power button i said HOME button i dont want then to have access to the HOME screen
Bray90820 said:
but i never said power button i said HOME button i dont want then to have access to the HOME screen
Click to expand...
Click to collapse
There is an application called surelock available in market which locks down your system and stops people accessing the home screen and other applications. There is a free trial available.
When your done using the tablet push the power button which will power off the screen and lock the tab. They won't be able to access anything without entering the code/pin.
--Seacrest Out.
Hi, i have an international Galaxy S3 (i-9300). I recently updated to Jelly Bean via Samsung Kies (baseband version I9300DXDLI5) and there's a change that has been bugging me. In stock ICS, when the screen turned off due to inactivity, pressing either the power button or the home button would turn on the screen and lets me pick up where i left off. Now in JB, pressing the home button to wake the phone will take me to the home screen. Pressing the power button to wake the phone in both ICS and JB works as normal.
For example, I'm browsing the web on Opera Mobile. The screen times out and turns off. In ICS, when i press the home button, the screen would turn on and i could continue browsing. In JB, when i press the home button, the screen would turn on but take me back to the home screen. Pressing the power button works but the home button is bigger and easier to press.
Anyone knows a fix for this?
I'm running stock JB and not rooted.
Thanks so much
It's a known issue. There's no fix for it on the stock ROM, but there is a workaround - use a different launcher, such as Apex or Nova. The issue only affects the default Touchwiz launcher.
anthropolyte said:
It's a known issue. There's no fix for it on the stock ROM, but there is a workaround - use a different launcher, such as Apex or Nova. The issue only affects the default Touchwiz launcher.
Click to expand...
Click to collapse
Not true. I use Nova Launcher (the paid version) and I also experience this problem (or is it a feature?).
The workaround I found is to wake the phone using the POWER button instead of the HOME button.
I found a fix\workaround (no root needed) to this please see the following thread:
http://forum.xda-developers.com/showthread.php?t=1929953
looks like that wasn't a work around.
Any updates on this?
I don`t seem to have that issues.. Goes right back to whichever apps I was using. Tried a bunch of apps too.
The bug happens only if you have disabled S-Voice.
If you have S-Voice enabled (double press home button) then you will not encounter this bug. But the trade off is the Home Button action is delayed.
Yes its either you have to enable s-voice but I don't like this idea so I use jkay framework. In jkay framework the issue is solved along with many other features and mods. Try it out
Sent from my GT-I9300 using xda premium
carrd said:
I found a fix\workaround (no root needed) to this please see the following thread:
http://forum.xda-developers.com/showthread.php?t=1929953
Click to expand...
Click to collapse
It has fixed the home button kill app wake issue. Thanks a bunch
Sent from my GT-I9300 using xda app-developers app
I went through that thread from start to finish, the only suggestion was actually a workaround.
Basically enable S-Voice, but at the trade of slowing down your home button.
How did you fix the issue uronfire?