rubiX Focused 1.9.5

[OnMy2ndGP]

Ok, today my battery life has been the best I've ever had. Usually with moderate to heavy use I'd be at about 15% to charging already by 5pm. I'm at 50% right now. Close to or more than 100 texts, 2+ hrs of talk time, DF forums, web browsing and of course a good bit of $0.99 NFS Shift! Ok I do have an extend battery too (BH6X) but it and 1.9.5 make a great combo.

rubiX 1.9.5/Gummy Watermark/1.35GHzULV via DF app

 

[dm4222]

Got it running at 1.2 ulv rock solid.

 

[thelionelking]

What app works best to OC and low volt? JRummy, SetCPU, Milestone?

 

[sephtin]

Are you on 2.3.15 or 2.3.320? If .320 then there is a patch to go to .340, otherwise you will have to flash .320 first then patch to .340.

He's on 1.8.6, which was 2.3.15 only. (1.8.6 said 2.3.20, as drod used some components from the R2D2 build that was released (2.3.20)... so he updated build.prop to state that, but the kernel/bootloader is certainly still on 2.3.15.)

Oh yeah, I should have caught that.

All yeah gotta do is sbf to 2.3.320 FULL and then sbf the 2.3.340 patch....reset cache and data in recovery and reboot. Re-root and install Droid X bootstrap, run it and then jump back into recovery and install Rubix

Enjoy.

True....I did the other cause it was less to download for me :icon_eek:

Just a note... If you DO go to 2.3.320, and then "update" to 2.3.340.. it's not ONE patch, but 3-4:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader

From 2.3.320, the only way to update the bootloader/kernel/baseband back to 2.3.340, is via the above linked patches. They are NOT the same between 2.3.320 and 2.3.340. If you are going to load a ROM, then the system patch listed does nothing, because the ROM will simply replace the system folder anyway....

Just wanted to post this for clarification.. because I'd hate for people to .sbf to 2.3.320, and then load the system update from 2.3.320 to 2.3.340, and think they're back on 2.3.340... which is not the case!

 

[sephtin]

Anyone tried Rubix 1.90 Tron Theme w/1.95? if so, Any compatibility issues?

