• 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
jlouang said:
Anyone found a fix or experience this? when you go to message and attach you get the icons but the words are blank. I attach a pic I'm on BB V1.0, Nex theme V 1.0.1 and 800mhz kernal

snap20100525010514.png
Click to expand...

Since I never use the stock msg app I never really noticed but mine does the same. I use Handcent.
 
llkevoll said:
Oddly enough last night/this morning at work my entire home screen <all 3 of them> went totally blank! ADW had LAB and RAB in place of my icons and the entire screen blank aside from the LWP running? Anyone else experience this? It wasnt a slow load....it was a NOT there...Flashed back to 1.0 for now...
Click to expand...

That's weird. I haven't had any problems with ADW rc1 or rc2.

As much as I respect LauncherPro...not sure why people aren't giving ADW the love. I think ADW is at least as snappy, and I've had no fc, reboots, lags...anything. The task bar is perfect...you get 8 customizable shortcuts!

NexBeast plus ADW plus no overclock = perfection for me. I'd always assumed I'd give CM another shot when they released 5.0.7...but now I'm thinking, why?
 
Benn running this for a couple of days now. LOVE the ADW launcher and this ROM is really really smooth. I was having issues galore with BB 1.0 after running it for a few days. I have had increased battery life with this ROM and just about zero FC's on anything. Great work Fabolous
 
jlouang said:
Anyone found a fix or experience this? when you go to message and attach you get the icons but the words are blank. I attach a pic I'm on BB V1.0, Nex theme V 1.0.1 and 800mhz kernal
Click to expand...

Yeah, that's actually a little bug, since I got the text to be white with a black background, the text for those attachment options is also white, but that pop up background is white too.

Hopefully I can fix that for the next release.
 
Fabolous said:
Yeah, that's actually a little bug, since I got the text to be white with a black background, the text for those attachment options is also white, but that pop up background is white too.

Hopefully I can fix that for the next release.
Click to expand...

Since you brought it up, when is the next release Fab :D
 
Finally got the themed launcherpro to download....switched back.. lol i rather the simple icons rather than the nextheme icons on the launcher.

Also want to note that i am running the most current nexbeast, and two days ago it was going super slow and laggy, didnt change any icons as i found it a perfect opportunity to test out my theory...;

All it needed to do was rest, i presume, and it went back to running as fast as ever by morning. Note that i did not remove any apps, or widgets or did anything to it at all, period. Did not reboot or turn off till morning, just left it on standby.. and it fixed itself.

Sent from my Droid using Tapatalk
 
Fabolous said:
You need to reboot to get rid of the transparency bug.

Also, you need to change the home key behavior, if you don't want it to bring up the preview.

It's all in the settings.

Sent from my Droid using Tapatalk
Click to expand...

Thank you, got it working perfectly! Now to get LEDs Hack working ;p
 
Hello? Anyone have any comments on the bluetooth? Come on now. Not exactly a small bug if it doesn't work for file transfer.
 
htowngtr said:
Hello? Anyone have any comments on the bluetooth? Come on now. Not exactly a small bug if it doesn't work for file transfer.
Click to expand...

Well I know for a fact that when my Wife and I got Droids, I xfered a bunch of MP3s via BT FTP over.. so it worked at one time!

It doesnt work now however!

:eek:
 
Yes you have to download an app for it off the market called Bluetooth File transfer... Android did not have it as part of the OS untill I believe 2.0. Also as of right now I believe it is only computer to phone and not phone to computer.

This really has nothing to do with this ROM...
 
ska.t73 said:
Yes you have to download an app for it off the market called Bluetooth File transfer... Android did not have it as part of the OS untill I believe 2.0. Also as of right now I believe it is only computer to phone and not phone to computer.

This really has nothing to do with this ROM...
Click to expand...
I know exactly what it is and I use it all the time (well, I DID use it before).

EStrongs gives the same error.

I will try to get screenshots and post. It has everything to do with the build whether it's Pete's BB or Fab's 1.0/1.0.1

I am going to backup my ROM and load Fab's 1.0 to see if something in 1.0.1 "broke it". Then I will download a different ROM and see what happens with it (like CM or something along those lines).
 
