• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Just accepted Jelly Bean update on my Bionic

Is it being pushed to the masses or is it a soak? I've read it both ways. Also I've read that the build 22 that's going out is tweaked from the test build that is being talked about.
 
I read it was being pushed but mine didn't recieve it , I got the file from XDA and loaded thru stock recovery, and used OTA rootkeeper to keep root
 
If this statement is the most convincing thing you can come up with, I don't see a whole lot of reason to doubt the build.




I said no such thing. But I'm going to choose to accept the decision of the company over some speculative and unconvincing internet comments






really? almost ALL of them? Almost All of the people directly involved with this build release are posting online that the build is a failure? I highly doubt the veracity of this statement. It's pretty hyperbolic.



I don't usually slam a wait and see approach, but idea that this build is a failure seems to be a bit overblown. And your declaration that people should not take it is a bit presumptuous.
I don't wish to get into an argument with you. However, I am extremely curious why you are so antagonistic to a wait and see approach and brush off so many experienced Bionic testers who say it's the best thing to do. I also notice the one part of my comment you willingly chose to ignore was the awful release of ICS for the Razr's.

You say you "choose to accept the decision of the company over some speculative and unconvincing internet comments" yet let's look at the decision's Verizon has made. Look at the awful mess of a build they decided to approve of for ICS for the Razr/Razr Maxx....


Droid RAZR & Droid RAZR MAXX ICS Issues Now Two Months Old

Motorola Droid Razr users still experiencing post-ICS issues | Mobile Bloom News

Now is this speculation that Razr's ICS issues happened? Of course you and anyone else is welcome to install JB now if you wish. I am not trying at all to tell anyone what to do. I do think however it is extremely foolish and quite a bit insulting of you to brush aside many of the most knowledgable Bionic users and testers who have always had insider experience (not me, I merely am listening to Samuri and Thom and others who, for no compensation offer up their expertise and are almost always right) and try to treat it as if it's meaningless. I've seen way to many cases on the forums where people ignore advice given by those in the know, then want to blame someone else when something bad happens.

EDIT: This is what Samuri says on the Android Central forums...
http://forums.androidcentral.com/droid-bionic/217680-droid-bionic-jelly-bean-update-65.html post 1603
No. Had I known how to read the tests better back then I'd have realized that 246 and 247 tested identically. 22 tested badly. I'm told by someone who says they still have access to the test results through another means that 23 tested very well. I have no way of verifying this myself. But I saw the 22 test results. They sucked. Badly.

Now, he goes on later to say something called ISIS may have been pulled from build 22 and maybe that was the root cause of the issue, but this seems to be why there is a need to take a wait and see. Apparently build 23 which tested very well wasn't appoved because it didn't contain much of Verizon's bloatware, and anyone who has had any experience with Verizon can easily believe they would push out a bad build with their bloat rather than a good build without it.
 
Is it being pushed to the masses or is it a soak? I've read it both ways. Also I've read that the build 22 that's going out is tweaked from the test build that is being talked about.
It's being pushed out to the public, not a soak test. But like other releases, it's not going to every location all at once.
 
I don't wish to get into an argument with you. However, I am extremely curious why you are so antagonistic to a wait and see approach and brush off so many experienced Bionic testers who say it's the best thing to do. I also notice the one part of my comment you willingly chose to ignore was the awful release of ICS for the Razr's.

I'm not antagonistic and explained pretty clearly why I had a problem with your statement. And I didn't willingly ignore anything. You're discussing a misstep in the past that has nothing to do with what we are talking about. Most large companies have had major snafu's along the way. Ok verizon botched an ICS release, I get it. That does not really mean anything here other than that a company makes mistakes sometimes. And that is something that I never disputed.




I am not trying at all to tell anyone what to do.

your own words:

" If it's build 22 I would reccomend to anyone who hasn't taken it yet to NOT to take it."



I do think however it is extremely foolish and quite a bit insulting of you to brush aside many of the most knowledgable Bionic users and testers who have always had insider experience (not me, I merely am listening to Samuri and Thom and others who, for no compensation offer up their expertise and are almost always right) and try to treat it as if it's meaningless. I've seen way to many cases on the forums where people ignore advice given by those in the know, then want to blame someone else when something bad happens.

EDIT: This is what Samuri says on the Android Central forums...
DROID BIONIC Jelly Bean Update - Page 65 - Android Forums at AndroidCentral.com post 1603
No. Had I known how to read the tests better back then I'd have realized that 246 and 247 tested identically. 22 tested badly. I'm told by someone who says they still have access to the test results through another means that 23 tested very well. I have no way of verifying this myself. But I saw the 22 test results. They sucked. Badly.

Now, he goes on later to say something called ISIS may have been pulled from build 22 and maybe that was the root cause of the issue, but this seems to be why there is a need to take a wait and see. Apparently build 23 which tested very well wasn't appoved because it didn't contain much of Verizon's bloatware, and anyone who has had any experience with Verizon can easily believe they would push out a bad build with their bloat rather than a good build without it.


straw man after straw man.

I'm not brushing aside anything. You again mention "many of the most knowledgeable user" while quoting the same one guy. I choose to ignore your advice not to install this because you don't have a strong case.
You are not in the know. And you have shown to have few sources other than one person, who again, is not directly involved with this release.
 
