Who is waiting for the OTA ICS??

[SamuriHL]

You know, that's the first thing I pointed out over at the Droidhive shoutbox when we got our first leak - how lucky we were to be Bionic owners and how good things come to those who wait. Who knows, the thing you speak of may be intentional due to some data they did collect from issues with other devices. Our builds would certainly be less problematic for them simply because we can do what we want without getting stuck. Seems it may be a case of "You know, they're gonna do it whether we condone it or not; why make life more difficult?"

I guess even if someone from Moto spent 5 minutes scouring the forums first thing in the morning while having their coffee, they might be able to drum up enough issues to discuss around the water cooler, and at that point it probably wouldn't hurt to check and see if they are reproduceable or not.

I still find it hard to believe they missed the lapdock issue on the RAZR build, though - you'd think they would have one of those in-house to test with, if for no other reason than because they built the damn thing.

If I were a betting man, and I'm not, I would say the RAZR leak experience maybe influenced the decision for us, as well. I'm willing to give them props for that one even without proof it was intentional.

As for the lapdock issue, I can tell you right now how that happened. The RAZR users were clamoring for an OTA release of ICS, moto promised to deliver in a certain timeframe, they have data on the limited number of lapdock users, and decided to release it knowing it was broken with the idea of pushing out a fix for it within weeks. And they are. It was a calculated move, not an oversight. That's simply my opinion, but, I've been in the game long enough to know that's how these things go.

 

[SamuriHL]

Yeah, I'm one of those types of people that wouldn't even consider calling something an issue until I tried everything in the book to keep it from happening, down to a reflash or a full data wipe. For example, I thought my home button was wacky on .232 until I did a cache/data wipe - and fixed the issue. It is for this reason that I am actually against the concept of patch updates for an entirely new OS. A new OS really NEEDS a proper data/cache wipe. The drawback would be the need to redownload apps, but everything else could theoretically be backed up to the cloud prior to the update.

And that is EXACTLY why I wrote my script so carefully. The chain of events that my script follows, assuming the user follows my freaking directions to a T which we know doesn't always happen, does try to maintain data integrity rather than simply just trying to keep all data. What I mean is I intentionally don't have them boot GB at all during the process and I make sure they do a cache wipe. The Android upgrade script runs on each app they have installed on first boot and those that have run my script successfully didn't report any of the flakey issues that those who restored system data from a TiBU backup without wiping cache afterwards reported. So yes, process counts here. I'm with you 100% on that one.

 

[Dave12308]

Here's an idea I wonder if anyone would be open to? A formal beta-test program by Moto that requires a couple of things. First, an electronically signed document stating that you are fully aware of the risks and dangers of installing unapproved software and will assume all liability for damage to your own device. Second, a short multiple-choice quiz with questions geared toward making sure we know exactly what we are doing when it comes to phones and Android. Something like:

Question 1:
When installing ICS builds in the 6.7.xxx series, the following system version must be present on the device-

a) 5.9.902
b) 5.9.905
c) Any 5.9.xxx build
d) Any 5.7.xxx build

Question 2:
To install ICS builds in the 6.7.xxx series, the device MUST be rooted

a) TRUE
b) FALSE

 

[ekf028]

I'd almost say more of a "we've got bigger fish to fry than worrying about this. But if you fry your device, don't come complaining to us. If VZW kicks you off of their network for running unapproved software (which IS against your TOS), don't come complaining to us"

That sounds good too.
Me...i don't do ANYTHING at all like this to my phone without fully researching it. I know the consequences, if I screw it up...it's my fault. I'll just buy a cheap dumbphone to get me through until the end of my contract lol.

Sent from my DROID BIONIC using Tapatalk 2

 

[Dave12308]

That's simply my opinion, but, I've been in the game long enough to know that's how these things go.

Very true, in all my years working in IT, I have seen many issues arise from a company trying to get a product to market too quickly. It is for this reason alone that I will not upgrade to a new version of Windows on my PC until it has had the first Service Pack installed.

