search

TBog / TBLauncher

based on https://github.com/Neamar/KISS
GNU General Public License v3.0
140 stars 18 forks source link

No screen elements shown other than the dock #484

Open ltguillaume opened 4 months ago

ltguillaume commented 4 months ago

Description

I'm regularly getting a blank screen in TBLauncher, save for the dock. It looks like the screen elements are there, but they're invisible/transparent. So I can click somewhere and it opens an app, or long-click and see the context menu, but in fact no widget, search result (app/shortcut item) and no search bar is visible. Only the dock is visible in the widget screen (but not in the search screen).

I have to restart TBLauncher to get it working again.

Context

I think this behavior started when my GrapheneOS device updated to the Android 14 June 2024 Quarterly Platform Release.

Screenshots and log

Here's a video that shows the empty screen (the partly visible keyboard at the beginning appears to be a bug in the Android screen recorder: the only thing visible for real is the dock). https://upload.disroot.org/r/f4WzS_SE#9jw1YaIOBhi2AZrWO2pX0+Gcn42BliTweXO/imGFCZY= (until August 10) It starts in widget screen, then opens search screen.

Here's the logcat dump: https://upload.disroot.org/r/L03htgUS#wyqNDOtR7HRFTPFPYPUQlJe3COucAOD5WG77rotmCtA= (until August 10)

Device info

ltguillaume commented 4 months ago

@TBog is this really only happening on my phone?

TBog commented 4 months ago

I'll post a new dev release for you to test

ltguillaume commented 3 months ago

Will the changes be in the next release either way? Otherwise I'll reinstall, but I'm not looking forward to that, because I have the F-Droid release installed right now and this isn't a reproducible build (yet?), hence differently signed. I have lots of shortcuts I'll lose, plus widget settings.

corbin-zip commented 2 months ago

I have this exact same issue, also on Graphene. Issue started around the same time as is reported in this GitHub issue.

A workaround I've found is toggling battery saver. If battery saver is on, turn it off, and vice versa.

Thank you!

ltguillaume commented 2 months ago

I never have the battery saver turned on, so I don't really understand why this should be of consequence.

As for the test build mentioned here: I have been running it for about a week now, and the issue still presented itself (twice).

ltguillaume commented 2 months ago

Not sure if there's any related info in the log, but this is a logcat dump right after the first time it happened with the test version: https://notebin.de/?8a3a55e5f2a092eb#CUdFXfHFTpsoK24Cct8VA4kotYnz5keanswujdoxUvns

corbin-zip commented 2 months ago

The next time you experience the issue, toggle battery saver on, and the issue should be resolved; you can toggle it back off if you'd prefer it off and it will still be resolved. The action of toggling it on or off seems to be all it takes. I also do not know why this would be of any consequence, but I have a 100% success rate with it.

It's a workaround and obviously not ideal; I'm just clarifying my previous message.

I can provide similar logs at a later time if those might be helpful, but there isn't anything obvious that stands out to me.

ltguillaume commented 1 month ago

@corbin-zip Has this ever occurred for you while on the dev build?

I haven't seen it since the first day I installed it, so maybe we could close this and reopen if it ever happens to appear again?

@TBog And perhaps it would be time for a new official release to provide the changes to everyone?

TBog commented 1 month ago

I'll release a new version asap

ltguillaume commented 1 month ago

@corbin-zip Doesn't seem to have anything to do with the battery saver: I just had the same issue again, then turned battery saver on, checked if the issue disappeared (it hadn't), then turned it back off again. Still no change.

Edit Ah, when I turn on the battery saver and then turn off the screen, it seems to work. But I'm pretty sure that just means that TBLauncher was closed and reopened.

Edit Yes, logs confirm that with wm_on_stop_called and wm_on_restart_called. Then it's no use, I can just as easily restart TBLauncher myself.

corbin-zip commented 1 month ago

I'll clarify my experience.

Problem: I realize that my icons aren't refreshing properly. I write text in the search box but the words don't appear. I attempt to swipe up and down through my icons, but nothing visually changes.

For example, if Firefox is my most recently used application and is thus on the bottom of the list, and I write "Joe" in the text box, nothing will visually change; it won't even show that I wrote the name "Joe." However, if I tap on Firefox, it will now call Joe. The launcher is functioning but its visuals aren't matching the elements that are "actually" there; the visuals don't seem to be refreshing.

My workaround:

I have a 100% success rate with this.

Alternatively, I can tap the breadcrumbs ("...") to open the TinyBits launcher menu, then select TinyBit settings, then tap Close launcher, then tap OK. For me, this is the same number of "actions" as toggling battery saver (3 swipes + 1 tap versus 4 taps) so, 6 in one, half dozen in the other I suppose.

I will try and remember to check the log the next time I experience this problem.

In response to your previous question about the dev build, I never installed it. I haven't installed any applications independent of either F-Droid or the Play Store on this phone so I didn't bother looking into it.

Looking forward to the next official release, however!

Corbin

ltguillaume commented 1 month ago

Ah, that's a bit different from my experience then: in your case, the screen elements seem "stuck", whereas mine are simply gone, or more specifically, invisible: everything in the results list is invisible, as are the widgets. The dock is still there on the widget screen, though.

I guess it just depends on what - after toggling the battery saver - triggers a TBLauncher restart specifically on your device. On mine, it didn't do so unless I turned off the screen.

corbin-zip commented 1 month ago

It is possible that my description isn't 100% accurate and that it is actually that case that no icons are appearing on the screen but that, out of habit, I swipe up again to force a sort-of single-frame refresh.

The icons may be appearing after I swipe up from the bottom of the screen again. I understand that swiping up should bring me to my launcher, and I am (obviously) already at my launcher, but it seems like swiping up causes a single-frame refresh -- thus, I see a bunch of icons that appear to be stuck.

Do you get anything if you swipe up again while looking at your icon-less launcher? I went to watch the video in your original post to compare with my experience but it seems like it has since been deleted.