I'm trying to replace the stock lock screen with my own app
In my code, i want to disable the Home button.
I know how to do this in Android 2.3 and below,
but the same code doesn't work with Android 4.0+ (return to desktop when Home button pressed)
Recently I found out an app called MiHome which has its own lock screen and is able to disable the Home button.
Does anyone know how it achieves this???
sam80180 said:
I'm trying to replace the stock lock screen with my own app
In my code, i want to disable the Home button.
I know how to do this in Android 2.3 and below,
but the same code doesn't work with Android 4.0+ (return to desktop when Home button pressed)
Recently I found out an app called MiHome which has its own lock screen and is able to disable the Home button.
Does anyone know how it achieves this???
Click to expand...
Click to collapse
i'm have same issue
Please help
Related
Hello together
I have a little problem with my HD2. I have the Goatrip 6 ROM installed with Cookie´s Home Tab 2.0 and S2U2 2.43. The problem is that S2U2 don´t lock the long press end key.
There is a not choosable option in S2U2 2.43. "Don´t lock long press end key"
I need a program who locks the long press end key similar with the lockscreen. Do anybody know a program? Thanks for your help.
I don't think it is possible.
The normal/official rom lock (with the slider or hd mini version) doesn't lock it either.
It's probably something to do with that key being the power key, that it will have priority over everything else to allow you to power off. All keys are able turn the screen on, but long press send key doesn't work while locked, maybe because it's a hack and not standard.
bbobeckyj said:
I don't think it is possible.
The normal/official rom lock (with the slider or hd mini version) doesn't lock it either.
It's probably something to do with that key being the power key, that it will have priority over everything else to allow you to power off. All keys are able turn the screen on, but long press send key doesn't work while locked, maybe because it's a hack and not standard.
Click to expand...
Click to collapse
I think u could remove it by closing Endkey.exe.... But u cannot block it just for S2U2...
Hi! Is there any way to make a different button than the Powerbutton, turn the screen on? It's uncomfortable to always press the Powerbutton to activate the Lockscreen.
Thank you!
AD
ad2003 said:
Hi! Is there any way to make a different button than the Powerbutton, turn the screen on? It's uncomfortable to always press the Powerbutton to activate the Lockscreen.
Thank you!
AD
Click to expand...
Click to collapse
if you are on cyanogenmod or blayo's rom, trackball for screen on is already activated
i use "widgetlocker" you can find it on the market, and there is an option to use the volume keys also for screen on
widgetlocker is a paid app, but it allows allot of customization for your lockscreen
how to use the home key idk
hope this helps a bit
thanks - I'll give it a try! ;-)
Using: [ROM][RC3][24.07.2011] Gingerbread 2.3.3 with HTC Sense 2.1
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.
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?
Hello
Is there a possibility to disable shortcut by long-hold home button? I'm using custom lock screen app (holo locker) and when i'm waking up phone with home button, always appears manager instead lock screen, even when i only click once button. I hate this bug.
Thanks from advance and cheers.