• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] rubiX Focused 1.0 by drod2169

Finally got my X burning some azz....Really loving this ROM so far. Not ONE reboot on this setup so far.

Leaked 2.2
Rubix 1.0 ROM
Jrummy O/C - 1.15ghz ULV
SetCPU- performance

Quadrant attached

Do you happen to have the stage fright mod turned on? It will give a "fake" high quadrant score, if not, good deal.
 
Do you happen to have the stage fright mod turned on? It will give a "fake" high quadrant score, if not, good deal.

Just went into Extras and turned all of Media options under stagefright to "ON". Didn't mess it beforehand. Benched 2162.

Went back switched them to "OFF" and benched 2241.

However, my MFLOPS is running around between 14-16....weird right?

Method:
1. Reboot
2. Open jrummy app: select ULV, then 1.15 (since I pretty much know it turtles above that on any voltage, not set on reboot)
3. Open SetCPU: select performance (I don't know how to use adv settings)
4. Run Quad bench
5. Run Linpack
 
Just went into Extras and turned all of Media options under stagefright to "ON". Didn't mess it beforehand. Benched 2162.

Went back switched them to "OFF" and benched 2241.

However, my MFLOPS is running around between 14-16....weird right?

Method:
1. Reboot
2. Open jrummy app: select ULV, then 1.15 (since I pretty much know it turtles above that on any voltage, not set on reboot)
3. Open SetCPU: select performance (I don't know how to use adv settings)
4. Run Quad bench
5. Run Linpack

Did you check your build.prop file? You need to reboot when you change the stagefright settings, turn them on again, reboot and see if you can get over 3000. That is weird that you're not getting a higher linpack score to go along with the quadrant score.
 
Did you check your build.prop file? You need to reboot when you change the stagefright settings, turn them on again, reboot and see if you can get over 3000. That is weird that you're not getting a higher linpack score to go along with the quadrant score.

I rebooted this time after changing the stagefright, went back to ULV/1.15ghz,
and benched 2379 and MFLOPS 15.99

Do you mean going into the build.prop from root explorer and seeing if the app actually changed the true/false values???

Thanks for looking over my numbers, while the phone is running super smooth and fast, the numbers look screwy.
 
You won't need to go back to an older version before you upgrade.. you can just install.
Unfortunately, there have been significant changes from 0.5 to 1.0. It's a significantly different core/framework. You will need to clear data/cache when you install, or you will boot loop your phone. So be prepared to reinstall your apps, and reconfigure your phone.

(The apps should start re-installing when you open the market for the first time. So I always recommend turning on WiFi after the install, BEFORE you open the market app for the first time... It will probably look like apps are stalled in Market, but they're all queue'd for download, and will eventually all be installed. I also recommend syncing with AppBrain to make sure you get all your apps back. If for some reason some of them don't reinstall.. it's just a matter of reinstalling appbrain app, and syncing to get them back.

HTH!

Thanks for the info. As an additional question, I know that you had mentioned that applying certain themes would cause the phone to become unstable/reinstall some of the removed blur. But do you think that a theme like neXTheme which has been optimized for an AOSP ROM (Apex) would work with this without slowing it down or causing problems?
 
Thanks for the info. As an additional question, I know that you had mentioned that applying certain themes would cause the phone to become unstable/reinstall some of the removed blur. But do you think that a theme like neXTheme which has been optimized for an AOSP ROM (Apex) would work with this without slowing it down or causing problems?

apeX is based on blur (2.3.15 to be exact).. and is not AOSP.
So short answer, no. It will almost certainly cause issues, and it will absolutely put incompatible stuff back. (Framework and services come to mind, as well as other things)...
 
I rebooted this time after changing the stagefright, went back to ULV/1.15ghz,
and benched 2379 and MFLOPS 15.99

Do you mean going into the build.prop from root explorer and seeing if the app actually changed the true/false values???

Thanks for looking over my numbers, while the phone is running super smooth and fast, the numbers look screwy.


run ---> cat /proc/overclock/mpu_opps <---- in terminal to verify the OC is correct. Uninstall quadrant and reinstall and run again

 
Does anyone have an idea why almost all of my pictures (20 random camera pics still remain) could be missing after installing this ROM? also, it won't allow me to install the 3D gallery from the market.
 
run ---> cat /proc/overclock/mpu_opps <---- in terminal to verify the OC is correct. Uninstall quadrant and reinstall and run again


mpu_opps[4] rate=1150000000 opp_id=4 vseld=62
mpu_opps[3] rate=900000000 opp_id=3 vseld= 58
mpu_opps[2] rate=700000000 opp_id=2 vseld=48
mpu_opps[1] rate=400000000 opp_id=1 vseld=33

uninstalled quadrant, reinstalled, benched 2112 after phone/apps being used all day.
Jrummy OC app still set at ULV 1.15
Also played a video right after to make sure the Media was still on.

Thoughts?
 
Does anyone have an idea why almost all of my pictures (20 random camera pics still remain) could be missing after installing this ROM? also, it won't allow me to install the 3D gallery from the market.

I've heard of this happening, but I have no explanation.. I've not been able to recreate, in all of the installs that I've done.

And what happens when you try to install 3dgallery from the market? error? where does it fail?

If it's the market app that seems to be having the issue, I suggest clearing data and cache for it:
Menu> Applications> Manage Applications> all tab> Market-
Force stop, clear data, clear cache.
then restart market app... and try again.
 
mpu_opps[4] rate=1150000000 opp_id=4 vseld=62
mpu_opps[3] rate=900000000 opp_id=3 vseld= 58
mpu_opps[2] rate=700000000 opp_id=2 vseld=48
mpu_opps[1] rate=400000000 opp_id=1 vseld=33

uninstalled quadrant, reinstalled, benched 2112 after phone/apps being used all day.
Jrummy OC app still set at ULV 1.15
Also played a video right after to make sure the Media was still on.

Thoughts?

you sir might just have a ballin phone.

but srs no clue
 
you sir might just have a ballin phone.

but srs no clue

Not sure either about those quad scores.
I just ran a linpack of 16.12, and looked through the recent runs, and it seems to be consistent (~14 for 1ghz; 18-19 for 1.3ghz).

I know I didn't pull those numbers on leaked 2.2.9, so I give ALOT of credit to this ROM. I would encourage anyone to at least try this one out.
Phone is running super smooth, and it loads webpages almost faster than my netbook. Props to the devs!!!!
 
Just installed this last night. I love it, it is so much faster than before and looks great. I installed Launcher Pro over top and I'm loving it.
 
is there a way to get the stock/vanilla sliders (i.e. droid x 2.1/rubix)? I don't want to use a lock replacement either. see pic just in case:

 
is there a way to get the stock/vanilla sliders (i.e. droid x 2.1/rubix)? I don't want to use a lock replacement either. see pic just in case:
...Image removed...
[/URL]

You just need to modify the framework-res file with the images you would like for the sliders... it could be done via a theme, or you could just change it yourself.. *shrug*.

So.. here's my quesiton.. I assume the screenshot is what you have now.. and you want the more solid sliders (I honestly dont' remember what the stock sliders look like. :S

I could probably throw something like that together if you need it.. send me a PM.. (Family in town this weekend, so time is limited, but wouldn't take too long.. *shrug*...
 
Just installed this. Now stuck in boot animation loop. What should I do?

Battery pull.
When you put the battery back in, hold the home button down.
Hold the home button, until you see the M logo.. then let it up. It should take you into the Android Recovery. You'll see a little droid image, along with an ! in a triangle. When you see that, hit the search button on the phone, which will take you into the menu.

From the menu, select to wipe data, and cache, then select reboot.. you should reboot back into Focused! HTH!
 
Next version. ;)

Awesome. Thanks for the great support.

By the way, is there a fix for the UID 1001 sensor issue? On every ROM except Fission 1.2 UID 1001 continues to run (spare parts=>sensor usage) after making a call. Not sure if the effect on battery life was huge, but I went from 25 hrs + easily to about 20 hrs.

In fission, the "dialer" sensor stops after the call ends. Since drod also worked on fission, I'm hoping there's a fix!
 
Installed this a few weeks ago, no I get random half reboots. I'm not OC'd at the moment either. Anyone else?
 
Back
Top Bottom