• 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
Am I missing something w/ the Speedtest app? My #s are quite diff then what most are posting. My best so far is 1759kb/s down and 804kb/s up. That's on 3G.

EDIT: Just went w/ Wifi and 5824kbps down and 2559kbps up. Why such a dramatic diff from what everyone else is reporting to mine?
 
YankeeDudeL said:
Am I missing something w/ the Speedtest app? My #s are quite diff then what most are posting. My best so far is 1759kb/s down and 804kb/s up. That's on 3G.

EDIT: Just went w/ Wifi and 5824kbps down and 2559kbps up. Why such a dramatic diff from what everyone else is reporting to mine?
Click to expand...

depends on a few things.
1. what app you are using to run the speed test
2. your signal strength
3. what server you are hitting when running the test.
 
tom108 said:
depends on a few things.
1. what app you are using to run the speed test
2. your signal strength
3. what server you are hitting when running the test.
Click to expand...

The one from SpeedTest.net, strong signal and a server in Tennessee (I live in coastal South Carolina). I'm gathering the higher numbers are better, I just didn't see anyone reporting anything about 800kbps and I'm well into the thousands. That normal, or is that kinda screwy?
 
snowman9031 said:
was that wifi, 3g, 1g and what program were u running
i am running speedtest.net app and wifi i got 4mb dn and 550 up on 3g 354kp dn 613kp up
Click to expand...
regular 3G, speedtest.net app

after rebooting a few times and reinstalling the original 600mhz kernel, it is now 800k down, 600k up
 
htowngtr said:
Is MMS still not working?
Click to expand...

snowman9031 said:
as far as i know fab is working on it. But yeah awol still.
Click to expand...

htowngtr said:
and I hope they can fix the mms issue soon

Love the ROM, but would really like to have video MMS.
Click to expand...

I got a video MMS fix guys, but you do lose the extra features of the new MMS app (customizable notifications, black background, etc).

It will be up in a few.

A FYI for anyone who wants to test video mms without bothering a friend, you can send them from your 'My Verizon' account. Then need to be under 3mb and 30s. That's how I did all my testing!

also, the videos to send from http://www.free-3gp-video.com/
 
Fabolous said:
Video MMS Fix

