Database Develop

HOW to fix proximity sensor delay during call in .205 firmware????

where is the fix for this trouble???
in .201 FW sensor work normal. in 4.1 work normal.
ON .205 and 207.
Proximity sensor reacts slow to turn on screen when phone is moved from ear
1 sec 2 sec .
it just infuriates and annoying, I can not stop talking immediately after the removal of the phone from his ear.

I think you can change the delay in build.prop.
"#mot.proximity.delay=25
#ro.lge.proximity.delay=25" or something like that

kassiss-x said:
I think you can change the delay in build.prop.
"#mot.proximity.delay=25
#ro.lge.proximity.delay=25" or something like that
Click to expand...
Click to collapse
tried it, does not help

dima_vrn1 said:
where is the fix for this trouble???
in .201 FW sensor work normal. in 4.1 work normal.
ON .205 and 207.
Proximity sensor reacts slow to turn on screen when phone is moved from ear
1 sec 2 sec .
it just infuriates and annoying, I can not stop talking immediately after the removal of the phone from his ear.
Click to expand...
Click to collapse
Mine is worst, sometimes it takes even 30 sec. or more to wake up [emoji33]
I though it was just mine, cause i don't see many people complaining about this..
Cheers.

The bad news is that none of the firmwares .205 jr .207 does not fix the problem

Many people suffer from this problem, in my opinion it is related to the base software.
I have tried most of the custom and stock Roms for LBL device and the all have this problem.
If you Google this problem it is well known but Sony have no solution other than go to a Service Centre for them to replace the proximity sensor which does not work either.

I just found an xposed module that can disable proximity sensor.. I'm using it now.. I have to manually turn off the screen during call but at least i can use the Phone!
Thank you.
Cheers.

Strange Adaptive Brightness issue

Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048

I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.

Same issue here.

Woah. I'm not alone. So for all you guys, it started just recently?

yeah. I noticed it a little less than a week ago

Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.

foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).

I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?

I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.

I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?

Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.

i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!

The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.

I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.

Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.

I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.

Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.

Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.

I think we should file a bug report here.
https://code.google.com/p/android/issues/list

I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.

Screen flickering trouble

my phone started flickering (2/3 rds from down to up)
it flickers when i lock\unlock the phone
when the light is set to auto and it gets low , to 10 % or so.
i found that the issue is worldwide with at&t phones,
tried :
solution 1 : wipe cache partition. => didn't work
solution 2 : activate developer mode, turn off "disable hardware overlays" => didn't work
solution 3 : turn off : setting\display\auto adjust screen tone => didn't work
then i downloaded : screen filter , allows you to put light at any percentage you want , i tried even 1%, the screen never flickers when i do the percentage manually.
so i guess the problem is software.

I have the same exact same problem..
I thought I was going crazy thinking it was only me..
I have tried screen shooting it when it happens but when I look at the screenshot in gallery it just shows a clean picture. Like nothings happening.
So weird
Sent from my SAMSUNG-SM-G900A using Tapatalk

MO35AB said:
my phone started flickering (2/3 rds from down to up)
it flickers when i lock\unlock the phone
when the light is set to auto and it gets low , to 10 % or so.
i found that the issue is worldwide with at&t phones,
tried :
solution 1 : wipe cache partition. => didn't work
solution 2 : activate developer mode, turn off "disable hardware overlays" => didn't work
solution 3 : turn off : setting\display\auto adjust screen tone => didn't work
then i downloaded : screen filter , allows you to put light at any percentage you want , i tried even 1%, the screen never flickers when i do the percentage manually.
so i guess the problem is software.
Click to expand...
Click to collapse
Same problem here!!! Maybe it's a hardware issue already, maybe a broken display?

its all over the world :/
the only thing i learned so far, never let the phone heat up, or you this might happen.
no solution yet.

mine started doing this after updating to 6.0.1. it gets really bad if the phone gets cold (on low brightness)

Hi. I just wanna share it. I found in this (xda comment post by some one I forget him for awhile looking for him to say thanks very much) fix for my s5 g900f with latest modem and bootloader. I use RR 7.1.2 rom.
The app is "active screen filter". That save my life.

XZ2 brightness flashing problem

Hello!
Sometimes, especially when downloading an app from Play store, when installing finishes, screen in XZ2 flashes for like 0.1sec. It goes very bright for a moment and then everything goes back to normal. Anyone knows why is that? I'm up to date with everything, ans have disabled everything connected with screen in settings, including adaptive brightness.

