• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM BETA] Bugless Beast V0.4 Android 2.2 FRF84B (Fully Deodexed)

Poll closed due to new release for this ROM

  • 5 Star ROM Rating: Elite

    Votes: 80 55.9%
  • 4 Star ROM Rating: Outstanding

    Votes: 60 42.0%
  • 3 Star ROM Rating: Average

    Votes: 3 2.1%
  • 2 Star ROM Rating: Not Ready for Primetime

    Votes: 0 0.0%
  • 1 Star ROM Rating: Not Usable

    Votes: 0 0.0%

  • Total voters
    143
Hey guys,

I just bought a used Droid with Bugless Beast already installed.
When I go to BB Toolkit it says I have Rom version V0.4(FROYO)
Is this the latest?

Also, i am having issues sending MMS messages. I used to have a rooted Eris, and i know this was a problem on several roms.
Does anyone know a fix for this?

Yes, you have the latest version. Do you have Root Explorer (if not, I highly recommend it)? Take a look in /system/app and see if Mms.apk is in there. If not, that's probably the issue and it needs to be put back. If your predecessor removed it using a BB script, then you can go into Bugless Beast Toolkit>Script Helper>mms and touch the button that has mms -cp. If that doesn't work, please report back and we can help you get it done.
 
Yes, you have the latest version. Do you have Root Explorer (if not, I highly recommend it)? Take a look in /system/app and see if Mms.apk is in there. If not, that's probably the issue and it needs to be put back. If your predecessor removed it using a BB script, then you can go into Bugless Beast Toolkit>Script Helper>mms and touch the button that has mms -cp. If that doesn't work, please report back and we can help you get it done.

Ok, tried both things and neither worked. Purchased Root explorer and MMS.apk was there.
Also, i ran the mms-cp script. Still can't send MMS messages.
:(
Any other suggestions I can try?
 
Download BB 0.4 from the first post in this thread, download ROM Manager from the Market, and then install BB using ROM Manager, making sure to backup current ROM and wipe data/cache when those options pop up in ROM Manager.
 
Just rooted for the very first time w/bb 0.4. The only bug that I haev encountered thus far is the sync icon appearing on the right without relegating itself to the background. Anyone knows what causes this? Thanks.

Btw, freakin' loving froyo and rooting. I can't believe I waited so long to take the plunge. Thanks to bb and Doid Life for making it so easy to dive into the rooting world.

EDIT: Noticed it is having problems syncing my my contacts. Anyone know how to fix this?
 
Regardless of a one-sentence post by Pete on another forum, BB for the Droid 1 is dead. If Pete wants to keep the illusion alive, he shouldn't be telling people to follow his Twitter, because they, like me, will see that his only concern is the DX and getting it rooted.

WTF?

Maybe Pete is excited about a new handset? I would be. He has released droid roms since he has been working on the EVO and Incredible. I hope he can get the X rooted, because then it may be worth buying.
 
Just loaded v.4 and am loving it with one problem...streaming music sound quality. I've found that both Rhapsody and Pandora sound noticeably worse after rooting my phone with this ROM.

Has anyone else noticed this? If not, how are you listening to your music and what's your basis for comparison?

I'm hoping there's a fix for this...
 
Alright guys, I bought an iPad (please don't flame too much, there was no good android tablet out) and I finally have a reason to use tethering. Went into my apps and didn't see a tethering application? I'm running bb 0.4 and I thought it supported tethering? Any help would be greatly appreciated.
 
Thanks guys. Much appreciated. Now, if I could only get the iPad hardware (which is crazy good) to run the Android OS I'd have the perfect tablet. :)
 
Thanks to GirLuvsDroid for that update! And Cheers to Pete for all the hard work!! I'm using BB 0.4 now and have no complaints, it works great. Can't wait for the new release! :)
 
Quick question about this rom guys...

If I'm running, say, ChevyNo1's ULV 1GHZ Kernel instead of the one that ships with BB 0.4, do I need to use SetCPU to monitor temperatures and speeds, or will the BB script that supposedly runs at boot manage this for me even if it's not with the packaged kernel?

Thanks! :)
 
Quick question about this rom guys...

If I'm running, say, ChevyNo1's ULV 1GHZ Kernel instead of the one that ships with BB 0.4, do I need to use SetCPU to monitor temperatures and speeds, or will the BB script that supposedly runs at boot manage this for me even if it's not with the packaged kernel?

Thanks! :)


I haven't really used SetCPU to monitor my temps but rather I use it to set profiles such as throttling down my CPU when I'm charging my phone or when I'm low in battery. I think it's highly recommended to use SetCPU even though BB 0.4 is capable of managing kernels.
 
