01-03-2022 10:44 AM - last edited 02-03-2022 11:25 AM
I received my Galaxy S22 Ultra 512GB, Exynos version, over a week before official release date. As I was using the phone I discovered several bugs with my unit, screen blackouts, occasionaly freezes, conversations loosing sound, phon not reachable over GSM network even if my signals was good. I decided to wait until official release date to see if new software would be released. On the 25th Samsung released new firmware for my phone, and I did a complet factory reset after new firmware was installed. I am now on firmware S908BXXU1AVBF and fresh phone setup.
My screen problems seems to be gone, but GSM network issues are still there. Several times I have been made aware of that my phone can not be reached by callers, even if phone is showing signals. Solution, reboot. Turning on and off flightmode did not help. Also I am experiencing sound dropouts during calls, call is not droped but sound oth ways are lost, duration 10 - 15 seconds. Also when making a call the phone uses much longer time to set up the call than other phones I have had. Calling my self from other phones give simular results, setting up phone calles to my Galaxy S22 Ultra take much longer then calling others.
Have been in contact with Samsung support, but there is no help to get there. Try this, try that, over and over again. I am starting to loose my patients now, and its impossible for me to have a phone I dont know if I can be reached at, and when I manage to set up a call, sound is lost several times during the call.
16-11-2022 07:35 AM - last edited 16-11-2022 07:38 AM
I have done the following basic stuff; airplane mode toggle, restart, network setting reset, factory reset and nothing really changed. So i logged in to Samsung for an appointment.
I brought mine to a Samsung Service Center last Saturday morning and they tested it. Confirmed very low to zero signal, cannot call or text and no internet also. They repaired it by changing a sub-board (IF SUB PCBA ASSY - SM-S908E; SM-S908E, SEA, DA). They also said they changed the kit that seals the unit to maintain the water resistance feature/claim. So far, all is good.
18-11-2022 09:12 AM - last edited 18-11-2022 09:16 AM
Hi,
I'm in France and did updated to the last patch (Android 13 + OnuUi5) and it worked fine a couple of weeks, until I rebooted my phone few days ago.
I can confirm that the problem is back again, even with the last update...
😞
The mother board issue/replacement seems to be the only escape
18-11-2022 09:31 AM
Hi Rekma31,
After the new update of november ?
18-11-2022 09:32 AM
it is a hardware issue. No basic stuff or software upgrade will solve this issue permanently.
18-11-2022 09:38 AM
Hi,
Not in all cases it would seem ...some users have had issues since a security update and the smartphone was working fine before the update ...
18-11-2022 10:06 AM
maybe the new update broke somthing in the phone? Not sure. My case was, I had it all good since I got it last August. After A13 update around end of October, I got this issue. It was only a HW (board) change that solved the issue. You are right, it might be a different case for others.
18-11-2022 10:11 AM
Hi Xter94
last update available for Orange, from October 25
29-11-2022 11:54 AM
The german android forum: https://www.android-hilfe.de has blocked my account, after I have been critical to the Samsung S22. Maybe they are sponsered by samsung.
Or its the typical way to solve problems in germoney.
29-11-2022 02:15 PM - last edited 29-11-2022 02:18 PM
You were banned because you also insulted users like here. You also constantly provoked and laughed at S22 users and portrayed them as stupid. In addition you constantly claimed that the telephony problem is a hardware problem, so everbody should sell its phone. Since A13 and the November patch, only very few people have the problem, so it's not a hardware problem. And now you're crying in this forum because you've been banned from another. What a pity.
29-11-2022 02:21 PM
Please play at your german sandkasten and let us experts here alone and dont lying about me. Its still a hardware issue. You make a fool of yourself.