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

Launcher takes several seconds to fully render, about 50% of the time #212

Open
spencerflagg opened this issue Apr 28, 2022 · 4 comments
Open
Assignees
Labels
bug (found in 1.2.4) A bug that was found in 1.2.4. priority: 🌋 high Priority 1. Must be fixed/implemented in the next release

Comments

@spencerflagg
Copy link

When returning to the launcher from another app, almost half the time the phone will hang on either a solid black or solid white screen for several seconds before displaying the launcher. The issue seems happen regardless of how I return to the launcher.

I've stopped using the launcher for now, as it became a significant inconvenience - but let me know if you want me to test it under certain conditions or send logs, etc.

Pixel 3 XL, Android 12
(note: the phone is several years old, with several hundred apps installed, but it is still running about as fast as ever. I almost never see lagging like this)

@github-actions
Copy link

Autogenerated branch name:

launcher-takes-several-seconds-to-fully-render-about-50-of-the-time

@nivisi
Copy link
Owner

nivisi commented Apr 29, 2022

@spencerflagg yep, it happens to me as well. I suppose it is related to our architecture that is going to be rewritten. Thanks for the report!

@nivisi nivisi added the bug (found in 1.2.4) A bug that was found in 1.2.4. label Apr 29, 2022
@nivisi nivisi self-assigned this Apr 29, 2022
@nivisi
Copy link
Owner

nivisi commented Apr 29, 2022

I will actually prioritise this issue, seems like a really not cool thing.

@nivisi nivisi added the priority: 🌋 high Priority 1. Must be fixed/implemented in the next release label Apr 29, 2022
@nivisi
Copy link
Owner

nivisi commented May 12, 2022

@spencerflagg hi! JFYI, this should be fixed when #213 is done. It will be a major release that will heavily clean the codebase and increase the performance (the latter — hopefully 😀). I'm also keeping in mind the things you suggested in #211, so I will probably bring those in the new release/at least will build a basement for it so you could fork and customise it as you wish.

Cheers x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug (found in 1.2.4) A bug that was found in 1.2.4. priority: 🌋 high Priority 1. Must be fixed/implemented in the next release
Projects
None yet
Development

No branches or pull requests

2 participants