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.
Related
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.
I think having the trackball function as the home button would be a feature many would like to have. Any developer out there willing to take on this function?
What would be the point of the actual home button then? This seems pointless
what would be more useful is if the trackball can be programmed for stuff then we can use it to launch apps and do all sorts of things.
PhantomRampage said:
What would be the point of the actual home button then? This seems pointless
Click to expand...
Click to collapse
I have 3 things for my home button now, Quickdesk on dubbletap, recent apps on hold in, and singletap for launcher pro. for me it would be awesome to have quicker access to the recent apps, by putting the home to the trackball. and have recent apps on single click. wouldnt hurt to have the option. and it should also be available to bind the trackball click to anything u like.
I agree, or trackball to answer a call, I don't use the trackball that much.
Creating a service to run in the background wouldn't be too hard to do. The only problem is that you wouldn't be able to use your trackball to select links in the browser, for example. Good in theory, wouldn't work great in practise i don't think.
Here are the reasons why this would be a great function, and how it should go down:
The capacitive home button is not as responsive as it should be. I think we all use it A LOT, so making sure it worked perfectly everytime would be awesome. Especially when accessing "recent apps" and long pressing the home button, the capacitive button will occasionally take you home before you see your recent apps.
Double tapping can be incorporated into the home button. With the capacitive button, double tapping it has an almost 50% chance of failure. The trackball home button would fix this.
I don't know about you guys, but I usually dont use the trackball to select things on the screen. Touching it is so much easier. The trackball would be much more usefull for notifications, scrolling, and as a home button.
I agree with a previous poster, the trackball should be given to option to route to anywhere the user would like it to... Though I don't know what else there is to route to...
The ACTUAL home button can also be routed to anything the user would like. Maybe to recent apps, changing of brightness, a favorite app, an alternate launcher... ANYTHING.
This is all hypothetical of course, and as a non-dev, I actually have no clue how hard or easy this would be to create.
But what do you guys think? I know this a feature that would be really useful to me at least, and sound like some other people too.
sorry, there was a double post due to the server upgrades/issues on XDA.
Sorry to revive an ancient thread.
My N1 had a broken trackball, and in the process of replacing it i managed to kill both my home button and my seach button.
I can live without the seach, but not without the home.
Is there any progress on this topic ?
tia
John_duh said:
Sorry to revive an ancient thread.
My N1 had a broken trackball, and in the process of replacing it i managed to kill both my home button and my seach button.
I can live without the seach, but not without the home.
Is there any progress on this topic ?
tia
Click to expand...
Click to collapse
Never mind, it was a software problem caused by an incomplete flash. (wiped everything separately, but that wasn't sufficient. Returning to factory settings did the trick)
All I want is trackball to blink beautifully for me!
That's all, baby.
+1
I would also like trackball mods such as
double tap to go to an app and other tap patterns for the trackball
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,
Does anyone know if there is compatibility for the old camera app on the new One Ui? Or is it possible to port it now or in the future?
Two things make the camera a downgrade when switching to the new One UI, for me at least:
- You had a separate button for video and picture, so you were one touch away from taking either a video or a picture. I had a really nice setup where I could take a video with the volume buttons and open camera and take picture with 1 click of the Bigsby button. This proved really useful when i went horse back riding for the first time, or with gloves on when the screen is not responsive.
- More importantly: You had a dual shot mode where you could take pictures/video with both cameras at the same time. This was really useful when trying to fit more people in a picture, or even for me to be in there, and have a nice memory stored.
They also locked the Bigsby button so you can no longer disable it... again...
Search for the app on apkmirror and try installing it.
dumitrudan608 said:
Hi,
Does anyone know if there is compatibility for the old camera app on the new One Ui? Or is it possible to port it now or in the future?
Two things make the camera a downgrade when switching to the new One UI, for me at least:
- You had a separate button for video and picture, so you were one touch away from taking either a video or a picture. I had a really nice setup where I could take a video with the volume buttons and open camera and take picture with 1 click of the Bigsby button. This proved really useful when i went horse back riding for the first time, or with gloves on when the screen is not responsive.
- More importantly: You had a dual shot mode where you could take pictures/video with both cameras at the same time. This was really useful when trying to fit more people in a picture, or even for me to be in there, and have a nice memory stored.
They also locked the Bigsby button so you can no longer disable it... again...
Click to expand...
Click to collapse
I agree with you. I would also like the previous functionality of having both the camera and video buttons on the same screen again.
As far as the Bixby button goes, you can use BxActions to disable and remap the button. It works pretty well.
Max_Terrible said:
I agree with you. I would also like the previous functionality of having both the camera and video buttons on the same screen again.
As far as the Bixby button goes, you can use BxActions to disable and remap the button. It works pretty well.
Click to expand...
Click to collapse
I do use BxActions,but how do you prevent Bigsby from appearing when you press it? You used to have to disable it from the Bigsby app, and yo no longer have that option.
dumitrudan608 said:
I do use BxActions,but how do you prevent Bigsby from appearing when you press it? You used to have to disable it from the Bigsby app, and yo no longer have that option.
Click to expand...
Click to collapse
I disabled my single press function. I only have a long-press function for my flashlight. Bixby doesn't show up for me when I single-, double-, or long-press the button. Occasionally it'll show the icon at the top and it did open Bixby once, but I couldn't figure out under which circumstance that was and I couldn't replicate it again since. Bottom line, Bixby doesn't show up for me when I press the button.