[Donglelife872]

Wow, this Note 20 Ultra is just full of surprises. Now, the phone app won't even work on incoming calls. I was calling from my old phone to test some custom ringtones. The phone rings, but nothing pops up - there's no way to accept or decline the call.

I was trying to get my ringtones working, I changed the USB settings in developer mode (and since changed it back), but other than that, nothing.

I don't think I've received any non-spam calls (which are blocked) since installing oneui 3.1 last night. I tested outgoing calls. Those work.

Yay, it's pretty useless as an mp3 player and even the phone doesn't work now.

[Donglelife872]

Experimented more, it seems to be a bug in Do Not Disturb mode. Incoming calls from allowed contacts ONLY show up in notifications, and that's the only way to pickup; swiping up to notifications and finding the phone there.

I received a wanted call yesterday so I know it was working then.

Until this is fixed, how do I block the unwanted calls? The only calls that I want are contacts.

Running 3.1, Android 11. Every single update that's available is installed for the system.

[B. Diddy]

Does it happen in Safe Mode as well?

[Donglelife872]

Yes, same thing. Only difference is that there's not even a ring sound in safe mode. I had to look up how to get in and out of safe mode. I had a brief scare when there was no signal when it booted up out of safe mode. Somehow, it booted up in airplane mode.

I turned off the airplane mode (do not disturb was still on) and retested. Same thing.

Is it just me or is it a universal bug in 3.1 with do not disturb/only contacts allowed?

[Donglelife872]

The phone's screwed up, but I did discover that it's easy to add custom ringtones to alarms with 3.1!

[Donglelife872]

I also experimented with making do not disturb favorite contacts only, making virtually all contacts favorites. No change.

[Donglelife872]

More experimenting: FIXED. Buried in the do not disturb settings were app exceptions. I enabled 'phone', which didn't solve the problem. Enabling 'call' did.

Changes in the 3.1. update must have changed something.

Problem solved.

[mustang7757]

More experimenting: FIXED. Buried in the do not disturb settings were app exceptions. I enabled 'phone', which didn't solve the problem. Enabling 'call' did.

Changes in the 3.1. update must have changed something.

Problem solved.

Marked this thread as solved .

[Donglelife872]

Perhaps someday you'll be able to mark the playlist problem as solved

[mustang7757]

Perhaps someday you'll be able to mark the playlist problem as solved

Between the members here and your pretty good at some troubleshooting yourself I'm sure it will .

[Kizzy Catwoman]

Thank you so much for sharing your experiences as you may help someone else as well.

[Donglelife872]

Excellent, thanks!

Now I stumped the official Samsung forum with my m3u question..d'oh! That forum is really confusingly laid out..it's a wonder that anyone finds anything.

I'm fairly quick to learn something. I had never bothered keeping up with phones before, so I didn't have the knowledge base (other than everyday stuff).

If I put my mind to it, I can get up to speed on the Note 20 Ultra and Android 11 fairly quickly. The ancient S5 has been in service a long time, so I've only been exposed to Android 11 (besides the videos) for a couple of weeks. However, the venerable S5 still kicks butt with playlists. It'll have to be pressed into service for an mp3 player for the near future. I'm not spending 2 hours on a playlist.

I'm wondering if anyone else has this problem after the 3.1 update? That's a fairly major bug.