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

Root [Themed ROM] NexBeast V1.1 (updated 5/27/2010)

How do I reset this poll!

  • Yes

    Votes: 63 80.8%

  • No

    Votes: 50 64.1%
  • Total voters
    78
I have the rom with the 800mhz kernel, and this thing has been rock solid and snappy as can be over the past few days. The font is the envy of other droid owners I know. Couldn't be happier with this rom. My search is over! Thanks again, Fabolous!! I may want to try one of the LV kernels at higher speeds at some point. What is the preferred way to backup everything just in case the new kernel doesn't load past the white 'M' screen on restart? I'm guessing if it hangs then I'll have to wipe and reinstall the rom, but that would be painful without an easy backup and restore solution. Does ROM manager offer one? Any others recommended?
 
peter_parker said:
I have the rom with the 800mhz kernel, and this thing has been rock solid and snappy as can be over the past few days. The font is the envy of other droid owners I know. Couldn't be happier with this rom. My search is over! Thanks again, Fabolous!! I may want to try one of the LV kernels at higher speeds at some point. What is the preferred way to backup everything just in case the new kernel doesn't load past the white 'M' screen on restart? I'm guessing if it hangs then I'll have to wipe and reinstall the rom, but that would be painful without an easy backup and restore solution. Does ROM manager offer one? Any others recommended?
Click to expand...

ROM Manager does offer an option to "Backup current ROM" and also one to "Manage and Restore Backups." You should definitely do a backup each time before making major changes, including applying Metamorph themes or making changes to your system files.

It's very easy to install a new kernel, though, without having to restore your whole ROM. Make sure you've stored several of the kernel options (including the 800Mhz that you know works) on your SD card. Then, if you're using Clockwork recovery, you can boot into recovery (if you're stuck in a boot loop, pull your battery, then put it back in, and start it up again while holding down the X key), then just choose to "Install zip from SD Card" then "Choose zip from SD card" and then scroll to the one you want and touch your camera button to install it.
 
Stingray, could you try pulling the Email.apk from the last version of CM that worked, and running it on this ROM? Something along the lines of:

Code: 
su
sysrw
mv /system/app/Email.apk /system/app/Email.bak          //make a backup of current Email
busybox cp /sdcard/Email.apk /system/app/                 //Copy over the CM email from sdcard
sysro
sync
 
Fabolous said:
Stingray, could you try pulling the Email.apk from the last version of CM that worked, and running it on this ROM? Something along the lines of:

Code: 
su
sysrw
mv /system/app/Email.apk /system/app/Email.bak          //make a backup of current Email
busybox cp /sdcard/Email.apk /system/app/                 //Copy over the CM email from sdcard
sysro
sync
Click to expand...

Thanks Fab. I'll pull the email.apk from 5.0.5.3, which was the last that worked for me. I believe I had heard of other people having this issue, but it doesn't sound like there are that many people that need this functionality. I spent some time several weeks ago finding out which CM ROM it became "broke" on, so it sounds like something changed at some point in time.

I'll pull when I get home this evening and plug it into Nexbeast and will let you know the result. Thanks for the help. Nexbeast is running so well on my Droid that I may just have to sacrifice my voicemail ability rather than downgrade to another ROM....

Do I need to load the old ROM on my Droid in order to pull it or is there a way to grab the email.apk another way?
 
All you need to do is download the .zip of the ROM and open it on your computer, then find the email.apk and place it onto your sd card. Then you can run the commands that Fab posted.
 
The weirdest thing happened this morning. I've been running BBv1 with NexTheme and the 1.1Ghz kernel. The ROM has been fantastic since Sunday when I flashed it! Except for a few random reboots but I don't mind those, if I did I would stop rooting :)

I unplugged my phone this morning, realized I hadn't turned it off in a few days so I did so (i do every couple days), and thus began a 2.5 hour long bootloop I couldn't stop. I let it go for about 20-30 minutes, then I pulled the battery and let it sit for 30 min. Turned it back on and more bootloops. I didn't have time to mess with it and I was understandably frustrated so I just left it and let it do whatever it wanted.

It would then stay on until I tried to access something, then it would reboot again. (During this time, Beautiful Widgets and Pure Calendar did not have themes, don't know why) This began at about 6:30AM, it did not stop (to my knowledge) until about 9AM. Now it seems to be running fine.

Has this happened to anyone else? Do you think it would be a good idea to reflash? I really can't have my phone out of service for 2.5 hours, I can't let this happen again. Also, if I reflash, I am going to flash NexBeast instead of BBv1 and NexTheme. (I got excited when i saw the BBv1 post on ALLDroid, shoulda checked here first!) Its also possible that it may never happen again, I just don't know.

Thanks for any help!
 
SoDroid said:
The weirdest thing happened this morning. I've been running BBv1 with NexTheme and the 1.1Ghz kernel. The ROM has been fantastic since Sunday when I flashed it! Except for a few random reboots but I don't mind those, if I did I would stop rooting :)

I unplugged my phone this morning, realized I hadn't turned it off in a few days so I did so (i do every couple days), and thus began a 2.5 hour long bootloop I couldn't stop. I let it go for about 20-30 minutes, then I pulled the battery and let it sit for 30 min. Turned it back on and more bootloops. I didn't have time to mess with it and I was understandably frustrated so I just left it and let it do whatever it wanted.

