Should we wait to install Jelly Bean

[wildkitten]

With word being that Verizon intends to push out build 22 of JB, which reportedly has a huge failure rate, rather than build 23 which reportedly has been very stable, should we wait on the upgrade?

And what possible reason would Verizon have for releasing build 22 rather than 23? Because if this is indeed true, I would think Google and Motorola would need to seriously complain to Verizon as they will likely get the blame, not Verizon.

 

[Thom]

I have no direct insight into what is happening with JB. I do recall that EXACTLY the same condition occurred in the past releases where there was a "much better" release that did not get pushed because of a decision from Verizon.

My recommendation is to wait and see what others encounter ...
- Will you be able to revert from JB after it is installed?
- If you are root-ed will it retain root?
- If you are not root-ed is there a path that will allow you to root after upgrading to JB?

Get those answers from the Bionic JB users and not the JB users on other devices ... things evolve.

I think you should plan on doing a Factory Data Reset after upgrading to JB. Are you prepared to do that?

... Thom

 

[wildkitten]

I have no direct insight into what is happening with JB. I do recall that EXACTLY the same condition occurred in the past releases where there was a "much better" release that did not get pushed because of a decision from Verizon.

My recommendation is to wait and see what others encounter ...
- Will you be able to revert from JB after it is installed?
- If you are root-ed will it retain root?
- If you are not root-ed is there a path that will allow you to root after upgrading to JB?

Get those answers from the Bionic JB users and not the JB users on other devices ... things evolve.

I think you should plan on doing a Factory Data Reset after upgrading to JB. Are you prepared to do that?

... Thom

Well, if this JB is bad, word needs to get out that Verizon released and earlier, buggy version and not a recent stable build.

Verizon seems intent on making sure their customers have a bad experience these past couple of years.

 

[OutOfPhase]

my feeling is I think I will wait. From what I read you can go to jelly bean maintain your root but if you need to FXZ to fix something you lose root and as of now there is no exploit that will work. DJ bliss is in retirement and he's the guy that has gained root access for most of the Motorola devices.

 

[Thom]

Well, if this JB is bad, word needs to get out that Verizon released and earlier, buggy version and not a recent stable build.

Verizon seems intent on making sure their customers have a bad experience these past couple of years.

I'm sorry but I do not agree.

In any upgrade I think you should be cautious and let others find the problems if you don't want to participate in that process.

There has been an ongoing he-said/he-said between Motor la and Verizon that has gone on for years. Believe whatever you want.

For this upgrade stuff ... ICS (that we waited extra long for) fixed just about every problem we were plaques with. In my opinion that one was fantastic.

Root-ing and the ability to recover and the ability to revert are in my opinion the issues. We will know the REAL answers to those after JB for the Bionic is released and Bionic users have played with it for a while.

... Thom

 

[wildkitten]

I'm sorry but I do not agree.

In any upgrade I think you should be cautious and let others find the problems if you don't want to participate in that process.

There has been an ongoing he-said/he-said between Motor la and Verizon that has gone on for years. Believe whatever you want.

For this upgrade stuff ... ICS (that we waited extra long for) fixed just about every problem we were plaques with. In my opinion that one was fantastic.

Root-ing and the ability to recover and the ability to revert are in my opinion the issues. We will know the REAL answers to those after JB for the Bionic is released and Bionic users have played with it for a while.

... Thom

Oh I fully intend to take a wait and see approach, but are you saying that this build 23 may not exist? I have read a few of the other sites and seems quite a number of knowledgable people seem to have knowledge of it as well as having knowledge that build 22, which is what is supposedly being pushed to us, had as high as an 80% failure rate in testing. I know this is all heresay, but seems to be from the usual reputable sources.

I know when we were pushed ICS, we got build 246 even though days before 246 was pushed to soak 247 had come out, but 246 had always been given stable reviews from those who had installed it.

 

[Thom]

TWT (Time Will Tell) ... it is all conjecture until Bionic users start using it ... whatever the version is.

... Thom

 

[johnlgalt]

My advice - wait. Seriously.

If you can get a hold of a build 23 then HoBble your phone with that, else wait.

 

[wildkitten]

My advice - wait. Seriously.

If you can get a hold of a build 23 then HoBble your phone with that, else wait.

I'm actually surprised we haven't seen builds here like we did with ICS. I remember someone even had 247 available a few days before ICS went to soak. Do you or anyone else know where to get these builds?

 

[Maddog241]

I'm actually surprised we haven't seen builds here like we did with ICS. I remember someone even had 247 available a few days before ICS went to soak. Do you or anyone else know where to get these builds?

Back in the GB days, there was a process known as Cheesecake which would actually allow a user to browse the Motorola servers where updates were posted for internal testing and Carrier testing.

ICS killed the access and the security of the servers was updated rendering the ability to "surf" them useless. I believe many of the early leaks were pulled and posted this way.

 

[wildkitten]

Back in the GB days, there was a process known as Cheesecake which would actually allow a user to browse the Motorola servers where updates were posted for internal testing and Carrier testing.

ICS killed the access and the security of the servers was updated rendering the ability to "surf" them useless. I believe many of the early leaks were pulled and posted this way.

I hate hearing that. I would really like to be able to use this Build 23 if this Build 22 does turn out to be as what happened in testing.

Who knows, maybe some work was done on Build 22 to fix the problems, but I have never heard of work being done on software and the same version number be kept.

 

[Maddog241]

I hate hearing that. I would really like to be able to use this Build 23 if this Build 22 does turn out to be as what happened in testing.

