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

[vincentp]

Finally found the time to get this bad boy installed and set up. Scored extremely high in all the benchmarks I've done. Ridiculously fast. I can't believe it. Every time I think this phone has peaked in it's performance, it just shows that it still has more potential.

I've had my Droid since November, and compared to the speed back then, it feels like a phone that should be 2-3 years newer. Compared it side by side to my friend's Incredible and it's definitely quicker. Kudos to Pete, Chevy (for his awesome kernels) and everyone involved in making these ROMs.

 

[akakrill]

its workin MINT!!!!!!!! thx

 

[UBRocked]

im using chevy's ulv 1.25 now and im getting great results. my linpack score was over 1700, short bench was 145. but my concern is the battery usage. it seems to drain quickly so i was thinking of scaling it back a bit. question is, if i use set cpu to so this, would this be as beneficial as downloading a lesser kernel?

Lower speeds = better battery life (for the most part)

If you are running at 600MHz, but every task takes twice as long, you could argue that you have to leave you screen on longer to check you facebook, email, news, weather, etc. and could possibly not have a benefit to extending your battery life.

If you are doing something like listening to pandora or music of some kind...go ahead and scale down your SetCPU to 500MHz or 600MHz to save battery. You have to play with some things to maximize you battery life.

Now, is it better to take a 1.25GHz kernel and just clock it down to 1.1 GHz or just load a 1.1GHz kernel? Well, if you are using a 7 slot kernel, then you are giving up a slot in your kernel. What this means is that if you are set to "on-demand" scaling via SetCPU, you now only have 6 possible speeds your phone could run at vs. the 7 you would have if you were running a 7 slot 1.1GHz kernel. Is that going to be noticeable...probably not much if any difference.

I think 1.0GHz is fast enough and anything over that is probably decreasing your battery and increasing heat MORE than it is giving you a return on performance. I run 1.1GHz cause that's what my phone can handle so I don't live by that rule but at some point, you are bound to see performance vs temp/battery life that proves the law of diminishing returns.

 

[droid37]

so because this supports adobe flash player i can go to the adobe website and install the flash player? if so what about java?

 

[droidrew]

So after flashing this update, I have been having two strange issues that I didn't have in other BB/Froyo ROMs:

1) My default ringtone for notifications keep resetting itself to a different ringtone after I change it. I don't have any ringtone apps installed.

2) The app Profiles is no longer able to control my notification volume settings.

Anyone had a similar experience? The Profiles issue is probably the more annoying of the two since I rely on that app to handle several different profiles that I use throughout the course of every day.

 

[riffdex]

So after flashing this update, I have been having two strange issues that I didn't have in other BB/Froyo ROMs:



1) My default ringtone for notifications keep resetting itself to a different ringtone after I change it. I don't have any ringtone apps installed.



2) The app Profiles is no longer able to control my notification volume settings.



Anyone had a similar experience? The Profiles issue is probably the more annoying of the two since I rely on that app to handle several different profiles that I use throughout the course of every day.

I have neither of these issues on my phone. My notification sound has not changed since ive had the rom, and i just downloaded Profiles to try to see if it did that for me, and it worked perfectly. I suggest you wipe data and reflash the rom new.



Sent from my Droid using Tapatalk

 

[bknewtype]

anyone know how i can change the slot cycle? i know i followed the instructions for a stock droid by dialing ##778 and im suppose to go into "edit" mode. however its been connected me to verizon everytime i dialed it telling me to contact a rep or check my number and dial again.

 

[shoadelf]

is it still possible to do wireless tether with this FRF84B build? if so are there any specifications to make it work besides having the .apk file and using a specific kernel?? (P3 kernel only??)

 

[G.Armour]

I'm not sure if the dev has fixed it, but barnacle wifi tether will work without a new kernal.. but last I checked it wouldn't work with froyo..

Sent from my Droid using Tapatalk

 

[digdug1]

I use Wireless Tether. Works great.

 

