[Motorola Atrix 2] sola fide:
I know this thread has gone on long enough and people are upset but I'd like to propose an alternative thought here. (At least for those in the USA and possibly other areas)

There was an ICS Soak test so we know they've been working on it. Clearly Moto had ICS at a stable condition for the A2 in regions without carrier intervention as it is being released in other regions. Does this immediately result that ATT is the culprit?...No.

Does this mean that ATT isn't the culprit?...No. At some point we have enough context clues to connect the points and realize that the information isn't adding up. However, lets think about this on a broader scale. What's below is clearly only my opinion using a timeline of events and the track record of Google and it's desire to maintain positive customer satisfaction.

Moto has been working on ICS for the A2...not sure for how long. Google released it publicly Oct 2011.

Google then acquires Moto (May 22 if I'm correct).

We should assume that Google is implementing some changes over at Moto...there is no way it's being left entirely untouched.

JB source is released in July and by now Google realizes that ICS for the A2 on ATT is very behind and possibly not up to their standards. (whether that's ATT's fault or not)

The push is made to complete ICS, soak test is given the green light to move forward, but in my opinion Google wasn't content with the product that was going to be released.

In markets outside the US, where there isn't carrier blockage and bloatware to implement, the ICS build meets Google's standards and is prepared to be pushed out as promised. Possibly slightly delayed in the hopes that the US version could catch up. (But I would say this is doubtful to just silly for me to assume)

As the ICS development on the US A2 continues, assuming there are roadblocks from ATT, Google realizes that they have 3 options. All three are going to upset their customers but they have to choose 1 of them. (I'll propose my theory in a 2nd post)

Sept 5th - Moto shocks most of the community (at least shocked me) by announcing the promise that most 2011 devices will get JB or users receive a $100 credit when upgrading to another Moto device. (To many: $100 towards a manufacturer you're currently pissed at isn't much...but to some this creates some forgiveness. To an average user who's prob not on XDA this could possibly mean a decent spec Moto phone for free or very low cost at the time of their next upgrade.)

In an effort to improve customer relationships Google is now possibly pushing Moto to, quickly, fix the ICS image to meet its standards and possibly release JB at the same time.

I'm not stating this as truth or that I fully believe this is what's happening. However, sometimes a lack of information can speak more than what's seen at first glance. Again, as I'm looking at the timeline and how things have unfolded I want to believe that Google/Moto is working hard to rebuild it's relationship with its customers. Not further upset them by giving them the run around.

---------- Post added at 08:47 PM ---------- Previous post was at 08:37 PM ----------

While this is correct...it also seems to me that this statement is incorrect. Is it that impossible for Motorola/Google to release an update that would take a two step upgrade process and push the code necessary for ICS and then reboot to follow up with the upgrade to JB? Would an upgrade like this also be walking a thin line of possibly bricking many user's phones? Yes, I believe it would but that doesn't mean it's impossible.

I'm not an expert in Linux, but it seems plausible that an update could achieve an ICS update and then JB update within the same package.

While I'm stating it: I'm also not an expert in Android and its framework so I could be entirely wrong and this could be absolutely impossible. :silly: