Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can disabled it in TouchWiz. I'm not sure you can in an AOSP rom, which your 4.4 rom is.
It could also just be a ROM bug that hasn't been worked out yet. I'd check the development thread for this rom and see if it's a known issue.
If it is, help the developers by posting a logcat of the problem in the develoment threads. (Because odds are no one else has)
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You didn't get a response in a development thread because development threads are not for tech support. They are for discussing development. Tech support questions (which this is) do not belong in development threads.
The rest of XDA isn't even for tech support. We are just happy to try and assist if you get stumped. And don't get me wrong, we are legitimately happy to try and assist you. But complaining that it's "usual that no one responds to you" is pretty rude. No one promised you tech support here. If you get help, it's because someone was trying to be nice, not because you are owed an answer.
If you are using an alpha release ROM it's YOU who should be providing tech support to the developers by giving them logcats of your error so they can review them and find out what is causing the conflict. That's how you can help add to XDA and assist the developers who are building cutting edge software for you and giving it away free as a gift.
If you aren't willing to put up with the proximity sensor errors, or to help the developers fix it by providing them with the logs of the error, then your best bet is to move back to a stable build of a 4.3 or 4.2 ROM for another month or two until the major issues with 4.4 are hammered out.
As for asking for help here, what else have you tried? Have you verified that the bug doesn't exist if you revert to a different ROM?
Have you done a full wipe and clean install of the 4.4 rom and tested for the bug immediately, before installing any other apps or user data? Since you are the only one having the issue this could easily be a conflict with some other app that you have installed. The full wipe and test is the best way to confirm that or rule it out.
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same scrap happening with me. The problem is the proximity sensor is always detecting something is in its proximity (most likely dust that got in through the ear piece grill). As a result, the screen turns off immediately when a call is answered, and in Android 4.4 the power or home button can not override this. Interestingly, in 4.3 the power or home button does in fact override the proximity sensor. Why the difference between 4.4 and 4.3 I'm not sure. As Skip Jack alluded to, in Touchwiz roms under settings>my device>call> "turn off screen during calls" can be toggled off to shut down the proximity sensor. If I could find a setting like this in stock 4.4, that would solve this issue.
I need to reflash a 4.4 rom and look for this setting, although I do not think it exists.
I've tried the "pressurized air into the ear piece grill" fix, but it didn't work for me.
Any other suggestions?
https://www.youtube.com/watch?v=zm4f2XjQLAM&feature=youtube_gdata_player
QUOTE=fateownzyou3;47870242]Well iv went thru the threads of the developme, section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent I rom my SGH-M919 using xda app-developers app[/QUOTE]
Canned air didn't work. So I took my phone apart as demonstrated on YouTube , and when I peeled back the proximity sensor and gesture sensor assembly (they're one piece, attached to the earpiece) i found little bits of sand and dust. A lot. I enjoy the beach in the summer. I cleaned the sensors and the screen area that they are housed in (the part of the screen they "look" out of) with a dry q tip. after putting it all back together its as good as new. *#0*# confirms all sensors now working. The vid above is what I used. You only have to remove sim, sd card, little screws, back speaker, side housing, and a small bracket (in that order) before disconnecting and peeling back the proximity/gesture sensors in order to clean.
You don't have to remove all that other stuff.
I am having the same issue since puttin on CM 11. In 4.1 there was a setting to turn the proximity sensor off but in 4.4 there isn't. I keep looking for an app or something else to trigger it but it is also driving me crazy.
It only happens when my protective case is on my phone, but I am the type of person that NEEDs a case on their phone otherwise itll crack or drown within a couple of days. Any help would be appreciative.
I am having the same issue. Just installed CM 10.2.0-jfltetmo
How do I get a logcat to post? Also, what other information would be helpful for development?
I don't think my issue is sand in the sensor... but I will post back after I open it up and check it out.
If anyone knows of a fix or way to access settings for the proxy sensor, that would be awesome! Also, isn't there a way to use the terminal session to read data from the sensor?
Thanks for any help provided!
Another idea for those who are stuck. I didn't find a way to disable the proximity sensor, but there is another way to hang up a call. If you go into Accessibility options, there is an option to hang up call with Power button. This way you at least have a way to hang up the phone call without having to pull the battery, etc. But it doesn't help if you need to enter additional numbers on the keypad unfortunately. But at least we can hang up now!
I've been having this issue as well which seems to be an aosp bug, but for the mean time, has anyone come up with a solution? Ive tried tasker actions to turn screen on during calls but it seems to be blocked due to the proximity sensor. I know that downgrading to 4.3 is an option but a workaround must be possible. If you find it, Post it.:good:
Edit: Came across this post. Haven't tested yet but it seems promising
Edit2: Wasnt able to get the app to solve the issue as others stated
Hardware fix for proximity sensor
The apps mentioned in this forum and others did not worked for me. My phone is not rooted; perhaps this is required. Apps that I tried are:
Proximity Screen Off Lite
Caffene
I did find the Phone Tester app very useful during the surgery.
I was able to desensitize the proximity sensor as follows. The sensor is made of an IR emitter and an IR detector. It is very sensitive. Small reflections from one side to the other will cause the sensors to show "near" instead of "far."
0. When you look at the Nexus 4 straight on (front camera on top right), of the two elements on the top left, the one more to the right is the IR emitter.
1. Open the phone and gently peel back the proximity sensor/headphone jack (2 + 9 screws; pry plastic and one flex).
2. On the hole corresponding to the IR emitter, apply two small squares of masking tape cut to 1.5 mm x 1.5 mm. Only cover that hole; you do not want to cover the ambient light sensor. The masking tape blocks enough IR to desensitize the system, but won't deactivate it.
3. Gently pry up the digitizer from the phone near the corner when the sensor is. Using a toothpick, apply a drop of superglue just inside the top left corner. Apply pressure and ensure that the digitizer sits firmly on the frame. This is necessary because a slightly separated digitizer will reflect the output of the IR emitter back to the sensor (think about standing behind a window about a foot versus having your nose up to it; you don't see your reflection when you are close).
All this assumes that you know your way around opening the phone and have the correct tools. Sharp objects, execessive force along any step can break your screen or the phone in a split second. If you are not comfortable with it, don't do this.
-PD
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
You only need to post your question once. You have it in a more appropriate thread already. Please don't dig up 5 month old threads to multi post your questions.
Related
Hi,
I've searched high and wide for a solution (other than sending it back to Motofailure repair) and am failing at finding one so far. So I'm hoping I can get some help from here.
So, this is the situation: I make a call, screen instantly turns dark and will only light up again when I press on the area where the light (&) proximity sensor is.
I've already tried the following.
1.) Done a factory reset (3x) - with mem card, with reformatted mem card, w/o mem card.
2.) Clearing the dust on the earpiece hole using an air duster.
3.) There were times that I worked properly after I've uninstalled apps but the issue came about again after a couple of tries.
So, now I'm thinking that I might want to root my Defy to set things right. I'm quite familiar with RSD Lite as I've used it before on my RAZR2 V8.
A bit of background: I bought my Defy on pre-order so this is one of the earlier models. I had the earpiece problem and sent it to Motofailure repair and the whole process took a month (32 days to be exact - long story. I'm avoiding having to send this PoS back. They updated the software when I got it back.
As far as I can recall, I didn't had this problem before the earpiece problem. And I'm thinking it might be a software problem hence I'm now looking at a solution by rooting and flashing the ROM with an original one.
I have no way of finding out (as far as I know) whether this is a hardware problem (hence hesitating to have it sent back to Motofailure repair).
What I've also observed is that when there is direct bright light, it works normally but when its dim, then the problem appears.
I don't have any screen protectors, just so you know.
Can anyone advise me on what to do?
During a call proximity sensor is activated to turn off the screen at the moment it detects proximity and asumes you are using the phone against your hear, so it turns off screen to save energy.
I think you might have some app installed in your phone, using and reversing the sensor status so it detects proximity when there isnt, and viceversa
You might want to try removing apps using that sensor and see if problem gets solved, there is also an app in the masket called sanity; which makes extensive use of proximity sensor for vaqrious things, and have an option to reverse proximity sensor, you might want to try it and see if problem gets fixed.
You might try this things: remove apps using proximity sensor, test phone. Deactivate in pocket detection; test phone, and install sainity, test phone, install a new rom?
If speaker is bigger than original one, or there was an assembly error, light/proximity sensor won't fit into right place.
I've seen such reports and you can't do anything unless you open up thing and check the problem, but you haven't seen the right assembly so you may not know the right place.
Are you using any screen protector? I know some screen protectors cause this problem.
Edit: Nevermind, I see that you're not using any.
how to calibrate the proximity sensor?
My new defy 's proximity sensor seems cannot work correctly,when i making a call ,the screen shut off immediately，and the screen could not light on by any key,but when i touch the proximity sensor with my finger,the screen may be light on!
so i download a app to test the proximity sensor which name's"Android sensor data",this app fingue out the state of proximity sensor,"near" or "far",sometimes I just passing my finger over the proximity sensor, the reading will show 'near' and then remain 'near' even when my finger is moved away!
Can anyone else help me to calibrate the proximity sensor?google told me some android phone can do this ,such as htc, zte etc.
goole tell me android phone have some standard testcode,such as *#*#4636#*#* can show the phone statue,it works correstly in Defy,*#*#0588#*#* test the proximity sensor ,but it doesn't work in defy!!!
I don't think this issue could be solved trough software tweaks. Chances are this is a hardware problem. Maybe you should contact the Motorola support.
try disabling in-pocket detection
have the same problem. it started 2 days ago. Im using CM7. It just turns dark and wont wake up unless someone else is calling me. Just got it tested, and when i cover the sensor with my finger it says 0cm distance for long time.
I've tried data wipe and similar, but nothing helped so far.
EDIT: I've just tried wiping the place where proximity sensor is with some soft cloth and alcohol and for the time being, it works. O.O
Could Wipe Dalvik help?
I was checking voicemail today.. put in my password thru the keypad.. and then once i put the phone back next to my ear.. i kept pushing the keypad buttons with my cheek. until the promixity sensor caught on..
anyone else getting this prob? just an fyi.. i have the SGP Oleophobic Screen Protector on my phone.. i'm not sure if that decreases the reaction time for the sensor or not.. but its a pain..
No mine does that too. I've been using google voice to keep my old number, which asks to hit a 1 or 2 to accept/decline thus keeping the keypad up.
When I'm on a call and shufflin' (everyday I'm shufflin') sometimes the screen pops back on with my face on it and all of a sudden you'll hear a bunch of tones over the phone. lol. Everyone asks, "What was that?!" and I just giggle and say, "Don't worry about it" or "I didn't hear anything" lol.
But yea. It's a tad slow. Probably just a setting. I'm sure it'll get fixed soon.
I thought I was the only one experiencing this issue! I had this proximity sensor issue on my Iphone 4, but it was hardware related. This only appears to occur when the dialpad is still on during a voicemail or phone call. This is BEYOND ANNOYING and I hope that Google is able to address this via software fix. I'm surprised they let this one slip through the cracks.
Proximity sensor slow
Yep. Mine too.
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
http://www.youtube.com/watch?v=cjTGQaK1Qvw
This thread is pretty dead, and I haven't found too many other posts regarding this issue. I'm shocked to not see any replies, including the ones who already wrote in this thread. I was hoping to get some confirmation if their "slow" responding phones are also exhibiting this correlation with the accelerometer.
Is this not a wide spread issue? Is what I demonstrated not expected behavior? Do I need to exchange my phone?
I hope not - I bought this from a Amazon merchant, so I don't know how hard it is to get warranty work done (since it's imported).
I'm in the US, and this is a GSM version. We only have the CDMA version (Verizon) officially.
Forgot to post here regarding this issue. Not fixed, but I think it's more of a software issue than hardware. I wrote and made a video that might explain why I think it's a software issue:
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
naddie said:
This thread is pretty dead, and I haven't found too many other posts regarding this issue.
Click to expand...
Click to collapse
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
case0 said:
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
Click to expand...
Click to collapse
It's an issue for me, no screen protector and the timing's almost sporadic when holding it naturally. But it could also be how I hold it as said earlier in the thread
I also have the same issue when checking voice mail. My damn cheek always hits a number or some button after putting in my pin.
Screen orientation in general seamed slow to me on 4.0.2. 4.0.4 speeds things up a bit, it's listed as one of the improvements.
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
ericshmerick said:
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
this is what i do too it's a pain though - i hope we get 4.0.4 in the UK on o2 soon! im tired of waiting for faster screen rotation and more responsive proximity sensing
All my P sensor issues were fixed after flashing the PrimeLA03 bootloader.
Hi people. I have the same issue on 4.0.4 (Stock OTA).
The proximity sensor shows no output after testing it with "Sensor List" and with "Elixir 2".
Any ideas? Thx.
I have this issue too!
I have it too, I just tilt the phone to touch the ear first and then bring it close to my face.
edit with a rom
If your using a Rom like AOKP, you can edit it to be faster and better in your desired ways.
Done it and it works the second I raise my phone to my ear when necessary.
Emergency Call from lock screen
Never had a problem GV or the stock phone but the orientation affecting the proximity sensor might explain why I am making emergency calls from the pattern lock screen.. wish there was at least a simple swipe needed to make the emergency call.
naddie said:
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
Click to expand...
Click to collapse
Not fix even on 4.1 ...
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
mrgwap said:
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Same Issue, would love some tips.
bobolinko said:
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Click to expand...
Click to collapse
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Martsmac said:
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Click to expand...
Click to collapse
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
thanks
I appreciate the response , however I'm sure its not dirt on the sensor and that its actually an issue with the software (in this case Cyanogenmod 11 nightly build) not detecting it/initializing it correctly. My reasoning for this is that as soon as I revert back to the stock ROM my issue is gone.
Really hope someone figures this out but for the time being I'm going to have to use a different ROM/stock. Love CyanogenMod though so hopefully it can be resolved soon.
Skipjacks said:
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
Click to expand...
Click to collapse
I have been using my 3a xl for a couple weeks and very happy overall with the speed and performance. I am having one issue trying to overcome that's very disappointing. I do a lot of of walking with my phone in my pocket. When ever I get a call or notification while my phone is in any of my pockets it will either answer it or because it's moving around it will go thru the menus etc. Even if I don't pull my phone out it will always do this. The pocket dial/proximity programming is not good. If you test the prox sensor by covering it up you can open, unlock, make calls etc. with it covered. I am coming from a LeMax 2 and never ever had a single problem with that phone. It had a setting in there and wouldn't allow you to accidently open, unlock, do anything if the sensor was covered. Does anyone have any workarounds for this or insight. I should be able to carry it in my pocket without it doing this. Thanks for any input.
You must have a detective prox sensor or something else is not working correctly with your phone. When I cover my prox sensor (with my hand or in my pocket) the screen does not come on for notifications, calls, or when I tap to wake.
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
retrov said:
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
Click to expand...
Click to collapse
Yes
I just tested my phone today and my screen does wake for incoming calls even when the prox sensor is covered.
This is very annoying.
It does not wake for notifications.
Very annoying for me as well. I guess it's the software program. With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
creeve4 said:
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
Click to expand...
Click to collapse
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
duh1 said:
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
Click to expand...
Click to collapse
It's all open source now. I have not experienced any bugs, it's working really well for me.
Search the magisk repo for Riru - Exposed. I use the sandhook variant. You can find links to more information in the module description.
GravityBox Pie has a thread on XDA.
retrov said:
With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
Click to expand...
Click to collapse
Sounds like an annoying bug to me as well.
Google / Pixel has a bug reporting system...
https://support.google.com/pixelphone/answer/6398243/
If we all submit reports, hopefully they'll take notice and the issue will be fixed in an update...
Just submitted a report on the issue. Thanks
Try the gravity screen app & see if it fixes your issues. I use it & the phone doesn't wake in my pocket for text notifications - but I'm not sure how it will respond to phone calls/notifications; it has options for proximity sensor & a "pocket sensor" feature as well.
retrov said:
Just submitted a report on the issue. Thanks
Click to expand...
Click to collapse
If we want this bug fixed in future updates, everyone should send in a report, especially with Google, squeeky wheel gets their attention...
Anyone that has a pixel 3a 3axl please submit a report on this issue.
My Pixel 3a ja behaving the same way. Coming from a OnePlus 5 with a splendid pocket mode this phone is really getting on my nerves. I love everything about this phone but the constant pocket answering is really bad. Thinking about stop using it...
I've tried every app in Play named pocket mode but nothing seems to work properly.
I've submitted feedback report a couple times hopefully everyone on here can do the same. Won't get fixed until they update on there end. That's the only bad thing I don't like about this phone so far.
Sent.
FYI - for others looking to do this, you file the report under your phone's Settings/About Phone/"Send feedback about this device"
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
acejavelin said:
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
Click to expand...
Click to collapse
Android 10 didn't fix this. I really hate Google right now.
I keep my current N6 phone in a wallet like case with a front cover. Do you guys think that might help?
Hello good day. When I receive a call to my redmi note 8 device, the screen turns black before I bring the phone to my ear. I wake up the device with the help of a button or fingerprint. I am getting information about the sensor setting. but it didn't work. I get a calibrated error message. previously i was using india original update now i am using xiaom.eu stabil 12. i am getting the same error. please help. thanks
I have the same problem. Try installing the latest firmware. It didn't work for me. A quick work around is to quickly cover and uncover the top portion of the phone where the proximity sensor is located (near the selfie camera). The phone screen should come back on. I really wish this would get fixed for the numerous people that have this issue.
tripper22 said:
I have the same problem. Try installing the latest firmware. It didn't work for me. A quick work around is to quickly cover and uncover the top portion of the phone where the proximity sensor is located (near the selfie camera). The phone screen should come back on. I really wish this would get fixed for the numerous people that have this issue.
Click to expand...
Click to collapse
Thank you for your answer. i'm loading other roms. In a few days the problem starts again. So I wonder if there is the same problem with other xiaomi models?
mesut0114 said:
Thank you for your answer. i'm loading other roms. In a few days the problem starts again. So I wonder if there is the same problem with other xiaomi models?
Click to expand...
Click to collapse
I forgot to mention that you shouldn't have any kind of screen protector on your phone when you are trying to figure this out. I don't know about other models. I've had the exact same problem with two different RN8's. It's either a bad batch of proximity / light sensors or it's a firmware / software problem that is yet to be resolved. I have done a full search of this forum and numerous users have the same issue we do. Nobody has a fix as far as I know. Please let me know if you learn anything new.