Hi everyone, i found the solution for the bad reading in the fingerprint reader in roms (at least works for me in Evolution 4.0 but should it work on any rom) the reason of the problem was that the finger print is optic and reads with light shined from the screen, but many roms shine light with the level of brightness of the system , meaning, brightness low= bad reading, brightness max = good reader.
The solution was installing Kernel iMMENSITY v13.0-MI9-FOD-25-01-20 but i imagine all versions with the name FOD should it work.
If any more can confirm this kind of solution please let us now.
Thanks to the developer of this kernel.
RoFeli said:
Hi everyone, i found the solution for the bad reading in the fingerprint reader in roms (at least works for me in Evolution 4.0 but should it work on any rom) the reason of the problem was that the finger print is optic and reads with light shined from the screen, but many roms shine light with the level of brightness of the system , meaning, brightness low= bad reading, brightness max = good reader.
The solution was installing Kernel iMMENSITY v13.0-MI9-FOD-25-01-20 but i imagine all versions with the name FOD should it work.
If any more can confirm this kind of solution please let us now.
Thanks to the developer of this kernel.
Click to expand...
Click to collapse
Using Pixel Experience
not working
Register my fingerprint with lowest brightness.
Then I found when using low brightness < 36 , It's working!
Then register with highest brightness, not working .... seems the fingerprint reader with high brightness not working.
Related
Hi,
my light sensor value is always at 33,no matter what ambient light there's in the room.
I'm using CM7 stable.
Any ideas?
and you see it in what software?
try to bring it exactly under desk lamp, if you use Elixir.
There is some "low" dead zones, need high contrast to see changes.
If not then wipe reinstall.
Hi,
i've checked with cyanogens build in feature.
Then i've installed elixir,placed the device under a lamp and the sensor started working and is working eversince.
So thanks a lot,"problem" solved.
hi all, I noticed that light sensor doesnt work properly, when I go from dark to light area, the brightness increases but when I go from light to dark area the brightness wont decrease, on honeycomb it worked properly, anybody else experiences this problem?
Same here, it goes bright but does not decrease.
I use the app https://play.google.com/store/apps/details?id=rubberbigpepper.DisplayBrightness&feature=search_result#?t=W251bGwsMSwxLDEsInJ1YmJlcmJpZ3BlcHBlci5EaXNwbGF5QnJpZ2h0bmVzcyJd
make an invisible slider on the edge of screen to adjust brightness.
is there any way to make it work properly?
Don't think so. Its pretty much unusable now.
Sent from my HUAWEI MediaPad using Tapatalk 2
There are lots of negative comments about light sensor, but i have to say it works well to me on ICS. Could be possibly massive amount of defected devices.
Lightsensor doesn't work for me either - too bad, hope it will be corrected.
Perhaps it's because I'm running ICS "General Channel".
HUAWEI MediaPad FIRMWARE(S7-301u,android4.0,C232B002,General Channel)
Do the sensor dim the light in the same session for you?
Here it turns up the light but not down again.
Sent from my U8800 using Tapatalk 2
Same here, adjusting upwards works fine, but it doesn't adjust downwards in low light conditions.
I have tried two apps that turns the light down again, custom auto brightness and lux auto brightness.
One small problem. The pad will crash on pattern unlock after sleep. I Also the light sensor will not work s after wake up sometimes.
Sent from my HUAWEI MediaPad using Tapatalk 2
mangoman said:
I have tried two apps that turns the light down again, custom auto brightness and lux auto brightness.
One small problem. The pad will crash on pattern unlock after sleep. I Also the light sensor will not work s after wake up sometimes.
Sent from my HUAWEI MediaPad using Tapatalk 2
Click to expand...
Click to collapse
I'm guessing no one has had any luck with this issue but I figure I'd necro the thread anyways. My light sensor sucks also. I used 'Android Sensor Box' to get the values coming out of the sensor. It only displays either 40 lux or 280 lux which is obviously not right. This is on Cyanogen 9, stock t-mobile ICS and the rooted international gingerbread(can't remember which one exactly).
So I was wondering if anyone who owns one of these has ever gotten a sensor value that makes any sense.
thanks
nope,
I use instead display brightness https://play.google.com/store/apps/details?id=rubberbigpepper.DisplayBrightness&hl=no
create an invisible brightness slider on theedge of the screen.
Try using custom auto brightness with the auto brightness on (there's a setting in that app that disabled the system auto brightness at screen on. Turn it off).
The original kernel only recognized 3 light levels. If you use bart's kernel it will recognize 6 levels.
Yes, I think there's a software problem because both app (lux and cua) crash hard in HMP, but I don't think fixing it is a priority.
Sent from my HTC Glacier using Tapatalk 2
How to use custom auto brightness without crashing the tablet.
There are 2 options that should be followed, other settings can be adjusted to your liking.
1. In preferences, Check Use pulsed sensor mode. Basically this option will make the app read the sensor itself instead of listening the sensor value given from the system.
2. In advanced preferences, set the sensor update speed to either half sec or 1 sec. I tried normal, but the app won't read the sensor value, so probably the slow normal maximum setting only works if you get the sensor value from the system.
You can set disable system auto brightness. I recommend it before because the setting was a "hack" which was making the system read the brightness value thus the app can get that value. Right now it's recommended that you check the disable system auto brightness.
So I've used the search bar and google
there are 4 circles at top
1. Ambient Light sensor
2. LED notification lights
3. ???
4. Proximity Sensor
so whats in between the earpiece and proximity sensor
also why dont apps recognize the ALS? I've used android sensor box, androsensors and my android sensors but still nothing. Though auto brightness works. I know, I move my finger over it and the screen gets dim
z50j said:
So I've used the search bar and google
there are 4 circles at top
1. Ambient Light sensor
2. LED notification lights
3. ???
4. Proximity Sensor
so whats in between the earpiece and proximity sensor
also why dont apps recognize the ALS? I've used android sensor box, androsensors and my android sensors but still nothing. Though auto brightness works. I know, I move my finger over it and the screen gets dim
Click to expand...
Click to collapse
The last 2 sensors are for proximity i guess, cause even on my mini pro i have 2 circles for proximity. In the stock rom, it is never detected, its on by default. In roms like cm10, CM10.1 etc. you can choose whether to use it or not, change the different levels etc.
Well in mini pro its
Led, ambient sensor, camera, proximity.
Tbh, I think I have seen two dots instead of one for sensor. (Really hard to see)
Regards
N
mnishamk said:
Well in mini pro its
Led, ambient sensor, camera, proximity.
Tbh, I think I have seen two dots instead of one for sensor. (Really hard to see)
Regards
N
Click to expand...
Click to collapse
Yep there are two sensors for proximity.
why are there 2 sensors for proximity? using the sensor apps I've noticed that only that the right most works the 3rd one doesnt really do anything when i cover it. but it works so I'm fine with that
but how come the apps dont detect the ambient light sensor? that too is obviously working because the screen dims when i hover over it
Try using the service menu and see if it works there
Regards
N
mnishamk said:
Try using the service menu and see if it works there
Regards
N
Click to expand...
Click to collapse
I did, it doesnt
To my opinion the display brightness slider seems to function non linear. In the lowest region it's very sensitive and in the middle region its not sensitve (to a slight increase of the slider) at all. This on itself is no big problem, but it seems that the Adaptive Brightness setting affected by this too. So when using the OPX in low light conditions the screen responds very heavily to a small change in ambient light. Resulting in sometimes a very bright screen and sometimes almost no back light at all. Using a OnePlus X E1003 with Oxygen OS 2.1.3 (not 2.1.3-x, but it's release notes don't note this).
Do some other users have this too?
koen12333 said:
To my opinion the display brightness slider seems to function non linear. In the lowest region it's very sensitive and in the middle region its not sensitve (to a slight increase of the slider) at all. This on itself is no big problem, but it seems that the Adaptive Brightness setting affected by this too. So when using the OPX in low light conditions the screen responds very heavily to a small change in ambient light. Resulting in sometimes a very bright screen and sometimes almost no back light at all. Using a OnePlus X E1003 with Oxygen OS 2.1.3 (not 2.1.3-x, but it's release notes don't note this).
Do some other users have this too?
Click to expand...
Click to collapse
yes. These kind of stupid bugs are irritating. This issue and USSD code issue infuriates me. Seems like they don't test the ROM at all.
Yes. That's a thing I hate in this phone.
Same here!
This seems to be solved mostly in OOS2.2.1.
Does anyone know if theres a file that can be edited to change the brightness values that correspond a certain position on the brightness slider?
Hello,
Has anyone noticed a promixity (maybe ambient light) sensor issue? Often (more in the dark) I can see a weak red light blinking right where there is the proximity sensor(it stays there if automatic brightness is on). I tried disabling and closing one app per time but it seems more like a software bug...
Anyone else?
Sony Xperia X F5121
Hello ! Yes! (sorry for my language I'm French).
Tonight, after charging my phone at 100%, I have seen a red little light in the '' capter '' a the right (for automatic luminosity I think). It was a big bug who during ~ 30 minutes. And I have lost 20% of battery, I think, cause to this bug.. Do you already have the bug today?
daddu97 said:
Hello,
Has anyone noticed a promixity (maybe ambient light) sensor issue? Often (more in the dark) I can see a weak red light blinking right where there is the proximity sensor(it stays there if automatic brightness is on). I tried disabling and closing one app per time but it seems more like a software bug...
Anyone else?
Sony Xperia X F5121
Click to expand...
Click to collapse
I've een it also sometimes but i've no idea what it is
me too,but i've noticed that only blinks when its recieveing data when changing from wifi to 4g and viceversa,when its done,it doesnt blink anymore.
Does anyone have any idea for this problem please ? :'(
daddu97 said:
Hello,
Has anyone noticed a promixity (maybe ambient light) sensor issue? Often (more in the dark) I can see a weak red light blinking right where there is the proximity sensor(it stays there if automatic brightness is on). I tried disabling and closing one app per time but it seems more like a software bug...
Anyone else?
Sony Xperia X F5121
Click to expand...
Click to collapse
@Mr High Tech @kistigun @kalel29
Are you kidding me guys? :laugh::laugh:
It's not a red light.... It's barely visible because it's an Infrared Sensor Infrared light is usually visible only in very dark conditions.
Hint that will make your day - when it's dark and you barely see it, try pointing a camera at it! It flashes white now, doesn't it.
Sebi673 said:
@Mr High Tech @kistigun @kalel29
Are you kidding me guys? :laugh::laugh:
It's not a red light.... It's barely visible because it's an Infrared Sensor Infrared light is usually visible only in very dark conditions.
Hint that will make your day - when it's dark and you barely see it, try pointing a camera at it! It flashes white now, doesn't it.
Click to expand...
Click to collapse
more than wanting to know what it is, i think they want to understand why; why does the proximity sensor stay on?
i had this question too, before updating to the latest firmware (.292). after that, it seems the "problem" doesn't occur anymore, but i'm not that sure. i'll have to double check.
however, do some of you use "Smart backlight control" feature?
carlo93 said:
more than wanting to know what it is, i think they want to understand why; why does the proximity sensor stay on?
i had this question too, before updating to the latest firmware (.292). after that, it seems the "problem" doesn't occur anymore, but i'm not that sure. i'll have to double check.
however, do some of you use "Smart backlight control" feature?
Click to expand...
Click to collapse
Smart backlight control makes use of the accelerometer of the phone. Keeps the screen on by detecting movement. Neat feature.
Smart call handling on the other hand uses the proximity sensor. Also the style cover preinstalled software. And of course Call handling uses the proximity sensor.
I'm using a modified version of Gravity Screen for pocket mode. Proximity sensor flashes all the time in order to turn the screen on and off when it's in or out of the pocket. Also I use the proximity sensor so that the screen won't turn on when it's in the pocket - like when a call comes in and I don't want to accidentally answer.
One thing you should know about the proximity sensor is that it uses a crazy low amount of power (0.18mA). Now the software that uses the sensor might have many wakelocks but we also need features so it's a small price to pay haha. Also if you're planing on using gravity screen (which is a cool app), you can always add a on/off widget.
There's really nothing to worry about - none of those features/apps I mentioned register on power consumption.