Related
Now I know that most seasoned HTC & XDA folks have already discovered what I am stating in the next five paragraphs ...
The Buttons applet in Personal -> Settings in the latest HTC 5.05.00.00 (5.05.405.1 WWE) stock ROM only provides a single button option which appears as Button 1 (Hold). The Button 1 (Hold) maps to a Long press of the Send hardware key. Snooping the HKLM\Software\Microsoft\Shell\Keys, one finds a sub-key of 40C6 which corresponds to Long Send from what I can gather.
Additionally, some hardware keys are being intercepted by services/applications that come bundled as part of the stock ROM - these are:
- Long Press End Key: invoked when one performs a Long press of the End hardware key
- Volume Up/Down: launches the HTC Volume (System/Ring) applet
- Home: which returns to TF3D Home (or Today) on a Short hardware key press
- Back: which issues a return/cancel on a Short hardware key press
- Send: which launches the Phone applet/initiates a call
- End: which return to TF3D Home (or Today)/ends a call
- Button: which issues OK/Select
Some further searching on the XDA site gives us the XCSdM Fuze PP Mod gem from XCSdM (http://forum.xda-developers.com/showpost.php?p=3127272&postcount=126).
There's also the short_XXXXX.lnk shortcuts that can be placed in the Windows folder.
And lastly, there are numerous other 3rd party applications which perform hardware and softkey button mapping - some free, most aren't, and come at the cost of some overhead.
I had figured it might be a simple matter of adding the missing sub-keys (for long & short press) to the HKLM\Software\Microsoft\Shell\Keys so that I could change the assignments of desired hardware/softkey buttons via the Buttons applet in Personal -> Settings ... apparently not.
So my question(s) ... finally
The Ideal Answer
1) Are there other sub-key entries that map to the hardware buttons (ex: 40C6); if so, can some kind soul point me in that direction?
Cause Nothing Seems As Simple As I Thought
1) As I suspect that this would have to be a fairly low-level running process; does anyone know of a program that leverages the LNK files in the Windows folder and the HKLM\Software\Microsoft\Shell\Keys registry key?
XCSdM's CAB provides this type of functionality (see Post) for the PTT button; it would be nice to have similar applet(s) for the remaining hardware keys.
As usual, insight from the fine folks in this community would be greatly appreciated. I've only been part of this community for a few weeks and have to say that I really appreciate the willingness to share experiences and knowledge; it has made the learning curve less steep than it would have been ... hopefully one day I can return the same to others.
* EDIT *
Solution: XCSdM PTTMod for the Raphael solves the problem.
[REF][04/21/09]Raphael OEM Package Repository
http://forum.xda-developers.com/showthread.php?t=482173
Do a search on AEBPlus. I use it and it offers pretty much complete button remapping. No registry entries to work with and VERY customizable.
Hi BoldFace,
Appreciate the response; had a look at it ... very nice application - problem is it's not free and I'm looking to eventually do some ROM cooking so I figure they may get a little annoyed if I add that to the ROM image.
Cheers,
Hi,
have you found a way to remap the volume buttons?
greetings, stan
Not as of yet,
Still trying to get the original items from the post working ... tracking down someone who'd be willing (and has time) to code this up has been a challenge.
* EDIT *
Volume keys are intercepted by the Manila volume control libraries.
Cheers,
Since the vibrant doesn't have a secondary input like most android devices, it's even more vital that we have unfettered access to the keyboard and its soft arrow keys. Unfortunately long pressing the menu button in some applications (notably the browser) brings up SEARCH rather than the keyboard by itself. That means no arrow keys for text selection or link highlighting.
This has been discussed previously in general at http://forum.xda-developers.com/showthread.php?t=776792
How difficult would it be to remap the long press of the menu key to bring up the keyboard by itself?
After researching it some on my own, it looks like I need to come up with a way to call showSoftInput() from one of the softkeys. It'd be ideal if I could get that to happen on menu long press, but if that's too far buried in proprietary configuration I'd settle for replacing the google voice search app mapped to the Search button long press.
Anyone have any tips on mapping system functions to a hardware key normally used for app launching? The lack of any keyboard in the browser is seriously inhibiting my ability to use this phone.
Dxtop pro does this, and long press back is tasks
Sent from my SGH-T959 using XDA App
fit333 said:
Dxtop pro does this, and long press back is tasks
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yeah, buth then you have to use dxtop. *non fan of dxtop*
fit333 said:
Dxtop pro does this, and long press back is tasks
Click to expand...
Click to collapse
dxtop takes over the long press of buttons only in the home screen context, and it doesn't use any of them to launch the keyboard. Plus there's no way to configure any of it so it's not really the same at all.
What I'm looking for is to alter one of the long press actions in a system-wide way to launch the soft keyboard.
cbisquit said:
After researching it some on my own, it looks like I need to come up with a way to call showSoftInput() from one of the softkeys. It'd be ideal if I could get that to happen on menu long press, but if that's too far buried in proprietary configuration I'd settle for replacing the google voice search app mapped to the Search button long press.
Anyone have any tips on mapping system functions to a hardware key normally used for app launching? The lack of any keyboard in the browser is seriously inhibiting my ability to use this phone.
Click to expand...
Click to collapse
Have you tried emailing Anderweb? ADW launcher intercepts the home button. You might be able to do something similar. It might only work on the home screen though, as his app is running there. For a system wide thing you might need to mod the underlying OS files, framework maybe? I'm not sure where that stuff launches. You could try asking one of the Cyanogen devs, they might have found it. They add stuff to the power button long press menu at least.
Certain apps (Visual Task Switcher and Itching Thumb) remap the search and home buttons to open themselves. I imagine this same idea could be used for the menu button, but I've never seen it.
I don't always complain, but when I do, I #BlameWes
some success...
Well I got a little app to work at opening the keyboard on long press of the SEARCH key. I don't want to override the home function, which is what ADW for instance does. The only other button that has an available intent as far as I can tell is search. This is my first java anything, so I wouldn't expect much out of it (it may not even work on anyone's phone but mine) but maybe someone with better android chops can use it as a proof-of-concept for what I was thinking. Install it and when you long press the search key you can choose "Search for Keyboard!"
One pretty major caveat... the swype soft cursor doesn't act anything like I'd wanted when I was envisioning this. There's no "execute" button that works like a click, so while you can use the soft arrows to select links it's not gonna do you much good. Also there's no way to effectively use "select text" in the browser. Concept 2, if I ever get around to it, would probably be more like a replacement touchpad area below the current application window.
i would like to see an app to remap long press menu on my i9000, anyone has success? thx
Another reason to ditch Samsung firmware and use AOSP-based ROMs, like CyanogenMod or MIUI.
FYI, nearly every "ROM" made for Galaxy S phones are Samsung firmware. They're not built from source like ROMs for other decent Android phones, they are just original Samsung builds being modified like nuts. And they use the same Samsung framework (though usually customized for themes and removing of annoyances like battery-full popup), and usually still include most of Samsung's stupid fixes that make their Galaxy S system software the most different in structure compared to any other Android system.
By using AOSP firmware like CyanogenMod and MIUI, these problems (like menu-button keyboard binding getting screwed up by Samsung) don't exist, because they were never present in official Android release. When problems do come up for AOSP, they get fixed quick because the source code is actually available.
Summarized process of development:
Samsung-based ROMs: What's broken or runs like ****? Try to fix it. Hack hack hack, hope it works, if it fails try again. Submit to XDA
CyanogenMod (in general): If there is a problem, try to fix it. Write code, build, test. Make sure it works before putting it in "stable" branch. After that think of brand new useful feature to implement, code it, bug test a lot, request it to be used in official releases or just make your own CyanogenMod-based ROM with your own enhancements, like BiffMod for the HTC Dream.
Btw, the reason why Samsung put this keybind is because the original international Galaxy S doesn't have a dedicated search key, so they set the search function up with the menu button. Our problem is that Samsung was a lazyass and forgot to change back that binding to the original for the Vibrant, which does have a dedicated search button and doesn't need the menu binding to search.
But aosp roms have other problems like poor 3d performance and no gps/compass. If the issues get worked out, I suspect many devs will be switching to aosp builds.
6/29/11 Update: Add keycodes for EF02's "" and "Sym". Thanks EvilDennisR for providing the new keycodes, eyecannon for confirmation.
5/5/11 Update: Fix handling of ENTER key in fix_dead patch, i.e., make non-printable and emit carriage return. Thanks xbj9000 & Fnorder for pointing out this bug.
1/13/11 Update: Add key_logic patch from git to make ConnectBot use the correct hardware keymap, eliminating the need for the previous '_' & '-' swap workaround. Add fix_dead patch to fully implement combining accent (dead key) support. See note about combining accents on the Epic below.
12/20/10 Update: Add keep local connection patch. Add Tab, Home, End, Page Up/Down keys. Add partial support for Swype's edit keyboard.
12/1/10 Update: Fix use of arrow keys for moving the selection cursor when copying text.
Attached is a build of ConnectBot v1.7.1 modified to better support the Epic's keyboard. Also attached are the source patches against the v1.7.1 sources.
Changes are:
Make "" an alternate dpad-center (one press emits Ctrl, two presses emit Esc).
Make "Sym" emit Tab.
Make ".com" (Fn+"Sym") emit '`' (backtick, the only missing printable ASCII character).
Make arrow keys able to move the copy selection cursor.
Make "" and Enter (to support Swype's edit keyboard) select the copy region.
Make Fn+Left emit Home, Fn+Right emit End, Fn+Up emit Page Up, and Fn+Down emit Page Down.
Enable Tab key in Swype & other virutal keyboards.
Enable Home, End, & Cursor Jump in Swype's edit keyboard. Cursor Jump makes the arrows emit Home, End, Page Up/Down.
Workaround to make Fn+W emit '-' (hyphen/minus) and Fn+E emit '_' (underscore).
Make ConnectBot use the correct hardware keymap for the Epic, fixes the swapping of '-' & '_' and other subtle keymap bugs.
Although the hardware-keyboard changes are specific to supporting the Epic, this build should run fine on other devices--I don't think the keymaps conflict.
About the workaround: in regular ConnectBot v1.7.1, Fn+W emits '_' (underscore) while Fn+E emits '-' (hyphen/minus), which is backwards compared to other applications. I'm not sure why this is, as the key character map appears to be correct from what I can tell. This bug is due to ConnectBot's previous method of decoding key characters where it assumes the hardware keymap is the first one specified in the Android properties database (hw.keyboards.0.devname), which it is not on the Epic. A fixed method of decoding key characters was comitted to ConnectBot's github repo last month in a patch that also partially (brokenly) implements support for combining accents. I've added this patch and another to this release to fix both the swap bug and fully implement support for combining accents.
Note on combining accents: The standard Epic keymap does not include support for combining accents (dead keys). I've posted a modified keymap to add these. See the thread for details.
I've also added a patch to reenable the use of arrow keys (on both hardware and virtual keyboards) to move the selection cursor when copying text. You may use either "" (hardware keyboard) or Enter (both hardware & Swype's edit) to select where the start and end the copy region.
Unfortunately Swype's Select All, Select Text, Cut, Copy, and Paste keys do nothing in ConnectBot as they do not emit keycodes, but copy & paste support is availble via the menu, arrow, and Enter keys. Also, Swype's Page Up/Down keys simply generate 5xUp/Down arrows. Cursor Jump+Up/Down may be used a real Page Up/Down instead.
Enjoy!
Mirror links (does not require forum login):
connectbot-1.7.1-epic-6.apk
connectbot_create_outdir.diff
connectbot_fix_copy.diff
connectbot_keep_local.diff
connectbot_key_logic.diff
connectbot_fix_dead.diff
connectbot_epic_keymap.diff
connectbot_swype_keymap.diff
very nice, thanks much for this.
5 bucks someone makes a comment about how this is in dev and not in the themes and apps board tho
shabbypenguin said:
5 bucks someone makes a comment about how this is in dev and not in the themes and apps board tho
Click to expand...
Click to collapse
Crud, I figured I made a mistake somehwere.
I don't believe I can move the thread myself, would the powers-that-be mind placing this in the appropraite location? Thanks!
Thanks
Wrong forum or not, this is perfect, I was going to change my system keylayout to accomplish this before, but this is a much better solution.
Amazing, thanks for this! ConnectBot was near-perfect for my needs, you just pushed it over the finish line
Haven't tried it yet, but I was just about ready to do keymappings identical to yours at the android layer... I like your solution a lot better, though, thank you!
Thx for this op!!!
Sorry, but im just about a month into the "rooting scene" and am not yet familiar with what this is, can someone please explain?
Sent from my SPH-D700 using XDA App
this will allow you to change what keys do what, it is a very handy app
Will it prevent the Epic from missing keystrokes???
JungleJiujitsu said:
Sorry, but im just about a month into the "rooting scene" and am not yet familiar with what this is, can someone please explain?
Click to expand...
Click to collapse
ConnectBot is an open-source terminal emulator and SSH client for Android. If you're a Windows user, think of it as a combination of the "Command Prompt" and PuTTY programs, but for your phone.
The Epic is an important device for ConnectBot users as it's one of the few programs that really requires (or at least benefits from) a hardware keyboard. Unfortunately, the Epic keyboard, while very good compared to the Droid (and I'd argue the G2 also) is missing a few keys important for ConnectBot, but has other extra keys that are unused. So this is a modified version of the program to better support the Epic's keyboard, making ConnectBot much more convenient to use.
In general ConnectBot is not a particularly important program for "rooting" (although root makes it vastly more useful locally). As suggested earler, this thread should really belong in the Themes & Apps forum.
That said, I imagine ConnectBot is a somewhat popular program among Epic owners as its (near) requirement of a hardware keyboard makes the Epic a much more suitable device to use with it than the Evo, and so those folks interested in using it are more likely to purchase an Epic.
This is awesome. Thanks a lot! Now ConnectBot is pretty much perfect.
shabbypenguin said:
this will allow you to change what keys do what, it is a very handy app
Click to expand...
Click to collapse
So is it like what someone posted a few weeks back on how they changed the smiley face key to place an @ symbol instead, but only now with this app I can change it to whatever I want?... TIA
JungleJiujitsu said:
So is it like what someone posted a few weeks back on how they changed the smiley face key to place an @ symbol instead, but only now with this app I can change it to whatever I want?... TIA
Click to expand...
Click to collapse
shabbypenguin is incorrect. ConnectBot has nothing to do with altering keyboard mapping for the entire system. I just posted a modified version of ConnectBot that has altered keybindings internally.
As a terminal emulator, it is unusual compared to most Android applications in that much of the hardware keyboard support is implemented internally (from the keycode level up) instead of using standard input widgets.
Sorry for the confusion.
Awesome work. Is there a Ctrl shortcut on the regular build? I got stuck the other day because I couldn't Ctrl+C out of an app.
Sent from my SPH-D700
Forcystos said:
Is there a Ctrl shortcut on the regular build? I got stuck the other day because I couldn't Ctrl+C out of an app.
Click to expand...
Click to collapse
Not on the hardware keyboard. But if you tap the screen an icon "Ctrl" and "Esc" appear that you can tap.
Awesome, muchas gracias. Can we donate?
I'm curious... does this version still disconnect in local mode when a call comes in? I like Connectbot, but being disconnected while editing my script locally with vi editor, was something that irritates me with the version I tried from the Market.
After researching the bug, the only fix I saw was a different source tree with a fix included.
If this fix is included, it would finally replace the Android Terminal for me.
Thanks for working on this for the Epic, by the way!
Sent from my SPH-D700 using Tapatalk
DRockstar said:
I'm curious... does this version still disconnect in local mode when a call comes in?
Click to expand...
Click to collapse
The update I just posted fixes this now. Somehow I never managed to run into this, but I was able to reproduce the problem and it's pretty annoying. Thanks for pointing out the patch.
Alt key?
I cannot for the life of me figure or find out how to use the Alt key w/my Epic. What am I missing? It must be supported....
-
ABOUT
ULTRA KEYBOARD has many features designed to give you a better Android keyboard experience.
Only $2.49 on Google Play! There is a free (48 hour) demo available.
https://play.google.com/store/apps/details?id=com.binarybulge.android.apps.keyboard.full
Look for us on AndroidPIT too, if you prefer (they accept PayPal!).
http://www.androidpit.com/en/android/market/apps/app/com.binarybulge.android.apps.keyboard.full
-
FEATURES
Choose your favorite way to type.
Touch-type like usual, or combine adjacent keys into COMPACT KEYS so they're easier to press. Slide your finger over words using WORD TRACING (instead of touching each individual letter).
The SUGGESTION BAR is smart and easy to use.
Choose words with just one swipe, even if they're not visible at first. A built-in English LANGUAGE DICTIONARY is included (and many other languages are available for download). Add new words to your personal CUSTOM DICTIONARY. BLACK LIST words you don't want to show up anymore.
Use WORD REPLACEMENTS to automatically expand abbreviations.
Tired of always typing "be right there"? Try "brt". You can even create your own.
The TOOL BAR provides a ton of functionality in a small amount of space.
You can scroll, drag, or flick through the available buttons.
Use SPEECH-TO-TEXT to transform your spoken words into text.
TRANSLATE your text to dozens of different languages.
CUT, COPY, and PASTE with a built-in CLIPBOARD.
Text you copy is saved so you can access it later. Remove anything you don't want to keep.
FULL-SCREEN MODE provides TEXT SELECTION HANDLES and a MAGNIFIER.
Accurately select portions of text to edit or copy.
The CHARACTER MAP makes more Unicode characters accessible.
Set up your own list of favorites for easy access. Includes Emoji on Android 4.1 devices.
Use the CAMERA OVERLAY* to see where you're going.
Watch what's in front of you while you type on the go. (* Android 2.3 or newer only.)
Create custom ACTIONS triggered by GESTURES or device buttons.
Want to swipe left to delete the previous word? Want your device's search button to activate the camera overlay? Do all this and more.
A DYNAMIC UI means you can customize the keyboard so it's perfect for you.
Are the keys too tall for your liking? Make them shorter. Don't like the ARROW KEYS? Hide them. Many things can be tweaked directly from the tool bar.
Change the keyboard's look with downloadable THEMES.
You can use the built-in THEME EDITOR to create your own themes, or customize existing themes with your chosen fonts and colors. You can even use themes designed for other keyboards!
-
CHANGE LOG
7.4.3 (1/31/2014)
Fixes:
Crashes involving the clipboard feature
Lag when updating the suggestion bar
Activity stack state issues when visiting settings/help from keyboard/tool bar
7.4.2 (1/30/2014)
Fixes:
Regression preventing lock screens from working
Problems with new word list interface
Clipboard tool wasn't honoring max entry setting
7.4 (1/29/2014)
Additions:
Customizable actions for long pressing modifier keys
Show the current dictionary on the space bar when multiple dictionaries are installed
A Done button in the full-screen editor
Improvements:
New interface for word lists (custom dictionary, replacements, clipboard entries, black list)
Made tool bar smoother and more predictable
The original suggestions are restored when undoing a selected traced word
Made it easier to cancel popup keyboards by dragging away from them
Only made certain dialogs transparent (the tool bar's Themes button for example)
Fixes:
Palette overlay in color picker didn't work
Character Map font color was wrong for light themes
The Done button didn't always dismiss the keyboard
Fixed crashes
7.3 (1/8/2014)
Additions:
"Character Map" feature (with Emoji for 4.1+ devices)
"Show Watermark" setting
Fixes:
Improved word tracing
Suggestion bar location was too low on 4.4 tablets
Couldn't always type in URL fields after tracing a word
Backspace didn't always work with selected text on 4.1+
Couldn't undo word corrections in some instances
Disabling "Typing->Capitalize Sentences" didn't work
Shift key wasn't always being updated after turning screen back on
Jumpy tool bar popup text
Fixed crashes on older versions of Android
7.2.1 (10/15/2013)
Suggestions:
Cursor position was sometimes incorrect when correcting existing words
Non-lowercase blacklisted words didn't persist
Typing:
Backspace deleted recently pasted text even after typing
Keys:
Previews could get stuck if keys were pressed as the keyboard was closing
Enter key long-press "take the default action" didn't work correctly
Tool Bar:
Position wasn't saved after a scroll
Emotes didn't show properly on certain versions of Android
Full-screen:
Cursor handles/magnifier could get stuck showing after leaving full-screen
Sentence capitalization didn't always work
Editor text didn't always get cleared when sending messages
Other:
Forced status bar to be shown when the keyboard is showing (avoids positioning issues)
Added direct app links to Facebook and Twitter profiles
7.2 (10/10/2013)
Suggestions:
Improved accuracy and speed (especially while tracing)
Undoing a suggestion sometimes mangled the text
Backspace deleted too many characters at times
Expanding the bar no longer steals focus from the current app
Typing:
Fixed capitals and symbols for shell/remote access apps
Prevented arrow keys from being triggered while typing
Improved popup key animations
Enter Key:
Fixed "Take the default action" behavior
Line break wasn't working on Android 4.3
Other:
Added "General->Show Automatically" setting
Worked around Android 4.3 clipboard crash
Popups (key previews, magnifiers, cursor handles) could get stuck on-screen
Tool bar item text size was too small for certain screen sizes
Increased heap size for extra-high-resolution screens
Crash fixes
7.1.1 (9/19/2013)
Fixes:
Enter key regressions (can't get past security/password lock; "Insert Line Break" broken)
Various crashes
7.1 (9/16/2013)
Additions:
Any selected text can be shifted
"Show/Hide Suggestions" action
Hidden characters on dedicated digit keys
Set default menu action to "none"
Theme names up to 32 characters
Updated key sounds
Fixes:
Editor button issues
Suggestions close when toggling full-screen mode
Compact popup keys close incorrectly
Compact alpha layout issues
Suggestion text size for small bar heights
Selected theme not migrated from demo
Inconsistencies in settings
7.0.1 (9/1/2013)
Fixes:
Issue deleting characters on Galaxy devices
Various crashes
7.0 (9/1/2013)
Additions:
Full-screen mode
New tracing animation
Physical key actions
Improved camera mode (with front-facing support)
New theme styles
Fixes:
Got rid of HUGE memory leak. Memory usage will be much lower now.
Many crash fixes.
LOTS MORE! Way too many to list here.
-
like this
good job I really like this app use it all the time
Hi, i have galaxy mini running stock 2.3.4 and market said its not compatible...why? and when i tried leaked version it was function but i cannot download language packs or skins...i really want to use it so ill buy it, but without support for my device...you know
i likeee...
Nice. I like this keyboard. It works really well. I tried the trial and purchased the full app today. Thanks OP.
Updated to v6.1.03.
· Added new built-in themes (Froyo, Gingerbread, Ice Cream Sandwich).
· Added new "Recent Apps" tool bar button.
· Added "Translate" option to dictionary button.
· Fixed performance issues.
· Enabled tracing (portrait) and disabled compact keys by default.
HI can you make it compatible with LDPI phones such as GALAXY MINI?Id like to use it on my phone...and does it support czech language ? if no dont bother with reply to compatibility issues
6.1.04:
· Fixed regressions (capitalization being ignored, full keyboard using compact suggestions).
Gnaver said:
HI can you make it compatible with LDPI phones such as GALAXY MINI?Id like to use it on my phone...and does it support czech language ? if no dont bother with reply to compatibility issues
Click to expand...
Click to collapse
I guess I was sort of hoping the LDPI phones have gone the way of the dinosaur. ;-) Was also thinking maybe Ultra is a little too heavy weight for lower-spec'd phones.
I'll definitely look into this. The medium DPI images should be scaled down on-the-fly on LDPI devices, but I think keeping Android 1.5 (Cupcake) support broke this.
I like to use forever !!!!! Link ?
Looks like a nice app
Updated to 6.1.06.
· Added an "Exit/Unload" option to the status bar menu.
· Fix: Word tracing crashes sometimes from native code.
· Fix: Certain black-listed words come back after restarts.
· Fix: Suggested words are incorrectly accepted when long-pressed.
· Fix: Suggested words stop working when editing a theme name.
· Fix: Suggested words stop showing at times, until the device is restarted.
· Fix: Clicking the status bar notification switches activities when the keyboard is open.
I linke!
Inviato dal mio Nexus S usando Tapatalk
Plz add option to change 'multi-tap interval' in t9
Sent from my GT-I9000 using Tapatalk
good, i will buy if there is russian language
Like this
Hi, got the Trial from the market...
Where can I change the Dictionary? Or is it disabled in the trial? I found Settings-Gestures-Dictionaries but it only offers me English.
And btw: can I migrate my old HTC personal Dictionary to the german one?
like this.
Updated to 6.2b.
· Increased performance and stability.
· Dictionary/tracing code completely rewritten.
· New theme features: can now stylize the suggestion bar.
· Almost too many fixes to count!
Hello fellow users from XDA,
I have a Galaxy S i9000 with a broken back button. That makes navigating pretty painful. In the rom called Slim Bean 4.2.2 Build 2 there are more options in the Hardware Keys section (including remapping the back button to, for example, the home button). I don't really like the ROM to be honest. My queston was, if there was a possibility to bring that to a different ROM (by flashing a ZIP-archive for example).
Greetings.
Rom developers generally do not respond to feature requests. You are better off trying to code it yourself.