[amageus]

Hey guys. Just wanted to put my input in. I have downloaded and tried bb v.04 w/ nextheme. I was happy with its snappiness but i too was having battery issues. I had left my phone off the charger with screen off @ 40-60% battery life when i went to sleep. I woke up to find my phone dead. Wasnt too happy. Ive since then reverted back to v.03. I found bb v.03 to have much better battery life. I use setcpu and have profiles set to 250/250 conservative while screen off with 90% priority. 100% set to high temps.

Heres a list of my upgrades:

BB 2.1 > Leaked froyo frf57 > Nexfro 1.0 > Nexbeast 1.0 > Nextbeast 1.1 > Kangerade 1.0 > BB v.03 > BB v.04 > BB v.03

Now i dont like wiping (my phone) so i dunno if thats the cause of my problems. Was hoping that i wouldnt have issues going to v.04. V.03 gives me by far the best battery life. I have wiped from v.04 to v.03. I was getting battery life with v.03 before and after wipe. May try v.04 again later unless theres a new release of bb. Dont want to wipe but may give that a try.

 

[UBRocked]

Hey guys. Just wanted to put my input in. I have downloaded and tried bb v.04 w/ nextheme. I was happy with its snappiness but i too was having battery issues. I had left my phone off the charger with screen off @ 40-60% battery life when i went to sleep. I woke up to find my phone dead. Wasnt too happy. Ive since then reverted back to v.03. I found bb v.03 to have much better battery life. I use setcpu and have profiles set to 250/250 conservative while screen off with 90% priority. 100% set to high temps.

Heres a list of my upgrades:

BB 2.1 > Leaked froyo frf57 > Nexfro 1.0 > Nexbeast 1.0 > Nextbeast 1.1 > Kangerade 1.0 > BB v.03 > BB v.04 > BB v.03

Now i dont like wiping (my phone) so i dunno if thats the cause of my problems. Was hoping that i wouldnt have issues going to v.04. V.03 gives me by far the best battery life. I have wiped from v.04 to v.03. I was getting battery life with v.03 before and after wipe. May try v.04 again later unless theres a new release of bb. Dont want to wipe but may give that a try.

Based on the fact that I am seeing better battery life with BB V0.4...I'm guessing that you might want to wipe before saying BB V0.4 causes short battery life.

BB V0.4 is based on a different (more recent) leak of Motorola's 2.2 ROM so I'm guessing they have tweaked some things in that leak that have helped with battery life. I did wipe data/cache as well as format all of the partitions (boot, system, data, and cache) as I always do...and strongly recommend regardless of whether you are switching from two completely different ROMs or just upgrading versions of your current ROM.

Wiping & Formatting = less minor problems and annoyances. If you have an issue with a ROM...you will not have "maybe I should have wiped" in the back of your mind as you are trying to fix things.

 

[amageus]

Does wiping prevent your apps from being restored? Adter installing v.03 i waited and waited and none of my apps were being restored minus 3 purchased programs. Then again i havent wiped prior to then so is it normal? Or is a list of installed apps stored somewhere with google?

 

[UBRocked]

Does wiping prevent your apps from being restored? Adter installing v.03 i waited and waited and none of my apps were being restored minus 3 purchased programs. Then again i havent wiped prior to then so is it normal? Or is a list of installed apps stored somewhere with google?

Apps are backed up via your google account. In some previous releases, there have been issues with the market syncing apps properly (or at all), and apps not showing up inside the market. There have been fixes for that released for many of the Froyo ROMs.

Typically, you will get all of your apps automatically when you first sign into your google account...Turn wifi on (if available) and then let the phone sit for several minutes after first signing into your phone...the apps will download and install automatically. If you open the market and download something on your own...you will stop the apps from automatically restoring themselves...so just let it sit.

Also, Titanium Backup is a great tool that will work if your google market apps fail to restore themselves.

 

[amageus]

