Database Users

Top of screen and capacitive buttons unresponsive!

Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.

bigb252 said:
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
Click to expand...
Click to collapse
you are unlocked/rooted/custom rom = no warranty
anyways backup and maybe reflash the rom and see how that goes.

Hopefully you don't need to replace the digitizer... But if you do, there are lots of videos and it's reported to be one of the easier phones to do. Keep that in your back pocket as an alternative to a lengthy and costly court fight over a phone with no warranty!
Sent

Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.

Bump...
Still lost

I would suggest backup all you apps and do a complete wipe of data. I had a similar problem when I first installed Alien. This fixed the issue.

bigb252 said:
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Click to expand...
Click to collapse
I would do a wipe and reinstall. You could also fix your permissions through rom manager or cwm.
Sent from my MB860 using XDA Premium App

I had a simillar problem: WIPE through CWM solved this problem

hi, guys i had the same problem... I remember getting it shortly after updating it to the leak version of gingerbread. Since then I have flash Alien built #3 but the problem remains...
I'm currently doing a Nandroid backup of my phone so i could try flashing to cherrypie hopefully this will solve my problem cuz I'm seriously feed up with it...
do you guy's think this will help? if so any suggestions before i flash? thanks in advance...

I had this problem brand new out of the box. I just took it to the store and they gave me a new one. One other thing i noticed was the FP sensor/button was almost like loose and i had to push it in real far for it to work. Maybe its a stuck FP button...
Sent from my MB860 using XDA App

im having the same issue, i cant make the buttons work, i have wiped everything in CWM, and using fastboot also and nothing, also tried flashing different roms but the problem persists, if anyone know how to solve will be great
thanks

I think you have one file corrupted... I'll try to remember which
Sent from my MB860 using XDA App

I think it may be touchpad.cfg. try Googling that and see if you can find a clue.
Sent from my MB860 using XDA App

Try here: http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html#androidKeymapKeyLayoutMapTitle
Sent from my MB860 using XDA App

thnaks for the answear, i flashed the 10 point multitouch patch to see if solved the problem but it didnt, yesterday i reproduced the error but idk how to solve ir, im gonna make a thread to show what i did

[Q] Knock on just stopped working?

I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.

GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it

tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply

I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do

GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app

well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work

I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.

mine still says rooted so i'm kinda screwed right now

Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?

Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it

The only solution is returning the phone

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped

rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.

He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app

This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us

Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.

Double tap to wake not working anymore

Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!

malikons said:
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
Click to expand...
Click to collapse
1. if by "the latest OTA" you mean cm-12.1-YOG4PAS3AJ (About phone: Kernel version 3.4.0-cyanogenmod-gef06bf8), then that is what I have, and double tap is working just fine.
2. although i am no engineer nor software developer, i feel i could say with fair confidence it is definitely a software issue. why? because i have used custom kernels that added such a feature to phones that didn't come with it.
3. you can try disabling Display & lights | Prevent accidental wake-up; use a task manager or Apps to look at your running processes and stop any that shouldn't be running then try again.

Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk

Im on 3OH. Double tap to wake wasn't working straight after the update, but i did some fiddling like turning it on and off, played with settings and after a reboot it was working again.

Thank you sir. You just gave me a huge hope. I'll keep playing and will hopefully make it to work. Cheers,
Sent from my ONE A2003 using Tapatalk

malikons said:
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
indeed you have (supplied your version no.), please excuse my oversight.
yours would appear to be newer than mine and, no, just checked & not available for me yet. sorry i can't be of help. hope someone else could. cheers.

I'm on 3OH and it works for me

After power on or reboot, go to settings-display, disable DTTS, turn off the screen with power button, turn on the screen, enable DTTS and now the DTTS will work until next reboot or power off. This is the way I manage to make it works. I hope Cyanogen will solve this bug in next build.

I have also problems with double tap, happened already 2 times in 5 days, reboot solves the problem...

Not sure what I did but the double tap to wake feature has started to work again. I messed around quite a bit with the settings and also rebooted the phone a few times. Although, the response is quite slow, like there is some lag between double tap and when the screen wakes up. It seems to be improving in response time as I play with it more, not sure if its psychological though . Hopefully cyanogen guys will take care of it in the future update.

