Hello. I have a problem with my proximity sensor. When I call, the screen dims instantly. Androsensor always shows 0. I have no screen protector. ROM and kernel is stock. What can I do?
Wololo7 said:
Hello. I have a problem with my proximity sensor. When I call, the screen dims instantly. Androsensor always shows 0. I have no screen protector. ROM and kernel is stock. What can I do?
Click to expand...
Click to collapse
Check that your radio version is compatible with your android version (i.e. .48 with 4.2.2). If it is, it might be a hardware problem :/
Sent by carrier pigeon
Sadly the modem is .48 with Android 4.2.2. Tried downgrading, didn't help. Thank you for answering.
Sounds more like a hardware problem if you're unrooted and still on stock. Has it only happened on 4.2.2 or was it the same on 4.2.1?
BrutalUK said:
Sounds more like a hardware problem if you're unrooted and still on stock. Has it only happened on 4.2.2 or was it the same on 4.2.1?
Click to expand...
Click to collapse
Well I got this phone with the defect. It was 4.2.2. Tried to downgrade to 4.2.0. But it did not help. I am covered under warranty though.
Related
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
Hello, I have a big issue with my LG G2.
The proximity sensor doesn't work, many times when I call the screen doesnt' turn off. I also have some problem with gravity sensor, the screen doesn't rotate. I check sensors answer with an app, and the sensor values holds at 0.
After a reboot gravity sensor works for a while, the proxyimity on the contrary doen't work after a reboot, it works when it want for few minutes and no more.
I tried to remove the screenprotector and to do an hard reset, but I got the same issues also before app and account restore.
Now I don't know if I should send it to assistance of to try to downgrade to android 4.2, what do you think?
May I lose warranty if I try to downgrade?
It is a bit strange issue because sensor sometimes works so I can't be an hardware problem. However I don't remember this issue with the first os versione 4.2 but only after the update to kitkat.
Thank you for your suggestions.
tobiascapin said:
Hello, I have a big issue with my LG G2.
The proximity sensor doesn't work, many times when I call the screen doesnt' turn off. I also have some problem with gravity sensor, the screen doesn't rotate. I check sensors answer with an app, and the sensor values holds at 0.
After a reboot gravity sensor works for a while, the proxyimity on the contrary doen't work after a reboot, it works when it want for few minutes and no more.
I tried to remove the screenprotector and to do an hard reset, but I got the same issues also before app and account restore.
Now I don't know if I should send it to assistance of to try to downgrade to android 4.2, what do you think?
May I lose warranty if I try to downgrade?
It is a bit strange issue because sensor sometimes works so I can't be an hardware problem. However I don't remember this issue with the first os versione 4.2 but only after the update to kitkat.
Thank you for your suggestions.
Click to expand...
Click to collapse
3845#*802# --> Settings --> update touchscreen firmware
Just remember Change the 802 part to your model
If you downgrade you may lose your warranty if they find out so if this fix doesn't work I would recommend you claim warranty on it.
Art Vanderlay said:
3845#*802# --> Settings --> update touchscreen firmware
Just remember Change the 802 part to your model
If you downgrade you may lose your warranty if they find out so if this fix doesn't work I would recommend you claim warranty on it.
Click to expand...
Click to collapse
Thank you.
I tried as you suggested. When i push on "update touchscreen firmware" the phone holds for some seconds (2-3) and nothing happends (no alert, no error,) i just push back to return to the hidden menu. Is is correct? If yes, it unfortunately doesn't solve this issue...
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
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
..
yeahman45 said:
Sometimes, when i try to wakeup my phone using home or power button, the capacitive keys light up but the screen is black.. I have to press power button to "sleep" and wake it up again... any idea? It was like this since I got it.... I updated recently and the problem still persists... it's not a big deal but a bit annoying at times.
Click to expand...
Click to collapse
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
vndnguyen said:
It may be due to firmware bug or some installed app.
You didn't tell what rom you are using (stock or custom). And also check for installed apps that you suspect.
Click to expand...
Click to collapse
It's a hardware defect. Mine was like this too since 11th april. After changing the motherboard to the newer, 1.1100 version, the problem is competeley gone away. It's waking up every time correctly.
We had a topic about this earlier...
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
yeahman45 said:
Hardware defect? Are you sure? I dont have a warranty. Bought it abroad. I was hoping it was just a software glitch. I am on stock unrooted
Click to expand...
Click to collapse
I'm totally sure because i had this bug from the beginning. I was trying all firmware updates, factory reset, etc. It's not related to the fingerprint sensor or any app installed or not.
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
yeahman45 said:
Ok i have no choice. Will try the solutions i read from google, seems to he a common issue
Click to expand...
Click to collapse
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Levus said:
All i can say is that the old motherboard was 0.800 according to the phone info app, and the new one is 1.100 .
Click to expand...
Click to collapse
anyone else can confirm it's a hardware issue? does it get worse with time? I still get it (but seems worse sometimes, where i need to press power button several times to wake it up) and i have tried a lot of suggestions
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
yeahman45 said:
anyone with a non-touchwiz rom have this problem? maybe it is related with touchwiz?
Click to expand...
Click to collapse
anyone can report if it also happens with a non touchwiz rom?? I can't flash one as my phone is still under warranty
no one can't reply? so this issue is not common after all?
guys i am going to void my warranty to flash cm12... does it solve this issue??
adit said:
Re-activation lock only works when knox is 0x0 but that too can be bypassed by installing custom rom so...
Click to expand...
Click to collapse
I can not install custom in my own phone ...0x1...after install xtrolite 2.2....f...
Have someone solved the problem by flashing a custom kernel? Still getting the issue on latest lollipop rom
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