Well i went ahead and wiped and am now on v.04 again. I just downloaded titanium backup and backed up everything before wipe. This time some of my apps were restored. Running smooth again. Hoping for good battery life. Just saw my battery go from 80 to 60 just now which is not a good sign. But isnt pete using 20% increments? Wel lets see what happens within the next few days.

 

[digdug1]

yeah i dislike the 20% increments so i downloaded a battery widget.

 

[UBRocked]

Well i went ahead and wiped and am now on v.04 again. I just downloaded titanium backup and backed up everything before wipe. This time some of my apps were restored. Running smooth again. Hoping for good battery life. Just saw my battery go from 80 to 60 just now which is not a good sign. But isnt pete using 20% increments? Wel lets see what happens within the next few days.

Yes...it's 20% increments.

Did you format your partitions as well as wipe data? I'm on 22+ hours use today with light phone calls and texting, web browsing, not to mention general phone things like updating apps, playing with ADW Launcher's and Launcher Pro's latest versions to see how they compare after several updates (still have more cool features like swiping gestures with ADW...but LP just works better and smoother ).

After all of that...I'm showing 40% battery remaining on both the notification icon as well as my battery widget. That is crazy battery life for me. Usually I would have been on the charger 4-5 hours ago.

 

[amageus]

No i didn't wipe the partitions. However i've been at 20% since i left work and it's still at 20%. That was 6 hours ago. Very light phone use til now. Im impressed now. Now i wanna see how long it will last with heavy phone use.

 

[Damademan3]

kind of a noob question but i just flashed this rom and i already knew it was oc to 800 already but i didnt think i would not be able to change that in setcpu. i wanted to bump it up by using the app compared to a kernel but im not finding that possible. I know kernels work different on each phone but is there a way i can just use setcpu to oc my phone more than the 800 already done? thanks.

 

[essplode]

I've been using this since it first came out w/ chevy's 1.1 ulv and the results have been amazing.

I think this is the best state my phone has ever been in.

My battery life is unbelievable. I think the lowest its ever been by the end of the night has been %20 and that is after heavy, heavy usage. Even today I played Zenonia for about 2+ hours, browsed the internet, downloaded some apps, etc and my battery is at about 40%.

And it rarely gets warm!

 

[snowquest]

Thank you! This ROM has been fantastic.

With one minor exception, the weather app does not see to find my location based on GPS since rooting and installing BB v0.4. Any ideas?

**Update: so in case anyone else has this issue, I solved it by going to Settings>Location & Security and turning on Use Wireless Networks. When I only had Use GPS Satellites it was not able to find my location. PEBKAC

 

[UBRocked]

kind of a noob question but i just flashed this rom and i already knew it was oc to 800 already but i didnt think i would not be able to change that in setcpu. i wanted to bump it up by using the app compared to a kernel but im not finding that possible. I know kernels work different on each phone but is there a way i can just use setcpu to oc my phone more than the 800 already done? thanks.

You have to download a different kernel if you want to clock over 800MHz. The phone comes with a 800MHz kernel but you can load up to 1.25GHz. Some phones can't run those higher kernels but it has been my experience talking with other people...I don't ever recall anyone saying their phone COULD NOT run at 1.0GHz. 1.1, 1.2 and 1.25GHz may or may not run on your phone. Visit the sticky on in this subforum (posted below) to get more information on Froyo Kernels.