Who knows, maybe some work was done on Build 22 to fix the problems, but I have never heard of work being done on software and the same version number be kept.

From everything I have read so far on various sites, the released build has favorable reviews. I updated the wife's bionic last night and it seems very good initially.

I don't believe they modify a build and keep the same number... Everything I have read from people who know far more than I says if anything is changed, the build gets a new number.

 

[OutOfPhase]

The way moto is set up is if they do anything to the build the build number changes.

 

[Thom]

I updated the wife's bionic last night and it seems very good initially.

Where did you get the update? Was it released or did you get a copy by some other means?

... Thom

 

[Maddog241]

Where did you get the update? Was it released or did you get a copy by some other means?

... Thom

It was leaked out in the wild. I discovered it yesterday morning and grabbed a copy immediately. I'm not sure if it is still there. Once I verified its validity through sources I trust, I loaded it onto wife's Bionic last night. So far it has been good.

 

[wildkitten]

The way moto is set up is if they do anything to the build the build number changes.

Yes, that's the way I understood it to be. The thing is, from how Samuri and others talked over at Android Central, Build 22 had ISIS in it for testing. Well, since that's Verizon's version of something like Google Wallet and the Bionic doesn't have NFC, I can see where that could be the reason for build 22 failing the test. There's been talk that build 22 that's been released doesn't have ISIS, but at the same time, that would be a change to the build, so I've been trying to get some more information on that.

 

[Thom]

It was leaked out in the wild. I discovered it yesterday morning and grabbed a copy immediately. I'm not sure if it is still there. Once I verified its validity through sources I trust, I loaded it onto wife's Bionic last night. So far it has been good.

So ... you installed an unofficial version of the system that may or may not be pushed out to all Bionic owners.

If someone is looking for some guarantees about the future I would recommend waiting until whatever is released is actually released.

... Thom

 

[wildkitten]

So ... you installed an unofficial version of the system that may or may not be pushed out to all Bionic owners.

If someone is looking for some guarantees about the future I would recommend waiting until whatever is released is actually released.

... Thom

Samuri over on Android Central I believe has the official build 22 on his site. Verizon did start rolling it out yesterday.

The big thing with it is at first the only way to keep root was to use Voodoo. Samuri thinks they may have found some Atrix method of rooting under JB but he says it's very complicated and require Linux to do it, not Windows.

So if anyone has any interest in keeping root or ever being able to root, they certainly do need to wait and make sure they take the steps neccessary before upgrading to JB or they may never be able to.

 

[Thom]

My point was slightly different. If you get it directly from Motorola or Verizon and there is a problem then you are justified in assuming that they will need to correct it. If you get it from a third party then you should assume that, like root-ing, you are assuming responsibility for what happens.

People where all really hyped to get ICS and the reason was simple ... GB was buggy and did not use much of the hardware and ICS fixed both. What is it that JB has that you can't wait another day, week, or month for?

... Thom

 

[wildkitten]

My point was slightly different. If you get it directly from Motorola or Verizon and there is a problem then you are justified in assuming that they will need to correct it. If you get it from a third party then you should assume that, like root-ing, you are assuming responsibility for what happens.

People where all really hyped to get ICS and the reason was simple ... GB was buggy and did not use much of the hardware and ICS fixed both. What is it that JB has that you can't wait another day, week, or month for?

... Thom

Oh I completely agree with you, I think waiting is very smart, even if just for the root portion. I think too waiting is the smart thing to do to see if ISIS has been removed. As OutOfPhase said, Moto has never made a change to a build without changing the build number (that we know of) but there seems to be some belief that this JB release of 22 is identical to the build 23 where ISIS was removed from the test build 22. Since 22 failed testing so badly, I myself want to be sure it's gone before doing the upgrade.

 

[dautley]

So if anyone has any interest in keeping root or ever being able to root, they certainly do need to wait and make sure they take the steps neccessary before upgrading to JB or they may never be able to.

Voodoo OTA RootKeeper works fine, if I can do it anyone can!

 

[Maddog241]

So ... you installed an unofficial version of the system that may or may not be pushed out to all Bionic owners.

If someone is looking for some guarantees about the future I would recommend waiting until whatever is released is actually released.

... Thom

I answered your question about where the update was found. I did not and do not seek guarantees or your or anyone's approval. I am fully aware of the risks associated with my actions and I do not take them lightly. I have sources that have gained my trust over time. I have not asked for guarantees nor have I offered any. I merely try to share information that I have knowledge of and believe to be valid.

 

[Thom]

Sorry for the confusion.

I was not trying to imply that you were expecting anything. My comment was to the community reading this thread. What is being discussed is some some software that is in test.

You understand the implications of what is happening. Not everyone reading it here does.

... Thom

 

[wildkitten]

Sorry for the confusion.

I was not trying to imply that you were expecting anything. My comment was to the community reading this thread. What is being discussed is some some software that is in test.

You understand the implications of what is happening. Not everyone reading it here does.

... Thom

What software in test? Do you mean the JB? That's not being tested, it has been released. Several on other sites have said they have gotten it OTA. Verizon even said it would start getting pushed out to people as of yesterday.

 

[global2]

Accepted the 22 update early this morning. Some new likable features like having my email accounts separated with different notification icons and I like the bedside dock. BUT - my hotspot SVTP paid app will not work. I get a "device not supported" error message. Hopefully, app developer can help or one of the forum readers might have a workaround?
I did not do a factory reset.