gotwillk
Android Enthusiast
haven't gone a full day yet on this kernel. kept switching back and forth. and rebooting and plugging it in and whatnot. but so far it seems pretty ok. i have it clocked at 1ghz though, not at the full 1.2.
-
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)
- Thread starter Fabolous
- Start date
-
- Tags
- motorola droid
haven't gone a full day yet on this kernel. kept switching back and forth. and rebooting and plugging it in and whatnot. but so far it seems pretty ok. i have it clocked at 1ghz though, not at the full 1.2.
Fabolous
Superuser
I made the mods to the pete file also and it's nice knowing that SetCPU and pete's script aren't butting heads.
A word of caution for those editing the file on their computers, don't use wordpad
It messes up the unix formatting of the script. Use Notepad++ instead, much better
Then, when you push it back onto the phone, don't forget to chmod 777 /system/xbin/pete
...or run fixperm I guess
A word of caution for those editing the file on their computers, don't use wordpad
It messes up the unix formatting of the script. Use Notepad++ instead, much better
Then, when you push it back onto the phone, don't forget to chmod 777 /system/xbin/pete
...or run fixperm I guess
So your pete file now looks like what you posted, basically just removed the overclocking command at the end? Or does it now just show an empty "bugless beast by pete" ?
GirLuvsDroid
Android Expert
PDR, just to be sure -- there was the overclocking command at the end and a number of lines of CPU commands toward the top that I deleted, so what was left is what I posted (and, as I noted, I added the last line so that I could be sure that it actually ran when I typed the script into Terminal Emulator).
GirLuvsDroid
Android Expert
GirLuvsDroid
Android Expert
So it worked!!! I was going to try this when I got a chance, even using the built-in text editor. I'm glad you read my mind and volunteered to be a guinea pig for me. You know, you're alright in my book!
I wonder why Pete put the 42 second delay... I'm sure it serves some purpose - I'm just curious what it is. He's much smarter than me on Android.
Well, glad we got all that behind us... Now, I'd like to start messing around with the freememory. I understand its purpose, but I just don't want certain apps in the background to be deleted. I guess I could start by deleting the busybox lines from Pete's script.
This is getting fun...
joshi3joshi
Newbie
Fabolous, im getting the 2.1 update notification, and i do have sprecovery installed. however, when i clicked install now when the ota notification came up, sprecovery didnt block it..it just said verifying, and it installed it over this nexbeast rom!! fortunately i made a nandroid backup so i can go back...but the 2.1 update keeps sitting in the system updates. what should i do?
Fabolous
Superuser
What version of SPRecovery do you have? Is it 0.99.3b, the latest? Because it should block it.
Try using ROM manager to flash the latest SPRecovery and seeing if it blocks.
joshi3joshi
Newbie
that might be my problem. i have recovery 1b..haha. Do i just buy rom manager from the android market, and then is there some option to install the newest sprecovery? ive never used rom manager before.
Fabolous
Superuser
Pretty sure the free version does this.
Just gotta scroll down to the bottom and 'Flash Alternate Recovery'
joshi3joshi
Newbie
thanks fabolous! it worked
xmr405o
Android Expert
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
Do we have to run this script every time we reboot?
Fabolous
Superuser
No, it runs by itself.
The reason we ran it once was to see if the message at the end was echo'd, to make sure the script still was running after we modified it.
StingRay
Well-Known Member
Sorry if this should have been a new thread, but really trying to get some feedback on this issue....having some issues that appear to be a result of ESE 81, but need a little help....
I receive my company voice mails on my phone in the form of an email containing a .wav file attachment. I can then listen to the voice mail by clicking the "open" file button, which opens up my wav player, Remote Wave, and plays the message. This "Open Button" is the standard Android icon shown for file attachments.
The ability to listen to these wav files via email has been "broken" with some if the most recent Cyanogenmod ROMs (5.0.5.4 - 5.0.6.2), and most recently with Nexbeast v1.0. Now when I open the email, instead of getting the ability to open the file attachment, I get an email that looks like this....
Not sure what is the culprit, but is not unique to Nexbeast or CM....my previous solution was to downgrade back to a CM ROM that allowed these messages to make it through (CM 5.0.5.3), but I don't want to have to do that anymore....my Droid runs too good on Nexbeast to give it up!
Any ideas from Fab or anyone more knowledgable than me?
I receive my company voice mails on my phone in the form of an email containing a .wav file attachment. I can then listen to the voice mail by clicking the "open" file button, which opens up my wav player, Remote Wave, and plays the message. This "Open Button" is the standard Android icon shown for file attachments.
The ability to listen to these wav files via email has been "broken" with some if the most recent Cyanogenmod ROMs (5.0.5.4 - 5.0.6.2), and most recently with Nexbeast v1.0. Now when I open the email, instead of getting the ability to open the file attachment, I get an email that looks like this....
Not sure what is the culprit, but is not unique to Nexbeast or CM....my previous solution was to downgrade back to a CM ROM that allowed these messages to make it through (CM 5.0.5.3), but I don't want to have to do that anymore....my Droid runs too good on Nexbeast to give it up!
Any ideas from Fab or anyone more knowledgable than me?
Is that on an Exchange account? It looks like something is going on with the message encoding or the headers that is causing the e-mail client on your Droid to not recognize the attachments properly. If it is Exchange then can you try installing the Touchdown trial and see if the problem persists?
StingRay
Well-Known Member
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.