I am having a problem with the space not being responsive when using the phone in landscape mode it is fine in portrait. i have tried calibrating and also with different software and its always the same the space bar just refuses to respond 80% of the time. is there anyway of fixing this as i like the rom as its lightning quick but have had to revert to stock as this is a major issue for me. I have googled but found nothing of interest. I have tried the 2 latest stable builds and the latest rc and its the same in all builds. is there a version of cynogen where this iosnt an issue?
Flip the phone to the right instead of the left.
Sent from my LT15i using xda premium
thats not how i use the phone im not left handed and need the buttons on the right so using the phone upside down isnt really a fix. is this prevalent in all versions?
The keyboard stay the same, no matter which way the phone is held. The only difference is the camera and volume buttons are on the bottom.
There are already heaps of threads/questions about this.
WebbyHRT said:
The keyboard stay the same, no matter which way the phone is held. The only difference is the camera and volume buttons are on the bottom.
There are already heaps of threads/questions about this.
Click to expand...
Click to collapse
the buttons would then be on the left and not the right ie the screen would have to be upside down for the keyboard to respond correctly Im to use to flipping the screen the way i do and also used to the buttons being on the right. is there no fix for this?
Related
samsung jack i637 on landscape mode and if you want to know how to get this to work on your phone replied to this thread.
How did you do that? can you change the arrow keys to, so Up is left, down is right, etc?
thanks
yes i can do all of that
great, how?
its a app i made
that im still working on because some themes you use on your phone will somtimes not look right but the rst is fine just fixing that part
I haven't been able to get my hardware camera button to work on the G2. I press the button and makes a beeping sound and I see the green square on the screen but the picture is never taken. I can keep holding it down for 10 seconds after the beep and no shot is taken. I am pressing the button so hard it is about to break. Any ideas? Thanks
mine works fine, so I'm not much help on the hardware button... but you can always use the on-screen button in the lower left corner in the camera app.
Thanks, that is what I have been using, but I don't like the idea of it not working. I called Tmobile and they said I can return it for a new one. They guy was telling me to swap it for a Mytouch 4g but not sure I want to do that, even though I find myself using Swype 90% of the time.
I still have the problem. I got mine a week ago. Has anyone found a solution to this problem? Could it be hardware or software?
rooted DZ w/ CM7
have u tried tweaking the settings....ex..button settings (in main settings) or shutter and delay settings in camera
I actually got it to work somehow.. I don't know how though. But still I'm curious on how it works.
Sent from my HTC Vision using XDA App
the htc desire Z hardware camera button is a two touch button.
as is, press it once <halfway in> - it focuses and u get the green square on the screen.
press it harder in <all the way down> - it takes the picture.
i myself thought my button was faulty until i did some google searching. cant remember where i read this. but hope it explains it better.
Just been noticing that I usually have to press the capacitave buttons a few times to get it to recognize.... anyone else notice this. On my EVO if I press home or menu or back it recognized it right away, on the ET4G it seems to not recognize touch very well, but only on those soft buttons, everywhere else on the screen is great...
Mine work good, a hell of a lot better than my Epics. I'd say mine are a little less sensitive than the Evo 4G's and the Shift though.
luigic81 said:
Just been noticing that I usually have to press the capacitave buttons a few times to get it to recognize.... anyone else notice this. On my EVO if I press home or menu or back it recognized it right away, on the ET4G it seems to not recognize touch very well, but only on those soft buttons, everywhere else on the screen is great...
Click to expand...
Click to collapse
I think these have a smaller area for the button than the EVO did because I was experiencing the same thing but then noticed I wasn't pressing low enough. Now that I'm getting more used to the layout it seems like I'm getting a response from the buttons every time.
datajosh said:
I think these have a smaller area for the button than the EVO did because I was experiencing the same thing but then noticed I wasn't pressing low enough. Now that I'm getting more used to the layout it seems like I'm getting a response from the buttons every time.
Click to expand...
Click to collapse
thanks I will try this
datajosh said:
I think these have a smaller area for the button than the EVO did because I was experiencing the same thing but then noticed I wasn't pressing low enough. Now that I'm getting more used to the layout it seems like I'm getting a response from the buttons every time.
Click to expand...
Click to collapse
just tried this, works perfect, basically just press as low as possible and they are money
never would have thought of that, thanks !!!!
luigic81 said:
just tried this, works perfect, basically just press as low as possible and they are money
never would have thought of that, thanks !!!!
Click to expand...
Click to collapse
Makes you wonder... Were they designed that way, for some odd reason, or was the form off, and nobody bothered to QC the mass production version?
I've had the phone for two days now and this has happened 3 times now.
The worst one was I got a phone call but the keyboard was up and the back button wasn't there to get rid of it. So I couldn't answer the phone.
One time I couldn't exit the settings menu because the buttons disappeared.
To remedy I turn off the display, turn it back on and unlock to the camera. I think because the camera has the special hidden buttons it causes the phone to refresh the button display otherwise I couldn't find another way to do it.
Has this happened to others? I haven't seen threads about it.
Sent from my Galaxy Nexus using XDA App
I lost them once but got them back by turning the phone sideways and then back upright once the buttons reappeared.
Sent from my Galaxy Nexus using Tapatalk
Oh wow, yea, that would probably work too. But some apps lock to portrait (dialer).
Sent from my Galaxy Nexus using XDA App
Happened to me while I was playing a game (Reckless Gateway) and received a call at the same time. After the call, soft buttons wouldn't appear anymore, had to restart my phone
I have only lost the buttons when flashing a mod that was not compatible...in that situation I did not have the virtual buttons or the notification bar at all.
Never happened to me on stock or rom. What build/android is your phone? You can find info in settings>about phone
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
This has happened to me a couple times while using Google Nav. I just pulled down the notification bar and hit the settings button - that seemed to bring the buttons back. Strange issue.
Just a few kinks that need ironing out.. hopefully Google is aware of minor bugs like this already
ericc191 said:
Just a few kinks that need ironing out.. hopefully Google is aware of minor bugs like this already
Click to expand...
Click to collapse
Yep, exactly. Though I wouldn't call this minor because it made me miss a call.
Another thing I just noticed. Go into an app that has the menu virtual button (the three dots) then turn off the screen. Turn it back on and the menu button will be the only virtual button on the Lock Screen. You can press it and automatically unlock the phone. I'm using slide to unlock and the news and weather app to do this every time.
Edit: Just tried with a different lock (pattern) and the menu button will not unlock. But it is still there and you can press it. It just does nothing. Weird.
Hiya! A friend of mine has a Sony Xperia S which the "c" key doesn't work when in portrait mode, an "x" or a "v" is registered instead. When rotating the screen to landscape mode it works fine.
I thought it could be software related so I installed the latest Swiftkey to his phone and the key kept not registering anything.
The next thing I thought is that that zone of the screen was somewhat broken or the calibration was off... so I detached Swiftkey and moved it to the top of the screen... and the same thing happened! The "c" key doesn't work in portrait mode regardless of the keyboard and the position of it on the screen. Isn't that weird?
Do you have any idea of what could be the issue here?
Deses said:
Hiya! A friend of mine has a Sony Xperia S which the "c" key doesn't work when in portrait mode, an "x" or a "v" is registered instead. When rotating the screen to landscape mode it works fine.
I thought it could be software related so I installed the latest Swiftkey to his phone and the key kept not registering anything.
The next thing I thought is that that zone of the screen was somewhat broken or the calibration was off... so I detached Swiftkey and moved it to the top of the screen... and the same thing happened! The "c" key doesn't work in portrait mode regardless of the keyboard and the position of it on the screen. Isn't that weird?
Do you have any idea of what could be the issue here?
Click to expand...
Click to collapse
What android version or rom?
darknessmc said:
What android version or rom?
Click to expand...
Click to collapse
Sony's stock version and latest OneOfaKind.
We figured out that it is a hardware problem, and after switching him to Swiftkey having some broken letters is bearable until the phone dies completely.
Deses said:
Sony's stock version and latest OneOfaKind.
We figured out that it is a hardware problem, and after switching him to Swiftkey having some broken letters is bearable until the phone dies completely.
Click to expand...
Click to collapse
Sorry for that but this problem in lollipop only. I have it in my device. When I back to JB it's work perfectly and works on marshmallow too.