-
Notifications
You must be signed in to change notification settings - Fork 40
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
[3.0][3.68][GCD=ux0 or GCD=uma0][boot time] Boot time takes noticeably longer with v3.0 compared to gamesd by xyz #39
Comments
Please test : |
I would definitely test it out if I could, but I'm the few people that uses my sd2vita mounted as uma0 and not ux0. The plugin you've linked me mounts sd2vita as ux0 by default, so I unfortunately can't use it. If anyone else could test the boot times for the plugin linked above, that would be great! |
@CelesteBlue-dev I haven’t had a chance to try the latest version of either plugin yet, but from what I understand it’s more noticeable now and even longer time is being taken. But my point is, the problem definitely existed before the latest version, even if it was shorter (and therefore less noticeable) Thanks for the plugin by the way. It’s one of my favorites :) |
3.68 h-encore takes longer to load too. It freezes for a while when I press Exit. It doesn't really bother me since I only reboot when I add a new plugin, but it's very noticable. |
So is this abandoned now? |
looks like it gamesd is more updated and faster |
No it is not abandoned. I am back. |
you should partner with YAMT its very fast. |
Yes YAMT is one of the ways to improve speed, but not the only one I'm aware of. Soon. |
With the latest version (v3.0), when restarting or powering on Vita, the boot time is now considerably longer compared to using previous versions of storagemgr or having the plugin disabled. Upon boot, vita hangs on the henkaku/enso logo for about 5-10 seconds longer.
Not a big issue, difference is only a few seconds, just like to point this out in case it could be fixed.
By the way, thank you for your hard work on v3.0 and fixing all the other issues!
The text was updated successfully, but these errors were encountered: