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

[kcdroid]

Yeah, I'll take a look into it, but he changed the way the graphics work a little bit, so the theming is a little more difficult, and I can't reuse the pictures I made from the last version.

Thanks man. I love the rom its def the best rom I have used. cant wait till the next update.

 

[msg04]

Just upgraded from 1.0 to 1.0.1, and when i tried to run the reccomended updates of the ADW Launcher in Terminal, all i was left with was a black screen with my notifications bar. I rebooted the phone and now its stuck at the boot animation. Anyone else experience this?

Update: Found the problem, I didnt name the file Launcher.apk, it was showing Launcher-rc1.apk. All fixed now!

 

[NickAppleese]

What do you mean by 'diag mode'? In recovery? USB debugging?

Sorry, should've elaborated. Diag mode (holding T on the kb while booting up). Let's my computer assign it a COM port so that I may flash my own PRL to it, and write stuff to memory via CDMA Workshop.

 

[inssane]

Any way to disable screen preview in ADW? That's probably my only bitch, I find it really annoying.

Uncheck "Home Key Binding". When you are on, maybe the fifth screen or in an app for example, home button will take you home. Press the home button again on your home page and it will preview.
I too got annoyed with it constantly launching the previews, but I still wanted that option. Uncheking this made it function as I wanted.

Or you can disable it all together as someone before me mentioned.
Nick

 

[Fabolous]

Sorry, should've elaborated. Diag mode (holding T on the kb while booting up). Let's my computer assign it a COM port so that I may flash my own PRL to it, and write stuff to memory via CDMA Workshop.

Ah! I didn't even know that existed! So is this ROM dependent, or is it separate (like recovery and baseband) ?

 

[NickAppleese]

ROM dependent, I believe. I think the 2.1 update may've disabled this functionality. Whenever I SBF back to 2.0.1, I have no problems whatsoever with my computer picking my phone in Diag mode and being able to connect to it. I don't remember having such problems on custom ROMs in the past.

I use cricket with my Droid. In order to be able to use the Droid on Cricket's network, I have to flash certain settings on my phone to enable talk, text, and the whole 9. I've tried to wipe data/factory reset, but that keeps the ROM, and it only results in FCs.

 

[j4claerr]

I don't think LEDs hack works correctly with Bugless Beast. It even says so in the app description. Hopefully the developer finds out what is causing these issues.


I am having the same issue with the LEDs Hack app as well. I did however work correctly with BB 1.0.

Also when I open the maps on my phone it says on the bottom "login failed" what does that mean? It does appear that everything in the maps is working correctly though.

 

[htowngtr]

When I ran the Launcher update, it FC'd my setCPU.

 

[htowngtr]

It also jacked all my widgets. lol

 

[SirVilhelm]

I don't think LEDs hack works correctly with Bugless Beast. It even says so in the app description. Hopefully the developer finds out what is causing these issues.


I am having the same issue with the LEDs Hack app as well. I did however work correctly with BB 1.0.

Also when I open the maps on my phone it says on the bottom "login failed" what does that mean? It does appear that everything in the maps is working correctly though.

Strange, LEDs Hack works just fine for me. I believe the login failed is from latitude. When I click 'Join Latitude" from the options menu is says 'Loging in...' then 'Login Failed'. Not sure why though.

 

[SirVilhelm]

Ok figure out the Login Failed for Google maps. Basically what is happening is that Latitude is trying to log in and share your location but Android is blocking it, you have to manually allow Latitude access to your location.

Open Google maps and wait for it to say login failed. I don't know if it is necessary but I also went to Menu -> Login and waited for it to fail again. Then while still in maps pull down the shade and you will see an item requesting your permission. Click on that and click 'Allow'. This will allow Latitude to share your location and login.

Hope this helps.

 

[markc2]

Lately I've been getting "The application Gmail (process com.goodle.android.gm) has stopped unexpectedly"..... and my Gmail becomes useless.
I've tried clearing the data in Gmail and Gmail storage, this has happened on this rom and the previous V1. Any ideas? Thanks.

 

