Related
Hello XDA'ers,
I am wondering what the reason behind why the buttons (camera, power, green, red, etc.) in Android on HTC Vogue map to the various tasks they do? For example, the camera button is back, but why not the red button? Is this something hard set in Android and cannot be changed or did someone specifically set it up this way for a reason?
Secondly I am wondering if I create a new "keylayout file" (source.android.com/porting/keymaps_keyboard_input.html) or modify the default one in /system/usr/keylayout/qwerty.kl will I be able to change the mapping of these buttons?
Compared to the Win Mobile mapping, they button layout can take some getting used to,
but once you get used to it, it's actually a very cool layout, especially if you are right handed.
You can hold the phone in your left hand, and use your thumb to access the settings 'top button',
Use your ring-finger to always back-out or end an app
Green button for phone / initiating calls
Red button to end a call, sleep mode, or power off
I wish the d-pad had more use, but I'm always using the stylus, so barely use it.
Would love for the d-pad center key to maybe be the main power-off button.
Does_It_Matter said:
... It's actually a very cool layout.
...
I wish the d-pad had more use, but I'm always using the stylus, so barely use it.
Would love for the d-pad center key to maybe be the main power-off button.
Click to expand...
Click to collapse
I completely agree the current layout is a very cool layout indeed, but as I imagine most people on here like to tinker it may be interesting to know how to customize the button bindings.
I am not sure if its just a matter of changing the button layout file.
I looked at that qwerty.kl file in the android.tgz
It looks like its just a mapping file, and if you change the mapping, you change
buttons,
but doesn't that mean you're just re-mapping the button itself?
Not re-mapping its functionality?
I.e., if you remapped the camera button to the d-pad center, for example, then
the d-pad center would do all functions the camera button used to do,
and the camera button would do any functions the d-pad center would?
Seems like you'd actually have to change more code than just the .kl file?
i wrote this application for polaris, and with simple changes you can add the vogue setup...
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.
Is it possible to replace the menu button with the ICS Task Manager/Multitasker? like in the galaxy Nexus? I think even the icon looks similar in a way to a list of apps. This would be useful especially since ICS deals with this perfectly by showing a menu button when it doesn't detect it as a hardware button.
What do you guys think about this idea?
Why not just hold the home button to bring up recent apps..
Sent from my GT-N7000 using xda premium
joshnichols189 said:
Why not just hold the home button to bring up recent apps..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
pachi72 said:
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
Click to expand...
Click to collapse
Agree. Home buttons degrade and break.
pachi72 said:
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
Click to expand...
Click to collapse
VTEChump said:
Agree. Home buttons degrade and break.
Click to expand...
Click to collapse
Yep, and because given the choice, I'm sure most will opt to use it this way. the menu button is getting deprecated as a hardware button and being implemented more and more inside applications.
Hopefully some more ICS ROM devs will see this and review this suggestion. I would love to know what they have to say about it.
I wouldnt mind a widget to do it either. That shouldnt be to hard to do.
moyajaya said:
Is it possible to replace the menu button with the ICS Task Manager/Multitasker? like in the galaxy Nexus? I think even the icon looks similar in a way to a list of apps. This would be useful especially since ICS deals with this perfectly by showing a menu button when it doesn't detect it as a hardware button.
What do you guys think about this idea?
Click to expand...
Click to collapse
+1.
Regards.
This was the first thing I wanted to do after installing ICS. The capacative buttons are mapped in /system/usr/keylayout/melfas-touchkey.kl;
Code:
key 158 BACK WAKE
key 139 MENU WAKE
I'm just not sure what to replace 'MENU' with. 'TASK'?
Hate to double post but I thought I'd share what I've discovered.
I tried replacing 'MENU' with 'APP_SWITCH' in melfas-touchkey.kl and sec_touchkey.kl and got the menu button to act just like the recents button, however there was then no way to access the menu
I had a brief look at the android source code and it looks like the value that decides to show the action overflow button in the toolbar is set depending whether the on screen buttons are being used. Not at all sure about that though and I've seen the new HTC one phones have a hardware recents button replacing the menu so it can't be impossible.
bootlessjam said:
Hate to double post but I thought I'd share what I've discovered.
I tried replacing 'MENU' with 'APP_SWITCH' in melfas-touchkey.kl and sec_touchkey.kl and got the menu button to act just like the recents button, however there was then no way to access the menu
I had a brief look at the android source code and it looks like the value that decides to show the action overflow button in the toolbar is set depending whether the on screen buttons are being used. Not at all sure about that though and I've seen the new HTC one phones have a hardware recents button replacing the menu so it can't be impossible.
Click to expand...
Click to collapse
Thank you for trying this and letting us know about the results. I was thinking if all fails maybe the search option that appears when you click and hold the menu button could be replaced with the menu?
Clicking the Old menu button = New app switcher
Holding the old menu button = Menu
how about that? I think most apps include a search icon if/when they include search functionality.
Had a brainwave today and got it 90% there. I decompiled framework-res.apk and enabled the navigation bar AND resized it to 0. This means the action overflow button shows up in apps without the galaxy nexus-like software keys getting in the way. I then remapped the menu key and it is working like a charm
Of course then there is the little issue of bringing up the menu when using a pre honeycomb app. The simplest solution for me was to use the pen's button+swipe up gesture. This isn't ideal and doesn't even work for people using CM9 or stock ICS.
Here is the modified framework-res for the Team Rocket ROM v1.5:
dl.dropbox dot com/u/2340506/navbarhidden.zip
These forums don't trust me with links
Install with CWM recovery. Don't use it on any other ROM! I can't even guarantee it'll work on every team rocket rom. I'm too lazy to load every ICS ROM but if you post your framework-res.apk I can edit it for you.
After you can remap the hardware keys in /system/usr/keylayout/melfas-touchkey.kl and /system/usr/keylayout/sec_touchkey.kl like I mentioned earlier with Root Explorer or ES File Explorer. I have it set up to mimic the HTC one phones and the galaxy nexus's layout, since I keep the key lights off.
Hopefully this is useful to people. A better way to access the menu on old apps should be easier to do once people start tinkering with the HTC one phones.
bootlessjam said:
Had a brainwave today and got it 90% there. I decompiled framework-res.apk and enabled the navigation bar AND resized it to 0. This means the action overflow button shows up in apps without the galaxy nexus-like software keys getting in the way. I then remapped the menu key and it is working like a charm
Of course then there is the little issue of bringing up the menu when using a pre honeycomb app. The simplest solution for me was to use the pen's button+swipe up gesture. This isn't ideal and doesn't even work for people using CM9 or stock ICS.
Here is the modified framework-res for the Team Rocket ROM v1.5:
dl.dropbox dot com/u/2340506/navbarhidden.zip
These forums don't trust me with links
Install with CWM recovery. Don't use it on any other ROM! I can't even guarantee it'll work on every team rocket rom. I'm too lazy to load every ICS ROM but if you post your framework-res.apk I can edit it for you.
After you can remap the hardware keys in /system/usr/keylayout/melfas-touchkey.kl and /system/usr/keylayout/sec_touchkey.kl like I mentioned earlier with Root Explorer or ES File Explorer. I have it set up to mimic the HTC one phones and the galaxy nexus's layout, since I keep the key lights off.
Hopefully this is useful to people. A better way to access the menu on old apps should be easier to do once people start tinkering with the HTC one phones.
Click to expand...
Click to collapse
Great finds! Thumbs up!
Thank you for your efforts!
I would love to try those but I moved back to Gingerbread for the time being. ICS in the note is far from being a daily driver for me. A lots of bugs and battery drains compared to Gingerbread. Hopefully this will change quickly. I trust the dev community and i'm sure they'll beat samsung in having stable ICS releases...
Back to ICS. Using ICS Stunner 4.3 ROM with the new LP5 kernel and modem. This setup is simply stunning. Best ROM I've tried so far.
Back to subject, how can the process go for AOSP ROMs? Like this one I'm using...
Anyone found any other way around this? Thanks !
Sent from my GT-N7000 using Tapatalk 2 Beta-5
moyajaya said:
Back to ICS. Using ICS Stunner 4.3 ROM with the new LP5 kernel and modem. This setup is simply stunning. Best ROM I've tried so far.
Back to subject, how can the process go for AOSP ROMs? Like this one I'm using...
Anyone found any other way around this? Thanks !
Sent from my GT-N7000 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1450138
I looked into doing the same thing as you did only because I love the tablet layout and holding the home button doesn't bring it up.
In order to get what you and a few others would want on select roms, the source for the framework would have to be adjusted as said in the thread, meaning each dev would have to implement this independently.
The second thing is alread mentioned in this thread, which is changing the key layout.
You can hope that the dev has no issues with inserting it into their build.
NOT changing the source but editing the key layout will only bring up the a Gingerbread styled task switcher. I've tried ;_;
I personally might I add, would just love the same hold the home button functionality while in tablet mode.
evilisto said:
1) change source code related to APP_SWITCH keycode.
platform/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
from :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0) {
showOrHideRecentAppsDialog(RECENT_APPS_BEHAVIOR_SHOW_OR_DISMISS);
}
return -1;
}
to :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0 && !keyguardOn) {
try {
mStatusBarService.toggleRecentApps();
} catch (RemoteException e) {
Slog.e(TAG, "RemoteException when showing recent apps", e);
}
}
return -1;
}
2) edit your keylayout files..
/system/usr/keylayout/
for example, if you want to use search key to recent apps on nexus s...
cypress-touchkey.kl
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 APP_SWITCH VIRTUAL
and mxt224_ts_input.kl (it would be better to edit both files..)
Code:
key 158 BACK WAKE
key 139 MENU WAKE
key 217 APP_SWITCH WAKE
key 102 HOME WAKE
Click to expand...
Click to collapse
Details of the device
I'm using the latest CM11 version from Novafusion.
Problem and steps I've taken
Currently I've got a problem where the home button intermittently activates on its own (but only long-presses, so if I disable long-press in the OS, it'll be fine for normal operation), without any interference. The side effect (which is my main issue) of this is that it means my phone's screen effectively turns on by itself 24/7, which is obviously bad for many, many reasons.
I'm asking whether there's anyway I can disable the home button? I've tried Android-HomeKey-Locker (can't link it, but the Google Play version of the thing on GitHub) but it hasn't done anything.
I'm aware I can turn on the software buttons, but they don't deactivate the physical buttons: and I only want to disable home anyway.
So my question is, is there any way of doing this? I can take the back and menu keys if needed.
Side note
Is it possible in anyway to bind long-press back to home? I asked this for CM12 a while back (and I've since downgraded), but is this possible with Cyanogen, as I've been able to do it with Carbon ROM on 4.4.4.
Hi! I currently use this app on CM 12.1 to enable softkeys and disable hardware keys:
https//play.google.com/ store/apps/details?id=net.alviano.android.softbuttons&hl=en
sorry for my bad english
Hi
Try disable the home button by following this. it worked for me
http://forum.xda-developers.com/showthread.php?t=2032117
Hey everyone,
Thanks for the help. Someone on reddit gave me a working solution by using Xposed Additions to remap the buttons how I wanted them to.
Hello,
after the sources for the Z2 Pro have been released and good Custom ROMs are possible, I would love to buy this beautiful device. I've read alot about this U-Touch thing, where you navigate only by using the Home Button... and I don't like it. So my question is: Does this phone also have the normal Back, Home and Recents hardware buttons?
Thanks!
Hi,
Yes, you can add on screen buttons in "Developer Options" menu. At least you can do it with z2 (non pro). I guess you will have this option too.
So there are no "real" hardware buttons to the left and the right of the home button?
On screen buttons are in developer options in both models, make sure you reboot to effect the changes.
Thanks for your answers. I know about the possiblity to show the On Screen Buttons, but that's not what I wanted to know.
I'm curious if the device also has dedicated hardware buttons (not on screen) for Back and Recents, or just the U-Touch button?
It only has 1 physical button on the front..
I'd love to see an app or even integration in a custom rom to be able to configure the behaviour of the front button. What are the chances this will become reality?
It already lets you configure what the button does. You can also preset actions to open specific apps.
Karly Johnston said:
It already lets you configure what the button does. You can also preset actions to open specific apps.
Click to expand...
Click to collapse
But that is in the ZUI ROM right? I'd like to see this in a separate app or built into custom ROM so it can also be used outside ZUI.
Now that the sources are available someone who knows what he is doing should be able to pull this off.
Is there a way to make swipe left on the u-touch button act like a back button? Maybe there would be a way to have it open an scripted action that acts as back button?
Edit: Just figured out that short tap is back, so my problem is solved!
Thanks, this helped me out!
I'm looking for a phone with this same exact button. I'm always super stunned how retarded iphones are compared to my $200 phone.