• 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
NetManiC said:
Recommended Updates
-ADW Launcher 0.7 RC1 Launcher-rc1.apk
Place on SD card, rename to Launcher.apk, open up terminal emulator

Code:
suswitchlnchr

* file was renamed to Launcher.apk
* file sitting in root of sdcard
* Android Terminal Emulator being used
* Above commands issued:

Code: 
# switchlnchr
switchlnchr: permission denied
Click to expand...

It's actually

su (enter)
switchlnchr (enter)
 
NetManiC said:
Recommended Updates
-ADW Launcher 0.7 RC1 Launcher-rc1.apk
Place on SD card, rename to Launcher.apk, open up terminal emulator

Code:
suswitchlnchr

* file was renamed to Launcher.apk
* file sitting in root of sdcard
* Android Terminal Emulator being used
* Above commands issued:

Code: 
# switchlnchr
switchlnchr: permission denied
Click to expand...

Just to be sure, you're typing "su" (without quotes), then hitting the return key, then typing the script, then hitting the return key right?
 
racketier said:
First off I've been really happy with the work Fab and BB has done for this ROM to be possible. I'm really enjoying the speed of everything and have had no problems until today.

Today I tried using my maps for the first time and my phone cant lock on to a GPS signal. After rebooting my phone and uninstalling/reinstalling google maps twice, I tried using the Compass application and it wasn't able to find my location either.

Anyone else having this issue? Or perhaps have a suggestion on a fix? My GPS was working fine with BB1.0. I'm hesitant to blame the rom, but I'm not sure what else could be causing the GPS failure.

Running Nexbeast 1.0.1 with P3droid 1.0ghz kernel and ADW launcer
Click to expand...

I'm on cyanogen and I was having major gps locking issues today - so I doubt it's a rom issue... - a complete reboot seemed to do the trick
 
NetManiC said:
Recommended Updates
-ADW Launcher 0.7 RC1 Launcher-rc1.apk
Place on SD card, rename to Launcher.apk, open up terminal emulator

Code:
suswitchlnchr

* file was renamed to Launcher.apk
* file sitting in root of sdcard
* Android Terminal Emulator being used
* Above commands issued:

Code: 
# switchlnchr
switchlnchr: permission denied
Click to expand...

I had the same problem. using root explorer, go to /system/xbin, set filesystem to r/w, find the switchlnchr script, change permissions to allow user to execute (rwx--r--r). That fixed it for me.
 
NetManiC said:
That is exactly what was entered.
What was showed were the results...
:cool:
Click to expand...

Well, the commands the script runs are just these:

Code: 
su
sysrw
busybox rm /system/app/Launcher.apk
busybox cp /sdcard/Launcher.apk /system/app/
sysro
sync

Quantify said:
I had the same problem. using root explorer, go to /system/xbin, set filesystem to r/w, find the switchlnchr script, change permissions to allow user to execute (rwx--r--r). That fixed it for me.
Click to expand...

That's curious, as I have the installer script setting those permissions automatically. Did you use SPRecovery or Clockwork to install the ROM? Also, did you use a P3Droid kernel? I'm wondering if that could have broken the permissions.
 
Fabolous said:
Well, the commands the script runs are just these:

Code: 
su
sysrw
busybox rm /system/app/Launcher.apk
busybox cp /sdcard/Launcher.apk /system/app/
sysro
sync



That's curious, as I have the installer script setting those permissions automatically. Did you use SPRecovery or Clockwork to install the ROM? Also, did you use a P3Droid kernel? I'm wondering if that could have broken the permissions.
Click to expand...

THE SUGGESTED CODE ABOVE FIXED IT! THANKS! :D

Answering the question above:

  • Clockwork was used
  • NexBeast v1.0 applied
  • CPU Speed Kernels applied
  • patch/fix for default fonts
  • patch/fix for MMS
  • NextBeast v1.0.1 applied
  • CPU Speed Kernels applied
  • patch/fix for default fonts
  • patch/fix for Tethering applied
Thanks again! :cool:
 
Yup, using 600mhz p3droid kernel. Everything else is working well. I'm going all day (18 hours) between charges, temps never go much above low 30s, and adw launcher is great...no fcs at all.

Sent from my Droid using Tapatalk
 
My temps are still running really hot. I am getting around 95f when decent load, around 85f after cooling down. I was installing some programs and it peaked at 105f.

This wasn't happening with 1.0
 
Ok so looks like I am the only one that liked Petes script. I had no problems with it so why should I dislike it. I seem to like launcher pro. Smooth and simple with or without apps in dock. I theirs going to be something down there better be good LOL (thats what she said). My temps a;ways stay cool ...;ucky I guess or careful! ;)
 
not sure if its my droid or a bug but sometimes i will reboot and when the droid comes on i will get no service. i have to reboot and it will conect to verizon wireless.
 
My phone kinda freezes up when I get an incoming call...it'll be ringing but the screen where i swipe to answer takes a little bit to pop up...its not instant like it was.

Is there any fix to this?
 
lockcity said:
My phone kinda freezes up when I get an incoming call...it'll be ringing but the screen where i swipe to answer takes a little bit to pop up...its not instant like it was.

Is there any fix to this?
Click to expand...

Are you using setCPU, and if so what is your sleep setting set at?
 
Fabolous said:
You can't from the terminal, but if you boot into clockwork recovery, all you need to do is go into the 'partitions' menu, and you can format all those partitions.
Click to expand...

When i flash ClockworkMod using ROM Manager, then reboot into recovery, it will not go into recovery it will just boot back up. And in order to get it to reboot into recovery i have to put this into the terminal:
su
flash_image recovery /sdcard/recovery-0.99.2b.img
reboot recovery
but that boots me into SPRecovery. The problem is, is that I want to boot up into ClockworkMod. Does anyone know a fix for this?
 
unobtrusivetones said:
I'm having the exact same problem with temps being too high, at idle it's running at 89.6F according to Set CPU just like yours. I've tried Bekits 1.1Ghz kernel and I just flashed P3's 1.2Ghz kernel temps still are a bit high. Love the ROM though and don't really want to change it.
Click to expand...

I don't want to change either but I think I'm going to have to. I'm getting 120F just talking on the phone. I've used both Bekit and P3 and same results. It just seems that it is phone specific, some phones like it and some don't. I used NexTheme and no overheating problems at all. Guess I'll be Beastless.:(
 
darkjinni2 said:
When i flash ClockworkMod using ROM Manager, then reboot into recovery, it will not go into recovery it will just boot back up. And in order to get it to reboot into recovery i have to put this into the terminal:
su
flash_image recovery /sdcard/recovery-0.99.2b.img
reboot recovery
but that boots me into SPRecovery. The problem is, is that I want to boot up into ClockworkMod. Does anyone know a fix for this?
Click to expand...

Problem solved, I had to uninstall and redownload the ROM Manger.
 
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.
 
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.
 
You must log in or register to reply here.
Back
Top Bottom