That being said, it wouldn't hurt Moto to have an ICS progress blog or something similar. People wouldn't be clamoring for something quite as much if they knew it didn't work properly.

I find the entire deal with the RAZR funny anyways. All the people crying for ICS, and now you check the RAZR forums and it seems alot of folks don't even like it.

 

[SamuriHL]

Here's an idea I wonder if anyone would be open to? A formal beta-test program by Moto that requires a couple of things. First, an electronically signed document stating that you are fully aware of the risks and dangers of installing unapproved software and will assume all liability for damage to your own device. Second, a short multiple-choice quiz with questions geared toward making sure we know exactly what we are doing when it comes to phones and Android. Something like:

Question 1:
When installing ICS builds in the 6.7.xxx series, the following system version must be present on the device-

a) 5.9.902
b) 5.9.905
c) Any 5.9.xxx build
d) Any 5.7.xxx build

Question 2:
To install ICS builds in the 6.7.xxx series, the device MUST be rooted

a) TRUE
b) FALSE

I love it!

Sent from my Xoom using Tapatalk 2

 

[ekf028]

Here's an idea I wonder if anyone would be open to? A formal beta-test program by Moto that requires a couple of things. First, an electronically signed document stating that you are fully aware of the risks and dangers of installing unapproved software and will assume all liability for damage to your own device. Second, a short multiple-choice quiz with questions geared toward making sure we know exactly what we are doing when it comes to phones and Android. Something like:

Question 1:
When installing ICS builds in the 6.7.xxx series, the following system version must be present on the device-

a) 5.9.902
b) 5.9.905
c) Any 5.9.xxx build
d) Any 5.7.xxx build

Question 2:
To install ICS builds in the 6.7.xxx series, the device MUST be rooted

a) TRUE
b) FALSE

That doesn't sound too bad

Sent from my DROID BIONIC using Tapatalk 2

 

[Dave12308]

That sounds good too.
Me...i don't do ANYTHING at all like this to my phone without fully researching it. I know the consequences, if I screw it up...it's my fault. I'll just buy a cheap dumbphone to get me through until the end of my contract lol.

Sent from my DROID BIONIC using Tapatalk 2

It is so refreshing to hear someone say that. If all people thought like you, Moto MIGHT just be open to a public beta program. There are too many "I screwed it up, so it's Verizon's problem" type folks out there to make such a beta program a realistic thing. I guess the reason I was initially scoffing at the notion of Moto benefitting from these leaks is due to the rampant number of people on the forums who simply do not know what they are doing. Sometimes I have to sit down and realize that with the number of people on this forum, there are actually lots of folks like us that truly do provide useful information.

 

[SamuriHL]

Very true, in all my years working in IT, I have seen many issues arise from a company trying to get a product to market too quickly. It is for this reason alone that I will not upgrade to a new version of Windows on my PC until it has had the first Service Pack installed.

That being said, it wouldn't hurt Moto to have an ICS progress blog or something similar. People wouldn't be clamoring for something quite as much if they knew it didn't work properly.

I find the entire deal with the RAZR funny anyways. All the people crying for ICS, and now you check the RAZR forums and it seems alot of folks don't even like it.

I agree. The razr build seems rushed for sure. I'm sure those waiting for it to go ota didn't think it felt rushed... Until the got it. Now they wait for bug fixes. Which is worse... Getting a rushed buggy build that taints your experience or having to wait longer for am finished experience? I bet we all say rushed with bugs because we like being on the bleeding edge. But the majority of users? Ask the razr people....

Sent from my Xoom using Tapatalk 2

 

[Dave12308]

Just for the record, I also believe that it is our RIGHT to have an unlocked bootloader, with the agreement that it voids the warranty. Those who don't even know what a bootloader is aren't going to voluntarily give up their warranty for something they don't understand, for the rest of us we would be able to easily fix our own device if we screwed it up without relying on luck.

I see no benefit to anyone locking the bootloader, unless Moto is trying to directly compete with RIM. And even if they are, they could simply lock the bootloaders on corporate devices.

 

