Database Develop

change button layout

just wanted to see what everyone thinks about the button layout.
should we keep it?
should we change it?
how can we change the button layout ourselfs?
is there any progress on making an application to allow us to change our button layout?
what does everyone think?
im used to the button layout now but i would love to customize it to my liking.

There needs to be a third option. "Allow for customization"
Everyone perceives their needs differently.
EDIT: Should also mention that I'm fine with it the way it is, but the way your post is worded makes the third option necessary.

Leave it,
Its perfect.

leave it. Only add button combination for running apps.. If everyone's is different, you will have a hard time giving directions based on buttons.

i like it the way it is as well. the only thing nicer would be more buttons; if we were able to get the red button to "go home, then sleep" it would allow long press camera to be used to display running applications.
a program to modify the keymap was in the works. don't know what happened to it.

i think it would be awsome if the keymap were like this. power is power, volume is volume, 1 tap camera goes to landscape, long press camera goes to camera, left d-pad is back, right d-pad is forward, up d-pad is menu, down or center d-pad to go home, red end button as is, green button as is.

cp0020 said:
i think it would be awsome if the keymap were like this. power is power, volume is volume, 1 tap camera goes to landscape, long press camera goes to camera, left d-pad is back, right d-pad is forward, up d-pad is menu, down or center d-pad to go home, red end button as is, green button as is.
Click to expand...
Click to collapse
can't change dpad function - need it for many games. for those who don't play games, would be great. once again, individualizable keymap seems best.

I personally like it.
We used to have an older configuration but this current one seems very usable making efficient use of the keys we have.

I like it as it is.

myn said:
I personally like it.
We used to have an older configuration but this current one seems very usable making efficient use of the keys we have.
Click to expand...
Click to collapse
If you mean the original, menu on the volume slider, that was THE worst. Last year I quit Android as soon as I started because I hated using the volume slider all the time.

slow88lx said:
If you mean the original, menu on the volume slider, that was THE worst. Last year I quit Android as soon as I started because I hated using the volume slider all the time.
Click to expand...
Click to collapse
personally i was in love with the old layout
i loved how holding the home button showed all running apps and made switching between them a breeze
if we could somehow incorporate the old layout
id be all for it!
even though i'm accustomed to the current one

cp0020 said:
i think it would be awsome if the keymap were like this. power is power, volume is volume, 1 tap camera goes to landscape, long press camera goes to camera, left d-pad is back, right d-pad is forward, up d-pad is menu, down or center d-pad to go home, red end button as is, green button as is.
Click to expand...
Click to collapse
it would be cool to have that button layout and make the center d-pad to swith back to the current button layout so we can use the d-pad for games and whatnot.

cp0020 said:
it would be cool to have that button layout and make the center d-pad to swith back to the current button layout so we can use the d-pad for games and whatnot.
Click to expand...
Click to collapse
That just seems overly complicated.
When I first switched to Android, I hated the layout, but it's grown on my now. Only thing I wish is for a spare button that could be made into a search button so I could have working quick compose in chomp sms.

preardon said:
That just seems overly complicated.
When I first switched to Android, I hated the layout, but it's grown on my now. Only thing I wish is for a spare button that could be made into a search button so I could have working quick compose in chomp sms.
Click to expand...
Click to collapse
if we can put android on our phones i think we can do that

cp0020 said:
if we can put android on our phones i think we can do that
Click to expand...
Click to collapse
I was saying more from a user standpoint than a development standpoint.

Would you recommend remapping the volume buttons?

Just wondering if people have done it and didn't like it, or vice-versa. It does seem bad for the hardware, but I can't stand softkeys/button saviour.

If you're using nookie Froyo, you can try the MENU/BACK soft buttons in the status bar mod, instead of remapping the vol+/- buttons. I've been using it since it came out, and can confim it works for nookie Froyo 6.7. Here's the link to the original thread: http://forum.xda-developers.com/showthread.php?t=932631
It does have it's issues, mainly with the stock browser, and causing it to FC. Other than that I have not noticed any other problems.
If you are interested in useing the mod, but don't know how to install it, let me know. I'll pm you or post instructions.

I absolutely recommend remapping the volume buttons. Softkeys is nice, but kind of a pain sometimes. For instance, when I would view pictures in the XDA APP, I would have to restart the app instead of backing out, for some reason softkeys wouldnt let me back out of the picture viewer. It's just much easier to have the menu and back buttons always available than rely on software. I installed volume volume control if I need to adjust volume for some reason.

Is there an app that puts volume in the status bar that anyone knows of?

buffnutz1 said:
Just wondering if people have done it and didn't like it, or vice-versa. It does seem bad for the hardware, but I can't stand softkeys/button saviour.
Click to expand...
Click to collapse
Yup... I've got a Pandigital Novel(white v2) w/custom fw and it'd be essentially useless w/o re-mapping the vol keys to menu and back along with soft-keys in the notification bar...
NC has one up on the WPDN though, it has the n home key plus the 2 vol keys and volume can be controlled through setting or a quick-settings app anyways or by adding soft-keys... still no substitue for physical keys or capacitive screen keys though, unfortunately... (spoilt by gtab with the full complement...)

