Back button on the far left? Second from the right?
Power button on the top? On the side?
Softkeys or real buttons? On-screen (a la Honeycomb) or off-screen?
Do we need a search button at all?
A lot of sweat, blood, and saliva has been spilled over it. [citation needed]
Now it's *your* turn to join the fray!
If you were to design *the* perfect Android phone, what buttons would you give it? And where? And what would it be like?
Or maybe you don't even care about how the buttons are placed, as long as the manufacturers could just agree and they all make devices with similarly-placed buttons?
Me? I'd personally place the buttons sorted by their frequency of use, starting from the leftmost to the rightmost (from the most natural to the most awkward for my thumb to press). Back button - Home - Menu - Search, from left to right.
But I see how this would be an issue to left-handed people, so I'd settle for Back and Home button in the center, and Menu and Search flanking them. That's fair enough I think.
I would love to experiment with placing the back button on the top of the left side of the phone (indexable for right-handed people, and thumbable for left-handed), but I can see how this is not for everyone I'm not even sure I'd like it.
However, if manufacturers could just agree on the placement of the buttons, that would be good enough for me.
Whether it's hardware buttons or touchscreen buttons ain't an issue to me.
I'd place the power button top center (index-fingerable).
I find volume buttons useful only during calls, so I'd like to have them function as volume buttons only during calls. During idle/homescreen/any other scenario, they would become two (customizable!) shortcut buttons (a la Blackberry). <-- if only one thing from my dream phone is manifested, I hope it's this one. Two wasted (and often pressed by accident) buttons, turned into something more useful.
If I wanna be detailed about it, I guess the volume buttons should be on the center of the right side of the phone, so one of them can be customized as shutter/camera button (although I wont use it as such, preferring to tap the screen instead).
How's yours?
I think power button on top right side, lock button under, or like you mentioned having them function as volume buttons during call. Do completely away with search button, add in maybe a camera button where my search is, but make it where you have to hold it for a second so you do not enable it accidently. Have a designated capture button for the camera, that also functions as a silent/vibrate setting out of the camera.
Sent from my SCH-I500 using XDA App
Different people, different preference. Perhaps a default Home key, + 2 customizable keys where the user can choose their preferred key to be assigned.
I'd have the Search Key and Back Key always on the screen.
Menu key shouldn't even be on the phone. That should force app developer to design and create user interface with menu function incorporated in their app for consistency purpose.
I would love to have buttons on the back of the device
Now that I'm getting used to honeycomb (and apps developed for it), i can assure you that the search and menu buttons are not really necessary. i'd want a device with a back button on the left, the home button in the middle and a end call / power button on the right. that's it. oh i actually forgot a volume rocker at the usual spot at the side of the device.
Dustin.Dwayne said:
I think power button on top right side, lock button under, or like you mentioned having them function as volume buttons during call. Do completely away with search button, add in maybe a camera button where my search is, but make it where you have to hold it for a second so you do not enable it accidently. Have a designated capture button for the camera, that also functions as a silent/vibrate setting out of the camera.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm.. No search button.. Interesting.
I find it useful to search things from the homescreen without having to open a particular app first (be it Market, Springpad, Contacts, Evernote, etc.), but I can surely live without it
albling said:
Different people, different preference. Perhaps a default Home key, + 2 customizable keys where the user can choose their preferred key to be assigned.
I'd have the Search Key and Back Key always on the screen.
Menu key shouldn't even be on the phone. That should force app developer to design and create user interface with menu function incorporated in their app for consistency purpose.
Click to expand...
Click to collapse
Customizable keys FTW!!
JuanDeaux said:
I would love to have buttons on the back of the device
Click to expand...
Click to collapse
Wouldn't that be awkward, Mr. Doe?
fabsn said:
Now that I'm getting used to honeycomb (and apps developed for it), i can assure you that the search and menu buttons are not really necessary. i'd want a device with a back button on the left, the home button in the middle and a end call / power button on the right. that's it. oh i actually forgot a volume rocker at the usual spot at the side of the device.
Click to expand...
Click to collapse
Oh, you even made the pic!
Your opinion is interesting. I can easily see why the search button isn't really necessary, but the menu button? Substituted by long-press, I presume? (I never tried Honeycomb for any longer than 2 minutes )
I'm beginning to get glimpses of what ICS is gonna be like Keep it coming, guys! Let's crowdsource this!
Thanks to the moderator who moved my thread. I was hesitant on where to put my thread, but finally decided on the "General" forum, even though my OP contains questions, because I thought it was more of a "discussion" thread instead of a particular question trying to uncover a particular answer (which is what Q&A usually is)
Related
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?
I am a Touch Pro which does not have a PTT button.
Any suggestions on how to reach the camera quickly? What is your quickest way to get to the camera?
remap the center button on your phone to start up camera
mobileSCR Gscroll, map the capacitive area of the screen(where the buttons are), really useful(can choose any sequence of taps to do anything, open application)
or AEButton... what' the use of a volume rocker? just use one button to get to the volume page and use the touch screen to change the setting...(one problem would be changing vol on the fly like during a phone call... that case, change the setting, one-button press = default volume behavior, two-button press = whanever you want, three -button, long press, whatever you want
mputtr said:
remap the center button on your phone to start up camera
Click to expand...
Click to collapse
Thanks! I will try to do this but I cannot find the built in remap ap on NRGs rom, still looking for it :-D
@paperWastage: Thanks for the tip! If I cannot find the built in software I will install AE buttons.
you cant remap the center button. i think he was being pedantic. maybe you can set a button to be voice command and say "start camera".
I just have the camera in the programs... Slide over to programs and press camera...
The Jack of Clubs said:
you cant remap the center button. i think he was being pedantic. maybe you can set a button to be voice command and say "start camera".
Click to expand...
Click to collapse
actually... i was serious. There is a fuze keyboard config software floating somewhere in the raphael forums. It might be able to let you remap the centerbutton.
but why would you want to remap your center button.
The Jack of Clubs said:
but why would you want to remap your center button.
Click to expand...
Click to collapse
I have to agree as this is a very important function.
Mayne a Long press center button maybe more appropriate.
I cant seem to find any remap built in software on the NRG rom. My Touch dual had one which allowed me to remap some basic buttons like volume button.
Looks like AEbuttons is the answer for me. Will try to test it first and update you guys.
If you go to Setting and on the Personal Tab there is a Buttons setting and you can change the receive call button (press and hold of course) to whatever you want, including the camera.
Also a good idea to go over to the Systems tab and change the Long Press End Key Setting to Lock Device or something else than Turn Airplane mode on/off, god that sound is annoying when Airplane mode is turned on
it depends on the rom or software if you have the unlocked all buttons. honestly theres no faster way to get there than start > camera or photos tab > camera. if you dont have an american phone with a ppt button, there wont really be a faster way.
i actually did not mean to map the single click. I thought it was obvious i meant the long press.
using softkey manager you can replace one of the softkeys on the homescreen, as ur using an NRG rom im guessing your two softkeys on the home tab are "action" and "contacts"? ive got rid of the contacts, because a. i could jus use the people tab, or b. jus press the call button to bring up the dialer... and have replaced it with camera
the softkey manager should be under utililites/tweaks... it is on mine and im using an NRG rom
hope this helps.
On my N1 a long press of the menu button brought up the keyboard regardless of what app you were in. This is especially helpful in apps that assume you have a physical keyboard (e.g. androidVNC). With my Captivate holding the menu button brings up the Google quick search bar which I could care less about.
Is it possible to edit/change this function?
We can't get a stock Android ROM for this thing soon enough!
i was actually thinking about the same thing too.
Let me remind you, long press on the menu button is exactly the same function as short press on the search button, so we really need a "mod" that'll change the duplication function.
This would be really great. Does anyone have any ideas?
Sent from my SAMSUNG-SGH-I897 using XDA App
They have a thread going over here: http://forum.xda-developers.com/showthread.php?t=706426 about the touch keys and modifying them. It looks like the long key press stuff is in the kernel. Not much we can do at the moment.
Solution found,see this:
http://forum.xda-developers.com/showthread.php?t=818499
Basically, I read some user feedback from Knyghtryda's Camera Mod and came up with this very simple solution. I converted the Power Button to be the camera shutter, which also works for recording and 2.3.4 GB, and does not require a modified camera.apk. The Search Button was converted to function as power on/off. I made these changes by modifying the system/usr/keylayout files.
Honestly, I find this configuration awkward unless I am taking pictures. The search button is my least favorite button and normally only hit it by accident. If this is not an ideal configuration or you can't live without a search function, just give me suggestions.
I'm not a developer or anything, I just like to experiment with my android. If anyone, dev or not, has any suggestions or improvements feel free to comment.
v1.0
Power Button=Camera Shutter, Search Button=Power on/off, No Search Button Function
Issues 8/5/2011
I haven't confirmed this with Gingerbread, only with Froyo: If you remap power button to any other button, it will function as power button but if the screen is asleep and not plugged in for a period of more than about 10 seconds, you have to press original power button followed by the new power button to wake the screen.
I have also tested a few button remapping apps made for other devices, but do not seem to be compatible with Froyo. I will be testing Gingerbread next.
Added Key Configurations
Search Button=Camera Shutter, Power=Default
Credits:
Knyghtryda- idea for the shutter and scripts
Jack$on- idea to relocate power to search button
Installation Instructions
To Change Button Configuration
Run key_remapper.zip or key_remapper_GB.zip for respective firmware version in CWM.
To Return to Default Key Configuration
Run keymap_reset.zip or keymap_reset_GB.zip for respective firmware version in CWM.
DO NOT RUN WRONG VERSION: The files look very similar but I have ran Froyo zip on GB on two occasions and all of the bottom row buttons stop working.
I think making the Search button the default camera button would work better in the long run. Don't like the camera.apk hack.. i end up with a power menu a lot popping up.
Also the power button is just too close to the lens for me.. annoys me.
Is this a configurable mapper?
Just opened the zip.
I see what you did there. I never have gotten around to doing any mods myself yet, cool, can be configured however by changing the lists.
dlang123 said:
Just opened the zip.
I see what you did there. I never have gotten around to doing any mods myself yet, cool, can be configured however by changing the lists.
Click to expand...
Click to collapse
Very simple like I said, some people would be clueless though. Also your idea would work better for me as well.
This is very nice. I hate the power button being on the side of my phone. I feel like I can't use my phone one-handed or have to shift the way I'm holding the phone just to be able to turn the screen on/off.
One quick note... In CWM after installation it says that the power button = search button which is incorrect.
Big thanks! I've been waiting for someone to come up with this!
dlang123 said:
I think making the Search button the default camera button would work better in the long run. Don't like the camera.apk hack.. i end up with a power menu a lot popping up.
Also the power button is just too close to the lens for me.. annoys me.
Is this a configurable mapper?
Click to expand...
Click to collapse
ya I agree. if u just made the search button a camera shortcut key and a camera shutter key im sure alot of people would use it for sure.
Sent from my SCH-I510 using XDA App
PKizzo36 said:
This is very nice. I hate the power button being on the side of my phone. I feel like I can't use my phone one-handed or have to shift the way I'm holding the phone just to be able to turn the screen on/off.
One quick note... In CWM after installation it says that the power button = search button which is incorrect.
Big thanks! I've been waiting for someone to come up with this!
Click to expand...
Click to collapse
Thanks, I see my mistake on the script.
dlang123 said:
I think making the Search button the default camera button would work better in the long run. Don't like the camera.apk hack.. i end up with a power menu a lot popping up.
Also the power button is just too close to the lens for me.. annoys me.
Is this a configurable mapper?
Click to expand...
Click to collapse
Made the Search Button the camera button just for you. I have not tested this on the Froyo build but I do enjoy this configuration better than the other. I have also tested the camera button on the up volume button, but couldn't find a suitable volume up alternative.
sk8tingusmc said:
Made the Search Button the camera button just for you. I have not tested this on the Froyo build but I do enjoy this configuration better than the other. I have also tested the camera button on the up volume button, but couldn't find a suitable volume up alternative.
Click to expand...
Click to collapse
which zip do I download to get the search as camera key?
Sent from my SCH-I510 using XDA App
Can the search key act as a search key normally, except when in camera mode?
kolosok17 said:
Can the search key act as a search key normally, except when in camera mode?
Click to expand...
Click to collapse
I can experiment with it, but not sure.
EDIT: I am not having any luck; I am not saying it is impossible, but it looks like you will have to wait for Knyghtryda to release a modified camera app with with the search button shutter, with the system keymap still set as Search. That may solve your problem! I wish I knew how to make longpress of search do camera and shortpress do search, if it is even possible. I will still look into it, I have just given up for the night.
jkat797 said:
which zip do I download to get the search as camera key?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
The search_shutter.zip or search_shutter_GB.zip depending what version you are running.
The key mapper seemed to be working at first but I noticed that if my phone sat idle for awhile the search button (now the power button) wouldn't start the phone back up. I would have to use the power button (modded to be the new shutter button) and THEN press the search button to get the screen to come back on.
PKizzo36 said:
The key mapper seemed to be working at first but I noticed that if my phone sat idle for awhile the search button (now the power button) wouldn't start the phone back up. I would have to use the power button (modded to be the new shutter button) and THEN press the search button to get the screen to come back on.
Click to expand...
Click to collapse
Which build are you on? It may have left out the WAKE flag or something. Thanks for letting me know.
Mapping the volume up/down buttons to reflect 'next track' and 'previous track' while the screen is off would be my biggest request.
Can the home button mapped to wake up the phone instead of power? this is my top of the wish list, pretty plzzz
sangweb said:
Can the home button mapped to wake up the phone instead of power? this is my top of the wish list, pretty plzzz
Click to expand...
Click to collapse
That shouldn't be a problem, but I think that I forgot to edit an extra file that effects the bottom row buttons and it seems to be on Froyo builds. I am updating this file to test reliability right now.
sk8tingusmc said:
Which build are you on? It may have left out the WAKE flag or something. Thanks for letting me know.
Click to expand...
Click to collapse
I am on froyo
Sent from my SCH-I510 using XDA App
Please
sk8tingusmc said:
That shouldn't be a problem, but I think that I forgot to edit an extra file that effects the bottom row buttons and it seems to be on Froyo builds. I am updating this file to test reliability right now.
Click to expand...
Click to collapse
I'll be your quality test as guinnea pig if you need one. I know I can use other widget to accomplish this but prefer to avoid 3rd party lock widget because sometime I have to unlock twice. You will be my "God" if you can get it working, Thx.
So I started looking at modding the Camera.apk.. decompiled into byte code.. doesn't look that bad, if I get some time I'll run some diffs on it and the original get what he changed.. and then I'll try to modify it for using the search button. That way search only does Camera if your in Camera.
Anyone know if there's a way to make the home button only work with a hard press? I'm not referring to unlocking the phone or turning on the screen, I'm asking about when using the phone or an app and wanting to press the home key, I would like the ability to disable a simple tap and make it feel more like a button by utilizing the pressure sensor. Anyone know if this is possible?
Thanks in advance
Look in Settings, Screen, Navigation bar, Home button sensitivity.
(English descriptions translated from Italian)
Outbreak444 said:
Anyone know if there's a way to make the home button only work with a hard press? I'm not referring to unlocking the phone or turning on the screen, I'm asking about when using the phone or an app and wanting to press the home key, I would like the ability to disable a simple tap and make it feel more like a button by utilizing the pressure sensor. Anyone know if this is possible?
Thanks in advance
Click to expand...
Click to collapse
Try this-
set/display/navigation bar/Home button sensitivity
Sensitivity can only do so much, I have it on minimum for purely comfort, because it's much more effortless to unlock your phone when the tap doesn't have to be so intense. And if I really am force-pressing on the button area at any force, I am trying to unlock the phone, so I don't really see a point in having to press it with a lot of effort.
But I've found out that the button is very largely hardware-based, since it works and vibrates even when changing themes, when things like system UI are not active, and normal nav buttons and status bar are gone. So I doubt that any sort of third-party development will be done for it without root access, since the hard press function seems to work as a real button press, and not a virtual press.