MultiIconMover is still undergoing beta testing. You're fully responsible for what you put on your device, so make sure you clearly understand the potential and risks and consequences of testing beta software. You may experience Safe Mode crashes and various other things.
As you may have noted from the IconSupport for iOS 5 article, the developer ashikase (@ashikase) has been extremely busy with getting all his work updated for iOS 5. Just a few moments ago, he tweeted out that he has added iOS 5 support for MultiIconMover in a .deb file he provided in the tweet. He mentioned in that message the he's looking for people to test on both iOS 4 and iOS 5.
Those of you that may not know what MultiIconMover is, it is a tweak that allows you to move more than one icon at a time on your SpringBoard. Simply go into wiggle mode, tap the icons you want, go to the page you wish to drop them on, and press the Home button again. MultiIconMover has been around for quite sometime and is an extremely popular tweak for jailbroken iOS devices.
If you wish to test the new MultiIconMover beta, the link is below:
Here are a few things to remember:
- MultiIconMover is in beta. That means it may not be entirely stable or work well with other packages. Treat testing this .deb file as such
- You're fully responsbile for what you install on your device. If you're not proficient in problem solving with your device on your own, it is not recommended that you test
- Because this is a .deb package, this will require you to SSH into your device and install the .deb package manually
If you don't know how to install a .deb package via SSH, either wait until MultiIconMover is available on a repository or search the forums on how to SSH and install a .deb package. There are numerous ways of SSHing into your device with various programs and applications, so choose a method that works best for you.
The developer is always looking for support feedback, so make sure if you run into any issues, report it to ashikase. That makes the package better for everyone in the coming future. Here are a few guidelines that I like to follow when beta testing that I would recommend you follow:
- If you run into any issues, make sure to report it right away to make sure you don't forget
- When reporting the issue, make sure you're stating the issue concisely and constructive. Check your grammar, spelling, and other things. Those are all important characteristics of a good report
- Be willing to coordinate with the developer to find out your issue
- Don't automatically assume that it is the package's fault. It may be a conflict with another application or tweak that you have installed (or the OS itself). Be respectful and humble in the regard that it may be a fault on your end as well
- Don't complain, whine, or get upset. It is a beta software and should be treated as such