Rubix vs Apex

[Inkarnit]

As much as I love to just run random scripts in my terminal emulator...

What exactly does this do? I understand you are saying it increases battery life and performance, but how does it do this? Does it sacrifice anything?

 

[teh_g]

So after using rubiX a little bit:

*I think there is an ever so tiny performance increase. It might be my imagination
*I don't like that I can't get StreetView to install on runiX. I don't use it, but knowing that I can't install it is annoying
*I like the Blur camera better than the rubiX one
*The boot animation on rubiX is better, it doesn't overflow in to the lock screen like in ApeX
*I like that rubiX is NOT overclocked by default. I don't like being forced to do things like that to my hardware, especially since overclocking does void your warranty while rooting and using ROMs doesn't
*Battery life is still up in the air. I think that they are about the same, maybe rubiX is a little better? My guessing isn't exactly scientific
*I like the rubiX Juice theme a lot. If anything, that is keeping me from switching back to apeX (though I don't like the thing in my notification window.

Honestly, beyond minor things, the two ROM are basically the same in my comparison of everyday usage.

 

[drod2169]

Different phones will have different results with different roms. Not all phones will run exactly the same even if they are on the same rom.

Your mileage may vary.

+1 to this. Even though are phones are made EXACTLY the same, they all run different. Exactly why some can run 1.8ghz overclock and some barely 1.15

The best way to know what works best for your phone is to try them all!
rubiX
FlyX
Apex
zapX
TranQuility
soon to be Ultimate Droid and Simply Stunning
plus whatever jrummy has cooking up

Are all great roms.

 

[drod2169]

*I like that rubiX is NOT overclocked by default. I don't like being forced to do things like that to my hardware, especially since overclocking does void your warranty while rooting and using ROMs doesn't
.

Actually, rooting does void your warranty. That's why it's necessary to flash back to stock before sending it in/taking it to Verizon

 

[teh_g]

Actually, rooting does void your warranty. That's why it's necessary to flash back to stock before sending it in/taking it to Verizon

I dug through the ToS of Asurion and didn't really see anything that points to rooting voiding their warranty. Here is my post on Android Central: Does Rooting Actually Void the Asurion Insurance? - Android Forums

And for laziness, here is the full text:

I did some searching and came up with nothing definitive.

Here is my perspective on this. I read through the entire document for the Wireless Phone Protection by Asurion. It say anywhere in the ToS that phones with modified software will not be covered.

Let's start with covered property in Section A.2, Covered Property:

[...]The wireless device owned by you for which: 1) the unique identification number (International Mobile Equipment Identity (IMEI), Electronic Serial Number (ESN), or Mobile Equipment ID (MEID) of such wireless device is reflected in the records of the Wireless Service Provider at the time your coverage initially became effective; and 2) for which airtime outgoing usage has been logged with the Wireless Service Provider on your account after coverage became effective;[...]

Rooting does not change any of the identification numbers as far as I know. Awesome, so far so good. Let's move on to what isn't covered. I have picked some that could possibly be used against you, but I feel don't mean a thing.

Property Not Covered (Section A.3)

e. Property that has been entrusted to (including to and from) others for any service, repair or replacement, other than Asurion Insurance Services, Inc., or its designee.

I know when I root it, I am not giving it to anyone else, I am doing the modification.

h. Wireless Equipment whose unique identification number (ESN, MEID or IMEI) has been altered, defaced or removed.

Again, I am pretty sure none of that is changed by rooting.

I see no mention of software modifications, perfect. Now we can move on to things that cause Exclusions. The blanket statement from this section (B.2) is, "This insurance does not apply to loss or damage caused by or resulting from any of the following:" I read that as saying that you can do things as long as it doesn't damage the hardware.

e. Electrical and Mechanical Breakdown
Mechanical breakdown and disturbance caused by battery power or any artificially generated electrical current.

Looks like modding the hardware or software for overclocking will definitely exclude you from getting a new phone from Asurion.

i. Programming, Repair Work
Programming, cleaning, adjusting, repairing, modifying, or performing any other work upon Covered Property.

Ah-hah! Programming ehh. Normally this would be the point where rooting is voiding this warranty. But reading the header where it talks about causing damage, I think we are okay for rooting. We can dig a little more in to one more exclusion of interest.