the framework between 1.9.0, and 1.9.5 are completely different. themes are NOT compatible between the two... (SHOULD say that in the first post I believe.. ??

 

[sephtin]

Changed over to this ROM from FlyX and is loving it! I finally have the full Market back.

2 things I noticed:
My contacts is not pulling photos from Facebook even after I messed with a few related settings (am I missing something?)
Alarm Clock Plus is not playing my m4a ringtones I'm using as my alarm sound (which worked fine before the ROM change) But PowerAMP can play those files fine.

Any ideas?

To confirm, from FlyX, did you .sbf back to stock, and update the phone to the latest OTA first? (2.3.340).

If not, you WILL have multimedia issues (playing files, camera, camcorder, etc. etc. etc.).

You can check, by going to Menu> Settings> about phone> and check your kernel version. The version for 2.3.340 is 2.6.32.9-g55626e1.

 

[sephtin]

Out of curiosity:
In the ROM file rubiXFocused1.9.5.zip, there is a file system/framework/framework-res.apk. Under this file, there is a folder red/drawable-hdpi which contains the files stats_sys_battery_0.png thru 100.
Septhin's black bar zip contains the same files in the same location. So, I'm guessing that's the location of the battery status for the bar with percentages?

Here is the question: what would happen if I repacked the framework-res.apk from the rom (or pull it via adb), modified those pictures and slapped a 10, 20, etc (like in Septh's file) respectively and then loaded that file via clockwork?

Would that work to add %'s to the my current battery icon?

Sorry for the long question. I've been reading a link provided by OnMy2ndGP about changing stuff and I was curios -but not brave enough to try it.

it'll work....u change basically any icon in that folder.....jus make sure that u sign tha apk before using it.....

You should zipalign it too.. but since Focused zipalign's .apks every boot anyway.. probably not necessary.

Note, that if you mess up the framework, you will probably boot loop. When playing with framework, be prepared to .sbf!

 

[rkrasny]

I have been loving this ROM until a few minutes ago. I was on 2.3.20 (leaked but not OTA) and did the wipe data/cache prior to installing 1.95. I did not use TiBU for restore.

I went to bootstrap recovery "success" then went to ROM Manager to nandroid a backup. I noticed about 15 minutes later my phone appeared to have just rebooted but I never saw it go into recovery. I went back to ROM manager and tried again and now have an infinite Motorola logo.

The problem is a can't get into the DX recovery mode - it says "bootloader 30.04" then the next line is "Err A5,70,00,00,2F" when I try. There's also an ominous message at the bottom that says "OK to program". I am guessing there might not be an SBF for me and I might need to goto VZW and play it dumb and have them flash the latest but does anyone have any idea if there is any way I can solve this myself?

Thanks in advance.

 

[sephtin]

I have been loving this ROM until a few minutes ago. I was on 2.3.20 (leaked but not OTA) and did the wipe data/cache prior to installing 1.95. I did not use TiBU for restore.

I went to bootstrap recovery "success" then went to ROM Manager to nandroid a backup. I noticed about 15 minutes later my phone appeared to have just rebooted but I never saw it go into recovery. I went back to ROM manager and tried again and now have an infinite Motorola logo.

The problem is a can't get into the DX recovery mode - it says "bootloader 30.04" then the next line is "Err A5,70,00,00,2F" when I try. There's also an ominous message at the bottom that says "OK to program". I am guessing there might not be an SBF for me and I might need to goto VZW and play it dumb and have them flash the latest but does anyone have any idea if there is any way I can solve this myself?

Thanks in advance.

Well, have a couple stupid questions.. so I'm sorry if it's wasting your time.. (but never know! so worth asking!).

The screen you're getting is indicative of holding down 2 of the buttons on the side of the phone (volume up, volume down, camera button (ANY two)), and rebooting.
SO, if you have a case, or were holding the phone tightly, or ... ??? button stuck, or ?? Then THAT could cause this!

To get to android recovery, power it off, and then hold HOME button while powering it up. When you see the android recov. screen (lil droid with ! in a triangle).. then hit the search button to get to the menu, wipe data/cache from there)...

Any luck?

 

[rkrasny]

I have been loving this ROM until a few minutes ago. I was on 2.3.20 (leaked but not OTA) and did the wipe data/cache prior to installing 1.95. I did not use TiBU for restore.

I went to bootstrap recovery "success" then went to ROM Manager to nandroid a backup. I noticed about 15 minutes later my phone appeared to have just rebooted but I never saw it go into recovery. I went back to ROM manager and tried again and now have an infinite Motorola logo.

The problem is a can't get into the DX recovery mode - it says "bootloader 30.04" then the next line is "Err A5,70,00,00,2F" when I try. There's also an ominous message at the bottom that says "OK to program". I am guessing there might not be an SBF for me and I might need to goto VZW and play it dumb and have them flash the latest but does anyone have any idea if there is any way I can solve this myself?

Thanks in advance.

Well, have a couple stupid questions.. so I'm sorry if it's wasting your time.. (but never know! so worth asking!).

The screen you're getting is indicative of holding down 2 of the buttons on the side of the phone (volume up, volume down, camera button (ANY two)), and rebooting.
SO, if you have a case, or were holding the phone tightly, or ... ??? button stuck, or ?? Then THAT could cause this!

To get to android recovery, power it off, and then hold HOME button while powering it up. When you see the android recov. screen (lil droid with ! in a triangle).. then hit the search button to get to the menu, wipe data/cache from there)...

Any luck?

Seph:

As I've learned from reading about a thousand of your posts - no question is too stupid to ask. Sadly, though, the DX is out of its case and I am just performing the basic recovery with the Power/Home and Power release at the M logo.

One step closer to VZW... - as you might say *shrug* or *sigh* or *sh@%*

 

[sephtin]

I have been loving this ROM until a few minutes ago. I was on 2.3.20 (leaked but not OTA) and did the wipe data/cache prior to installing 1.95. I did not use TiBU for restore.

I went to bootstrap recovery "success" then went to ROM Manager to nandroid a backup. I noticed about 15 minutes later my phone appeared to have just rebooted but I never saw it go into recovery. I went back to ROM manager and tried again and now have an infinite Motorola logo.

The problem is a can't get into the DX recovery mode - it says "bootloader 30.04" then the next line is "Err A5,70,00,00,2F" when I try. There's also an ominous message at the bottom that says "OK to program". I am guessing there might not be an SBF for me and I might need to goto VZW and play it dumb and have them flash the latest but does anyone have any idea if there is any way I can solve this myself?

