rubiX Focused 1.9.7, back and better than ever

[wooddale]

Some quick questions. I flashed this rom from the liberty rom. I like it alot more. But I noticed a few things the wallpapers menu is messed up like it was from liberty, it loads but they wallpapers are just all grey.

Also the progress bar and highlights when you select something are yellow the same from liberty should it be yellow or a different color? Because I think some settings came over even though I did a factory reset because a wallpaper form liberty was set on it after I flashed it.

Also I have noticed my battery draining faster. I check the usage and it says phone idle is using about 40% of the battery when before it was pretty much always display was like 70-80% and phone idle was a lot lower. Is something messed up?

Sounds to me like your still on liberty did you bootstrap

 

[munkle]

Some quick questions. I flashed this rom from the liberty rom. I like it alot more. But I noticed a few things the wallpapers menu is messed up like it was from liberty, it loads but they wallpapers are just all grey.

Also the progress bar and highlights when you select something are yellow the same from liberty should it be yellow or a different color? Because I think some settings came over even though I did a factory reset because a wallpaper form liberty was set on it after I flashed it.

Also I have noticed my battery draining faster. I check the usage and it says phone idle is using about 40% of the battery when before it was pretty much always display was like 70-80% and phone idle was a lot lower. Is something messed up?

Sounds to me like your still on liberty did you bootstrap

yeah i did (I went droid x boot strapper, boostrap recovery, reboot recovery, wipe data/factory reset and install zip from sd card, reboot phone). The boot logo is rubix. And when I go to settings>about phone it says the build is rubix 1.9.7

I'm wondering if liberty did something funky because when I was running liberty if my phone was off but I plugged it into a wall charger it would boot into recovery it was really wierd.

 

[dwcasey]

A few nights ago, disconnected from the charger around 10:30pm. Set it on the nightstand beside my bed. Woke up and headed out the door the next day around 7:30 and checked the phone, it said 90%.

Possibly some background apps or desktop widgets doing something while it should be "sleeping" ?

 

[munkle]

So i just tried to use my stock backup to restore to stock and was going to flash rubix from there and I get md5 sum mismatch. That sucks. I copied the back up right on to my pc after I made it so I will put that back on the card. But if that doesn't work what are my options? Not to sure how to do a "sbf"

Just tried the backup I copied to my pc. Same thing md5 mismatch. Sweet...

One thing I have noticed is installing new roms I also get madden and nfs even though I doubt those come with the roms prepackaged?

 

[sephtin]

So i just tried to use my stock backup to restore to stock and was going to flash rubix from there and I get md5 sum mismatch. That sucks. I copied the back up right on to my pc after I made it so I will put that back on the card. But if that doesn't work what are my options? Not to sure how to do a "sbf"

Just tried the backup I copied to my pc. Same thing md5 mismatch. Sweet...

One thing I have noticed is installing new roms I also get madden and nfs even though I doubt those come with the roms prepackaged?

Easiest way back to 2.3.340, is this (make sure you wipe cache/data before installing):
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html

Afterwards, just re-root with z4root, reinstall bootstrap, and reload whatever you want.

