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!

rubiX Focused 1.9.5

oh darn. i was really hoping that the usb problem would be fixed in this rom. Has anyone had any problems with the USB MTP driver not installing? I've had this problem ever since 1.8.6...
 
oh darn. i was really hoping that the usb problem would be fixed in this rom. Has anyone had any problems with the USB MTP driver not installing? I've had this problem ever since 1.8.6...

I have never had a USB issue on any of the RubiX ROMs and still don't. Sorry.
 
Try clearing cache/data for the Microbes LWP app:
Menu> settings> Applications> Manage applications> all tab> Microbes LiveWallpaper
Force stop, wipe cache, wipe data.

See if that helps (??).


Edit: Previously in this thread, someone said that they had to reinstall it... instructions in their post (search if you can't find it, but it was in the last 4-5 pages.. I believe).

Bump again. Did a thread search couldn't find anything on reinstalling the microbes lwp. Any answers?

Answer again.
This time with useful info.. (sorry about that.. I got forums mixed up! *sigh*)

See if this info helps a little more.
rubiX Focused 1.9.5

Great! Thanks!
 
If it helps, here is how I installed quick office:
1.- copied /data/rubix/quickoffice.bak
2.- navigated to /system/app/ and mounted folder as rw
3.- pasted quickoffice.bak in /system/app
4.- renamed quickoffice.bak to quickoffice.apk
4.1.- I can't remember if I ran quickoffice.apk first...
5.- after a reboot, quickoffice is working ok.

You have no idea how dumb I feel right now. Thanks Sephtin!

Just assumed that cause I was rooted, that I would not need to su. How wrong I was.


Sounds like it's failing to mount system as RW... which requires root.

Just guessing.. but what happens if you run "su" before running the script?

No no!! That's an easy thing to overlook.. honestly, I don't even know if the scripts work.. (see above.. failed testing) :(

Worst case, most of the stuff is there, just .. ? Worst case, there are patches for most of that stuff.. heh
 
If it helps, here is how I installed quick office:
1.- copied /data/rubix/quickoffice.bak
2.- navigated to /system/app/ and mounted folder as rw
3.- pasted quickoffice.bak in /system/app
4.- renamed quickoffice.bak to quickoffice.apk
4.1.- I can't remember if I ran quickoffice.apk first...
5.- after a reboot, quickoffice is working ok.

I think you want to make sure the permissions are correct if you follow the above.. (??).
 
If it helps, here is how I installed quick office:
1.- copied /data/rubix/quickoffice.bak
2.- navigated to /system/app/ and mounted folder as rw
3.- pasted quickoffice.bak in /system/app
4.- renamed quickoffice.bak to quickoffice.apk
4.1.- I can't remember if I ran quickoffice.apk first...
5.- after a reboot, quickoffice is working ok.

I think you want to make sure the permissions are correct if you follow the above.. (??).

Which of the 9 boxes do we need to check?
 
If it helps, here is how I installed quick office:
1.- copied /data/rubix/quickoffice.bak
2.- navigated to /system/app/ and mounted folder as rw
3.- pasted quickoffice.bak in /system/app
4.- renamed quickoffice.bak to quickoffice.apk
4.1.- I can't remember if I ran quickoffice.apk first...
5.- after a reboot, quickoffice is working ok.

I think you want to make sure the permissions are correct if you follow the above.. (??).

Which of the 9 boxes do we need to check?

User: Read,Write
Group: Read
Other: Read
(Should look exactly like the rest when done: rw-r--r--
 
Thanks for this rom, everything is great, i'm just having one small problem.
The camera and video is functional, however I can't view video taken with the camera in portrait mode, it will only playback in landscape mode. If i record in portrait mode, it will play in landscape mode but the video will be sideways. So in actuality its recording correctly, it's just when held portrait the screen is black for the duration of playback. I read somewhere that you were still working on some HDMI issues, but I wasn't sure if this problem is related to that or not.
Thanks again for your dedication!
 
Question for everyone.

What Rom our you using Themed or non Themed one? Just wanted to see why each of you liked the one that you are running. Both of them are outstanding I am sure of that!!! dancedroiddancedroid
 
I'm starting to see a trend with whatever roms I use.
The battery lasts really long the first time.
But after a full night's charge, it gets drained so fast.
the first time I installed this rom, I had nearly 20 hours.
And now it's been 2 hours and im at 70%.
Maybe my battery is just bad? I haven't done anything to change my phone.
Even the brightness is still the same.

I have had this happen. My solution was to make sure the battery was 100% and then used the reset battery stats in clockwork recovery and then ran the phone till it shut it self off. it recovered the next charge.

This is not specifc to this rom, just had it happen with a number of roms...

I'll give that a try! Thanks!

EDIT: After your phone shut off, did you fully charge it with the phone OFF? Or did you just leave it on as soon as you had enough juice to turn it on and left it charging whilst in usage?
 
Last edited:
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.

Thank you so much for your answer, sephtin. It's really cool that you're holding down the fort for everyone.

I didn't end up using SBF at the end to update my kernel (though I'm sure I could have used the practice). I thought of another tactic that, luckily turned out to be sound. I'll post it here in order to help others in my situation (feel free to move it). The whole purpose of these forums is to help others :)

Anyway...

Anyone who has read any guide to rooting the DX has created a backup from the first moment that they got the new recovery. This was the case with me. That first backup brings you back to the original Motoblur (newly rooted). I performed the system update and (in my froyo case) it updated straight to .340.

I admit, I do not understand the logic behind this, but my updated phone stayed rooted with su still installed.

I rebooted into bootstrap (had to manually turn the phone off - bootstrap wouldn't actually reboot automatically at the press of the button).

Installed the rom (after wiping everything).

Worked like a charm :)

In the words of others in the rom community: This rom is truly "the latest and the greatest" by drod2169. GB stock is fantastic!
 
I am guessing most of the script stuff doesn't work for you folks, too? Adblock gets an error trying to copy hosts to or from sdcard/rubix , when removing some applications like carhome, they have incorrect filenames.

Haven't seen any reports on same issues, but I know its a low priority issue. Any tips on applying hosts file for adblocking other than adfree? Thanks :)

Sent from my DROIDX using DroidForums App

AdFree works fine on mine, and on three others I have setup for guys at work.
 
Is anyone else having trouble adding a Facebook account? I can't do it through Accounts & Sync. I'm using SyncMyPix for contact pictures now, but I'm just wondering if this was a blur dependency that was removed or I had an error with my installation (I fully charged, wiped data/cache/dalvik cache/batt stats...).

Download the Facebook app via the Market. Mine did the same thing. You will also want to set the sync from the app if you want your contacts synced between FB and your phone.
 
Back
Top