Develop Bugs

NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns

NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?

the only time I've had that happen to me is when I use a cheap charger I've got and yeah the screen just skitses out. I am using a hero tho but this is the first time I've seen anyone else encounter this so I thought il'd churp in.

I had something similar only once.
The notification bar went mad. It was flicking up and down constantly without me touching the phone at all.
I had to pull the battery to fix the problem.
Hasn't happened since.
Fon22

Happened to me also when loading a ROM in Nesoid.

So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?

quicksite said:
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
Click to expand...
Click to collapse
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.

Brilliant, Alex... You got right inside my head and answered exactly what i was trying to ask.... the physics of the system.
I'm okay with little glitches here and there, and I am sure I will learn to avoid proximity issues that tend to trigger these mis-fires... just as I learned to adjust my tap-key behavior in typing on the on-screen keyboard on capacitive screen vs all the resistive screens I had used before on Windows Mobile, where fingernails could & would engage the resistive screen -- vs learning that the bottom surface of the finger has to make contact on the keys on capacitive screen... (sorry i am USA and we still resist the world's metric standard, so i don't know the equivalent distance in cm,)... but it's over a 1/4-inch of an upward shift in the position of one's fingers above the capacitive screen from the tip of the fingernail.
But once you train your senses to activate the keys sensors properly, the finger impact behaviors of resistive screens goes away after a while (at least for me)
(oh, btw, I ordered the new HTC capacitive stylus which is a couple of months old now, but is an official DESIRE accessory, so that will be an interesting experience... the thing i miss most about the resistive screen and stylus was being able to scribble notes really fast, way faster than i could ever type -- and draw pretty detailed images or maps and directuions for people. so it will be interesting to see the granularity of control the capacitive stylus will give)
So thanks very much for giving me the exact level of detail I can process as a lay person.. and for assuring me, as the rest of you have as well, that this apparently comes with the territory of this phone -- and therefore should not be seen as a defect. Because i sure as hell didn't want to go shipping this phone back. I can live with an occasional spazzoid misread of intended impact spot on screen...
And, fnally, this was funny -- re the different degree of touch we all consider "normal" --
The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
thanks!
Alex_w said:
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse

I was thinking it is softwarerelated. The bar remains halfway the screen, is in the layer below the active app, and jumps to front upon touching the screen.

I have the Problem, too. And that since Monday. I went mad since yesterday evening so i tried to go back to stock, unroot and all.
But the problem is still there.
How can i fix it? Or is my Phone damaged?!
The Notification Bar scrolls down without touching the display and then freezes the phone. so i must lock the phone and relock it and then i can use the phone but after a short time the same problem came back!!

So I reckon you're an undertaker for a living?
Sent from my HTC Desire using Tapatalk 2

erklat said:
So I reckon you're an undertaker for a living?
Click to expand...
Click to collapse
Sorry but i don't understand what you mean
The problem makes me crazy because i have now the stock rom because i thougt it was an issue due a custom rom or a kernel or something.
If you can help me please do that, this problem robs me to sleep
But i havent the Desire. I Have the HTC EVO 3D GSM

19Marc89 said:
Sorry but i don't understand what you mean
Click to expand...
Click to collapse
lol digging up the dead
Sent from my HTC Desire

Sorry but I do not understand the background of your information which is in context with my problem of the notification bar.

@19Marc89 He meant that you responded to a an old (dead) post. Listen, I'm trying to recondition an old Motorola Milestone (Droid) with a crazy touchscreen problem, whose cause I believe I've narrowed down to static electricity - can you do me a favor and try stroking the glass side of the phone lengthwise in one direction down your sleeve, preferably if you have a wool sweater on? Call me crazy, but this works for me, at least temporarily. I posted more here:
http://forum.xda-developers.com/showthread.php?t=1041943&page=5

install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
quicksite said:
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
Click to expand...
Click to collapse
REPLY :
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!

I know I am many years late but did you somehow manage to solve this problem?

[Q] Problems with 5.1.1

My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?

5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.

nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.

Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.

Device wake issues (power button ignoring first press)..

Hi,
I've had my M9 for a couple of weeks now, and slowly getting it to work how I want it to. One thing nagging me is this weird issue I have with waking the device from sleep.
I have tried to disable all the gesture/smart wake features (double tap the screen, etc). The issue I'm having seems to relate to the light and/or proximity sensor. It seems (and I haven't been able to find any info on this, online or on the phone) that there is a feature which will enable the device to wake up when being picked up or taken out of my pocket. This doesn't always work, but sometimes it does. When I pull my phone from my pocket, it will sometimes wake up. When I glide my finger over the front camera & light sensor, it will sometimes wake up. This is a minor annoyance, as I would like to only be able to wake my device by hitting the power button.
It gets really annoying when these 'gesture' wakes start to interfere with the power button wake. For example (and this is happening more often than not), when I pull my phone out of my pocket, the phone is off, then I hit the power button once, and the phone still doesn't wake. Hitting the power button a second time will wake the device. It seems to me that the smart waking is some how interfering with the manual waking.
Is anyone else seeing this behavior?
Any suggestions for a solution?
Thanks a lot for any help.

