Apps UI lag/loading delay upon launch

[Lord-Of-Mysteries404]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I'm on the latest version.
• I'm not using a test build (alpha/beta/release-candidate).
• This issue contains only one bug.

Describe the bug

Just as the title suggests, when I open the app, the apps takes a bit too much time to load

Expected Behavior

When I open the app, the UI should load normally

Neo Store's Version

1.1.1

Installation Source

Official F-Droid repo

Last Known Working Version

No response

Relevant information

• Device: Galaxy J7 NXT (3/32)
• Android Version: 9
• ROM: One UI 1.1
• Disabled battery optimization for Neo Store? : No
• What is your selected installer? : F-Droid

[machiav3lli]

I'd assume this has to do with your phone's performance. Can you please provide a screen record to understand what is delayed better.

[Lord-Of-Mysteries404]

I'd assume this has to do with your phone's performance. Can you please provide a screen record to understand what is delayed better.

My phone performance? For a 3 GB ram phone it runs quite modestly so far so that couldn't be it. Had no issues with Droid-ify or any other apps.

And I meant the apps list takes a bit much time to appear when I open the app (Droid-ify is butter smooth on that matter)

[SynapseScribe]

it loads slowly the installed apps list on onepus 7t pro too

[gbakeman]

This sounds related to #820, but I can confirm that I'm experiencing this problem since 1.1.2 (installed apps list remains blank, Neo Store consuming 15-20% CPU constantly) and remains now in 1.1.5.

[machiav3lli]

Should be fixed on 1.2.0, can you please test and report back

[gbakeman]

Not OP, but Neo Store appears to be much more responsive. Excellent work!

[Neoneczeq]

This issue still exists on 1.2.0.

[machiav3lli]

@Neoneczeq @Lord-Of-Mysteries404 can you then please provide an example/explanation (e.g. screen record) of what you understand as the issue here?

[opk12]

Could it be due to excessive heap fragmentation (related #661)?