I'm not antagonistic and explained pretty clearly why I had a problem with your statement. And I didn't willingly ignore anything. You're discussing a misstep in the past that has nothing to do with what we are talking about. Most large companies have had major snafu's along the way. Ok verizon botched an ICS release, I get it. That does not really mean anything here other than that a company makes mistakes sometimes. And that is something that I never disputed.






your own words:

" If it's build 22 I would reccomend to anyone who hasn't taken it yet to NOT to take it."






straw man after straw man.

I'm not brushing aside anything. You again mention "many of the most knowledgeable user" while quoting the same one guy. I choose to ignore your advice not to install this because you don't have a strong case.
You are not in the know. And you have shown to have few sources other than one person, who again, is not directly involved with this release.

A reccomendation is NOT telling someone what to do, it is simply warning that there may be bad consequences. If you don't know the difference, well, I don't know what to tell you.

But let me point to what YOU said....
"But I'm going to choose to accept the decision of the company"
This is the same company that has a precedent of sending out buggy releases and you seem to be willing to blindly accept what they send out. That's fine. If you or anyone else wants to do so, that is your prerogative and you are free to do so.

Also, I am not making straw man arguments. Build 22 did fail testing. There is some debate on something called ISIS being removed from it which MAY have been the cause of the problems so this update MAY be ok. All the people who have inside knowledge are saying is that the best thing is to see how it goes for people who are willing to test it for the rest of us.

And yes, Samuri is the only one I have quoted directly as he is the creator of HoB and is seen by many as the "face" of Bionic testers. However, if anyone cares to read the links, they will see other knowledable testers making the exact same comments. That fact you say only one source says this rather shows you haven't read any of the links. MANY people are saying the same thing, but Samuri's name is the one most people recognize best.
 
Just wanted to point out what ISIS is. This is Verizon's version of Google wallet.

Verizon Wireless - Explore

I also think you "guys" should agree to disagree and leave it at that. We all make our own decisions based on what we believe is best for us and not everybody has the same wants and needs in their device.
 
I have been reading things at Android Central as they seem to be more up on this release. Has ISIS been removed from the release of 22 or do you know? For some reason there is some thought that this may have been the cause of 22 failing the tests.


ISIS has only been released in austin and salt lake city and I believe for only certain devices.

I am pretty sure that ISIS is not the reason Verizon went with build 22 because it uses NFC (near field communications) which the Bionic is not capable of.
 
ISIS has only been released in austin and salt lake city and I believe for only certain devices.

I am pretty sure that ISIS is not the reason Verizon went with build 22 because it uses NFC (near field communications) which the Bionic is not capable of.

Oh so the test fail of build 22 could have been because the Bionic couldn't handle it since it doesnt have the hardware in it? Cause the talk was that in testing ISIS was in build 22.
 
I was part of the soak test and most every thing went well.Changes are few, but my phone is a lot smoother, and faster.I think I will do a FDR today just to make sure that all is ok.
 
Did the FDR , and the phone is running really sweet. It is a good upgrade however you may wait a while and see what others have to say.I am very happy with it.
 
Mine has finally settled down and looks ready for prime time.


first impressions: Browser is definitely faster. General app and widget speed also appears to have improved. Swype seems fine, but I'll need at least a week to properly evaluate it. Same goes for most everything else in general.

So it looks good for now. My Bionic may get a stay of execution for a while


To follow up: Everything seems pretty good. However, I do think my phone may be eating battery slightly faster than it was before. Not 100% on that and probably need another few days of observation. I looked at my battery app and noticed that screen and WiFi seem to be eating a little more batter than before. This is all highly unscientific, though.

Also, battery life is probably highly subjective depending on what apps each individual user has installed and whatnot.
 
I bought mine maybe a week after release. I still don't have it. I had to wait several days for ICS as well. Not sure why I'm always last. Do they go in reverse order?
 
I bought mine maybe a week after release. I still don't have it. I had to wait several days for ICS as well. Not sure why I'm always last. Do they go in reverse order?
No, but honestly, that may not mean much. Imagine they ship a bunch of the first batch of phones to one place, but they sit around for a while, while the 4th batch of phones gets sent to another and sell right away. Well, some in the 4th batch may have been bought first, but may not get updates till after.

Crude example, but I hope that clears it up.

EDIT: I have had to decline it twice so far cause I still can't find out some information about it and still haven't made up my mind about rooting now so I will have root in the future.
 
Updated a few hours ago. No major problems except for my paid hotspot app, SVTP, rendered useless. UGH.

NEW: Switched to FoxFi - seems to work fine. Hope that SVTP can update for JB users.
 
Is this the easiest way to get back to 905 to get the update? It seems complicated...

http://androidforums.com/bionic-all-things-root/480176-how-flash-5-9-905-gb-6-7-246-ics-rsdlite.html#post3778757
 
You need to get to 6.7.246 to get the update not .905. If you have rooted, deleted apps or any other modding than yes that is the easiest way.
 
I bought mine maybe a week after release. I still don't have it. I had to wait several days for ICS as well. Not sure why I'm always last. Do they go in reverse order?

I could be wrong about this, but I believe that they go in the order of one particular digit in the MEID. It may the last digit. I heard that years ago.

There are 16 hex digits, so to get it out in a week, they do 0s and 1s first, then 2s and 3s, then they may accelerate it.

Again, I may be wrong about that...
 
Back
Top Bottom