This is really odd considering the M9 doesn't support air gestures. Sorry, I have no solution, but is it possible you may have installed an app that may be causing this?

I would think two button push would be the normal, otherwise you could accidentally hit it once and turn the screen on. Do you have Ambient display and pocket detection all turned off ?
Gravity Screen in the play store gives you total control of all that stuff

That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?

[email protected] said:
That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?
Click to expand...
Click to collapse
Settings / Display & Gestures / Ambient display (Wake screen when device is picked up or notifications arrive)
Pocket Detection is part of some Rom Tweaks (insertcoin & viperOne if i remember right)

Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.

[email protected] said:
Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.
Click to expand...
Click to collapse
Yes I have it, but I'm on LeeDroid right now. He adds so much stuff i forget whats "custom" and whats stock

Got the same issue
The power button will ignore the first push while standing by for a long time. Thought it might be caused by apps like greentify?

Hi Ducati, is that a fact or is that just how you understand it? Seems strange that that would be intentional. But it definitely seems to be the case.
I do not have greenify installed either.
Do you get similar behaviour on your One?

After a bit more testing. I can confirm that there are some sort of air gestures on this device. I can wave my finger in front of the front light sensor/camera, and the device will wake.
This doesn't happen all the time, I am not always able to reproduce this. But right now, it is happening. Can anyone else reproduce this?
http://somevid.com/N1OnU8JS

I have the same issue on my M9. Glad I found this thread. Thought my power button was defective.
I can't activate any gestures by waving my hand.
I think it's happening mostly when waking from deep sleep.

I know it's an old thread, but I just installed CyanogenMod 12.1 and I guess my google-fu is rusty. I find that if I hit the power button in quick succession (double click) it turns off the phone. Anyone know how I can stop this?
By quick succession I mean multiple times within 20 seconds

Bottom edge of touch screen not responding

So, last week I bought the P2. So far I'm very pleased with the device. Next to the known audio sync issue I ran into one other thing that still bugs me after a week of use: the bottom edge of the touch screen doesn't seem to respond to touch. When I slowly slide my finger from above the screen over the edge of the screen, it immediately picks up my finger, even when only a small part (maybe a millimeter) touches the screen. When I do the same thing at the bottom of the screen, it will only start registering my touch when I'm about 6mm in.
6mm doesn't sound like a lot, but it's enough to make me miss-touch the space bar half of the time. I thought I'd get used to it, but it is still quite annoying... Is this the same for all P2's? I'd like to hear if anyone can confirm this.

Herjan said:
So, last week I bought the P2. So far I'm very pleased with the device. Next to the known audio sync issue I ran into one other thing that still bugs me after a week of use: the bottom edge of the touch screen doesn't seem to respond to touch. When I slowly slide my finger from above the screen over the edge of the screen, it immediately picks up my finger, even when only a small part (maybe a millimeter) touches the screen. When I do the same thing at the bottom of the screen, it will only start registering my touch when I'm about 6mm in.
6mm doesn't sound like a lot, but it's enough to make me miss-touch the space bar half of the time. I thought I'd get used to it, but it is still quite annoying... Is this the same for all P2's? I'd like to hear if anyone can confirm this.
Click to expand...
Click to collapse
Same problem here, it seems that when you hide the on-screen buttons that area is effectively useless. On 6.0.0 and 6.0.1. I have no idea how to fix, but you definitely aren't the only one

i too had experienced same problem, while playing Asphalt extreme, it doesnt let me press the NEXT button

Well, I'm glad that my phone isn't broken. Let's hope it's a firmware issue and not a hardware one!

Check your keyboard set up. I have hidden buttons and the whole Spacebar is active to touch. Right to the bottom of the visible Spacebar. There is a gap slightly narrower than the Spacebar beneath it at bottom of screen. This does not respond to touch. My advice would be to be a little more accurate with typing . As there is no way to fix this and keep hidden buttons. Gesture home button, hidden navigation buttons and big battery are best features of this phone!

I wouldn't even have noticed this issues if you hadn't pointed it out. It's present, but it doesn't really bother me too much. Especially since I switched from my G4 which had me miss the spacebar and hit the home button way too often lately for no particular reason. Not having those softkeys is still an upgrade for me ^^

