Original topic:

Landscape Mode touch issue

(Topic created on: 02-11-2022 02:01 AM)
761 Views
vanshgaint
Active Level 1
Options
Galaxy A
I have an A31. And whenever I use it in landscape mode, the lower part of the screen doesn't respond to touch properly. 

I have taken every step possible. Believe me.

Today, after talking to a Samsung Customer Care Executive, I concluded it is a bug. He has agreed to note down my feedback, and include a fix in the next update. Hopefully, it is resolved.
2 Comments
cs_member8
Moderator
Moderator
Options
Galaxy A

Dear Samsung Customer,

Greetings from Samsung Customer Support!

Thank you for sharing your concern. We acknowledge your query and apologize for the same. And please follow the easy troubleshooting steps which might help to solve the issue.
If you attach a ''screen protector'' or optional accessories to the ''touchscreen'', the touchscreen may not function properly. Especially, some ''Samsung-Unapproved protector glasses'' or films only have tapes on the side edges.
When you attach such products to the device, protector film or glass may not be in perfect contact with the device and may get loose from the device.
This causes that some areas of the touchscreen may ''not recognize touch'' actions and no respond.
We recommend to use only ''Samsung-approved accessories'' and using ''unapproved accessories may cause the performance problems'' and malfunctions that are ''not covered by the warranty''.

Please follow the below steps, If the battery is non removable:

Press the power and volume down key simultaneously for few seconds.

Have you recently change ''device display'' from the service center?

In case ''non-genuine LCD/Touch panel'' is used on your device, similar problem may occur after Android OS Update.

Samsung recommends repairing your device using original Samsung parts at ''authorized Samsung Dealer/Service Center''.


Thank you for writing to us.
Warm Regards,
Samsung Customer Support.

0 Likes
Maikel7
Beginner Level 2
Galaxy A

I'm suffering from the same thing

The new Android 12 update didn't fix it

Have you gotten a solution?