[To Pete] Having Weird Issues With BB v0.4?

[JohnnyDepth]

I've transcended out of the *noob* title and I'm on my way to becoming
a ROM loading machine like most of you guys here on DF...

My issue is with BB and I'm not sure what is causing it/them?

Moto Droid (1)
Bugless Beast v0.4
Froyo 2.2 FRF84B
Using P3's 250mhz-1200mhz (LV) kernel.

I am experiencing zero FC's.
Instead (while browsing using the stock browser)
I am getting either a reboot, but skips the Motorola (M) logo
-an automatic backing out of the browser, and when I attempt to
click the browser again it reloads the home page, and the previous
page is gone.

When I am viewing flash it will either close the app (without a FC dialogue)
OR
I will get a bootloop (and a high temp of about 50 C accompanies this action)

If I pull the battery, and wait.
I can reboot the phone and it works.


Since this is my 1st and only ROM I've tried (and liked)
is it the high clock speed doing this?

If I down clock the speed to say 700MHZ the temps go just as high
(when multi-tasking) and eventually the same problems surface.

Should I not down clock the 1.2GHZ speed to a lower speed and
use a proprietary clock speed? The issue still happened with the stock
800MHZ kernel that came with BB, but far less frequently.

I use zero task killers and only use
*Auto Killer* to finely tune the androids native task managing capabilities.

I don't know if the issue is with BB or not but these issues are killing me!

Battery life is pretty horrible.
If I use the phone for flash, or just light web browsing I can go
from 100-80-60 in an hour? Is this right?


I'd like to add that while getting Quadrant scores of 1573
and a Linpack score of 19+ is awesome I'd rather have a smoother scrolling
app switching experience.

[kennydied23]

You should try to lower your clock speed, you also might want to try a different kernel. Also the Auto Killer could be the cause of the problem, too.

[rlarson_mn]

Pete may not respond. So I will since I have had the same issues with Bb v0.4 when applying a CPU level above the 800mgz that Pete has set up with his ROM release. What we the user community have found is that not all droid phones are capable of going as high a jacked up speed that you have mentioned with out some issues and in some cases serious issues. The original CPU maximum speed is 500mgz prior to any CPU overclockimg. The way I was able to get my unit to be rock solid stable was to not do any advanced over clocking other than what Pete supplies with the ROM. Another tip I will give you from my experience is when using the gps application I reduced the CPU over clocking to the 500mgz level to stop a the unit from over heating and cutting off the gps transmission. I ended up using an application called 'Setcpu' to create a profile to reduce the CPU over clocking based upon the heat of the CPU. Works like a champ.

[benb1974]

Might sound weird, but try kernals with medium or standard voltage. Sometimes I get lower temps and smoother running phone. Like previous poster says about some droids not handling higher freq, some might not respond well to lower voltage. Stock freq is 600 underclocked to 550 from factory.

[ClumsyNinja21]

You should lower your clock speed. Visit "overclocking 101" on this site( forgive me but the auther escapes me). He has an amazing test and try process. Also on some droids, set CPU doesn't always play nice bb. I'm running bb4 with p3's 800mhz and it runs sweet.

[JohnnyDepth]

You should try to lower your clock speed, you also might want to try a different kernel. Also the Auto Killer could be the cause of the problem, too.

I have lowered the clock speed to several different speeds.
I've run different kernels albeit from the same developer.
I'd never b-lame the dev because his work is outstanding and the errors
could be user related. The auto killer is dialed in and isn't the traditional
"task killer" in that it doesn't delete anything arbitrarily but adds functionality to the built in management already native to the Android OS.
Thanks for the help and the post, Kenny. I will look into the
auto killer app more closely.

I have had the same issues with Bb v0.4 when applying a CPU level above the 800mgz that Pete has set up with his ROM release. What we the user community have found is that not all droid phones are capable of going as high a jacked up speed that you have mentioned with out some issues and in some cases serious issues. The original CPU maximum speed is 500mhz prior to any CPU overclocking. The way I was able to get my unit to be rock solid stable was to not do any advanced over clocking other than what Pete supplies with the ROM. Another tip I will give you from my experience is when using the gps application I reduced the CPU over clocking to the 500mgz level to stop a the unit from over heating and cutting off the gps transmission. I ended up using an application called 'Setcpu' to create a profile to reduce the CPU over clocking based upon the heat of the CPU. Works like a champ.

Thanks for the advice!
I researched this and found it to be true.
I couldn't find the original kernel that came with BB0.4 so I tried
Chevy's ULV 125-1200 and using the profiles and settings found on the net
I have a cooler, stable, and almost instant loading phone!!!!

Might sound weird, but try kernals with medium or standard voltage. Sometimes I get lower temps and smoother running phone. Like previous poster says about some droids not handling higher freq, some might not respond well to lower voltage. Stock freq is 600 underclocked to 550 from factory.

I will definitely try this next once I try this new kernel I
just flashed from Chevy. Thanks!

You should lower your clock speed. Visit "overclocking 101" on this site( forgive me but the auther escapes me). He has an amazing test and try process. Also on some droids, set CPU doesn't always play nice bb. I'm running bb4 with p3's 800mhz and it runs sweet.

I never heard of this so thanks! I will give this a shot as well.

(Follow up post regarding the fixes I've done)

[JohnnyDepth]

I hope this can serve as an eye opener in addition to the wealth of information I've found already here at DF and other Droid sites elsewhere...


SetCPU
Reading the defined terms within this app I found that setting the
frequency of the CPU frequency from ondemand to Performance
made my phone much more stable and cooler. at first glance you'd think the
opposite but try it!

-Then I setup profiles for the CPU temps (battery not needed)
-Charging, screen off, battery status are all profiles I also setup...

Amazing!!! Performance, and battery life seems to be better already.

LauncherPro (Plus)
I bought and use LP Plus, so like many users got sick of the
classic "redraw issues" that have plagued other users...

-I turned off all animations
-I set LPP to be kept in memory (general settings)

-Via the Advanced Settings>Memory Usage Settings:

-Use homescreen caches
-Memory usage Preset: High

VM heap size:
According to most users the Moto Droid came stock at 24m
BB v0.4 seemed to increase this to 30m (not sure but it was set to this)

I changed that setting inside the build.prop file
within the system folder (set the R/W) using root explorer to 32m


Auto Killer:
I use the "Agressive" setting and efficiently manages all
apps, programs, process and services set via this setting...

I hope I don't speak tooooo soon when I say this has solved all
of my issues!


Thanks for your help/posts. I really appreciate it!