crwdns2933423:0crwdne2933423:0

The Galaxy A14 is a low-end slate Android smartphone released by Samsung in January 2023 as a successor to the Samsung Galaxy A13. Identifiable by model number SM-A145 (followed by version/carrier-specific character.

Why is my screen becoming unresponsive after One UI 7 update?

I updated my phone to Une UI 7(latest update) and the screen became unresponsive after a day. On One Ui 6 this never happened

crwdns2934089:0crwdne2934089:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 1
crwdns2934285:0crwdne2934285:0

crwdns2933315:02crwdne2933315:0

Updated my phone yesterday for 7.0 update and my phone keeps freezing and can't go on anything at all so have to keep turning my phone off then back on

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0

crwdns2947414:01crwdne2947414:0:

I know i did it thinking it will delete corrupted files or something thats bugging out but it still happening

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

Disclaimer: the update descriptors are for the generic, carrier-free European region (EUX).

Apparently, if you have the SM-A145R version (MediaTek-based), the first OneUI 7 update also ships with an undocumented display panel firmware update in the A145RXXUADYGC update, which means you getting a very nasty surprise when the display's touch function simply just refuses to work.

I also had that problem showing up when I was naively thinking everything would work, but when the morning alarm started, it was literally a rude awakening to see this problem unfold.

I eventually turned off the alarm using my watch but then I used an OTG dongle + a wireless mouse to restart the phone. After several sorts of testing, I decided to simply just reset the phone to the earlier A145RXXSACYC1 (OneUI 6.1 and Android 14) firmware using Odin, and when I reset the phone I made sure to disable the system update components to prevent this from happening all over again.

Luckily the Bit revision number was the same for the last updates so you could do this rollback.

Also I've seen that there's a newer update with the A145RXXSADYI2 number but I'm not sure if it has this issue resolved or not.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Lolboy crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 6

crwdns2936753:030crwdne2936753:0 53

crwdns2942667:0crwdne2942667:0 483