Thanks in advance.

Well, have a couple stupid questions.. so I'm sorry if it's wasting your time.. (but never know! so worth asking!).

The screen you're getting is indicative of holding down 2 of the buttons on the side of the phone (volume up, volume down, camera button (ANY two)), and rebooting.
SO, if you have a case, or were holding the phone tightly, or ... ??? button stuck, or ?? Then THAT could cause this!

To get to android recovery, power it off, and then hold HOME button while powering it up. When you see the android recov. screen (lil droid with ! in a triangle).. then hit the search button to get to the menu, wipe data/cache from there)...

Any luck?

Seph:

As I've learned from reading about a thousand of your posts - no question is too stupid to ask. Sadly, though, the DX is out of its case and I am just performing the basic recovery with the Power/Home and Power release at the M logo.

One step closer to VZW... - as you might say *shrug* or *sigh* or *sh@%*

Ya, just weird that it goes to bootloader screen, but says "OK".. :S Just sounds to me like stuck buttons!

I hate to say this, but short of powering off, and repeatedly hitting the buttons on the side of the phone to *cross fingers* (see, a new one! "unstick them"... hehe..
I'm out of ideas. If it's last resort anyway, you could try .sbf'ing I suppose.. you're on the bootloader screen anyway. (?). But doesn't sound to me like it'll help.. I'd guess that it'll just boot right back to bootloader screen no matter what happens. :S
Worth a shot though ... ?

 

[cpjr]

He's on 1.8.6, which was 2.3.15 only. (1.8.6 said 2.3.20, as drod used some components from the R2D2 build that was released (2.3.20)... so he updated build.prop to state that, but the kernel/bootloader is certainly still on 2.3.15.)

Oh yeah, I should have caught that.

All yeah gotta do is sbf to 2.3.320 FULL and then sbf the 2.3.340 patch....reset cache and data in recovery and reboot. Re-root and install Droid X bootstrap, run it and then jump back into recovery and install Rubix

Enjoy.

True....I did the other cause it was less to download for me :icon_eek:

Just a note... If you DO go to 2.3.320, and then "update" to 2.3.340.. it's not ONE patch, but 3-4:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader

From 2.3.320, the only way to update the bootloader/kernel/baseband back to 2.3.340, is via the above linked patches. They are NOT the same between 2.3.320 and 2.3.340. If you are going to load a ROM, then the system patch listed does nothing, because the ROM will simply replace the system folder anyway....

Just wanted to post this for clarification.. because I'd hate for people to .sbf to 2.3.320, and then load the system update from 2.3.320 to 2.3.340, and think they're back on 2.3.340... which is not the case!

Ahh, my misunderstanding....sorry. So I'm on .320, that's ok cause with Rubix 1.9.5 my phone is running like a beast

 

[dm4222]

What app works best to OC and low volt? JRummy, SetCPU, Milestone?

I'm using droid x overclock by jrummy from the market . Running solid. Rom is crazy fast. Battery life is excellent so far.

 

[dr0id99]

I'd love to see a patch that includes the status bar battery icon and keyboard from themed for the non-themed. If someone could point me in the right direction I would look into packaging it myself into a mod =)


dr0id99

Repackaging the keyboard would be easy, it's just /system/app/latinime.apk (?).
The battery icons would require cracking open the framework-res.apk.

My bar-mod will be based on the stockGB bar, probably remove some of the Green, the battery WILL contain %'s on it, and it'll have a few extras.

Extrating and replacing latinime.apk worked like a charm =)

 

[Johnnysyeah]

Ok, today my battery life has been the best I've ever had. Usually with moderate to heavy use I'd be at about 15% to charging already by 5pm. I'm at 50% right now. Close to or more than 100 texts, 2+ hrs of talk time, DF forums, web browsing and of course a good bit of $0.99 NFS Shift! Ok I do have an extend battery too (BH6X) but it and 1.9.5 make a great combo.

rubiX 1.9.5/Gummy Watermark/1.35GHzULV via DF app

Still not having any luck with my battery..
I let it go to 0% this morning, and charged it while it was off until 100%. Then I turned it on and unplugged my charger.
I'm at 3 hours and it's at 60% already.
Goshhhhh I wonder what is wrong?!