Related
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
konga056 said:
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
Click to expand...
Click to collapse
Time to root!
Whoa. I never even knew you could get the number pad to show up on the lock screen. I have had my lock screen sift before. It happened once about 2 weeks ago. I just reset the phone and it hasn't happened since. Is this something that keeps happening to you?
Unfortunately this happens quite often and requires me to reboot the phone to unlock it.
I had this issue once with the pattern lock as well. Shifted up and right leaving only the lower left exposed and had to reboot.
Sent from my SGH-T999 using xda app-developers app
+1 it's happened to me a few times. Had to restart phone to get it properly aligned again.
Sent from my SGH-T999 using xda app-developers app
Yup.happens here to..... once in a while
Sent from my SGH-T999 using xda premium
konga056 said:
Anyone else having this same issue where your unlock screen shifts so that not all the number pad is visible to unlock the phone? I keep having this happen to me.
I'm completely stock
http://imageshack.us/photo/my-images/827/screenshot2012080409201.png/
Click to expand...
Click to collapse
This has never happened to me on the lock screen personally, but my girl had this happen to her phone randomly one day at work and afterwards she found out her IMEI code on the phone had been blocked, had to send it back in for a replacement.
It's possible if you lose your data connection under certain conditions this may happen. I'm assuming this might also occur if the screen turns on while trying to change it's orientation as this has happened to me in certain programs which required a reboot to fix (this occurred while reading during the 5 second period between the screen shutting off automatically and the screen locking therefore the screen had not yet locked before it was turned back on).
Yes, have had it happen to be as well. Am rooted. Reboot seems to be the only solution.
Sent from my SGH-T999 using Tapatalk 2
Happened to me once too, and I'm stock, just a glitch
I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?
I don't use Instagram, so can't help with that app, sorry.
But if you go into Developer Options, and turn on "Show touch data", it might help add some more info to the discussion. It will show a trace on the screen of what the phone's touchscreen interpreted from your last tap/swipe.
It would presumably show a swipe up, and then back down, when you're getting these ghost touches that change the scroll direction. But perhaps it could also help show if swipes are interpreted the same way in other apps. It might help you learn a little more about what the phone is seeing, at least.
Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Sent from my LG-H811 using Tapatalk
Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.
shook187 said:
Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Click to expand...
Click to collapse
Apologies, first time I posted it I was thinking it was just Instagram-specific.
KL643 said:
Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.
Click to expand...
Click to collapse
Ahh good to know I'm not alone on this!
chobie said:
Apologies, first time I posted it I was thinking it was just Instagram-specific.
Click to expand...
Click to collapse
To me it looks like it is IG specific because I don't have this problem with any other app
You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk
alanchai said:
You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Done that but it doesn't solve this problem.
chobie said:
I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?
Click to expand...
Click to collapse
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....
KL643 said:
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....
Click to expand...
Click to collapse
Nope, I use Swiftkey from the beginning. Only LG stock keyboard is installed.
Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone
KL643 said:
Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone
Click to expand...
Click to collapse
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?
chobie said:
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?
Click to expand...
Click to collapse
Well this problem is only related to the LG G4 and IG for me...I don't have any other touchscreen problems with this phone. So for me I guess this is not hardware related. During the day I just had 2 small "ghost touches", way better than before. Will see how it goes the next few days...
Edit :
after a view days, it looks like it didn't solve this issue. Today I notice the ghost touches were there again in IG
Force GPU rendening under Developer options somewhat helped.
The new v10f on my Australian G4 didn't fix the issue as well.
Any updates on this? I had same issue. N this is a replacement unit after 2.5 weeks of waiting
Just day one and this ghost touch come up.
I also have this problem
Did you solve the problem?
I am facing similar issue.between...i am not using ig.
I've had this issue as well (not just IG) and sent the phone back for servicing. It was sent back to me with a report showing that they'd done a few things but the problem is still there. I'd been thinking I'd send it back in once more and ask them to have another look. I'm getting ghost touches everywhere and quite a bit, it's very annoying.
Someone mentioned there was another, large thread about this issue but I can't seem to find it, can anyone point me to it?
Hi, I posted this in a new thread yesterday as I couldn't find anything. Never thought to search for 'ghost taps' duh.
Every now and then when just doing normal things on the my phone it totally freaks out and all by it self it suddenly starts to tap random parts of the desktop, slides the pages, opens apps, closes apps, goes into calculator and a bunch of buttons are pressed randomly. It's almost like someone has hacked my phone and is trolling me by just tapping randomly on the phone.
Just today when looking at Facebook it closed the app, scrolled down notifications, data was turned off and wifi turned on.
I thought it might have been my screeen protector, bit of moisture in it or something. Took that off and still does it. Took out the battery for a minute and still does it.
It happened a few months ago then nothing for ages and now it's started again this weekend.
Thought it might have been only when connected to data but has now done it when offline.
Any one got a solution? Does a custom rom fix?
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
IncendiaryPyro said:
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
Click to expand...
Click to collapse
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
iivii14 said:
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
Click to expand...
Click to collapse
Sorry but once the bootloader is unlocked, there is no method to relock.
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
DroneDoom said:
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
Click to expand...
Click to collapse
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using Titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
tag68 said:
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
Click to expand...
Click to collapse
I got in touch with Motorola's/Lenovo's authorised repairer here in Australia. I was told the motherboard would have to be changed- around $400 so not worth it.
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
iivii14 said:
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little
Click to expand...
Click to collapse
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
iivii14 said:
and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
Click to expand...
Click to collapse
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
tag68 said:
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
Click to expand...
Click to collapse
It's about 20 seconds- I know it's not thaaaat bad but still I'd like it to fire up asap.
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
I'm uncertain if its actually a different OS- it looks like the original one but its almost like the previous owner unlocked it to get Nougat on it before it was officially released- thought someone might know from the screenshot.
iivii14 said:
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
Click to expand...
Click to collapse
You may consider adding a power block to your setup. I'm usually not charging my mobile from the car, but from a power block which has the advantage that I don't need long cables (cigarette lighter is on the other side of steering wheel). They are cheap and add flexibility.
If you charge the power block at home or from the car, maybe charging power block and mobile sometimes in parallel using dual adapter in the car, and which size of power block you use, may be worth consideration.
iivii14 said:
...- thought someone might know from the screenshot.
Click to expand...
Click to collapse
Sorry, I can't tell.
If it turns out to be some wrong version or if you just don't trust the current installation, you are free to flash an original one. Unfortunately Lenovo does not release signed official versions, at least not until now. There are some links on xda. Some of them should be the right one
iivii14 said:
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
Click to expand...
Click to collapse
You would get 'N/A' in place of the 'bad key' message. This because custom rom devs don't encrypt/sign their roms like Moto does so there is no key to compare (thus N/A).
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
I know this is old, but I'll place my own answer as an exercise on the subject, if you don't mind: "Bad Key" sign means that someone flashed an unsigned, stock but non-original OS version on your phone; if just unlocked bootloader and even flashed custom recovery on an otherwise original OS (as shipped) it must read "N/A" instead. In both cases, phone should be equally usable; however, if OTA updates can be downloaded, they won't be installed as usual. Assuming that forcefully needed, updates can be ADB or recovery sideload installed. Relocking bootloader won't be possible under given conditions. The black screen with "Bad Key" in there simply means that there is actually no bootlogo installed, probably because previous owner failed in flashing an unwarned one and just refused to keep trying. You can't get rid of the "Bad Key" sign, but you can cover it by flashing any bootlogo of your likes, either with a full white background or a custom made image with a white section that covers exactly on the sign coordinates. Creativity should be used here. No way someone try to charge you big fat megabucks for a new motherboard, since there is no motherboard failure and there's no actual need for such a radical "solution". According to humble my point of view, you just can go rooting Z Play and enjoy the hell out of it...
Sent from my Moto Z2 Play using XDA Labs
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.