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

[NetManiC]

Didnt see this in this thread so I will explain what I am seeing:

If I seem to 'push' the GUI/Launcher a little, at random I will get an error:

SORRY!
The process android.process.acore has stopped unexpectedly.
Please try again.

I am running NexB v1.01
P3Droid kernel, 1000Mhz
SetCPU
Default fonts
Did Not installed newest Launcher (htowngtr did), since I had a problem yesterday with Constant Reboots, without ability to stop... restored back to v1.0 and re-applied v1.0.1

Any ideas... I know htowngtr is also seeing this...

 

[Fabolous]

Can someone point me to a tutorial in script writing? I have yet to get Rom manager (paid) to actually restore a backed up rom without first manually re-calculating the md5 sum. It works fine as long as I do that first and I'd like to just write a script so I'm not having to manually do it every time, thanks.

I just used Notepad++ to write my scripts, then save them as a file (no extension). Push them to /system/xbin/ and chmod to 755.

fab, did you get the 2.2 source code?

It's not out yet. Those 2.2 "ROMs" for the N1 and Eris are built off the SDK ROM, which is missing a lot of things. Thats why they run like molasses.

Is anyone else experiencing an autokill of setcpu? It usually happenes to me when i am browsing the web. When i go back my setcpu widget it has stopped working so i have to restart the app and place the widget again. Is there anyway to stop setcpu from being killed? I am running the 900mhz lv p3 kernel.

Could you take a look at /system/xbin/pete for me. I think you can just use ASTRO to open it as a text file. See if there's a line at the bottom saying something along the lines of:

kill com.mhaung.overclocking.apk

If so, you still have the old 'pete' script running. If not, do you have an automated task killer that could be killing it? Make sure SetCPU is on the exceptions list of any task killer.

Didnt see this in this thread so I will explain what I am seeing:

If I seem to 'push' the GUI/Launcher a little, at random I will get an error:



I am running NexB v1.01
P3Droid kernel, 1000Mhz
SetCPU
Default fonts
Did Not installed newest Launcher (htowngtr did), since I had a problem yesterday with Constant Reboots, without ability to stop... restored back to v1.0 and re-applied v1.0.1

Any ideas... I know htowngtr is also seeing this...

I've run into this once or twice. I just either hit wait or force close and it seems like nothing happened. It's curious...I'll try to find out what's up, but so far, it hasn't really happened again.

 

[scutzi128]

Could you take a look at /system/xbin/pete for me. I think you can just use ASTRO to open it as a text file. See if there's a line at the bottom saying something along the lines of:

kill com.mhaung.overclocking.apk

If so, you still have the old 'pete' script running. If not, do you have an automated task killer that could be killing it? Make sure SetCPU is on the exceptions list of any task killer.

I don't see kill com.mhaung.overclocking.apk and I dont have any task killers setup to autokill. a little ot but is it possible to edit that script and add in custom programs to auto kill or does it do that automatically?

 

[Fabolous]

I don't see kill com.mhaung.overclocking.apk and I dont have any task killers setup to autokill. a little ot but is it possible to edit that script and add in custom programs to auto kill or does it do that automatically?

Yes, you can edit the script to autokill more apps, but it only runs once at bootup time.

Just follow the syntax that is already there.


As for SetCPU being killed, I don't know what could be causing it otherwise. Perhaps you're loading up the RAM a lot with other apps, so as the ROM tries to free more RAM, it may be killing SetCPU.

But then again, I've done that too, many times, and SetCPU has always kept running, regardless. Do you have the latest version 1.5.3a?

 

[Fecious]

I've been running Nexbeast 1.0.1 with Bekits 1200lv clocked at 800mhz and it's running so amazing. Cool temps and no lag. ADW is still my launcher of choice because it's just so damn functional.

 

[scutzi128]

Yes, you can edit the script to autokill more apps, but it only runs once at bootup time.

Just follow the syntax that is already there.


As for SetCPU being killed, I don't know what could be causing it otherwise. Perhaps you're loading up the RAM a lot with other apps, so as the ROM tries to free more RAM, it may be killing SetCPU.

But then again, I've done that too, many times, and SetCPU has always kept running, regardless. Do you have the latest version 1.5.3a?