[SamuriHL]

It is so refreshing to hear someone say that. If all people thought like you, Moto MIGHT just be open to a public beta program. There are too many "I screwed it up, so it's Verizon's problem" type folks out there to make such a beta program a realistic thing. I guess the reason I was initially scoffing at the notion of Moto benefitting from these leaks is due to the rampant number of people on the forums who simply do not know what they are doing. Sometimes I have to sit down and realize that with the number of people on this forum, there are actually lots of folks like us that truly do provide useful information.

I try to fit in this category. Sometimes I jump without knowing all the consequences BUT I accept the responsibility for it. Go read the 34 pages on rootzwiki from December if you want to see that in action. I never once blamed anyone but myself or ever expected anything from vzw during that experience. There are, however, far too many who won't take the same responsibility for what they do and that does ruin it for those who would. That's why I'm going to spend the money on a developer phone... To show support for responsible bootloader unlocking.

Sent from my Xoom using Tapatalk 2

 

[SamuriHL]

Just for the record, I also believe that it is our RIGHT to have an unlocked bootloader, with the agreement that it voids the warranty. Those who don't even know what a bootloader is aren't going to voluntarily give up their warranty for something they don't understand, for the rest of us we would be able to easily fix our own device if we screwed it up without relying on luck.

I see no benefit to anyone locking the bootloader, unless Moto is trying to directly compete with RIM. And even if they are, they could simply lock the bootloaders on corporate devices.

Yup... This is why I'm supporting it with my $$$.

Sent from my Xoom using Tapatalk 2

 

[Dave12308]

I agree. The razr build seems rushed for sure. I'm sure those waiting for it to go ota didn't think it felt rushed... Until the got it. Now they wait for bug fixes. Which is worse... Getting a rushed buggy build that taints your experience or having to wait longer for am finished experience? I bet we all say rushed with bugs because we like being on the bleeding edge. But the majority of users? Ask the razr people....

Sent from my Xoom using Tapatalk 2

Of course, instead of demanding a bugfix patch for ICS, those very same folks are now telling Moto to hurry up and get a Jellybean build going. I honestly don't think many people can comprehend how many lines of code Android is comprised of. Although customers were demanding a rush on things, in the end it tarnished alot of user's views of ICS. I've actually found myself telling people in the RAZR forum to wait for the bugfixed version because going by the experience on my Bionic running .232; it really IS a decent OS.

 

[ekf028]

It is so refreshing to hear someone say that. If all people thought like you, Moto MIGHT just be open to a public beta program. There are too many "I screwed it up, so it's Verizon's problem" type folks out there to make such a beta program a realistic thing. I guess the reason I was initially scoffing at the notion of Moto benefitting from these leaks is due to the rampant number of people on the forums who simply do not know what they are doing. Sometimes I have to sit down and realize that with the number of people on this forum, there are actually lots of folks like us that truly do provide useful information.

Yeah, follow instructions to the T...and you'll be all good!
I remember my very first flash (Rubix) on my DROID X about a month after I got it. Missed the wipe data part and bootlooped. Scared the living hell out of me. After scouring some forums (probably this one) I got it fixed.
With a little research...anything is fixable with Android. The dev community here is second to none.

Sent from my DROID BIONIC using Tapatalk 2

 

[Dave12308]

I try to fit in this category. Sometimes I jump without knowing all the consequences BUT I accept the responsibility for it. Go read the 34 pages on rootzwiki from December if you want to see that in action. I never once blamed anyone but myself or ever expected anything from vzw during that experience. There are, however, far too many who won't take the same responsibility for what they do and that does ruin it for those who would. That's why I'm going to spend the money on a developer phone... To show support for responsible bootloader unlocking.

Sent from my Xoom using Tapatalk 2

Yes, I remember your ordeal. Like I said, the ONLY folks I have an issue with are those who committ blatant warranty fraud. I always say "be prepared to pay, if you are gonna play". People like us are prepared to pay, so we should be able to play - unrestricted.