This is a problem I seem to recall having on really earlier versions of Android on older phones, but now it’s absolutely plaguing me on the Teracube to the point where I just had to post about it.
When dealing with notifications on the lock screen (phone dings, I check phone, I investigate/act on the notifications), I very often find this is the process:
- phone dings
- I click the screen on (wish it’d turn on and highlight why it dinged, but hey)
- I find the notification. Sometimes it’s grouped in with 2 or more in a notification bundle from an app. Trying to expand a group of notifications has the same problem.
- I pull down the notification. As my finger is on the notification, pulling it down, I can read the whole thing, it’s fully expanded.
- I let my finger up, hoping it’ll stay expanded. It does not. It collapses back up.
- Repeat (4) 3-4 times.
- Either it finally sticks, and the notification stays expanded, or I give up and just hold my finger on the “stretched” notification to keep it from collapsing as I read it.
In the above, it seems like notifications near the top of the list on the screen have the most trouble, while ones at the bottom work more reliably.
I mean, I stretch the thing open all the way to the bottom of the screen. There is absolutely zero ambiguity as to my UI intent - I’ve pulled about half the screen width and holding it… and it still snaps back shut.
Similar with dismissing notifications. Swipe to dismiss… it snaps back. SWIPE. Snaps back. Swipe. Swipe. Swipe. Swipe. Like I’m fidgeting with the world’s most frustrating rubber band. These are definitely dismissable ones - the “sticky” ones like YouTube (ugh) don’t slide as far before snapping back, and eventually I can get them all to dismiss, but it takes way more attempts than it should, most of the time.
Are there some tunable parameters in the development world for this (e.g. for the low DPI screen), or some tips and tricks that might make this routine slightly less frustrating? 