j. Virus
Computer virus or any other malicious code or similar instruction that:
(1) Disrupts the normal operation of the Covered Property; or
(2) Results in destruction of or unsuitability of data or programs stored in the Covered Property.

Again, I think this does not apply to us, since we aren't really disrupting the "normal operation" of the phone at all. Even if we extend this to what smart phones are normally doing, web browsing, running applications, taking pictures, etc. I firmly believe that having root access does not interrupt the normal operations.

If you end up disagreeing with Asurion, you have already agreed to arbitration, which is a little scary, but I think doable. I went ahead and attached their ToS brochure.

Any comments on this?

 

[drod2169]

Ah see that's perfect for asurion, but asurion is a seperate company for verizon, and asurion doesn't warranty your phone, you pay a monthly fee for them to insure it, not verizon

Sent from my DROIDX using DroidForums App

 

[C21johnson]

I consistently jump back and forth between ApeX, RubiX, and Fission each time there is a new release just to do some testing, and help find bugs for developers.

With my experience, I've had the best battery life with ApeX, plus, sometimes, I enjoy "some blur" on my phone.

RubiX is also a great ROM, but perhaps it's just the performance on my phone. I haven't flashed the newest release, but older versions seemed to have periodic reboots on the lock screen. Plus battery life was below par. Perhaps I'll try to run these lines with the newest update of RubiX and see if I can get better performance and stability.

I am currently on Fission 1.2; I just flashed it over yesterday. So far, it's performing well. The developers have done a great job considering that they do not have a DX device to work with. I'll probably continue to support this ROM and I like the developers and their outlook on the developing community.

I solely base my decisions on a stable and battery efficient ROM. I mainly use my phone for college purposes, taking notes, recording lectures, scanning notes, apps to help study, etc. As a premed student, I am hammered with endless classes and lab times, so battery life is a MUST as is the lack of FC's and reboots. Don't get me wrong, I do like speed, but you'll see me underclocking/undervolting just to get a few more hours of battery life.

Based on my experiences...

Fission:
----- Speed: 4.0/5
----- Battery: 4.5/5
----- Compatibility: 4.0/5
----- Stability: 4.0/5
----- Customization: 2.0/5
----- Overall: 3.7/5

RubiX:
----- Speed: 4.0/5
----- Battery: 3.0/5
----- Compatibility: 3.5/5
----- Stability: 3.0/5
----- Customization: 4.0/5
----- Overall: 3.5/5

ApeX:
----- Speed: 5.0/5
----- Battery: 4.0/5
----- Compatibility: 3.0/5
----- Stability: 3.0/5
----- Customization: 3.0/5
----- Overall: 3.6/5

They're all, in my opinion, very close overall, but looking at certain factors, some prevail over others.

 

[randroid123]

Randroid123
What do you gain by installing ADW or LP to system? Will they still update via market? And how do you do that? Thanks

Sent from my Droid X w/ Fission via Tapatalk

Having the launcher installed to you system/app folder as opposed to your data/app folder will make the launcher load much faster at boot and will ensure that it is one of the last things that android will resort to kicking out of memory... So its generally snappier.
You attach it to the system by using root explore... Find the app in data/app, and move it to system/app... Then set permissions to 644 and reboot! U will have to redo this process for every update because the market won't recognize it from your system file

 

[drod2169]

I am currently on Fission 1.2; I just flashed it over yesterday. So far, it's performing well. The developers have done a great job considering that they do not have a DX device to work with. I'll probably continue to support this ROM and I like the developers and their outlook on the developing community.

as i'm very biased, i won't comment on the rom selection

but

i'm on team defuse. i developed the core for fission, so we do have a droid x to work with just wanted to enlighten you a little

 

[hyperlite]

I am currently on Fission 1.2; I just flashed it over yesterday. So far, it's performing well. The developers have done a great job considering that they do not have a DX device to work with. I'll probably continue to support this ROM and I like the developers and their outlook on the developing community.

as i'm very biased, i won't comment on the rom selection

but

i'm on team defuse. i developed the core for fission, so we do have a droid x to work with just wanted to enlighten you a little

I love fission, but you guys (DeFuse) should probably stop asking for donations on the basis that you don't have a droid x to test builds on...

 