Stopped working for me too! Seems since the last 2 updates things have gotten bad! If it ain't broke, why fix it?
Sent from my Z1 using Tapatalk

Double tap to wake is working again! I think my phone has a mind of it's own lol!
Sent from my Z1 using Tapatalk

Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk

Double tap to wake has stopped working again! Bloody updates.
Sent from my Z1 using Tapatalk

Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk

Lol! Thanks will try that but shouldn't have to.
Sent from my Z1 using Tapatalk
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
malikons said:
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked! Lol
Sent from my Z1 using Tapatalk

Agree , we shouldn't have to but this phone isn't very stable at the moment. Sometimes I wonder why I'm even using it there's something in this phone I really like though and I believe in cyanogen

My phone was perfect when I bought it. The problem started with the countless updates I've had since then.
Sent from my Z1 using Tapatalk

malikons said:
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It also happens with CM nightlies

Thank you for saving me a lot of time and frustration

Moto X Play Camera Busy

I'm sorry if i posted it on the wrong forum but i really need some help with this. I bought it a couple days back and everything was working fine, after five days the camera gave this error (Camera Busy Unable to start. If this repeats please power off your device and restart) and ever since i couldn't get it working, i searched google for some answers where they asked me to clear the camera app's cache and data. a couple of times it worked but after a while even clearing caches and data didn't helped. I decided to go for a factory reset which helped me get it back to normal but only for a couple of days... Now I'm back to the same problem again with no clue what to do next. I have a 15 days return policy for the device which will expire tomorrow. Should i return it or this can be sorted out???
Please help me!
Edit: I kept an eye for any updates of apps conflicting with the camera by checking my camera every time i updated an app from the play store AFTER the phone was factory-resetted. But nothing unusual happened. Also before the factory reset i had the camera app updated, after the reset i did not update that app as it had negative reviews

neo4all said:
I'm sorry if i posted it on the wrong forum but i really need some help with this. I bought it a couple days back and everything was working fine, after five days the camera gave this error (Camera Busy Unable to start. If this repeats please power off your device and restart) and ever since i couldn't get it working, i searched google for some answers where they asked me to clear the camera app's cache and data. a couple of times it worked but after a while even clearing caches and data didn't helped. I decided to go for a factory reset which helped me get it back to normal but only for a couple of days... Now I'm back to the same problem again with no clue what to do next. I have a 15 days return policy for the device which will expire tomorrow. Should i return it or this can be sorted out???
Please help me!
Edit: I kept an eye for any updates of apps conflicting with the camera by checking my camera every time i updated an app from the play store AFTER the phone was factory-resetted. But nothing unusual happened. Also before the factory reset i had the camera app updated, after the reset i did not update that app as it had negative reviews
Click to expand...
Click to collapse
Leave negative reviews aside. Get it updated though play store and check if it solves the issues. You can uninstall the updates. Don't worry.

K.khiladi said:
Leave negative reviews aside. Get it updated though play store and check if it solves the issues. You can uninstall the updates. Don't worry.
Click to expand...
Click to collapse
I did that and didn't helped!
Strange thing is it comes and goes at times now

neo4all said:
I did that and didn't helped!
Strange thing is it comes and goes at times now
Click to expand...
Click to collapse
Contact moto service center. A faulty handset then maybe.

neo4all said:
I'm sorry if i posted it on the wrong forum but i really need some help with this. I bought it a couple days back and everything was working fine, after five days the camera gave this error (Camera Busy Unable to start. If this repeats please power off your device and restart) and ever since i couldn't get it working, i searched google for some answers where they asked me to clear the camera app's cache and data. a couple of times it worked but after a while even clearing caches and data didn't helped. I decided to go for a factory reset which helped me get it back to normal but only for a couple of days... Now I'm back to the same problem again with no clue what to do next. I have a 15 days return policy for the device which will expire tomorrow. Should i return it or this can be sorted out???
Please help me!
Edit: I kept an eye for any updates of apps conflicting with the camera by checking my camera every time i updated an app from the play store AFTER the phone was factory-resetted. But nothing unusual happened. Also before the factory reset i had the camera app updated, after the reset i did not update that app as it had negative reviews
Click to expand...
Click to collapse
From where did you buy?
Sent from my XT1562 using Tapatalk

