[DaveiPhone]

Originally Posted by x999x

So, you've got a decision to make at this point, do you wait it out and avoid a restore? Or, do you take measures into your own hands and get immediate peace of mind at the cost of starting out fresh again?

Those really aren't the only choices.

The mobilewatchdog method works quite reliably, is much faster, and leaves your phone exactly as it was. I'm not saying your method doesn't also work, but for those who are comfortable with SSH and terminal, killing mobilewatchdog is a fine alternative.

For those who haven't seen this method, here's a link:

http://www.hackint0sh.org/forum/showthread.php?t=49782


To be clear, this type of crash has nothing to do with Cydia. Manually installing an app can trigger the exact same problem. It's simply poor design on Apple's part.

[DTRocker]

I know ive had my fair share of freezing when using cydia, but nothing major only have had to force restart 2 or 3 times since jailbreak for iPhone 3G came out, um I know that after installing an app you have to make sure to go back instead of just exiting the app with the home button, otherwise it may freeze or just wont do anything at all, and if you hold the home button to close it out after a freeze hold it for a good 20-30 sec its not as fast as it used to be pre2.0 FW, my 2 cents

[x999x]

Originally Posted by DaveiPhone

Those really aren't the only choices.

The mobilewatchdog method works quite reliably, is much faster, and leaves your phone exactly as it was. I'm not saying your method doesn't also work, but for those who are comfortable with SSH and terminal, killing mobilewatchdog is a fine alternative.

For those who haven't seen this method, here's a link:

Workaround for 2.0.x stuck at apple logo after installing apps - Hackint0sh


To be clear, this type of crash has nothing to do with Cydia. Manually installing an app can trigger the exact same problem. It's simply poor design on Apple's part.

At the rate the 3G battery dies, who leaves SSH on anymore mate?

[DaveiPhone]

Lots of folks, (including myself, having TESTED it extensively) don't believe leaving SSH on has any significant impact on battery life. And it's a great safeguard when things go bad.

Even if you don't leave it running, it's simple enough to set it up to automatically turn on when the phone reboots.

[Atreides]

<-- SSH always on, no noticeable battery impact, considering I have to charge intraday anyways (i.e. with or without SSH running)...

On another note, I read another thread that Saurik was looking into a "something" to at least temporarily address the mobilewatchdog bug. I've not confirmed this first hand, so if he's out there maybe he can weigh in (or some other devs out there with a better understanding of internals - i'm poking in dark still...)

I am experimenting with a script that on condition (not sure what yet - perhaps double home tap) it will kill mobilewatchdog and reboot. On successful reboot it would restore mobilewatchdog. Unfortunately, I am far behind the curve compared to many of the other devs out there, so maybe someone else will get something sooner...

[x999x]

Originally Posted by DaveiPhone

Lots of folks, (including myself, having TESTED it extensively) don't believe leaving SSH on has any significant impact on battery life. And it's a great safeguard when things go bad.

Even if you don't leave it running, it's simple enough to set it up to automatically turn on when the phone reboots.

I don't recharge at the office, and therefore I see a considerable loss of power when SSH is on :T

[joshWUa]

You are the ****.... This worked very good for me. Now answer me this, should i now go and kill mobilewatchdog now that i can SSH? Will deleting this file harm the phone? What solution would you recommend for this problem not to happen again?

[dkallan]

Originally Posted by joshWUa

should i now go and kill mobilewatchdog now that i can SSH? Will deleting this file harm the phone?

No, do not delete it! Without mobilewatchdog running, the built-in hardware watchdog will hard-restart your iPhone every ten minutes. Temporarily disabling mobilewatchdog is just a workaround to allow extra time for the full code signing and application map rebuilding processes to complete.

Hopefully, Apple will loosen this up in 2.1 so that it becomes a non-issue.

[Atreides]

By kill, you are temporarily moving the mobilewatchdog out of startup folder. Letting Springboard start up properly. Then moving mobilewatchdog back to the startup folder, else your phone will reboot every 10 minutes... Not a nice thing...

as originally posted here :

mv /System/Library/SystemConfiguration/mobilewatchdog.bundle/ /
reboot

After a few seconds the device will start to reboot, and after approximately 3-6 minutes (depending on how many apps you have installed) you will reach the lock screen as normal, when that happens we now have to re-enable the watchdog timer, and reboot again, so again log in with ssh, and type:

mv /mobilewatchdog.bundle /System/Library/SystemConfiguration/
reboot

[philhu]

Originally Posted by Atreides

<-- SSH always on, no noticeable battery impact, considering I have to charge intraday anyways (i.e. with or without SSH running)...

On another note, I read another thread that Saurik was looking into a "something" to at least temporarily address the mobilewatchdog bug. I've not confirmed this first hand, so if he's out there maybe he can weigh in (or some other devs out there with a better understanding of internals - i'm poking in dark still...)

I am experimenting with a script that on condition (not sure what yet - perhaps double home tap) it will kill mobilewatchdog and reboot. On successful reboot it would restore mobilewatchdog. Unfortunately, I am far behind the curve compared to many of the other devs out there, so maybe someone else will get something sooner...

I wrote that script. You don't need SSH, just install MobileTerminal.

I wrote a script called arm. When my phone comes up, I run that automatically. It moves the mobilewatchdog folder to root. Since the program is running, it can be moved, thanks to Unix using files by file handle, not location after openning them.

So, if I install and get the ALoD, I restart my phone, when it comes up, I get on, go to MobileTerminal, and run the 'disarm' script. It move Mobilewatchdog back where it belongs and reboots.

Then after that reboot, I run 'arm', and wait until my phone gets stuck again, i am ready

oh, and BTW, Apple did NOT fix this in 2.1

They added a cache file to make the springboard thing run faster, so the watchdog should not trigger. Fine except Cydia kills the cache file, forcing Springboard to recreate it sometimes causing the same problem.

They need to change the timeout to 5 minutes and the hw one to 20
or better, yet, FIX IT! Make sprinboard call the watchdog during enumeration of the desktop

[Atreides]

Philhu - slick! Sweet and simple! So far so good with 2.1, i've not crashed it yet. I think throwing many of my apps into Categories also helps, since I would think it greatly reduces the # of apps Springboard has to enumerate. I am guessing at this, perhaps I am wrong. Considering I have around 80 apps on my phone, with 2.1 I am stable...

[whynotubabe]

Cydia has been GREAT to me...everything works fine.... it sounds like a PERSONAL ERROR on your side!!!!

[stlcaddie]

I've had this issue in the past only maybe twice. All I did was when it was froze was connect to iTunes and forced reboot on the iPhone it self. And it fixed it self.

[RonnyT24]

Ummmmm i duno if this could be it but intelliscreen was doing this to my phone after installs of programs would force my phone back to the lock screen. Which then intelliscreen would crash my phone. I would have to do a restore every time. I finally landed on it being intelliscreen and didnt reinstall it and boom, been crash free for months. Intelliscreen was my prob... mabe its some of you alls?

[TehNait]

My iPhone has also had these problems. Just once though. And I think i've figured out one of the main reasons why.
You can't overwrite files with cydia.
When downloading certain apps from cydia they have requirements as you know.


Say you need Hackx in order to make some other app work so you get it.
Now say something else requires hackx, but gets it from a different source. Cydia will automatically grab the files needed. (Including hackx)
The install fails because it's already there and can't be overwritten. And then you get bricked

This happened to me with ********** and one of the required files.