Notification Panel Bug after OneUI 6.1 (only expand with 2nd pull down)

[Patrickm98]

I have a huge problem with my notification panel after updating to Oneui 6.1 on my S23U. As shown in the video, notifications won't expand with the first pull, instead I need to pull down a second time - everytime I pull down the notification panel. But that problem only occurs when I use side gestures from the One Hand Operation+ App. When I pull down from the top of the screen, everything works. I have the same problem on my Tab S9 so I guess it's because of Oneui 6.1. I hope they can fix that in the next update. 

[AndrewL]

@Patrickm98: If you swipe from the top of the screen to the bottom to open the Notification panel, then tap the drop down arrow to the right of the notification, then this will expand it without the need to swipe down a second time to expand the panel. 

[Patrickm98]

I just noticed the same problem while tapping on a notification or while trying to swipe one to the side. Any notification (except do not disturb for some reason) doesn't react to the first touch... This bug needs to get fixed. 

[gotwillk]

I have the exact same problem and it also started with 6.1 update to my S23 Ultra.

Pulling down the notification shade the first time makes everything in that shade to be non responsive. The only action I can do is pull it down a 2nd time to get to the full panel. If I do this and then go back to the first shade, I can now start to interact with my notifications. If I exit out of the shade completely, I will have to repeat these steps.

Another way to interact with the notifications is if I do a single tap on anything in the first pull down shade. This seems to "wake up" the GUI and now I can interact with notifications but this essentially means I have to double tap everything.

Another thing I found is if pulled down the notification shade, and I used the Home button or action to get out of the shade, I'm able to interact with the shade the next time I pull it down again. However, if I swiped up to close the shade instead, the shade will be non responsive the next time. So I basically always have to remember to use Home button to close the shade.

I also use One Hand Operation+ to use gestures to pull down shade. However, I've already disabled this and the issue still occurs. In fact, I've disabled all my GoodLock modules and it still occurs.

This is a VERY annoying bug that needs to be resolved ASAP.

[Patrickm98]

Exactly what I mean! It's so annoying! The weird thing is: If you managed to pull down a group of notifications (several WhatsApp messages for example) but don't wipe it away, you'll be able to pull them down with the first touch if you open the notification shade again. Anything else just responses with a second touch. I don't understand how they messed that up... I guess they wanted to release the new update as fast as possible before April. 

[gotwillk]

Hmm, I just tried what you said and it doesn't work for me. The only way that will work is if use Home to get out of the shade, then go back into the shade. This method seems to work every time but its too annoying to keep using Home when I just want to simply swipe the shade back up to close it out. Also, I don't want to go back to homescreen every time just to swipe away my notification shade, its ridiculous.

I'm also surprised we seem to be the only 2 people with this problem?? I've been searching everywhere for a solution the past few days and seems like no one else is reporting this for some strange reason.

[gotwillk]

Also I forgot to ask, are you using Nova Launcher or any other 3rd party launcher?

[Patrickm98]

I was looking for a solution too but couldn't find anything... Can't believe it. I'm using the stock OneUI Launcher but have the same problems with Nova Launcher so it's definitely not the launchers fault. 

[Patrickm98]

Not that important but I found the same topic as here on reddit: https://www.reddit.com/r/GalaxyS23/comments/1bt9xzs/oneui_61_bug_when_expanding_notifications_via/

It's definitely good know that it's a widespread bug. I'm loosing my mind if it doesn't get fixed with the next April update. 

[gotwillk]

Nice, at least its not just us! I was looking on Reddit the other day and there was no one reporting it. In fact, you were the first person that I've found anywhere that reported this same issue.