This is for Samsung Omnia 7 if you have used the Diag app/code to mess about with the settings. I had screwed my rotation by changing some settings. Tried a reset via code but that didn't work. In the end I used code *#2580# to enter integrity control and ensured it was at '1' (on), then use code *#0*# to enter LCD test, lay the phone flat and press the 'CAL' button. It returned 'true' and now my accelerometer works again.
Hope this is actually a fix and it helps someone out. I have noticed a few people lost the rotation on their Omnia 7's. This will probably work for Samsung Focus too. If this does fix your problem let us all know so this can help others too.
Yep - that CAL is calibrate, I imagine. You can also do it with the "Level" application from Microsoft (spirit level thing) if you don't fancy the diag codes.
Diagnostics / Accelerometer (+ fix)
Yes, if you play around in the diagnostics - BE CAREFUL!
To enter diagnostics on your Samsung (confirmed for Omnia 7) enter ##634# and press "call"
Then type the following for the following services:
*#0*# Various diagnostic settings incl accelerometer, compass, screen colour
*#2*# Detailed battery info (incl. charge to nearest 1%)
*#3*# Screen brightness
Be carefull if you choose to calebrate the accelerometer as it will muck up your auto rotation if the phone is incorrectly positioned.
To reset the rotation do the following:
- Ensure the yellow flowers picture is upright (aligned with the flowers towards the top of the phone)
- Lay the phone down on a true horizontal flat surface (XYZ values do not matter for this) ensuring the flowers remain upright
- Touch the "Cal" button. If you get "True Return" you have reset. If "false", try again in slightly different positions until it works.
wt7881 said:
Yes, if you play around in the diagnostics - BE CAREFUL!
To enter diagnostics on your Samsung (confirmed for Omnia 7) enter ##634# and press "call"
Then type the following for the following services:
*#0*# Various diagnostic settings incl accelerometer, compass, screen colour
*#2*# Detailed battery info (incl. charge to nearest 1%)
*#3*# Screen brightness
Be carefull if you choose to calebrate the accelerometer as it will muck up your auto rotation if the phone is incorrectly positioned.
To reset the rotation do the following:
- Ensure the yellow flowers picture is upright (aligned with the flowers towards the top of the phone)
- Lay the phone down on a true horizontal flat surface (XYZ values do not matter for this) ensuring the flowers remain upright
- Touch the "Cal" button. If you get "True Return" you have reset. If "false", try again in slightly different positions until it works.
Click to expand...
Click to collapse
Thank you !
I am currently experience another issue since I launched that app.
The start button doesn't turn on the display anymore,
maybe I'm getting crazy but I think holding that button was indeed turning the display on.
Actually I did miss my calibration but thanks to your help, I fixed,
do you think the Start button issue could be related to that tool as well ?
Thank you
Would this solve the slow auto rotation of the UI?
I had the HD7 and the auto rotation on the Omnia seems to damn slower and less responive than it was on the HD7
aybe0 said:
Thank you !
I am currently experience another issue since I launched that app.
The start button doesn't turn on the display anymore,
maybe I'm getting crazy but I think holding that button was indeed turning the display on.
Actually I did miss my calibration but thanks to your help, I fixed,
do you think the Start button issue could be related to that tool as well ?
Thank you
Click to expand...
Click to collapse
I have the exact same problem for a few days now, don't remember what could have been the setting for it.
Start button doesn't turn on the display anymore. I want that back! How can I get the start button to default?
Thx.
I have just reset my phone to factory defaults : Parameters, About, Reset ...
Notice that resetting will erase everything, I've lost my IE favorites by the way ...
Everything is back, Start button as well ...
In fact I did play too much with the settings, it was turning the screen off
as soon as I was making a call, the only way to turn it back on was the called one to end the call ...
Tried to fix (lol) proximity and lights settings but nothing ...
I think I'll just leave the Diagnostics app. for now, too dangerous
there seems to be an option to do that as well from the app.
But will it erase your data ? I don't know ...
aybe0 said:
I have just reset my phone to factory defaults : Parameters, About, Reset ...
Notice that resetting will erase everything, I've lost my IE favorites by the way ...
Everything is back, Start button as well ...
In fact I did play too much with the settings, it was turning the screen off
as soon as I was making a call, the only way to turn it back on was the called one to end the call ...
Tried to fix (lol) proximity and lights settings but nothing ...
I think I'll just leave the Diagnostics app. for now, too dangerous
there seems to be an option to do that as well from the app.
But will it erase your data ? I don't know ...
Click to expand...
Click to collapse
My proximity sensor went crazy too. The fix is to go to diagnostics mode (google for it) and register a bit larger proximity value as a default. I used my hand to block the sensor. On my phone the absolute minimum seemed to be 3, which made the phone unusable. Something in the range of 10-20 seemed to be the most useful compromise. You may need to experiment a bit to get a suitable value. This way you don't have to reset the entire phone.
I still wonder what the default proximity value is... if anyone knows, please reply.
I have Samsung Focus 1.3 Mango 7720, but i don't see "cal" in the settings of the Proximity?
can you help?
Thanks
I have an Omnia 7 and my problem is that when I make/receive and calls, the screen goes black and stops me from pressing anything (meaning I cannot end calls). I have to take the battery out to try and reset it. This is beacuse of the proximity sensor settings and in the past I have used the field testing tools (*#9908# in diagnosis) to adjust the proximity sensor and set it to 20 or 30 which did the job. However I need to do this again as I had reseted the phone. Now when I go into field testing, the set option isn't there. Is there any way to adjust the proximity sensor?
Can anyone offer any help? I have diagnosis ver.0628 which allowed me to adjust the proximity sensor before.
mebula999 said:
Can anyone offer any help? I have diagnosis ver.0628 which allowed me to adjust the proximity sensor before.
Click to expand...
Click to collapse
i have the latest t-mobile MANGO ROM it has the same diagnosis app ver.0628. which ROM you have now? normaly you can load a new diagnosi app over phone dailer and ##634#? + dail
if not you will flash your device new ...........
here my nice guide
[GUIDE] Unlock/InternetSharing/Backup your OMNIA 7
The reason why i get the black screen problem is that the corner of the screen with the proximity sensor is a little loose (because i repaired the screen). As a result the default value is 14. What I managed to do is find an old nodo backup I had made annd flashed that. I was then able to install and older version of diagnosis which allowed me to set the proximity sensor value. Then I reupdated to Mango. So the problem is fixed for now but for future formats, is there any way to extract the diagnosis app?
http://forum.xda-developers.com/attachment.php?attachmentid=783826&d=1321392331
here a older diagnosis.xap - you need a unlocked phone to deploy this xap. good luck
i have same problem too.
i have try this older version of diagnosis. but i don't know which code is going promixty set menu. if *#9902# its going gprs setting menu.
more older diagnosis xap. ? or any new code for set promixty sensor
I´ve searched this forum, but found nothing like what I am facing. As per title, whilst on a call, with the phone on my ear (left ear usually, if that means anything) the on screen buttons are pressed, because I usually end up with the call on hold. Other times, it finishes the call, other times it dials a number from the contact list...Here´s a list of what I have done so far with no success:
1. Calibrate proximity sensor with apps
2. Use hidden menu to test functionality (it works as advertised)
3. Calibrate motion sensor
4. Full reset of the phone
5. Clear dalvik cache
6. Test sensor functionality with app (again, works as it should). It detects when my hand is covering the sensor and it detects when my hand is taken away from it. Instantly. Also, left my hand covering the sensor for a while (simulating a call) to see if at some point it stopped working, but no, the darned thing worked as it should.
I read somewhere here that a mod on build.prop might help (it has to do with the delay time of the proximity sensor) but since the post didn´t explain the exact setting, i googled it, and found 2 settings that might apply:
1.) ro.lge.proximity.delay
2.) mot.proximity.delay.
Neither of them is in my build.prop file, so, the questions that pop to my mind are:
1.)Which one of the two would affect the described issue? Apparently those settings are modified by users that had a problem with black screens after a call or with long delays for the screen to come back after taking the phone from their ears to use the keypad, but no post that I read indicated which one of the settings influenced what. I have the feeling that one of them is for the proximity sensor to "kick in" while the other controls how long does it take for the screen to come back after the proximity sensor stops detecting your ear.
2.)Can I add that setting to my build.prop without risking a bootlop or a brick?
As the title say, I have a D800, with official AT&T 5.0.2 ROM, rooted, with stock recovery.
Any help would be highly appreciated. As you can imagine is terribly frustrating that I cannot use my smartPHONE as a PHONE because of this!
Thanks in advance!
Frank.
a small, shameless bump!
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.
stanley56 said:
In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.
Click to expand...
Click to collapse
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?
Fortis10 said:
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?
Click to expand...
Click to collapse
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.
DelphinusMinor said:
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.
Click to expand...
Click to collapse
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
I can't help there but left/right holding is an issue I guess with this phone. Or maybe it's the Pro. I forget offhand.
Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.
Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.
jonathan_jon said:
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.
Click to expand...
Click to collapse
Is the EU rom that better?
I mean is there any plane to compare the known issues between the global and EU ?
I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.
hi @All!
is there still no permanent solution for fixing proximity bug?
its really annoying and making me crazy....
even after making it working again using quicktune app - doing one call it is broken again
fasty said:
I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.
Click to expand...
Click to collapse
Exactly what i've experienced.
Super annoying when you accidentally hang up during a call.
It happend countless times so far.
I'm on eu beta btw.
Wish there would be a solution.. . But afaik proximity is even more bugged in non miui custom roms.
I had this problem to. my proximity sensor what not responding at all. I thought it was defective because the calibration was not working to.
Then i went to the system update settings, downloaded the latest package and flashed it. After reflashing it started working with no problem at all.
Factory reset did the trick for me. Working normally now.
Install Quick Tuneup. Then do Sensor Celebration & Restart your device twice.
Two solutions
Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
It turns out that the problem is because MIUI does not activate the proximity sensor when the smartphone is turning on.
To force MIUI to ALWAYS activate the sensor at each start, we can do two things:
1- Always have "Automatic brightness" activated
2- Activate the "Pocket mode" (the best choice)
After applying one of these situations, it is necessary to restart the phone.
Only by activating the pocket mode it is no longer necessary to have automatic brightness activated all the time.
In the video I show how to activate the "pocket mode"
w w w . youtube.com/watch?v=2dfrqmH02O8
I published this solution in a forum in my country (Colombia).
w w w . laneros.com/temas/soluci%C3%B3n-sensor-de-proximidad-xiaomi.239997
I don't speak English, I had to use the google translator, sorry for any translation error.
2- Activate the "Pocket mode" (the best choice)
After applying one of these situations said:
KMILO_PARRA is a KING .........................
above is proof to SOLVE the Proximity Sensor no reaction in my Redmi Note 7.
I was having lots of TASKER Profile depending on whether or not Proximity Sensor is covered.
I found all those Profiles no more function due to the issue after I believe OTA to Global rom the latest ( August-2019 )
Thanks again to KMILO_PARRA
Click to expand...
Click to collapse
Actually, the proximity sensor for Redmi Note 7 isn't in the "usual" top-center position, it's a little bit on the top-right edge (if you watch the phone "against the light" you can actually see a small dot on that side).
If you're calling\responding try to put your ear at that angle, you'll never have those problem anymore.
I know it seems crazy, and of course the first times could be "unusual" to put the ear there, but it actually worked out flawlessly for me.
Mr
Quaresma_7 said:
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.
Click to expand...
Click to collapse
Thanks.....
It works for me
Hi guys,
I have made a little workaround, using the suggestion of @KMILO_PARRA user. (pocket)
https://taskerprofilecenter.blogspot.com/2019/09/project-proximity-sensor-workaround-for.html
This is mainly for Tasker users, but I have generated an APK to be installed too. So any user can use it. But what is needed, by now, is root, as it needs to write to Settings table.
Please, report me back if it does the job or not.
Note1: For those users that don't know how Tasker works, just install the app, and give it root permissions, and allow Write System Settings permission (Android option). I recommend you to not set it as an app to be killed from the OS using the battery optimization, as it could be killed. It acts on every shutdown and device boot.
Note2: It will generate two permanent notifications: Place holder, and the one that is the mini-Tasker code monitor (required). Just, disable the Place holder one, as described in the same notification (click on it), and disable notifications completely for the installed app to get rid of the last one.
---------- Post added at 12:44 AM ---------- Previous post was at 12:31 AM ----------
What it does exactly?
Well, as I explained on my web, it just changes the value (0/1) from the 'enable_screen_on_proximity_sensor' Global Settings table, that makes the pocket option to be toggleable in an automated way.
So, be sure not to use that option as a daily one, as the project/app uses it to allow the sensor be available at startup. And do not forget that you will need root too! Sorry.
What to download if I don't know what Tasker is?
You will only have to download the APK from the 'Kid App (APK)' link, provided under the 'DOWNLOAD' section. Nothing else.
If you know Tasker, you will know what to do.
Does it work really?
I'm currently testing this workaround, but as I could see, at least on my device (lavender too), seems to be working as expected. But needs to be tested a little more.
So, if it does not what it's intented for, please, report it me back.
After installing the app, giving root permissions, and allow it to modify system settings, reboot the device to take it effect.
Solution in post #4.
I have a H872. I had been running Havoc OS v3.1 10/01/2020 without any issues. This past weekend I decided to update to Havoc OS v3.4 21/04/2020 (clean flash) and everything was great until I realized that the proximity sensor wasn’t working. When I received a call the screen stayed black. Swiping down from the notification bar let me answer the call but the proximity sensor didn't work - screen stayed black. I couldn't even hang up - had to wait for the other caller to hang up. Same issue when I initiated the call.
I then tried Havoc OS v3.4 18/04/2020 (clean flash again) and the same calling/proximity sensor issue remained PLUS I could not send/receive MMS even though APN was set up exactly the same as my original configuration (I had taken screenshots of my original setup). I attempted Havoc OS v3.4 21/04/2020 once again and MMS stopped working too! As well as the proximity sensor issue.
I then restored my original nandroid of Havoc OS v3.1 10/01/2020. While it restored successfully in TWRP, it never booted into the system. It just hung on the last frame of the boot animation. I am at a complete loss as to how to fix this phone now. I have just installed MSM Xtended and the proximity sensor is still non-functioning. I have since switched my sim to my Xiaomi backup but really want to get back to my G6.
It worked perfectly…I attempted a simple upgrade and all hell has broken loose! Any tips? Please.
Update:
I completely restored the phone to stock with H872 20g kdz/LGUP and was able to send MMS but the proximity sensor was still not functioning. Can the sensor just suddenly go bad like that? It was working perfectly until I updated Havoc.
Anyway, I have re-rooted and reinstalled the latest havoc. I am hopeful that I will get MMS to work, however, am not sure the proximity sensor will. I have found here that Android 10 allows for all sensors to be disabled with a Quick Settings Tile. This would work for when I initiate a call (can use the power button to turn the screen off/on). But would not be able to activate it once a call comes in. Is there a way to automate the sensor to turn on/off automatically when a call comes in? Or better yet, just disable the proximity sensor, and only the proximity sensor, completely? Been Googling all morning but haven't found much aside from this toggle, and an Xposed mod that may not even work with Riru Xposed...not to mention I want to avoid Xposed if I can.
Still looking for advice if you have any.
Thanks!
Update 2:
I am now running the latest Havoc with working MMS but still the proximity sensor issue persists. I am getting around it by using the Quick Settings Tile/toggle that is activated in Developer Options. This turns off the proximity sensor, as well as compass, accelerometer, & gyroscope. So I have to remember to disable it after a call.
I have searched to no end for a way to disable the proximity sensor permanently but there is very little on the subject. I've tried some apps that claim to turn it off, but they have not worked for me. It seems to me it should be an easy thing to do...but no!
My request:
Someone that can explain how to disable the proximity sensor on Havoc, or someone that could maybe recompile the dialer.apk to not utilize the proximity sensor.
Thanks again!
Final update: Solved!
I decided to install EdXposed and Sensor Disabler. After a lot of experimenting I found settings that work. In Sensor Disabler I selected:
LGE Virtual Proximity Sensor & selected "Remove Sensor" and Saved
Proximity (There are 2 listed - I set both the same) & selected Mock Sensor Values & set them to the highest setting possible and Saved.
Now I can make & receive calls and have access to the Accept/Reject/Message functions, as well as the keypad to input if needed and can end calls. The power button is easily accessible on the back and turns the screen off & on during a call, so I can keep it off the whole time I'm talking.
Not the most ideal situation but works for me considering the proximity sensor is completely useless now. Hope this helps anyone else in the same predicament.
EDIT - Sensor Disabler doesn't appear to be the most reliable. After a reboot it's hit or miss if it will work. It seems that after rebooting it takes a couple minutes for the app to "kick" in and function...but then it only seems to work more for incoming calls. Ultimately I am still using the Quick Settings tile to turn off all sensors during calls.