But yes...you can use SetCPU to set the clock and profiles. Pete has made it so that you don't "have to" use SetCPU...the phone will automatically scale itself for the kernel you use but I don't think there are any profiles set up with that (I don't know what the clock changes to while in standby or when charging...SetCPU will be able to do those things so I still use it.

http://androidforums.com/all-things-root-droid/98988-froyo-kernels.html

I've been using this since it first came out w/ chevy's 1.1 ulv and the results have been amazing.

I think this is the best state my phone has ever been in.

My battery life is unbelievable. I think the lowest its ever been by the end of the night has been %20 and that is after heavy, heavy usage. Even today I played Zenonia for about 2+ hours, browsed the internet, downloaded some apps, etc and my battery is at about 40%.

And it rarely gets warm!

Good stuff, Thx for posting (feel like I'm crazy as I haven't seen many people posting the same kind of battery life that I am getting).

Pete does a hell of a job, but I'm thinking the difference has more to do with the base (FRF84B) than it does with any tweaks that Pete has done to it. I don't know if there are changes with JIT and the associated battery consumption or what was changed...but I'll take it

Bad thing about leaks...you don't get a list of things that were changed between the versions

 

[GirLuvsDroid]

But yes...you can use SetCPU to set the clock and profiles. Pete has made it so that you don't "have to" use SetCPU...the phone will automatically scale itself for the kernel you use but I don't think there are any profiles set up with that (I don't know what the clock changes to while in standby or when charging...SetCPU will be able to do those things so I still use it.

I'm one of the people who stopped using SetCPU on Pete's ROMs because I've found that I don't have heat or battery issues without it. Pete's CPU scaling is set to ondemand, with 250Mhz as the minimum setting and the max setting being whatever your kernel max is (mine is 1.1Ghz) and it doesn't seem to be limited to the 7 slots in the kernel. For instance, I'm sitting here watching the CPU clock speed on my Droid (using SystemPanel) while it's charging and basically idle, other than the 20 widgets I have running in the background, and it's changing from 286Mhz to 302Mhz to 486Mhz to 313Mhz to 293Mhz, etc. -- there's a fairly constant variation. It simply responds to whatever my Droid needs at the moment. My real-time battery temp as I'm watching this is 87.8F, which is higher than it would be if weren't on the charger. I've never seen my battery temp get above 115F on this ROM, and that was after really pushing it to see how hot it would get, and the temp dropped very rapidly once I stopped pushing it, even on the charger.

 

[UBRocked]

I'm one of the people who stopped using SetCPU on Pete's ROMs because I've found that I don't have heat or battery issues without it. Pete's CPU scaling is set to ondemand, with 250Mhz as the minimum setting and the max setting being whatever your kernel max is (mine is 1.1Ghz) and it doesn't seem to be limited to the 7 slots in the kernel. For instance, I'm sitting here watching the CPU clock speed on my Droid (using SystemPanel) while it's charging and basically idle, other than the 20 widgets I have running in the background, and it's changing from 286Mhz to 302Mhz to 486Mhz to 313Mhz to 293Mhz, etc. -- there's a fairly constant variation. It simply responds to whatever my Droid needs at the moment. My real-time battery temp as I'm watching this is 87.8F, which is higher than it would be if weren't on the charger. I've never seen my battery temp get above 115F on this ROM, and that was after really pushing it to see how hot it would get, and the temp dropped very rapidly once I stopped pushing it, even on the charger.

If it doesn't rely on the slots that a kernel has...that is a more efficient design IMO. One of my concerns with letting Pete's script run the OC would be when using it as a navigation device and having it plugged in. Have you had any issues with that in terms of it getting too hot? I know that if I don't have charging profiles set up (or if I don't manually adjust the clock to 550 or 600MHz) the phone will get really hot when using the navigation (upwards of 130 deg if at 1.0+ Ghz).

 

[GirLuvsDroid]

If it doesn't rely on the slots that a kernel has...that is a more efficient design IMO. One of my concerns with letting Pete's script run the OC would be when using it as a navigation device and having it plugged in. Have you had any issues with that in terms of it getting too hot? I know that if I don't have charging profiles set up (or if I don't manually adjust the clock to 550 or 600MHz) the phone will get really hot when using the navigation (upwards of 130 deg if at 1.0+ Ghz).

I haven't had any issues with heat while using navigation (and I always have it plugged in to the charger in the car). Now, this might be attributable, at least in part, to the fact that my phone cradle is attached to the A/C vents in the car, so the A/C is blowing directly on my Droid while in navigation mode.