What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[ROM] Zero Blur! Zero Lag! rubiX Focused 1.0

Can't edit posts from app, sorry for double post...

Is there anything I can do to install a while clean rom (rubix) and also not lose all my text messages, apps and settings?

Sent from my DROIDX using DroidForums App

You'd have to back them up first using a backup app. Because you will need to wipe all data/cache to install.
 
Would titaniym do the trick?

Sent from my DROIDX using DroidForums App

I would assume so, Ive never used Titanium but heard good things about it....I use My Backup Pro.

Yes, but be VERY careful with tatanium that you don't backup (or.. at the very least, that you don't RESTORE) anything from SYSTEM.
MyBackup Pro doesn't backup system stuff, titanium gives you the option to...

If you backup system stuff from one ROM or install, and restore it to a DIFFERENT ROM or install, it can cause all kinds of horrid stuff... and the only fix is to reinstall. :(
 
What would happen if I installed rubix blurless on top of birdmans rom?

Sent from my DROIDX using DroidForums App

It would install fine. The install script will wipe the /system dir (where all of birdman's ROM is installed), and you would need to wipe data and cache to get rid of any incompatibilities... should work great.
Just follow the instructions in the first post of the thread (or use ROM Manager). :)
 
How does one sync contacts with facebook with out blur?

Sent from my DROIDX using DroidForums App

Saw a post answering this that mentioned getting facebook app from market, and checking the sync box.

If it's still not syncing, go to Menu> accounts, and verify sync settings there...
 
There is definitely some kind of battery drain issue with this ROM. Whether its the cell standby issue (which was in the high 70s for me) or something else, its definitely present. I really wanted to stick with this ROM because of the speed but I have switched back to stock minus some bloat and battery life is back to normal (which is very good). Hopefully the issue can be addressed and resolved in a future release.
definitely something different in this ROM that is causing battery drain. I have hacked this droid x to hell and back, tried just about every rom out there- rubix 1.0 doesn't like my device.... battery killed
How long is your battery lasting you though...compared to stock. I mean in hours per day with normal usage.

The battery statistics IMO dont mean squat. Mine are always reading high, however I get anywhere from 14-18 hours battery life with the extended battery, better than with the stock ROM. But thats my experience.

I got about 8-11 hours with rubix. I get about 20-30 with stock.

I've used mine for testing ... almost 8 hours straight, and had around 60% battery left... Battery life in Focused for me is AMAZING.

If you came to ask for assistance, rahther than to complain.... the first thing I'd start with.. would be:
What was done after the ROM was installed?
--Theme?
--Mods?
--Overclock?
--Restore anything from backup?
--When you installed, confirming that you wiped data/cache.
--Any task killers, battery manager applications, etc.? (99% of these will WORSEN your battery life, ESPECIALLY task killers!)
 
uh, i haven't complained, i was just giving info which might help others in their quest for knowledge.

is it so hard to believe someone else?

edit: and their quest for a phone that doesn't die after 12 hours
 
Last edited:
and i do believe you... but my experience is different.

period.

edit: if you want to hear complaining, i could write alot more but that wouldn't help anybody.
 
Last edited:
There is definitely some kind of battery drain issue with this ROM.

This was your very first post.

Now, there is obviously definitely NOT any type of battery drain issue with the ROM....

Otherwise EVERYONE would be having the issue. And honestly at the moment you are the ONLY one having that issue.

So you see why people are skeptical, we arent saying your lying, simply stating that its got to be more than the ROM itself.

PS- Like I said, I run this ROM themed, overclocked @ 1.45ghz medium voltage (which isnt even very low) and STILL get 15-18+ hours or so life or better with adequate usage.

PPS- Now if another ROM is working great for you....thats great, its all about personal choice, dont think anyone cares which ROM you choose.
 
Last edited:
uh, i haven't complained, i was just giving info which might help others in their quest for knowledge.

is it so hard to believe someone else?

edit: and their quest for a phone that doesn't die after 12 hours
and i do believe you... but my experience is different.

period.

edit: if you want to hear complaining, i could write alot more but that wouldn't help anybody.

Ok. so .. let us help you!
But.. you didn't answer a single question I listed in my post.....
 
Otherwise EVERYONE would be having the issue. And honestly at the moment you are the ONLY one having that issue.

Well, not from what I have read. A good number of people are having the same issue.

Now, there is obviously definitely NOT any type of battery drain issue with the ROM....

And you are absolutely, positively, most definitely sure of this??? I'm a programmer and I know how it goes. QA and use case testing gets the lowest priority, unfortunately.

Listen, I believe you. I think this ROM does work for the majority of people. But something is going on. I've eliminated all the usual suspects with this install. I fought it for a week. Maybe its my particular hardware, I dunno. I will say that I have not tried to install this immediately after a SBF. I may try that next and report back. Again, the speed of this ROM made it hard to go back but I could not solve the battery issue.
 
^Simply put, my argument is this.

1. If it was the ROM, everyone would be having the same issue. Thats not the case.

2. So...I believe you have battery issues, and they could be tied to this ROM....but I think its more than just the ROM doing it...thats it.

You may be a great programmer...and you've stated you've done a ton of testing....but like Sephtin said, if you want help or wanted to help someone else you would answer his questions or explain in detail what you've done....instead of just coming like you did....cause I just think everyone took it as a blatent complaint. Just trying to help and anyways makes no difference to me....mine's working great.
 
Last edited:
^Simply put, my argument is this.

1. If it was the ROM, everyone would be having the same issue. Thats not the case.

2. So...I believe you have battery issues, and they could be tied to this ROM....but I think its more than just the ROM doing it...thats it.

You may be a great programmer...and you've stated you've done a ton of testing....but like Sephtin said, if you want help or wanted to help someone else you would answer his questions or explain in detail what you've done....instead of just coming like you did....cause I just think everyone took it as a blatent complaint. Just trying to help.

well, the thing is, reading other people's description of the same problem helped to validate my decision on switching back so I guess I was trying to do the same thing for other people experiencing my problem. No offense, that's just the way it is.

edit: and also, problems are not absolute across use cases. my job would be alot easier if it were.
 
OK - I'm all set up with rubiX. Everything I use seems to be working great. I'm OC'd to 1.3 GHz.

My question (probably due to lack of understanding) concerns the Droid X and how it was supposed to be locked out by Motorola from any custom ROMs. Has this all changed now? I tried keeping up with the news but I must have missed something.

What makes rubiX work when the last I heard the X would be bricked by custom ROMs?
 
Back
Top