Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
bzadi said:
Hello everyone!
So my problem started a few weeks ago when i flashed ABC Rom on my MiMix2, the proximity sensor, in calls, started to not work after a time, but it was a gradual process, until it didn't work at all. So a few days ago i decided to try and solve the problem. I've read in different places that it could be the persist partition, that holds the drivers for the sensor.
I have tried flashing the persist.img with fastboot from the original xiaomi site, but it kept telling me the partition is write protected. Tried with adb but then i couldn't mount the partition. In the end i ended up reflashing the original image with MIUI Flashing Tool, modifying the image to flash the persist image, with no positive results, except i could mount the partition again. I then looked in the persist.img file to find out it is empty, all of them that i could find are almost empty(some empty folders).
I fount a thread on XDA with some sensor files for my phone that i had to copy in my root/sensors directory, so i did and nothing changed.
The weird thing is that after all of this, when i enter the calibration app that that MIUI has and hold my hand on the sensor sometimes it detects my hand.
Sooo.... after all of this is my problem a software one or a hardware one (if its a hardware one, its a strage one, because the sensor works but its just weak).
Can anyone help me with some answers please. Thanks and sorry for the long post.
Click to expand...
Click to collapse
Probably the custom ROM causing the issue
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
I've got the exact same problem, now proximity sensor doesn't work at all
bzadi said:
This is what i assumed at first, but i flashed the original xiaomi image with their tool, and still the same behavior. This problem now persists on all the roms i flash.
Click to expand...
Click to collapse
Nvjoel said:
I've got the exact same problem, now proximity sensor doesn't work at all
Click to expand...
Click to collapse
Do you have any kind of screen protection?
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
Nope, no screen protector, no case.
XDRdaniel said:
Do you have any kind of screen protection?
Click to expand...
Click to collapse
No case and no screen protection.
Related
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
Hello everyone
I would like to ask. So i have Mi 6 128GB variant and right now I'm having problem with the (i think) microphone. So the problem is when i place a call, the other side can't hear me, also when i try to record something the voice result will be so small, and i have to speak from a very close distance. And when using ok google i also have to speak from a very close distance. It seems the problem is not in the hardware. I bought it about a month ago, and when i just bought it i tried to flash to unofficial LOS ROM, the first one that appeared is the calling problem. So i tried to flash different kind of custom ROM, mostly LOS (because there are several version from different developer) and AOSP Extended. All is same, the microphone seems not functioning properly. And at one point i try to go back to MIUI 8.2.2.0. At that time i notice the phone displaying the message that the IMEI is lost. So i tried different kind of way to restore the IMEI mostly through flashing qcn. Right now the IMEI is back, but it's not my original IMEI, when i restore my original IMEI, the MEID is different from the original one, because i use qcn fthat i obtained from web, so maybe the MEID from the original qcn still intact. So right now i tried to flash the unedited qcn to see whether the problem is solved. But it's still same.
Any help will be really appreciated
Hi ,i have this problem with the mic also the solution is to install a new rom with full format ,and NOT active the google assistant,thats what make the problem for me.
good luck
hac12 said:
Hi ,i have this problem with the mic also the solution is to install a new rom with full format ,and NOT active the google assistant,thats what make the problem for me.
good luck
Click to expand...
Click to collapse
Hi bro, by full format do u mean the "format data" option in TWRP?
fuqiangyang said:
Hi bro, by full format do u mean the "format data" option in TWRP?
Click to expand...
Click to collapse
hi, yes thats right,
sorry for the late answer
hac12 said:
hi, yes thats right,
sorry for the late answer
Click to expand...
Click to collapse
Thanks bro, but i just realized that the real problem is the sticker that covering the mic holes! So there was a kind of warranty sticker that is stick to the phone and covered almost all the mic holes, and when i removed it the mic is going back to normal...I never thought the is the issue, lol
Should i delete this thread?
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.
Hi i have PixelUI_13.0 rom on my redmi note 8t, i have a problem, the accellerometer, orientation, temperature, gyroscope sensors doesn't work.
I've tryed to flash persist.img from the stock rom (willow_global_image_V12.5.6.0) but the problem is not solved.
Any help?
P.S: please don't tell me i need to reflash stock rom and the custom another one time.
Luigi2201 said:
Hi i have PixelUI_13.0 rom on my redmi note 8t, i have a problem, the accellerometer, orientation, temperature, gyroscope sensors doesn't work.
I've tryed to flash persist.img from the stock rom (willow_global_image_V12.5.6.0) but the problem is not solved.
Any help?
P.S: please don't tell me i need to reflash stock rom and the custom another one time.
Click to expand...
Click to collapse
Didn't you format persist by any chance unintentionally?
*Edit: Didn't see the next line. Are you sure the reflash was successful? My persist partition was also damaged somehow and had to reflash like 3 times. After that suddenly all sensors came back.
Yeah, the reflash didn't give me errors
Luigi2201 said:
Yeah, the reflash didn't give me errors
Click to expand...
Click to collapse
Were you able to solve? I have a similar problem. None of the sensors work, including the proximity sensor. Which file can be corrupted ?
Luigi2201 said:
Yeah, the reflash didn't give me errors
Click to expand...
Click to collapse
SOLVED.
The main problem was Persist.img