Hey guys,
I have a question about what I am noticing and is bugging the heck out of me.
When I am on a call the screen goes black like it should, but once I remove the phone from my ear, the screen always came back on by itself..... Until I upgraded to Kit Kat. Now it just stays black and I have to press the power button to turn the screen on.
Is there a setting for this somewhere that I am missing?
Thanks!
Sent from my Nexus 4 using Tapatalk
Hmm, sounds like an issue with the proximity sensor. It should turn back on based on my use of the N4 from 4.2.2, 4.3, and 4.4.2.
Maybe try re-loading the OS?
Itz mostly that your proximity sensor bug !! What you can do is download a proximity sensor app from the play store like proximity on/off and test whether that works !! If it doesn't that means you have a bug in your ROM !! If u have unlocked your boot loader then flash the stock image or if u have rooted+custom recovery you can flash custom or a stock zip file
I hope it resolves your issue !! Hit the Thanks button if you find my post useful !!
Sent from my Nexus 4 using Tapatalk
Hmmm yeah I just tried a sensor app and it just says no change detected. It's weird cause I am running stock rom downloaded straight from Google. Just rooted and unlocked bootloader.....
Sent from my Nexus 4 using Tapatalk
So maybe the Proximity Sensor doesn;t work at all on this phone ... (I just got it through a warranty exchange because on my old N4 the screen broke).
I just flashed factory images again (EVERYTHING) and the Proximity Sensor still doesn't work. It shows it doesnt detect anything, even if I put my finger right over it. It does say Proximity Sensor is available though ....
so idk ...
If you go back to 4.2.2, does the proximity sensor work?
Proximity sensor is definitely broken, it's not a software issue. If you've still got warranty you should send it in.
audit13 said:
If you go back to 4.2.2, does the proximity sensor work?
Click to expand...
Click to collapse
I'm gonna flash 4.2 later and see. I just got the phone as a warranty exchange 2 days ago so if it still doesn't work I'm locking it all back up and telling tmo.
Sent from my Nexus 4 using Tapatalk
Talked to T-Mobile.... They're sending me another one. Glad I caught that early. Thanks for all the input yall!
Sent from my Nexus 4 using Tapatalk
Related
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
should probably backup your things and reflash, preferable with odin i would think.
KateC1 said:
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
Click to expand...
Click to collapse
You could take it in to the store and see what they can do...they will probably just do a hard reset....I think your best bet is to, like the other poster said, do a fresh install of EB13. Most of the problems with this update were with the update and not with the clean install...good luck!
I could probably assume you don't know what odin is and everything so.. maybe someone could post a link to odin and the eb13 tar??
From My Samsung Epic Using TapaTalk.
It's just your install, use the full 200MB samsung exe after backing up your data and you should be good to go. That's not a bug of EB13, just the way your phone patched to it.
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
KateC1 said:
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
Click to expand...
Click to collapse
Sorry you did all of that for nothing :-( Download Z-Device Test from the market. There is a test for the proximity sensor in there. If it is not working in the test, I would say you should go to Sprint and have them fix it...I searched for others with your problem and there were a few (not from updating, you might have had it stop working by coincidence). They all ended up going to sprint and having the screen replaced. Just make sure that if you have a screen protector you remove it so Sprint doesn't try to blame that.
Good luck Katie
P.S. If you are feeling adventurous, you could always Odin back to DI18 and see if the sensor works and the back to EB13 to see if it still works....you could also try installing a ROM on top of EB13 and see if that makes it work (though I don't see why it would) Good Luck
Patrick
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
KateC1 said:
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
Click to expand...
Click to collapse
No problem... just tell them it happened after the update and I don't see any reason that they should charge... they seem to be hit or miss about charging sometimes, try a different store if they want to charge... good luck Katie. Let me know how it turned out.
Sent from my SPH-D700 using XDA App
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Burkettacb said:
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Wow this is happening to me as well. I'm running the optimus rom currently. I'm reverting to stock here shortly in hopes for the KK update soon so I'll see if that fixes it.
nope. up to date stock zva now and knock on doesnt work but knock off does work as you stated. well this is wierd.
Well thats ****ing depressing
Sent from my LG-LS980 using xda app-developers app
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
This could also be an issue with your proximity sensor. If something (screen protector, finger, dust, etc.) is blocking your proximity sensor, it could be reporting to the phone that it is in a pocket, and to keep the screen off. Try to clean that area, and avoid obstructing the sensors "view". As for the leaving it in the sun, you could have damaged the sensor? You could test it by making a call real quick and see if the screen turns on when you pull the phone away from your face.
Sent from my LG-LS980 using XDA Premium 4 mobile app
The sensor seems to be working fine. Just tested it.
DrZeuss said:
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
Click to expand...
Click to collapse
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
4NDR345 said:
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
Click to expand...
Click to collapse
My screen turns completely on and off when I use the button/knock-off feature. I'm going to take it to a technician today and see what they have to say about it.
First, What are you running on your device? Stock? Rooted...
Burkettacb said:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That's odd, I have not seen much on this... if running stock
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Or againg, a ROM you may be using.
More detail would be helpful:good:
For me it happend on stock and rooted with aospa... Dont know What can cause this. I Sent it to my Carrier they found nothing....
Gesendet von meinem LG-D802 mit Tapatalk
running stock myself. Technician was useless and told me nothing.
DrZeuss said:
running stock myself. Technician was useless and told me nothing.
Click to expand...
Click to collapse
Same here
Gesendet von meinem LG-D802 mit Tapatalk
Did you try the Stop Having Sprint fix?
Sent from my LG-D800 using XDA Premium 4 mobile app
I got the d802...
Gesendet von meinem LG-D802 mit Tapatalk
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
ingoljosh said:
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
Click to expand...
Click to collapse
This^. For me I have to use my entire thumb or even palm, but it occasionally works.(still like 1/30 tries). This leads me to believe that it is software related. This one issue is killing me. I hate using the power button on the back so I only used knock on. Now that it's not working I'm hating this phone. Knock off works great and I know knock on is kernel based so maybe someone can create a kernel that fixes this issue.
This did work for me. Fixed the knock on feature on my D802.
Credit: Smith I Run (Thread from android central. Can't post link to thread)
There is a solution; (not sure about it, my friend had the same problem and he fixed it with this method)
Open dialer menu and type;
5689#*980# (Sprint)
3845#*801# (T-Mobile)
3845#*803# (AT&T Canada)
3845#*802# (International)
3845#*800# (At&T)
3845#*980# (Verizon)
And when hidden menu is showed up, go to "Settings"
and go to "Update Touch Firmware".
The touchscreen won't work until after 5 seconds, Wait for it and if touchscreen gets working, exit the menu.
Lock the phone and try knocking on the screen, It should be working :laugh:
Click to expand...
Click to collapse
Hello guys,
I have Note 3 (SM-N9000Q)
Android version: Stock 4.4.2 N9000QXXUDND2 -Turkey-
I get this phone new.
After having a call screen comes up with very low bright. Do you know what would be the reason? Software? Hardware?
* I did auto-brightness off (I using full brightness)
* Auto adjust screen tone off
* Adapt display off, but did not improve.
After some calls to very low the screen brightness :S
I making a call, I'm holding my hand over the sensor
and the occasional screen brightness too low to be opened.
Help
@serdar_gs if you cover the sensor when talking on a call, screen goes off.
Is this you want to say?
Sent from Galaxy Note 3 SM-N9005
@thahim, I do not use cover but screen has a protective transparent gelatin.
@serdar_gs what I mean to say when you put ur hand on the sensor near the ear peice while in a call. Not the cover.
Sent from Galaxy Note 3 SM-N9005
@thahim sorry for my bad english
I do not use cover. no cover.
There is gelatin screen saver.
Not a problem with this constant, I call and occasional screen is low brightness opened by.
Sometimes to be opened with normal brightness, sometimes unfold with low brightness :S
@serder_gs which language do you speak. Ill try to translate
Sent from Galaxy Note 3 SM-N9005
@thahim my speak Turkis and i using google translate
Help guys What is the solution?
Try to do a factory reset to make sure that it's not a software issue. If the issue persists, it may be a hardware issue (sensor maybe?)
@Bibz0r I did that test proximity sensor. Everything seems normal. I'm downloading rom, I will do the installation from scratch.
Is there anyone experiencing this issue?
I think this might be an issue KitKat =)
I'm using a KK ROM now but I had stock KK before and never had this issue.
I'm curious, what ROM are you installing?
Bibz0r said:
I'm using a KK ROM now but I had stock KK before and never had this issue.
I'm curious, what ROM are you installing?
Click to expand...
Click to collapse
I using and installing stock 4.4.2 turkey rom. I get this phone new. I dont install other roms and root.
I did wipe data and again install stock 4.4.2 rom. problem continues =)
I think the this problem is that 4.4.2 ROM turkey
serdar_gs said:
I did wipe data and again install stock 4.4.2 rom. problem continues =)
I think the this problem is that 4.4.2 ROM turkey
Click to expand...
Click to collapse
Have you installed a stock ROM from SamMobile? You can get them here :
http://www.sammobile.com/firmwares/
Let me know if you are still having issues.
@Bibz0r yes I did download it from there.
Don't rule out a possible hardware issue too. Or maybe a bug in the Turkish ROM, like you said.
If it's a new phone, you still have warranty?
Yes new phone and have warranty
Then I would suggest you contact your carrier/manufacturer to get it checked.
Let me know how it goes.
ok thanks
Hello everybody .. when i put the phone in my pocket it keeps vibrating and the pocket not small so there is no buttons clicking ..and i couldnt figure out why it is vibrating.. does anyone have the same thing?
Sent from my ONE A2003 using XDA-Developers mobile app
It might be triggering the double tap to wake gesture, while walking by bumping in your leg. I had the same issue on a custom rom (don't rember which exaclty), while on OOS it was fine. I think there are some roms which have a sensor block, so it doesn't false wake , or something like that.
I have the same issue and I am on latest Temasek....
I would be happy for any solution
brausi said:
I have the same issue and I am on latest Temasek....
I would be happy for any solution
Click to expand...
Click to collapse
I am on stock rooted oxygenOS and i think it might be fingerprint sensor
NY_3 said:
It might be triggering the double tap to wake gesture, while walking by bumping in your leg. I had the same issue on a custom rom (don't rember which exaclty), while on OOS it was fine. I think there are some roms which have a sensor block, so it doesn't false wake , or something like that.
Click to expand...
Click to collapse
Sent from my ONE A2003 using XDA-Developers mobile app
I'm pretty sure it's the fingerprint sensor which is triggering the vibration but I haven't found a way yet to fix this issue. I'm on official CM 13 by Grarak.
okaay3D said:
I'm pretty sure it's the fingerprint sensor which is triggering the vibration but I haven't found a way yet to fix this issue. I'm on official CM 13 by Grarak.
Click to expand...
Click to collapse
I made sure that it the fingerprint sensor because Everytime it starts vibrating and i take it out of my pocket and try to unlock the screen using fingerprint it tells me that the phone is locked because i tried to unlock it too many times
Sent from my ONE A2003 using XDA-Developers mobile app
Today my phone started staying in pocket mode and auto brightness quit working. When I turn on the front facing camera it starts off as a white screen and then adjusts from there. I took off the screen protector and case, made sure everything was clean, and still, no light sensor working.
OOS 10.3.2
Idk if your rooted but I had that problem I had to unroot and start from scratch not sure what caused it ..but it was something i flashed in magisk
JB calhoun said:
Idk if your rooted but I had that problem I had to unroot and start from scratch not sure what caused it ..but it was something i flashed in magisk
Click to expand...
Click to collapse
No ****? Huh, the only thing I flashed recently was an update to the call recorder app. Funny if that's the thing that buggered up the proximity sensor.
What steps did you take to unroot and reroot? I was about to reflash the latest OOS, and do all the steps involved with that.
jova33 said:
No ****? Huh, the only thing I flashed recently was an update to the call recorder app. Funny if that's the thing that buggered up the proximity sensor.
What steps did you take to unroot and reroot? I was about to reflash the latest OOS, and do all the steps involved with that.
Click to expand...
Click to collapse
The call recorder app is your problem
I have the same problem .. did a factory reset bust still the same.
I have the same problem
Switchonthelight said:
I have the same problem
Click to expand...
Click to collapse
Yeah, I never found a solution, just had to go with adjusting the brightness manually. But, I did break my phone and had to go with a cheaper replacement.
Sent from my motorola one action using Tapatalk