Question What are the minimal requirements to avoid random flickering? - OnePlus 11R (Ace 2)

Hi All,
Could anyone comment on the minimal requirements to avoid flickering and potential random restarts? At this stage I turned off AOD, turned off fingerprint for locking/unlocking (only use pass + face recognition) and turned off the auto brightness. With these settings the flickering/random restarting problem is gone. I just wonder whether there is a solution with potentially fingerprint for locking/unlocking off, but with auto brightness on and with at least basic AOD on. Thanks in advance for your help!

Related

[TASKER] Help with proximity sensor conditionals and wifi profiles

Hi
Tasker begginer here.
I'm having some minor issues with Tasker that I was hoping you could help me sort out:
I use Greenify and I was having a little problem with autohibernation feature in my unrooted Nexus 5: The screen has to turn on in order to automatically greenify something. This is a problem when the phone is in my pocket or facing down on the table because it conflicts with Gravity Screen (this app turns the screen off -and keeps it off- when the proximity sensor is active and the device is in a particular orientation), so when the phone is in my pocket or laying face down on a surface, Greenify can't finish its job because Gravity Screen will quickly turn the screen off.
In light of this, I disabled the autohibernation feature in Greenify and made a rather simple group of profiles to control it from Tasker. The main profile, the one that calls the "Hibernate now" shortcut from Greenify, is triggered when the screen turns off and has and If condition. This is the logic of that if:
- If
Proximity sensor: Not active
AND
Screen off
- Then
Run task
I do this to make sure that the hibernate action is not triggered while the screen is on or while the proximity sensor is active. Since Tasker doesn't have a variable for monitoring the proximity sensor, I made a profile that sets a variable (%PROX) to 1 when it's covered and 0 when its uncovered. So the if conditional uses the value of %PROX.
The problem is that if I turn the screen on WHILE the proximity sensor is active, Tasker skips the if statement (as it should), but if I turn the screen off with the proximity sensor uncovered and then cover it, it'll run the task. It's as if the profile that sets the variable %PROX to 1 does not work while the screen is off. Is this normal behaviour? How can I make this work better?
I managed to sort this out by deactivating Gravity Screen at the beggining of the task and reactivating it at the end (with a little waiting to give Greeenify time to finish), but I still want to keep my screen off while the phone is in my pocket.
My other doubt is regarding a group of profiles (that I got from here) that turn Wi-Fi on whenever I'm near two locations using the cell tower and Wifi near state in Tasker. I made some minor adjustments to these profiles, but they're still basically the same. The problem I'm having is that, most of the times, these profiles won't do anything if the screen is off. For example, I have it set to recognize cell towers near my house (and of course my Wifi connects automatically). Let's say I get home and I haven't used my phone in a while (screen off), I'd expect to see my Wi-Fi on and connected some time after I arrived, but this is not the case. It is not until I turn the screen on AND unlock the phone that I see the profiles doing their thing. I see wifi connecting, flash alerts and so on. This probably have something to do with the fact that, for some reason, my phone will not connect to a network while the screen is off. Same example, I get home with wifi on and the screen off, and I'll only see the wifi connecting after I turn the screen on (this happens with or without Tasker and with any wifi) regardless of how long I've been home.
Could it be that the near wifi profile cannot toggle wifi or can't recognize any network while the screen is off due to this bug I have with Wifi connections in my phone (Which I haven't been able to sort out)?
Thanks in advance and sorry for the long post!
Help with wifi profile
Hi, i saw your post in here and i think i can help, do you still have that problem or you managed to fix it? I think I might be able to help you

[Q] Help / Bug - Moto Display approach action sometimes not working

Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.

[GSI] [Lineage OS] [Pie] Display is not sleeping automatically after inactivity.

My display will not sleep and I have to manually switch off display. No matter which values I set at `settings -> display -> sleep` the display never sleeps. If I forgetfully leave the display on, it will stay that way till I attend to it.
I observed my device did not have this issue if I am using stock ROM.
It is a serious security, privacy and batter issue.
What is preventing my display from sleeping? What can I do?
I have found the issue. I installed a xposed module, HiddenCore. It is keeping the screen from sleeping. After I uninstalled it the display is going to sleep after the timeout.

Amazfit T-Rex -- Is the screen suppose to light-up on touch?

