Related
[Info]:
My only gripe about the trackpad wake mod (while it is awesome), is that we do it in order to avoid reaching for the awkwardly placed power button, but then we still have to reach for it anyway when we want to shut the screen back off. So it only helps us for half of the task.
After trying to find a way to directly map the search soft-key (or any of the soft-keys) to a power button, and failing, I've decided to come at it from a different angle. Attached you'll find a very simple app, that simply turns off the screen when clicked, along with instructions on how to map it to the search soft-key or the rosie button for sense users.
[Options]:
1. Search key short press. This is the method I use, as it is both the fastest and accessible from within any app. It will completely replace the search key. Single-tap it at anytime to turn off the screen. You'll need to install the app, and push the keyboard remapping file that I have also attached. Note that there are 2 different key mapping files, one for Sense ROMs and another for Vanilla. They will make the following changes:
Sense version:
-Search soft-key is now mapped to the user programmable key #2. Set it to open the Kill Screen app.
-www/com key is now TAB.
-USER 3 key, which didn't work anyway, is now BACK.
-USER 2 key, which is now not needed, is HOME.
-USER 1 key (left of the space bar) is left as normal.
Vanilla version:
-Search soft-key is now mapped to the user programmable key #3. Set it to open the Kill Screen app.
-USER 3 key, which is now not needed, is now BACK.
-USER 1 and USER 2 are left as normal.
2. Rosie's right button. This is for those who want to keep the search key as normal. See my rosie remap thread here for the option to have it launch when you press the right dock button. Keep in mind you still need to install the app, and you'll (obviously) have to be viewing one of the home screens to press it.
NOTICE: Do not post asking me to adapt this key layout to your needs, as we will end up with 500 different files before long. Instead, change it yourself! Editing this file is about as easy as it gets. You don't need anything special installed, or any programing experience whatsoever. Simply open the attached (or your own) vision-keypad.kl in any text editor (Notepad, Notepad++, etc) and change your desired key to your desired function. If you want to know what key corresponds to what number, you can boot to clockworkmod recovery --> advanced --> key test. Touch any key on the phone, and it spits out the number.
NOTICE #2: As with any app that is given administrator permissions, you will need to remove the app from the admin list in order to uninstall it. Menu --> Settings --> Security --> Select Device Administrators --> Uncheck Kill Screen. Then uninstall as normal. You will be reminded to do this when you first give the app the admin permissions.
[How To]:
Method 1 - Install the app, then grab a copy of the modified key layout and then reboot to recovery and enter this code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [your saved file location]\keypad_owamod_xxxxx.kl.zip /system/usr/keylayout/vision-keypad.kl
Reboot and enjoy.Method 2 - Install the app first, then see the linked thread for how to get the modified rosie.apk
That's pretty awesome Will definatley try out when I get a Z
Great news but something like that exists already for a few monts:
http://forum.xda-developers.com/showthread.php?t=795811
I used it on the Nexus One and now on the Desire Z.
Works great! Thanks a lot!!
g4rb4g3 said:
Great news but something like that exists already for a few monts:
http://forum.xda-developers.com/showthread.php?t=795811
I used it on the Nexus One and now on the Desire Z.
Click to expand...
Click to collapse
Not quite.
You should read the whole post, people fail to do so far too often on this forum. Of course the app exists, there are multiple versions, both pay and free, on the android market and floating around the forums.
What does not exist, is the remapped key file to make the app launch with a short press of the search key (method #1) and the remapped rosie buttons to launch the app from the right dock button (method #2).
The only method I really cared about is the short-press search button (method #1), which completely replaces the search button, so that it functions to turn off the screen (like it should have been from the factory) like the G1. This also allows it to work while the screen is still locked, so you can single press the trackpad, check the time/messages/missed call, then turn the screen back off without ever unlocking it! But I made this mod and guide, so that you have THREE options: the long-press method (like the one that you linked to) AND two NEW ways.
Using all of the default files while running CM 6.1.1 Colourized, I can get my DZ to sleep only by long-pressing the Search button, not a short-press.
I checked the .kl file and confirmed the USER2 key is 217 and that matches my Key Test number in Recovery.
A short-press of my Search button doesn't do anything.
I've set KillScreen as the default app for the long-press and it works as it should, but I'd like to leave that as a Search (Vlingo) button and have a short-press go directly to KillScreen.
Suggestions?
I tried the Rosie_killscreen.apk , it installs ok i get the little power icon on my Rosie launcher bar but when I press it, it doesn't do anything, I tried to re-download the file in case it was corrupt and re-install it but the same thing happens, nothing. I installed the Rosie_contacts.apk and it work fine but can get the Rosie_killscreen.apk to work. Has anyone gotten the Rosie_killscreen.apk to work?
EDIT- My fault forgot to install the main app..... Sorry, let me try this again.
Update: The app works great on the Rosie_launcher, Just a reminder to install the KillScreen.apk first, then follow the process for pushing the app to the Rosie launcher.
I like this very much!! I have Launcher Pro Paid and I have set it up as one of my swipe options on the dock.
I use cm6.1.1 lockscreen gestures and the "screen off and lock" app. I setup a gesture of "L" and link the gesture to the "screen off and lock" app so when I am on the lockscreen and do a "L" gesture and it shuts off the screen. I also have it set as a shortcut in the dock for adw launcher too so I can lock/screen off just by pressing it. So far it works great.
B73C said:
Using all of the default files while running CM 6.1.1 Colourized, I can get my DZ to sleep only by long-pressing the Search button, not a short-press.
I checked the .kl file and confirmed the USER2 key is 217 and that matches my Key Test number in Recovery.
A short-press of my Search button doesn't do anything.
I've set KillScreen as the default app for the long-press and it works as it should, but I'd like to leave that as a Search (Vlingo) button and have a short-press go directly to KillScreen.
Suggestions?
Click to expand...
Click to collapse
I'm not really sure what the issue is. If you choose the method where Kill Screen acts as the short-press search, you will not have a long press function anymore.
I'm experiencing a problem with the long press method where the screen turns off for a second but immediately turns back on to the lock screen. Manually launching the app shuts off the screen properly. Anyone else getting this?
I am having problems downloading the 2 .zip files
I use the one called "Lock Screen Button" in the market. It's simple and the icon is very clean.
cyricc said:
I'm experiencing a problem with the long press method where the screen turns off for a second but immediately turns back on to the lock screen. Manually launching the app shuts off the screen properly. Anyone else getting this?
Click to expand...
Click to collapse
After a bit of testing I'm pretty sure this has something to do with the capacitive buttons remaining active for a very brief time after the screen shuts off: since the search button is held while the kill screen action runs, it immediately triggers wake. Pressing the power button while holding down any of the capacitive buttons has the same effect (screen turns off then back on to lock screen).
I'm guessing this can be fixed by adding a delay to turning the screen off. Or by setting the capacitive buttons to not wake the screen somehow.
Can't uninstall kill screen app
I installed the KillScreen.apk, however if I try to uninstall the app via the manage applications I get "Uninstall not succesful" and app is still in my applications list.
How can i permanently remove the KillScreen.apk?
As for the app not working properly with the long-press method, you are right, it seems to be bugging. I will take a look and hopefully get a new version up soon. The other two methods work ok, but I don't use that method, so I didn't do enough testing
LQT said:
I installed the KillScreen.apk, however if I try to uninstall the app via the manage applications I get "Uninstall not succesful" and app is still in my applications list.
How can i permanently remove the KillScreen.apk?
Click to expand...
Click to collapse
This is the second time in one thread I've had to quote someone and tell them to READ. Do they not teach you kids to read in school anymore? READ PEOPLE. You are working with rooted phones in a programming development forums, you SHOULD have some smarts to you.
Since you missed the "--WARNING!!!!---:READ:---WARNING!!!!--" text in all caps across the whole screen when you first gave the app permission, allow me to take my time to type it again for you: You need to remove ANY app that has been given administrator permissions from the admin permissions list in order to uninstall it. Since you gave this app administrator permissions, you need to do so. Menu, Settings, Security, Select Device Administrators. Uncheck kill screen. There will be a pop up box. Do not just hit the ok blindly, READ that too. Then uninstall.
the1wingedangel said:
Since you missed the "--WARNING!!!!---:READ:---WARNING!!!!--" text in all caps across the whole screen when you first gave the app permission, allow me to take my time to type it again for you: You need to remove ANY app that has been given administrator permissions from the admin permissions list in order to uninstall it. Since you gave this app administrator permissions, you need to do so. Menu, Settings, Security, Select Device Administrators. Uncheck kill screen. There will be a pop up box. Do not just hit the ok blindly, READ that too. Then uninstall.
Click to expand...
Click to collapse
Dude relax, no reason to get so agitated!
I actually did press the ok blindly, the reason for that was that the phone didn't do anything after the installation. So i tried to tap the screen to make it work and by accident tapped the ok button before reading the warning post.
If you do tell people to read, please give them the information to read. Either put it in first post or put it somewhere inside the app so people can re-read it.
I managed to uninstall the app, thanks for the info.
Relax, cheers
LQT said:
Dude relax, no reason to get so agitated!
I actually did press the ok blindly, the reason for that was that the phone didn't do anything after the installation. So i tried to tap the screen to make it work and by accident tapped the ok button before reading the warning post.
If you do tell people to read, please give them the information to read. Either put it in first post or put it somewhere inside the app so people can re-read it.
I managed to uninstall the app, thanks for the info.
Relax, cheers
Click to expand...
Click to collapse
Actually I do have reason to get agitated! (Even though I wasn't that upset at the time, my posts often just come across that way) Because after 2 years of seeing stuff like this with android users, it gets very tiring! For example: the countless comments on the market for an app that says in the description "ONLY works on Nexus 1" and the commenter says "Does not work on Droid" and rates it 1 star. But I can forgive those, because its the general public. On a development forum, however, I expect nothing less than every member to have their wits about them. Though, realistically, it's probably just wishful thinking.
the1wingedangel said:
Actually I do have reason to get agitated! (Even though I wasn't that upset at the time, my posts often just come across that way) Because after 2 years of seeing stuff like this with android users, it gets very tiring! For example: the countless comments on the market for an app that says in the description "ONLY works on Nexus 1" and the commenter says "Does not work on Droid" and rates it 1 star. But I can forgive those, because its the general public. On a development forum, however, I expect nothing less than every member to have their wits about them. Though, realistically, it's probably just wishful thinking.
Click to expand...
Click to collapse
Lol! I do that same thing in my thread. It's hard to not snap on some people lots of times. I have come to the conclusion that a lot of people just don't have the brain power to read/comprehend certain things. I've had to learn to relax a bit... It's quite useless to argue with them because it just rolls off them with no worries while people like us simply struggle to understand why and end up getting pissed off. It's tough being cynical sometimes
Thanks for the little app! Just some feedback. Wanted to install method 1. Followed the steps. However, it still acts as method 3, long press on search, instead of just the short press. Running Virtuous 0.8.1.
Recently moved away from IOS JailBreak to Android, and can't say im used to the new FileSystem! I am trying to map keys specifically while the lockscreen is active. Most of my searches are littered w/ the global keylayout method. I noticed how the camera app remaps vol and pwr hard buttons (to zooming and controls lock respectively), while lockscreen nulls the 4 touch keys but keeps the global hard buttons, except camera. IOS JB had "activator". It is able to set button and gesture actions for the lock screen, home screen, while an app was active, and global (across the other 3). I dont need the full "activator", just wish to do lockscreen specific remappings to better utilize unused keys that otherwise have a good function. Anyone know a good FS mod shortcut or does the lockscreen.apk it's self need to be altered to achive this?
You can simply pull the key mapping file off the phone itself and edit it in notepad, save it, and send it back on. You need root though, I believe. Follow this guide and mix it up yourself! There are many tutorials on how to do this, if this certain one isn't too helpful. This one specifically is for the G1 but the steps should be very similar.
http://forum.xda-developers.com/showthread.php?t=551344
Post #4 of http://forum.xda-developers.com/showthread.php?t=1046761. Epic specific button mapping file.
Thanks, but those are, what I refer to as, the global keylayout, because it affects the phone's lockscreen, homescreen, and where ever else applicable. For Example, I am trying to mod the lockscreen camera buttons to control music, but it goes back to the camera buttons @ homescreen. I would also like to set the 4 touch buttons that are normally blocked on the lockscreen to do Media stuff as well. The keylayout overtakes too much. I'm lookin a bit more into the filesystem to day, might look into the AOSP work for better insight. Still open to any suggestions on where 2 look.
Hi,
Is there an xposed module, app (rooted or not) or any other trick to give me the option to turn on flashlight torch when I press and hold power button even when the screen is off,
PS , running Cm13
Many thanks!
There is a xposed module named "xposed torch" that worked on my z1c
But on the 1+3 it seems to be broken, it just softreboot itself everytime i try to switch on my flashlight with it.. so i sticked with the "V" gesture
Actually I want this on my O+X , does not seem to work, I have tried the following,
Gravitybox MM
Sense for xposed
Xposed torch
Play store apps (out of frustration)
Others
I don't know if such thing is possible with Tasker, so maybe some1 will help with that
Also, there was a Moto X feature called Chop Twice for flashlight , is there a way to make that possible on AOSP Roms?
Many thanks!
The ResurrectionRemix ROM supports that I think...
ExtentedByte said:
There is a xposed module named "xposed torch" that worked on my z1c
But on the 1+3 it seems to be broken, it just softreboot itself everytime i try to switch on my flashlight with it.. so i sticked with the "V" gesture
Click to expand...
Click to collapse
Kharabsheh said:
Actually I want this on my O+X , does not seem to work, I have tried the following,
Gravitybox MM
Sense for xposed
Xposed torch
Play store apps (out of frustration)
Others
I don't know if such thing is possible with Tasker, so maybe some1 will help with that
Also, there was a Moto X feature called Chop Twice for flashlight , is there a way to make that possible on AOSP Roms?
Many thanks!
Click to expand...
Click to collapse
Xposed Torch by Wanam works for me
Kharabsheh said:
Hi,
Is there an xposed module, app (rooted or not) or any other trick to give me the option to turn on flashlight torch when I press and hold power button even when the screen is off,
PS , running Cm13
Many thanks!
Click to expand...
Click to collapse
xposed additions is the app you are looking for. I have OP3 myself and use this module for media skipping etc None of the other modules seem to work
hit thanks if I helped u
GravityBox MM works for me. Locked, screen off, power button hold and press - flash on.
arushdude said:
xposed additions is the app you are looking for. I have OP3 myself and use this module for media skipping etc None of the other modules seem to work
hit thanks if I helped u
Click to expand...
Click to collapse
Be careful if your are on OOS when you try to use Xposed additions. There are some bugs,
1. Xposed additions will make feedback vibration of touch buttons unavailable;
2. Double click power button to open camera quickly is not available anymore;
3. Maybe there is little delay when you use 'volume-'+'power button' to make a screenshot.
Iceyogurt said:
Be careful if your are on OOS when you try to use Xposed additions. There are some bugs,
1. Xposed additions will make feedback vibration of touch buttons unavailable;
2. Double click power button to open camera quickly is not available anymore;
3. Maybe there is little delay when you use 'volume-'+'power button' to make a screenshot.
Click to expand...
Click to collapse
true, but i use it for media controls and direct dial on triple click of power button for someone special as well.. so i prefer all these over the camera shortcut provided by OP.
im using custom slider xposed module to turn on and off flash light
Xposed Torch by Wanam does work at the beginning but after being in standby a while it doesn't launch the torch. from my perspective there isn't a sufficient solution that does fully work and does not break anything else.
arushdude said:
xposed additions is the app you are looking for. I have OP3 myself and use this module for media skipping etc None of the other modules seem to work
hit thanks if I helped u
Click to expand...
Click to collapse
Do you use xposed additions for Screen Off actions? I'm curious how reliable it is while the screen is off.....does it sometimes not trigger if you have had your screen off a while?
Have you tried Xposed Physical Button Music Control module? Serves almost identical purpose.....but I occasionally run into the issue I described. I'll Re-Map a Volume Up command (while screen off) to do some action.....sometimes it won't trigger if the screen has been off a while. Anyways, I'll be doing some extensive testing between these two (almost identical) modules and report back which I find more reliable/stable. I've used Xposed Physical Button Music Control for a LONG time and noticed the screen off actions are a bit flakey
http://forum.xda-developers.com/xposed/modules/mod-physical-button-music-control-1-8-t2620777
Stupifier said:
Do you use xposed additions for Screen Off actions? I'm curious how reliable it is while the screen is off.....does it sometimes not trigger if you have had your screen off a while?
Have you tried Xposed Physical Button Music Control module? Serves almost identical purpose.....but I occasionally run into the issue I described. I'll Re-Map a Volume Up command (while screen off) to do some action.....sometimes it won't trigger if the screen has been off a while. Anyways, I'll be doing some extensive testing between these two (almost identical) modules and report back which I find more reliable/stable. I've used Xposed Physical Button Music Control for a LONG time and noticed the screen off actions are a bit flakey
http://forum.xda-developers.com/xposed/modules/mod-physical-button-music-control-1-8-t2620777
Click to expand...
Click to collapse
xposed additions works for me perfectly all the time,be it screen off or screen on..
PBMC didnt work for me at all.. i tried it first for mapping music controls when screen is off but nothing went right...
i tried several modules but in the end xposed additions was the best of them all...
hit thanks if I've helped you
Here is my comparison so far for both Xposed Modules (Physical Button Music Control vs Xposed Additions)
Both apps have reliability issues with Screen Off triggers. To demonstrate, keep your screen off and don't touch your phone for quite a while (30+ minutes at a minimum). Now try to do a Screen Off trigger. It likely won't work. Now turn your screen on and off again. Try a Screen Off trigger immediately. It will work. So obviously, something is disabling/sleeping these apps after the phone goes idle for a while thus preventing these Screen Off triggers from working. I have no idea how to solve this. I've already added both apps to the Whitelist for Doze battery optimization. It is rather frustrating having this issue.
Both apps are NOT able to use the Home Button as a trigger while the screen is off
Xposed Additions CANNOT use the Home Key as a trigger....period. PBMC can.
Seems PBMC does not function on OOS....but it does work on CM based ROMs.
Both apps can play nicely together. So if you like specific things from both apps, you can use both.
Conclusion....they both perform pretty equally. I'll continue to investigate the reliability issues. There has GOT to be something we can do about this. I might write the xposed additions developer since he seems to be a OP3 user.
I use Gravitybox MM on OOS 3.2.7 and don't have any problems.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
NOTE: On a rooted device, this is the fastest, most reliable and problem-free method for remapping Bixby (no limitations, no setup)
Button Mapper allows you to remap any action you want to physical or capacitive hardware buttons. This includes volume buttons, Bixby button, and many buttons on game controllers and other hardware you attach to your phone.
You can map shortcuts, apps or actions to single press, double tap and long press for hardware buttons.
The Bixby button on the Galaxy S9 and S9+ is supported as of version 0.62
Bixby remapping of single, double and long press is completely free. No ads. Pro version not required.
Does not require root. If your device is rooted, you will have many more options (essentially unlimited). Also with root, Bixby remapping does not involve any hacks, it is implemented at the input level (native).
This does require an adb command to remap Bixby on unrooted devices. It's a one-time setup. I do not use the method used by other apps because it leads to a poor user experience (i.e. swiping right causes actions to occur, get stuck in a loop)
This app is continually updated with new features and improvements.
Download on XDA Labs:
https://labs.xda-developers.com/store/app/flar2.homebutton
.
Big update update on the way soon.
You can remap all Bixby stuff for free with this app, and it has the most options of any remapping app.
I'm looking for volunteers to translate. Go to this link if interested
http://oskwvu0.oneskyapp.com/collaboration/project/258033
Version 0.66 is now released. It will roll out slowly on the Play Store, if you want it now, get it from XDA Labs
https://labs.xda-developers.com/store/app/flar2.homebutton
This version has tons of small fixups: the AOD crash is fixed, activities open right away after pressing home, everything is faster, and there are more options. Also quite a few UI improvements.
Changes:
Pocket detection (pro)
Toggle auto brightness
Toggle Wifi hotspot (Android 7 and lower)
Toggle mobile data (root)
Clear notifications
Compatibility with Android P
Option to use speaker with Pressy, MiKey, etc
Global bypass option
More long press duration options
Receive incoming phone calls with home button (Samsung)
Add Spanish
Update translations
UI improvements
Optional lock method that allows fingerprint unlocking
Fix AOD crash with screenshot action (Samsung)
Optimizations and bugfixes
@flar2 anything about using Bixby button to take camera pics? thanks
[email protected] said:
@flar2 anything about using Bixby button to take camera pics? thanks
Click to expand...
Click to collapse
To click the shutter? You can do that with select/enter action, but it requires root.
flar2 said:
To click the shutter? You can do that with select/enter action, but it requires root.
Click to expand...
Click to collapse
yes, I was thinking if it was possible without root.
[email protected] said:
yes, I was thinking if it was possible without root.
Click to expand...
Click to collapse
Not that I can think of
I've deleted the bixby services without know that the remap apps wouldn't work anymore
This app doesn't work either.
ekvintroj said:
I've deleted the bixby services without know that the remap apps wouldn't work anymore
This app doesn't work either.
Click to expand...
Click to collapse
It's the only way to detect Bixby since Samsung bypassed the usual Linux input system..
thanks for this app. works great!
Hi
Thanks for this great app.
I use pro version.
Does it possible to remap back, home and recent soft keys on S9 ?
edzamber said:
Hi
Thanks for this great app.
I use pro version.
Does it possible to remap back, home and recent soft keys on S9 ?
Click to expand...
Click to collapse
I don't think so. It's definitely not possible using the methods used by this app.
So...people don't like free stuff? Should I make you guys pay for double press and long press?
Nice job with this app man. Very easy to turn on flashlight and get to google assistant. I'll be unlocking the pro version in a little bit.
It also appears that, even though I am not rooted, the bixby button works to turn on my flashlight while I'm on the AOD so that is SUPER helpful.
UPDATE!!
Version 0.74 has lots of new goodies. It's rolling out slowly on the Play Store, if you want it now you can download from XDA Labs:
https://labs.xda-developers.com/store/app/flar2.homebutton
-Menu action is now available without root
-Pause and resume remapping from notification, quick settings or public intents that can be used with Tasker or other automation apps
-If you use the notification, you can now change the priority
-Option to turn on screen with screen off actions, so if you launch an app with the screen off, the screen will automatically turn on (requires Pro version)
-Zello PTT toggle and hold actions (requires Pro version). This allows you to either set a button to toggle send, or hold the volume up or down button to talk
-Copy and paste actions
-Option to use VOICE_ASSIST for assistant
-Restore autobrightness when using brightness actions
-Fix shortcut bug
-Many other bugfixes and improvements
-Update translations
Here are the intents to pause and resume remapping. The first is a toggle, the other two explicitly pause or resume remapping. Use whichever best fit your needs.
flar2.homebutton.TOGGLE_REMAPPING
flar2.homebutton.PAUSE_REMAPPING
flar2.homebutton.RESUME_REMAPPING
@flar2
Screenshot sound toggle doesn't work for me on Galaxy S9+
Can we also have an option to disable bixby single tap when the device is locked or in always on display mode?
fmaher said:
@flar2
Screenshot sound toggle doesn't work for me on Galaxy S9+
Can we also have an option to disable bixby single tap when the device is locked or in always on display mode?
Click to expand...
Click to collapse
Screenshot sound toggle only works for my screenshot implementation. It can't be controlled on the native screenshot (I assume you're rooted)
flar2 said:
Screenshot sound toggle only works for my screenshot implementation. It can't be controlled on the native screenshot (I assume you're rooted)
Click to expand...
Click to collapse
Sorry didn't get your point. How can choose your screenshot implementation? There is only one screenshot action available in the list.
fmaher said:
Sorry didn't get your point. How can choose your screenshot implementation? There is only one screenshot action available in the list.
Click to expand...
Click to collapse
If rooted, it uses the built-in screenshot. If not rooted, it uses my own custom screenshot because I can't access the built in one. The built-in is preferable to the custom screenshot, but there is no control over the sound in the built in screenshot.
I bet everyone is sick of the key on Moto G 5G plus just like me. I have looked for a solution everywhere but I failed to find one.
Few days ago I found Physical Button Master Control (PBMC) and it was the solution. You can find a thread by @Xspeed HERE. He deserves the donation for turning this useless button into anything you want it to be.
Pre-requests:
1- Magisk
2- lsposed
3- PBMC
I'm not gonna go into how to root your phone using magisk as you can find many guides on xda and same for lsposed.
once you have magisk and lsposed, download PBMC from the link in @Xspeed thread and install the app and activate it in lsposed then restart the phone.
1-Open PBMC and press add (plus sign)
2-Enter any name in the (Name this chain) space. Personally I named it bright because I changed the function of the assistant key so it makes the brightness goes up; it helps me when I go outside and it's sunny as I don't activate auto brightness because it's annoying
3-Click on open chain diagram and from here you'll see three boxes.
a) The condition box is something that has to be true in order for the key to do its function. I chose screen state (screen on, lock screen)
b) the second box is add input key. choose basic then single press. you'll see a space says Unknown. click on change then press the assistant button so the app detects it then ok.
c) The last box is add action. From here you can choose the new action of the assistant key. I chose keypress and searched for brightness up.
4-Once you're done, go back and click save ( the button next to the add button).
You should see it in the chain list tab. If it has any problems, swipe it to the left and make a new one.
No need to reboot
Thanks for @Xspeed effort, this key used to bug me a lot as it was too useless and now it serves me very well.
olik2000 said:
4-Once you're done, go back and click save ( the button next to the add button).
You should see it in the chain list tab. If it has any problems, swipe it to the left and make a new one.
No need to reboot
Click to expand...
Click to collapse
thanks !
it works but after each change a reboot was needed for me to work
I failed to make the assistant button launch the camera with this method. Tried Xposed Edge as well. Only thing that works is Buttons Remapper app.
Edit: As of May, 10th 2023 Buttons Remapper no longer works. Shame.