[Fabolous]

When I ran the Launcher update, it FC'd my setCPU.

It also jacked all my widgets. lol

Yeah, you'll need to redo your homescreens.

Lately I've been getting "The application Gmail (process com.goodle.android.gm) has stopped unexpectedly"..... and my Gmail becomes useless.
I've tried clearing the data in Gmail and Gmail storage, this has happened on this rom and the previous V1. Any ideas? Thanks.

I've not run into this issue. Did you do a clean install of either (this version or V1), or were they over a different ROM? That's my only idea of what could be causing these FC's.

 

[ne0lyfeism]

Fab - Ran the launcher script as per your instruction. Yes, my widgets were an issue, but all I did was trash and re-add them. The only question I had was in the AWD Settings, it still says rc1.. so I'm not sure if the script worked (which I think it must have or else my widgets wouldn't screw up) or that it did, but the dev didn't update this field.

Any ideas?

 

[Fabolous]

Fab - Ran the launcher script as per your instruction. Yes, my widgets were an issue, but all I did was trash and re-add them. The only question I had was in the AWD Settings, it still says rc1.. so I'm not sure if the script worked (which I think it must have or else my widgets wouldn't screw up) or that it did, but the dev didn't update this field.

Any ideas?

The old one was 0.7-UNSTABLE, the new version is 0.7-RC1. I'm pretty certain you did it right.

Do you have settings to change the scroll speed? You should lower it to about 250 for optimal performance.

 

[ne0lyfeism]

Yeah.. had settings to change scroll speed in the previous version too. But you're right Fab, I do remember it saying "unstable" in the previous version.

My bad..

 

[markc2]

Both installs were with triple wipes, cache, data, boot, system. The problem seems to start when I install a different kernal. I was happy with the default 600 mhz but decided to overclock again, now I've tried bekit, chevy, and P3 and still getting the error, I've also deleted the second gmail account thinking that was part of it but no joy.


I've not run into this issue. Did you do a clean install of either (this version or V1), or were they over a different ROM? That's my only idea of what could be causing these FC's.[/QUOTE]

 

[racketier]

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

 

[s1ckGhost]

Anybody know how to get the settings back on the MMS.APK with functional Video playback?

 

[Quantify]

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.

No issues with GPS here...sorry. I'm using the p3droid 600Mhz kernel, and the new ADW launcher.

 

[flex_droid]

Well, I am finally up and running with the themed launcherpro. Everything is working optimally! As Fab noted, with LauncherPro there is no lag even without overclocking...

In other news, I was running @ 1.2GHz and have now decreased it to P3droid 1.0 GHz. My battery life running P3droid 1.2 GHz sucked really bad. I hope 1.0 GHz gives me a better battery life.

 

[NetManiC]

I am getting a permission denied when I try this. It is changing the prompt when I go type su. Any suggestions?

I also have this issue...PERMISSION DENIED.

Saw the other response to go a long way, but being a newbie, I am wondering if anyone else had a better/easier solution!

 

[Fabolous]

Which script are you trying to run again? I can just post the actual commands to run through the terminal emulator.

I am getting a permission denied when I try this. It is changing the prompt when I go type su. Any suggestions?

I also have this issue...PERMISSION DENIED.

Saw the other response to go a long way, but being a newbie, I am wondering if anyone else had a better/easier solution!

Sent from my Droid using Tapatalk

 

[eeraider]

Which script are you trying to run again? I can just post the actual commands to run through the terminal emulator.




Sent from my Droid using Tapatalk

I tried using the switchlnchr script, and I kept getting a permission denied. Used the adw.launcher.07-rc1.zip from this website and just updated through recovery.

 

[NetManiC]

Which script are you trying to run again? I can just post the actual commands to run through the terminal emulator.




Sent from my Droid using Tapatalk

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:

# switchlnchr
switchlnchr: permission denied