Close

What are you looking for?

cancel
Showing results for 
Search instead for 
Did you mean: 

A72 unresponsive screen

(Topic created on: 22-04-2022 02:34 PM)
68308 Views
Members_nKESL5v
Apprentice
Options

My phone starts fine and then operates normally, but after a few minutes use the screen becomes unresponsive to touch/swipe etc. Only solution is to keep forcing a restart so I can use for a short while.

I've tried starting in Safe mode and the have the same issue.

The screen must be ok as it works for a while, but why does it suddenly become unresponsive?

Any help appreciated 

Go to solution
98 REPLIES 98
Bigslime96
Voyager
Options

No don't lose hope there will be a fix believe me

Just have some patience I'll keep you posted my friend

 

 

 

 

 

 

0 Likes
ZaiMedZ
Explorer
Options

you were auch a great help. thank you

Bigslime96
Voyager
Options

I switched to a A52s 5G

European market version so no more touch problems 

So now I got a A53 &  a A52s 5G

 

0 Likes
Bigslime96
Voyager
Options

But the fix will come for you A72 but it can take some time

 

Android 13 didn't fix all bugs

Cause my A53 still doesn't super fast charge

So I think there will be bug fixes updates coming in the near future for the A72 and other models

0 Likes
ZaiMedZ
Explorer
Options

there is finally an update for my a72, but unfortunately it doesn't solve the issue. I wonder why samsung doesn't take any action about it

Bigslime96
Voyager
Options

The December patch has bugs fixes so i think that will solve it

0 Likes
Dean81
Explorer
Options

I have also the same problem. It seems it's global. More and more users are reporting the same issues.

 

0 Likes
Dean81
Explorer
Options

Same problem.

 

Dean81
Explorer
Options

I also have the same problem. As I saw, the internet is floated with users that are reporting this problem. I tried everything, including wiping all data and cache, and still, it is not working.

 

Dean81
Explorer
Options

I have the same problem. Cannot believe that Samsung is doing nothing to fix it. I am running the latest Android 13.