It would then stay on until I tried to access something, then it would reboot again. (During this time, Beautiful Widgets and Pure Calendar did not have themes, don't know why) This began at about 6:30AM, it did not stop (to my knowledge) until about 9AM. Now it seems to be running fine.

Has this happened to anyone else? Do you think it would be a good idea to reflash? I really can't have my phone out of service for 2.5 hours, I can't let this happen again. Also, if I reflash, I am going to flash NexBeast instead of BBv1 and NexTheme. (I got excited when i saw the BBv1 post on ALLDroid, shoulda checked here first!) Its also possible that it may never happen again, I just don't know.

Thanks for any help!
Click to expand...


I wanna say its your kernal doing that. I have had problems with every kernal except the 800mhz one. I have gotten yours to work but it makes my phone act weird. Try flashing the 800mhz kernal to see if your phone responses better to it.
 
StingRay said:
Yes it is exchange...the voicemail system creates an email with a .wav file attachment and sends it to the owner. The purpose is primarily so that the user can simply access voicemails through Outlook, but also works on a mobile device (usually). I had not had any problems when on older versions of CM, but later versions caused the result you see. I was hoping that changing over to Nexbeast or BB v1.0 would solve, but I'm getting the same gibberish, with no wavefile attachment. I've used Touchdown previously, but really don't care for the interface, so I'd like to see if there is a solution to use the native exchange email app.
Click to expand...

I use this type of voicemail every day and have not had any issues. I use TD with my corporate exchange server and the stock client with my personal Exchange server. I have forwarded once of the wavs from my corporate account (on exchange 2003, TD client) to my personal account (exchange 2007, Native client) and have had no issues getting my wav attachments. Sorry, I dont really have any suggestions other than try another client since you are having some sort of compatibility issue here.

Have you tried making a nandroid backup of your phone, wiping your apps and data and then setting up your e-mail for a quick test on a pristine BB or CM install?
 
GirlLuvsDroid, I did what you said in your posting.. pushed the file back to the /system/xbin directory and then applied the chmod permissions as per Fab (doing all of things via console, not using Root Explorer), but I'm getting the following message:

/system/xbin/pete: cannot create /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_free
: directory nonexistent

Any ideas?

**UPDATE**
The issue was resolved when I used Notepadd++ to edit the file and then push it back to my phone.. it's still running a bit warm though under typical load (web surfing, pandora, bluetooth, email), so I may try a different kernel..
 
Fab,
i am loving this Rom you did a great mashup. i just wish it ran a little cooler. i am still in the safe range but it runs about 10-15F warmer that any of my previous roms including your next roms.
 
I just ran the pete script again manually to see if I got any error messages, but it ran perfectly. The only thing I can think of is that the file didn't get edited correctly, or something corrupted between the PC and the Droid. Hopefully, Fab or one of the other gurus around here will have a better answer for you.

UPDATE: Apparently you were typing your update as I was typing my response! LOL.
 
ne0lyfeism said:
**UPDATE**
The issue was resolved when I used Notepadd++ to edit the file and then push it back to my phone.. it's still running a bit warm though under typical load (web surfing, pandora, bluetooth, email), so I may try a different kernel..
Click to expand...

Yeah, Notepad++ follows the Unix way of text editing. If you used Wordpad, it inserts junk characters in when you modify the script.

Glad you got it working!
 
GLD and Fab - Thanks! I tend to keep at these things until they either work or I'm seriously stumped, haha..

Fab, what temps are you seeing during the usage I mentioned in my earlier post? (pandora, web surfing, bluetooth, email)
 
Ok, so the 1Ghz Bekit kernel was a little too warm for my tastes (compared to P3Droid on NexTheme R2 and R3). Tried the 1.2 Ghz and it was even warmer when put through the same paces!

I've just flashed the 800Mhz Kernel.. will keep you posted on temps and such..
 
ne0lyfeism said:
Fab, what temps are you seeing during the usage I mentioned in my earlier post? (pandora, web surfing, bluetooth, email)
Click to expand...

I'm running the 1.2GHz kernel at 1100, and it idles in the low to mid 20s. Moderate usage goes up to high 30s. High usage, such as the scenario you're asking about, goes up to mid 40s.

Seems about right to me :)
 
Fabolous said:
I'm running the 1.2GHz kernel at 1100, and it idles in the low to mid 20s. Moderate usage goes up to high 30s. High usage, such as the scenario you're asking about, goes up to mid 40s.

Seems about right to me :)
Click to expand...

lucky you. at 1200 i get high 40s looking at CNN.
 
ok i loaded P3Droids 1000LV Kernel and all is good. on bott i used to see an immediate 105F but on this kernel it is in the mid 90F it seems to be a noticeable 10-12 degrees cooler all around.
i checked and petes script is still running and wireless tether works as well. so far everything seems fine.

it also seems to be running faster. i throttled it back down to 800 and it seems to run just as fast as 1000 or 1200 on the other kernels.

you can get his kernels here http://www.p3designs.info/kernels/
but i don't take any responsibility for anything bad that happens since these are not approved by pete.
 
tom108 said:
ok i loaded P3Droids 1000LV Kernel and all is good. on bott i used to see an immediate 105F but on this kernel it is in the mid 90F it seems to be a noticeable 10-12 degrees cooler all around.
i checked and petes script is still running and wireless tether works as well. so far everything seems fine.

it also seems to be running faster. i throttled it back down to 800 and it seems to run just as fast as 1000 or 1200 on the other kernels.

you can get his kernels here P3Droid Kernels
but i don't take any responsibility for anything bad that happens since these are not approved by pete.
Click to expand...

Kewl, thanks for the update! Your results are similar to others I've seen reported at AD. I think I'll backup and try it, too.
 
You must log in or register to reply here.
Back
Top Bottom