[drod2169]

I am currently on Fission 1.2; I just flashed it over yesterday. So far, it's performing well. The developers have done a great job considering that they do not have a DX device to work with. I'll probably continue to support this ROM and I like the developers and their outlook on the developing community.

as i'm very biased, i won't comment on the rom selection

but

i'm on team defuse. i developed the core for fission, so we do have a droid x to work with just wanted to enlighten you a little

I love fission, but you guys (DeFuse) should probably stop asking for donations on the basis that you don't have a droid x to test builds on...

Well let me clarify a little..

I developed the ground base for fission.

I haven't contributed (asides from telling ang various things to fix bugs) since 1.0 because I've been focusing on rubiX. My role on the team is wayyyy stepped down from what it was. Angdroid makes the final call on what gets released, so he's trying to get one for him to be able to test, since I'm either un reachable, or busy when he needs something tested. I'm more of an advice/bug fixer now, although once I get what i'm working on completed, I'll be a lot more involved in the team.

 

[luv2increase]

I am currently on Fission 1.2; I just flashed it over yesterday. So far, it's performing well. The developers have done a great job considering that they do not have a DX device to work with. I'll probably continue to support this ROM and I like the developers and their outlook on the developing community.

as i'm very biased, i won't comment on the rom selection

but

i'm on team defuse. i developed the core for fission, so we do have a droid x to work with just wanted to enlighten you a little

I love fission, but you guys (DeFuse) should probably stop asking for donations on the basis that you don't have a droid x to test builds on...

What?!? These people are bringing the cosest thing we have to true ROMS for the DX/D2, and you thinking they should quit asking for donations?

That is illogical.

Sent from my DROIDX using Tapatalk

 

[GTvert90]

Randroid123
What do you gain by installing ADW or LP to system? Will they still update via market? And how do you do that? Thanks

Sent from my Droid X w/ Fission via Tapatalk

Having the launcher installed to you system/app folder as opposed to your data/app folder will make the launcher load much faster at boot and will ensure that it is one of the last things that android will resort to kicking out of memory... So its generally snappier.
You attach it to the system by using root explore... Find the app in data/app, and move it to system/app... Then set permissions to 644 and reboot! U will have to redo this process for every update because the market won't recognize it from your system file

Just move the apk or is there a folder and whatnot? And what's 644 look like threw root explorer permissions? I never understood the numbers for permissions


Sent from my Droid X w/ Fission via Tapatalk

 

[armedmonkey]

What does this do?

$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# chmod 755 /system/etc/init.d/01cpuod
# chmod 755 /system/etc/init.d/02vm
# busybox run-parts /system/etc/init.d


You only need to run it once. Drod mentioned this at XDA but may not have here. It will increase performance and battery life!


Sent from my DROIDX using Tapatalk

 

[hyperlite]

as i'm very biased, i won't comment on the rom selection

but

i'm on team defuse. i developed the core for fission, so we do have a droid x to work with just wanted to enlighten you a little

I love fission, but you guys (DeFuse) should probably stop asking for donations on the basis that you don't have a droid x to test builds on...

What?!? These people are bringing the cosest thing we have to true ROMS for the DX/D2, and you thinking they should quit asking for donations?

That is illogical.

Sent from my DROIDX using Tapatalk

edit, retracted: OK, i understand how my statement could have been misinterpreted. If you've read the Fission 1.2 thread or been to the Team DeFuse website, you've surely read that they are asking for donations, which is fine and to which i have contributed to, but they are asking partially on the premise that they do not have a physical droid X to test builds on. That had been my understanding, and part of the motivation behind my donation. Then, as i'm sure you saw, Drod comes in and says that they do indeed have a DX, which is what prompted my original comment. Now, he has clarified and stated that, as i understand it, the CURRENT, WORKING DeFuse team does NOT have a Droid X. whew...

BUT, this has all been a massive digression from the topic of the thread, to which i say:

I run Apex. I went Fission 1.1>1.2>Apex. Fission 1.2 absolutely flew, but i can't live without my panoramic pictures and HDMI out. I'm happy with my current Apex setup for speed, flexibility, capability, and reliability. I'm probably going to flash back to fission this weekend and see if i can get some of the blur apk's that fab provided to run.