Weird Bug On the Tiq Mini M5

I have a really weird issue that happens on my tiq running the latest version.

Randomly when I try to pull down the notification screen the screen goes black till I let go of the screen.

I had this on one phone and they sent me a replacement. I set up the second one and it’s happening again.

If you ever had this issue please let me know.

Most people I asked who own a tiq never had this. It’s the second phone it’s happening to so it can’t be a device specific hardware issue.

It probably has to do with an app I have on the phone. But how can I know which one?

I got the logs anyone good at reading them?

It’s sms backup restore app

Uninstall it or prevent background activity

Though I’m not 100 percent sure, the logs didn’t capture the exact moment.

These are the exact logs of when I pulled down the notification screen.

03-18 14:43:54.793 1432 1481 W FrameTracker: Missing SF jank callback for vsyncId: 2378420

03-18 14:43:55.479 1432 1553 D WifiSignalController: isWifi6: false,wifiVisible: true

03-18 14:43:55.480 1432 1553 D WifiSignalController: iconId: 17302899

03-18 14:43:55.485 1432 1432 D CentralSurfaces: Received new disable state: enaihbcrso.qingr (unchanged)

03-18 14:43:55.519 1432 1432 D BufferQueueConsumer: [](id:59800000147,api:0,p:-1,c:1432) connect: controlledByApp=false

03-18 14:43:55.544 1432 1523 D BLASTBufferQueue: [VRI[NotificationShade]#327](f:0,a:1) acquireNextBufferLocked size=480x640 mFrameNumber=1 applyTransaction=true mTimestamp=18320085057475(auto) mPendingTransactions.size=0 graphicBufferId=6150393172642 transform=0

03-18 14:43:55.547 1432 1432 D CarrierTextController: send message to updateCarrierText

03-18 14:43:55.548 1432 1432 D CarrierTextController: send message to updateCarrierText

03-18 14:43:55.548 1432 1432 D CarrierTextController: send message to updateCarrierText

03-18 14:43:55.548 1432 1432 D CarrierTextController: send message to updateCarrierText

03-18 14:43:55.550 1432 1432 D CentralSurfaces: Received new disable state: enaihbcrso.qingr (unchanged)

03-18 14:43:56.418 1432 1432 D CentralSurfaces: Received new disable state: enaihbcrso.qingr (unchanged)

03-18 14:43:56.584 1432 1432 D CentralSurfaces: call showBouncerOrLockScreenIfKeyguard

03-18 14:43:56.584 1432 1432 D CentralSurfaces: Received new disable state: enaihbcrso.qingr (unchanged)

03-18 14:43:56.585 1432 1523 I GED : ged_boost_gpu_freq, level 100, eOrigin 2, final_idx 2, oppidx_max 2, oppidx_min 0

03-18 14:43:56.598 1432 1432 D BLASTBufferQueue: [VRI[NotificationShade]#327](f:0,a:1) destructor()

03-18 14:43:56.598 1432 1432 D BufferQueueConsumer: [VRI[NotificationShade]#327(BLAST Consumer)327](id:59800000147,api:0,p:-1,c:143

Here’s the video of the issue:

So far the thing that triggers the issue to start is when I click on a notification on the lock screen and unlock my phone it opens the notification. Then when I swipe down from the top of the screen I get the issue.

The issue doesn’t always get triggered.

I had this while using pattern unlock method. I changed to number unlock and didn’t have the issue yet. Gonna wait some more to see if the pattern unlock is part of the issue.

It doesn’t seem like the sms back up app is the issue

It seems that the issue stems from the unlock pattern feature to unlock the phone

Would you know what’s causing it or what app to clear cache on that is tied to the pattern unlock feature?

Haven’t looked into it further

It also only gets triggered when you press a notification on the lock screen and then Your prompted to unlock the phone so you unlock it. Then you try, pulling down the notification screen and get that.

I find it weird that I was the only one out there using the swipe pattern on the tiq. Unless there’s another combination such as having notifications be visible on the lock screen. @william what’s that setting set to.

Even when not on pattern unlock mode?

No. Only when you use the pattern. I currently use the numbers to unlock. And I have no issue.