rubiX Focused 1.8.9/1.9.3

[sephtin]

First off.. I wanted to say thanks to all the guys providing info on this board, and to septin. Your black bar mod is awesome, and i've now used it on what seems like 10 versions of Rubix.

I have a question about whether or not I should consider switching over to the leaked rom and updated to 1.9.3. I'm currently on 1.8.9 and its running smooth.

I've read the thread about the leaked rom, and the potential issues (i'm not sure if they have a valid SBF for recovery or not yet though), and i'm willing to accept those risks, but I don't understand for sure if those changes on the new leak mean anything after updating to rubiX.

I'm not sure how to put this technically, but my question is basically:

Do any of the benefits of the leaked SBF still exist or function after updating to rubiX 1.9.3?

Or even more simply:

Is a perfectly installed (no install issues) 1.9.3 better than 1.8.9 in any ways?

I know there has been discussion about installing these and the issues, etc... but has anybody done a pro/con ?

Very sorry if I missed something about this...

As said before, the two ROMs are the same. 1.9.3 has framework changes to work on the leak. And that's pretty much it.

Also as said before... and also my personal opinion, is the leak doesn't provide enough of a benefit to give up the .sbf safety net.
Hell, I'm still on the 2.1 bootloader (which is actually really nice and stable. I've had awesome luck with it.

 

[P3Droid]

You're not in the majority...

Doing anything blindly -- without taking the time to thoroughly research and understand what you are doing and what the risks are -- to a $500 piece of equipment is generally ill-advised.

For example: I've been obsessing over the new Team Black Hat leak, and I follow the thread at mydroidworld.com, and as much as it sounds like the majority of people are having good (even great) success with this leak, I'm not about to do something to my phone that doesn't have a full, fool-proof life-preserver in case of SNAFU. I'm happy to wait for the OTA, when I'll do a full SBF and apply the OTA to a non-rooted system. If things go south then, it's Verizon's problem!

(No disrespect intended to TBH or anyone running the leak. It's just a bit too risky for my taste!)

Very well said.
I might add, while I've heard much confidence thrown about.. that the leak IS the version that's coming out from Moto/VZW.... just saying, that if it's not.. there are going to be a lot of people STUCK on that version. the OTA is a patch, it doesn't replace files, it modifies them (mostly, anyway). So, if you're not on the leak, you can't go back, and (POSSIBLY... but we won't know until OTA announced) maybe you can't go forward to OTA either.

Small risk, I know (As I trust TBH, well, I trust P3... and what I've been told...
BUT, it's a risk. *shrug*

Again, same as previously posted.. nothing against TBH or the devs, or those that have installed the leak and are enjoying their goodness.. I'm sure everything will work out...

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

 

[droidxchat]

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

what? then why haven't you posted it so that people who've been bricking their phones don't have to send em in for replacement? or so that people who've been wary to upgrade have the peace of mind to do so because they have a way back available?

 

[sephtin]

Quick question: Can we change the boot animation through root explorer? I thought I read someone having issues on v1.6 just want to see if anyone has done it yet? I'm on the new Leak and v1.9.3

/system/media/bootanimation.zip

I think there's a utility that will change it too.. but I believe that one changes the M boot animation.. I'm much more likely to recommend finding an animation and changing it via the .zip file.

 

[sephtin]

hmm well it seems to be running awesome at the moment. il see if it affects my phone. wasnt 1.8.6 zipaligned also?

Zipaligning is something that is done to .apk's to make them more efficiently read by the system. If you change anything INSIDE the .apk, then it needs to be re-zipaligned.

Easy to do. Grab the android SDK, and run zipalign -v 4 <infile> <outfile> from the tools directory.

But yes, after changing the .apk, it's def. recommended. (drod checked with me, after my early barmods weren't zipaligned).

 

[jdhas]

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

what? then why haven't you posted it so that people who've been bricking their phones don't have to send em in for replacement? or so that people who've been wary to upgrade have the peace of mind to do so because they have a way back available?

It's like I could feel you reaching into my throat and literally yanking the words out of my mouth.

It was sort of gross. I'm not going to lie.

 

[sephtin]

Doing anything blindly -- without taking the time to thoroughly research and understand what you are doing and what the risks are -- to a $500 piece of equipment is generally ill-advised.

For example: I've been obsessing over the new Team Black Hat leak, and I follow the thread at mydroidworld.com, and as much as it sounds like the majority of people are having good (even great) success with this leak, I'm not about to do something to my phone that doesn't have a full, fool-proof life-preserver in case of SNAFU. I'm happy to wait for the OTA, when I'll do a full SBF and apply the OTA to a non-rooted system. If things go south then, it's Verizon's problem!

(No disrespect intended to TBH or anyone running the leak. It's just a bit too risky for my taste!)

Very well said.
I might add, while I've heard much confidence thrown about.. that the leak IS the version that's coming out from Moto/VZW.... just saying, that if it's not.. there are going to be a lot of people STUCK on that version. the OTA is a patch, it doesn't replace files, it modifies them (mostly, anyway). So, if you're not on the leak, you can't go back, and (POSSIBLY... but we won't know until OTA announced) maybe you can't go forward to OTA either.

Small risk, I know (As I trust TBH, well, I trust P3... and what I've been told...
BUT, it's a risk. *shrug*

Again, same as previously posted.. nothing against TBH or the devs, or those that have installed the leak and are enjoying their goodness.. I'm sure everything will work out...

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

As previously said.. Don't TELL me, SHOW me.
P3... You are amazing. And I BELIEVE you... but in the mean time, while you're saying "no one will be stuck".. I'm seeing a TON of people stuck right now. There are tons of people bricking and having phones replaced by VZW DIRECTLY because of a leak you are responsible for releasing...

I have a TON of respect for all you've given and done. As Drod says, you're a genius...
BUT, if you have some "secret" up your sleeve, or some info/? that you're not sharing... I am completely confused?

TLDR; What's in the bag?

 

[sruel3216]

hmm well it seems to be running awesome at the moment. il see if it affects my phone. wasnt 1.8.6 zipaligned also?

Zipaligning is something that is done to .apk's to make them more efficiently read by the system. If you change anything INSIDE the .apk, then it needs to be re-zipaligned.

Easy to do. Grab the android SDK, and run zipalign -v 4 <infile> <outfile> from the tools directory.

But yes, after changing the .apk, it's def. recommended. (drod checked with me, after my early barmods weren't zipaligned).

ok thanks. i haven never used sdk. do i launch the SDK manager app? or do i just plug my phone in and go to the tools folder and then launche zipaling? when i launch zip all that happens is a quick flash on my screen. i really have no idea

 

[sephtin]

hmm well it seems to be running awesome at the moment. il see if it affects my phone. wasnt 1.8.6 zipaligned also?

Zipaligning is something that is done to .apk's to make them more efficiently read by the system. If you change anything INSIDE the .apk, then it needs to be re-zipaligned.

Easy to do. Grab the android SDK, and run zipalign -v 4 <infile> <outfile> from the tools directory.

But yes, after changing the .apk, it's def. recommended. (drod checked with me, after my early barmods weren't zipaligned).

ok thanks. i haven never used sdk. do i launch the SDK manager app? or do i just plug my phone in and go to the tools folder and then launche zipaling? when i launch zip all that happens is a quick flash on my screen. i really have no idea

As drod taught me...
--Copy the framework-res.apk file to the SDK\tools folder
--Rename the framework-res.apk to frameworkres.apk (minus the dash).
--run zipalign -v 4 frameworkres.apk framework-res.apk (It will use frameworkres.apk as the IN file, and framework-res.apk as the outfile.. so it is again correctly named).

The framework-res.apk that is created is then zipaligned, and ready to go.

Edit: Never used the SDK manager app.. just run the above from command line.

 

[sruel3216]

Zipaligning is something that is done to .apk's to make them more efficiently read by the system. If you change anything INSIDE the .apk, then it needs to be re-zipaligned.

Easy to do. Grab the android SDK, and run zipalign -v 4 <infile> <outfile> from the tools directory.

But yes, after changing the .apk, it's def. recommended. (drod checked with me, after my early barmods weren't zipaligned).

ok thanks. i haven never used sdk. do i launch the SDK manager app? or do i just plug my phone in and go to the tools folder and then launche zipaling? when i launch zip all that happens is a quick flash on my screen. i really have no idea

As drod taught me...
--Copy the framework-res.apk file to the SDK\tools folder
--Rename the framework-res.apk to frameworkres.apk (minus the dash).
--run zipalign -v 4 frameworkres.apk framework-res.apk (It will use frameworkres.apk as the IN file, and framework-res.apk as the outfile.. so it is again correctly named).

The framework-res.apk that is created is then zipaligned, and ready to go.

Edit: Never used the SDK manager app.. just run the above from command line.

hmm still a little new and confused to this. il try to figure it out. thanks tho

 

[P3Droid]

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

what? then why haven't you posted it so that people who've been bricking their phones don't have to send em in for replacement? or so that people who've been wary to upgrade have the peace of mind to do so because they have a way back available?

this is not the perfect thread for this discussion so this will be brief.

people bricking their phones is NOT the same as a way back when the OTA rolls out. Those are two mutually exclusive things.

 

[P3Droid]

Very well said.
I might add, while I've heard much confidence thrown about.. that the leak IS the version that's coming out from Moto/VZW.... just saying, that if it's not.. there are going to be a lot of people STUCK on that version. the OTA is a patch, it doesn't replace files, it modifies them (mostly, anyway). So, if you're not on the leak, you can't go back, and (POSSIBLY... but we won't know until OTA announced) maybe you can't go forward to OTA either.

Small risk, I know (As I trust TBH, well, I trust P3... and what I've been told...
BUT, it's a risk. *shrug*

Again, same as previously posted.. nothing against TBH or the devs, or those that have installed the leak and are enjoying their goodness.. I'm sure everything will work out...

NO ONE AND I MEAN, no one who has updated will be stuck when the OTA comes out. before this was released you have to have known we have a way back. I'm just sayin...

As previously said.. Don't TELL me, SHOW me.
P3... You are amazing. And I BELIEVE you... but in the mean time, while you're saying "no one will be stuck".. I'm seeing a TON of people stuck right now. There are tons of people bricking and having phones replaced by VZW DIRECTLY because of a leak you are responsible for releasing...

I have a TON of respect for all you've given and done. As Drod says, you're a genius...
BUT, if you have some "secret" up your sleeve, or some info/? that you're not sharing... I am completely confused?

TLDR; What's in the bag?

Don't bite the hand young man....

But I said anyone who has UPGRADED has a way back...not anyone who has BRICKED we have a way back. Very different scenarios, and they call for different solutions. Be that as it is, we can fix 99% of anything that any of you consumers can do to your phones. That does not mean that you will always get it or see it. Just means with time we can.

Enjoy Rubix..great rom, but remember, don't bite the hand that feeds you.

 

[coolj478]

Anyone know of a theme with a black status bar, transparent curtain, circular battery icon, and percentages (by 10s) in the circle?

I'm using juicman blue theme and it's perfect except missing the percentages.

Sent from my DROIDX using DroidForums App

 

[jdhas]

Gosh, how I love trash talk, bruised egos, and thinly-veiled threats on the internet.

 

[droidxchat]

this is not the perfect thread for this discussion so this will be brief.

people bricking their phones is NOT the same as a way back when the OTA rolls out. Those are two mutually exclusive things.

You're right, bricking is different from rolling back, but that doesn't mean that fixing a brick is done any differently from rolling back from a custom release. SBF flash for instance... I would find it extremely unlikely that this "way back" of yours, which is conveniently left secret for no apparent reasons at all, is any different in that characteristic.

Enjoy Rubix..great rom, but remember, don't bite the hand that feeds you.

P3Droid... I also love the stuff you release, but I dont understand why you think you can just come to the thread and give us a warning or a threat, when we're only asking you to divulge a fix for a problem that you (albeit unintentionally) played a hand in causing. You were kind enough to release this leak, and were responsible enough to tell everyone to use it at their own risk, but if you have a way to roll back, which is a direct pair to something you've already released, it is largely irresponsible of you to keep it to yourself. At least say why you can't release it, because right now it looks like you're just full of it...

You're good at this stuff P3Droid.. that's a given. But when I volunteer at my local soup kitchen, I don't threaten the people who I'm feeding just cuz they ask for more, nor do I presume to be any better than they are...