rubiX Focused 1.9.5

[sephtin]

anyone got pics of what the rom looks like?

I know it doesn't do either version justice, but check http://www.sephtin.com for a few quick snaps.

 

[sephtin]

would anyone be so kind to tell me how to get these updates? I'm currently on .15 and running rubix 1.9

You're going to have better luck checking the DroidX FAQ section, or the Technical help section, or .. maybe the ROMs section.. I know there are plety of people that have guides out, and all kinds of other info on how to update to the OTA (2.3.340) from a custom ROM.

There are a few ways that I know of to get updated to 2.3.340 (OTA). In short:
A) Get back to stock 2.3.15 via nandroid restore, or patch (Think FAB has a return to stock patch ??) so that you can take the OTA.
B) .sbf to get back to stock, then take the OTA
C) ??

Some poeple that tried A had an easy time of it, and others tried all kinds of things, but just ended up .sbfing anyway to get back to 2.3.15 so they could update.
MY suggestion, is to simply go for the .sbf, get back to stock, and OTA.
Guides EVERWHERE on .sbf'ing, my fav. here:
http://www.droidforums.net/forum/dr...e-droid-x-sbf-flashing-guide.html#post1025361

Sorry if I'm bringing this topic up again. I went through 15 pages of comments and feel like this topic has been dropped already.

I had the impression that you do not need to go back to the OTA in order to flash this rom. In the past, I thought drod2169 avoided leaked OTA's because there were no SBF's to fall back on. There's no mention in the original post regarding going back to 320 or 340.

Are you saying that those of us who have been using Rubix from 1.0 (till 1.9) will now have to SBF in order to get this ROM?

Again, sorry if this is being re-addressed. I didn't see this in the original post or in the "before you use 1.9.5 post from a few days ago).

No worries. Let me re-address it a little.

Sorry for the confusion.
You dont' need to go "back" to 2.3.320/2.3.340. BUT you have to have already taken the 2.3.320/2.3.340 updates for this to work.

The 2.3.320/2.3.340 update updates parts of the phone that ROMs can't touch (the baseband/bootloader/kernel).

Once you have updated your kernel (etc.) to 2.3.340, you are fine to install 1.9.5, and any future rev's of this ROM (as well as others.. I believe ALL devs are going to be building ROMs pretty much only for the 2.3.340 kernel.)

The .sbf you refer to, for falling back on, is the 2.3.320 .sbf. The 2.3.320 .sbf can be used for both 2.3.320, and 2.3.340, and then you only need to load the patches from TBH to re-upgrade your kernel/bootloader/baseband (the .sbf will revert those from the 2.3.340 version to the 2.3.320 versions).
BUT, it IS a safe path to get you back to 2.3.340.
Hope that helps clarify.

 

[sephtin]

I rooted my Droid X when I bought it a few months ago. It came with 2.2 on it -- system version 2.3.15. Coming from the original Droid, I absolutely hated (and still hate) the Moto-trocity Motorola added to try to help, but instead ruin, Android, so I settled on rubiX after trying 4 ROMS the first day -- rubiX is by far the cleanest. The version at the time was 1.6 -- I upgraded to 1.9.0 no problems.

The other day, I decided to give Fission a try, as I hadn't tried it before, and I installed it, and reported on the Fission thread that my music wasn't working -- it kept saying "Sorry, the player does not support this type of audio file" no matter what file I tried. We're talking simple MP3 files, CBR or VBR... should have played flawlessly. I got the same trouble when I flashed rubiX 1.9.5, and since I spend a lot of time on campus at my local college, I need my music to work on my phone. I had come directly from rubiX 1.9.0, from the 2.3.15 system version, and I *did* wipe data and cache.

The reason you were having problems, is because you were on the incorrect kernel for that ROM. I'm guessing the version of Fission you were using was the one designed for 2.3.340.. if so, then media will have all sorts of issues (including camera and camcorder)....

As a means of trying to fix the problem, I backed up my rubiX 1.9.5 system and settings nandroid style, and restored to the stock Droid X rom to attempt a system update -- I had a feeling my kernel was causing the issue since I had never updated to 2.3.40. Most of you would know that doesn't work well since the bootstrapper prevents the system update from going through OTA, or even via update.zip... so I eventually found a 2.3.15 SBF, flashed it with RSD Lite 4.8 on Windows, and then ran the OTA without any problems.

That is the appropriate fix.

