So I've seen the kernels that will allow you to make the HTC logo act as a capacitive menu button. Has anyone looked into completely remapping all the buttons?
I'd like to see the HTC logo be the home button and the current home button turned into the menu button.
Would that be possible? Inquiring minds want to know.
I still haven't switched to Nova Launcher, I'm happy with sense atm, but when it auto downloaded on initial setup, the HTC logo brought up the home selector.. Seems like nova will let you customize use.
elrey75 said:
I still haven't switched to Nova Launcher, I'm happy with sense atm, but when it auto downloaded on initial setup, the HTC logo brought up the home selector.. Seems like nova will let you customize use.
Click to expand...
Click to collapse
I'm running Nova. I don't recall seeing that during the set up. There are a lot of settings to change the CURRENT Home button into whatever you'd like it to be but nothing on mapping the "HTC Button".
cdaniel76 said:
So I've seen the kernels that will allow you to make the HTC logo act as a capacitive menu button. Has anyone looked into completely remapping all the buttons?
I'd like to see the HTC logo be the home button and the current home button turned into the menu button.
Would that be possible? Inquiring minds want to know.
Click to expand...
Click to collapse
I think that would definitely be possible. I'd suggest posting in the kernel thread to see if this is something the dev would look into
Related
Ok so i've got a rooted Nexus One... had it for about a week... messin around with some roms and I like Cyanogen. But while trying out the Desire port I noticed when you use the trackball to move between home screens pretty easily. Is there anyway I could do that with Cyanogen?
Yeah I really love this in Sense roms too, but the simple answer is no.
Android 1.6 has the "AdvancedLauncher" replacement that can hide the titles on home screen shortcuts and make them essentially invisible to trackball selection. This way, there is nothing for the trackball to highlight and it just jumps whole screens. I have not seen that on 2.x yet.
HelixLauncher has the option to hide text label now but it still allows the trackball to highlight icons, and this prevents the jump from screen to screen.
So far, you can only have this feature on a Sense UI rom. Personally, I'm rocking the Desire rom!
I am on Cy 5.0.6 and I can use the trackball to navigate through all my home screen pages
Hold down on the app drawer button. Flash cards will pop up, you can use trackball from there.
Hold down on the app drawer button. Flash cards will pop up, you can use trackball from there.
Click to expand...
Click to collapse
Oh dang I didn't even remember that! I'm not fully proficient with the new UI yet, I haven't had my Nexus too long. So that's another alternative.
I, however, prefer not to have any orange highlights on anything on the home screen at all. This is why I like the Sense way of doing it.
liam.lah said:
Hold down on the app drawer button. Flash cards will pop up, you can use trackball from there.
Click to expand...
Click to collapse
After doing all that I might as well just use my finger and flip normally between screens lol
I was just hoping there might be an app or something that I could just scroll left or right without worrying about going from icon1-to-icon2-to-icon3-to-icon4 THEN to the next screen and doing it all over again.
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
Today I bought the HTC One with the surprise that it doesn't have a dedicated menu button. I am guessing that sometime in the future this will get remedied somehow, but in the meantime is there a workaround for this?
For example, on my previous HTC Desire phone, I was using Launcher8 as my main launcher however to edit its settings I'd need to press the menu button and then press settings.
Without a dedicated menu button, I can't find anyway to change its settings. So is there any way to get around this? or will I need to root my phone and install a new ROM for this? (which I don't want to do at the moment in case I void my warranty).
look for three dots in a line going downward on the screen, press that for the menu, there is no dedicated hard menu button
John.
Tinderbox (UK) said:
look for three dots in a line going downward on the screen, press that for the menu, there is no dedicated hard menu button
John.
Click to expand...
Click to collapse
Yeah I saw the menu icon in some apps, but I tried it on Launcher8 and the only way to access the settings was from the homescreen itself. There are no menu icons to press to get the settings as far as I am seeing.
EDIT: Actually, nevermind. I found that I can make an icon for it.
This will be fixed when HTC finally delivers 4.2.2. The leaked versions let you assign holding down the home button for settings. They should have done it like this in the first place. The 3 dots thing looks hideous.
Hi. I'm having this problem that my home screen button doesn't work like it should. I use 5 panes and one of them is marked as a "home screen" when I'm not I my home screen pane I should be able to quick access to my home page by just hitting the home button. This is how my friends Z1 works and all my previous Android devices for that matter. But for some strange reason my home button doesn't do anything in to home screen or in any other pane. When I hit the home button the screen flashes quickly like it's trying to do something but nothing happens. Otherwise the home button works just like it should long press activated Google now and in other programmes it brings me back to the home screen. So the problem is somewhere in stock launcher.
Has anyone else noticed this and what might be the reason?
Kohozga said:
Hi. I'm having this problem that my home screen button doesn't work like it should. I use 5 panes and one of them is marked as a "home screen" when I'm not I my home screen pane I should be able to quick access to my home page by just hitting the home button. This is how my friends Z1 works and all my previous Android devices for that matter. But for some strange reason my home button doesn't do anything in to home screen or in any other pane. When I hit the home button the screen flashes quickly like it's trying to do something but nothing happens. Otherwise the home button works just like it should long press activated Google now and in other programmes it brings me back to the home screen. So the problem is somewhere in stock launcher.
Has anyone else noticed this and what might be the reason?
Click to expand...
Click to collapse
Try a different launcher like the excellent kit kat one from the Nex 5, it's been rock solid for me, but that issue you describe does sound weird, maybe a reflash of the rom you're using might do the trick.
Obviously reboot your phone often too, just incase you hadn't.
Problem solved.
I did install / uninstall of another launcher and after that the xperia launcher works like it should.
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