Monolithus said:
Hello!
Sometimes, especially when downloading an app from Play store, when installing finishes, screen in XZ2 flashes for like 0.1sec. It goes very bright for a moment and then everything goes back to normal. Anyone knows why is that? I'm up to date with everything, ans have disabled everything connected with screen in settings, including adaptive brightness.
Click to expand...
Click to collapse
I have the same issue as well at times. I will need to monitor what trigger this

Rithina said:
I have the same issue as well at times. I will need to monitor what trigger this
Click to expand...
Click to collapse
Do you use additional screen white balance in settings? It looks like this was the trigger for me. In certain situations it looks like phone forgot the options for color calibration and moment later was back to definied settings. So I set them back to default and since then no problem (despite more bluish screen comparing to custom white ballance settings of course )

Monolithus said:
Do you use additional screen white balance in settings? It looks like this was the trigger for me. In certain situations it looks like phone forgot the options for color calibration and moment later was back to definied settings. So I set them back to default and since then no problem (despite more bluish screen comparing to custom white ballance settings of course )
Click to expand...
Click to collapse
It didn't happened for my xz2c compare to my xz2. I going to try the wb to see that cause this issue

Rithina said:
It didn't happened for my xz2c compare to my xz2. I going to try the wb to see that cause this issue
Click to expand...
Click to collapse
Same here if screen is red and it finished installing an app from play store

Same here

Mi8 Display flash Problem

Hi,
I have a Problem with my mi8.
The Display flash
https://youtu.be/cLJ4-46QTsI
I think its a Hardware Problem
What you think ?

toniq1 said:
Hi,
I have a Problem with my mi8.
The Display flash
I think its a Hardware Problem
What you think ?
Click to expand...
Click to collapse
Turn off aod

Aod ?

toniq1 said:
Aod ?
Click to expand...
Click to collapse
Always on display. Sametimes it's help but it's probably fault of ambient light sensor or screen.

It is the same If aod Off
Not good

That's a common thing with faulty oled screens, it is a hardware issue

I have the same flashing screen when I turn the screen off before the aod is displayed. It does not happen all the time. Turning off aod does not help. I doubt that it is a hardware issue as the flashing started after updating to MIUI 11 - at least for me.

I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all

navzahed said:
I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all
Click to expand...
Click to collapse
ago是什么意思

beibei2 said:
ago是什么意思
Click to expand...
Click to collapse
It is used for past time if you're asking

So a little update on the flashing screen situation
I disabled auto brightness and set the brightness a little below middle of brightness bar and so far so good. No flashing here for a while
Also disabling the AOD completely solves the problem

Another update on the state of this flashing issue, after Android 10 update haven't seen any flashing so far, AOD display works fine, light sensor and automatic brightness work just fine.
I guess it was a software issue after all

I hope you have solved it. Do you have the anti-flick on?

Nikos kouk said:
I hope you have solved it. Do you have the anti-flick on?
Click to expand...
Click to collapse
Nope I don't

Anyone else who has this issue:
Try disabling hardware overlays in developer options, also check to see if the Game driver option within Developer options is set to default. Although its possible that this could be the beginnings of a hardware issue, it could also be a software related issue.
If none of the things that I mentioned work, i would try reflashing the stock fastboot rom. ( must be fastboot version)

Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.

koudy66 said:
Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.
Click to expand...
Click to collapse
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.

tsongming said:
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.
Click to expand...
Click to collapse
I have TWRP installed and thought of checking it out but it simply flashes there as well. Right now i have the display on, set never sleep in Developer options and simply keeping it up until new phone arrives. Once i am on new phone, i will try factory reset on this first and go from there i think. Not sure how to get to fastboot when display is not working.
Due to such weird nature that nothing really helps i tend to think that this is HW issue.
EDIT : Turned off display by accident (because phone call happened) and now it's back to flashing disco with absolutely nothing working. Fastboot (power + lower volume key together) is of course flashing as well so inacessible.

Happened to me too. Turned off AoD, restarted, turned on and it was ok for a while. Now flashed again. Dont know what is causing this :/
Odesláno z mého MI 8 pomocí Tapatalk

I also got the same issue on my dipper. The only solution that works perfect is by flashing to LineageOS 17.1. I know it's an OLED screen faulty but Lineage really fixes it. Been using Lineage for a few months and never have this display issue again. Other custom ROMs can't fix this display issue.