Diagnosing your tweak conflicts isn't always easy.

The process of diagnosing tweak conflicts or SpringBoard crashes can be a little tedious. You may get lucky and make a good guess based on what you have installed recently, or what is happening right before the crash.

For the most part, it all boils down to manually disabling tweaks one by one in iCleaner Pro and testing for the crash each time.

The good news is that it gets a little easier the more you do it.

Diagnosing Your Own Tweak Conflicts

Crash Reporter will detect a crash and help you report tweak conflicts to developers.

Submitting A Crash Log With Crash Reporter

Automatically

A lot of the time for SpringBoard crashes, Crash Reporter will detect a crash and find a culprit. This automates a lot of the process down to a few taps:

  1. Crash Reporter will send you a notification, tap on it to open CR right to the report.
  2. Tap on ‘Main Suspect’, this will open up the dialogue shown in the screenshot of CR on the left.
  3. Tap ‘Contact Author’.
  4. This will then generate an email and prompt you to fill in a little user note. Write anything here that may help with the issue: what you installed before is happened, what you were doing when it crashed, things like that.
  5. Tap ‘Submit’.

Manually

You didn’t receive a notification for a crash, but you know something is up because your device just crashed to safe mode:

  1. Open Crash Reporter.
  2. Tap on the latest crash.
  3. If you don’t see a culprit, check the crash log, there should be a line that says: “Triggered by Thread:  X”
  4. Scroll down the log to the specified thread, there should be an asterisk by one of the lines. If there isn’t then Crash Reporter failed to detect the culprit and all you have is a nearly unreadable log of text.
  5. Go ahead and forward the crash report to yourself for your own records.

Disabling Your Tweaks With iCleaner Pro

Disabling Substrate Addons can help you narrow down the cause of tweak conflicts.

When all else fails, it’s time to turn to iCleaner Pro. Head on over to the plus sign tab on the left. Here you will see ‘Cydia Substrate Addons’ under ‘Advanced’ near the top.

This is where you’re able to manually disable each .dylib file on it’s own.

Disabling A Single Tweak

This is useful when you know what is causing the tweak conflicts, you’re able to keep the tweak installed until an update is released.

  1. Find which tweak you’d like to disable.
  2. Tap the toggle in the corresponding cell.
  3. Tap Apply in the top right corner and let iCleaner Pro respring your device.

Bulk Disabling To Diagnose Tweak Conflicts

When you have no idea what is causing your issues, it’s helpful to disable more than one at a time. You can do a handful at a time but I usually disable them by the view, so in the above screenshot I’d start by disabling everything from Activator to AntiSocial. Then scrolling down to AppList and repeating the process.

  1. Tap all of the toggles you can see in the view to ‘off’.
  2. Respring.
  3. Check if your problem persists.
  4. If it does, turn them all back on.
  5. Scroll down to the next full-page view.
  6. Repeat steps 1 through 3 until you you identify the problem.

Summary

Diagnosing your own tweak conflicts is an essential part of every jailbreakers tool belt. When we step out of Apples walled garden, we accept responsibility for our own device and the software running on it; there is no brick-and-mortar Cydia store near you.

If you have gone through troubleshooting a bit on your own and still can’t figure it out, making a well-written post on the jailbreak subreddit is the next step. In the next How-to post, we will go over some of the things that should help get your post seen on reddit.

Is there anything you do differently to figure out whats going wrong when your device starts acting up?

Let us know in the comments and stay tuned for our next how-to post!

LEAVE A REPLY