Related
Yippeee!!
I just found out how to get around the problem where the "Start" button gets disabled and soft-reset was the only way to re-enable it! A little more info on the problem -
PROBLEM DESCRIPTION
- The last application that ran would appear instead of "Start" even after you close/minimize the application.
- Clicking on the button, would do nothing...the button goes dead.
- Clicking on the signal strength icon is dead, clicking on any notifications does nothing, you cant alternate click the clock! Only thing clickable is the "Close" button and the speaker button (only when in a call)
HERE's HOW TO GET YOUR DEVICE OUT OF THIS STATE!
Simple! Just press the POWER button of your device to turn it off, and simply press it again to turn it back on to get all the buttons on the top bar functional again!! Haha!!
I used to soft reset all the time for this, now this is an easy fix ;o)) Just thought i'd share it if others have this same problem on their devices!
Cheers!
San
Guys, this is what I have done with my button mappings and so far it seems to be working reasonably well. Well, reasonably enough that I am happy with it/can live with it.
Now I am very nit-picky and am coming from a heavily customized WisBar world. But in my quest to be stylus-free (and loving the WOW-factor of TF3D), I am able to live with the device by making the changes listed below.
-+-+-+-+-+
1. AEBPLUS - Volume Buttons
o Remapped volume buttons to provide Up/Down scrolling
o HOLD volume up or down - normal volume control
I did this because the TP was rejecting calls on its own whilst in my holster -- you know, the "press any volume button to mute the ringer" feature.
Note that if you do this, don't forget to look at the "Restore Volume Slider" option in AEBPlus (that guy thought of everything). I have all of mine unticked. Also take a look at: Options|Other Options|Control Volume Directly.
Screenshot: http://auxiliary.razer7.com/aevolume.png
··········
2. AEBPLUS - Phone Key ("Green Phone Button" in AEBP)
o Press once = Phone Button
o Press twice = Task List (Swipe left shows Programs)
o Press three times = Action List <-Note the Cut/Copy/Paste here!
Screenshots:
Task List: http://auxiliary.razer7.com/tasklist.png
Task List - Swipe Left: http://auxiliary.razer7.com/programs.png
Action List: http://auxiliary.razer7.com/actionlist.png
ABOUT THE TASK LIST: The Task List (and Programs list) is all touchable. AEBPlus provides its own task list as well but it isn't as nice as the one that I am using nor is it fingerable. The one that I am using is a freeware program called "MortButtons".
Download MortButtons here:
http://www.sto-helit.de/index.php?module=download&action=list&category=13
NOTE: Don't forget to also download the "ClickLED" skin on the same page. This skin closely matches the TF3D colour scheme.
During my testing, I've noted that MortButton uses about 250K (if you decide to leave it resident (recommended!)) and zero CPU since it is being called by AEBPlus.
ABOUT THE ACTION LIST: The "Action List" (as pictured above) is part of AEBPlus and can be custom-catered to your liking. I like to keep it simple and simply have cut, copy and paste in there, as well as toggle Wi-Fi (which works on the TP).
··········
3. AEBPLUS - End Call Button ("Red Phone Button" in AEBP)
o Press once = End Call
o Press twice = Last Task (ALT-Tab)
o Press thrice = Call DinarSoft TapText*
* "TapText" is a little utility that allows you to create a menu with clippings in it. I used it for email addy's and more. Check it out. I find it very useful and worth the ten bucks to register.
Screenshot of TapText in action: http://auxiliary.razer7.com/taptext.png
-+-+-+-+-+
4. About the Home and OK Buttons...
Now these two buttons *can* be mapped using AEBPlus, however, they can't be *re-mapped*.
In other words, if you map something to these buttons, they will also perform their inherent functions (i.e. the Home button will always go home first; the OK button will always send an OK message to the system, etc.)
Personally, I have left these two alone.
-+-+-+-+-+
CLOSING COMMENTS:
Now there is MUCH MORE you can do with the above two apps in the configuration I've described. Customize it to your delight.
I hope that this post helps some of you guys out. I need to give back to this community!
This community R0X.
Thanks for sharing. Will try this out as soon as possible.
You're very welcome!
I was playing around with this setup earlier today and so far, it has been working really well.
Take care.
I have AEBPlus and it is working great. My home key is mapped to be the start menu on a single press and torch on a long press, the back button closes active applications on a single press. My soft keys are mapped to lock the device and contacts. Works perfectly for me.
I'd already re-mapped the volume buttons as you did, though for a different reason. I use MS Readern often, and find the circular direction button on the TP pretty useless - I try to press arrow down and get the centre keypress instead more often than not. The volume buttons are a perfect substitute.
On tip though - when mapping the volume buttons it works best if you map double click and triple click to none. Doing otherwise gives confusing results.
Excellent post Minus-1, AEBPlus is a program I'd been looking for since getting my touch pro and the Mortbuttons program is proving to be a very useful program itself. one q though on the button options list in AEBPlus which ones cover the touch pros 'home' button and '<-' button
grezz said:
On tip though - when mapping the volume buttons it works best if you map double click and triple click to none. Doing otherwise gives confusing results.
Click to expand...
Click to collapse
Absolutely. I have only single click (directional up or down) and press-and-hold (volume control).
I often double-click the volume button to move up two elements, etc.
Excellent tip. Something definitely worth noting!
P.S. One quick note about the smartwheel: I used to HATE it but now I LOVE it. U have to get used to it and memorize the length of your stroke, etc. Once you do, tho, honestly, doing things become a breeze (especially whilst reading RSS).
yan2k said:
Excellent post Minus-1, AEBPlus is a program I'd been looking for since getting my touch pro and the Mortbuttons program is proving to be a very useful program itself. one q though on the button options list in AEBPlus which ones cover the touch pros 'home' button and '<-' button
Click to expand...
Click to collapse
Hiya, Yan2K!
I'm glad that you're enjoing AEBPlus and MortButtons.
In AEBP, the '<-' is mapped as the "OK Button" (which is precisely what that button means; some people like to call it the "back button" but it actually send a WM_OK message to the system).
As for the HOME button, you will have to map it...
In AEBPlus, go to the FILE|ADD BUTTON menu entry and press your HOME button. The TP will go back to the home screen but don't worry -- AEB is still running. Just click on your Quick Menu in the home screen (upper right corner of your task bar) and switch back to the AEB task.
Now remember: if you map these two buttons, they will NOT unmap their original functions... I generally leave these two buttons alone m'self.
Cheers!
thanks for the quick reply. I've created the 'home' button as you instructed, ended up with 'button #00ED' but cant get it to do anything either on 1-2-3 or long button press nor can i get the 'ok/<-' button to do anything either. prob doing something stupid can you help? ideally i want to be able to run a program on a long 'home' key press
Well mine is working, but not when TF3D is the active application. I remaped the (Long press) Home butoon to Second Today, and when I press it (long) it opens Second Today. Again, only when the TF3D is *not* the active program.
Hope that makes sence...
Cheers,
Cacti
yan2k said:
thanks for the quick reply. I've created the 'home' button as you instructed, ended up with 'button #00ED' but cant get it to do anything either on 1-2-3 or long button press nor can i get the 'ok/<-' button to do anything either. prob doing something stupid can you help? ideally i want to be able to run a program on a long 'home' key press
Click to expand...
Click to collapse
Mapped the volume buttons as you did. Just what I was looking for. Also set 'back' to proper 'ok/close'.
Cheers.
I think,the original functions are hardcoded somewhere(dll or something else). We need to find the file and modify it to disable these functionalities.
I remapped the "green" button the following way:
1 press) Phone application
2 presses) Alt+Tab
However, now when there is an incoming call I can't use it to answer. Which is quite logical.
Is there a way around this?
le_cactus said:
Well mine is working, but not when TF3D is the active application. I remaped the (Long press) Home butoon to Second Today, and when I press it (long) it opens Second Today. Again, only when the TF3D is *not* the active program.
Hope that makes sence...
Cheers,
Cacti
Click to expand...
Click to collapse
played around with it and found purely by chance that just like you said you cant use the home button or '<-/ok' button to do anything when you've actually got the TF3D home screen showing. hopefully someone will come up with a workaround for this as although i can make use of the '<-/ok' button it pretty much makes the 'home' button redundant for anything else but its original purpose
yan2k said:
played around with it and found purely by chance that just like you said you cant use the home button or '<-/ok' button to do anything when you've actually got the TF3D home screen showing. hopefully someone will come up with a workaround for this as although i can make use of the '<-/ok' button it pretty much makes the 'home' button redundant for anything else but its original purpose
Click to expand...
Click to collapse
Oh man, the OK button is one of the buttons I miss the most.
Specially while texting and such.
I hope I can remap some of the full keypad buttons as well.
I noticed that it sometimes doesnt' start up well, but oh well.
I re-maped the volume down to Ok/Close and Volume up to Start Menu
Then changed the volume settings to long hold, Which half the time when i press the buttons the volume comes up. haha.
hello!
I want to remap some buttons and I've tried with AE button Plus without success. Can you help me?
What I have is the call button configured for a long press to cyberon voice dial.
The disconnect button long press is for vibrate / ring.
what I want is to turn home and back buttons long press to wifi and bluetooth on/off and.
is it possible?
can I do this without AE button +? like a registry change? would be even better... or another program suggestion is also a good help!
Please help!
deiota
Is it able to remap the PTT button? That would be AWESOME.
dumb question, but where can I download AEB Plus?
I can't find a direct link or site to get the program!
Thanks...
http://ae.inc.ru or ask directly the author AE(here on XDA-Alexander Eltsyn).
So, is there any way to change the mapping on my keyboard? Like the hot button keys really get in my way, and I'd rather have a TAB key than a CAPS key, and stuff. So is this possible yet?
Hello....is there any way of changing the action when the handsfree button is pressed or even long pressed & doublepressed
yes, same question. Extremely annoying how easy it is to accidently double tap the button and call the last person.
any suggestions anyone ??? maybe a registry edit or anything..... still waiting
The handsfree button has the same function as the call button typically.
double press -> redial (same as call button on phone)
long press ->
a) on some ROMs simply doesn't work. Guess it depends on driver version
b) if workiing, you can set the function in Buttons, gets same function as long press Button 1 (left phone button)
isnt there a cab or file cause its really annoying and would love to set it to next song or previous song
bump any one some one help its really annoying randomly calling someone
Not sure but;
Check in your registry in HKCU\Control Panel for your headset settings
Search for 'audio manager headset tool' on forums.
Try this cab
Havent tested it my self yet
[APP+DRV] [Keys remapper] Topaz Keyboard Controller GSM v1.4
markisme said:
Hello....is there any way of changing the action when the handsfree button is pressed or even long pressed & doublepressed
Click to expand...
Click to collapse
Topaz Keyboard Controller;
http://forum.xda-developers.com/showthread.php?t=555821
What is it ?
It's a solution that allows you to remap ALL keys of your device.
Any key (yeah, i mean ANY, including Home and Back keys) can be reassigned to perform desired actions.
Have fun,
Senax
Thanks for replying ... I already have Topaz Keyboard Controller installed but it does not let you configure the (wired) handsfee button.. or if there is a way then pls help !!!
i am going for another head-set...
samsung has a usb-mini where the call button is less sensitive, plus you can change the headset via mini jack
donno yet if the samsung works on htc
but there should be other brands
What about this headset?
http://www.htcaccessorystore.com/nl/p_htc_item.aspx?i=179134
djg269 said:
What about this headset?
http://www.htcaccessorystore.com/nl/p_htc_item.aspx?i=179134
Click to expand...
Click to collapse
thanks for the suggestion - see there is a hold button
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.
Hello there!
Key Mapper is an open source key mapping application, which aims to remap any combination of your keys/buttons and provide unique features.
It is currently in beta and any feedback (positive or negative) would be greatly appreciated. Please post your thoughts in the thread or send me an email.
First things first...
Downloads!
XDA Labs: https://labs.xda-developers.com/store/app/io.github.sds100.keymapper
Google Play: https://play.google.com/store/apps/details?id=io.github.sds100.keymapper
F-Droid: https://f-droid.org/en/packages/io.github.sds100.keymapper/
GitHub: https://github.com/sds100/KeyMapper/releases
Source code
https://github.com/sds100/KeyMapper
Donations
Ko-Fi: https://ko-fi.com/sethschroeder
What can be remapped?
There is NO GUARANTEE any of these buttons will work and this app isn't designed to control games. Your device's OEM/vendor can prevent them from being remapped.
ONLY HARDWARE buttons can be remapped.
• Volume buttons.
• Navigation buttons.
• Bluetooth/wired keyboards and mice connected to your device.
• Buttons on other connected devices should also work but there is no guarantee.
You can combine multiple keys to form a "trigger" and have as many triggers as you want for each action. You can make a key map only work on a long press and to vibrate as well.
What can’t be remapped?
• Pixel Active Edge
• OnePlus Alert Slider
• Power button
• Bixby button
Your key maps don't work if the screen is OFF.
What can I remap my keys to do?
Some actions will only work on rooted devices and specific Android versions.
• Open an app
• Open an app shortcut. This feature is very useful since you can tell another app to do something Key Mapper can’t. E.g If your launcher has a shortcut to open the app drawer, you can select that shortcut in this app and make any button open the app drawer.
• Go back
• Go home
• Open recents
• Open menu
• Expand notification drawer
• Expand quick settings
• Collapse status bar
• Toggle/enable/disable WiFi
• Toggle/enable/disable Bluetooth
• Toggle/enable/disable mobile data (ROOT only)
• Toggle/enable/disable NFC (ROOT only)
• Toggle Play/pause media
• Pause/play media
• Next/previous track
• Fast forward/rewind
• Volume up/down
• Increase/decrease a specific volume stream
• Cycle through and change the ringer mode
• Show the volume dialog
• Mute/unmute/toggle mute (Android 6.0+)
• Toggle/enable/disable auto-rotate
• Force portrait/landscape mode
• Switch between portrait and landscape mode
• Toggle/enable/disable auto-brightness
• Increase/decrease brightness
• Toggle/enable/disable flashlight (Android 6.0+)
• Take a screenshot (Android 9.0+)
• Open the Google Assistant
• Open camera
• Consume key event (Do nothing)
• Lock the device
• Move the cursor to the end
• Toggle/show/hide the keyboard
• Show the keyboard picker (ROOT only for Android 8.1+)
The Key Mapper input method needs to be selected for these to work and you can’t use a soft keyboard at the same time:
• Input a specific keycode
• Input a key
• Insert a block of text
More will be added. If you have any ideas, leave a comment or email the developer.
What other things can the app do?
• Option to show a persistent notification which can pause/resume your keymaps. It can also open the accessibility settings on the device to enable/disable the service. Rooted devices can start/stop the accessibility service without going into settings and just tap the notification.
• Automatically change the input method to the Key Mapper one and/or show the input method picker when a chosen Bluetooth device is connected and switch back to the old one when it is disconnected.
• Option to show a toast message whenever an action is performed.
• Option to log events and send them to the developer so it is easier to debug issues with the app.
Planned features
• Double tap to perform an action
• Remap media (i.e volume, headset) buttons when the screen is off. Android only allows apps to detect media buttons when the screen is off.
• Action to broadcast an intent with extras.
• Multiple profiles which can be activated and deactivated automatically when a Bluetooth device is connected or when you open an app.
• Integrate the AOSP keyboard into the Key Mapper input method so a soft keyboard can be used at the same time.
CHANGELOG
https://github.com/sds100/KeyMapper/blob/master/CHANGELOG.md
is it possible to remap the play / pause button of the bluetooth headset to start Assistant?where is the download?
dario2106 said:
is it possible to remap the play / pause button of the bluetooth headset to start Assistant?where is the download?
Click to expand...
Click to collapse
I haven't tried using buttons on a Bluetooth headset but I have tried using the buttons on a wired headset and it does work. Most buttons should work as long as they don't have a proprietary implementation in the Android skin you're using. E.g Bixby, Pixel Active Edge. XDA doesn't allow new members to put links in posts until they have posted 10 times for security reasons. Once I can, I will definitely put links in the description.
dario2106 said:
is it possible to remap the play / pause button of the bluetooth headset to start Assistant?where is the download?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/apps-games/app-keyboard-button-mapper-t3914005
Here is the link to the app on XDA labs
sds100 said:
I haven't tried using buttons on a Bluetooth headset but I have tried using the buttons on a wired headset and it does work. Most buttons should work as long as they don't have a proprietary implementation in the Android skin you're using. E.g Bixby, Pixel Active Edge. XDA doesn't allow new members to put links in posts until they have posted 10 times for security reasons. Once I can, I will definitely put links in the description.
Click to expand...
Click to collapse
Update: I can add links on mobile completely fine. :laugh:
Nice! Will map a button to a broadcast intent be implemented?
Droidphilev said:
Nice! Will map a button to a broadcast intent be implemented?
Click to expand...
Click to collapse
Yeah! Great idea. I've added it to the "issues" on the GitHub repo. I have exams coming up so it will probably be a couple months.
It would be great if you could add the possibility to force close the app in use! Thanks and keep up the work!
articuz said:
It would be great if you could add the possibility to force close the app in use! Thanks and keep up the work!
Click to expand...
Click to collapse
Thanks! That's now been added to the planned features. Would you say the app is stable enough to come out of beta?
New version!
1.1.0 Beta 1
Added
Setting to change the long-press delay.
Persistent notification which can pause/resume your remaps. It can also open the accessibility settings on the device to enable/disable the service. Rooted devices can start/stop the accessibility service without going into settings and just tap the notification.
Use Material Design 2 for homescreen.
Bugs Fixed
Persistent notifications wouldn't show on boot
The app would crash if using the "open google assistant" action if the Google app wasn't installed.
Prevent the accessibility service from stopping if there is a fatal exception and show a toast when it happens.
New version!
1.1.0 Beta 2
Won't immediately crash on KitKat anymore!
Bug Fixes
Persistent IME notification wouldn't automatically show when it is enabled.
App would crash if it couldn't find the device's accessibility settings page.
Feature request:
App currently conflicts if the same button is mapped twice
Example
Short press mute = play/pause
Long press mute= open notification drawer
Result:
Long press mute results in both actions being performed.
Expected result:
Long press mute key should not activate the short press mapping
Fixes:
1. Change short press so that it ONLY activates if the button is RELEASED before the long press kicks in (should be around 500ms)
(Long press delay meaning how long the key must be held before performing the function)
Long press actions should happen if the button is NOT released within that time.
2. Multi-triggers should have a flag for "in sequence" that makes them work in sequence instead simultaneously. In sequence enabled should also Grey out / disable the long press flag on the current trigger.
And you should be able to set the same trigger twice.
Example: vol up, vol up = quick settings
To do this, you'd have to make it so that short presses are only activated if the button is released before the long press delay AND there are no other key presses within 300ms of releasing it
Great app.
Thanks
Nah.uhh said:
Feature request:
App currently conflicts if the same button is mapped twice
Example
Short press mute = play/pause
Long press mute= open notification drawer
Result:
Long press mute results in both actions being performed.
Expected result:
Long press mute key should not activate the short press mapping
Fixes:
1. Change short press so that it ONLY activates if the button is RELEASED before the long press kicks in (should be around 500ms)
(Long press delay meaning how long the key must be held before performing the function)
Long press actions should happen if the button is NOT released within that time.
2. Multi-triggers should have a flag for "in sequence" that makes them work in sequence instead simultaneously. In sequence enabled should also Grey out / disable the long press flag on the current trigger.
And you should be able to set the same trigger twice.
Example: vol up, vol up = quick settings
To do this, you'd have to make it so that short presses are only activated if the button is released before the long press delay AND there are no other key presses within 300ms of releasing it
Great app.
Thanks
Click to expand...
Click to collapse
Thanks for the feedback! I'll try to implement/fix these problems. They should be relatively easy to fix (hopefully). ?
New version!
1.1.0 Beta 3
Reduced the repeat delay to 5ms
Force expand the menu on the homescreen
Made the cards on the homescreen slightly more compact
Added
Flag to vibrate and an option to force vibrate for all actions
Action which just consumes the keyevent and does nothing
Action to lock the device (ROOT only for now) and an option to lock the device securely (without root).
Bug fixes
The bottom app bar on the homescreen would overlap the list items
The app would potentially crash when trying to perform a flashlight action whilst the camera is in use in another app.
Short press actions with the same trigger as a long press action would be performed with the long press action
A keymap would still have the "Show volume dialog" flag if the action is changed to a non volume related action
The app would crash if trying to show the menu on the homescreen if it is already showing.
The accessibility service status on the homescreen wouldn't change when the service is started/stopped.
Hi,
it is possible to make it work with the Mi Box S controller? Especially with the Netflix and Live buttons, I tried the back button and it works, but not those two "special" buttons. I will be very grateful
Sent from my Lenovo TB-8704F using XDA Labs
Ja_som said:
Hi,
it is possible to make it work with the Mi Box S controller? Especially with the Netflix and Live buttons, I tried the back button and it works, but not those two "special" buttons. I will be very grateful
Sent from my Lenovo TB-8704F using XDA Labs
Click to expand...
Click to collapse
Do the other buttons also work? I'm guessing the Netflix and Live buttons don't send a standard KeyEvent which apps installed by the user can see. Xiaomi probably have some agreement with Netfix to have that button there to drive more people to Netflix which is why they don't want us changing it.
sds100 said:
Do the other buttons also work? I'm guessing the Netflix and Live buttons don't send a standard KeyEvent which apps installed by the user can see. Xiaomi probably have some agreement with Netfix to have that button there to drive more people to Netflix which is why they don't want us changing it.
Click to expand...
Click to collapse
Most buttons work, home, back, left, right, up and down are recognized propperly. OK and 'all apps' (not sure if it the right name of that button) have no name in triggers but they work. If I try to record trigger with vol. up or down, it is not recorded, it just changes the volume. The mic. button is recorded with no name, but when I try to use it to trigger the action it does nothing.
Sent from my Lenovo TB-8704F using XDA Labs
Ja_som said:
Most buttons work, home, back, left, right, up and down are recognized propperly. OK and 'all apps' (not sure if it the right name of that button) have no name in triggers but they work. If I try to record trigger with vol. up or down, it is not recorded, it just changes the volume. The mic. button is recorded with no name, but when I try to use it to trigger the action it does nothing.
Sent from my Lenovo TB-8704F using XDA Labs
Click to expand...
Click to collapse
Hmmm... I'll firstly add names to more buttons so they aren't blank. I'm sorry but I don't really know what to do. This behaviour sounds like the accessibility service is broken somehow and needs disabling and then enabling. This has happened to me before during development. But it is likely those buttons won't work. It's quite hit and miss when it comes to non-standard buttons/controllers unfortunately.
No success with Bixby button on S10