Hi,
I have this issue with my watch: sometimes I can light-up the watch by touching the display and most of the times this doesn't work. Is this a feature (when it works) or a bug (when doesn't work)?
Thank you!
Just few seconds after your screen goes off, it would get back on by tapping on screen. In other cases you couldn’t make it on by tapping.
I just hop on this thread about screen light.
I trying to find the setting to turn off the screen while on running activity. I notice the screen is light on entire running activity until complete. I had already enable wrist lift option to turn on the screen when i need checking the running stats.
Anyway find the setting to turn it off or perhaps sleep mode. Thank you in advance.
There is no such option in Zepp yet. Hopefully they will add it, since screen-on is very battery-consuming.
casper709394 said:
I just hop on this thread about screen light.
I trying to find the setting to turn off the screen while on running activity. I notice the screen is light on entire running activity until complete. I had already enable wrist lift option to turn on the screen when i need checking the running stats.
Anyway find the setting to turn it off or perhaps sleep mode. Thank you in advance.
Click to expand...
Click to collapse
You can turn it off by going into workout settings.
If you disable light on lift, touch to light up display will be also disabled. At least it happens on mine.

Question Any solutions to fixing occasional screen flickering when unlocking phone?

Flashed Ace2 to OxygenOS A.08 and updated to A.10, problem still persists.
Happens both with auto brightness enabled and disabled.
gavebim144 said:
Flashed Ace2 to OxygenOS A.08 and updated to A.10, problem still persists.
Happens both with auto brightness enabled and disabled.
Click to expand...
Click to collapse
Was this issue also present on ColorOS?
Disable always on display
Any unlock securities
Fingerprint, pin, code etc..
I haven't encounter any screen flashing
I have same issue, tried turning all off, did help, but i need fingerprint unlock... Autobrightness does not work at all, just dimms the screen a bit when turned on, and goes bit up when turned off, no changes in light or dark room
So i believe i figured it out, it is connected to always-on display features, which includes animation for fingerprint unlock. There is an option to turn off animation for fingerprint when display turned off, but then you have to turn on the screen before using fingerprint...
Also this phone gets pretty warm when only looking youtube or browsing, when on 120Hz refresh rate. I used setedit app to reduce it to 90Hz, much better battery life and no heat...
One last solution for the screen flickering, turn off always-on display, and turn off fingerprint animation only, it is under security/fingerprint/fingerprint animation setting, just choose none, it still litghs up the fingerprint, but has no animation, and most important, no screen flicker...
The same problem, flashing, removing the fingerprint, and using the pattern, the problem is gone
Yeah, it started again be me, so no lighting for fingerprint, and then works fine... Just turning off animation did the trick for short time
zidoon said:
The same problem, flashing, removing the fingerprint, and using the pattern, the problem is gone
Click to expand...
Click to collapse
Do you have region lock too?
jopac84 said:
Do you have region lock too?
Click to expand...
Click to collapse
Yes, I had a region lock, after contacting the seller. It was opened with TeamViewer, now 3 weeks. There are no region lock messages.
So the seller could remove it? Mine keeps saying only oneplus can remove it. Did you what he did? I am nit sure if it completely removed or just blocked... The bigger issue is these software issues, especially flickering which could damage the screen... I wonder if these issues exist on all oxygen os phones, or only on these flashed from color os
jopac84 said:
Yeah, it started again be me, so no lighting for fingerprint, and then works fine... Just turning off animation did the trick for short time
Click to expand...
Click to collapse
So turning off lighting for fingerprint fixed the problem for good?
Yes, turning off any always on display features, which includes animation and lighting for fingerprint does eliminate the problem.. i suppose it is some drivers for AOD that are incompatible. Same goes for light sensor, if you test it with software the problem is obvious, light sensor does not work at all, it is recognized, but it does not react to light changes.
Hi All,
Could anyone comment on the minimal requirements to avoid flickering and potential random restarts? At this stage I turned off AOD, turned off fingerprint for locking/unlocking (only use pass + face recognition) and turned off the auto brightness. With these settings the flickering/random restarting problem is gone. I just wonder whether there is a solution with potentially fingerprint for locking/unlocking off, but with auto brightness on and with at least basic AOD on. Thanks in advance for your help!
Hi I have the same issue screen flickering and diming after turning one the screen with in addition and the most problematic the call is blocked by a message concerning the region.
If I make a factory reset the calls work work a time then the same problem comeback
i fixed screen flicker... show fingerprint icon off, Finger print animation off, AOD off. Auto Brig off

Categories

Resources