Bugless Beast: first impressions and lessons learned (part 1)

A couple of weeks ago I bought an original Motorola Droid from eBay. The seller mentioned that it was running a hacked ROM called ‘Bugless Beast,’ and wondered if I wanted him to flash it back to stock before shipping. I did a little research, saw how easy it was to re-flash the device back to stock, and decided to try Bugless Beast out for myself.

[simage=152,200,n,right,]A new version of the ROM was released while the phone was in transit to me, and when I first tried to use the phone the Android Market app had a tendency to crash after installing a program or two, necessitating a reboot, so my first task was to perform an update. After a little while hunting around on the Web for a how-to on upgrading my ROM, I discovered an app called ROM Manager, which makes the whole process really simple. Basically, you drop the zip file containing the new ROM onto the SD card in the phone, and tell ROM Manager to use that ROM for the upgrade. The app will prompt you as to whether to perform a backup, and then whether to wipe the ‘data and cache’ on the phone. I chose not to wipe the data, but to perform a backup, and went ahead with the upgrade.

The whole process took about 15 minutes, after which the phone automatically rebooted itself and I was able to see all the cool Gingerbread features that have been embedded into v0.6 of Bugless Beast. Unfortunately, the issue with the Market app persisted. All in all, it definitely wasn’t a show-stopper, as the increased performance that you gain from Bugless Beast was well worth the annoyance (BB overclocks the 550MHz CPU on the Droid up to 800MHz, the difference in how the phone performs is quite noticeable). I decided to stick with Bugless Beast and wait for an update to see if it fixed the Market issue.

Jan 23, 2011

• Posted by Vasken
• 2 comments
• Technology
• android, bugless beast, overclock

StackOverflow

Comments