PL3 Stability Issues
It's come to my attention recently that although PL3 seems to be a good step forward from a jailbreak perspective, it is affected by some rather weird stability issues.
I'm not sure if anyone else has experienced it, but I occasionally get the odd hard lock when exiting from a game to XMB. Worse than this however is compatibility with my Modnation Racers backup. This game freezes constantly and at random spots in the game. I haven't tested this with any other payload (ie hermes), but I have found some posts in another forum suggesting that this crashing doesn't occur using a hermes payload.
I'm curious as to what might be causing both of these crashes (I'm assuming they are for different reasons) and if there is a some sort of debug I can perform to provide some data on the issues at hand?
Has anybody else experienced these XMB locks or random freezing playing backups? If so, what titles seem to be problematic for you?
From the testing I have done so far on my collection Modnation seems to be the only problem title I have where I can re-produce these freezing issues. As for XMB locks, this doesn't happen frequently and I don't think this is title specific.
Any information would be appreciated.
For me, Dante's Inferno kept freezing in the same spot towards the end of the game when using PL3. I switched to Hermes V4B and got past the freezing point with no problem, so I'm sticking with that for now. I also experienced the same XMB lock but it only happened once.
I researched quite a bit about different payloads and managers before finally deciding to jailbreak my PS3. Kakaroto's detailed article about how Hermes' code is dangerous etc,something about allocating a specific memory block and how it could lead to crashes/restarts etc. As any other cautious user would, I chose to go the PL3 way. It works, yeah...the funny thing is, it's actually PL3 that is causing the type of intermittent problems that were supposed to happen with Hermes. Random restarts(esp after game backups finish), freezing/hard lock-up while quitting to XMB etc.
I tried using Hermes 4b for a day or two and it ran everything without any such occurences. I don't know what to think of this. People say PL3 is the future, it's dependable and not dangerous. I want to stick to PL3...but it really gets on my nerves sometimes.
One thing I can confirm and the main reason I am using PL3 is because of it's compatibility with retail discs. For instance I can backup one of my retail games and play it with PL3 NUS and should I decide to use the original disc instead of play it off the HDD then the install data still works correctly.
I believe this is not the case with the hermes payloads because of some permission issues. This is a major sticking point for me, as I want the best of both worlds...
I'm hoping with some debugging we can get the PL3 freezing issues fixed, just looking into some of the debug features at present...
You are correct, that's one of the main reasons for me too. I think the "fix permissions" packages should resolve the issue with game data/updates installed via Hermes though(I'm not too sure).
I was a Hermes V4b user until I tried to play the new Dragon Ball game, after much stuffing around I kept getting a 8001 error (sorry cant remember the rest of the digits) and was frustrated... I was googling and found the latest PL3 has fixed this... I flashed my T++ and the game is working, I have not tested any other games...
My ps3 has frozen twice now, once when i preshed ps (middle button) to come out of f1 2010 and another when i was watching a film off a usb and then went back to main menu.
I'm using a nano 1G, hermes + Wanninkoko + mathieulth on 3.41.
was upgrading from hermes 4 so tried PL3, for the same reasons of the OP. Have to say it was constantly locking up in the same way, so i tried hermes 4b and its as stable as hermes 3 with no lock ups... odd as i thought PL3 was the "cleaner" payuload (yes did the fix perms thing etc). :cry:
Originally Posted by charliebrown
Can you link me to hermes 4b fix perm things or what ever it is, i'm going to try that....
reformat start from scratch and dont use hermes... this will likely fix your crashes ;) hermesv4b just messes up file permissions, which you might not notice till later on.
if it doesnt, it could be your files.