Hero Screen Anomaly:
I found this out purely by chance. The sensitivity of the screen on the HTC Hero severely decreases when the phone is laid on a flat surface,with normal G-Sensor calibration.
However, if you place the phone upright and calibrate the G-Sensor such that the phone "thinks" it's on a flat surface, the screen sensitivity becomes normal when the phone is again laid on a flat surface. Has anyone else experienced this? Is this by any chance a power saving feature?
mine does the same thing. I think it has something to do with the accelerometer conflicting when laying down, which causes it to not respond to a press of the finger.
Yes, I've noticed the same thing. Specially on the right edge of the screen.
Right edge? Interesting. So it might not be a power saving feature? Ha-ha. Guess it's not that much of an annoyance to you guys too?
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
Ok, probably not. There's gotta be a perfectly valid explanation, but I just noticed this:
When I open Albums on my Hero and look at a single photograph, I can zoom in and out by pinching. Same goes for web pages. We all know this.
But the thing is: if I put my phone down on the table and try to pinch with just one hand (thumb+index finger), it doesn't work!
I only need to touch the phone with one finger on my left hand and it starts working. I have to touch the back or the frame. The chin doesn't react.
I tried it on an iPhone and it works with only one hand. It must be some conductivity issue and the Hero simply has a touch screen that works differently from iPhones.
It isn't really a problem for me: I can hold the phone in both hands while pinching. I just found it slightly interesting...
Yeah I have noticed that as well. Although if you try to calibrate using the g-sensor calibration tool it sometime fixes the issue...
Clue is in the technology? Capacitative touch screen....hit the physics books guys
A good capacitive screen doesn't require the user to complete a circuit with the phone using another hand to hold it, or by touching the bezel with a finger. The problem is either in the circuitry driving the touchscreen or possibly with the algorithms used to establish finger gestures and position.
It's even feasible that the metal bezel interferes with the electrostatic field introduced when your finger is in proximity with the screen. This would explain why the sensitivity is reduced around the edges of the screen.
Spose you need to form a complete circuit for it to work. Interesting point though, I didn't know that capacitive screens needed a second 'plate' to work (i.e. more than just the screen alone).
Makes sense though if you think about it.
Q.I indeed
jayjay said:
Ok, probably not. There's gotta be a perfectly valid explanation, but I just noticed this:
When I open Albums on my Hero and look at a single photograph, I can zoom in and out by pinching. Same goes for web pages. We all know this.
But the thing is: if I put my phone down on the table and try to pinch with just one hand (thumb+index finger), it doesn't work!
I only need to touch the phone with one finger on my left hand and it starts working. I have to touch the back or the frame. The chin doesn't react.
I tried it on an iPhone and it works with only one hand. It must be some conductivity issue and the Hero simply has a touch screen that works differently from iPhones.
It isn't really a problem for me: I can hold the phone in both hands while pinching. I just found it slightly interesting...
Click to expand...
Click to collapse
The metal bezel actually acts like a ground point between the capacitive circuitry and your finger. When you are touching at the very edges of the capacitive area there simply isn't enough room to get a good grounding point so the driver/controller gets a hard time of locating what points are actually grounded. The bezel helps in this regard.
Switchbitch said:
A good capacitive screen doesn't require the user to complete a circuit with the phone using another hand to hold it, or by touching the bezel with a finger. The problem is either in the circuitry driving the touchscreen or possibly with the algorithms used to establish finger gestures and position.
It's even feasible that the metal bezel interferes with the electrostatic field introduced when your finger is in proximity with the screen. This would explain why the sensitivity is reduced around the edges of the screen.
Click to expand...
Click to collapse
...perhaps not then lol
Yeah, well I hate to be the one to ask, but why does it work on the iPhone then? I realize it's a grounding / closed circuit issue, but if another similar phone can do it, then there's obviously a way around it.
And another question: Why doesn't pinching work, but normal one-fingered touching does?
Only place where I could see this becoming a problem is when you dock your device to some plastic holder in a car and want to pinch to zoom in some navigator software. Letting go of the steering wheel to use two hands on your phone isn't necessarily the safest thing in the world. One would assume though, that the interface in any navigator software wouldn't require complex gestures while operating it...
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!
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.
problem: certain area of the touchscreen jumps when pressed. In my case it's over s and z of the keyboard in vertical mode.. effectively preventing me from typing s or z.
possible cause: that's exactly the area that I use to scroll. so it's definitely a high usage area.
quick research: humidity can cause screen to do weird things like that.
quick solution: wrapped the phone without battery in plastic wrap and dumped it into a container used to hold dried almonds along with 2 packs of those humidity absorbers that you aren't suppose to eat.
well. wish me luck
Does it only happen when using keyboard?
maybe try a different one?
Sometimes if my G5 has not been used for an hour or so, it is refusing to wake up from double tap, power button or volume button quick shortcut. Only plugging it in has seemed to wake it up on these occasions.
Has anyone else had this issue?
Not yet.
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Same problem, same case.
What I have found is if you pull the phone out of the case it wakes up. Thinking proximity sensor.
Sent from my LG-H830 using XDA-Developers mobile app
Yup. It really doesn't take much extra coding for them to allow the power button to "Always Wake" the device... I imagine there will be an update in the near future.
As for me... jumping ship to the S7 edge. I really liked the G3, and was hoping this phone could have been that for me... Well, not like I really swap batteries out often anyway
Same case. Same issue. Take the phone out of the case and throw a blanket over yourself and the phone. (Simulating night) and my screen unlocks easy peasy. Something about this lifeproof case. You would think this issue would have been caught in testing and QC.
Yes the phone has a built prox. override. But it only becomes an issue at night. Outside of the case I have no issues with prox. sensor.
I have experuenced this exact same issue with my g5. Whenever its in the dark the power button nor the double tap will wake the screen when in the lifeproof fre case. When out of the case the phone works just fine.
Word to the wise though if you have a zagg glass screen protector and drop your phone both the screen protector and the screen with shatter even if in the lifeproof case. I just experienced this and now have a replacement phone. Just a heads up.
soninja8 said:
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Click to expand...
Click to collapse
I have the rs988 variant and I have noticed this behavior when screen is in always on mode: if I suddenly change from light to dark by covering sensors, the always on clock goes out and nothing I do will allow it to wake up, until I allow brighter light again and the clock reappears. and I can use the double tap and power button again to see the screen. I also notice that the always on clock seems to have an auto brightness independent of the screen settings - I leave screen at 50% no auto brightness, yet I still see clock light levels dim in low light, One other thing - I notice that when I answer a call the screen blanks out (the way it is supposed to ) but does not reappear until I press the power button, just taking away from my ear does not bring display back; I also have the lifeproof case. and just removed it and verified my display now works when I take away from my ear; I just took some spray lens cleaner and cleaned all the surfaces of the phone and case with a microfiber cloth and put it back together and has vastly improved the issue, maybe gone, not sure yet. Update: seems like no matter how clean it is there is still a problem with the case doing something to the proximity detector, cleaning made it better. I can always wake up with the power button for the calling screen(sometimes swiping across top sensor too), wonder if the sensor is a passive light sensor or active (rf/infrared emission)
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
There are allot of other cases you can use but not waterproof. That really sucks good thing for this thread I was going to buy a lifeproof case. Using a otterbox defender right now. Thanks for the post guys saved me some grief.
still under warranty?
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
if still under warranty, see if they will honor it. They did with mine but that was right at the beginning when these problems were linked to the case; mine was in the first 3 months, but the new one worked well for a while, now a little flakey again but not enough to bother me...too bad, a great case otherwise
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
It's not a bug and not poor implementation. Its not light for "dark rooms" lol.. As far as I know it's the proximity sensor. When it is blocked it means the phone is in a pocket or bag and should not register taps. It really makes sense. If you dont xover the sensor and double tap doesn't work ..well.. Well, eother you have defective device or sensor , or the sensor is blocked (maybe bad screen protector?). This didnt happen with my G5 even once. It works 100% (assuming I tapped the same place)
Are the problems as described in this thread still manifesting on current firmware?