I might even go so far as to suggest to change the *TITLE* to.........."FIXES POST-JB LOCKUPS"!!! I just repeatedly try to do a brand new 32gb for a buddy & could not stop the locking up to save my life. Re did the JB (yes, z 3.0) and did the text-stuff and all's perfect!!!
Hooray! a detailed explanation other than "type in a bunch of text = fix".. it all makes sense now. Are there (m)any other issues related to this one?
FINALLY! Someone who know's what he's talking about! I just wasted hours trying to figure out what the problem was!
The only other situation I've run into is when the music wouldn't play on my iPhone as well. Here's a detailed technical assessment, just for the record: I spent a little time diagnosing this problem because I wanted to see if there was a fix I can suggest to current jailbreak authors that will get around the problem without people having to worry about it at all. It was something to do with the mediaserverd daemon not being able acquire the audio hardware. I don't really know how a program without superuser privileges manages to get a lock on hardware, but apparently mediaserverd can do it ordinarily. However, in that particular testcase, it could not. If I manually ran mediaserverd as root, then everything worked. So it must be a permissions problem. However, I couldn't find the file that had incorrect permissions. The fact that things as disparate as music and keyboard entry can be affected by the same thing also scared me. We can fix keyboard freezing in jailbreaks (by pre-creating the right folders with the right permissions). With a little more research, we can fix the music problem too. But what other weird issues might people run into? Claiming to have fixed the problem might lead people into a false sense of security. That's why I think the best thing to do right now is to tell people to just play with their device a little before going into Installer. There's no guarantee that anything else could completely eliminate the problem.