i am sure its definitely a SOFTWARE problem, official lenovo forms also has a thread about this problem..
so lenovo would patch up in their next update

It is software, but it won't be patched. There needs to be a certain amount of space at edge of screen (dead zone) to allow swipe up of navigation buttons but also avoid unintentional swipe ups. They could tweak the size of the dead zone I guess, but I don't see it happening. Alternatively they give an option to totally deactivate on-screen navigation buttons and accept some apps may have issues.... I guess it is a trade off. As I say, I cannot see Lenovo changing it.

helppme said:
It is software, but it won't be patched. There needs to be a certain amount of space at edge of screen (dead zone) to allow swipe up of navigation buttons but also avoid unintentional swipe ups. They could tweak the size of the dead zone I guess, but I don't see it happening. Alternatively they give an option to totally deactivate on-screen navigation buttons and accept some apps may have issues.... I guess it is a trade off. As I say, I cannot see Lenovo changing it.
Click to expand...
Click to collapse
The last option would work for me I guess, although you do need the navigation buttons sometimes for older apps that still use the menu button.
nandakis4 said:
i am sure its definitely a SOFTWARE problem, official lenovo forms also has a thread about this problem..
so lenovo would patch up in their next update
Click to expand...
Click to collapse
Ah, found it. They say it's required for the "swipe up" gesture... Seems strange to me, but let's wait for another reponse from Lenovo...

I have the nav bar enabled all the time so I didn't noticed this issue.

But why there is no option to turn the swipe function off, because we can use the full functionallity with the home button?..

kevincash said:
But why there is no option to turn the swipe function off, because we can use the full functionallity with the home button?..
Click to expand...
Click to collapse
already complaint at lenovo forum but seems like they will ignore it
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/lp05_en/page/1/thread-id/872
if any of the user here experience similar problem, please raise your concern at the thread at lenovo forum.

Herjan said:
So, last week I bought the P2. So far I'm very pleased with the device. Next to the known audio sync issue I ran into one other thing that still bugs me after a week of use: the bottom edge of the touch screen doesn't seem to respond to touch. When I slowly slide my finger from above the screen over the edge of the screen, it immediately picks up my finger, even when only a small part (maybe a millimeter) touches the screen. When I do the same thing at the bottom of the screen, it will only start registering my touch when I'm about 6mm in.
6mm doesn't sound like a lot, but it's enough to make me miss-touch the space bar half of the time. I thought I'd get used to it, but it is still quite annoying... Is this the same for all P2's? I'd like to hear if anyone can confirm this.
Click to expand...
Click to collapse
Have u checked through Lenovo app in the phone? Run diagnostic through the app, if any point in the screen doesn't register the touch, you should be able to claim warranty with Lenovo. I had the same problem, and Lenovo service centre gave me a new unit....

solazz said:
Have u checked through Lenovo app in the phone? Run diagnostic through the app, if any point in the screen doesn't register the touch, you should be able to claim warranty with Lenovo. I had the same problem, and Lenovo service centre gave me a new unit....
Click to expand...
Click to collapse
That is not the problem. And if you try the touch screen test in the Lenovo app you see the the bottom area of the screen is white and it cannot be tested. What he is talking about is not a hardware error, it's just a poor implementation in software.
---------- Post added at 01:33 PM ---------- Previous post was at 01:23 PM ----------
Is there anyone in here that have root that have tried Immersive mode? There are apps in Play store that lets you activate this. Does this help the bottom of the screen to register touch?

Is any custom rom resolve this problem? Because I will unlock my bootloader and root my phone to increase the headset volume.

Lennis01 said:
That is not the problem. And if you try the touch screen test in the Lenovo app you see the the bottom area of the screen is white and it cannot be tested. What he is talking about is not a hardware error, it's just a poor implementation in software.
---------- Post added at 01:33 PM ---------- Previous post was at 01:23 PM ----------
Is there anyone in here that have root that have tried Immersive mode? There are apps in Play store that lets you activate this. Does this help the bottom of the screen to register touch?
Click to expand...
Click to collapse
I understand that there's potential issue with the software as many has reported as well... However it's good to confirm that it is not a hardware issue... In marshmallow, you should be able to test it, it won't be whitish... I tested before when I'm claiming warranty for my previous unit... Same issue, space bar does not respond...

how gps navigation works on p2 via google maps ? Does it work like apple phones , I mean accurate most of time ?

Himmi23 said:
how gps navigation works on p2 via google maps ? Does it work like apple phones , I mean accurate most of time ?
Click to expand...
Click to collapse
From my experience, it's accurate and locks very fast...

Unresponsive screen bottom

Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?

Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk

Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue

winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?

I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.

Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem