Related
Wow. Just noticed something really odd with the keyboard/screen, but then it could be my phone!
If put your phone on a flat surface (ie table) - try type some letters on the right/left/bottom edge - i find it not as responsive as if you typed in the middle part of the screen. But if you hold the phone in your hands, its perfectly fine!
Anyone else getting that weird problem?
Yep
Noticed the problem to.
I'm guessing there is some screen sensitivity changes when it knows its flat on a surface.
I guess its another on the list of things to fix when the release a new build (or some devs release soem cooked ROMs).
I wonder if this is related to the capacitive nature of the touchscreen? I can replicate the effect if the phone is flat on the surface and I'm only touching it with my typing finger. However, if I rest another finger on the device, or hold it lightly by the edges (still sitting flat on the surface) it works fine.
If this is the case, I doubt any rom will be able to fix it since it is likely to be the capacitive touch screen technology and not a software "fault" per se.
Regards,
Dave
I have seen this too. I wondered if it was a perspective thing - are you pressing the right part of the screen?
are you pressing the right part of the screen?
Click to expand...
Click to collapse
Oh yeah, looks like I am pressing the right part. It just have to be more firmer pressing those edge buttons. It doesn't matter which way the keyboard layout is.
Anyway, thanks to everyone confirming that you got the same problem. I would have thought it was hardware related, but it could be software related I suppose. Perhaps whatever software is trying to rotate the keyboard is having a hard time to work out what direction to show the keyboard is causing that weird problem
Try holding the phone between thumb and forefinger whilst it is on a flat surface and then typing. If I do this, I have no issues, but the second I remove my fingers, I then get the lack of response for the keys on the bottom row of the device.
Regards,
Dave
mines the same may be to avoid key presses in your pocket?
I have the same problem too. It isn't a problem with all capacitive screens as the iphone never used to do this (l know, I know)
So far I've found no solution, let's hope it gets a quick fix
wow, and I thought it was only me, when I put the phone on the desk, and try use my fingers it becomes really unresponsive but when I'v got it in my hand and I'm using my thumb its all fine, hmmm really weird
it's not really a fault, but more of the nature of the capacitive screen and/or software. In comparison with the iPhone, the iPhone's capacitive screen lets you type/navigate with the phone lying on a flat surface. I find that the Hero's screen requires you to apply a tiny bit more pressure and more surface-area of your finger/thumb, for it to respond. I hope HTC somehow tweak the software for this to be more responsive with less pressure/surface-area contact required so it is usable on a flat surface - don't always want to be picking my phone up to use it at work.
i confrim, using hero without touch the metal edge result in less responsivity and difficult on multitouch operation
hope new firmware can solve this, too many errors using it like a normal keyboard on a table!
Noticed the same problem when using the Hero in my In Car Holder. Makes data input into CoPilot very difficult indeed.
A couple of observations...
I actually have mine in one of those Silicon Covers - the new style 'Gel' ones (work really well and looks good too, unlike old Silicon ones). So it's not actually about having contact with metal as such.
Problem does not occure when plugged into USB.
Now this bit could just be perception rather than reality, but I tried typing while flat (USB disconnected) when touching the coated surface around the trackball and it did not seem to improve things. Trying to do the same while touching the metal area around the speaker grill did seem to improve things. You guys observing similar ?
Anyway, I'm hoping that when I have my car charger, it will fix my CoPilot problem since this should be the same as having the USB plugged in.
Zuber
Hey all, I searched, but couldn't find anything on this.
I'm here in Canada. This is my first Android phone/Touchscreen phone. So i'm not sure if the issue is just my lack of experience or if there is a legit issue.
(btw I ordered my sgs2 from handtec, and got it with no issues.)
Issue:
Dead screen sensor?
Symptoms: (see below picture for example)
My issue is when I am in portrait mode (with the samsung branding at the top), swyping words that start with
A,S,Z (and to some extent W,E,D) letters it "hiccups"? for lack of a better description and registers that i hit/touched both S and Z instead of just S.
When I'm in landscape mode (with samsung to the left) It appears to be the K and M letters. which correspond to the areas of S,D,Z,X from portrait mode....
Question:
Does this happen to anyone else? Is this me? or the screen? or what?
I love swyping, but this just ruins the experience as i can't seem to ever get it to accept what i'm typing/swyping with any word starting with aszd
as an addendum, I can replicate it practically all the time.
It almost seems as if the screen stops recognizing the swype/finger, then has to start again and so then re-registers a starting point, and then the prediction is wrong because of the sudden stop/start.
After looking at the problem a bit more, and using one of the test codes to test the screen, I found that swyping slowing from right to left near the problem area reveals a spot where the line deviates from my swype path.
Possible that I have a bad screen with a dead sensor area?
Here is a picture of what i mean: my finger line never changes - ie: it's straight. note the line that results though!!
Second picture:
I've taken a screen cap on the test page to show you what i mean. I think there is a dead sensor space and the line jumps to the next nearest sensor. It is very annoying, and makes text-tapping, or swyping, very very difficult.
see picture. In this picture i am swyping my finger from right to left. The lines seem to be straight in some areas north/south of the problem area, but when the line meets the problem area, it swerves. above or below.
Sigh, nobody?
Sent from my GT-I9100 using XDA Premium App
Just as an update, if anybody else is/was having this issue: Turns out the screen had a dead spot on the sensors. Had to ship phone back to Handtec (at my cost which sux) for a replacement. Still waiting for replacement.
is there a way to calibrate the accelerometer, it is way too sensitive, sometimes when im holding the phone on my palm to read email/text/webpage it auto rotates because i tilted it a TINY little bit.
i downloaded the app gps status, it has this crosshair thing to see which way you are pointing the phone towards, and it should be dead center if it is laid flat on a flat surface, but its shifted towards bottom left a bit.
i'm wondering if anybody has this problem also.
Maybe your flat surface isn't entirely level.
Hi my problem is strange. After a fall mi phone HTC GRATIA is similar HTC Aria have a problem during the call. Sometimes the display became black similar a stand by and not answer to the all impulse. If i want stop the call i have to do remove the battery.....
Have you any help for me ?
thank you
I've got a similar problem. I've replaced my digitizer and done everything by the instructions I've found. However the proximity sensor doesn't work and disable the screen when calls are answered.
I've got the rubber gasket on the light sensor, didn't lost it, and the light sensor works OK. I've tried prying very gently in between the digitizer and the housing, and while I do that sometimes the proximity sensor will show a value of 3.5in, and not 0 as always. I'm using AndroSensor.
I don't mind disassembling the phone again, but I don't know what I need to fix it.
I've searched all the forum posts about it, but either people disabled it somehow, and others just say they fix it but didn't mention how.
Any help on this?
CaptainMaki said:
I've got a similar problem. I've replaced my digitizer and done everything by the instructions I've found. However the proximity sensor doesn't work and disable the screen when calls are answered.
I've got the rubber gasket on the light sensor, didn't lost it, and the light sensor works OK. I've tried prying very gently in between the digitizer and the housing, and while I do that sometimes the proximity sensor will show a value of 3.5in, and not 0 as always. I'm using AndroSensor.
I don't mind disassembling the phone again, but I don't know what I need to fix it.
I've searched all the forum posts about it, but either people disabled it somehow, and others just say they fix it but didn't mention how.
Any help on this?
Click to expand...
Click to collapse
You need to get the light sensor, gasket, and the small window in the digitizer all lined up perfectly so that the light sensor is not being blocked by anything. Not as easy as it sounds.
thanks for the explanation, but is the best way to do this?
and why the light sensor shouldn't be blocked? it seems by AndroSensor that it works fine, the problem is with the proximity sensor.
These phones where manufactured by the thousands per day in some factory, there sure is a way to assemble them precisely somehow.
CaptainMaki said:
why the light sensor shouldn't be blocked?
Click to expand...
Click to collapse
If it is blocked, then it will not be able to sense anything (It's like you (the light sensor in this case) are trying to through a wall (whatever's blocking it)).
CaptainMaki said:
These phones where manufactured by the thousands per day in some factory, there sure is a way to assemble them precisely somehow.
Click to expand...
Click to collapse
Special machines used to place them accurately.
I meant that the light sensor is "blocked" by the rubber gasket and seems to works fine.
by the way, as far as I know, most electronics are assembled by hand. laptops, iphones and ipads are, so I don't think that Aria is any different.
If anyone has any tips on how to do this, since I'm sure I someone has managed to replace the digitizer on this phone? how do they do this in repair shops or AT&T store?
CaptainMaki said:
I meant that the light sensor is "blocked" by the rubber gasket and seems to works fine.
by the way, as far as I know, most electronics are assembled by hand. laptops, iphones and ipads are, so I don't think that Aria is any different.
If anyone has any tips on how to do this, since I'm sure I someone has managed to replace the digitizer on this phone? how do they do this in repair shops or AT&T store?
Click to expand...
Click to collapse
The ambient light sensor and the proximity sensor are two separate things, though they are right next to each other on the Aria. The proximity sensor is MUCH more sensitive to being precisely aligned.
I incorrectly used the term "light sensor" in my earlier post. The proximity sensor, NOT the ambient light sensor, is responsible for turning the screen off during calls.
drumist said:
I incorrectly used the term "light sensor" in my earlier post. The proximity sensor, NOT the ambient light sensor
Click to expand...
Click to collapse
That's what I assumed you were talking about.
As I've said the proximity sensor is the right sensor and the ambient light is the left sensor that is covered with the rubber gasket.
The light sensor works perfectly as I've said. In AndroSensor at least it jumps between 33 LUX when covered and 77 LUX and 220 LUX when placed directly under a desk lamp.
But the proximity sensor doesn't seem to respond at all. What perfectly aligned means, that the sensor is right below the "hole" in the digitizer plastic? if I place the digitizer and it falls into the place, how come it isn't aligned? it's not like the digitizer has where to move in the frame.
CaptainMaki said:
The light sensor works perfectly as I've said. In AndroSensor at least it jumps between 33 LUX when covered and 77 LUX and 220 LUX when placed directly under a desk lamp.
Click to expand...
Click to collapse
I have two Arias and they both max out at 698 lux. If you can't get it to go above 220, it might be partially obstructed.
But the proximity sensor doesn't seem to respond at all. What perfectly aligned means, that the sensor is right below the "hole" in the digitizer plastic? if I place the digitizer and it falls into the place, how come it isn't aligned? it's not like the digitizer has where to move in the frame.
Click to expand...
Click to collapse
Do you notice a gap between the LCD and digitizer that is larger than it was from the factory? I wonder if it might just be related to the digitizer sitting too far from the proximity sensor. If you press down on the top right corner of the digitizer while in a call (without covering the sensor itself), will the screen turn back on?
Possibly unrelated, but similar.
I have an identical issue with the DroidX.
It needs a "gasket" over its proximity "light source" to keep light from reaching the proximity light sensor when there is nothing in front to reflect it back.
Looks like the light source had a rubber hood over it with a pinhole directed straight out, away from the sensor adjacent to it. Thus keeping stray light from triggering the sensor.
AAARGH. To have that little rubber piece.
Erbid
after replacing another screen and this time I've done it right, this is what I've learned.
I've assembled the phone with androsensor turned on and tested the sensors all the time. It seems that they should be perfectly clean (some air spray will do just fine), perfectly aligned with the holes in the digitizer and don't have to much distance between the digitizer and the sensors.
It's seems like a hassle but actually it's not, since if you put the right tape and put the keep it all clean, it can work with no problems at all. Make sure you test everything before you close the phone completely.
Hey Guys,
First time Razr Maxx user here, after all of your input i've made the jump, thanks guys
I want to contribute a simple fix to you all, I've read that some people have their compass sensor stuck on one direction continuously, no calibration can solve it. I myself had this problem today, but it turns out it is fixable easily.
The cause:
The Phone (especially on the top right, right after the front cam part, where the sensor is located) gets too close with a magnetic object for a long period of time
The Tools needed:
Phone Tester app on Google Play Store
Small Fridge Magnet (Magnet doesn't have to be powerful, at least it will stick to fridge door or your PC case)
The steps:
Install and Open Phone Tester app, go to Sensor menu,
you'll find one of the axis is stuck at one value, mine was stuck at Axis X value at 1159.1 uT
Place the phone lying on the table, screen is upside
Place the magnet around the top right part of the phone (it is Maxx version but CMIIW on the standard one), right after the front camera part. You should see the stuck sensor axis fluctuates.
After 2-3 seconds, Remove the magnet, review the axis value again with moving around the phone.
Repeat step 4-5 until the axis value fluctuates continuously with your phone movement.
You're done
If the problem persists, please consult to the dealer, but the above fix was 100% successful for me so you should try it. Below is the attachment to describe which part should be attached with magnet for a while. Hope it helps
G'day!
Thank you, thank you very much.
It works.
Sent from my XT910 using xda app-developers app
In my case, most probably I got the 'stucked compass' syndrome, when I put the phone and earphones in my shirt's pocket. Since the earphones also have magnets, it may magnetized the metal in the phone's component, and affected the compass.
Actually I am almost going to send it to the Motorola service center for the repair, but, not need to. Thanks for the tip.
Thank you.
bahathir said:
In my case, most probably I got the 'stucked compass' syndrome, when I put the phone and earphones in my shirt's pocket. Since the earphones also have magnets, it may magnetized the metal in the phone's component, and affected the compass.
Actually I am almost going to send it to the Motorola service center for the repair, but, not need to. Thanks for the tip.
Thank you.
Click to expand...
Click to collapse
Nice to know it works well for you mate
Confirmed! This works. In my case it's undoubtedly caused by the magnetic lock of the pouch. You saved mi peace of mind, I was starting to think my Razr was defective. Thank you! (button pressed)
Excellent, it worked!
hansip87 said:
Hey Guys,
First time Razr Maxx user here, after all of your input i've made the jump, thanks guys
I want to contribute a simple fix to you all, I've read that some people have their compass sensor stuck on one direction continuously, no calibration can solve it. I myself had this problem today, but it turns out it is fixable easily.
The cause:
The Phone (especially on the top right, right after the front cam part, where the sensor is located) gets too close with a magnetic object for a long period of time
The Tools needed:
Phone Tester app on Google Play Store
Small Fridge Magnet (Magnet doesn't have to be powerful, at least it will stick to fridge door or your PC case)
The steps:
Install and Open Phone Tester app, go to Sensor menu,
you'll find one of the axis is stuck at one value, mine was stuck at Axis X value at 1159.1 uT
Place the phone lying on the table, screen is upside
Place the magnet around the top right part of the phone (it is Maxx version but CMIIW on the standard one), right after the front camera part. You should see the stuck sensor axis fluctuates.
After 2-3 seconds, Remove the magnet, review the axis value again with moving around the phone.
Repeat step 4-5 until the axis value fluctuates continuously with your phone movement.
You're done
If the problem persists, please consult to the dealer, but the above fix was 100% successful for me so you should try it. Below is the attachment to describe which part should be attached with magnet for a while. Hope it helps
G'day!
Click to expand...
Click to collapse
Thanks so much for this, I thought my compass had crapped out and now it's working perfectly.
Thanks!
Beautiful!! Easy solution that worked on both my wife's and my phones. Both were stuck and both now work. I have a geocaching app and we each have Google Sky Map, neither of which were working properly-until we used this extremely simple fix. One suggestion that I remember from my days in radio; rather than just set the magnet on the phone, move it around in circles for a few seconds as we used to do to degauze tapes for reuse.
Not certain but this didn't seem to work until I got the magnet to around the center right side of my RAZR (non Maxx) near the volume rocker. That seemed to unstick it!
:good: