Just got my 206 for a month, the ambient sensor between the proximity sensor and front camera is emitting blinking red night in a dark room or at night.
Does anybody has this issue? Can it be fixed by flashing or it's a hardware issue? Does it worth it to send it back to get it fixed?
Thank you.
Try flashing.
stanley321 said:
Just got my 206 for a month, the ambient sensor between the proximity sensor and front camera is emitting blinking red night in a dark room or at night.
Does anybody has this issue? Can it be fixed by flashing or it's a hardware issue? Does it worth it to send it back to get it fixed?
Thank you.
Click to expand...
Click to collapse
"I don't have that problem, and never had, try flashing." - Correction, I have that problem also, have some remarks in a comment a few post after this one.
stanley321 said:
Just got my 206 [...]
Thank you.
Click to expand...
Click to collapse
This problem is discussed https://forum.xda-developers.com/yotaphone-one/help/proximity-sensor-active-t3520013
and it happens mostly on YD206 devices with EU/RU firmwares and CN radio. At the moment there is no solutions, except having the radio which comes within the firmware currently installed. Some users doesn't have this blinking, some does, It's a matter of combining different firmwares & radio. For example, my phone is on latest RU 134, when I flashed the CN radio the sensor started blinking, after putting back again RU radio, it stopped.
for this I don't install a CN radio but the downturn is that with other radio if you have a Y206 you will lose phone signal...
I discovered that I also have this problem, I was with the wrong radio, had to flash the Chinese radio and it suddenly appeared, this is what I have found I have an YD206, so I wonder how the YD201 behaves:
On YD206:
With wrong radio. radio (Russia xx versions) on YD206 , in KitKat or Lollipop ROMs the proximity sensor is OFF by default BUT, as soon you turn ON an app that uses it, it won't turn off again, it keeps blinking even if you force kill the app that started. However it will turn off if the screen is off, after 5 seconds after. Also it's important to acknowledge that 2G only with this radios fails. On Lollipop Wifi won't turn off automatically, just manually.
YD206 With the correct radio. radio S01_003_3034_CN1_M05 2G 3G (UMTS) and 4G (LTE) all work and with better reception, but as soon the screen is ON, the proximity sensor starts working, does not matter what app you have open, when you turn OFF the screen the proximity sensor will turn OFF in about 5 seconds. If you are using the EPD screen the proximity sensor will turn OFF faster than 5 seconds, but as soon you touch the EPD it will turn ON for 3 seconds or so. On Lollipop Wifi won't turn off automatically, just manually.
So the problem acts differently when you flash a different radio, I am not sure where's the bug comes from, but it seems there's also a bug with YotaRom. There's a Xposed module to disable proximity sensor in specific apps, I haven't tried that, I also would like to know how this behaves with the Marshmallow Beta.
(For the ones that are not aware of this problem, keep in mind that to see this problem you need to be on a dark place to see the very faint red light of the proximity sensor.)
Best regards,
This problem is also being discussed here: https://forum.xda-developers.com/yotaphone-one/help/proximity-sensor-active-t3520013/
Related
Hello,
I have bought myself a diamond touch 2, and i directly flashed it to Dutty's R6 rom because i like it much better and i made up my mind about it even before i bought it.
Now i seem to have a problem, and i don't know what would be the problem; either the device or the rom?
Proximity doesn't work; setting automatic backlight dimms the screen to a low-light level. Holding a flashlight above it doesn't make any difference.
Also, when making a call, the display keeps being illuminated the whole time, no matter if i hold it to my ear or not.
Does someone recognize this problem?
Cheerz
Exca said:
Hello,
I have bought myself a diamond touch 2, and i directly flashed it to Dutty's R6 rom because i like it much better and i made up my mind about it even before i bought it.
Now i seem to have a problem, and i don't know what would be the problem; either the device or the rom?
Proximity doesn't work; setting automatic backlight dimms the screen to a low-light level. Holding a flashlight above it doesn't make any difference.
Also, when making a call, the display keeps being illuminated the whole time, no matter if i hold it to my ear or not.
Does someone recognize this problem?
Cheerz
Click to expand...
Click to collapse
Settings\System\Power\Backlight\ Turn off Auto adjust.
If i turn off auto adjust i can indeed set full brightness, but that's not the point. I want the auto-dimming and proximity sensor to work, so when i hold the piece next to my ear it locks and turns off the screen...
If I turn on auto-adjust, it doesn't respond on any lightchange or action; it just dimms the screen to about 40% and keeps it there.. either a bug or a hardware fault with my unit?
Not sure that it ever worked perfect out of the box.
Have you tried tweaking the settings with TD2 Tools?
How do you mean tools? As far as i know i can only find one box to turn auto adjust on.. you have the same configuration, does it work for you?
EDIT: I installed the app "LumosWizard". Now the phone's backlight adjusts depending on the light the sensor receives. The sensor works well as the values go up when putting a flashlight on it.
However, i wonder why this doesn't work with just auto-adjust on, that's what the HTC Auto-Backlight should do right? Also, with this app, the backlight doesn't go out when no light is reveived (auto-lock when putting into pants, or turned off backlight when calling...) ?
This is what i'm looking for: http://www.youtube.com/watch?v=6xakUmz1zwc
=> i don't think this is achieved by an additional application, but is just standard HTC service doing this because of putting on the auto-adjust...
There is NO proximity sensor on Touch DIAMOND II. Only light sensor. Use Touch_InCall_Screen_Tweak instead. This program use G-sensor and block the screen when your phone is in vertical position.
m72m72 said:
There is NO proximity sensor on Touch DIAMOND II. Only light sensor. Use Touch_InCall_Screen_Tweak instead. This program use G-sensor and block the screen when your phone is in vertical position.
Click to expand...
Click to collapse
Thanks, installed and works good!
Still wondering though why i need a 3rd app like LumosWizard to make the lightsensor work, as htc's autoadjust apparently doesn't
I did find this .cab called Glight and it works great on my TD2
More about it here:
http://www.ageye.de/index.php?s=glight/about
Okay.lately my flash hasn't been working on my camera.
My screen recently cracked and I got it fixed, could that be related ?
I have tried different kernels but the flash remains broken.
Torch and other flashlight apps also don't work.
My battery is above 20 percent.
I do know how to turn flash on.
Is there an easy fix?
well if nothing works with your flash are you sure your LED's arent broken?
Are leds the red light when charging?
If so, then yes, those work
Yeah that is an LED indicator but he's talking about the LED Lights which make the flashlight. I don't think there's anything to do, they've probably just worn out.
Is there a fix ? Software or hardware? Any ideas on how much such a fix would cost ? Its not a big deal since my gf just bought a 14mp camera , but it does hurt the resale value of the phone
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
I tried with Sensor List and it does indeed show up the sensor, but doesn't seem to be getting any data from it. So it's not just your tablet.
Same thing with "AndroSensor", it shows it but no data change in it either. Hopefully we can figure out what the issues is? Are both of you using the factory install rom? Or a rooted one with a tweaked kernel?
sda.171 said:
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
Click to expand...
Click to collapse
I got Sensorlist and tried it and I do get data from it.
xhz/xxxx or xxxxxms and a red line. The upper limit is 227 and lower limit is -227 and the red checked number changes. It's nowhere as quickscrolling as the other sensors but I get a jagged red line moving across.
okay guyz i think i figured this whole thing out most probably-
I just came back from this electronic store, i closely examined the iconia on display- a500 - noticed the black glass under the volume rocker and rotation lock and THE LIGHT SENSOR WAS THERE! :O - looking like just any ordinary light sensor-
This made me come up to the following conclusions- since i have had another iconia before i returned it for warranty- i was able to identify the following differences-
1st variant-model
Light sensor present
Mic volume low
Volume locker button hard to push
Power button sorta pushed inside
2nd variant model -( the one i currently have)
Light sensor absent? Or hidden under black glass? (Manufacturing defect?)
Loose rotation lock (hardware) toggle
Mic volume high (as in proper)
-(i faced these additional problems)-> glass over the camera came off and the glossy label on the side slipped out.
So if u have the first variant, the one i previously had and the one i examined in the shop today- that should give u data from the light sensor, and the 2nd variant with hidden/absent light sensor won`t.
These are my findings. Feel free to point out and discuss-
What should we do? I m considering a second replacement now -_____-
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
I appear to have what you call the second variant model. I just checked with Androsensor, and the light sensor does appear to be present beneath the black glass, just under the volume up rocker. I agree it does appear to sleep until it senses a light source.
cm0901 said:
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
Click to expand...
Click to collapse
I just downloaded andro sensor-
Under light sensor it sed-waiting for event-
I took my hd2, turned on the flash! Pointed it right above the sensor and no response, it just kept saying waiting for event- so does this mean i have a defective sensor?
Can this be a kernel/rom related issue?
Pls someone try this and let us all noe.
Thanks
It's a long shot but you might attempt flipping the check mark a few times under the brightness setting and "auto adjust" as that probably toggles the sensor as well, though these apps are supposed to do it. Or close and start the app a few times and then check the sensor. I don't know what activates it but I can confirm that it has some kind of threshold where it sleeps or isn't active and another where it is, so you might want to try various things to, as others have mentioned, wake it up.
Are you using any ROMS by any chance or are you on stock? Have you done any sort of modification of the system - rooted and removed things or replaced kernels, etc?
If you are on a ROM or have done any modifications, you may want to try going back to full stock 3.2 or 3.1 and seeing if that helps before you decide it's actually defective.
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
KILLER_K said:
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
Click to expand...
Click to collapse
Same as Killer, seems to be working, rooted 3.2, couldnt see until bright light on it.
Anyone have any idea where the mic(s) are, not really important just wanna know which end to scream into when doing voice search
Mic is located directly in the top center of the front face, in the space between the glass and the bezel. You should be able to see it with just a small amount of light shining on it.
FINALLY!
after various non stop auto brightness toggle on and offs - waiting for event went and 1 lux came xD - i shone light the reading increased - and stopped working agen :|
I dunnu maybe the apps are not fully compatible.
I can say it is working because i changed my brightness to full manually and then turned auto on and the brightness level set itself automatically.
So will we have to wake up the sensor from a state of sleep all the time or is it just for the apps xP - last confusion.
Thanks every1 for ur responses, the mystery is finally coming to an end xD!
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
my video, search on youtube: Proximity Sensor always on Xiaomi Mi A1 BUG?
THANKS
https://www.youtube.com/watch?v=zdONFH0B6xg
UPDATE VIDEO: https://www.youtube.com/watch?v=H09kbi4-DCM
Mr.Oscar said:
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
my video, search on youtube: Proximity Sensor always on Xiaomi Mi A1 BUG?
THANKS
https://www.youtube.com/watch?v=zdONFH0B6xg
Click to expand...
Click to collapse
Unfortunately it looks like a bug in newest February stable stock ROM.....
This is how it looks like on my phone:
https://www.youtube.com/watch?v=0SO34GCD8Pg
ves626 said:
Unfortunately it looks like a bug in newest February stable stock ROM.....
This is how it looks like on my phone:
https://www.youtube.com/watch?v=0SO34GCD8Pg
Click to expand...
Click to collapse
Thanks, i have oreo patch january and on my xiaomi, when the screen is off, stops flashing
Yep! It is blinking when the screen is on. (I'm on February Patch.)
I'm on February patch and not facing this behaviour. Maybe you have an app making phone work like this? Hope you solve it.
carmeloamg said:
I'm on February patch and not facing this behaviour. Maybe you have an app making phone work like this? Hope you solve it.
Click to expand...
Click to collapse
No, I don't have any application which does this. Check it by a camera ( I think it is infrared) and when the screen is ON.
My proximity sensor test
Same here also
Mr.Oscar said:
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
Click to expand...
Click to collapse
I think it's a bug in new February Patch Stable Update
First of all, I can't reproduce it (used my work iPhone's camera, and yes iPhone sucks but it's for my job, no choice here ).
Second, are you sure it's a bug? Did you do similar check before Feb update?
I'm not a pro of phone hardware, but it seems normal to me that the sensor will be always working. I'm even using an app to wake the phone with the sensor (https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup) so the sensor is working all the time, even with screen off.
It's not a bug, it's the same for a lot of phones, don't worry
N1ck474 said:
It's not a bug, it's the same for a lot of phones, don't worry
Click to expand...
Click to collapse
thanks, many mi1 owners do not have this bug
BtB said:
First of all, I can't reproduce it (used my work iPhone's camera, and yes iPhone sucks but it's for my job, no choice here ).
Second, are you sure it's a bug? Did you do similar check before Feb update?
I'm not a pro of phone hardware, but it seems normal to me that the sensor will be always working. I'm even using an app to wake the phone with the sensor (https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup) so the sensor is working all the time, even with screen off.
Click to expand...
Click to collapse
thanks bro, I'm not sure it's a bug, however the sensor should only be activated for calls
It's not a bug. The proximity sensor is also used for auto brightness control.
When the proximity sensor is tripped, values from the light sensor is ignored, which means that screen brightness won't change even when the light sensor detects changes in ambient light.
This is useful for e.g. when you play a game or watching a movie in landscape and your hand covers the light sensor. The screen won't go dark, but stays at the same brightness. Without the proximity sensor activated, your screen would go dark every time you accidentally cover the light sensor with your hand.
Try turning off adaptive brightness and see if it's still on. It shouldn't be necessary to have the proximity sensor on all the time if you set the screen to a fixed brightness.
quetzalcoatl2435 said:
It's not a bug. The proximity sensor is also used for auto brightness control.
When the proximity sensor is tripped, values from the light sensor is ignored, which means that screen brightness won't change even when the light sensor detects changes in ambient light.
This is useful for e.g. when you play a game or watching a movie in landscape and your hand covers the light sensor. The screen won't go dark, but stays at the same brightness. Without the proximity sensor activated, your screen would go dark every time you accidentally cover the light sensor with your hand.
Try turning off adaptive brightness and see if it's still on. It shouldn't be necessary to have the proximity sensor on all the time if you set the screen to a fixed brightness.
Click to expand...
Click to collapse
Thanks for reply, I deactivated ambient display, and automatic brightness.
But it still does!
If can help someone I mock value with sensor disable xposed module.
My set is 2.5 (half of total value)
But my phone is a redmi 4a
#EDIT
Did one more test, my Mi A2 don't even use the proximity sensor, it uses only the front camera/light sensor to turn off the screen.
#EDIT
Hello, friends, everyone is well know about the problem supposedly about the proximity sensor, that is inaccurate when playing whatsapp sounds, in calls, messenger and etc. But, after several tests, calibrations and apps, today I figured out the REAL problem.
Today I tried to hear a whatsapp audio outside, with sun, and everytime I tried, the screen went off. So, I tried to calibrate the proximity sensor with the app, and the sensor was activated always, covering it or not.
Then I went to *#*#8464#*#* and instead of calibrate the proximity sensor, I calibrated the LIGHT sensor. For my surprise, it worked. The light sensor comes from the front camera, so, for some reason, on Oreo and Pie, don't know if it's Xiaomi software problem, or Google problem, but the Android is using the light sensor together with proximity sensor to turn screen off, or not. And because of this, bad programming or not, there is this problem. Even in other Xiaomi phones I heard about this problem, like Redmi 7.
Also, that's justify my other point, about Adaptive Brightness, if it's on, almost solving this problem.
Don't post here go to the Q&A section!
fir1996 said:
Don't post here go to the Q&A section!
Click to expand...
Click to collapse
Oh, sorry, tought that would be a discussion.
If any mod could move for me, I appreciate that.