Hello gentlemen.
I have been tinkering with my setup (nav keys especially) ever since getting my s8+.
My question here - after applying "gemu.hw.mainkeys=1" to my build.prop to eliminate the navbar (replaced by button gestures) the pressure sensitive home button does not work anymore during normal operation.
It does however still work from the sleeping state, to wake the device, so I am thinking it is still receiving input
Is it possible that after removing the navbar, the associated action, triggering the home button is removed ? There is no haptic feedback whilst pressing the area after unlock, only while in locked/sleep mode.
Is there any way to assign a function to the action of pressing the area through editing generic.kl ? Or am I missing something here.
Thank you in advance.
Related
Using Froyo, the volume hard buttons on my Nook color are hardcoded to Back and Menu functions. I have looking for a way to add full-time volume softkeys OR find a way to make long presses on the volume buttons change the volume. Another option would be to have volume controls in the notification bar and keep the bar open all the time.
Button Savior has the ability to have full-time softkeys, but nothing for volume (that I know of).
Any ideas?
You could use ClutchPad for this. There's just one item on the screen, but you could set swipe up to be volume up and swipe down to be volume down.
Thank you. I got it to work, but it's a little slow and the up/down swipes are a little difficult to perform correctly. I don't know why it's slow to access the volume controls, but I think the swipe difficulty may be due to the Nook's screen edge sensitivity. Overall, though, I'm very happy to finally have a solution. Thanks again.
Is it possible to remap the action invoked by pressing the Back and Home buttons? Or can it be removed? Like long-press Back acts as the Home key. And long-press Home pulls down the notification bar?
It's annoying because I always press Back to exit an app, not Home. And sometimes it lags so a tap of the Back key registers as a long-press and actually sends me Home.
Is it possible to remap by changing stuff around in the keylouts?
And also, is it possible to remove that "feature" of the volume being lowered when headphones get connected? That's annoying, too.
badboi_zero said:
Is it possible to remap the action invoked by pressing the Back and Home buttons? Or can it be removed? Like long-press Back acts as the Home key. And long-press Home pulls down the notification bar?
It's annoying because I always press Back to exit an app, not Home. And sometimes it lags so a tap of the Back key registers as a long-press and actually sends me Home.
Is it possible to remap by changing stuff around in the keylouts?
And also, is it possible to remove that "feature" of the volume being lowered when headphones get connected? That's annoying, too.
Click to expand...
Click to collapse
/system/usr/keylayout/
directory may be of some use.
I'm not able to access those files at the moment but i think the file s3c-keypad.kl allow for some remapping as well.
I'll post back with more help when I'm actually able to access those files for the phone.
Hey there,
I am looking for a way to remap my power button to launch a shortcut.
My goal is to make Tasker hibernate all 'greenified' apps, and turn off the screen when I press the power button.
This way I can turn off automatic hibernation in Greenify, and only 'greenify' apps when I explicitly turn off my screen, and not when it times out.
I've looked into several apps, but they all lack the ability to either remap the power button, or making it launch a shortcut.
I am running CyanogenMod 11 on my Samsung GT-I9300.
Hope someone could help me out!
You really don't want to do anything that would make you use the power button more. That is the first thing to die and you've got problems if it does. Much better to map a soft button or gesture to do what you want.
I thought about your comment, but it won't make me use the button more, because I use it anyway to lock my phone.
But nevertheless I could try to use it less. The problem is I use touch to wake the screen, and only if I lock it with the power button touch wil not wake the screen. If I wear the phone in my pocket, my leg wakes the screen trough the pocket.
I now made two profiles. One with proximity sensor, screen off and orientation upside down. And one the same, but orientation face down.
This way it will greenify apps when I put the phone in my pocket, standing or sitting.
I might look into gestures because then the sensors won't have to run when the screen is off saving me some precious juice am I right?
Still like to hear about remapping hw keys.
you can remap your power button here
System/usr/keylayout
then edit with text editor "Generic.kl"
kismetmookz said:
you can remap your power button here
System/usr/keylayout
then edit with text editor "Generic.kl"
Click to expand...
Click to collapse
Can I also map a shortcut to it? And do I have to remap again after an update?
GT-i9300, CM10.2, Googy-Max kernel
I accidentaly found out that there's a difference between the 'Tasker lock system' and the 'Secure Settings lock' actions.
With the Tasker action, touch to wake still works, but with the Secure Settings one it won't.
I now set up two profiles, screen on + proximity + upside down and screen on + proximity + face down. These greenify all apps and turn my screen off with Secure Settings. Also long pressing the menu (touch)key will do the same.
This way, when I put the phone in my pocket it will lock the screen and not wake up when still in my pocket.
But if I leave it face up and the screen times out my apps won't be greenified. I also made a double tap gesture in Nova Launcher that turns my screen off by the default Tasker system lock, so I can wake it by touch and my apps won't greenify.
Not really the idea that I started with, but maybe even better!
joriswagter said:
Can I also map a shortcut to it? And do I have to remap again after an update?
GT-i9300, CM10.2, Googy-Max kernel
Click to expand...
Click to collapse
you have to every update.. but i suggest you getting a CM rom =)
My i9300 is running CM11 nightlys. I update weekly, so it will be a pain in my behind
Sent from my GT-I9300
Maybe I just have meaty digits, but I often find that when I'm trying to take a picture, my thumb will graze the hardware back button and exit the camera app completely. Then I have to reload the camera app and I've totally missed the moment.
I finally got fed up and switched to the soft navigation bar - in CM11, it's under Settings > Buttons > Enable on-screen nav bar - but it's not a very elegant solution.
Ideally, while I'm in the camera app, I'd like the phone to require a long press of the back button to exit. But I don't know of a way to conditionally remap the hardware keys - e.g. "if CAMERA is running, remap Back Key short press to NULL and remap Back Key long press to BACK."
Any suggestions?
Anyone know if there's a way to make the home button only work with a hard press? I'm not referring to unlocking the phone or turning on the screen, I'm asking about when using the phone or an app and wanting to press the home key, I would like the ability to disable a simple tap and make it feel more like a button by utilizing the pressure sensor. Anyone know if this is possible?
Thanks in advance
Look in Settings, Screen, Navigation bar, Home button sensitivity.
(English descriptions translated from Italian)
Outbreak444 said:
Anyone know if there's a way to make the home button only work with a hard press? I'm not referring to unlocking the phone or turning on the screen, I'm asking about when using the phone or an app and wanting to press the home key, I would like the ability to disable a simple tap and make it feel more like a button by utilizing the pressure sensor. Anyone know if this is possible?
Thanks in advance
Click to expand...
Click to collapse
Try this-
set/display/navigation bar/Home button sensitivity
Sensitivity can only do so much, I have it on minimum for purely comfort, because it's much more effortless to unlock your phone when the tap doesn't have to be so intense. And if I really am force-pressing on the button area at any force, I am trying to unlock the phone, so I don't really see a point in having to press it with a lot of effort.
But I've found out that the button is very largely hardware-based, since it works and vibrates even when changing themes, when things like system UI are not active, and normal nav buttons and status bar are gone. So I doubt that any sort of third-party development will be done for it without root access, since the hard press function seems to work as a real button press, and not a virtual press.