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

The application is really slow and crashes more often compared to the previous version #622

Open
FlawlessCasual17 opened this issue May 27, 2024 · 13 comments

Comments

@FlawlessCasual17
Copy link

FlawlessCasual17 commented May 27, 2024

What the title says.

If you want video proof I'll post it later on.

Edit: it seems to only happen when I enable the option that allows the search bar to appear on the bottom instead of the top

@FlawlessCasual17 FlawlessCasual17 changed the title The application is really slow and crashes more often compared in the previous version The application is really slow and crashes more often compared to the previous version May 27, 2024
@Cohenl19
Copy link

I am experiencing similar issues but regardless of the layout. I have 40 Repositories enabled but I don't suspect this to be the reason for the crashing. However it might.

Regardless of that, when I search and click on an app. It takes a painful amount of time to load. Then once it's opened & let me review the details, the moment I exit out, OR exit out and press another app. It crashes IMMEDIATELY. Extremely frustrating!

@machiav3lli
Copy link
Member

I have 40 Repositories enabled but I don't suspect this to be the reason for the crashing.

@Cohenl19 it's exactly this the reason for most crashes e.g. enabling F-Droid archive is a 100% ensurance to get regular crashes for now. Yours seem to be #556 (it doesn't only apply to archive as community discussions made clear)

@machiav3lli
Copy link
Member

Now into the issue. Here's some helpful infos:

  • What device/SoC?
  • What Android version?
  • How many and what repos are active?
  • Define "slow" better? e.g. What is slow, is opening the search page or scrolling or…

@Cohenl19
Copy link

Then it might be what you said. As you can see when I need to tap something, I have the ability to tap it multiple times before it FINALLY opens. And it does it with every app I attempt to press on, until near the end where it eventually completely crashes

Screen_Recording_20240529_070337_Neo.Store.mp4

@Cohenl19
Copy link

Note 20 Ultra 5G
Android 13
SD865+
40+ repos (I have been removing & readding some to see if it's one of the repos)
Slow as in it takes MULTIPLE seconds just to open app information, where if I compare this to Droid-ify, it opens instantly, and I have FDroid archive enabled on Droid-ify.

If I may ask. What causes NeoStore to feel so behind in comparison to Droid-ify? I actually prefer the way NeoStore lays out information in comp to Droid-ify

@FlawlessCasual17
Copy link
Author

FlawlessCasual17 commented May 30, 2024

Now into the issue. Here's some helpful infos:

  • What device/SoC?

  • What Android version?

  • How many and what repos are active?

  • Define "slow" better? e.g. What is slow, is opening the search page or scrolling or…

Samsung s20 FE 5G
Android version 13

These are all repositories I have enabled:

Screenshot_20240529_190951_Neo Store
Screenshot_20240529_191013_Neo Store
Screenshot_20240529_191027_Neo Store
Screenshot_20240529_190928_Neo Store

Here is a demo of the "slowness" I experience while using the app:

Screen_Recording_20240529_191437_Neo.Store_1.mp4

@machiav3lli
Copy link
Member

@FlawlessCasual17 @Cohenl19 as mentioned above, disable F-Droid archive and report back again. Enabling all repos could add alot of extra fail points… I would suggest to be more reasonable about what repos are required and what not…

If I may ask. What causes NeoStore to feel so behind in comparison to Droid-ify?

NS changed the old database structure inherited from Foxy Droid, while Droidify kept this. The old one is effective but far less flexible, making changes bothersome, while NS's scheme allows for moving faster, adding features etc… I've already tested many alternatives and convinced that couple of smaller fixes (specially to memory management and composition sides) and time (for improvements on Jetpack Room) should be enough…

@FlawlessCasual17
Copy link
Author

I disabled both the f droid archive, and The Guardian Project archive. That fixed my issue it seems to be a lot faster now.

Thanks

@Cohenl19
Copy link

Cohenl19 commented Jun 1, 2024

@FlawlessCasual17 @Cohenl19 as mentioned above, disable F-Droid archive and report back again. Enabling all repos could add alot of extra fail points… I would suggest to be more reasonable about what repos are required and what not…

The thing is, Droid-ify allows me to keep the archive, and having it & The Guardian Project enabled is valuable to me because I take advantage of both repos. Also it's important to note that I don't actually have every repo enabled, as can be seen in my recording.

I guess I will have no choice but to disable these repositories, but in the future if this issue could be solved without needing to do this, I'd be very grateful. Anyhow, regardless of this, I'm happy for the work done on this app! I like seeing alternatives to the original F-Droid app, as I use that app as a reminder to how things could be much worse lol.

@machiav3lli
Copy link
Member

The Guardian Project enabled is valuable to me

@Cohenl19 Be aware that @FlawlessCasual17 didn't deactivate The Guardian Project main repo, but the archive. That said, I'm not sure how problematic is Guardian Project archive, cause it's relative small compared to the F-Droid's archive. And surely the goal is to have all things function with no corner-cuts, this will take some time…

@Cohenl19
Copy link

Cohenl19 commented Jun 1, 2024

Okay understood! Again, thank you for the work you do regardless, even if there are issues here and there, I really do like what Neo Store could become!

@FlawlessCasual17
Copy link
Author

I do love the Neo Store, I just wish led it remembered search queries, and didn't crash when you searched up something that you previously didn't

@RoestVrijStaal
Copy link

I feel the same for the long time.

I prefer the version of 2022 which is much simpler. It does not have those "overlays" when you tap on an entry in the search results or (installed) app list.

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

4 participants