NFS is on the /preinstall dir, whick will get installed every time you wipe.. unless you remove it from there (If you do, go ahead and remove it's md5 file as well)...

 

[munkle]

So i just tried to use my stock backup to restore to stock and was going to flash rubix from there and I get md5 sum mismatch. That sucks. I copied the back up right on to my pc after I made it so I will put that back on the card. But if that doesn't work what are my options? Not to sure how to do a "sbf"

Just tried the backup I copied to my pc. Same thing md5 mismatch. Sweet...

One thing I have noticed is installing new roms I also get madden and nfs even though I doubt those come with the roms prepackaged?

Easiest way back to 2.3.340, is this (make sure you wipe cache/data before installing):
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html

Afterwards, just re-root with z4root, reinstall bootstrap, and reload whatever you want.

NFS is on the /preinstall dir, whick will get installed every time you wipe.. unless you remove it from there (If you do, go ahead and remove it's md5 file as well)...

I just did the sbf to .320 so I assume I can use that also to update to .340?

Also if I check for updates it says I am up to date. Wouldn't verizon say I need to update to .340?

 

[sephtin]

So i just tried to use my stock backup to restore to stock and was going to flash rubix from there and I get md5 sum mismatch. That sucks. I copied the back up right on to my pc after I made it so I will put that back on the card. But if that doesn't work what are my options? Not to sure how to do a "sbf"

Just tried the backup I copied to my pc. Same thing md5 mismatch. Sweet...

One thing I have noticed is installing new roms I also get madden and nfs even though I doubt those come with the roms prepackaged?

Easiest way back to 2.3.340, is this (make sure you wipe cache/data before installing):
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html

Afterwards, just re-root with z4root, reinstall bootstrap, and reload whatever you want.

NFS is on the /preinstall dir, whick will get installed every time you wipe.. unless you remove it from there (If you do, go ahead and remove it's md5 file as well)...

I just did the sbf to .320 so I assume I can use that also to update to .340?

Also if I check for updates it says I am up to date. Wouldn't verizon say I need to update to .340?

The verizon update is looking for 2.3.15. So.... no.

 

[munkle]

Ok so I did the .340 update. Made a backup and restored from that backup to make sure it actually worked. Rooted and flashed the rubix rom. What's wierd is this time it had me activate my phone right after I flashed this rom and the .340 update. But when I did the liberty rom it didn't have me activate my phone even though I did a wipe before it. My guess is either the first wipe went skrewy or liberty did something funny.

rubix is on there now and without anything funny from before. But wallpapers menu still doesn't work oh well.

 

[alosenster]

So i just tried to use my stock backup to restore to stock and was going to flash rubix from there and I get md5 sum mismatch. That sucks. I copied the back up right on to my pc after I made it so I will put that back on the card. But if that doesn't work what are my options? Not to sure how to do a "sbf"

Just tried the backup I copied to my pc. Same thing md5 mismatch. Sweet...

One thing I have noticed is installing new roms I also get madden and nfs even though I doubt those come with the roms prepackaged?

Did you by any chance change the name of your backup file? If you put spaces in it or something like that, you'll get that error.

 

[kingczarii]

I searched the thread already, and I came across one unanswered question about lock screen lag. So I will re ask, is this a known issue? If I am either in the rotary lock screen, or the slide lock, there is a noticeable delay between when the slider hits the unlock button, and when the slider continues its animation. I was looking at my buddy's dinc (lol) running cm7 and his rotary lock screen is smooth as butter. Is there anything the devs can do to improve the lock screen performance on the DX? This has been noticeable to me since I was running stock, one of my biggest beefs with the dx overall.

So I too had this problem and found the answer. For me the reason it lagged was because of the haptic feedback for the slide lock is on. The only way that others said to over ride this was to use the widget locker app. So I am using that now and in the app there's a option to remove haptic feedback and it works great.

Not sure if theres a native way to do this in Rubix without that app.

Sent from my DROIDX using DroidForums App

 

[digitalslacker]

Ok so I did the .340 update. Made a backup and restored from that backup to make sure it actually worked. Rooted and flashed the rubix rom. What's wierd is this time it had me activate my phone right after I flashed this rom and the .340 update. But when I did the liberty rom it didn't have me activate my phone even though I did a wipe before it. My guess is either the first wipe went skrewy or liberty did something funny.

rubix is on there now and without anything funny from before. But wallpapers menu still doesn't work oh well.

I have had the activate coming from other roms back to rubiX, because you ALWAYS come back to rubiX.

I remember seeing an explanation about why but I can't remember what it was.

 

[sephtin]

I searched the thread already, and I came across one unanswered question about lock screen lag. So I will re ask, is this a known issue? If I am either in the rotary lock screen, or the slide lock, there is a noticeable delay between when the slider hits the unlock button, and when the slider continues its animation. I was looking at my buddy's dinc (lol) running cm7 and his rotary lock screen is smooth as butter. Is there anything the devs can do to improve the lock screen performance on the DX? This has been noticeable to me since I was running stock, one of my biggest beefs with the dx overall.

So I too had this problem and found the answer. For me the reason it lagged was because of the haptic feedback for the slide lock is on. The only way that others said to over ride this was to use the widget locker app. So I am using that now and in the app there's a option to remove haptic feedback and it works great.

Not sure if theres a native way to do this in Rubix without that app.

Sent from my DROIDX using DroidForums App

Hmm, have not heard of the haptic feedback setting causing lag on slider unlock...

I HAVE heard of SetCPU causing it though... (It seems SetCPU is changing the system speed or something about the same time most people are unlocking.. and you get lag from it)... If you have this issue, and are using SetCPU, try without SetCPU and see if it helps.

 

[keysersoze25]

ok so noob question but how do i make a backup of all my settings when i update from 1.9.5 to 1.9.7? i always have trouble doing this step and i have to manually retrieve all my apps back as well as settings, what my homescreens look like, etc...

 

[IamGod2U]

Market Crash?

Installed rubiX Focused 1.9.7 and LOVE everything about it presently, except for one major problem. Every time I click on Market it immediately force closes. I know there were issues in previous versions, but I can't find mention of it here.

Is there a solution? That's a non-negotiable issue, and I would hate to go back to stock because I love a whole lot about this ROM.

 

[sephtin]

Installed rubiX Focused 1.9.7 and LOVE everything about it presently, except for one major problem. Every time I click on Market it immediately force closes. I know there were issues in previous versions, but I can't find mention of it here.

Is there a solution? That's a non-negotiable issue, and I would hate to go back to stock because I love a whole lot about this ROM.

Market FC's are usually (but not always) caused by restoring from backup (titanium/mybackup).
And usually fixed by wiping cache/data:
Menu> Settings> Applications> Manage Applications> all tab> Market-
Force stop, Clear cache, Clear data, try again.