One warning, you will lose the custom notification features. This is just the stock MMS that comes with 2.1, though I have themed it a little to match NexTheme. The background is white (can't change).
Click to expand...

Awsome.downloading now. I think that I rather have it work than nething else. Some dam good forwards out wink wink. Thanx Fab I will let you know how it is. Is there going to be an update to match Mod.
 
snowman9031 said:
Is there going to be an update to match Mod.
Click to expand...

Don't quite understand this one. This file is already themed to match NexTheme.

As for the MMS fix, this will fix all future video MMS you get, however, the ones you got previous will still not play.

Pretty sure it has something to do with the way the old app saved the messages.
 
cool, got it installed and looks like I did it correctly as the white background is back

no problem with that though, I'd rather it just work
 
Fabolous said:
Don't quite understand this one. This file is already themed to match NexTheme.

As for the MMS fix, this will fix all future video MMS you get, however, the ones you got previous will still not play.

Pretty sure it has something to do with the way the old app saved the messages.
Click to expand...

The custom features. Really no big deal as long as they play thanx fab
 
Just installed this and it is LIGHTNING fast! So i first tested out the 1ghz kernel and noticed my phone was running a bit hot on average use (texting, web browsing, etc), i even went up a notch to the 1.1ghz kernel to see if it would run hotter, but it stayed almost the same temp as the 1ghz kernel. I felt adventurous and decided to run the 1.2ghz kernel, and surprisingly, my phone runs about 5-8 degrees cooler doing the same things i was doing while running 1ghz & 1ghz kernels.

I'm not complaining that I am able to run 1.2ghz and yet have a cooler phone. Like I said, this rom is lightning fast! Anyone else have these kind of results?
 
msg04 said:
Just installed this and it is LIGHTNING fast! So i first tested out the 1ghz kernel and noticed my phone was running a bit hot on average use (texting, web browsing, etc), i even went up a notch to the 1.1ghz kernel to see if it would run hotter, but it stayed almost the same temp as the 1ghz kernel. I felt adventurous and decided to run the 1.2ghz kernel, and surprisingly, my phone runs about 5-8 degrees cooler doing the same things i was doing while running 1ghz & 1ghz kernels.

I'm not complaining that I am able to run 1.2ghz and yet have a cooler phone. Like I said, this rom is lightning fast! Anyone else have these kind of results?
Click to expand...

yea my phone is also running cooler with the 1.2ghz kernel. i just noticed that today. i tried all the kernels and they were all running hot so i decided to try the 1.2 kernel which was an IV kernel unlike the others which are LV. i think for some reason, my phone doesn't play nice with LV kernels. i also had the same issue way back on pete's earlier roms.
 
gotwillk said:
yea my phone is also running cooler with the 1.2ghz kernel. i just noticed that today. i tried all the kernels and they were all running hot so i decided to try the 1.2 kernel which was an IV kernel unlike the others which are LV. i think for some reason, my phone doesn't play nice with LV kernels. i also had the same issue way back on pete's earlier roms.
Click to expand...

How is your battery life so far with the higher kernel?? Think of doing it myself cause I know it could handle it but I was afraid of half way though the day of slacker I was dead. i always try to keep the display off know it is a huge sucker of juice!
 
I have a couple questions. When reading through the thread I am unclear on a couple of things.

1. is it recommended to do the ota fix or is that just for ppl who have gotten the notification to update? I have not gotten anything on my phone about updating, so am I to assume I don't need to do this? I already sprecovery.

2. Could someone explain to me the setcpu thing? Right now my setcpu is enabled. Do I uninstall it, or delete the script then use setcpu? Or just leave everything as is right now.
 
Titaniac said:
** FIRST OFF: DO NOT JUST GO DO THIS. I AM ONLY SOLICITING OPINIONS FROM THOSE WHO ARE MORE EXPERIENCED WITH ANDROID. I AM PRETTY NEW TO SCRIPTING AND STUFF LIKE THAT **

Girl: Thanks for all the help you give us here. I read the posts by you and Nismo explaining to delete the script "Pete". Do you think we could just edit the script so that we could keep the "free memory" features of the script? Specifically, we could delete all of the "echo" statements (EXCEPT THE LAST ONE) because these set the parameters for the CPU speed, governor, etc. The last echo statement deals with the freememory portion. We would also need to delete the last busybox statement that kills SetCPU.

This is just a suggestion so that we could keep the applicable portions of the script while allowing SetCPU to set our parameters and perhaps save battery. On the other hand, once PETE is ran, these parameters are saved; should we then go to /sys/devices/system/cpu/cpu0/cpufreq and delete those values. I'm just not sure how SetCPU would set and maintain its parameters.

Soliciting opinions from those of you who are more experienced in this...
Click to expand...

Okay, here's what I did, and it worked. First, because I had deleted the "pete" file, I unzipped the ROM and pulled the "pete" file from /system/xbin, then pushed it to /system/xbin on my Droid and changed the permissions so that they were the same as all the other files in xbin (all boxes checked in Root Explorer).

Then I used Root Explorer to long-press on the file and open in text editor, and edited all of the CPU commands out (and added "Bugless Beast by Pete" at the end so I would know the script ran), so it looks like this:

#!/system/bin/sh


echo "2560,3840,6400,17920,19200,20480" > /sys/module/lowmemorykiller/parameters/minfree
sleep 42s
busybox killall -q com.cooliris.media
busybox killall -q com.android.mms
busybox killall -q com.android.email
busybox killall -q com.motorola.calendar
busybox killall -q android.process.media
busybox killall -q com.android.deskclock
busybox killall -q com.android.bluetooth
busybox killall -q com.google.android.apps.uploader
busybox killall -q com.android.voicedialer
busybox killall -q com.google.android.voicesearch
busybox killall -q com.android.settings
busybox killall -q com.android.calendar
busybox killall -q com.google.android.apps.maps:FriendService
busybox killall -q com.google.android.gm
busybox killall -q com.amazon.mp3
busybox killall -q com.android.im
busybox killall -q android.process.im
busybox killall -q com.android.music
echo 'Bugless Beast by Pete'

I saved my edits and rebooted, then opened Terminal Emulator, typed su, then pete. The pete file has a built-in 42-second delay, so it takes that long before you'll see the "Bugless Beast by Pete" and another # sign will appear.
 
well I just tried 1300 kernal and I got the magic M over and over so knocked it down to 1200 and so far so good but not really notice ne difference so I might step down to 1100. I will see!
 
GirLuvsDroid said:
Okay, here's what I did, and it worked. First, because I had deleted the "pete" file, I unzipped the ROM and pulled the "pete" file from /system/xbin, then pushed it to /system/xbin on my Droid.

Then I used Root Explorer to long-press on the file and open in text editor, and edited all of the CPU commands out (and added "Bugless Beast by Pete" at the end so I would know the script ran), so it looks like this:

#!/system/bin/sh


echo "2560,3840,6400,17920,19200,20480" > /sys/module/lowmemorykiller/parameters/minfree
sleep 42s
busybox killall -q com.cooliris.media
busybox killall -q com.android.mms
busybox killall -q com.android.email
busybox killall -q com.motorola.calendar
busybox killall -q android.process.media
busybox killall -q com.android.deskclock
busybox killall -q com.android.bluetooth
busybox killall -q com.google.android.apps.uploader
busybox killall -q com.android.voicedialer
busybox killall -q com.google.android.voicesearch
busybox killall -q com.android.settings
busybox killall -q com.android.calendar
busybox killall -q com.google.android.apps.maps:FriendService
busybox killall -q com.google.android.gm
busybox killall -q com.amazon.mp3
busybox killall -q com.android.im
busybox killall -q android.process.im
busybox killall -q com.android.music
echo 'Bugless Beast by Pete'

I saved my edits and rebooted, then opened Terminal Emulator, typed su, then pete. The pete file has a built-in 42-second delay, so it takes that long before you'll see the "Bugless Beast by Pete" and another # sign will appear.
Click to expand...


just did this as well and it echoed back pete after 42s so. :)
however my terminal emulator now reads this when i open it.
exportPATH=/data/local/bin:$PATH
 
tom108 said:
just did this as well and it echoed back pete after 42s so. :)
however my terminal emulator now reads this when i open it.
exportPATH=/data/local/bin:$PATH
Click to expand...

So does mine, but it might always have. I just tried another script (free75mb) and it ran perfectly.
 
tom108 said:
nice. wonder if their are any downsides to running those free ram scripts
Click to expand...

If you get the free RAM number too high, it might keep you from playing music, browsing the web, and other multitasking items all at the same time. If that's a problem, though, you just reboot because the freeXXmb scripts have to be run on each reboot.
 
GirLuvsDroid said:
If you get the free RAM number too high, it might keep you from playing music, browsing the web, and other multitasking items all at the same time. If that's a problem, though, you just reboot because the freeXXmb scripts have to be run on each reboot.
Click to expand...

in other words, it turns into an iphone.
 
You must log in or register to reply here.
Back
Top Bottom