It looks like the issue is between phones. I used a different computer (same Win 7 x64) and its working for transfers.

Will try again with NetManic to get our phones to sync up.
 
23u7vnq.jpg


What happens after I attempt to connect with NetManic who is running the same 1.0.1. I am going to try again with the other computer.
 
I got a little over-ambitious with Pete's rm* scripts and deleted the stock messaging app. Now I can't receive MMS (turns out Handcent needs the stock app for MMS). How do I re-install? I tried extracting Mms.apk from the NexBeastV101.zip file and installing with Root explorer, but that was a no-go.
 
Fabolous said:
As for the camera bug, can you elaborate? I can still take pictures with 40% battery.
Click to expand...

when battery gets to 40% and i try to take a pic, the pic comes out either half cut off or is really dark. even with flash on. it would flash but it would be a very dim flash.

this happens to 90% of the pics taken. it only happens when i need flash and in dark places, like a bar. if its in a somewhat lit place, its better, but still the pic gets cut off. its actually better on the Nexbeast compared to on BB, where pics would just be super blurry and out of focus in addition to the pics being cut off. my sister also has the same issue but she's on BB, so hers is worse.

this doesn't happen at 50% battery and above though.

i'm surprised no one else has mentioned this. i remember reading a long while back about ppl having this exact same issue on the older roms (i think 2.0 or 2.0.1) and then it was fixed. but now its broken again.
 
Are you going to port over the new lockscreen? The one that allows an actual PIN(like iphone) as a way to unlock the phone. the one on CM isnt the real deal.
 
NetManiC said:
Well I know for a fact that when my Wife and I got Droids, I xfered a bunch of MP3s via BT FTP over.. so it worked at one time!

It doesnt work now however!

:eek:
Click to expand...


Not sure if it is the same thing or not but. I went to Walmart earlier to print out some pictures for my daughters school project. When I got there I realized I'd left my CF card at home with the pictures on it but, I had my wife email them to me and I was able to transfer them to the machine there in the store over BT without issue.
 
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...

Just a follow up to my high temp issue:
This may sound strange but after flashing different kernels and trying everything to get my temps lowered with no success, I changed my default home launcher from ADW to LauncherPRO and Bam! temps lowered almost immediately. I went from temps idling in the high 80's to low 90's F using the ADW Launcher to high 60's, low 70's F using LauncherPRO.

I've switched launchers back and forth several times and confirmed the ADW launcher causes high temps on my droid. Wierd :eek:
Maybe I'm a rare case but hopefully this might help someone else with their high temp problems.
 
adwfroyo.png


Anyone know how to get the RAB and the LAB or whatever they are called to be colored icons like in the above picture? Mine are still the "grey" ones. Or is this not possible? I looked in the setting and could not find an option.
 
j4claerr said:


Anyone know how to get the RAB and the LAB or whatever they are called to be colored icons like in the above picture? Mine are still the "grey" ones. Or is this not possible? I looked in the setting and could not find an option.[/QUOTE]

UI Settings > Tint AB

uncheck it. :)
Click to expand...
 
The replacment phone is here and has 2.1 preinstalled. My question about the old phone, after putting the 2.01 .sbf "live without fear..." back on, (it was working for the one or two days while I waited for the replacement), I then did a factory re-set and reformatted cache etc. to wipe the phone. I had tried then to let it go through the 2.1 update after the new phone arrived, and again it gets stuck at the M. Is there any reason NOT to let it go back to Verizon like this? I mean it should just be a stock phone with stock radio correct? Just stuck at the M, with no "non stock" recovery. My reason for exchanging as previously mentioned is data corruption on the SD card, several times since I got the phone in January.

I just don't want to send it back and somehow they know it's been rooted before and stick me with a new phone price billing.... Any help greatly appreciated, thanks.

Fabolous said:
I think this is a hardware issue. Hopefully your replacement will be working well!

If it doesn't come with 2.1 preinstalled, you can easily root it with the file found here:

http://androidforums.com/all-things-root-droid/78548-how-easier-method-root-2-1-a.html

If it does come with 2.1, you can just .sbf SPRecovery on there and load up a custom ROM.
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom