rubiX Focused 1.6

[johnny9374]

this thing ran great for a few days then nothing but freezes and reboots

Anything done/changed in the last couple days? Decided to try changing LCD Density, or oveclocking/undervolting, or ??

nope i mean those few days it ran great no problems at all i cant think of anything that i changed to cause that to happen

 

[kameleongt]

this thing ran great for a few days then nothing but freezes and reboots

Anything done/changed in the last couple days? Decided to try changing LCD Density, or oveclocking/undervolting, or ??

I was running UV prior to getting phone ready but for the most part its been able to install each time and its just gets stuck at the bootscreen loop.

 

[kameleongt]

i'm also now running from rom manager verizon droid x 2.2, stock stable, rooted. would it be safe to go from this to rubix 1.6? should I deodex first?

 

[sephtin]

i'm also now running from rom manager verizon droid x 2.2, stock stable, rooted. would it be safe to go from this to rubix 1.6? should I deodex first?

You won't need to. The install will format /system (deodexing would just change some of the files on /system, which would be wiped out anyway).

You should be set!

 

[sephtin]

this thing ran great for a few days then nothing but freezes and reboots

Anything done/changed in the last couple days? Decided to try changing LCD Density, or oveclocking/undervolting, or ??

I was running UV prior to getting phone ready but for the most part its been able to install each time and its just gets stuck at the bootscreen loop.

and you did wipe data and cache, right?

From the boot loop, if you go into android stock recovery (hold home while phone is booting, and then press search button to get to menu), wiping data and cache there help? or ?

 

[kameleongt]

thanks i'll post up if i get stuck again, you guys helped out tons never had this kind of help on a forum.


THANKS AGAIN.

 

[kameleongt]

Anything done/changed in the last couple days? Decided to try changing LCD Density, or oveclocking/undervolting, or ??

I was running UV prior to getting phone ready but for the most part its been able to install each time and its just gets stuck at the bootscreen loop.

and you did wipe data and cache, right?

From the boot loop, if you go into android stock recovery (hold home while phone is booting, and then press search button to get to menu), wiping data and cache there help? or ?

I'm just now about to install 1.6 did clear data/cache usually i would get stuck at the rubix bootscree, i'll leave it on that for a 5 min or so if it doesn't go past. your saying I should go into stock recovery and clear data/cache. then resboot?

 

[kameleongt]

i'm on the M logo for about 3min now didnt' get into rubix bootscreen yet.

originally when I first tried the rubix install yes i did clear data/cache, on 2nd try i didn't and this time I did and i'm on the M logo.

 

[sephtin]

i'm on the M logo for about 3min now didnt' get into rubix bootscreen yet.

originally when I first tried the rubix install yes i did clear data/cache, on 2nd try i didn't and this time I did and i'm on the M logo.

Weird, do goign into the android boot menu (hold home while booting, hit search when at the triangle + "!" logo), and clearing data/cache fix?

 

[jloya]

thank you for the clarification Sephtin

No worries, and I can understand the confusion.. I just don't want something like that to start driving people to OTA'ing unnecessarily... There haven't been any known benefits (or otherwise) to going one way or the other, and this ROM is no exception.. *shrug*

You've been a great help on the boards, and your feedback is appreciated by many, I don't mean to take away... I just wanted to clear that particular issue up.

Sorry if my tone sounded harsh at all, or anything. :S

ohh I didnt take the reply in a harsh that way at all, I was happy to see the post correcting my reply. Thanks again for all the help

 

[kameleongt]

i'm on the M logo for about 3min now didnt' get into rubix bootscreen yet.

originally when I first tried the rubix install yes i did clear data/cache, on 2nd try i didn't and this time I did and i'm on the M logo.

Weird, do goign into the android boot menu (hold home while booting, hit search when at the triangle + "!" logo), and clearing data/cache fix?

nope it ended up staying on the boot screen i'm going to try flashing 1.0 rubix of rom manager see how that goes.. seems like something is def. up. 4 times now not being able to boot into rubix 1.6 maybe something went wrong when i downloaded 1.6 so i'll redownload also the reboot clear from android boot menu i didn't get to try since It froze up at the m logo this time and stay there.

 

[Drae123]

Is the phone idle stat on the battery manager bugged like the cell standby stat? I really like this rom, doing whatever I can to track down the source of this small battery drain. I get through the day fine, but I dont know how a blurred SSX rom is giving me noticeable better battery life. Just tried a fresh install from a SBF and had the same issue still. I have the OTA version of 2.2, so maybe thats what it is. Performance wise they both feel the same, i just hate the bloat and would like to use rubix if I can nail this down.

 

[cpjr]

Well been running medium voltage @ 1.45ghz....

Decided to try ULV @ 1.0ghz today, phone still runs fast and after 8.5 hours off the charger...fairly light use, just a few phone calls and txts...but Im still @ 90% battery left

 

[johnny9374]

Anything done/changed in the last couple days? Decided to try changing LCD Density, or oveclocking/undervolting, or ??

I was running UV prior to getting phone ready but for the most part its been able to install each time and its just gets stuck at the bootscreen loop.

and you did wipe data and cache, right?

From the boot loop, if you go into android stock recovery (hold home while phone is booting, and then press search button to get to menu), wiping data and cache there help? or ?

yes i did the wipe data/cache even reinstalled it started locking up on me right away so i went back to apex

 

[jloya]

correct me if im wrong but isnt this ROM undervolted? Which means the ROM could not play nice with certain phones?

this MAY be the case for johnny9374