I have a crazy problem I could use some help with. I was trying a few different kernels on the new TMOUS 4.3 update including various button mods and somehow I lost all Google Now actions from Home button. I tried reboots, swapping the Gestures options in Settings, Xposed Framework Mods, and even reflashing the stock Kernel. The button vibrates on long press but does nothing. Even remapping the button with the Sense 5 Toolbox does nothing. It's really bizarre. Has anyone seen this or knows a fix without reflashing my entire system partition from TWRP (I smartly made a backup)? I've done a lot of customizations I don't want to have to redo. Any help is greatly appreciated!
I am having the same problem with my home button. It does nothing on long press (doesn't even vibrate) even though it is set to Google Now. I've tried the same things you have but haven't been able to fix it. If anyone knows what the issue is please help! Thanks.
As a work around I have used the Xposed Frameworks and Sense Toolbox to add Google Now to a long press on the back button. It's a quick and dirty fix but the home button failure is troublesome. There has got to be a container that maps the function of long press to the apk. Maybe you should try the Xposed/Sense Tool box Mike and see if you can remap your Home to GNow (or trigger a reset to it). It didn't work for me but I at least get the vibrate confirmation that it wants to do something. Also did you notice all of the kernels (or one of them also perm effected this too) force the vibrate intensity to 2000 (too low for my comfort)? Even flashing stock didn't restore that. You can barely feel the motor and I had to install TrickDroid from the market to reset the value on boot. >_< Is that a build.prop mod or something?
Related
So, if you were following my other thread (which I doubt anyone was since no-one offered help), I managed to fix my incredibly hard soft brick
Everything's running great now, except the menu key isn't functioning. This would be fine, except the 3dot menu xposed module is causing other problems when installed and I'm not running a CM ROM so I can't simply make it double press the home button for menu or anything like that.
So I actually need to get the menu button working, not find an alternative. I can't seem to find the number of the button tho. I know you can check with CWM but I don't have it and don't want to risk stuffing up my phone again right now because I will be relying on it pretty heavily for the next week or so. How can I remap the menu button so it can be used as the menu button if I don't know the hard key number? International S4 Active, thanks.
You can try here
http://forum.xda-developers.com/showthread.php?t=2534697. In the Aroma Installer, there's is a button fix of sorts, used on the i537 in safestrap, so we could use regular s4 roms, soomewhere else, don't remember where, the is the button .zip file, by itself.
Sent Via Smoke Signals
tiskael said:
So, if you were following my other thread (which I doubt anyone was since no-one offered help), I managed to fix my incredibly hard soft brick
Everything's running great now, except the menu key isn't functioning. This would be fine, except the 3dot menu xposed module is causing other problems when installed and I'm not running a CM ROM so I can't simply make it double press the home button for menu or anything like that.
So I actually need to get the menu button working, not find an alternative. I can't seem to find the number of the button tho. I know you can check with CWM but I don't have it and don't want to risk stuffing up my phone again right now because I will be relying on it pretty heavily for the next week or so. How can I remap the menu button so it can be used as the menu button if I don't know the hard key number? International S4 Active, thanks.
Click to expand...
Click to collapse
You should be able to flash the keys fix in the MasterPatch that @captaincado posted above. For the actual key numbers see below.
Code:
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 172 HOME
key 139 MENU
key 158 BACK
Good luck.
Just an update, I followed all the instructions, couldn't get this working. It's possible that the button just happened to physically break when I flashed the ROM but it doesn't matter, because I found All in one Gestures (link below) which I used to replace the menu button... and then every other button, plus some. It's really good, I recommend it to anyone who has trouble reaching certain button, has a broken button or would just wants to have a go at increasing speed:
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en
Hi, everyone
Recently I started using the Cover Lockscreen on my samsung S Advance which is a great alternative to the stock lockscreen. However I got this annoying behavior when waking up my phone with the home button because systematically I get back to the home screen and then losing my last app position.
After searching in the forum I found that other users (Note2 and S3) are reporting the same behavior about the home button when waking the phone up with a lockscreen. And I tried the next advised solution:
First with R/W root permission, one should open the file /system/usr/keylayout/gpio-keys.kl
Then inside the gpio-keys.kl the last line must be edited to change from "key 172 HOME WAKE" to "key 172 HOME WAKE_DROPPED"
In theory this should fix the problem but in fact on my S Advance it doesn't work. Then I wanted to ask if anyone has a better solution or any clue to solve this frustrating behavior.
At the moment my single solution is to deactivate the home button while the screen is off. This can be done if the last line in the gpio-keys.kl doesn't include the "HOME" word. This means that I can only wake my phone with the Power button which it is still not very ergonomic to my taste.
INFO: I'm using a stock Jelly Bean ROM 4.1.2 (XXLQE), the Co-core 8.2 Kernel and LightJB.
I hope you can help to figure out how to fix it.
Thanks in advance
SOLUTION: Xposed Additions Module
The fix can be done using the Xposed Additions Module.
Actually it's pretty easy:
-Install / Enable the Adittions Module inside Xposed Framework and Reboot.
-Open Xposed Additions and go to the last menu option "Buttons"
-Remap [HOME] and choose the condition "Screen Off / One click Action / Power". Voila! you're done.
I thoughtI I had to live forever with that issue. Thanks and all the credit to the developer.
Hi guys,
I am looking for a reliable way to remap the camera button. The end result should be like on stock ROM, but with a camera app of my choosing. Meaning, i press the camera button when the screen is off or the phone is locked, and a camera app pops up immediately.
I got pretty close with Tasker, but it's still not there - I need to manually unlock the phone.
My device is rooted, my bootloader is unlocked, I already flashed a ROM trying to solve this (Omni) and I don't mind flashing anything else to try and fix this. So, open to any suggestions -- apps, tasker profiles, ROMs, config changes, you name it.
I already tried the Additional Actions xposed module but that doesn't work either.
Any ideas? There has to be some way to do this... It's just a button.
Details of the device
I'm using the latest CM11 version from Novafusion.
Problem and steps I've taken
Currently I've got a problem where the home button intermittently activates on its own (but only long-presses, so if I disable long-press in the OS, it'll be fine for normal operation), without any interference. The side effect (which is my main issue) of this is that it means my phone's screen effectively turns on by itself 24/7, which is obviously bad for many, many reasons.
I'm asking whether there's anyway I can disable the home button? I've tried Android-HomeKey-Locker (can't link it, but the Google Play version of the thing on GitHub) but it hasn't done anything.
I'm aware I can turn on the software buttons, but they don't deactivate the physical buttons: and I only want to disable home anyway.
So my question is, is there any way of doing this? I can take the back and menu keys if needed.
Side note
Is it possible in anyway to bind long-press back to home? I asked this for CM12 a while back (and I've since downgraded), but is this possible with Cyanogen, as I've been able to do it with Carbon ROM on 4.4.4.
Hi! I currently use this app on CM 12.1 to enable softkeys and disable hardware keys:
https//play.google.com/ store/apps/details?id=net.alviano.android.softbuttons&hl=en
sorry for my bad english
Hi
Try disable the home button by following this. it worked for me
http://forum.xda-developers.com/showthread.php?t=2032117
Hey everyone,
Thanks for the help. Someone on reddit gave me a working solution by using Xposed Additions to remap the buttons how I wanted them to.
Hi everyone,
I will try to stay as clear as possible. I do not like "swipe to unlock" or something like it, what I like is to click power button to lock and unlock my android. But I noticed that lots of the time I accidentally press this power button for example in my pocket or even when I am walking holding it in my hand... So I have an idea to wake/unlock the phone not by pressing the power button once, but pressing it twice to unlock/wake the device...
Till now I have just been playing with simple tasker tasks, but this one seems to be difficult for me. Any ideas is it possible? Tried to look for app which could do like this, but couldn't find any. I own rooted Nomu S30 Android 6.
All ideas appreciated!
hi friend, I don't think Tasker can do this. Maybe you should check out some Xposed modules for that, since you have root, and this looks like system level controls.
alienyd said:
hi friend, I don't think Tasker can do this. Maybe you should check out some Xposed modules for that, since you have root, and this looks like system level controls.
Click to expand...
Click to collapse
I have xposed on my android (Nomu S30, original ROM), but it seems that modules does not want to work... It says like "module activated" but actually it does not work at all, atleast those I have tried just does not work... Any ideas about this?
sorry, I cannot assume anything generally , you probably should check with Xposed to see what happens. It could be that:
- Framework not yet active
- Device not yet restarted
- Compatibility issue
- Wrong module/usage
Maybe an app like Proximity Lock/Unlock will help.
How about gestures in wake up?