I do beleive that is the issue and yes i do have 1.5.3a. About only running at startup what is the point if it only runs at boot? Also i thought thr rom had a script to try to keep 50mb memory free? Sorry if the questions are basic but root is new to me.

 

[markc2]

Twice today I've had constant re-boots, no stopping, and had to re-install from scratch. Is this because of the ADW launcher? I've also had acore fc's.

Didnt see this in this thread so I will explain what I am seeing:

If I seem to 'push' the GUI/Launcher a little, at random I will get an error:



I am running NexB v1.01
P3Droid kernel, 1000Mhz
SetCPU
Default fonts
Did Not installed newest Launcher (htowngtr did), since I had a problem yesterday with Constant Reboots, without ability to stop... restored back to v1.0 and re-applied v1.0.1

Any ideas... I know htowngtr is also seeing this...

 

[Quantify]

Twice today I've had constant re-boots, no stopping, and had to re-install from scratch. Is this because of the ADW launcher? I've also had acore fc's.

I've been using my Droid hard all day - multitasking while on the phone, Lots of data, switching apps, etc. Zero reboots, freezes, or FCs. Difference may be that I am not overclocked (although I am using SetCPU to keep my sleep/standby profile 250/400).

Loving ADW Launcher...still zippy, finally a launcher that's a smooth as my wife's iPhone...

 

[markc2]

I've been using my Droid hard all day - multitasking while on the phone, Lots of data, switching apps, etc. Zero reboots, freezes, or FCs. Difference may be that I am not overclocked (although I am using SetCPU to keep my sleep/standby profile 250/400).

Loving ADW Launcher...still zippy, finally a launcher that's a smooth as my wife's iPhone...

I think you're right about overclocking, I don't start having issues with this rom until I start using faster kernels....

 

[Fabolous]

About the rebooting, are you using a notification that's located on your sd card? Please try unchecking 'sd card notification' in your sound & display settings.

Sent from my Droid using Tapatalk

 

[markc2]

I wasn't using any off the SD card, except to set phone ringtones off the card which I assume copies to the main "drive". I unchecked it just the same. Afraid to install a faster kernal at this point....

About the rebooting, are you using a notification that's located on your sd card? Please try unchecking 'sd card notification' in your sound & display settings.

Sent from my Droid using Tapatalk

 

[Knitewulf]

How do I install this over Nexbeast 1? I don't wanna lose any of my apps and I don't remember how to do this.

 

[markc2]

Wonderful, now I"m getting gmail "has stopped unexpectedly" again. CRAP, I've about had it.

I wasn't using any off the SD card, except to set phone ringtones off the card which I assume copies to the main "drive". I unchecked it just the same. Afraid to install a faster kernal at this point....

 

[dB Zac]

since I use Handsent for my sms and mms should I or even can I remove the stock message app

 

[Fabolous]

How do I install this over Nexbeast 1? I don't wanna lose any of my apps and I don't remember how to do this.

The instructions are in the first post of this thread.

Wonderful, now I"m getting gmail "has stopped unexpectedly" again. CRAP, I've about had it.

I'm sorry to hear this. I have no idea what could be going wrong. I haven't heard of anyone else with this error either. Could it be an application conflict with something else you have installed?

since I use Handsent for my sms and mms should I or even can I remove the stock message app

You could, but Handcent does not receive MMS without the stock app (you can still send them though)

 

[Papadroid]

I'm a little confused about setCPU. I thought I read from Pete's BB post that you don't need to use setCPU to overclock, that all you needed to do was select the overclock speed that you wanted from the Bekit links and install that. Yet I see everyone here using setCPU to overclock, am I missing something? I mean I'm happy with the way NexBeast is running and I've got the 1000LV installed.

 

[dB Zac]

You could, but Handcent does not receive MMS without the stock app (you can still send them though)

I was afraid handsent wasnt stand alone. Thanks for the info. Also, I have been running Petes roms for a while and I love your twist on it, Its by far the best looking "vanilla" Android rom I have seen yet

 

[dB Zac]

