Skip to content
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

Open
basteks opened this issue Jan 4, 2024 · 4 comments
Open

Strange behaviour since v2.0.0 #207

basteks opened this issue Jan 4, 2024 · 4 comments

Comments

@basteks
Copy link

basteks commented Jan 4, 2024

Since the last update, I get arbitrarily strange behaviour with Unllauncher :

  • the current time on the home screen only displays tens of minutes but no longer units (for example 08:5 for 8:55)
  • when this happens, the custom apps on the home screen no longer display

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.

@jkuester
Copy link
Owner

jkuester commented Jan 4, 2024

the current time on the home screen only displays tens of minutes but no longer units (for example 08:5 for 8:55)

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:
https://github.com/jkuester/unlauncher/blob/105c8ce09893b7052a1bdf3c7f25250597eec778/app/src/main/java/com/sduduzog/slimlauncher/ui/main/HomeFragment.kt#L237C26-L237C26

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:

  1. How often does this happen? (Daily, weekly, hourly, etc)
  2. You mention that customizing the visible apps in the drawer can cause the app to snap out of the behavior. What about changing any of the other values (e.g. the theme or the Quick Buttons)? Does that cause the problem to go away?
  3. When this behavior happens next, can you try rebooting the phone? I am curious when the phone starts back up if Unlancher is back to behaving normally or not.
  4. Any details you can provide regarding the environment you are seeing this in would be helpful!
    1. What version of Android are you running?
    2. What is the model of the device?
    3. Approximately how many apps do you have installed?

@basteks
Copy link
Author

basteks commented Jan 13, 2024

Hi again, and sorry for the late reply. Here are the answers to your extra questions :

  1. This happens around two times a week
  2. Last time it happened, I tried to check/uncheck the Set theme background as wallpaper slider, and it effectively makes the problem go away
  3. I also tried rebooting the phone which didn't give me complete satisfaction : the bug on the time display disappeared, but the home apps still weren't shown
  4. My phone is a Redmi 7a, running on MIUI Global 12.5.2 based on Android 10 QKQ1.191014.001, with around 40 apps installed

@khwolf
Copy link

khwolf commented Feb 5, 2024

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?
Currently i do not have time at hand so i can not verify or fix, but should be quite simple to solve (e.g. initialize to 99:99), if someone wants to take on the issue.

@jkuester
Copy link
Owner

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants