Just got my Galaxy S3 a few days ago and today when I answered a call the screen immediately went blank and I could not turn it back on until the caller hung up. I've had other calls prior to today and cannot recall if the phone behaved the same way. I've been searching for a solution and everything points to a faulty proximity sensor. I've worked around the problem by disabling "Auto screen off during calls" under "Call settings". This works but it's not perfect since if I forget to manually turn off the screen I'm likely to press buttons with my face.
Under *#0*# -> Sensor -> Proximity Sensor: The PROXIMITY always reads 1.0. The ADC field increases as I get closer to the proximity sensor but never drops below 1 (should it?). Are PROXIMITY and ADC both readings from the same sensor?
Under *#7353# -> Proximity Sensor: It always says "Working" and vibrates. From the other tests in this menu I assume this is the "On" state and that the correct behavior would be to not vibrate and display a different message when the sensor is "Off" (ie: nothing is close to the sensor).
Several test apps (Android Sensor Box, Proximity Sensor, Sensor Test) also report 0cm or something similar indicating that something is close to the sensor.
Thanks in advance for any help :good:
machx0r said:
Just got my Galaxy S3 a few days ago and today when I answered a call the screen immediately went blank and I could not turn it back on until the caller hung up. I've had other calls prior to today and cannot recall if the phone behaved the same way. I've been searching for a solution and everything points to a faulty proximity sensor. I've worked around the problem by disabling "Auto screen off during calls" under "Call settings". This works but it's not perfect since if I forget to manually turn off the screen I'm likely to press buttons with my face.
Under *#0*# -> Sensor -> Proximity Sensor: The PROXIMITY always reads 1.0. The ADC field increases as I get closer to the proximity sensor but never drops below 1 (should it?). Are PROXIMITY and ADC both readings from the same sensor?
Under *#7353# -> Proximity Sensor: It always says "Working" and vibrates. From the other tests in this menu I assume this is the "On" state and that the correct behavior would be to not vibrate and display a different message when the sensor is "Off" (ie: nothing is close to the sensor).
Several test apps (Android Sensor Box, Proximity Sensor, Sensor Test) also report 0cm or something similar indicating that something is close to the sensor.
Thanks in advance for any help :good:
Click to expand...
Click to collapse
This may be a stupid question, but do you have a case that might be covering the proxy sensor? I'm also assuming you have cleaned the area where the sensor is. Other than that you might be able to take the phone into the Sprint store and get it replaced. If they won't take it back, call up Samsung customer service. If it's a faulty sensor, they might replace the phone free of charge (others have had good experiences with Samsung customer support)
Hope you get it fixed!
topherk said:
This may be a stupid question, but do you have a case that might be covering the proxy sensor? I'm also assuming you have cleaned the area where the sensor is. Other than that you might be able to take the phone into the Sprint store and get it replaced. If they won't take it back, call up Samsung customer service. If it's a faulty sensor, they might replace the phone free of charge (others have had good experiences with Samsung customer support)
Hope you get it fixed!
Click to expand...
Click to collapse
Thanks for the response. No screen protector or case. I did clean the entire screen this morning and the behavior didn't change. Was hoping I wouldn't have to take the phone back but then again if this was a common problem with a simple solution my searching this morning probably would have turned up an answer
machx0r said:
Thanks for the response. No screen protector or case. I did clean the entire screen this morning and the behavior didn't change. Was hoping I wouldn't have to take the phone back but then again if this was a common problem with a simple solution my searching this morning probably would have turned up an answer
Click to expand...
Click to collapse
Lol yeah, this is the first time I've seen anything about this, and I respond to literally almost every thread, or at least read through each one. But like topherk said, its probably a hardware issue. Would you be able to check to see if the "1.0" value is present on another S3? Maybe its a default of some kind (i would check myself, but my S3 took a 4 story dive recently and is out of service)
CNexus said:
Lol yeah, this is the first time I've seen anything about this, and I respond to literally almost every thread, or at least read through each one. But like topherk said, its probably a hardware issue. Would you be able to check to see if the "1.0" value is present on another S3? Maybe its a default of some kind (i would check myself, but my S3 took a 4 story dive recently and is out of service)
Click to expand...
Click to collapse
I don't know anyone else with an S3 but if anyone wants to check their *#0*# -> Sensor screen and tell me what the PROXIMITY and ADC values are when you aren't close to the sensor I'd appreciate it. Maybe I'll hit up the Sprint store and test it on a display model :laugh:
That said the page I discovered the *#0*# menu on has a screenshot and the PROXIMITY is showing 0.0 (I assume he's away from the sensor):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where as this is mine when I'm away from the sensor:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
machx0r said:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
Click to expand...
Click to collapse
Have you ever installed a flip cover app?
Sent from my SPH-L710 using xda premium
xblackvalorx said:
Have you ever installed a flip cover app?
Click to expand...
Click to collapse
No, pretty standard apps installed and nothing specific to motion or proximity (aside from the handful of test apps I've installed to see what the proximity sensor readings are).
machx0r said:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
Click to expand...
Click to collapse
Interesting...
Lol, i would recommend going to the Sprint store (if its not a hassle) and testing it out with their S3 on display, surefire way of knowing if something got borked with yours
I dont know whether they would charge for this or not, hopefully they dont, but you could also ask the reps to check it over for you and say you've been having some weird behavior with your incoming calls and the screen on/off events
machx0r said:
I don't know anyone else with an S3 but if anyone wants to check their *#0*# -> Sensor screen and tell me what the PROXIMITY and ADC values are when you aren't close to the sensor I'd appreciate it. Maybe I'll hit up the Sprint store and test it on a display model :laugh:
That said the page I discovered the *#0*# menu on has a screenshot and the PROXIMITY is showing 0.0 (I assume he's away from the sensor):
Where as this is mine when I'm away from the sensor:
Click to expand...
Click to collapse
Exactly what's been happening with my Samsung Galaxy Note 2 running stock firmware (rooted) with no screen protector. Been searching the internet for months and tried several proximity screen off apps to no avails. After countless tests and trials I am convinced that the proximity sensor when activated is stuck "near" (PROXIMIY = 1.0 at ADC level <= 12) unless there is bright enough ambient light. If some gurus could shade some lights on how to set the proximity threshold "prox_thresh" to be greater than 12 (say 30) (and that setting will stick after restart) that would be great!
I have the same problem with my brand new TMobile Galaxy Note 2 where proximity sensor does require a lot of ambient light in order to switch the screen on and off during the call. I noticed that the screen protector is part of the problem so I removed it and it helped a bit but not always. I was afraid the sensor is broken itself and requested for replacement phone however I tried the *#0*# combination to test the sensor and found that ADC (analog to digital converter) output changes as I approach the sensor. With no proximity ADC shows value of between 11 and 15 and it is increasing smoothly to 140 as I move closer and furthermore reaches 190 as I press my finger against the screen. So the proximity sensor hardware actually works just fine it is the software layer including driver that possibly creates a problem which results in Proximity value being always equal 1.0 despite of ADC output precisely following the actual proximity. Several applications available call play market follows the Proximity value therefore making sensor based ofperation difficult or useless. I hope that upcoming system update will address the flaw making sensor based functions to work finally as they should.
Sent from my SGH-T889 using Tapatalk 2
Galaxy S3 proximity sensor replacement
Same issue here. A few things that may be of interest. My issue did not start after an update, it just started happening out of the blue. It is not because of being dirty or a because of a case. When I get into the diagnostic screen, the proximity sensor reads 0 and then goes to 1 when you get in proximity. It then stays at 1 and won't go back to 0. The ADA changes values, apparently correctly. The one thing that I thought was interesting, if I flash a bright LED flashlight on it, it does go back to zero. It is almost like it is not as sensitive to light all the sudden. This light trick works no matter how far away the light is. I am thinking the sensor is going bad.
I see several options to replace it on eBay, I changed out the screen last year, so I know how to change out the front camera and sensor. The only OEM ones I see are used or from China. Has anyone ever tried any of these, OEM or otherwise? They are cheap, I think I will give it a shot.
SOLVED
Just a heads up, I fixed my problem with a new front facing camera and sensor off of ebay. It took less than 10 minutes to put it in and it works great now. It was $5.99 shipped.
try this
esdwa said:
I have the same problem with my brand new TMobile Galaxy Note 2 where proximity sensor does require a lot of ambient light in order to switch the screen on and off during the call. I noticed that the screen protector is part of the problem so I removed it and it helped a bit but not always. I was afraid the sensor is broken itself and requested for replacement phone however I tried the *#0*# combination to test the sensor and found that ADC (analog to digital converter) output changes as I approach the sensor. With no proximity ADC shows value of between 11 and 15 and it is increasing smoothly to 140 as I move closer and furthermore reaches 190 as I press my finger against the screen. So the proximity sensor hardware actually works just fine it is the software layer including driver that possibly creates a problem which results in Proximity value being always equal 1.0 despite of ADC output precisely following the actual proximity. Several applications available call play market follows the Proximity value therefore making sensor based ofperation difficult or useless. I hope that upcoming system update will address the flaw making sensor based functions to work finally as they should.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
I can now stop pulling out my hair...
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
Worked like a charm! Original values were evidently not properly calibrated, but the above approach reset the values such that the display now switches off (in phone calls) at approximately 8 cm, and following hang up, immediately powers on.
Thank you
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
sea2summit said:
Worked like a charm! Original values were evidently not properly calibrated, but the above approach reset the values such that the display now switches off (in phone calls) at approximately 8 cm, and following hang up, immediately powers on.
Thank you
Click to expand...
Click to collapse
God, i've been looking for that information for dozens of years (felt this way at least).
And i find it the day i put my phone back to stock for an RMA !
I went back to root, and tried those lines in the ROM Toolbox Pro's terminal, it says " can't create /sys/class etc. permission denied", what's wrong please guyz ?? I tried several ways to re root, root checker says "status : rooted, ID : uid=0(root) gid=0(root), SuperUser (can't find), BusyBox : /system/xbin/busybox, Su : /system/xbin/su => maybe that's the issue, am i badly rooted ?
Isn't there a no root solution, a very simple way to calibrate ? While looking for a solution, I heard about Als-Ps calibration, doesn't it exist on the N7100 ?
Any help would be very appreciated.
EDIT : OK, i typed "su" to get the terminal to get the SU request, and typed the command, rebooted the phone : the issue's still there.
I'm a noob to Android Terminal, so i tried putting
do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
into it, but it didn't work, then i tried
"$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal"
and it didn't work, so i had to remove the first "$" to get it to work
(so it looks like "su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal")
Am I doing something wrong ?
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
Thank you Gryncc!!! it worked for me in im i9500. I did it with ADB Shell... the comands where...
su
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
the 0 did nothing, so I tried 1 and after reset, the sensor worked again!
Regards,
Julián
julianbl said:
Thank you Gryncc!!! it worked for me in im i9500. I did it with ADB Shell... the comands where...
su
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
the 0 did nothing, so I tried 1 and after reset, the sensor worked again!
Regards,
Julián
Click to expand...
Click to collapse
can u post a screen shot for commands to be used.
a video will be most appreciable,,
This is how it looks like,
2 separate commands, echo 0 = reset, echo 1 = calibrate
For me it worked till i restarted device.
Gonna send it in for repair now.
Yes it works on note 2 even.but how to stop it going away after restart any thing permanent? ??
Hi,
The proximity sensor on my Galaxy Note 2 has broken, which means as soon as a I make a phone call the screen goes black and I can't end the call or wake the screen up.
In touchwiz there is an option to disable the proximity sensor during calls but I'm using an AOSP rom, I have had a look in all the settings and there is nothing about disabling the proximity sensor during calls.
The sensor is called "cm36651", I have tried to disable it using Hardware Disabler but I can't find it in the list of devices even when I search from "/".
So does anyone know another method of disabling the proximity sensor?
Thanks
Go into the phone app. Click settings. Untick the turn on proximity sensor during calls.
Sent from my GT-N7105 using XDA Premium 4 mobile app
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
During calls, does your screen turns on again if you shine the proximity sensor under a bright source of light? If yes, all you need to do is recalibrate. I had the same thing happening.
http://forum.xda-developers.com/showthread.php?t=2045569
Sent from my GT-N7105 using xda app-developers app
spigget said:
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
Click to expand...
Click to collapse
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
costcutter said:
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
Click to expand...
Click to collapse
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
CanadianKB said:
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
Click to expand...
Click to collapse
I Got It! Click Here --------> https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix ... the app is call Proximity Fixer i have a Note 2 Verizon running on CM 11 and it works perfectly :good: :laugh:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
disable prox sensor
j3oomerang said:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
Click to expand...
Click to collapse
I tried everything I could find, including several root programs, and nothing would keep my screen from going black when I made phone calls on Nexus 5 (after broken screen replaced). Tried every single proximity sensor "fix", and disabler app but nothing worked. The Sensor kept showing 0.0 meaning it though it was right up against an object.
I finally put a piece of foil in front of the sensor, and now it reads 5.0 (max distance) and FINALLY the screen stays on in phone calls - unless I tap the power button to shut it off.
There must be some factory calibration they do with the original screen, and any replacement one is just not quite exactly the same.
Hello, I'm currently using CyanogenMod 11 [BR4] and I'm unsure if it's an issue with the rom or my device as they used to work before this rom.
The bottom button light is always turned on when the screen is turned off. The brightness goes down, but they're still turned on at a dimmed level.
Any suggestions?
Thanks.
Scriptaculous said:
Hello, I'm currently using CyanogenMod 11 [BR4] and I'm unsure if it's an issue with the rom or my device as they used to work before this rom.
The bottom button light is always turned on when the screen is turned off. The brightness goes down, but they're still turned on at a dimmed level.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Settings > Device > Buttons > Backlight > Tick Illuminate buttons.
dr.patron99 said:
Settings > Device > Buttons > Backlight > Tick Illuminate buttons.
Click to expand...
Click to collapse
Already tried this and the lights are still always dimmed
Scriptaculous said:
Already tried this and the lights are still always dimmed
Click to expand...
Click to collapse
Not from my side at least,I'm also on BR4. Well the only way you may try is to change the rom, Try any nightly or any other rom. But in my opinion it has nothing to do with Capacitive sensors. Some sort of light panel issue(Hardware Issue) :fingers-crossed:, not rom itself.
dr.patron99 said:
Not from my side at least,I'm also on BR4. Well the only way you may try is to change the rom, Try any nightly or any other rom. But in my opinion it has nothing to do with Capacitive sensors. Some sort of light panel issue(Hardware Issue) :fingers-crossed:, not rom itself.
Click to expand...
Click to collapse
Seems the issue was to do with overclocking. Reduced the CPU speed and seems to work perfect now.
Hi...plz help me I am unable to use miui due to a problem with screen turning on.. When I click.the power button to wake the screen sometimes there will be delay delay in the screen turning on or sometimes it wont turn on....I tried custom kernal but still no difference.. Thnx. Plz help
Miui which version and rom type?
Eziogamer said:
Hi...plz help me I am unable to use miui due to a problem with screen turning on.. When I click.the power button to wake the screen sometimes there will be delay delay in the screen turning on or sometimes it wont turn on....I tried custom kernal but still no difference.. Thnx. Plz help
Click to expand...
Click to collapse
Go to Settings > Display > Colors & Saturation > and set it to "Standard". It will solve it.
Or if u still want to use "cool" color setting, Go to lock screen settings and turn on "Prevent pocket dials".
I had same issue with MiUi with Xposed installed ! If you RUN both....try uninstalling Xposed
jahraKaL said:
Go to Settings > Display > Colors & Saturation > and set it to "Standard". It will solve it.
Or if u still want to use "cool" color setting, Go to lock screen settings and turn on "Prevent pocket dials".
Click to expand...
Click to collapse
Thnx I will try..
only the fingerprint sensor big is fixed for me but its not available on screen off only can be used when screen in on
thearorahimanshu said:
only the fingerprint sensor big is fixed for me but its not available on screen off only can be used when screen in on
Click to expand...
Click to collapse
Coming from pie to Android 10 I can use it with the screen off
Baron60 said:
Coming from pie to Android 10 I can use it with the screen off
Click to expand...
Click to collapse
is there "4" written next to wifi in status bar and notification Toggle ?
thearorahimanshu said:
is there "4" written next to wifi in status bar and notification Toggle ?
Click to expand...
Click to collapse
Yes.. it shows you if you're on 2.4 or 5 ghz
thearorahimanshu said:
is there "4" written next to wifi in status bar and notification Toggle ?
Click to expand...
Click to collapse
It means that you are connected to a 2.4GHz WiFi network.
When you connect to a 5GHz Wifi, the "4" changes to "5".
ok so what about hotspot's "5" ?
thearorahimanshu said:
only the fingerprint sensor big is fixed for me but its not available on screen off only can be used when screen in on
Click to expand...
Click to collapse
android 9 ?
Nothing has been fixed basically
Pretty underwhelming
Fingerprint Issue is fixed.
thearorahimanshu said:
only the fingerprint sensor big is fixed for me but its not available on screen off only can be used when screen in on
Click to expand...
Click to collapse
As it was in Pie, fingerprint is back to normal.
1. Fingerprint appears even when screen is off.
2. No difference in speed.
imarchit19 said:
As it was in Pie, fingerprint is back to normal.
1. Fingerprint appears even when screen is off.
2. No difference in speed.
Click to expand...
Click to collapse
what do you mean at point 1? Has option to dont show when you move phone, that means only when you put your finger to unlock it shows.
you are so confusing.
Settings > display > advanced > lock screen display > new notifications (turn this on) by turning this on fingerprint scanner in screen off is working for me... try it
L1p1c1 said:
what do you mean at point 1? Has option to dont show when you move phone, that means only when you put your finger to unlock it shows.
you are so confusing.
Click to expand...
Click to collapse
Sorry if I sounded confusing.
What I meant by Point 1 was that despite the update and fingerprint working.
Many of my peers said the option to show fingerprint location on lockscreen wasn't working.
In my case fingerprint appeared both when my screen was on and off.
thearorahimanshu said:
Settings > display > advanced > lock screen display > new notifications (turn this on) by turning this on fingerprint scanner in screen off is working for me... try it
Click to expand...
Click to collapse
I love you buddy
I've received today March security patch in Android 9.
Size: 93.7MB
eu
Bugs
I'm still bothered by the fact that I can't change media volume when the screen is locked.
Is the proximity sensor fixed yet? I keep accidentally triggerrimg flashlight and DND mode.
Also I don't think I'll ever get the A10 update. They're so slow. This might be the last xiaomi A1 phone I buy. Or any xiaomi phone. Where to report bugs?
This is an joke
LeAntsy said:
I'm still bothered by the fact that I can't change media volume when the screen is locked.
Is the proximity sensor fixed yet? I keep accidentally triggerrimg flashlight and DND mode.
Also I don't think I'll ever get the A10 update. They're so slow. This might be the last xiaomi A1 phone I buy. Or any xiaomi phone. Where to report bugs?
Click to expand...
Click to collapse
To change the media volume with locked screen, it must be turned off - disable showing fingerprint icon and it'll work just fine. I'm using it since I bought the phone.
Proximity sensor works fine, you just need to "learn" how to use the phone - when calling, put it against your ear at angle with the top edge first, this will trigger the proximity sensor. Then push it against your ear.
To report bugs, use Feedback app from system settings.
Other phones do not need any special usage procedures, proximity sensor just works, but in A3 it is screwed.
Got this today