I bought it from flipkart and asked for a return, they asked me to install an app called smartchck to verify the fault and today morning they called me up to check if its really faulty or not. They confirmed its a faulty device and hence I'm getting a replacement by 16th of December
I'm really happy for this and thank you for your support guys

neo4all said:
I bought it from flipkart and asked for a return, they asked me to install an app called smartchck to verify the fault and today morning they called me up to check if its really faulty or not. They confirmed its a faulty device and hence I'm getting a replacement by 16th of December
I'm really happy for this and thank you for your support guys
Click to expand...
Click to collapse
I have encountered this issue on other devices and one of the ways to fix it is by accessing the stock recovery and formatting the cache partition along with un-installing third party camera apps before doing so.
It's pointless now since you already gave it back.

neo4all said:
I bought it from flipkart and asked for a return, they asked me to install an app called smartchck to verify the fault and today morning they called me up to check if its really faulty or not. They confirmed its a faulty device and hence I'm getting a replacement by 16th of December
I'm really happy for this and thank you for your support guys
Click to expand...
Click to collapse
Good! Flipkart has 3O days return policy
Sent from my XT1562 using Tapatalk

abhish3k9 said:
I have encountered this issue on other devices and one of the ways to fix it is by accessing the stock recovery and formatting the cache partition along with un-installing third party camera apps before doing so.
It's pointless now since you already gave it back.
Click to expand...
Click to collapse
Before posting it here i have had my share of tinkering with the help of Google
Cleaned Cache data of the camera app
Installed updates of the app, uninstalled updates of the app
tried third party camera apps,removed them, factory resets, wiping cache partition from recovery, safe boot.. almost everything
when nothing worked i came to the developer haven for android

neo4all said:
Before posting it here i have had my share of tinkering with the help of Google
Cleaned Cache data of the camera app
Installed updates of the app, uninstalled updates of the app
tried third party camera apps,removed them, factory resets, wiping cache partition from recovery, safe boot.. almost everything
when nothing worked i came to the developer haven for android
Click to expand...
Click to collapse
I see. But, clearing the cache partition still worked at least temporarily (in your case).
Out of curiosity, were you using a third-party camera app to take photos?

After the New Update Exynos Model (BUGS)

Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103

None of these problems here. All that tested and works fine. Phone is super fast after update. Oh and i didnt format the phone after update

klemen241 said:
None of these problems here. All that tested and works fine. Phone is super fast after update
Click to expand...
Click to collapse
Thanks for your reply! I hope somebody facing similar problems has overcome and provide suggestions.
But Sammobile blog has also confirmed these issues.

II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.

I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.

shuvadeep said:
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
Click to expand...
Click to collapse
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.

Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.

Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
***Update***
Yes this trick is working.
---------------
Also one more question I don't know if it's my phone or everyone is facing this issue. Whenever I switch on VoLTE calls (Screenshot Attached) my phone temperature increases and battery drains.

Nitin5556 said:
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Click to expand...
Click to collapse
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.

gee2012 said:
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
Click to expand...
Click to collapse
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?

Nitin5556 said:
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
Click to expand...
Click to collapse
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..

cbotadra said:
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
Click to expand...
Click to collapse
Yes the problem is there in the May update.
Samsung should do something about this.

Nitin5556 said:
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Click to expand...
Click to collapse
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.

gee2012 said:
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
Click to expand...
Click to collapse
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic

Whiskey103 said:
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Click to expand...
Click to collapse
No, its possible that some users who do flash a rom with Odin could face some issues too but i personally don`t. I`am using the ABN bank app and i haven`t rooted for a long time now. I used to do it because of theming and getting updates/upgrades but nowadays i personaly don`t see a reason anymore to root anymore. So i can`t help you with your question.

I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).

Virgo_Guy said:
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Click to expand...
Click to collapse
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?

gee2012 said:
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
Click to expand...
Click to collapse
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.

Virgo_Guy said:
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Click to expand...
Click to collapse
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.

gee2012 said:
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
Click to expand...
Click to collapse
Erase playstore cache and you won't even notice it for a while only to re-appear after sometime.
"Less noticiable" and "very much noticiable" in my usage in 1x & .5x respectively. In ASD5 build, this transition slips like a soap.