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

Root bugless beast 7.6 now up on the other site!

I've been running at 1.3 for 10 days now, and y'all are getting excited about 1.2 just now? LOL

And most of you are the ones that are all impatient about 2.1 and Flash coming. You're a tough lot to figure out, that's for sure...
 
Having problems with BB7.6

Installed 7.6 via update from 7.5 which was installed via nandroid

1) Several boot loops with the M logo as reported by others. I think this may have been because the default was 1200.....but I couldn't ever get past the boot screen to change this. Finally I plugged it in without the battery and it booted up enough for it for me to change it to 1100. No luck there as well......even 1000 gives me a few random boots every now and then...

2) I seem to be getting a new type of boot every now and then, the screen will shut off and move to the droid icon boot sequence (NO M logo) and then quickly get into my lockscreen. Looks like some sort of partial restart....where it reloads only the OS, not the recovery.

3) There is something wrong with the temp monitor. It seems to be stuck on either 44 or -1C (!!!) regardless of the load and speed. Some boots have 44, some have -1. Tested from 1000 to 500 Mhz. The battery temp seems to be correct. Normally, my CPU temp is about 4 degrees or so hotter than the battery

4) Metamorph does not work. It tells me I have don't have memory in my system dierctory (I have about 32MB left) or I don't have busybox installed. Titanium backup says I have 1.5.3 installed.

5) My alarm did not go off this morning...even though it said it was on and time indicated was correct.

Oh well....it was fun...back to 7.5 for me I think

Thanks!
 
Having problems with BB7.6

Installed 7.6 via update from 7.5 which was installed via nandroid

1) Several boot loops with the M logo as reported by others. I think this may have been because the default was 1200.....but I couldn't ever get past the boot screen to change this. Finally I plugged it in without the battery and it booted up enough for it for me to change it to 1100. No luck there as well......even 1000 gives me a few random boots every now and then...

2) I seem to be getting a new type of boot every now and then, the screen will shut off and move to the droid icon boot sequence (NO M logo) and then quickly get into my lockscreen. Looks like some sort of partial restart....where it reloads only the OS, not the recovery.

3) There is something wrong with the temp monitor. It seems to be stuck on either 44 or -1C (!!!) regardless of the load and speed. Some boots have 44, some have -1. Tested from 1000 to 500 Mhz. The battery temp seems to be correct. Normally, my CPU temp is about 4 degrees or so hotter than the battery

4) Metamorph does not work. It tells me I have don't have memory in my system dierctory (I have about 32MB left) or I don't have busybox installed. Titanium backup says I have 1.5.3 installed.

5) My alarm did not go off this morning...even though it said it was on and time indicated was correct.

Oh well....it was fun...back to 7.5 for me I think

Thanks!


From what I have read on the thread for BB other people are having problems with booting as well.

Ill stick with 7.5, 1 ghz is fine for me right now until they fix the bugs in 7.6
 
For those having problems read the faq rabbitfoot has prepared. It's at the top of Petes section. Can't link or I would've.
 
I've been running at 1.3 for 10 days now, and y'all are getting excited about 1.2 just now? LOL

And most of you are the ones that are all impatient about 2.1 and Flash coming. You're a tough lot to figure out, that's for sure...

I think that's because not everyone was able to overclock to 1.3. So they went back to their respective clock speeds. Some may even feel that their phone might be able to handle 1.2.

Screw this, I'm going back to sleep....
 
I've read the FAQ....while it is good generic information......I didn't see anything addressing the issues I had. Maybe I missed it
 
just installed beast 7.6 and so far so good. Only thing i dont like so far is that the min over clock is now set at 250mhz. I had my sleep/stand by set to 125mhz in my setCPU profile. Its still set in my profile, but if i make any changes my 125mhz will go away.
 