I haven't really used SetCPU to monitor my temps but rather I use it to set profiles such as throttling down my CPU when I'm charging my phone or when I'm low in battery. I think it's highly recommended to use SetCPU even though BB 0.4 is capable of managing kernels.

Personally I use setcpu to throttle up my cpu when its charging.
 
Just loaded v.4 and am loving it with one problem...streaming music sound quality. I've found that both Rhapsody and Pandora sound noticeably worse after rooting my phone with this ROM.

Has anyone else noticed this? If not, how are you listening to your music and what's your basis for comparison?

I'm hoping there's a fix for this...

Apparently, this is a problem with Froyo in general and not specific to BB. Check out this thread: http://androidforums.com/all-things-root-droid/119289-any-rom-compatible-pandora.html

and this Android bug report: Issue 9308 - android - eaac+ and aac+ decoding sound quality problems (Android 2.2) - Project Hosting on Google Code

I'm suffering through this too :( but I am confident they'll fix it sooner or later seeing as quite a few Froyo users are complaining about it.
 
I think it's highly recommended to use SetCPU even though BB 0.4 is capable of managing kernels.

I have a contrary view. I purchased and used SetCPU from the very beginning when O/C kernels were first available, and considered it an absolute must-have app for overclocking. However, I've let Pete's automatic CPU ondemand frequency scaling manage my kernels for the last few versions of BB, and I'm seeing better battery life, cooler temps (measured by battery temp and "feel" of the phone), less lagginess (better performance) and more stability without SetCPU than I've had on BB with it. I've seen others reporting similar results.

That said, every Droid is different and everyone has his/her own preferences. You need to try it with and without for yourself to see what works for you and your setup.
 
I have a contrary view. I purchased and used SetCPU from the very beginning when O/C kernels were first available, and considered it an absolute must-have app for overclocking. However, I've let Pete's automatic CPU ondemand frequency scaling manage my kernels for the last few versions of BB, and I'm seeing better battery life, cooler temps (measured by battery temp and "feel" of the phone), less lagginess (better performance) and more stability without SetCPU than I've had on BB with it. I've seen others reporting similar results.

That said, every Droid is different and everyone has his/her own preferences. You need to try it with and without for yourself to see what works for you and your setup.

I agree here - I've had a better, smoother experience with BB 0.4 without running SetCPU, but, as GLD said, your personal mileage may very.
 
I have a contrary view. I purchased and used SetCPU from the very beginning when O/C kernels were first available, and considered it an absolute must-have app for overclocking. However, I've let Pete's automatic CPU ondemand frequency scaling manage my kernels for the last few versions of BB, and I'm seeing better battery life, cooler temps (measured by battery temp and "feel" of the phone), less lagginess (better performance) and more stability without SetCPU than I've had on BB with it. I've seen others reporting similar results.

That said, every Droid is different and everyone has his/her own preferences. You need to try it with and without for yourself to see what works for you and your setup.

I agree here - I've had a better, smoother experience with BB 0.4 without running SetCPU, but, as GLD said, your personal mileage may very.

Liars! :p Just kidding. Maybe I'll test your suggestion with my Droid. I've had most of Pete's roms on my Droid but I believe the first time he implemented his Auto CPU, I had issues with heat and battery life. I never thought to try it again after that.

We'll see. It doesn't hurt to try.
 
Okay never knew BB had Auto CPU. Is it as the name implies "automatic" or is there a script to be run or box to be checked.

It's set automatically to OnDemand (basically it'll throttle your CPU up or down based on usage from the lowest slot in your kernel to the highest). My quadrant scores with SetCPU set to Performance were about 200 points higher; however, I have a far smoother experience overall without using SetCPU, as I mentioned above. If you just want gaudy numbers to post (1740 or so was my average with it set to performance, as opposed to 1530 or so with Pete's built-in), then you'll probably want SetCPU. If you just want a fast, smooth phone that runs cool and has tremendous battery life, I'd recommend just trusting in Pete (well, Pete and Chevy - Chevy's ULV 1.2 gHz kernel is a monster that still gives me excellent battery life).
 
Regardless of a one-sentence post by Pete on another forum, BB for the Droid 1 is dead. If Pete wants to keep the illusion alive, he shouldn't be telling people to follow his Twitter, because they, like me, will see that his only concern is the DX and getting it rooted.

I just felt I should point out that in the last week or so he has discussed working on BB for Droid (1)...Do you even read his twitter?

Peter Alfonso (PeterAlfonso) on Twitter

Just reactivated my #Droid 1...time to work on #BuglessBeast
Sun Jul 18 2010 17:19:42 (Pacific Daylight Time) via web
 
Back
Top Bottom