-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange behaviour since v2.0.0 #207
Comments
This is super strange! As far as I can tell, at the app code level there should be no way to lose the minutes from the time value: Perhaps the rendering thread is crashing half-way through drawing the screen... (That also might explain (kind of) the home apps not being shown.) Issues like this that we cannot recreate are pretty much impossible to debug, but I can say that we reworked some of the logic for keeping the home screen refreshed and up-to-date in the upcoming release (particularly thinking of #194, but other adjacent things changed as well). The beta should be available on F-Droid soon and it would be very interesting to see if the issue still occurs on the new release. Also, I have a few more questions that might help clarify some things here:
|
Hi again, and sorry for the late reply. Here are the answers to your extra questions :
|
Thoght about it and the issue might be that the clock (and therefore it's width) gets initialized with a short time (like 11:11) and so longer times do not fit in? |
Just merged #227 which might help address the clock display issues. I am going to leave this issue open for now, though to see if folks are still experiencing the issue on the next release... |
Since the last update, I get arbitrarily strange behaviour with Unllauncher :
To correct this problem, I have to edit the customize drawer/visible apps settings to uncheck / recheck an app. This makes the custom apps on screen app reappear, but the app of the drawer I unchecked/rechecked is now invisible -> I have to set it to visible one more time.
The text was updated successfully, but these errors were encountered: