Related
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.
Hello,it seems there is no Q&A forum for this device, so here is my doubt:
Although the tech manual for the xperia S from the sony website report a proximity sensor, I fail to find one on my phone.
There seems to be a black oval spot on the glass next to the light sensor as if some sort of sticker can be removed to install the sensor.
The light sensor seems to work, since I've seen the screen go darker and brighter, but when I'm in a call and put the phone in my ear the screen wont shut off like in my old SGS nor will it turn on when I move the phone away from my face.
are your phones like mine? or is mine a defective unit?
I guess ur device has something wrong with it.
By the way; did u place a screen protector?? Coz if u did that may be the problem!
I think the light and proximity sensor are the same.
There is something wrong with your phone,maybe you should try to flash a new firmware.
Sent from my LT26i using Tapatalk 2
grained said:
Hello,it seems there is no Q&A forum for this device, so here is my doubt:
Although the tech manual for the xperia S from the sony website report a proximity sensor, I fail to find one on my phone.
There seems to be a black oval spot on the glass next to the light sensor as if some sort of sticker can be removed to install the sensor.
The light sensor seems to work, since I've seen the screen go darker and brighter, but when I'm in a call and put the phone in my ear the screen wont shut off like in my old SGS nor will it turn on when I move the phone away from my face.
are your phones like mine? or is mine a defective unit?
Click to expand...
Click to collapse
Hi,
Mine works fine...
Do this:
1>Go to dialpad and type *#*#7378423#*#* (*#*#SERVICE#*#*)
2>A menu pops up in that u will see service tests select that
3>Then scroll down and select Proximity Switch
4>Initially it will display as OFF. Now u place your finger or hand on the Proximity Sensor, then the value of Proximity Switch on the screen will change to ON.
If this is working then the sensor is just fine u need to update the firmware else u need to go and replace the piece IMO though.
Thank you all for the feedback.
I used the service menu to check the sensors ...
indeed the proximity sensor is always off, even when I put my finger on it, it seems someone forgot to remove the black paint from behind the glass, but I will update it anyway to make sure before returning it.
grained said:
Thank you all for the feedback.
I used the service menu to check the sensors ...
indeed the proximity sensor is always off, even when I put my finger on it, it seems someone forgot to remove the black paint from behind the glass, but I will update it anyway to make sure before returning it.
Click to expand...
Click to collapse
sensor is IR, so darkened window is normal for it. but if it have always closed windows - than its status must be always ON. so, most likely you have faulty sensor (or bug in firmware)
goodwin_c said:
sensor is IR, so darkened window is normal for it. but if it have always closed windows - than its status must be always ON. so, most likely you have faulty sensor (or bug in firmware)
Click to expand...
Click to collapse
Hi,
Exactly it should be showing status as ON if it's covered replace the piece as soon as possible
shoz_on4u said:
Hi,
Exactly it should be showing status as ON if it's covered replace the piece as soon as possible
Click to expand...
Click to collapse
If it was covered by the glass/ cover it would show OFF because the glass doesn't radiate heat like your body does.
Sent from the Delta Quadrant using a transwarp conduit.
Pezo said:
If it was covered by the glass/ cover it would show OFF because the glass doesn't radiate heat like your body does.
Sent from the Delta Quadrant using a transwarp conduit.
Click to expand...
Click to collapse
Proximity sensor on phones does not react to heat. It have simple IR transmitter, which emits a beam, and IR sensor, which react on reflected beam.
goodwin_c said:
Proximity sensor on phones does not react to heat. It have simple IR transmitter, which emits a beam, and IR sensor, which react on reflected beam.
Click to expand...
Click to collapse
You are right, just tested it and it seems to be a reflective sensor.
thanks for the tips, it was indeed a faulty sensor and they gave me a new phone right away .
I hope I don't get any more problems like a yellow tint :X (knock on wood with fingers crossed)
I had a bunch of requests for Wave Control to have this functionality. I thought it best to do a dedicated app so here it is!
Flip Case Control was designed to work with Samsung's Flip Case on the I9300 while using as little battery as possible. (I left it running all night ~8.5 hours and the battery dipped 1% more than usual)
IMPORTANT: If your case is black or dark on the inside, the sensor doesn't read correctly when the case is closed. To fix this, put a piece of light colored tape on the inside of the case where it lines up with the sensor (located next to the front camera)
Note: A Samsung based ROM is required. CM won't work well.
Here's a demo video:
Play Store Links:
24 Hour Trial Version
Full Version
Could you guys with the Flip Case test it out?
All feedback is appreciated greatly!
I would like to try it for you but unfortunately i don't have flipping cover for this lovely device as it is not here yet everyday im searching everywhere but nothing
Waiting OP to give us their opinion about this app
Sent from my GT-N7100 using Tapatalk 2
I have the combination.Let me try it and i ll report back
edit: works fine with stock rom and flip case.
Sent from my Galaxy Nexus using Tapatalk 2
afilopou said:
I have the combination.Let me try it and i ll report back
edit: works fine with stock rom and flip case.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for letting me know!
Is there something special about Samsung's Flip Case? I have a generic flip case but can't get this to work. Running rooted Deodexed LJ1.
dosher said:
Is there something special about Samsung's Flip Case? I have a generic flip case but can't get this to work. Running rooted Deodexed LJ1.
Click to expand...
Click to collapse
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
MarksThinkTank said:
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
Click to expand...
Click to collapse
I bought the full version ystd. Yes it does work sith my rock flip case but i had uninstalled ot as it does turn off my screen for no obvious reason when im using it.
Hopefully you can come up with a fix for it soon
MarksThinkTank said:
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
Click to expand...
Click to collapse
It's a cheapo from ebay until I can find a decent one...
http://www.ebay.co.uk/itm/Samsung-G...sPouches&var=540094094344&hash=item4d05abf35b
But you're right - the sensor doesn't like black. If I use a piece of lighter coloured tape on the inside of the cover it works! The only issue I have now is that the app is not auto loading at boot.
Jaemon said:
I bought the full version ystd. Yes it does work sith my rock flip case but i had uninstalled ot as it does turn off my screen for no obvious reason when im using it.
Hopefully you can come up with a fix for it soon
Click to expand...
Click to collapse
I'm working on an update right now to help reduce the unintentional triggers. I need to test it a little bit more but it should be out soon.
dosher said:
It's a cheapo from ebay until I can find a decent one...
http://www.ebay.co.uk/itm/Samsung-G...sPouches&var=540094094344&hash=item4d05abf35b
But you're right - the sensor doesn't like black. If I use a piece of lighter coloured tape on the inside of the cover it works! The only issue I have now is that the app is not auto loading at boot.
Click to expand...
Click to collapse
Are you running the full version? I limited that function to that version. Great to hear the tape fix worked
According to me proximity autolock works well and it is available on play store
Sent from my GT-N7000 using xda premium
It works OK at the moment, I think the sensitivity should be decreased though as something passing an inch or two above the proximity sensor will still turn off the screen. Seeing as flip covers get up close and personal with the proximity sensor this seems a bit too sensitive.
EDIT: Definitely too sensitive, seems to turn off at random at times. Just had a phase where it wouldn't let me keep the screen on.
Maybe a failsafe of sorts could be implemented? Leave the screen on until timeout/power button press if turned on by the power button?
Edit 2: I uninstalled the app to stop it turning the screen off constantly, but it continued even after a reboot, I went into the display settings and saw the screen timeout had been changed to "()"and this was causing the issue, as soon as I changed it back to 30 seconds it was fine. Is this supposed to happen?
MarksThinkTank said:
Are you running the full version? I limited that function to that version. Great to hear the tape fix worked
Click to expand...
Click to collapse
Yeah, just running the trial version - that explains it.
D3_ said:
It works OK at the moment, I think the sensitivity should be decreased though as something passing an inch or two above the proximity sensor will still turn off the screen. Seeing as flip covers get up close and personal with the proximity sensor this seems a bit too sensitive.
EDIT: Definitely too sensitive, seems to turn off at random at times. Just had a phase where it wouldn't let me keep the screen on.
Maybe a failsafe of sorts could be implemented? Leave the screen on until timeout/power button press if turned on by the power button?
Edit 2: I uninstalled the app to stop it turning the screen off constantly, but it continued even after a reboot, I went into the display settings and saw the screen timeout had been changed to "()"and this was causing the issue, as soon as I changed it back to 30 seconds it was fine. Is this supposed to happen?
Click to expand...
Click to collapse
Ah.. crap. I thought I fixed that bug before I released it. I guess there's still a way for that to happen.
I'm working on an update to help filter out false triggers and will patch that bug. It shouldn't happen. Sorry.
garvit18 said:
According to me proximity autolock works well and it is available on play store
Click to expand...
Click to collapse
Proximity Autolock is a nice app with some excellent features but uses too much battery on The Note 1, an additional 8% overnight. And it doesn't work well on my Note 2.
The app works well. I bought it
It's a very useful feature that Samsung should have built in, but hey, I don't mind supporting you.
Gnarfsan said:
The app works well. I bought it
It's a very useful feature that Samsung should have built in, but hey, I don't mind supporting you.
Click to expand...
Click to collapse
Thanks!
I agree Samsung should have made this app. When I first showed it to a friend, he said "Isn't it already supposed to do that?"
A Beta
Here's what I'm playing with right now.
It should hopefully fix the bug D3_ ran into as well as reduce the false triggers. There will still be some due to sensor placement but this should make it much less sensitive. Also response time to turn on the screen should be a little bit faster. It's working well on my I9300, hopefully it should be the same on the Note II.
Let me know if this is performing better for you guys.
Still coming:
Disable in Landscape Mode
Disable when plugged in
[Edit: Removed Old Beta]
Just installed the beta, will report back after some use of it.
V1.05
Just uploaded version 1.05 to the Play Store
Changes:
Reduced false triggers for screen off
Changed button UI
Added notice about dark cases
Updated icon
Sped up screen on response a little bit
Cant you just do this using Tasker? I already spent money on the flip cover, so kinda hesitant to spend more for this functionality (which should be there in the first place!)
Hi.
I seam to have a strange issue with the proximity sensor on my SGS3. I just got a flip cover that replaces the default back cover. When this is covering the screen, I thought that the sensor would register this, but it don't. It does register if I keep the cover just a multimeter above the screen, but if it touches the screen just above the sensor, it does not register that it is being covered.
This means that I have to keep the flip open during calls, otherwise the screen will be kept on. It also means that I can't use any of the flip-screen-off apps on the market.
This is even an origin Samsung cover http://www.samsung.com/us/mobile/cell-phones-accessories/EFC-1G6FBEGSTA
Anyone knows how to deal with this issue?
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?