Long wake delays on non oos 8.1 roms - OnePlus 5T Questions & Answers

Some 5t users noticed a very long wake delay on using 8.1 custom roms. It seems the screen is on as it reacts to touch input but stays rotaly black. Sometimes it even goes back off by itself when the phone is still locked. I lately noticed there is somekind of light below the amoled when the delay occurs. I was only able to see it when my screen was cracked due an accident. So the only logical explanation to me is that there must be somekind of black overlay preventing the user from seeing the content. Also the fact that some users never saw this bug on thair device it is possible that this issue is caused by some kind of google setting which is getting synched and the rom isnt fully compatible yet as it hasnt that implementation yet.
Many people keep saying its caused by pocket mode.
But its still present no matter what setting is used and even occurs after a fully clean installation of the rom without any changes to the default settings.
The only fully working workaround (no body is mentioning) i found out by my self, is to fully disable the lockscreen. xou have to disable swipe lockscreen too. The wake delay will never occure when there is no lockscreen at all.
I made this poll to see how many people had this problem and who didnt.
Who ever saw the wake issue by himself will understand the fact that i think all current 8.1 roms are almost impossible to use when having a lockscreen. Esspecialy at the morning it can take minutes to wake the phone no matter what unlock method/ swipe/ gesture/ password/ fp
i also provided all kind of logs and found the error lines. I showed them to all the devs of the different roms in telegram a month ago. But all we get is: "Disable pocket mode" and it clearly doesnt fix the problem.
one thing i also noticed is, that the problem started when the expanded screen feature got included (im not saying that disabling or enabling expanded desktop causes the issue)
Im not blaming any dev. Im just afraid this bug is beeing ingnored as most people never saw it happen.
I hope the dev will sort this issue as its literally the only bug preventing me from using custom roms.

Did you manage to fix the issue without disabling the lockscreen? I just got the phone yesterday and having this problem

Don't have any bugs you said above, just one issue that no body help me till now, in lastet ob4, the output sound when recording video/sound is really really low compared to the stable 5.04, I have to set the volume to the maximum level to hear clearly. I said this thing many times but may be it's just me, no one else.

do you use expanded desktop enabled on all apps? If so there's a Xposed fix http://repo.xposed.info/module/fr.merams.r.deepscreenoreo

Related

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

One X Multitouch Issues (possible fix)

