Hi! Unfortunately circa once per 10 minutes or just randomly when I tap back capacitive button I feel 2 vibrations instead of one and in fact phone performs 2 back actions (like goes back 2 times in apps). I noticed it on stock OOS 4.5.14 and NoLimit rom same version. Is there any solution to it? Have you guys ever had this issue or am I alone?
Best regards
Anybody?
hi i have same problem like u . i trying everything but probably we can't do nothing I'm now on official beta oreo and this problem still exists
Wysłane z mojego ONEPLUS A5000 przy użyciu Tapatalka
I had this problem only in open beta.
Which version of nolimits are you? Nougat or Oreo one? I'm using Nougat based nolimits now, and have no problem. I think is something related to the open beta and will be solved.
Issue from the open beta.
Unfortunately I'm on NoLimits Nougat :/ and I had the same problem even on stock OOS 7.1.1
noticed same problem today
Are you using any glass protector? I thought maybe that's the reason why it happens? Or just hardware/software bug...
Have the same problem in Oreo open beta 1.
i guess it's software but cuz it wasnt present
Pshemo__ said:
Hi! Unfortunately circa once per 10 minutes or just randomly when I tap back capacitive button I feel 2 vibrations instead of one and in fact phone performs 2 back actions (like goes back 2 times in apps). I noticed it on stock OOS 4.5.14 and NoLimit rom same version. Is there any solution to it? Have you guys ever had this issue or am I alone?
Best regards
Click to expand...
Click to collapse
I think it's a software issue in some devices because in 7.1.1 I had this issue too. Randomly sometimes I feel 2 vibrations and this back 2 times in back button (it's very annoying in Instagram for example) or open and close recents faster in recents button but now I'm on Beta and sometimes I still feel 2 vibrations when I press back, recents and Home too (Home doesn't vibrate 2 times in 7.1.1) but even I feel 2 vibrations, the phone performs only 1 action in fact. I never got 2 actions when I press buttons after install Oreo Beta. I don't know if OnePlus use different brands for Display Panels but I think this problem affect some users in 7.1.1 and they are trying to fix this and it's the cause of all users gets 2 vibrations in Oreo Beta.
Thanks for the answers guys I hope it will be solved in the future
I did not notice this ... But I have buttons swapped under buttons settings, and double tap action is set open last used app...
EDIT:
I test both buttons and this is not happening on either of them... just for test can you make setup like mine and test it... Wondering if that fix your issue...
I can report that I moved to AOSiP and this problem doesn't appear here. Once or twice in the last 24 hours I felt 2 vibrations while tapping a button but "double action problem" has never occured
Related
Hey guys,
I registrated for this issue, but still I want to thank all of you here. I've found help here for many many years before, so thank you for that .
Now I need to describe my problem to get some help: I've bought my Z1 October last year and suddenly since yesterday the fingerprint reader feels just kinda broken. What I mean is that on Cyanogen OS 12.1 (stock) the fingerprint reader just stopped working completely. I then flashed CM13 (newest nightly) and here it is working, but only when I wake up the phone with the ON/OFF button, and not the home button with the integrated fingerprint reader.
When I use the ON/OFF button everything works perfect, but the home button doesn't work in like 9 out of 10 times. Now I wonder if the fingerprint reader is just broken already or if this is "just" some software issue. But I don't really think that the fingerprint reader is broken, because why didn't it work at all on Cyanogen OS 12.1 but now just not the home screen? I don't know.
Is there any way to test if the fingerprint reader is actually broken? Or another way to fix this? I really, really like the Z1 so far, but this really bugs me.
Thanks in advance .
PS: If this issue was already a topic I'm sorry, i didn't find it. And forgive my english, it's not my mother tongue.
Now that's funny.. exactly the same thing happened to me. All of a sudden, fingerprint reader stopped working yesterday, without having installed an update. When I now try to active fingerprint, it sort of crashes, vibrating for a long time and speeding through the ' fingerprint tutorial' as if I were touching it, which I'm not. This, combined with some random rebooting and crashing. Just did a factory reset and doesn't solve the problem. Not sure whether the reader is broken, but I'm getting pretty fed-up with Cyanogenmod.
Ok that's very interesting. Kinda sounds like it would be a broken update or something, even tho we both didn't install an update. Very strange.
Which OS are you running right now? Is it the same you were running when the issues started? I kinda thought about trying out ZUI, but I've heard it's kinda complicated to get it to work and to go back to CM if required.
running CM12.1. Guess I just wait and see if 13.0 solves the problem.. if they are ever gonna finish that this year. Phone is a lot quicker after the reset btw.. so that is recommendable
Yes, maybe I will try out CM12.1 later today and reply if it worked for me or not. At least CM13 is working like half the time.
Edit: Where can I download the CM12.1 stable? I can't find it on the CM site.
Many people including me are having this problem. We can't find a solution: it's almost one month since fingerprint stopped working.
Home button stopped working too, so I have to use onscreen buttons now. Really frustrated
Inviato dal mio Z1 utilizzando Tapatalk
simoneser said:
Many people including me are having this problem. We can't find a solution: it's almost one month since fingerprint stopped working.
Home button stopped working too, so I have to use onscreen buttons now. Really frustrated
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
OK, that's very strange and very frustrating. Gladly my homebutton is still working. But this sounds like a serious issue. And it sounds like a software issue.
Are you using Cyanogen OS?
I am on cyanogenmod 13. I tried to switch between many ROMs, tried to go back to cyanoOS with QFIL but had the same problem you mentioned (phone fast skipping the initial configuration of fingerprint, or always vibrating)
After some days, home button stopped working too (it works 1 time out of 6-7)
Inviato dal mio Z1 utilizzando Tapatalk
simoneser said:
I am on cyanogenmod 13. I tried to switch between many ROMs, tried to go back to cyanoOS with QFIL but had the same problem you mentioned (phone fast skipping the initial configuration of fingerprint, or always vibrating)
After some days, home button stopped working too (it works 1 time out of 6-7)
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
Damn, that really sucks. I hope this won't happen to my phone too. I was really happy with the Z1 until now, but why tose issues started with so many people now?
Did you think about sending it back?
I don't really know!
Yes, as soon as I'll get a spare phone I'll send it to China (I've ordered it from Gearbest so I will have to wait for months to get it back)
Inviato dal mio Z1 utilizzando Tapatalk
simoneser said:
I don't really know!
Yes, as soon as I'll get a spare phone I'll send it to China (I've ordered it from Gearbest so I will have to wait for months to get it back)
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
Damn, bad news. Well I wish you the best with your Z1!
Hey
I just have an status update if anyone else is having this problem and finds this thread.
After my Z1 having terrible battery life on CM13 I went back to the stock Rom (Cyanogen OS 12.1). Right after I've used the Zuk Z1 root tool (to find here on xda) to go back to stock my phone told me that there is a new official update. Right now I'm running stock Cyanogen OS 12.1 YOG4PAS60J. I've just tried out the fingerprint reader again and now it works without any troubles. So it seems like this was just a software issue.
I will try it out more detailed the next days but for now it works wonderful. I hope this is helpful for someone who is having the same problems.
brotbret said:
Hey
I just have an status update if anyone else is having this problem and finds this thread.
After my Z1 having terrible battery life on CM13 I went back to the stock Rom (Cyanogen OS 12.1). Right after I've used the Zuk Z1 root tool (to find here on xda) to go back to stock my phone told me that there is a new official update. Right now I'm running stock Cyanogen OS 12.1 YOG4PAS60J. I've just tried out the fingerprint reader again and now it works without any troubles. So it seems like this was just a software issue.
I will try it out more detailed the next days but for now it works wonderful. I hope this is helpful for someone who is having the same problems.
Click to expand...
Click to collapse
Can you tell me what did you do step-by-step please? I am still on original YOG4PAS60J by air.
Is "Zuk Z1 root tool" this prog?
m4e2 said:
Can you tell me what did you do step-by-step please? I am still on original YOG4PAS60J by air.
Is "Zuk Z1 root tool" this prog?
Click to expand...
Click to collapse
Hey, yes of course I can do this. And no, the Z1 root tool I meant is another one. I will link it in the steps.
1) I've flashed CM13 Nightlies, later I've clearly flashed the CM13 Snapshot
2) Because the Fingerprint Reader wasn't really working on CM13 either and I had terrible battery life I went back to Stock Cyanogen OS 12.1
3) To archieve that I#ve used this tool from Mauronofrio: http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
4) I used the instructions in the linked thread to go back to Stock
5) After everything went fine I was setting my phone up when I got a popup for a new Update OTA: YOG4PAS60J
6) I've installed that
7) After like 2 or 3 days I tried out of curiosity if maybe the fingerprint reader works again, and it does.
That's all I've done. After some testing with the fingerprint reader I think my fingerprint reader has still a little bit loose contact, but it works pretty good. So I think it's a mix out of an hardware and an software issue.
I hope I could help you a little bit.
EDIT: It started to not work anymore. I just said "**** it" and disabled the fingerprint reader now. Im very sure now that it's only a hardware problem.
This is exactly what happened to mine! In about 2 days it started lagging a lot and almost stopped working. When I tried to set new fingerprints, it just got stuck in the screen. Did a factory reset (including user data!), tried to set fingerprints and on the 1st try, it just speeds through the wizard without me touching the fingerprint reader, on the 2nd, it starts to vibrate like I was pressing it and I've to force the shutdown to stop. Pretty disappointed with this right now. :/
brotbret said:
OK, that's very strange and very frustrating. Gladly my homebutton is still working. But this sounds like a serious issue. And it sounds like a software issue.
Are you using Cyanogen OS?
Click to expand...
Click to collapse
If you found a fix do post it. I've the same issue of fingerprint not working after some days of updating to the latest update. Home button does works though
Post Preview:
My fingerprint stopped working and it is not resetting whenever I try to reset it vibrates for long time and speed up the screen also i tried to factory reset the device and this also not working i am running on cyanogen os 12.1 plzz help me
Hey people.
I had the same problem few days ago. It happened when i restored the stock rom back through twrp. Now i have flashed dirty unicorns 6.0 and the finger print seems to be working fine now.
the problem is in hardware button on my zuk fingerprint stopped working around 1 year ago i tried installing various softwares as zui or cm13 but it did not worked so i have use it only as home button then around half year ago it just stopped working i decided to buy it for 10 dollars from ali express after dissambelling the phone and installing it works now with all functions so the problem is only hardware maybe installing some zip folder will help you for a while but it will stop working soon by the way dissasmbeling the screen was wery hard i have done that with a heat pistol on 300°c
I thought it might be a sensitivity issue because I'm coming from a N6 where I barely touch the screen and it registers. I did some testing and turned on show visual feedback for taps in developer options and I started tapping on the screen in random places every 2 seconds and on average every 5th tap it didn't register and sometimes it's the second and I had issues sometimes where 3-4 taps in a row in different places wouldn't register. For me it's not isolated to certain parts of the screen like many people have found, for example only on edges.
My sample size isn't very much but I've figured out that the majority (or only UI elements because I haven't tested enough) tapping on or around UI elements such as toggle settings in the developer options, any app (swiping/scrolling in apps too) that this issue occurs. When I moved an app icon to create a new screen and started testing I never had any registration issues(visual feedback for taps and long pressing to bring up the wallpapers/widgets/home settings intermittently between taps)
So is this a hardware issue, software UI or maybe a mix of both? I don't know enough about touch screens and android. I don't want to RMA if it's software but I do if it's a hardware issue. Does anyone have any insight on this?
So I did a factory reset and it's working perfectly now. I don't know what was causing it but it's good to know it wasn't hardware
I have the same issue, fingers crossed the upcoming update will fix this.. Mostly its a software issue (or hoping so), but I've seen few complaining about this..
I have the same issue. Its most likely a software issue that can be addressed through an update.
Mine seems to come and go. Sometimes it's fine; sometimes I'm having the same issues you're describing.
I was thinking last night it seemed like every once in a while a double tap is required, after idling for a few seconds. This to me sounds like a driver issue that could be fixed.
Today however I'm thinking it might have something to do with cold dry fingers, as I was having it outside but it's totally fine now indoors.
Can't really put my finger on it yet. Gonna give it a few more days before I think about an RMA.
Any of you guys using SwiftKey beta?
edit: are you on 8.0 or the 8.1 preview?
Just got my xl today and I have this issue. It's just randomly around the screen and not in any specific area.
I believe my phone is not recognizing vertical sliding if it is diagonal, versus the same diagonal slide on my 6p is recognized. Not sure why this is happening but I believe it is intentionally being done because if I touch same spot and closer to vertical up and down, it recognizes it.
Ferenczy68 said:
Any of you guys using SwiftKey beta?
edit: are you on 8.0 or the 8.1 preview?
Click to expand...
Click to collapse
I am using swiftkey Beta on 8.0 and all functioning great
I don't know if this is related but I've been using accubattery and after I did a factory reset I didn't install it at first and everything was working great then I installed it and after awhile I noticed the issue come up again. I uninstalled it about an hour ago and did testing and the issue is gone.
I'm on 8.0
Issues came back even with accubattery uninstalled
I have the same problem. When trying to scroll a web page in Chrome, I have to touch twice to get the touch to register. Also having trouble with the long presses.
I'm on 8.0
I have Swiftkey (not beta)
I do not have Accubattery
I'm having major issues with this all of the sudden today. Something isn't right. Ugh - one issue after another.
I made a video of my issues:
https://www.youtube.com/watch?v=tfnE_Cv-s20
Sometimes, when trying to scroll a web page in Chrome beta, I have to touch twice to get the touch to register. Saw this on 8.0 and now on 8.1.
Neverendingxsin said:
I made a video of my issues:
https://www.youtube.com/watch?v=tfnE_Cv-s20
Click to expand...
Click to collapse
That's horrible. I opened my gboard in chrome and it doesn't do that for me but it will do that swiping/scrolling, randomly typing and with GUI elements sometimes. Multiple times in a row to where i have to just stop tapping and wait a second or two and tap again.
I'm going to try using the 8.1 dev preview to see what happens
I'm having this issue too
Sent from my Pixel 2 XL using XDA-Developers Legacy app
dekciw said:
That's horrible. I opened my gboard in chrome and it doesn't do that for me but it will do that swiping/scrolling, randomly typing and with GUI elements sometimes. Multiple times in a row to where i have to just stop tapping and wait a second or two and tap again.
I'm going to try using the 8.1 dev preview to see what happens
Click to expand...
Click to collapse
I get the same thing while typing, i'll think i tapped something (because I know i did) but it won't register. Extremely annoying and all 3 phones I've gone through had the same issue, getting tired of RMAing
I mainly get this problem with gboard and the home button. It will double click a lot when I only touch once
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I'm also seeing this randomly as well! This is my biggest bug right now...
I installed the 8.1 dev preview and right off the bat it's working perfectly but let's see what happens in the next few hours. I don't understand why it's fine then all of a sudden not. It's completely ridiculous
Make sure you guys are enabling "show taps" under input in the developer options because when you tap and the visual feedback doesn't show then it's not registering. Enabling "pointer location" helps make it more obvious also
dekciw said:
I installed the 8.1 dev preview and right off the bat it's working perfectly but let's see what happens in the next few hours. I don't understand why it's fine then all of a sudden not. It's completely ridiculous
Make sure you guys are enabling "show taps" under input in the developer options because when you tap and the visual feedback doesn't show then it's not registering. Enabling "pointer location" helps make it more obvious also
Click to expand...
Click to collapse
I'm on 8.1 still having these issues
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Touch sensitivity of top part of screen is very low, this leads missed "notification pull down" if done quickly.
The below video shows the issue. One can see that the pointer trace does not happen at the top part of the screen, when done quickly. But if swiped slowly, the trace happens from the top, this means, that during quick swipes, the top portion touchscreen is unresponsive, that leads to missed notification pull down.
Video
Any one with similar issue?
I have already submitted this as issue using mi feedback app.
Probably just your phone. Mine's doing well.
Are swiping down from off the screen mate?
Sent from my Mi A1 using Tapatalk
This was an issue on my previous Redmi Note 2.
Whit A1 I'm not experiencing this problem.
robgee789 said:
Are swiping down from off the screen mate?
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Yes the normal swipe action of notification pull down, but just doing it quickly.
Sent from my Mi A1 using Tapatalk
Hey man, i also got that problem when I was using Pixel Launcher. At first it wasn't an issue, everything was fine, but around 2 weeks after using it, i got the same problem as you too, in fact it was yesterday. Today I'm still seeing the issue but not as bad as with the Pixel Launcher, i think something else is triggering this issue. So, maybe you can try to use the stock launcher first? (I'm also still figuring out what the problem is)
Best regards
Did you test it with stock Launcher too?
ashjas said:
Touch sensitivity of top part of screen is very low, this leads missed "notification pull down" if done quickly.
Click to expand...
Click to collapse
I watched your video. I am using Lawnchair as my daily driver so I switched to stock launcher to test it, because in Lawnchair this couldn't be a problem (you could pull down notification shadow from anywhere on the screen). But even with stock launcher I couldn't confirm this and I tried it really hard with hyper sonic fast pull downs.
BTW Lawnchair has its own issues, I opened one for similar problem: Unresponsive top row.
Hello ashjas
I purchased brand new Xiaomi Mi A1 and I am having exactly the same issue as on your video. Did you get it fixed?
Hello guys,
I bought my 6T a few days ago and have been noticing some annoying software issues:
1. When I unlock my phone it doesn't take me to the application I was using before I locked the screen; it takes me to the home screen.
2. The recent applications keep getting cleared even though I've turned the battery optimisation off.
3. In the lock screen when there's a notification, the ambient display shows the notification but touching on it doesn't turn the screen on. You have to hit the power button or unlock the phone in order to check notifications.
There a couple of other minor issues like apps crashing and then restarting that don't happen too often.
Just wanted to check if others are facing these issues as well and if someone has any solutions.
Those sounds like bugs in the OS, I say this since I'm experiencing the same issues on my OP6 running Open Beta 6 (based off OS 9.0.4 for the 6T).
Have you submitted a bug report on OnePlus feedback page? This way it will get the right people in front and get the issues resolved.
Note2Lover said:
Hello guys,
I bought my 6T a few days ago and have been noticing some annoying software issues:
1. When I unlock my phone it doesn't take me to the application I was using before I locked the screen; it takes me to the home screen.
2. The recent applications keep getting cleared even though I've turned the battery optimisation off.
3. In the lock screen when there's a notification, the ambient display shows the notification but touching on it doesn't turn the screen on. You have to hit the power button or unlock the phone in order to check notifications.
There a couple of other minor issues like apps crashing and then restarting that don't happen too often.
Just wanted to check if others are facing these issues as well and if someone has any solutions.
Click to expand...
Click to collapse
The device and oxygen Pie is pretty new so you gotta give it some time for software update.
Also do you have the tmo variant or the unlocked version?
Because the tmo variant has not gotten any software updates yet.
y2k1ltd said:
Those sounds like bugs in the OS, I say this since I'm experiencing the same issues on my OP6 running Open Beta 6 (based off OS 9.0.4 for the 6T).
Have you submitted a bug report on OnePlus feedback page? This way it will get the right people in front and get the issues resolved.
Click to expand...
Click to collapse
That's a fair point. I haven't done it yet, but I will. Thanks for suggesting it.
harpin14789 said:
The device and oxygen Pie is pretty new so you gotta give it some time for software update.
Also do you have the tmo variant or the unlocked version?
Because the tmo variant has not gotten any software updates yet.
Click to expand...
Click to collapse
I have the unlocked version. You're right it's still pretty new and OnePlus might have jumped the gun a little bit in releasing this in an attempt to be there first OEM to push Pie. Let's hope they fix this in a future update.
I think I finally figured out why the recent apps get cleared. OnePlus has set the background app limit to 16 which is retarded. I remember it was the same on the OnePlus 3 as well. And of course you can't just modify the build.prop file to increase this limit.
It's things like this why we need root. I'm probably gonna have to do it soon if I don't find a way around this.
Hi, Issues with keyboard responsiveness started after updating to Android 11 Global - buttons located in the edges of the screen got a delayed reaction to pressing or are just getting stucked. This issue is also reproducible for other oneplus 8 but somehow nobody else mentioned this issue before.
Could u please check if this issue is reproducible for you? Please check the video that i have attached - it shows that buttons “Q” and “P” are pressed with delay
The problem is completely absent on the OOS 10.5.9 IN21AA firmware version, but it has already appeared in the OOS 10.5.12 IN21AA version.
Same for me here! The keyboard is really sluggish.
Also, a little here as well....
Are you using QHD? Try FHD and as silly as it sounds, give the screen a thorough clean and wipe.
I'd high sensitivity on?
I am using FHD and also same issues