I couldn't get any of the one-step rooting solutions to work, so I eventually tried this manual rooting method involving typing commands into Terminal Emulator physically on the device after installing Astro and unpacking a zip file on the device, and it was successful. After re-rooting, I installed the bootstrap and restored my rubiX 1.9.5 nandroid backup, booted it up, tried the music and low and behold, it worked.

z4root should work. Some people have reported that sometimes it will fail, and you have to reboot and try again (and sometimes again.. took me 2x reboots).

My theory was that something with the radio or kernel that is NOT backed up / overwritten by a nandroid backup or a new ROM zip flash that changed in the 2.3.40 update disallowed my Fission and rubiX 1.9.5 music files from being able to be played. It may not have been that directly, but when I flashed back to stock with the SBF, updated OTA, re-rooted and went back to my rubiX 1.9.5, everything worked as I expected immediately.

I searched the other day for this issue, and found no help, so I thought I'd post my theory, experiment, and results here... it worked successfully.

Thanks drod for this great ROM. It makes the Droid X bearable -- I'd have returned it the second day I had it without a fully de-blurred ROM.
:motdroidhoriz:

Theory is .. mostly correct.
ROMs, nandroids, etc. do NOT affect the kernel/baseband/bootloader.
.sbf's, and upgrades from Moto/VZW DO.

So, while you were on 2.3.15, you couldn't get media to work on ROMs that were designed to work with the 2.3.340 kernel, and now that you're correctly on the 2.3.340 kernel, all is well, as expected.

You're on the right track. If you do have further issues, throw a post up, and I'm sure someone will help you out!

 

[jgmarz]

How do I delete all contacts

how do I delete all contacts
I have a duplication problem I'd like to delete all my contacts and resync with google. I keep getting google and corporate contacts listed in each contact The only thing I have checked is google contacts.Please help

 

[sephtin]

I also cannot play any music or audio files using any media player, stock and playerpro.... any fixes? Thanks

music and video works fine for me..

you both on the leak .320 or the ota .340?

I went from the stock rom to rubix 1.9. never did the leak update and then just wiped data/cache before installing 1.9.5 and now no audio? when i went into about phone i couldnt see anything about .320 or .340

The key part of your post is "The stock ROM".
Which version of the stock ROM?
You need the leak, or the OTA from VZW (pref. the OTA from VZW 2.3.340)... to get the latest versions of ROMs to function properly.

Once you have the latest kernel/bootloader/baseband, you will have no troubles updating to the latest version of any ROMs... as they're all created to work with 2.3.340.

 

[ashah87]

Is anyone having trouble with notification LED lights? I'm not getting it for my text messages and cant seem to find the option to enable it.

 

[chaoslimits]

I've never used 3g hotspot (I use wifi tether). Does 1.95 use the nvram hack?

 

[ashah87]

Is anyone having trouble with notification LED lights? I'm not getting it for my text messages and cant seem to find the option to enable it.

nevermind...started working lol

 

[sephtin]

I've never used 3g hotspot (I use wifi tether). Does 1.95 use the nvram hack?

No. But the hack should work with it correctly.

 

[motormadness]

One other small issue I noticed on this rom is the compass. I was in google maps and noticed that the phone thought I was facing a direction I definitely wasn't. If anyone knows how to calibrate the compass with this rom, that would be very helpful.

Sent from my DROIDX using DroidForums App

I just tried looking but I couldn't find anything on configuring it. I'll keep looking though.

Sent from my DROIDX using DroidForums App

Grab "Analog Compass" from the market. It has a Calibrate Compass function.

This worked nicely. Thanks for the tip.

Sent from my DROIDX using DroidForums App

 

[avt123]

ROM is working flawlessly for me. Amazing as always!

 

[detox]

Five hours unplugged and still at %90 battery oc'd and uv'd. Nice work drod!

Sent from my DROIDX using DroidForums App

 

[digitalslacker]

Five hours unplugged and still at %90 battery oc'd and uv'd. Nice work drod!

Sent from my DROIDX using DroidForums App

I'm 7 hours and at 80%

 

[DJSketch]

Is anyone having trouble with notification LED lights? I'm not getting it for my text messages and cant seem to find the option to enable it.

Are u able to change the colors?

Sent from DROIDX using Tapatalk Pro

 

[Porterhouse0]

Is anyone having trouble with notification LED lights? I'm not getting it for my text messages and cant seem to find the option to enable it.

Are u able to change the colors?

Sent from DROIDX using Tapatalk Pro

im not getting the LED light up either. and MMS isnt working