• 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
Hey everyone, here's the themed version of the YouTube.apk from the EVO 4G. You can enable always HQ from the settings menu. There's also recommended videos if you're signed in, as well as an option for captions! The widget also scrolls through most viewed videos (though it is cut off a little, possibly due to the theme)

YouTube.apk

Install like this (place YouTube.apk on your sdcard first):

Code:
su
sysrw
mv /system/app/YouTube.apk /system/app/YouTube.bak
busybox cp /sdcard/YouTube.apk /system/app/
sysro
sync

Enjoy!
 
Didn't know you had been continuing on with NexTheme lol.

I have Pete's 1.0 but am off to install yours - it was / is pretty nie to look at. :D

Thanks for all your hard work.
 
Help please,

Alright here's the scenario: Im coming from Droidmod because they arent doing shit and i havent gotten an update for almost 2 months now and im trying to flash the mod using Clockwork. I install the NexBeastV101.zip when i am in the Clockwork screen and i reboot my system but EVERYTIME i try it just goes into bootloop. I thought that it just might be the rom i am trying but EVERY rom i try and flash does the same thing. Is there something i am doing wrong?

Basically I go into bootloop no matter what rom i try and flash

Please help! (:


Did you wipe data and cache before installing?
 
Fab, I finally got fed up with the lag issues and FC's so I just did a complete wipe and re-installed 1.0.1 and now everything is much better. I'm running BeKit 1.0G LV and changed to the ThemeLauncher.
 
You just hold down on any text field, select input method, and switch to htc_ime.

Sent from my Droid using Tapatalk
 
Fab, I keep trying to use BT File Transfer and it isn't working to anything. Is something broken in this ROM that doesn't allow BT FTP?

Gives the error of "Machine lacks OBEX FPT or OBEX OPP"
 
Alright..so this may be too much to ask from anybody, but can someone please provide the file for the themed LauncherPro.apk.. the link on the first page of this thread works for others, but I can NOT get it to work for me no matter what browser I use..with firefox, it redirects me to a blank page.. with ie, it redirects me to an http error page.. so, if anybody can do this, it would be much appreciated.

and yes, i have tried many times to download the file.. that link just does not work for me, any other file from there I can download but that one just doesnt work for me..uggh

also, ive tried to download from my phone..and nothing, though I dont think i can download that file ..lol either way, can someone do me that favor, in return.. a cookie!
 
anyone else notice a decrease in performance lately? ever since i flashed to this, i noticed it was running choppier than Pete's BB. it runs fine at first when phone is first booted and also after i kill everything and free up memory in ATK, but after a while it starts to lag again. also noticed battery life was a little worse than BB.

not sure if this is because apps are taking up memory. when it gets laggy, i check ATK and it has only 40M left. seemed like it was an issue with the pete file but also not sure if it could be a SetCPU issue so i decided to disable SetCPU and restore an old pete file i had saved, and now its smooth again. memory killing now seems to be working more effectively. it stays at around 60M of free memory when i check ATK.

using P3 1ghz kernel.

Yes, same experience here and reverting back to the BBv1 "pete" script seems to have fixed mine also. I love this ROM but it really started to lag after a few hours and changing launchers, kernels, apps, etc didn't help any.

NexBeast 1.01/P3 1Ghz kernel/Launcher Pro
 
Does any know have the problem of/know what causes/how to fix the constant acore FCs that I get on BB. and NexBeast? some times its the home and some times its contacts but it always says acore.

+1 I created a topic on this w separate concerns just before I read this.
 
+1 I created a topic on this w separate concerns just before I read this.
I think the issue is a few problems wrapped into one.

First, I installed 1.0.1 over 1.0 and that seemed to start the snowball downhill. Second, I stopped using Pete's script and installed P3Droid w/ setCPU. Lastly, I had ADW with far too many widgets and screens (5) running at once on an unstable frequency (1.2).

Funny thing is that I had NB 1.0 with Bekit 1.2GHz LV and it was running like a champ without any acore FC's. After I overlayed 1.0.1 everything started getting a lot worse. Yesterday I did a full wipe and started from scratch with 1.0.1 and BeKit 1.0GHz LV then changed to the Theme Launcher, not ADW.

My phone has been smooth as glass except for a Bluetooth bug that I mentioned above. I think there was a problem with this newer version being loaded over the old one.
 
any reason why when using the "clock" app in the multimedia dock, the dim setting does not stick? i hit dim and the screen dims for a few seconds and then goes back to normal.
 
I still get sparatic FCs with the ADW launcher sometimes and I did a full wipe before updating to 1.0.1. But it still seems a bit faster and more stable than the stock launcher I was using in 1.0.

I have a Q though; Do you have to be rooted to use the ADW launcher? I tried putting the updated .apk on my wifes stock (unrooted) Droid and it wouldn't install with Astro. No error, it just says something like "unable to install". Thanks for any help on this ;).
 
I have a Q though; Do you have to be rooted to use the ADW launcher? I tried putting the updated .apk on my wifes stock (unrooted) Droid and it wouldn't install with Astro. No error, it just says something like "unable to install". Thanks for any help on this ;).

Yes you do, the "SU" command stands for Super User
 
I think the issue is a few problems wrapped into one.

First, I installed 1.0.1 over 1.0 and that seemed to start the snowball downhill. Second, I stopped using Pete's script and installed P3Droid w/ setCPU. Lastly, I had ADW with far too many widgets and screens (5) running at once on an unstable frequency (1.2).

I have my phone running up at 1.2, I have ADW as my default launcher and I haven't had a force close in two days. I think an app or widget is dont working well with ADW, I noticed some Live wallpapers would cause a forced close over and over. One live wallpaper even caused a reboot loop for me. I also noticed a few other widgets caused some issues. You just need to start with a blank screen and a static background and add one thing at a time, I now have 7 screens full of stuff and no issues
 
I have my phone running up at 1.2, I have ADW as my default launcher and I haven't had a force close in two days. I think an app or widget is dont working well with ADW, I noticed some Live wallpapers would cause a forced close over and over. One live wallpaper even caused a reboot loop for me. I also noticed a few other widgets caused some issues. You just need to start with a blank screen and a static background and add one thing at a time, I now have 7 screens full of stuff and no issues

I have noticed that the Audio Manager widgets can sometimes cause FCs on launchers... I had it happen with the large widget on Helix 2 for a while until the dev fixed it, and then with LauncherPro one of the skins for the Audio Manager widget was causing some FC issues...
 
It was said somewhere several pages back that LEDs Hack wasn't working. I wanted to confirm that since switching over to this ROM LEDs Hack will not allow the screen to sleep. It used to dim and go into a "night" mode but it no longer will.
 
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.

This is what I was looking for, yes LEDs hack is broken for me too.
 
Hey guys, sorry to hear about all these acore FC's.

The dev just finished ADW rc2, so as soon as he puts that out, I'll have it for you guys. Hopefully it is a bit more stable!
 
Fab, anyone else mentioned the bluetooth not connecting for file transfer?

My phone claims that no one has OBEX file transfer enabled (although that's nonsense).
 
OK I have been running this ROM over the weekend and wanted to share my experiences for the sake of feedback if nothing else:

I started with the standard stock 2.1 Root and fooled around with that, installed the p3 LV 800mhz kernel and Overclocked with SetCPU. After trying that out for a bit then I did a data/cache wipe and installed this ROM.

I used the stock kernel for a bit but was unimpressed with my temperatures just doing standard stuff (while web browsing my temps would go up to 105 F or higher)

So I recently installed the P3 1 ghz kernel and I'm under-clocking at 800 max. I may swap to the belkit 1 ghz kernel with the same settings in a few days to compare. So far temperature is better. (comes out of sleep between 57 and 64. Doing some browsing takes me up to 86 or so, back down to low 70s when I return to Home)

My battery life wasn't amazing, however I did have the screen brightness all the way up (outside at the beach) and took over 100 photos with vignette. So I guess the battery life was actually just fine considering how much work the phone was doing.

I'm holding off on final judgement till I have used it as I normally do at home and work.

I've had a few issues with Gallery (sometimes photos will not rotate when I tell them too, sometimes photo albums do not show up in the list, some Force Closes while uploading to picasa and viewing photos at the same time)

I have had at least one acore FC while viewing a contact

Today I installed the Google finance update through the market. It downloaded and installed, then I got a phone call, had a 4 minute phone conversation, hung up and went to clear notifications from the notification pull down and the system rebooted itself. This is the first time that has happened (at least that I have noticed)

I've been using Settings Profiles and have had somewhat buggy experience with it (although that may be the program more than the ROM) Some profiles don't activate or deactivate according to the rules I have set up.

I am running Helix Launcher 1.4b (5 screen) I removed the standard Launcher.apk from the system all together, I also removed IM, CorpCal and Email system apps.

I have ATK, but I do not have it set to AutoStart nor do I really even use it to Kill apps, I check in every now and then to see what is running and what my available memory is. Typically after basic use I'll have 50-60 free with a few services running.

I have the Weather Toggle Flip clock widget, the 2.1 News Widget, pure calendar agenda and a few toggle widgets (power strip, included Nextheme MotoTorch/Ringer Widgets) Screen changes are smooth, no real slowdowns at all, I get an occasional Helix FC at startup, but choosing "wait" usually it resolves itself.

I get a 6.618 MFLOPs on Linpack running 800 max 500 min conservative.

I get 8.303 MFLOPs running 1000 max 800 min performance

Overall it's been a great experience, I'm very impressed, as stated above I've had a few buggy instances, but not really any more buggy than before I was rooted. The gallery issues are a little frustrating, but not a deal-breaker.
 
I loaded this ROM a few days ago, and I'm pretty impressed with it. There have been a few strange things that have happened (the first day I used it, market and browser closed as soon as I started them but that seems to have stopped, and there was once when a call came in and during the 1st ring the phone rebooted itself). Very nice work. :)

I did get the latest build of ADW from AnderWeb, and that seems to make it a bit more stable.

I have not had any problems with TiBu.

Would be great if this ROM was included in RomManager.
 
Back
Top Bottom