-------------

buffnutz1 said:
I'm sure you guys know where I'm screwing up. After I adb pull, I only get this
/system/usr/keylayout/twl4030-keypad.kl -> ./twl4030-keypad.kl
/system/usr/keylayout/qwerty.kl -> ./qwerty.kl
/system/usr/keylayout/AVRCP.kl -> ./AVRCP.kl
but it says to edit " 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' "with your text editor of choice; I used vi, always a safe choice.
I don't have the omap. what should I do?
Click to expand...
Click to collapse
Just modify the qwerty.kl in the place of omap. That's what I did and things are working fine.
--ex

Love my remapped buttons and i saved the originals so i can go back anytime i wish.

buffnutz1 said:
Is there an app that puts volume in the status bar that anyone knows of?
Click to expand...
Click to collapse
I am on the stock 1.1 rooted and have mapped my volume buttons - I have tried the other ones, and I MUCH prefer having hard buttons.
I downloaded a volume app "Volume Master Free". It has about 5 different volume controls, but I only use the system volume and the media volume controls.
I use Zeam as home screen; and I put a shortcut to Volume Master on the bottom right of my Zeam shortcut bar. It works very well. I do need to go to the home screen to change volume; but I can tap on the notification bar and toggle mute, so that works for me.

Yes, it makes a huge difference on the stock rom and froyo -- though honeycomb's soft buttons eliminate the need to do so.

Can't recommend remapping the keys enough. On froyo it makes a huge difference in functionality on. The device, life is a pain without it.

how do you remap the vol buttons? i would love to do it

TweetyBear said:
how do you remap the vol buttons? i would love to do it
Click to expand...
Click to collapse
Go here for instructions:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
--ex

I remapped.
I also recommend remapping your volume buttons. It's handy having tactile buttons for the back and menu functions.
What really sold me on remapping was that I didn't like to have a Softkeys button floating on the home screen. Without a floating button, I would have to double tap the hardware "N" button to bring up the Softkeys interface, then hit "menu" or "back." If I have to double tap a hardware button to use "menu" or "back," I might as well just remap those functions to the volume buttons and use a single tap.

evilxenu said:
Go here for instructions:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
--ex
Click to expand...
Click to collapse
thanks. will attempt over the weekend

can remapping the volume buttons be done when running cm7 nightlies off SD ?
I didn't find a definitive answer

I ran with the CM7 softkeys, Button Savior, remapped volume keys and I just finally settled on zMooth.

Why is soft keys necessary on stock rooted NC?

Does everyone realize that on a stock rooted nook, if you swipe right to left on the status bar on the bottom, it's a 'back' button? I don't get why soft keys is necessary. I shut it down on both my nooks and have never once needed it. Just extra overhead, to me...
Can someone educate me as to why this program is so 'important'?

doncaruana said:
Does everyone realize that on a stock rooted nook, if you swipe right to left on the status bar on the bottom, it's a 'back' button? I don't get why soft keys is necessary. I shut it down on both my nooks and have never once needed it. Just extra overhead, to me...
Can someone educate me as to why this program is so 'important'?
Click to expand...
Click to collapse
Full screen apps like angry birds? I also fail to see why this issue was so important to you that you had to make a thread about it. Softkeys is an optional app, you don't have to install it yourself.

I personally use Button Savior, less noticeable and easy to access.

ewong90 said:
I personally use Button Savior, less noticeable and easy to access.
Click to expand...
Click to collapse
Button Savior looks like much nicer than Soft Keys - what basic steps to remove Soft Keys and run Button Savior instead? Any gotchas? Im also using the Gingerbread keyboard and hope this change wont affect that?

timekeeper said:
Full screen apps like angry birds? I also fail to see why this issue was so important to you that you had to make a thread about it. Softkeys is an optional app, you don't have to install it yourself.
Click to expand...
Click to collapse
I can always use the home button (and then a task killer if needed) to get out of the few full screen apps that won't let me back out.
But softkeys is part of the autonooter package, which a lot of people use - I didn't specifically install it. I haven't used the other 'packages' - not sure if it's included there as well. It's positioned as a "must have", but doesn't really seem to be. So someone thought it was important enough to include there and so I wanted to know why.
Gee. I'm sorry. I guess I'm not allowed to ask questions? Should I ask you if you deem an issue important first before I ask a question in the future?
Here's my next question - let me know if it's important enough: Why did you have to be an ass about my previous question?

timekeeper said:
Full screen apps like angry birds? I also fail to see why this issue was so important to you that you had to make a thread about it. Softkeys is an optional app, you don't have to install it yourself.
Click to expand...
Click to collapse
No offense timekeeper but I was wondering the same thing, so I found this helpful.

It's not just the back key that's important.
Most apps have additional functionality that you can only access via the 'menu' key.
That's the one I find most needed.

ewong90 said:
I personally use Button Savior, less noticeable and easy to access.
Click to expand...
Click to collapse
Ditto. Soft Keys does a passable job, but the attractive design and customizability of Button Savior makes it a better choice.

