I would too. Consedering we got GB not to long ago, we might not see it until mid late 2012, but who knows maybe the google motorola merger thing might speed things up.
I would too. Consedering we got GB not to long ago, we might not see it until mid late 2012, but who knows maybe the google motorola merger thing might speed things up.
Some of us are still waiting for Gingerbread, dammit...
I'm looking forward to ICS, but I'm enjoying Gingerbread right now. I'm not in a massive hurry to upgrade. Everything is stable and buttery smooth on my Atrix right now.
Ditto...
And, I honestly won't be upset if there is never an ICS for the ATRIX. I would rather wait until the OS has been out a while, kinks worked out of it, and get a new phone built to run it. It will usually be a much nicer experience than reverse coding ICS down to a phone released 2 builds back.
Think of it like computers.... Take a nice computer built, designed and optimized for Windows XP. Sure, that computer will probably run Windows 7 no problem. But, what about Windows 8? Maybe you can get it running on there, maybe it runs great, maybe it runs like crap, maybe not at all.
So, no, I'm in no hurry to get a rushed ICS build for our Atrix phones. I'd rather stick with what works until time to upgrade my phone.
Myself, I DEPEND on my phone, so I don't fool with custom ROM's. So, if Moto does not release an official build, my phone may never see ICS (unless I get a new phone and this one get's to become my "Test Subject" - ***Insert evil laugh here***).
Last edited by WolfmanRobby; October 24th, 2011 at 10:10 AM.
Reason: Fixed Funky Font Formatting!
Exactly, I am still waiting for my OTA Gingerbread. Seriously bummed about this, may not buy another Motorola phone again!
This is a silly thing to say. First off, correct me if I'm wrong but hasn't motorola supplied a way to upgrade to gingerbread through a placing one of their official downloads onto your sdcard? Anyway...where are you going to go, Samsung? I had the samsung galaxy s captivate, and if you want to see an example of a truly ludicrous amount of wait time between upgrades, look at the galaxy s line. If you truly want quick upgrades, the only thing you can do is get a google nexus phone.
Traditionally, motorola and htc have been faster than samsung to upgrade firmware, but there's no telling yet on whether samsung has straightened up their act. We'll find out depending on how fast the motorola razr and samsung galaxy s 2 get their upgrades. I doubt the atrix and other phones that came out Q1 and Q2 this year will see ics until late Q1 next year.
Device(s): Motorola Backflip; Motorola Atrix 4G and Lapdock
Carrier: Not Provided
Thanks: 37
Thanked 185 Times in 173 Posts
Also, the Atrix 4G has had three updates this year alone. I that's pretty good for a cellphone. Remember that these cellphones are coming out so fast now and the manufactures are trying to make money. (To get you to upgrade your phone.)
This is a silly thing to say. First off, correct me if I'm wrong but hasn't motorola supplied a way to upgrade to gingerbread through a placing one of their official downloads onto your sdcard?
I think the SD card builds are limited by carrier. And, that's where the real hold up is, more than it's Motorola's fault.
They have to put out a version for each carrier. Those of us on AT&T got ours. Those on other carriers have not. It's not that Motorola has not built GB for the phones. Those carriers have yet to test that build on their network, and have not provided all of their branding into the build for Moto to release.
It's no Moto's fault. It's the carrier that's the hold up.
The nice thing with BB was that we could download builds from other carriers, delete a vendor.xml file, and load it on our AT&T phones with no problems.
Those of us in Europe are getting the shaft royally. Still no GB update, let alone anything else. Thus the idea of not buying Motorola products again is a good one. Other manufacturers at least update worldwide, they are not US centric as it appears Motorola are...
Those of us in Europe are getting the shaft royally. Still no GB update, let alone anything else. Thus the idea of not buying Motorola products again is a good one. Other manufacturers at least update worldwide, they are not US centric as it appears Motorola are...
Did you not even read my post just before yours??
It's not Motorola's fault. They can't put out the build for your carrier until the carrier approves it.
Don't blame Motorola. They have GB for the Atrix ready and deployed to carriers that have tested and approved it.
Blame your CARRIER. They are the road block. Example" If you are on Orange UK and they have not released GB for your phone (I'm not sure if they have or haven't - I'm just pulling them as an example. Orange and Vodaphone UK are the only 2 carriers over there I know by name), it's because Orange UK has not told Motorola it's OK. Maybe Orange has not fully tested the phone running GB on their network. Maybe Orange has not finished giving them the tweaks (Customization) that they want in the build for their customers. OR, Maybe Orange does not want you you have GB on the phone to make you want to upgrade to a new phone.
Did you not even read my post just before yours??
It's not Motorola's fault. They can't put out the build for your carrier until the carrier approves it.
Don't blame Motorola. They have GB for the Atrix ready and deployed to carriers that have tested and approved it.
<snip>
But, It's NOT Motorola's fault!
Although I appreciate what you're saying about the delays from carriers is true, the GB delay in the UK is actually down to Motorola - they have still not released the GB update to retail (ie non-carrier supplied) Atrixes over here. Current speculative date is mid-November for retail updates (according to the latest posts on the Motorola support forum and electricpig
On the back of Motorola's original promise (via an electricpig interview) of simultaneous updates for USA & UK customers, this is a pretty poor show; it could have been mitigated a lot if they had actually come forward with what I'm sure are valid reasons for the delay. But instead they went down the route of keeping their customers in the dark
Although I appreciate what you're saying about the delays from carriers is true, the GB delay in the UK is actually down to Motorola - they have still not released the GB update to retail (ie non-carrier supplied) Atrixes over here. Current speculative date is mid-November for retail updates (according to the latest posts on the Motorola support forum and electricpig
That eletricpig article makes a very wrong assumption that the problem is with updating MotoBlur... that has nothing to do with it. Motoblur is the same for both systems. If the problem was updating Motoblur, it would have delayed even the US builds.
I'll take an even more LOGICAL (and educated) guess and say that the delay has been from the carrier testing of the radio/network on this build. Even the UNLOCKED phones have to be performance/compatibilty tested on the carriers networks. Or would you rather they push out an untested update that may or may not work properly???
It's the carrier branded builds that I really don't know if radio/network testing is the ONLY holdup. Usually, after they do that testing, they have to have all of their "tweaks" added to the build.
EDIT - for clarification of how the process works for those that don't understand.
1) The OEM (in this case Motorola) gives the carriers a GENERIC build of the OS for testing on their network. They work with the carriers trying to get any "Bugs" out related to the functionality of the build.
2) Once carriers are satisfied with the build, it splits into 2 paths. Path one, the OEM releases that "Generic" build for the unlocked phones. Path two is that the carriers start "Customizing" the build for their use.
3) Once the carriers have finished butchering the build (Adding their logos, boot animations, custom bloatware apps...), then the OEM releases that build for the users on that carrier.
Last edited by WolfmanRobby; October 26th, 2011 at 08:20 AM.
That eletricpig article makes a very wrong assumption that the problem is with updating MotoBlur... that has nothing to do with it. Motoblur is the same for both systems. If the problem was updating Motoblur, it would have delayed even the US builds.
I'll take an even more LOGICAL (and educated) guess and say that the delay has been from the carrier testing of the radio/network on this build. Even the UNLOCKED phones have to be performance/compatibilty tested on the carriers networks. Or would you rather they push out an untested update that may or may not work properly???
It's the carrier branded builds that I really don't know if radio/network testing is the ONLY holdup. Usually, after they do that testing, they have to have all of their "tweaks" added to the build.
EDIT - for clarification of how the process works for those that don't understand.
1) The OEM (in this case Motorola) gives the carriers a GENERIC build of the OS for testing on their network. They work with the carriers trying to get any "Bugs" out related to the functionality of the build.
2) Once carriers are satisfied with the build, it splits into 2 paths. Path one, the OEM releases that "Generic" build for the unlocked phones. Path two is that the carriers start "Customizing" the build for their use.
3) Once the carriers have finished butchering the build (Adding their logos, boot animations, custom bloatware apps...), then the OEM releases that build for the users on that carrier.
I don't recall ever suggesting that I would like an untested build, nor do I think I am being illogical in holding Motorola responsible.
Motorola employees made the original suggestion of a simultaneous release, and have chosen to keep quiet about changes in timescales / reasons for delay.
From an end user perspective Motorola have let us down by:
- offering something that they cannot guarantee (because they are not fully responsible for delivery)
- failing to communicate with their customers.
As such I consider them responsible for the delays, because they have made no real attempt to clarify matters to some 88 pages of disgruntled customers in their own support forums. When I and my team delay a software release, we provide clear reasons why (if we didn't then we would expect to lose customers) and we take responsibility where we are working with third parties to supply a feature.
Personally I'm pretty happy with my Atrix apart from a few specific issues that Gingerbread is rumored to mitigate / resolve. I purchased it based on what it could do with Froyo, rather than what *might* be introduced in the future.
However when I compare their poor communication regarding updates against Asus, who have been extremely communicative regarding updates, fixes and ICS for the Transformer series, I am unlikely to choose Motorola for my next phone.
*EDIT*
Where can I get that cake from ? O_O
Last edited by CodeMonkey; October 26th, 2011 at 09:58 AM.
Reason: I want Cake!
Think about this... Asus does not have to deal with carriers and carrier contracts that limit what they can say publicly about the releases.
In other words, Asus does not have a contractual "Non-disclosure" ball-gag stuck in their mouth by the carriers.
Again, Blame Motorola if you want. You are wrong, but it's your right to be wrong.
EDIT--
Motorola is great about communications when they have a problem that they can talk about, like the Motoblur interface or hardware issues. But, when the problem is with the carriers, and they have a contractual obligation MUTING them to it, they can't talk about it. So, take their lack of communications as it is something they can't talk about. What can they not talk about? Problems related to the carriers.
Second, what's the difference between a build for a US phone verses the UK phones? Carrier related issues like radios/network compatibility. Obviously, they have GB working, we have it here in the states. What's the difference? The carriers.
The lowest common denominator are the carriers. Thus, logic dictates that's where to assume the hold up is.
I understand your frustration. I just want to make sure you aim it in the right direction.
Last edited by WolfmanRobby; October 26th, 2011 at 10:57 AM.
Myself, I DEPEND on my phone, so I don't fool with custom ROM's. So, if Moto does not release an official build, my phone may never see ICS (unless I get a new phone and this one get's to become my "Test Subject" - ***Insert evil laugh here***).
Hey there Wolfman, I respectfully disagree with some of your prior post. I also depend on my phone, which is why I unlocked the bootloader, rooted it and run nothing but custom roms. Why custom roms over OTA manufacturer releases? Part of my need for a dependable phone is a matter of trust: I trust custom rom creators (or at least the ones I know well enough to install their products on my phone) and I have no trust whatsoever in Motorola or AT&T (actually, *any* manufacturer or carrier) because the carrier wants to load bloatware onto every phone they service and the manufacturers have their own agendas. The really good custom rom developers have no need or desire to install bloatware in their roms, are usually quick to respond to questions or problems that are directed to them, and in general take pride in their product. Since their products are offered free of charge, there's no monetary gain from loading junk programs like golf or other games into their rom.
I limit my endorsement of custom roms to "most developers" rather than "all developers" because there are some less than perfect developers out there. However, it has been my privilege to count a number of developers as personal friends and I know for a *fact* that these guys do what they do for a number of reasons, but money isn't one of them. They take pride in turning out a *quality* product that people will use and appreciate and while contributions are always nice to get, they don't expect (or usually get) money in return for their efforts. These guys, I trust.
Now switching back to the OTA scenario: Google creates the Android OS that we install, one way or another, on our phones. Google I trust. Unfortunately, with the exception of the Nexus line of phones, Google doesn't send their software directly to the end user. Instead, you have Motorola and the carrier (Verizon being the *prime* offender) who in acting as middlemen insert the bloatware (the carrier) and the "gotchas" (Motorola) which plague the phones of those of us who have chosen to mod our phones.
The solution: place your faith in those you trust (for me, custom rom developers and Google) and avoid the alternative (OTA updates) like the plague.
As I said upfront, I respectfully disagree with Wolfman, but this is just my slant on things. There's no right or wrong position, it's just whatever works for you and your phone.
-Mike
__________________ Rooted HTC Inspire 4G NINJA-0817 (2.3.4) Rom
Rooted Motorola Atrix 4G
With UNLOCKED Bootloader The DarkSide v1.4 - Empire Rom
Now switching back to the OTA scenario: Google creates the Android OS that we install, one way or another, on our phones. Google I trust. Unfortunately, with the exception of the Nexus line of phones, Google doesn't send their software directly to the end user. Instead, you have Motorola and the carrier (Verizon being the *prime* offender) who in acting as middlemen insert the bloatware (the carrier) and the "gotchas" (Motorola) which plague the phones of those of us who have chosen to mod our phones.
If you knew what you were doing, you could download the source code and build your own ROM.
As for OEM's verses custom ROMs... I run custom ROM's on my Tablet's. And, while they don't have the bloatware, there are always issues the ROM developers can't workout. Like drivers for some of the hardware.
Example: On my ViewSonic G-Tab. No one can get a HoneyComb based ROM to work the front facing camera due to the lack of drivers. In fact, about the only 3rd party ROM's that can get the front facing camera to work are still FroYo, and that's only because they can pull the OEM drivers out of the OEM ROM. The only exception to this that I've found is the VeganTAB ROM. It's GB, and I think the developer was able to trick it into using the FroYo camera drivers.
But, I don't depend on my tablet like I do my phone.
No one knows the hardware in my phone better than the OEM. That means, they are the most reliable on that matter. I'd rather deal with a little bloatware that, most of the time I can remove or disable to make sure I have a device with the most accurate device drivers.
Another point you miss on the OEM verses custom ROMs... WARRANTY. Like I said, I depend on my phone. If something goes wrong, I need to get it replaced ASAP. Motorola puts an eFuse in the Atrix that BLOWS if you unlock the bootloader. This means, if I were to unlock the bootloader, regardless of if I load another ROM or not, the Warranty is VOID. So, if the phone breaks, I'm up Sh!t Creek.
EDIT- Unlocking the bootloader on the Atrix and blowing that eFuse in the process also means you can never go back to an official, stock ROM. This means you can't simply FLASH an OEM ROM back onto the phone to take it in for a Warranty replacement.
Like you say, to each their own.
Myself, I find it easier and more reliable to uninstall that unwanted Golf Game, than to root my phone, unlock the bootloader, blow the eFuse, void the warranty, and load a 3rd party ROM on it.
Last edited by WolfmanRobby; November 9th, 2011 at 09:46 PM.
Like you say, to each their own.
Myself, I find it easier and more reliable to uninstall that unwanted Golf Game, than to root my phone, unlock the bootloader, blow the eFuse, void the warranty, and load a 3rd party ROM on it.
As I indicated, it comes down to a matter of trust (You trust the manufacturer, I don't) as well as personal taste (You like the OS that Motorola delivers, by way of AT&T, I don't). I tried to conch my original posts in non-confrontational language, but you seem annoyed so we'll just drop the entire issue, OK?
I tried to conch my original posts in non-confrontational language, but you seem annoyed so we'll just drop the entire issue, OK?
I'm not annoyed. I just pointed out the basis for why I think the OEM ROM's are better for me and my needs. Including information that I think people need to be aware of (IE: Blowing the eFuse, voiding the warranty, and never being able to come back to OEM).
After all, you explained why you think custom ROM's are better. I just figured it would be fair for me to explain my views.
Might I interject here and ask if anyone has ASKED the carrier in question OR Motorola where the hold up is? I mean actually speaking to someone at either end?
Might I interject here and ask if anyone has ASKED the carrier in question OR Motorola where the hold up is? I mean actually speaking to someone at either end?
I know ... WAY too simple!
One does not simply walk into Mordor.... nor do they simply call up Motorola and ask them if they are going to release an ICS build for this phone.
The SIMPLE thing to do, is wait and see if it gets added to the list of devices they are going to release ICS for.
Until they announce it publicly, they won't give an answer if you just simply ask.
I doubt motorola will be upgrading to Ice Cream, they have bigger fish to fry now, the atrix has been released almost a year ago, all the other phones coming out are as powerfull or more powerfull. If the atrix gets it it will be because they have made the update compatible with other motorola's such as the Razr. Anyways I am basing it purely on logic but knowing moto they will want to speed up new device development for you to buy more and not spend resources on upgrading older devices people have already bought.
Device(s): Motorola Atrix HD (and loving it)
Motorola Atrix (AKA SUPERPHONE)
Motorola Defy (on AT&T - shelved)
Carrier: Not Provided
Thanks: 19
Thanked 20 Times in 17 Posts
SO I am running 2.3.4 Gingerbread and the wife's new Atrix 2 has 2.3.5 Gingerbread, what's the difference?
I know her's has buttery smooth menus and the app drawer now swipes to the left and right instead of up and down....is that all the "new motoblur lite" or is that part of the continuing update of Android?
I know her's has buttery smooth menus and the app drawer now swipes to the left and right instead of up and down....is that all the "new motoblur lite" or is that part of the continuing update of Android?
The App drawer direction is from the Launcher (in this case, she has the new MotoBlur). My fist Android (Archos 5"Tablet) ran 1.6 and it's app drawer went left to right like that. So, it's not anything new.
My current tablet is running 2.3.4 (like my Atrix) and it's Launcher goes left to right. I think the launcher on it will let me change from left/right to up/down. If that's something you like, you can try another launcher on your Atrix. I know Launcher Pro does not do that (that's what I use) but, there are others out there.
Device(s): Motorola Atrix HD (and loving it)
Motorola Atrix (AKA SUPERPHONE)
Motorola Defy (on AT&T - shelved)
Carrier: Not Provided
Thanks: 19
Thanked 20 Times in 17 Posts
Quote:
Originally Posted by WolfmanRobby
The App drawer direction is from the Launcher (in this case, she has the new MotoBlur). My fist Android (Archos 5"Tablet) ran 1.6 and it's app drawer went left to right like that. So, it's not anything new.
My current tablet is running 2.3.4 (like my Atrix) and it's Launcher goes left to right. I think the launcher on it will let me change from left/right to up/down. If that's something you like, you can try another launcher on your Atrix. I know Launcher Pro does not do that (that's what I use) but, there are others out there.
I have Launcher Pro too, hate the motoblur that came on the Atrix.
So is there any real, noticeable difference with 2.3.4 to 2.3.5?
So is there any real, noticeable difference with 2.3.4 to 2.3.5?
You are in a better position to answer that than we are. The Atrix runs 2.3.4 and the Atrix 2 runs 2.3.5.
You should be able to do a side by side with your wife's phone and see the differences. If not, you might want to ask in the Atrix 2 forum for someone that has actually used both phones that can tell you more.
Device(s): Motorola Atrix HD (and loving it)
Motorola Atrix (AKA SUPERPHONE)
Motorola Defy (on AT&T - shelved)
Carrier: Not Provided
Thanks: 19
Thanked 20 Times in 17 Posts
Quote:
Originally Posted by kycats
No. Version 2.3.5 is a maintenance update.
From Android.com:
2.3.5
25 Jul 2011
Brought improved network performance for the Nexus S 4G, among other fixes and improvements.
Fixed bluetooth bug on Samsung Galaxy S
Improved Gmail application
What's New in GMail?
Save bandwidth and battery by only syncing priority mail
Use label notifications to mash up filters, labels, and ringtones
Remember ‘Show Pictures’ for senders
Turn off sticky message actions in landscape or all orientations
Better TalkBack support for accessibility
Performance improvements
Quote:
Originally Posted by WolfmanRobby
You are in a better position to answer that than we are. The Atrix runs 2.3.4 and the Atrix 2 runs 2.3.5.
You should be able to do a side by side with your wife's phone and see the differences. If not, you might want to ask in the Atrix 2 forum for someone that has actually used both phones that can tell you more.
All we can do is comment on 2.3.4. - Sorry
Thanks guys, I only noticed the things I mentioned, new menus and some differing icons, near as I can tell that's all part of motoblur lite. So I guess as stated above, it's 99% identical (just a maintenance update) and since the phones named in the first post do not include any Motorola phones, it must be for all intents and purposes the same Moto to Moto.
Has this been mentioned yet? [KANG] CM9 Atrix Test Build by wrldsuksgo2mars - xda-developers
I've been running it today testing it out, and really aside from the camera, google maps and flash video it runs just fine (I'm also running adw launcher because the stock one crashes a lot)
Has this been mentioned yet? [KANG] CM9 Atrix Test Build by wrldsuksgo2mars - xda-developers
I've been running it today testing it out, and really aside from the camera, google maps and flash video it runs just fine (I'm also running adw launcher because the stock one crashes a lot)
lol, might be a bit of a wait than if ever :/ would be nice though, maybe if they released an official port it would be easier for developers to make a less buggy rom lol
Device(s): Motorola Backflip; Motorola Atrix 4G and Lapdock
Carrier: Not Provided
Thanks: 37
Thanked 185 Times in 173 Posts
I'm in no hurry to upgrade to ICS. I just upgraded to GB in Nov. and still learing it. (I love it by the way.) I'd really rather wait until ICS has been out for awhile and all the bugs worked out. (Look at the bugs reported on the Atrix 4G when upgraded to GB.) I depend on my phone for my day to day activities and can't afford to be without. (I never thought I'd put this much into a cellphone.) The times we live in.
I emailed Motorola last week about ice cream sandwich 4.0; I have not gotten a reply yet so am thinking we won't get ICS they just want us to buy new phones with the ICS already on it. Maybe someone will just have to phone Motorola and ask whats going on????
Last edited by Waloshin; January 3rd, 2012 at 05:54 PM.
ok people i was talking to some jim guy from Motorola chat and this is what he had to say sorry if i didn't spell right i was typing to fast sorry (Jim: Hi, my name is Jim. How may I help you? Waloshin: hi i have a motorola atrix 4g and me and others were wondering if we were going to get the ice cream sandwich 4.0 anytime soon or if ever? i did already email motorola my self a week ago i got no reply so i was just wondering thanks Jim: I apologize for the inconvenience. We are planning to upgrade DROID RAZR, DROID BIONIC, Motorola XOOM including the Wi-Fi only and the XOOM Family Edition to Ice Cream Sandwich. We will provide more precise guidance on timing once deployment details have been finalized by Google, as well as any possible additions to this list of devices. As of now, we do not have inforrmation when the Motorola Atrix will be included on this list. Waloshin: ok do you think they will do the upgrade? Jim: I'm really sorry. I do not have information about the update on the Atrix to ICS. Waloshin: ok thanks Jim: You are welcome. If you need any more information get in touch. Thanks from Motorola, bye! Jim has disconnected.
1. Read reason Motorola will update razr and bionic is that they both use same or similar Texas instrument Omap processor google used as template for the galaxy nexus.
2. Yes Xoom is/has gotten ICS and has tegra 2. But Xoom is also a "google experience device" meaning Google helps out Motorola with early access to updates.
So it's not looking good for ice cream on the atrix. Atrix is not a google experience device and doesn't have the omap processor.
Google Chrome for Android is now available in the Android Market Place, but it requires Android 4.0 Ice Cream Sandwich phone to install it. Now Google is making amends -- to some Android users, at least. The brand new Chrome for Android is only for Ice Cream Sandwich products at this time, leaving most Android customers out in the cold. I got the information here: Google Chrome now available for Ice Cream Sandwich.
Out of curiosity, what about ISC is beneficial over Gingerbread?
Go onto youtube and look for ICS demo videos. I put ICS on my generic tablet the other day. The interface is a little easier to use and has some cool new features. More importantly everything seems to run faster and smoother - despite the fact that the standard benchmark numbers haven't changed.
The Motorola Atrix 4G brings several firsts to AT&T's lineup, among them a dual-core CPU in the form of NVIDIA's Tegra 2 platform. The CPU is clocked at 1GHz per core, providing enough zip to match the HSPA+ connectivity and 4G download... Read More
Give me Ice Cream Sandwich !!!
Waloshin: hi i have a motorola atrix 4g and me and others were wondering if we were going to get the ice cream sandwich 4.0 anytime soon or if ever? i did already email motorola my self a week ago i got no reply so i was just wondering thanks
Jim: I apologize for the inconvenience. We are planning to upgrade DROID RAZR, DROID BIONIC, Motorola XOOM including the Wi-Fi only and the XOOM Family Edition to Ice Cream Sandwich. We will provide more precise guidance on timing once deployment details have been finalized by Google, as well as any possible additions to this list of devices. As of now, we do not have inforrmation when the Motorola Atrix will be included on this list.
Jim has disconnected.