I'm a little confused about setCPU. I thought I read from Pete's BB post that you don't need to use setCPU to overclock, that all you needed to do was select the overclock speed that you wanted from the Bekit links and install that. Yet I see everyone here using setCPU to overclock, am I missing something? I mean I'm happy with the way NexBeast is running and I've got the 1000LV installed.

Not sure if you "need" it but most kernals have steps that you can pick from if you have setCPU and the profile options can really add to battery life. Not to metion the temp monitor

 

[s1ckGhost]

For Anyone Who Has Had android.core foreclosures.

I believe that this will ride itself over. I had this happening plentiful, and was considering going back to just Bugless Beast v1.0.. I ended up trashing my engadget widget.. and the foreclosures just seized to happen.. I havent had a single foreclosure since.. also another thing I did was hide my notification bar and switched back to bekit 1ghz...so maybe it wont ride itself over, but this really helped me. I dont believe you have to hide the notification bar, I just did it cause it looked better with how I have it..






In other words.. there may be a widget that is causing conflict with your phone.. in my case it was Engadget.. probably the fact that it kept fetching articles would be why it was clashing... hope this helps in anyway.

edit: I forgot to ask; is there anyway for me to get the settings from the previous mms.apk (LED change, extra settings) with the working video playback from a video message? Also.. how do I get my phone to not vibrate during a call when I get a text without having to go into settings and unchecking vibrate under notifications? thanks in advance

 

[krichek]

For Anyone Who Has Had android.core foreclosures.

I believe that this will ride itself over. I had this happening plentiful, and was considering going back to just Bugless Beast v1.0.. I ended up trashing my engadget widget.. and the foreclosures just seized to happen.. I havent had a single foreclosure since.. also another thing I did was hide my notification bar and switched back to bekit 1ghz...so maybe it wont ride itself over, but this really helped me. I dont believe you have to hide the notification bar, I just did it cause it looked better with how I have it..
View attachment 4825

View attachment 4826

View attachment 4827

In other words.. there may be a widget that is causing conflict with your phone.. in my case it was Engadget.. probably the fact that it kept fetching articles would be why it was clashing... hope this helps in anyway.

edit: I forgot to ask; is there anyway for me to get the settings from the previous mms.apk (LED change, extra settings) with the working video playback from a video message? Also.. how do I get my phone to not vibrate during a call when I get a text without having to go into settings and unchecking vibrate under notifications? thanks in advance

I was just going to ask the person above who was having the acore FC issue if he had the Engadget app installed.. It causes all kinds of FC issues and severe moments of lag coming out of sleep for me too.

 

[htowngtr]

Fab, I'm having such horrible lag with this 1.0.1 that I didn't have with 1.0 and my ADW will routinely freeze for a few seconds then catch up then freeze again. I'll try down-clocking the P3 1.2 kernel to 1.0, but I know of others who are even running the P3 1.0 kernel who are having problems with acore FC's and lockups and what not.

I'm honestly contemplating 1.0 again.

 

[King_Bean]

I have not switched from V1 since I flashed it. It's the most "perfect" ROM I've ever run (especially with LauncherPro), so why switch? If it aint broke...

 

[Fabolous]

Fab, I'm having such horrible lag with this 1.0.1 that I didn't have with 1.0 and my ADW will routinely freeze for a few seconds then catch up then freeze again. I'll try down-clocking the P3 1.2 kernel to 1.0, but I know of others who are even running the P3 1.0 kernel who are having problems with acore FC's and lockups and what not.

I'm honestly contemplating 1.0 again.

Did you do the update to the latest ADW found in the first post?

To be honest, I've actually dumped ADW in favor of LauncherPro, which I find to be incredibly fast. I've even lowered my overclock to 800MHz, and I can't tell the difference from when I was running at 1.2GHz.

 

[lockcity]

Did you do the update to the latest ADW found in the first post?

To be honest, I've actually dumped ADW in favor of LauncherPro, which I find to be incredibly fast. I've even lowered my overclock to 800MHz, and I can't tell the difference from when I was running at 1.2GHz.

what's the best way to switch to LauncherPro?

 

[Fabolous]

You can just download the .apk I have on the first post under optional mods.

It will install like any other file, as long as you have "allow non market sources" enabled.

Sent from my Droid using Tapatalk