Related
Hello again everyone! Has anyone else had an issue during calls with the proximity sensor? When I take the phone away frorm my ear the screen does not away come back on.. I have googled it wihtout much luck. Does anyone know any tips to use to recalibrate it on cm11 with a relay 4g? The only thing I found was this link [I can't post links, but google 'calibrate proximity sensor android legend' should be 1st result] but towards the end the *#0*# dialer code used to test it doesnt work so im not sure if the fix will work or not. Since I expect all of you to be using your Relay 4g's as a phone, you guys must have done something. What do you all suggest? Thank you all for your help!!
Dominic
d4dd7wh0 said:
Hello again everyone! Has anyone else had an issue during calls with the proximity sensor? When I take the phone away frorm my ear the screen does not away come back on.. I have googled it wihtout much luck. Does anyone know any tips to use to recalibrate it on cm11 with a relay 4g? The only thing I found was this link [I can't post links, but google 'calibrate proximity sensor android legend' should be 1st result] but towards the end the *#0*# dialer code used to test it doesnt work so im not sure if the fix will work or not. Since I expect all of you to be using your Relay 4g's as a phone, you guys must have done something. What do you all suggest? Thank you all for your help!!
Dominic
Click to expand...
Click to collapse
is it doing it for you in any rom or just one rom in particular?
REV3NT3CH said:
is it doing it for you in any rom or just one rom in particular?
Click to expand...
Click to collapse
CM11-M3 is the only one I've had the issue with.. It's happened during the day, but I spoke to my wife on the phone tonight and outside at night it worked fine. I have been using this rom for 2days so far and i dont make too many phone calls, but its happened roughy half the time..
d4dd7wh0 said:
CM11-M3 is the only one I've had the issue with.. It's happened during the day, but I spoke to my wife on the phone tonight and outside at night it worked fine. I have been using this rom for 2days so far and i dont make too many phone calls, but its happened roughy half the time..
Click to expand...
Click to collapse
ok that ensures its the Rom and not hardware...ill lok into it a bit more but its an issue in hex coding within /system/lib/hw/ and was built with this issue from source....had this issue on my last device and was fixed
Im using PA4.5 with franco kernel (i switched to this kernel because the standard kernel also had this problem
After a while i try to wake up the device with gestures (i always try with gestures first and then with the power button) it just dont turn on the display.
Adb and the home, back and option buttons are lighted up, the cpu is also pushed to different freqs, but the screen keeps empty. I need to force a restart and it boots normally.
I have turned on any gesture.
I couldnt find any to Opo related thread
Edit:
I have installed xposed app settings
Does it happen on other ROMs our only on PA?
Transmitted via Bacon
I didnt test, but isnt there anybody who has the same problem? I love this phone, and PA makes it more awesomer
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
timmaaa said:
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
Click to expand...
Click to collapse
I now flashed cm11 nighly for testing
zephiK said:
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
_Beni_ said:
I now flashed cm11 nighly for testing
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
Click to expand...
Click to collapse
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
_Beni_ said:
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
Click to expand...
Click to collapse
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
zephiK said:
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I dirty flashed CM, in the offical OPO forum smb wrote that uninstalling xposed fixs it.
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
skydayzer said:
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
Click to expand...
Click to collapse
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
_Beni_ said:
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
Click to expand...
Click to collapse
I've used Franco's Kernel upto now with Mahdi-Rom 2.7... And now am running it's kernel and it's working well
Ok i dont want anymore a noname rom, too much change when i switch the phone
EDIT:
nice my bluetooth headset is not working with cm11, lets go back to PA
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
gary93 said:
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
Click to expand...
Click to collapse
Did you update to XNPH33R to see if the problem still occur?
had the issue too, guess it wasnt resolved and i created a jira ticket, you may as well just vote for it now..
Google: jira bacon-736
sorry, but i'm not yet allowed to post outside links!
?
is it a kernel problem?
Q&A for [ROM][CM11.x]mastamoon's unofficial cm11.x
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM11.x]mastamoon's unofficial cm11.x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello, I just rooted my galaxy s3 from metro pcs and I have no signal!!!!
Can someone please help me. I used the the latest rom 10-24-14
CM12
Just installed on my verizon s3. All seems to be working well. Now I get to install all my apps. Thanks for putting this out there Masta
---------- Post added at 01:21 PM ---------- Previous post was at 12:39 PM ----------
swipe does not seem to work yet. home button doesnt bring phone out of sleep
The phone does not react as not to enter the call
Friend I need help my problem is that since 9/16/2014 M10 CM11 can not update my phone because when you upgrade to the latest version of CM11 and now updating your rom CM12, everything works fine wifi, data, text messages, all but the only thing is that I if I can make calls perfectly, but if someone calls me, the phone does not react as not to enter the call, but to put it together on the phone that is calling me hear them (tic, tic, tic) as when you put it near a speaker, meaning that the call reaches the cell, but the cell does not react. I hope someone help me or help me since I can not upgrade my phone.
juankva said:
Friend I need help my problem is that since 9/16/2014 M10 CM11 can not update my phone because when you upgrade to the latest version of CM11 and now updating your rom CM12, everything works fine wifi, data, text messages, all but the only thing is that I if I can make calls perfectly, but if someone calls me, the phone does not react as not to enter the call, but to put it together on the phone that is calling me hear them (tic, tic, tic) as when you put it near a speaker, meaning that the call reaches the cell, but the cell does not react. I hope someone help me or help me since I can not upgrade my phone.
Click to expand...
Click to collapse
If you've installed CM 12 your going to run into bugs on the rom as masta posted on several pages in the actual thread itself that there is and will be bugs
From my CM11 S3
What modem are you on?
sjpritch25 said:
What modem are you on?
Click to expand...
Click to collapse
ML1, been on it for quite awhile and I've never had any issues at all
From my CM11 S3
Weird. I'm on the same baseband & don't have that issue.
ShapesBlue said:
ML1, been on it for quite awhile and I've never had any issues at all
From my CM11 S3
Click to expand...
Click to collapse
I also have a SGS 3, now running Masta's Lollipop CM 12 initial release. I was on the same modem but updated to NE1 one posted by Masta in his thread. It does NOT lock the bootloader. Good luck and post back your results. Have a nanod backup just in case. Gary
Raphael0311 said:
Hello, I just rooted my galaxy s3 from metro pcs and I have no signal!!!!
Can someone please help me. I used the the latest rom 10-24-14
Click to expand...
Click to collapse
try putting a random micro sim card or a regular sim trimmed to fit micro sim in the sim slot, this works for the d2vzw and d2lte roms on the straight talk s3, we were having the same problem with these roms but a sim fixes data for us, maybe it will for you too, doesn't have to be a working or active sim just needs a sim in the slot to connect for some reason, hope this works for you
Sent from my SCH-S968C using Tapatalk
Misc data usage now at 40%, that's a lot higher than it was.
At 30% right now with one hour screen on time.
Pretty bad, haha
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
Misc data usage now at 40%, that's a lot higher than it was.
At 30% right now with one hour screen on time.
Pretty bad, haha
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Tried out the lollipop rom, it was solid until it froze on making calls. Flashed back to my backup of CM11 M12. I'll seriously wait until the bugs are worked out. Spotty calling doesn't make me want to run it at all
From my CM11 S3
Hi Everyone,
I'm still on an old CM10.1 masta build from 7-30-2013 and I'd like to get back into things with these CM12 alpha builds. How should I go about this? I know I need to update my firmware/baseband (still on MF1) as well, but what should be my order?
Recovery - nandroid
Flash - Firmware/baseband
Reboot - to make sure all is well
Back to recovery
Wipe data/cache/factory reset
Flash - rom/gapps/SU
Done?
Then just dirty flash subsequent builds?
Thanks for your help, I've had solid performance from this old rom but looking forward to an update.
Dfuentes said:
Hi Everyone,
I'm still on an old CM10.1 masta build from 7-30-2013 and I'd like to get back into things with these CM12 alpha builds. How should I go about this? I know I need to update my firmware/baseband (still on MF1) as well, but what should be my order?
Recovery - nandroid
Flash - Firmware/baseband
Reboot - to make sure all is well
Back to recovery
Wipe data/cache/factory reset
Flash - rom/gapps/SU
Done?
Then just dirty flash subsequent builds?
Thanks for your help, I've had solid performance from this old rom but looking forward to an update.
Click to expand...
Click to collapse
flash the ROM and Gapps THEN do your wipes, if you don't you might flash the ROM and when you reboot it might be buggy and you might think its the ROM when it might be something left behind from before so do your wipe so you don't run into that; always flash then wipe before reboot, sometimes you can skip that step and flash one over the other without wiping to fix issues in what you are flashing new but that's for experienced people to play around with and doesn't always work, anyway fkash rom and gapps then wipe and reboot
Sent from my SCH-S968C using Tapatalk
Ambient Display
So, this is in regards to the CM12 alphas, and since I don't have 10 posts yet, gotta post here.
Ambient Display was merged, which is pretty sweet, except it seems to randomly display for no reason. I don't have any notifications showing up, so why is it coming up? It can display several times in a minute, or go several minutes too, it seems pretty random. Only thing I can think of is it's picking up subtle vibrations and thinking I've picked it up?
no incoming calls
Anyone else having an issue with no incomming calls? Ive realised since a few months on cm11 i get no incomming calls unless its a private number.. I would love to use cm12 but theres the same issue. Seems to affect people using this phone outside the US like i am. I saw someone mention this in the main thread but im stuck posting here since im a new member :/
Yes my girlfriends phone after i installed cm11 on it. Never did figure it out.
Top and bottom mic swapped in skype and other such apps?!
First off my last no calls issue was solved with this file. i cant post links so maybe search d2gsm_rilblobs.zip
Ever since I've used CM on my S3 i noticed during my skype calls when i hold the phone to my ear the other person doesn't hear me well especially when there's allot of ambient noise!
I soon discovered that when using any app that records audio it uses the top mic only. but in regular phone calls through the network its normal using the bottom mic! Does anyone experience this? i mean it works fine and if u don't pay attention it may not bother you, but as an audio technician i notice these things! u can try if u have skype using the test call talk in the top and then bottom and you'll see the top is louder when its played back.
I went back to stock and the mic worked at the bottom as it should.. maybe there's a fix for this floating around? I have the Verizon S3 but if anyone notices this i would love to know its not just me!!
On masta's CM12 nightlies, I'm having an issue with data between flashes. When I dirty flash a nightly over the previous one, the phone refuses to connect to mobile data, even though everything is apparently fine. Anyone else have this issue?
ajtauro said:
On masta's CM12 nightlies, I'm having an issue with data between flashes. When I dirty flash a nightly over the previous one, the phone refuses to connect to mobile data, even though everything is apparently fine. Anyone else have this issue?
Click to expand...
Click to collapse
You try turning airplane mode off then back on? Make sure your mobile network is set to lte or 3g and not global.
Just got an update. June 1 security update. Fixed my FP sensor issue (had to push, release, then push again to recognize) but once again, auto brightness bug fix has been skipped. Ugh
Fp sensor?
pre4speed said:
Just got an update. June 1 security update. Fixed my FP sensor issue (had to push, release, then push again to recognize) but once again, auto brightness bug fix has been skipped. Ugh
Click to expand...
Click to collapse
My finger print sensor seems to be working better as well. Thanks for posting about the update.
Mikey said:
Fp sensor?
Click to expand...
Click to collapse
Yes, it would not react to single touch. I would have to put my finger, release, and then put back for it to recognize. Now it's single touch like it was in the beginning.
Agreed. I received the update and the fingerprint sensor seems to be working better. The auto-brightness however.... WOW. it's terrible. Slow to react to changes in light, and dims far too much. They should add a way to control the dimming. Something like a percentage of the current profile they have e.g. maintain the max brightness, but if the coding would reduce brightness by 80%, then I would want to select a 50% setting, so the effective reduction in brightness would be only 40%. Trying to read my phone in a store or a restaurant is a royal pain. Who did the real-world testing of this functionality? Some cartoon character that has flashlights for eyeballs?
Anyone having issues sending or receiving MMS after the new update. I can reset my device and is okay for about an hour and then stops sending or receiving MMS messages. I have not wiped with this new update and that is my next step, just wanted to see if anyone else has experienced this by chance.
Sent from my LM-V600 using Tapatalk
pimpmaneaton said:
Anyone having issues sending or receiving MMS after the new update. I can reset my device and is okay for about an hour and then stops sending or receiving MMS messages. I have not wiped with this new update and that is my next step, just wanted to see if anyone else has experienced this by chance.
Click to expand...
Click to collapse
Are you using the private DNS feature? I had this problem and it turned out to be a T-Mobile issue
Ryano89 said:
Are you using the private DNS feature? I had this problem and it turned out to be a T-Mobile issue
Click to expand...
Click to collapse
Interesting, it had been on automatic from the time I got it and never had an issue. I did a reset and got it all set up and turned that off. My wife's phone we just turned that off and her issue has gone away as well. I remember reading about that DNS issue a while ago here, but never thought about it again since I never had an issue. Thanks for the reminder.
Sent from my LM-V600 using Tapatalk
pimpmaneaton said:
Interesting, it had been on automatic from the time I got it and never had an issue. I did a reset and got it all set up and turned that off. My wife's phone we just turned that off and her issue has gone away as well. I remember reading about that DNS issue a while ago here, but never thought about it again since I never had an issue. Thanks for the reminder.
Click to expand...
Click to collapse
It's a huge network flaw that T-Mobile has. You either have to turn private dns off, or use Google messages. Either one solved the problem
Well the update broke the floating bar mod that I had. No longer does the screen record, screenshot edit etc. Only has quick contacts. Anyone else?
I used to be able to video chat with my friend with a S9 phone, after the update , today she tried to video chat with me and she couldn't, I noticed the native Video chat icon is no longer on the contact , it now has the Duo Call instead. Ugh..
Update? My phone still says it's on the April 1st update.
Placebo effect for Fp sensor. Back to having to double touch before its recognized. ?
Anybody on the April 1st security software having 5g connectivity issues? I have been having issues for over a month and a half. Got them to send a new phone after factory reset and new sim didn't work. Got the new phone today and everything was working great until it updated to the April 1st security patch. It hasn't updated to the latest update yet, but I had that update on my previous device and the issue was persistent still even after. So something on that specific software is screwing up my 5G to where I can't use my phone unless I'm on Wi-Fi.
Swizzle82 said:
Anybody on the April 1st security software having 5g connectivity issues? I have been having issues for over a month and a half. Got them to send a new phone after factory reset and new sim didn't work. Got the new phone today and everything was working great until it updated to the April 1st security patch. It hasn't updated to the latest update yet, but I had that update on my previous device and the issue was persistent still even after. So something on that specific software is screwing up my 5G to where I can't use my phone unless I'm on Wi-Fi.
Click to expand...
Click to collapse
I'm in June patch now, but I had no connectivity issues when I was in April. If you turn 5g off do you have data in 4glte?
Ryano89 said:
I'm in June patch now, but I had no connectivity issues when I was in April. If you turn 5g off do you have data in 4glte?
Click to expand...
Click to collapse
That's pretty much where I'm at. I'm having to run with no 5g. They sent me a new phone again, and when it arrives I'm going to try to avoid the update for as long as possible.
Did they pull this update? I got it right away on my first phone but I had to exchange that one and the new one still hasn't received it.
tbxn said:
Did they pull this update? I got it right away on my first phone but I had to exchange that one and the new one still hasn't received it.
Click to expand...
Click to collapse
Possibly, I have it. But it's not listed on the T-Mobile update page.
T-Mobile latest firmware
Does anyone have KDZ file of latest firmware (10R)?
I can not perform OTA update.
Mine would also not pull down the OTA. I had to use LGUP.
Tested via Xiaomi built-in QC, Look at mark 0:15, the number stays 0 after I removed my hand from the sensor.
Another user on reddit is facing similar issue.
https://www.reddit.com/r/PocoX3/comments/m43121
There are a lot of people who are facing this issue with the Poco NFC. There are usually 3 problems and you need to try all of them.
1: Hardware issue : Cannot be fixed in software and requires device replacement in warranty.
2: Screen Guard that's dirty or too large covering the sensor area.
3: A bug in the software that can be fixed with a factory reset.
The proximity sensor is located on the top left of the camera punch hole near the LED light. So make sure nothing is clogged in that area or the screen guard is not scratched or covering that area. You will be able to see the sensor if it's working if you make a call and point another camera at it and notice a blinking light. I'm hoping it's just dirt or debris and that you don't have to get a device replacement.
Me having exactly same issue. Screen doesn't turn off during calls when I put my face near or touch the sensor.
****ty thing else
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via fastboot the previous one and stay with it or go to custom rom (with 12.0.7.0 or older firmware/vendor)
fonz93 said:
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via fastboot the previous one and stay with it or go to custom rom (with 12.0.7.0 or older firmware/vendor)
Click to expand...
Click to collapse
Good to know, but I'll wait for the next update and hopefully they will fix it.
fonz93 said:
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via
Click to expand...
Click to collapse
MrPotatoBall said:
Good
Click to expand...
Click to collapse
Pocopoñy said:
Me having exactly same issue. Screen doesn't turn off during calls when I put my face near or touch the sensor.
****ty thing else
Click to expand...
Click to collapse
MrPotatoBall said:
Good to know, but I'll wait for the next update and hopefully they will fix it.
Click to expand...
Click to collapse
Okay I don't understand this new XDA reply thing... But if you guys figure out the particular trigger in the MIUI software please let me know.
What is this new complex reply system?
I can't even cancel it. Even if I clear data of the browser and log in it brings me back to this complex stacked reply system. Can anyone explain?
Anyone managed to find a solution?
Recalibrate proximity sensor.
1. open settings
2. click all specs
3. click Kernel Version 3 milion times
4. CIT menu will open.
5. click three dots top right corner
6. click additional tools
7. select option nr.10 proximity sensor
8. click calibrate.
9 go back to CIT
10. Select option nr. 15 proximity sensor to test
tuncay_93 said:
Recalibrate proximity sensor.
1. open settings
2. click all specs
3. click Kernel Version 3 milion times
4. CIT menu will open.
5. click three dots top right corner
6. click additional tools
7. select option nr.10 proximity sensor
8. click calibrate.
9 go back to CIT
10. Select option nr. 15 proximity sensor to test
Click to expand...
Click to collapse
Still doesn't work after calibrated.
RMA your device.
You have a faulty sensor.
Alrich said:
RMA your device.
You have a faulty sensor.
Click to expand...
Click to collapse
Nope, it's software issue. Many Xiaomi phone have the same problem.
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Alrich said:
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Click to expand...
Click to collapse
why should it be an hardware issue when it's clear that the bug came with a software update? so we all have a faulty proximity sensor? it's full of people having this problem... we just downgraded to 12.0.7.0 firmware and all it's solved, custom rom it's not the solution, downgrading the firmware is... then you can do what you want (installing a custom rom too)
Alrich said:
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Click to expand...
Click to collapse
Yes, I'm CONFIDENT to say it is a "software" problem.
You obviously didn't even follow this thread.
fonz93 said:
why should it be an hardware issue when it's clear that the bug came with a software update? so we all have a faulty proximity sensor? it's full of people having this problem... we just downgraded to 12.0.7.0 firmware and all it's solved, custom rom it's not the solution, downgrading the firmware is... then you can do what you want (installing a custom rom too)
Click to expand...
Click to collapse
Well said.
There is a new update available, 12.0.8.0 Android 11 seems to fix the proximity sensor problem.
MrPotatoBall said:
There is a new update available, 12.0.8.0 Android 11 seems to fix the proximity sensor problem.
Click to expand...
Click to collapse
Yes it does, but android 11 seems to be pretty buggy/laggy at the moment...
Had this problem but for me it was the screen protector messing with the sensors i had a better one and its solved
fonz93 said:
Yes it does, but android 11 seems to be pretty buggy/laggy at the moment...
Click to expand...
Click to collapse
Android 11 is perfectly fine. MIUI is buggy