Screen buttons not working after latest upgrade

[Robert Spinden]

Upgraded to 12.0 now my on screen phone buttons will not answer or end phone calls and my alarm button will not end the alarm. Is there a setting I can check or change?Does anyone else have this problem? It's irritating to not be able to answer calls for my business.

 

[Robert Spinden]

You will probably have to reflash your phone

What is "reflash"? And what does it do? Will I lose any content, files, photos, data etc.?

 

[Unforgiven]

Reflash normally mean reinstalling the firmware. I don't think that is the solution for you. Are you running stock Samsung firmware? For clarity, that means you didn't root your phone, install a custom recovery, and flash a custom firmware. You simply used the firmware that came with the phone from Samsung.

 

[Robert Spinden]

Reflash normally mean reinstalling the firmware. I don't think that is the solution for you. Are you running stock Samsung firmware? For clarity, that means you didn't root your phone, install a custom recovery, and flash a custom firmware. You simply used the firmware that came with the phone from Samsung.

Yes, all stock. Everything was working fine and changed after the upgrade.

 

[Unforgiven]

Hmmm.... ....I haven't got the update on my S20 yet, so cool for you to have it already.

My understanding is that there is some UI changes where some things need to be swiped instead of tapped. I'm not sure if this is what you are experiencing as I haven't had a chance to play with 12 yet.

 

[Hadron]

I never had Samsung's version of 11, so don't know what it was previously, but with 12 I've generally found it pretty obvious what needs to be swiped or tapped.

From memory I think (because I do this stuff without thinking, so don't trust memory) I generally swipe up to answer calls with the full-screen call screen, tap the button if it's a little pop-up at the top. Alarms (as in alarm clock) are swipe to cancel, but you don't need to swipe very far (just tapping the button doesn't cancel it). Don't know about calendar notifications because I don't use Samsung's calendar app.

But I tend to suspect it is something like that, as it would be very strange for there to be bugs like this in a couple of specific Samsung apps (and it would imply no testing at all for them not to spot it!). I assume that the touchscreen works normally for other things at the same points on the screen?

 

[Robert Spinden]

I never had Samsung's version of 11, so don't know what it was previously, but with 12 I've generally found it pretty obvious what needs to be swiped or tapped.

From memory I think (because I do this stuff without thinking, so don't trust memory) I generally swipe up to answer calls with the full-screen call screen, tap the button if it's a little pop-up at the top. Alarms (as in alarm clock) are swipe to cancel, but you don't need to swipe very far (just tapping the button doesn't cancel it). Don't know about calendar notifications because I don't use Samsung's calendar app.

But I tend to suspect it is something like that, as it would be very strange for there to be bugs like this in a couple of specific Samsung apps (and it would imply no testing at all for them not to spot it!). I assume that the touchscreen works normally for other things at the same points on the screen?

Thanks for replying:
Everything seems to work except my Alarm Clock Cancel button which doesn't work now either. I'll try "swiping which is not a motion that I usually use. I prefer just tapping the button. Why would they change this feature? I hate when my phone changes. I've missed several calls and had to call back.

 

[Hadron]

I spent the last 4 years using Google's Clock app, where you would cancel the alarm by swiping to one side or snooze it by swiping to the other. So when presented with a button that doesn't respond to a tap the next thing I tried was a swipe (to be honest that's what I do with Android generally: if it's not clear try tap, harder press, swipe until one of them works ).

If Samsung did change the interaction without changing the appearance that would be dumb, but it wouldn't be the first time that a big corporation made a dumb change (Google are certainly guilty of a few).

 

[Robert Spinden]

I spent the last 4 years using Google's Clock app, where you would cancel the alarm by swiping to one side or snooze it by swiping to the other. So when presented with a button that doesn't respond to a tap the next thing I tried was a swipe (to be honest that's what I do with Android generally: if it's not clear try tap, harder press, swipe until one of them works ).

If Samsung did change the interaction without changing the appearance that would be dumb, but it wouldn't be the first time that a big corporation made a dumb change (Google are certainly guilty of a few).

I just went through a session with Samsung "tech support" with no answers and have now reset just about everything and am now re configuring my phone. All WiFi passwords, gone etc, What a pain. Why are they requiring "swipe" when I don't use that feature, never have. OMG, have the programmers or developers never heard the phrase, "if it's not broken don't fix it"?

 

[Hadron]

Someone might have decided that it's a clearer gesture, less likely to be triggered accidentally? Or just seen that that was what another manufacturer did and copied it? No way of knowing.