just installed beast 7.6 and so far so good. Only thing i dont like so far is that the min over clock is now set at 250mhz. I had my sleep/stand by set to 125mhz in my setCPU profile. Its still set in my profile, but if i make any changes my 125mhz will go away.

I'm certain the main reason as to why they took 125mhz out is because people were having issues with their phone waking up when receiving calls and such.
 
I've been running at 1.3 for 10 days now, and y'all are getting excited about 1.2 just now? LOL

And most of you are the ones that are all impatient about 2.1 and Flash coming. You're a tough lot to figure out, that's for sure...

I can't get over 1Ghz. Any more and it freaks out. :(
 
If you're experiencing boot issues and stability issues at 1200 MHz:

Change your SetCPU profiles so that they include supported frequencies. Some frequencies (namely, 550 and 950) are not included in the range of this release (0.7.6). This may lead to stability issues when your phone throttles up and down.

I've been running 0.7.6 since last night after an update.zip installation. I got reboot patterns similar to magnus at 1200 MHz so I left it at 1000-1100. Today I edited the profiles, and this seems to have helped if not alleviated the problem entirely. I'm running at 1200, and it's been stable so far. Benchmarks around 170-180, runs 3D and other proc intensive applications without breaking a sweat. My only concern is the lack of tempmonitor support, so I'm leaving it at 800 for now, as my phone tends to run a little hot.
 
Moved to "All Things Root" sub-forum. If you feel it's best merged with similar existing thread(s) just holler and someone will do it.
 
Having problems with BB7.6

Installed 7.6 via update from 7.5 which was installed via nandroid

1) Several boot loops with the M logo as reported by others. I think this may have been because the default was 1200.....but I couldn't ever get past the boot screen to change this. Finally I plugged it in without the battery and it booted up enough for it for me to change it to 1100. No luck there as well......even 1000 gives me a few random boots every now and then...

2) I seem to be getting a new type of boot every now and then, the screen will shut off and move to the droid icon boot sequence (NO M logo) and then quickly get into my lockscreen. Looks like some sort of partial restart....where it reloads only the OS, not the recovery.

3) There is something wrong with the temp monitor. It seems to be stuck on either 44 or -1C (!!!) regardless of the load and speed. Some boots have 44, some have -1. Tested from 1000 to 500 Mhz. The battery temp seems to be correct. Normally, my CPU temp is about 4 degrees or so hotter than the battery

4) Metamorph does not work. It tells me I have don't have memory in my system dierctory (I have about 32MB left) or I don't have busybox installed. Titanium backup says I have 1.5.3 installed.

5) My alarm did not go off this morning...even though it said it was on and time indicated was correct.

Oh well....it was fun...back to 7.5 for me I think

Thanks!
If you're already on 7.5 you should just use the update method. NOT the nandroid method. Just update over your 7.5 and reboot.
If you want to start over use the nandroid method. Wipe cache and data first.
 
The keyboard is nice. Is it just a visual improvement because it seems as though I can type faster with fewer mistakes? Also seems as though there is very little lag as I am currently on my phone using the multitouch browser and the words are being typed on the screen in real time...nice! I had been using the better keyboard with Sholes 2.0.5 and it was really laggy.
 
I had major issues with 1200 MHz as well, and my profiles were not set to anything crazy, AFAICT, but I'll take a close look at them again.

My phone would make it past the Moto icon, but would lock up, then go to black screen, then the LED backlight in the screen would come on and it would sit therre as the phone got hotter and hotter.

Finally, I got into SetCPU after yet another battery pull, and downclocked the default setting to 1100 MHz and all is well.

Like I said, I am gonna triple check my profile settings, but I am almost positive that I did not have any non-supported setting set before....
 
It killed my battery today only because I set up Pandora and Slacker again, and tested both, then played several rounds of MilleBorne, and updated a few apps, and spent most of my time today in a building notorious for its 'shielding' effect.

Still, after 7 hours I had well over 30% battery life....
 
Back
Top Bottom