I wasn't a fan of the softkey button size and could never find a place on screen that i liked it. Button Savior is much better. Both add a huge amount of functionality to a rooted NC.

Except you don't see any silly on-screen buttons with SoftKeys if you set it up properly.. Then you just press the N key once or twice, depending upon config, to get the pop-up with back, menu, etc..
http://nookdevs.com/NookColor_Default_Launcher
As for the Op saying "Can't I ask questions?" Sure you can, just don't act like a free piece of software which is VERY useful is somehow killing you .

ajaik said:
Button Savior looks like much nicer than Soft Keys - what basic steps to remove Soft Keys and run Button Savior instead? Any gotchas? Im also using the Gingerbread keyboard and hope this change wont affect that?
Click to expand...
Click to collapse
Just make sure you have USB debugging enabled. You don't have to uninstall softkeys, just disable it. Button Savior should run normally from startup and shouldn't affect anything else.

doncaruana said:
Does everyone realize that on a stock rooted nook, if you swipe right to left on the status bar on the bottom, it's a 'back' button? I don't get why soft keys is necessary. I shut it down on both my nooks and have never once needed it. Just extra overhead, to me...
Can someone educate me as to why this program is so 'important'?
Click to expand...
Click to collapse
I didn't know you could swipe to go back, so thanks for that.
There are some apps that run full screen and the status bar isn't visible which then you would need either soft keys or button savior.

I went ahead and uninstalled SoftKeys. Button Savior rocks.

[Q] Enable Software + Disable Hardware Buttons

So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.

rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
not until we have s-off. The emmc checks files against its last known configuration and discards any changes. Its been that way since the evo3d. its the same reason supercid wont stick also.

Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?

rougegoat said:
Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?
Click to expand...
Click to collapse
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.

benmatlock said:
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.
Click to expand...
Click to collapse
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.

rougegoat said:
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.
Click to expand...
Click to collapse
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...

tmuka said:
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...
Click to expand...
Click to collapse
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."

rougegoat said:
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."
Click to expand...
Click to collapse
Yeah, sorry, i realize i didn't answer your question. I hope you find the low level solution you're searching for, and that my tip helps you in the short term.

rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE

luisrod03 said:
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE
Click to expand...
Click to collapse
No dice. The files are editable but have no impact.

Is there now any way to disable the hardware keys? I only want to have software keys (paranoid android 4.4 rc1)
Gesendet von meinem Nokia 3310 LTE

Kernel that just enables logo as a button?

I am running stock GPE android 5.1 (though my phone came with Sense). I want to change the capacitive buttons to match the normal google layout i.e. I want to enable the htc logo as the home button and change the home button to display recent apps. Is there a simple kernel that will just do this and nothing else? If not is there a simple kernel that will just enable the htc logo as a button and not give me options to overclock or change a bunch of other stuff? Thanks for your help.

the_angel_moroni said:
I am running stock GPE android 5.1 (though my phone came with Sense). I want to change the capacitive buttons to match the normal google layout i.e. I want to enable the htc logo as the home button and change the home button to display recent apps. Is there a simple kernel that will just do this and nothing else? If not is there a simple kernel that will just enable the htc logo as a button and not give me options to overclock or change a bunch of other stuff? Thanks for your help.
Click to expand...
Click to collapse
I don't know exactly if you can do that specific option with this kernel, but ElementalX has the aroma installer so you can leave everything stock without having to overclock and you enable just the features you want. I'm running it with Logo2Menu, so maybe there is an option to change the button arrangement. Doesn't hurt to give it a try.

the_angel_moroni said:
I am running stock GPE android 5.1 (though my phone came with Sense). I want to change the capacitive buttons to match the normal google layout i.e. I want to enable the htc logo as the home button and change the home button to display recent apps. Is there a simple kernel that will just do this and nothing else? If not is there a simple kernel that will just enable the htc logo as a button and not give me options to overclock or change a bunch of other stuff? Thanks for your help.
Click to expand...
Click to collapse
You don't want that feature trust me. It doesnt turn the logo as a button, but puts the sensor a little bit above it, so when you are typing you accidentally open the stupid menu and hit something random, and next thing you know, you are in a video call with someone from madagascar. Trust me dude, you dont want this stupid feature on the htc one m7.

You can also just enable soft keys too instead of using the physical buttons.

There is an app somewhere that actually uses the space above the logo, but this is different then the kernel. I just used the elementalx kernel (which was my backup plan if I didn't find something better). I can't do logo2home and home2recents like I wanted to, but I don't have any problem with accidentally hitting the logo button instead of space. I guess this could be because I usually swipe to type, but I'm testing it now and I have to be off the screen before it hits the button (though just barely). Overall I'd say definitely worth it for me.
Sent from my HTC One using Tapatalk

fireball0093 said:
You can also just enable soft keys too instead of using the physical buttons.
Click to expand...
Click to collapse
Yeah, but if there's already a space for the button...
Sent from my HTC One using Tapatalk