I'm using CM 4.0.2 wiith htc _ime keyboard. I'm having 3 issues with the physical keyboard. BTW no issues until I started using CM roms, so odds are tiny that it is a hardware issue.
1: My right side alt and shift keys do not function. When pressed they create the little carrot marker under the cursor, but they do not cause the desired effect, the regular letter is displayed as if the alt/shift button was not pressed. Left side works fine.
2: This is somewhat sporadic, but when I double press the space bar I do not always get a . At the end of the sentance, sometimes there is a space before it. i.e. Hi . I am fine .
3: I still get the autocorrect for the physical keyboard sometimes. I thought Cyanogen fixed that, am I mistaken?
It's most likely a hardware issue, it was probably just a coincidence when you flashed.
If you think its Firmware related, try reflashing to see if it cures the issue.
Gilliland12 said:
I'm using CM 4.0.2 wiith htc _ime keyboard. I'm having 3 issues with the physical keyboard. BTW no issues until I started using CM roms, so odds are tiny that it is a hardware issue.
1: My right side alt and shift keys do not function. When pressed they create the little carrot marker under the cursor, but they do not cause the desired effect, the regular letter is displayed as if the alt/shift button was not pressed. Left side works fine.
2: This is somewhat sporadic, but when I double press the space bar I do not always get a . At the end of the sentance, sometimes there is a space before it. i.e. Hi . I am fine .
3: I still get the autocorrect for the physical keyboard sometimes. I thought Cyanogen fixed that, am I mistaken?
Click to expand...
Click to collapse
I, too, have also noticed all of these things occurring in 4.0.2 using the htc_ime keyboard, i think for the last one he reverted the fix back because the vk kept popping up even when using the pk.
Related
Is there a spot on THE RIGHT SIDE your Xperia X1's SPACEBAR where when you press down, YOU GET TACTILE FEEDBACK, but the press is NOT registered?
Thank you for any input.
Not on mines.
yea i do...
it gets annoying now...had to press it hard now
mr_sheen said:
yea i do...
it gets annoying now...had to press it hard now
Click to expand...
Click to collapse
I have to GO BEYOND pressing and feeling the tactile feedback because the press isn't registered even with the click. This is a very frustrating experience, you just can't type with "faith", even with the click, you still have to be sure the "space" appears, or you have to backspace/left to insert a spacebar. It is highly irritating.
It is also the right side, which I use because I somehow seem to use the left alphabets more than the right alphabets when typing anything, so I have more freetime with the right thumb. And it is exactly the right side that is unresponsive.
Hey yogi, good for you.
I realised there was already another thread describing similar issues.
The thing is, my X1 is in the service center's custody at the moment for repair and they said that it is normal for the keyboard to be like this. I am really wondering if I should push for a keyboard replacement.
It is sad that Xperia as a device boasting a nice keyboard having wear and tear at such a pace.
Design
I don't think it's wear and tear. Mine has had this problem since day one, it's just to do with where on the key the actual "button" that registers the press is, and since the key is "bendy" it wont register in every place you press it.
Strangely, as one person said, they use their right thumb more, I being left handed tend to use my left thumb much more, infact I dont use my right thumb at all when touch typing on my desktop keyboard, BUT I find that I use my right thumb a lot more for the space bar on the xperia.
alias_neo said:
I don't think it's wear and tear. Mine has had this problem since day one, it's just to do with where on the key the actual "button" that registers the press is, and since the key is "bendy" it wont register in every place you press it.
Strangely, as one person said, they use their right thumb more, I being left handed tend to use my left thumb much more, infact I dont use my right thumb at all when touch typing on my desktop keyboard, BUT I find that I use my right thumb a lot more for the space bar on the xperia.
Click to expand...
Click to collapse
right now im practicing to start hitting that spacebar with my left thumb. It feels weird though...
Whenever im typing fast, about 5 times out of 10 the spacebar will not register. Bloody annoying...
Im thinking about taking it back for a repair...do you guys think it will worth the time?
mr_sheen said:
right now im practicing to start hitting that spacebar with my left thumb. It feels weird though...
Whenever im typing fast, about 5 times out of 10 the spacebar will not register. Bloody annoying...
Im thinking about taking it back for a repair...do you guys think it will worth the time?
Click to expand...
Click to collapse
My hands are pretty big and I have just noticed that because it causes me to type so slow I can infact type space just as easily with either thumb, or infact both at once.
My main concern is my thumb nails catching hte chrome at the top when i use the top row and I am just hopeful I dont "chip" it off.
Personally I don't think repair will help, it just seems to be a design flaw in the space bar, best solution might be to find if you can perform a mod on it yourself to make it more responsive, but that's if you're up for that kind of disassembly/work on such an expensive device.
okay, seems i've found the solution for the problem.
On spacebar, u've got to hit almost the right end part. If u hit it between the middle and right part, most likely it wont register.
I've had problem with the (ok) and the (.) key too. for this one you just have to press it slightly harder.
Ok.
I found also, that if you press arund 1/3 of the way along the space bar it makes a double click instead of a single one, this is the point at which it either doesn't register or it registers 2 spaces. As long as you try to avoid this section you should be ok.
gee...
Its all a bit too much for something that we put quite bit of money into hey
yes... i even get doubles or triples sometimes.. crazy keyboard imho
I have started to have this problem since last month and have reported it on another thread.
http://forum.xda-developers.com/showthread.php?t=483644
It also started with the space bar, on the right side. I then practice in hitting the spacebar using my left thumb (instead of my right thumb) and it's OK for a while, until the problem affected spacebar on both the left and the right side.
Then it started to affect other keys as well, such as the Fn (blue) C, V, N and dot (.) keys, among others. The interesting thing is that the problem seems to be only affecting the keys on the lower part of the keyboard, and not the upper part one.
Basically similar symptoms: the key is not responsive and doesn't register the key we have pressed even though we get tactile feedback from the key. And sometimes, if we press harder, it will register double of the keys, sometimes triple. Really annoying and irritating.
Is it worth bringing the phone to the service centre? Do you think they will be able to resolve this problem, since it seems to be a design flaw to me.
Any feedback is highly appreciated.
Thanks.
indrapr said:
I have started to have this problem since last month and have reported it on another thread.
http://forum.xda-developers.com/showthread.php?t=483644
It also started with the space bar, on the right side. I then practice in hitting the spacebar using my left thumb (instead of my right thumb) and it's OK for a while, until the problem affected spacebar on both the left and the right side.
Then it started to affect other keys as well, such as the Fn (blue) C, V, N and dot (.) keys, among others. The interesting thing is that the problem seems to be only affecting the keys on the lower part of the keyboard, and not the upper part one.
Basically similar symptoms: the key is not responsive and doesn't register the key we have pressed even though we get tactile feedback from the key. And sometimes, if we press harder, it will register double of the keys, sometimes triple. Really annoying and irritating.
Is it worth bringing the phone to the service centre? Do you think they will be able to resolve this problem, since it seems to be a design flaw to me.
Any feedback is highly appreciated.
Thanks.
Click to expand...
Click to collapse
Yes, I have SAME problem. I think the reason is dust or some thing like that and any solution on this CRAP problem???
indrapr said:
I have started to have this problem since last month and have reported it on another thread.
http://forum.xda-developers.com/showthread.php?t=483644
It also started with the space bar, on the right side. I then practice in hitting the spacebar using my left thumb (instead of my right thumb) and it's OK for a while, until the problem affected spacebar on both the left and the right side.
Then it started to affect other keys as well, such as the Fn (blue) C, V, N and dot (.) keys, among others. The interesting thing is that the problem seems to be only affecting the keys on the lower part of the keyboard, and not the upper part one.
Basically similar symptoms: the key is not responsive and doesn't register the key we have pressed even though we get tactile feedback from the key. And sometimes, if we press harder, it will register double of the keys, sometimes triple. Really annoying and irritating.
Is it worth bringing the phone to the service centre? Do you think they will be able to resolve this problem, since it seems to be a design flaw to me.
Any feedback is highly appreciated.
Thanks.
Click to expand...
Click to collapse
well that is quite concerning. So it DOES gets WORSE over time
I'll try to speak with the guys down at the sony ericsson centre about this. Hopefully they have something to say
Yes, it does get worse over time. Over time, more keys will be affected by this.
mr_sheen, appreciate if you can share with us later what is the outcome of your discussion with the service centre guys about this.
Thanks.
latest update... indeed my keyboard is getting mroe crazy
Since more and more users are encountering this problem, I would foresee that this will become a common problem, and more users will start encountering this problem over time.
I would appreciate if the moderator can merge this thread with the other similar thread ( http://forum.xda-developers.com/showthread.php?t=483644 ) and make this thread sticky until we can find satisfactory permanent solution from Sony Ericsson to this problem.
I will also try to bring my phone to the local Sony Ericsson service centre here in Singapore this coming weekend and see what they say.
i just got back from the center and they say that it was quite NORMAL. They said that it was a normal wear and tear and isn't covered on warranty. Is that so? i haven't got time to read all the warranty thing(too lazy...LOL) and im quite disappointed by this to be honest....
I live in Indonesia by the way, half the time the technician down at the Sony Centre haven't got any clue on how to fix an X1....bloody hell...
indrapr said:
Since more and more users are encountering this problem, I would foresee that this will become a common problem, and more users will start encountering this problem over time.
I would appreciate if the moderator can merge this thread with the other similar thread ( http://forum.xda-developers.com/showthread.php?t=483644 ) and make this thread sticky until we can find satisfactory permanent solution from Sony Ericsson to this problem.
I will also try to bring my phone to the local Sony Ericsson service centre here in Singapore this coming weekend and see what they say.
Click to expand...
Click to collapse
If you do post here. Heard many negative things ant Singapore sony service centres
Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance
im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.
I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.
not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..
I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.
I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.
The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!
The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.
So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.
I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.
May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.
I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.
i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2
I recently flashed a gingerbread rom and I am supposed to have multitouch with the keyboard, but i have tried pushing two letters at the same time and it does not work. Does this feature not work on the nexus one? I also had smartkeyboard pro before and it would kind of work but would mistype sometimes. sorry if someone had already asked this but i couldn't find it. oh and i can pinch zoom in the browser though.
The digitizer in the N1 is a POS. Why do you think Google left the
2 fingers rotate out of the N1?
The 'fix' for rotate on Maps also 'works' with the keyboard.
Rusty! said:
The 'fix' for rotate on Maps also 'works' with the keyboard.
Click to expand...
Click to collapse
It does help but still the limitations is in the hardware itself.
Hence the inverted comma use.
Rusty! said:
The 'fix' for rotate on Maps also 'works' with the keyboard.
Click to expand...
Click to collapse
Seems to me that 'fix' would be worse then the problem. When trying to detect two touches that are close along an axis it really kills the accuracy. If you try holding shift and pressing a key, I wouldn't be surprised if you end up hitting the wrong key half the time.
pfmiller said:
Seems to me that 'fix' would be worse then the problem. When trying to detect two touches that are close along an axis it really kills the accuracy. If you try holding shift and pressing a key, I wouldn't be surprised if you end up hitting the wrong key half the time.
Click to expand...
Click to collapse
Yup, that's exactly what happens. I enabled multitouch on my N1 and have the gingerbread keyboard apk installed. If you press and hold shift while trying to hit any of the buttons near the shift key ..... don't bother.
I'm handy with screwdrivers - is there any way to upgrade the digitizer?
zuberio said:
I'm handy with screwdrivers - is there any way to upgrade the digitizer?
Click to expand...
Click to collapse
Now that would be a Christmas miracle If I only had a decent digitizer and maybe double the internal memory then I could go the rest of my life without even looking at another phone!
pfmiller said:
Seems to me that 'fix' would be worse then the problem. When trying to detect two touches that are close along an axis it really kills the accuracy. If you try holding shift and pressing a key, I wouldn't be surprised if you end up hitting the wrong key half the time.
Click to expand...
Click to collapse
Right, that's the issue with the digitizer, not the 'fix'. It seems that Gingerbread (and Maps 5.0, I suppose) makes an attempt to make up for the errant multitouch responses on our phone by just filtering them all out. The 'fix' removes that filter, so you get pure, unadulterated NexusOne wonky digitizer action. It works decently for gestures (rotating the map, for instance) but less so for things that require accuracy (keyboards).
zuberio said:
I'm handy with screwdrivers - is there any way to upgrade the digitizer?
Click to expand...
Click to collapse
Physically replacing the digitizer would only be half the battle. You'd still have to get the hardware interfaces to match up, and get the software drivers working. Call me crazy, but if you need precision multitouch, you'd probably be better off just getting a different phone. Samsung phones are supposed to have some pretty excellent multitouch.
I have been having problems lately with my HP touchpad on CM9. They are as follow: the touchscreen goes crazy and does all sorts of random typing and button pressing. At one point I could not use it so I webOS doctored it up and then flashed CM10. So far it fixed the issue but now my corner "back" button only works when you press it on the side closest to the middle. Some other buttons are like this or do not work completely in apps. I don't think it could be a hardware issue as I have always been careful with all of my devices. Thanks in advance!
Can you completely rule out hardware issues by testing your screen using a drawing app?
numanair said:
Can you completely rule out hardware issues by testing your screen using a drawing app?
Click to expand...
Click to collapse
I will try that now.
Update: Ok please try to work with this: In landscape look at the arrow, the width of the arrow, that entire section is not working from bottom to top. You have to almost tap on the very right edge of the back arrow. I still do not think it is hardware.
Bump, please help
I'm on CM w/android 4.2.2 and have similar screen issues... screen sometimes goes a static non-moving "fuzzy" blue... not sire if ther is any pattern to it or not, but reboot fixes it for a while.
lately I've noticed that ill get artafacts... fpr example todays google doodle viewed using stock android browser app will often produce black a d white horizontal artafacts. perhaps driver issues?
Sent from my TouchPad using xda app-developers app
going crazy
I'm struggling with the same phenomenon, have you been abe to solve it ?
in portrait mode my back, home button and recent apps does not work, I must turn the screen into landscape in order for them to work, what gives?
gt5oh said:
in portrait mode my back, home button and recent apps does not work, I must turn the screen into landscape in order for them to work, what gives?
Click to expand...
Click to collapse
You don't say what Rom you are using but it certainly works on Jcsullins latest.
Evervolv but now i am thinking its an lcd digitzer screen problem cause nothing in that area works regardless of the rom. I never dropped the device so i am not sure why just a section of the lcd screen would stop responding..
Hi,
The SPen of my n7000 is not working properly. After a few seconds "writing", it stops writing. Some seconds later it begins again. Then stops.... intermitently. It seems like there is a problem in the pressure sensitivity or something. The problem began some months ago, first failing once in a while only, then more and more frequently, to the point of not being usable today.
Funny thing is that the cursor is shown correctly, it never stops moving. The spen only stops "writing".
Ok, so I bought a new SPen. The new one writes only when I press the button (and I have to press hard). When I don't, it does not write, unless I use the pen almost parallel to the phone. Cursor is shown fine too. Still, it seems it works OK only when I keep pressing the button. But then there's other problem: the pen writes even if not touching the screen, so writing decently is impossible. Quite similarly like here: https://www.youtube.com/watch?v=viDDKGPj2FI. I took off the pen's button, but then there is no potentiometer inside (as opposed to the original spen).
Any idea how to fix this? How to tell the spen to keep the button pressed by default, or to rever behaviour? Which system file does control this?
Thanks!
L.