EDIT: This fix may apply to you if you've already disabled "3 Finger Gestures", as this seems to be the go-to fix for these issues. If disabling or enabling this setting doesn't work (like it didn't for me), then the following might be of some use.
Just wanted to post this is a possible blanket resolution to the somewhat common issue with One X (4.0.3+) and multitouch...more specifically...the loss of touch registration on all fingers contacting the screen when one finger is lifted away. You will notice this issue immediately if you try to play any games requiring more than one finger (emulators in particular).
If this is you, do the following...
Enable "Pointer Locations" under the developer options.
Press two fingers to the screen and lift only one of them. If both 'crosshairs' vanish, restart your phone.
As soon as your phone is done rebooting, repeat the above step. If multitouch is working properly (one crosshair stays), immediately lock your phone via the button on the top right edge.
Unlock your phone, and repeat the two-finger test, then see below.
If the problem exists after you lock your screen, you might want to disable (or outright uninstall) any lockscreen modifications or apps. The biggest hurdle here was discovering that locking my screen was where the problem was beginning, and a lockscreen app (UnKeyLocker, to be exact) was causing the problem. I was frustrated as hell trying to pin down what was causing the issue to just show up out of nowhere.
Hopefully my experiences here might shed some light on why others are having similar issues.
confirmed this issue when selecting "no lock screen" onjelly bean sense. caused all the above issues preventing multi touch games fromworking properly.
omfg
badboyvtec said:
confirmed this issue when selecting "no lock screen" onjelly bean sense. caused all the above issues preventing multi touch games fromworking properly.
Click to expand...
Click to collapse
Thank you, seriously, just flashed and reflashed and updated hboot and tried fresh and everything until I found this. i was enjoying having no lock screen but it was obviously causing the problem.
Thanks again guys

[Q] Galaxy S4 Shrinking Lock on lock screen?

Hello everyone, this is my first post. So recently I have been having a certain issue concerning my lockscreen bothering me. It really isn't a deal breaker, but it messes with my OCD. So at random times, the lock and message (life companion) on my lock screen shrink as shown in the attached image. It does not seem to do anything except for bother me. The lock screen does this unpredictably, but it does not do it often. I have tried a hard reset a few times and it does not fix it. It even fixes itself after a once again, random amount of time. I am not rooted, I use basic touchwiz, basically its how I got it out of the box with some games I installed through humble bundle. Any ideas?
Pr1m4lcur5e said:
Hello everyone, this is my first post. So recently I have been having a certain issue concerning my lockscreen bothering me. It really isn't a deal breaker, but it messes with my OCD. So at random times, the lock and message (life companion) on my lock screen shrink as shown in the attached image. It does not seem to do anything except for bother me. The lock screen does this unpredictably, but it does not do it often. I have tried a hard reset a few times and it does not fix it. It even fixes itself after a once again, random amount of time. I am not rooted, I use basic touchwiz, basically its how I got it out of the box with some games I installed through humble bundle. Any ideas?
Click to expand...
Click to collapse
It's a TW bug. It can also happen with the unlock "pad lock" icon that appears on the lock screen if you have no unlock effect enabled. It doesn't affect function and a restart fixes it. Happens to me maybe twice a month. Maybe it'll be squashed with the next official release. No biggie.

[Q] Touch sensitivity issue cause?

I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.

Notification bar pull down stutter after unlocking phone

I searched forum for similiar issues but could not found anything(though there are some reddit topics).
When I wake the phone with power button or fingerprint sensor, and try to pull down notification bar, there is a stutter/lag lasts 1-2 seconds. Lets say you pull up for app drawer there is nothing but pull down and there it is.
Also wallpaper seems to affect it a little bit but it might be a placebo effect as it still stutters(light the way wallpaper seems to solve it a little bit.).
It started after Android 10 update and I even tried to clean flashing whole rom but result is same and I do not have any UI altering apps.
It seems like a slow wake up issue and may be playing with sleep frequencies might solve it but I did not root so it is not a option for me.
Is anyone else facing this ? Vanilla or custom roms/kernels ?
Yep, I have the same issue. It's pretty annoying, but I did get it to stop, for me at least it seems the new gesture navigation is causing this because I can't get it to stutter while using the 2 or 3 button navigation methods. I've had this happening since I updated to Android 10 (stable release, not beta) but after a while it just fixed itself, unfortunately my phone ran out of battery yesterday and today after I booted it up it came back to haunt me :/
Alright I got it to stop, disabling both "New notification" and "Double-tap to check phone" did it for me. Hopefully this helps.
Scythe said:
I searched forum for similiar issues but could not found anything(though there are some reddit topics).
When I wake the phone with power button or fingerprint sensor, and try to pull down notification bar, there is a stutter/lag lasts 1-2 seconds. Lets say you pull up for app drawer there is nothing but pull down and there it is.
Also wallpaper seems to affect it a little bit but it might be a placebo effect as it still stutters(light the way wallpaper seems to solve it a little bit.).
It started after Android 10 update and I even tried to clean flashing whole rom but result is same and I do not have any UI altering apps.
It seems like a slow wake up issue and may be playing with sleep frequencies might solve it but I did not root so it is not a option for me.
Is anyone else facing this ? Vanilla or custom roms/kernels ?
Click to expand...
Click to collapse
I have exactly the same issue on my Pixel 2XL, manage to fix it by disabling Google Feed on the left of the main home screen. Try it let me know if it works.
Update 1: disabling google feed doesn't work. I try to switch back to 3 button navigation and the issue gone.
I do not know how but now it is smooth everytime I try to wake phone and double tap+alwayson display is enabled. Also I tried all wallpapers and it works without any stutter.
Probably monthly updates fixed it, idk.

Categories

Resources