[P2JB Testing] v0.8-dev-a1b152e

P2JB Test Results Needed

Please share your test results for build v0.8-dev-a1b152e. You can test P2JB on firmware above 10.01, up to 12.70.

Important

Do not interact with your PS5 while P2JB is loading. It takes ~50 minutes to complete.

When sharing your feedback, please specify which firmware version you are on.
If you have more success with another P2JB/Y2JB setup, please share details.

[Theone5000]

The Gezine method works (FW 12.70). Wrote a little tut about it: https://gbatemp.net/threads/ps5-exploit-guide.613891/post-10869362
Will do your version next and report back.

[Theone5000]

This is the first attempt: https://gbatemp.net/threads/ps5-exploit-guide.613891/post-10869412

FW: 12.70

Findings:

1. From a UX standpoint it could be improved (a bit). Just writing it down. Don't know what's possible from a development standpoint.

• Optimize loading bars with percentage indicators by ensuring they move at a steady or accelerating pace, never stalling or reversing. So keep it centered. The loading screen is now jumping from one spot to another. Perhaps this is intentional.
• Accelerating fill: A progress bar that starts slowly and speeds up as it nears the end naturally feels more trustworthy and faster than a decelerating.
• Add pulsation: Incorporating animated, backward-moving ribbing or pulsations inside the bar tricks the brain into perceiving the wait time as shorter. The big Sony shows this pulsation animation with the loading bar - as an example.
• Example: Time left : {x minutes/seconds} - Transfer / JB speed: {x value, so 48.43% instead of 48%}

2. Min FW type 12.02 > must be 12.20. Mentioned by Gezine: Gezine@95d4a1a

3. KP-ed on the first attempt. After around 94%. Normally I use the P2JB 2.6 p2jb.js version. This one works better then the 2.3 version for me. I will do a 2nd run to see whats happening.

Screens:

1. ui can always be improved, but I don't want to add any animations etc. It's as lightweight as possible on purpose.
   The progress bar is not "decelerating", it's going up at a steady pace :)
   And there's no point adding decimal points to the percentage or counting seconds, as it's only an estimate set for 50 minutes. Sometimes it will load slightly quicker, sometimes it will take a bit longer. And it's refreshed only once every minute (again, to keep it lightweight).
   In the future we can add real progress instead of estimate, but at current point I don't want to modify anything in p2jb until I know how stable this is.

2. Thanks, will add this (that's just a string though, doesn't affect anything)

3. p2jb v2.3 (with one small fix) is exactly same thing as v2.6 except for added support for older Y2JB versions which we don't need anyway.

[Theone5000]

Alright 2nd attempt: succes.

1. Check > improve what you want and can. It's a nice to have.
2. Check, just a typo.
3. 2.3 works. With Yarpe I always got a 100% succes rate with 2.6, even after 20 reboots with. Changes should not affect it. But then again for 12.70 2.6 is stable. Just FYI;