Related
I got this from another thread on XDA, if it needs to go to the Q&A section, please move it.
What I find interesting, is the BOLD section.
This "explanation" has to do with the Samsung Galaxy S series, but, could also be viable to all android phones.
Now, never let it be said I'm defending at&t in ANY way, but perhaps some of the lag on updates, could be this.
If the manufacturer is "selling" an android update to a carrier, wouldn't that be in violation of the open source agreement?
To explain the political situation, first, a primer on how phone firmware upgrades work for carriers. When a carrier decides to sell a phone, a contract is usually written between the phone manufacturer and the carrier. In this contract, the cost of updates (to the carrier) is usually outlined. Updates are usually broken into several types: critical updates, maintenance updates, and feature updates. Critical updates are those that resolve a critical bug in the phone, such as the phone overheating. Maintenance updates involve routine updates to resolve bugs and other issues reported by the carrier. Finally, feature updates add some new feature in software that wasn’t present before. Critical updates are usually free, maintenance updates have some maintenance fee associated with them, and feature updates are usually costly. In the past, most phone updates would mainly consist of critical and maintenance updates. Carriers almost never want to incur the cost of a feature update because it is of little benefit to them, adds little to the device, and involves a lot of testing on the carrier end. Android has changed the playing field, however – since the Android Open Source Project is constantly being updated, and that information being made widely available to the public, there is pressure for the phone to be constantly updated with the latest version of Android. With most manufacturers, such as HTC, Motorola, etc. This is fine and considered a maintenance upgrade. Samsung, however, considers it a feature update, and requires carriers to pay a per device update fee for each incremental Android update.
Now, here’s where the politics come in: most U.S. carriers aren’t very happy with Samsung’s decision to charge for Android updates as feature updates, especially since they are essentially charging for the Android Open Source Project’s efforts, and the effort on Samsung’s end is rather minimal. As a result of perhaps, corporate collusion, all U.S. carriers have decided to refuse to pay for the Android 2.2 update, in hopes that the devaluation of the Galaxy S line will cause Samsung to drop their fees and give the update to the carriers. The situation has panned out differently in other parts of the world, but this is the situation in the United States.
Some of you might have noticed Verion’s Fascinate updated, but without 2.2 : This is a result of a maintenance agreement Samsung must honor combined with Verizon’s unwillingness to pay the update fees. In short, Android 2.2 is on hold for Galaxy S phones until the U.S. carriers and Samsung reach a consensus.
Some might wonder why I didn’t deliver this over a more legitimate news channel – the short answer: I don’t want to lose my job. I do, however, appreciate transparency, which is why I’m here.
Hey was just wondering if anyone on the Telus network recieved the update yet?
I am on TELUS with LG Win 7 phone and wanted to make sure they aren't being blocked by my carrier as Microsoft said they might be for some networks. I've checked through Zune and still nothing I know it's only been two days but I'd rather know now if I have to start finding another solution to get updates. If anyone has recieved a notification or knows anything about it let me know thanks
I did not get anything either. I have a feeling a lot of carrier based phones haven't got them yet, and I doubt a lot of them are blocking it.
Edit: I stand corrected according to wmpoweruser It seems like telus hasn't pushed any updates but this can be due to the whole samsung fiasco delaying things.
Any chance you can send me a link to that page would love to see what's going on.
bond7734 said:
Any chance you can send me a link to that page would love to see what's going on.
Click to expand...
Click to collapse
it was an informal poll, just people leaving comments saying they had or hadnt gotten it.
I just spoke with a telus rep who wasn't able to tell me anything more about if/when the update would be available (I was on hold while he contacted "the technical team").
The only piece of information I got (which was assumed ... by me anyways ) was that unlike the old system where Telus paid OEMs to create the updates the wp7 updates are "free" to the carrier.
March 1 and still no update. I think Telus is skipping this one. The Telus rep I called didn't even know Telus carried any Windows phones and thought I meant the iPhone, so you can imagine how long that phone call lasted.
The 7008 update is now available for Telus customers. Here's news for the 7389 update (NoDo);
The earliest date that a TELUS customer can receive the Windows Phone 7 software update is Tuesday March 29th, 2011. Microsoft is releasing the software update in a phased approach and it may take up to four weeks for all TELUS customers to have the option to receive the update and upgrade their device software.
Keep your smartphone running efficiently by using the latest available software.
The release of OS software 7.0.7389.0, provides the following benefits and enhancements for your smartphone.
Introduction of copy and paste functionality.
http://www.telusmobility.com/en/QC/lg_optimus_7_support/
The one thing I noticed after updating my phone is that it did not do a backup of it. (There was only 9 steps done on the update process) I thought that the pre-nodo update was supposed to make a backup of your phone.
i have a telus lg optimus 7 unlocked and now on the sasktel network. my question is am i screwed for getting these updates because sasktel doesn't recognize the phone as one of there models and i am not on the telus network so they wont push it to me? i cant justify paying 400 bucks for a phone that i cant get the new updates the Microsoft rolls out.
If you do not get this update, you will get the next one (By mid March) definitely. Microsoft has confirmed that much. I contacted Telus, and it seems they have "no information to offer at this time". Basically, Telus is the only carrier in North America that has yet to offer update for their WP7 devices, but two weeks is not that long to wait, right? Especially considering that this update does...nothing, and all updates are cumulative.
kapanak said:
If you do not get this update, you will get the next one (By mid March) definitely. Microsoft has confirmed that much. I contacted Telus, and it seems they have "no information to offer at this time". Basically, Telus is the only carrier in North America that has yet to offer update for their WP7 devices, but two weeks is not that long to wait, right? Especially considering that this update does...nothing, and all updates are cumulative.
Click to expand...
Click to collapse
I'm planning on giving Telus a few more days before complaining loudly, as the rollout was to be staged, so maybe they volunteered to be last on the list :|
Personally, I'm fairly concerned about this as Telus doesn't have the greatest record for updates in the past, and holding this back isn't a good sign (imho).
Even if this minor update is rolled into "no-do", there's no guarantee "mango" won't be an 'odd numbered' update, or that we won't be weeks behind others getting either/both.
From the windows phone team blog
(http://windowsteamblog.com/windows_...-answers-about-our-first-software-update.aspx)
Q: I still haven’t received an update notification yet. When can I expect it?
A: It’s hard to predict because it depends on many factors. It could be days—or even weeks—before you’re able to update your phone.
Click to expand...
Click to collapse
So as the rest of the world gets copy/paste, theoretically we telus users could just be getting the pre-nodo update.
I'm right there with you I had the same thought when I read that article. I don't understand why Rogers and Bell both have launched it but Telus hasn't I tweet'd customer service about it and they answered back they had no information about unreleased updates.
I am hoping that maybe Telus wanted to "save us" from the trouble of doing 2 updates in a fairly short period of time. At least we know that they can't block nodo. Out of curiosity does anyone know how Telus is with android updates?
bond7734 said:
I'm right there with you I had the same thought when I read that article. I don't understand why Rogers and Bell both have launched it but Telus hasn't I tweet'd customer service about it and they answered back they had no information about unreleased updates.
Click to expand...
Click to collapse
I've been looking around all the standard places for more info but haven't come across anything. My fear is that the wp7 userbase on Telus is small enough that they don't consider us a priority.
nVd90 said:
I am hoping that maybe Telus wanted to "save us" from the trouble of doing 2 updates in a fairly short period of time. At least we know that they can't block nodo. Out of curiosity does anyone know how Telus is with android updates?
Click to expand...
Click to collapse
They're mediocre at best.
http://www.androidincanada.ca/category/telus-android/
Another thread discussing similar possibilities for crappy timing/rollout (carriers get 8 weeks?!)
http://forum.xda-developers.com/showthread.php?t=968990
I hope that we are considered a priority. I'll do my part and call and bug them maybe if everyone jumps on board we'll get this update.
i spoke to sasktel and they have already rolled out the patch on there network. but because my phone is telus branded and the zune software see the phone as telus it wont give me the update. sasktel does not recognize my phone for updates so i would assume that's because they don't sell the phone.
I'm in the same situation as you kazman. Have an unlocked Telus branded Optimus 7 running on the Bell network, and wondering if I'll get the update when/if Telus releases it.
Will report if I do.
I cannot believe we can't find a solution to get the update...
Like Android, installed custom ROM of WP7 to avoid carrier blocking.
xdapants said:
I've been looking around all the standard places for more info but haven't come across anything. My fear is that the wp7 userbase on Telus is small enough that they don't consider us a priority.
They're mediocre at best.
http://www.androidincanada.ca/category/telus-android/
Another thread discussing similar possibilities for crappy timing/rollout (carriers get 8 weeks?!)
http://forum.xda-developers.com/showthread.php?t=968990
Click to expand...
Click to collapse
So I emailed client care about the update, (your gonna love this)
"Hello Justin,
Thank you for taking the time to write to TELUS via e-mail.
Windows has not released any official updates yet. Please refer to the following link for details:
http://www.microsoft.com/windowsphone/en-us/features/update-info.aspx
When an official update is released from the manufacturer, it's also posted on our equipment page specific to your phone:
http://www.telusmobility.com/en/ON/lg_optimus_7/index.shtml
For further information or assistance, please reply to this message, including your original e-mail and our response. If you prefer, you may also call our Client Care team toll free Monday to Friday from 8:00 AM to 10:00 PM, and Weekends and Holidays from 9:00 AM to 8:00 PM at 1-866-558-2273 (or *611 from your wireless handset).
Thank you for using TELUS' online service and have a great day."
So I have emailed back asking that he double check the site and not just send me to the page that tells people what the next update is but infact to check the update page (http://www.microsoft.com/windowsphone/en-us/howto/wp7/basics/update-history.aspx) Still waiting on an answer but it's great that they took the time to really look into it So I have emailed back and shown them the link and also shown them Bell and Roger's pages releasing it as well as a few carriers with the same phone (LG Optimus 7) that have released it. (because you know that's where they would go next) Will post results on here if I get them.
that is completely ridiculous. i called a telus store yesterday in Saskatchewan and she told me that they don't know about updates and recommended that i move the date on my phone ahead a year and i should get the update then. but she had just told me a minute ago that there where no updates. they need to get a clue.
So it seems like Telus just doesn't know what to do with updating the phone. I am a bit surprised and doubtful that Microsoft didn't tell them though. It just shows a huge lack of communication within Telus.
as I posted in the other thread, I talked to a telus rep who also no idea about the update; but was able to confirm they didn't have to pay MS for it, so we should be getting it.
I've got a 10 year old account with them and made it clear I would be willing to switch carriers if they dropped the ball.
Hopefully we can get enough people telling telus the same that they'll get their act together.
i would like to know why we cant just get the update from the zune software. and if a carrier such as telus hasn't released the update how does the zune software know not to offer you an update or does telus need to respsond to microsoft that the update is out on there network. how about a new rom from bell or rogers that would solve all our problems.
kazman13 said:
i would like to know why we cant just get the update from the zune software. and if a carrier such as telus hasn't released the update how does the zune software know not to offer you an update or does telus need to respsond to microsoft that the update is out on there network.
Click to expand...
Click to collapse
It's going to be something like that (e.g. telus tells MS it's approved, WinPhoneUpdate sets the flag to allow it).
kazman13 said:
how about a new rom from bell or rogers that would solve all our problems.
Click to expand...
Click to collapse
I'd assume going to a differently branded rom would solve it, although that'd likely negate access to the telus app store. Another potential issue is that the telus optimus7 is a different model number from the european one. I have no idea which version the mexicans got so there may not even be a viable alternate rom. :|
An unfortunate truth
Look guys, this first update was OPTIONAL for carriers. It did not provide any new features and was just a test update before the real update in a week and a bit. Unfortunately for you guys, TELUS decided to not push this one in favour of just sending one update later. You shouldn't be upset at TELUS ... yet. I had an Android phone with them before and just about lost my mind over the update issue, but I think WP7 will be different because MS has more say than the OEMs do regarding Android. I feel bad that you guys are suffering, but it isn't really TELUS' fault.
Commander Data said:
Look guys, this first update was OPTIONAL for carriers. It did not provide any new features and was just a test update before the real update in a week and a bit.
Click to expand...
Click to collapse
That doesn't really disuade any concerns.
It's not just a test and no user visible features does not equal not necessary - think API changes before mango
My main fear is that something I'll deem critical will be in one of these minor updates, and telus will make me wait 6 months till the next major update instead of just pushing me the fix.
Commander Data said:
You shouldn't be upset at TELUS ... yet.
Click to expand...
Click to collapse
I concur, as this is hopefully a unique/one time scenario, which is why I'm waiting to see what they do with NoDo before complainging too loudly/switching carriers
Commander Data said:
I feel bad that you guys are suffering, but it isn't really TELUS' fault.
Click to expand...
Click to collapse
Just because I feel like nitpicking (I'm just being a smart-ass, don't take it seriously/personally ):
There are three "entities" involved in getting my phone updated
1) Microsoft - they've released the update, not their fault
2) Myself - I've connected to my computer and forced zune to check for updates, not my fault
3) Telus - They're not pushing the update for whatever reason ... pretty sure it's their fault
optional or not this still makes telus look bad when all other major carriers in canada are pushing this update but not telus.
bond7734 said:
So I emailed client care about the update, (your gonna love this)
"Hello Justin,
Thank you for taking the time to write to TELUS via e-mail.
Windows has not released any official updates yet. Please refer to the following link for details:
http://www.microsoft.com/windowsphone/en-us/features/update-info.aspx
When an official update is released from the manufacturer, it's also posted on our equipment page specific to your phone:
http://www.telusmobility.com/en/ON/lg_optimus_7/index.shtml
For further information or assistance, please reply to this message, including your original e-mail and our response. If you prefer, you may also call our Client Care team toll free Monday to Friday from 8:00 AM to 10:00 PM, and Weekends and Holidays from 9:00 AM to 8:00 PM at 1-866-558-2273 (or *611 from your wireless handset).
Thank you for using TELUS' online service and have a great day."
So I have emailed back asking that he double check the site and not just send me to the page that tells people what the next update is but infact to check the update page (http://www.microsoft.com/windowsphone/en-us/howto/wp7/basics/update-history.aspx) Still waiting on an answer but it's great that they took the time to really look into it So I have emailed back and shown them the link and also shown them Bell and Roger's pages releasing it as well as a few carriers with the same phone (LG Optimus 7) that have released it. (because you know that's where they would go next) Will post results on here if I get them.
Click to expand...
Click to collapse
Here's the answer! I got back from Telus after showing them where the update was and asking why we don't have it and why Rogers and Bell have released it.
Hello Justin,
Thank you for your reply.
Due to the technical requirements involved we are unable to disclose when the update will become available.
I would recommend to check our Website for updates as this is the first place any new information on your handset will be advertised:
http://www.telusmobility.com/en/ON/lg_optimus_7_support/
I regret any inconvenience or confusion this has caused and thank you for your patience in this matter.
For further information or assistance, please reply to this message, including your original e-mail and our response. If you prefer, you may also call our Client Care Team toll free Monday to Friday from 8:00 AM to 10:00 PM, and Saturday and Sunday from 9:00 AM to 8:00 PM at 1-866-558-2273 (or *611 from your wireless handset).
Thank you for using TELUS' Online Services and I hope you have a wonderful day.
Best regards,
Aekta
e.Care Specialist
TELUS
There's a technical requirment that makes them unable to disclose when the update will become avalible... doesn't make too much sense but I do agree with all of you. It's not that I desperatly want this update or that it's really negativly effecting me in anyway, it's that I fear this pattern may continue on to updates that improve the phone. We'll see what happens in March hopefully Telus pulls it together or at least has a better answer then just because.
Alright... before the huge amounts of responses and memes responses, let's make something clear:
This is the US version purchased from amazon.com during a trip to the US.
I have a mobilicity (Canada) SIM in my phone
Still no update
The only thing I imagine is blocking my update is my IP address/GPS location or my carrier sim card.
- Does anybody know how to bypass this check? or fool the phone to think i am in the US? I am not really into rooting this phone or losing the warranty on it.
- Anyone with a US version in Canada who received the OTA? what carrier are you using?
Thanks in advance.
Motorola is releasing the update in batches, so not even all US phones have officially received the update yet. You can update your's immediately by following these steps: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
JJJame said:
not even all US phones have officially received the update yet
Click to expand...
Click to collapse
it's been more than almost a month. I thought everybody in a US MotoG in the US had their update already. Anyone in the US that has NOT gotten the update?
jrcastillo said:
it's been more than almost a month. I thought everybody in a US MotoG in the US had their update already. Anyone in the US that has NOT gotten the update?
Click to expand...
Click to collapse
I have the unlocked global GSM version bought off Amazon. No update, still on Kitkat.
jrcastillo said:
it's been more than almost a month. I thought everybody in a US MotoG in the US had their update already. Anyone in the US that has NOT gotten the update?
Click to expand...
Click to collapse
I do not. 2014 Moto G single SIM US Market GSM model purchased at Best Buy in Denver. No OTA and no update available via the Moto Device Manager software.
EDIT: There are some Moto comments in this thread saying they're still working on L so it seems they pulled the full update: https://forums.motorola.com/posts/6168839e0e?commentId=838808#838808
jrcastillo said:
it's been more than almost a month. I thought everybody in a US MotoG in the US had their update already. Anyone in the US that has NOT gotten the update?
Click to expand...
Click to collapse
Same boat here: Moto G XT1064 (USA GSM, Unlocked, Carrier-independent) bought from Amazon in early November, still no Lollipop update for me, also checked OT and via Motorola Device Manager. Apparently Moto has pulled the update to fix some bugs, but they've done a TERRIBLE job of messaging this. They have an "official blog" which trumpets the launch of Lollipop but no mention anywhere, on any of their support pages or their blog, that this update has been shelved to fix some bugs. I'm fine with that, but I need to *know* that's what's happening rather than just sitting around pushing update and wondering why my phone still hasn't gotten the update yet.
Moto needs to better message this stuff so that we don't have to hunt through forums to find answers to our questions. I even contacted Motorola support a few days ago and they didn't mention a word of this, so it almost seems like the left hand doesn't know what the right is doing. Either way, this has been a really disappointing rollout
illuminerdi said:
Same boat here: Moto G XT1064 (USA GSM, Unlocked, Carrier-independent) bought from Amazon in early November, still no Lollipop update for me, also checked OT and via Motorola Device Manager. Apparently Moto has pulled the update to fix some bugs, but they've done a TERRIBLE job of messaging this. (
Click to expand...
Click to collapse
interesting. I too believe that is OK if they had to pull it... but had i known they had done this I wouldn't have checked every day like a maniac hoping to get the OTA.
what you mean OT and via Motorola Device Manager. I tried using the MDM but it never detected my device. When i plug it in, windows 8.1 detects it as XT1064 and i am able to access the memory card, etc. But MDM did not see the device. I read somewhere that this happens if its not supported.
how did you get MDM to work with your device?
What you mean by OT? did you mean OT"A"?
AT&T: Hello! How may I help you today?
Chris: Hello thank you for chatting in how can I help?
Tim: hello I have a question about my phone
Tim: Verizon recently allowed it's customers to unlock their bootloaders via the motoroloa site. When will this happen for at&t
models of this phone? (moto x 2014)
Chris: Let me look into this Tim.
Tim: Verizon did it because you all we'rent pushing the marshmellow update
Tim: I would really like to install a custom rom and have complete control over my device.
Chris: We are currently prepping for sending out the Marshmallow update to our Android customers. For unlocking the bootloaders I believe that is done through Motorola in general, we just unlock devices through the network.
Chris: I cannot assist with setting up a custom OS/Rom on the device, for liability reasons, this would have to be done from your end, I apologize.
Tim: it was announced that this device would not get the update
Tim: will at&t allow motorola customers to unlock their bootloaders?
Tim: on this model
Chris: Unlocking bootloaders is handled on Motorolas end, we do not have access to that information on our end, I apologize.
Tim: but you could look into if this specific model has any unlocking info to be sent to motorola
Tim: right?
Chris: The only unlocking information I am aware of is unlocking the device for use with other networks/international use
Tim: Motorola is telling me that it is at&t that will not allow the unlocking
Tim: No no, unlocking bootloader. at&t specifically told motorola to not let customers unlock bootloader on this phone. Verizon just gave in, and I was curious if I can get any info
Chris: Not that I am aware of. I apologize for this inconvenience Tim. I was told by my supervisor this is only handled from Motorolas end, if applicable
Tim: that is unfortunate.
Chris: From what I read into the Moto X 2014 model may get the marshmallow update, from what I read it's still up in the air.
Tim: can you link me to where you read this?
Chris: I don't have the ability to send that article to you - this is on our database.
Tim: I've read many articles about how the moto x 2014 would not get it on either verizon or att.
Tim: strange that your database would say that
Chris: It's not finalized. At any rate I think Android would know whether or not the moto x 2014 model will get it and which carriers would have it.
Tim: ok, thank you
He doesn't seem very knowledgeable about the situation.
Seem like you was talking to a brick wall
seems like part bot, part trainee.
We all need to message ATT on Social Media to get a proper response.
Sent a Tweet @att & @attCares regarding this very subject.
Do it guys. Lets show them the potential of power users who want their bootloaders unlocked.
well i just asked twiter: @att @lenovo @motorola now that the @verizon moto x 2014 has an official unlock for the bootloader when will the att version?
Doing this right now. I've only messaged them on fb but these are all good ideas.
Thanks brother!
Sent from my XT1097 using XDA Free mobile app
Great man. Still hoping att will release Marshmallow for the X (the last true Moto/ not Lenovo).
I've had conversation with AT&T and Motorola. Both are pointing at each other for unlocking. Not sure where should I bang my head.
"At any rate I think Android would know whether or not the moto x 2014 model will get it and which carriers would have it." Proves they don't know much lol. How could Android know if a phone will be updated? Lmao.
chris23445 said:
"At any rate I think Android would know whether or not the moto x 2014 model will get it and which carriers would have it." Proves they don't know much lol. How could Android know if a phone will be updated? Lmao.
Click to expand...
Click to collapse
That's when I realized this person knew nothing and ended the conversation. Idiots.
Sent from my XT1097 using XDA Free mobile app
timmypbass said:
That's when I realized this person knew nothing and ended the conversation. Idiots.
Sent from my XT1097 using XDA Free mobile app
Click to expand...
Click to collapse
I just received amazon order of moto X Pure 2014, same condition as mine except the AT&T logo. Swap and return might be a faster way? Lol.
wangminh12 said:
I just received amazon order of moto X Pure 2014, same condition as mine except the AT&T logo. Swap and return might be a faster way? Lol.
Click to expand...
Click to collapse
Surely, you are joking.
For one thing, the IMEI on the device won't match one on the box, which a good seller (if it wasn't Amazon directly) would have denoted, prior to shipping it out.
dirtykimchi said:
Surely, you are joking.
For one thing, the IMEI on the device won't match one on the box, which a good seller (if it wasn't Amazon directly) would have denoted, prior to shipping it out.
Click to expand...
Click to collapse
Lol.I bought directly from Amazon Warehouse deal- used. Haven't noticed a different between Marsmallow and Lollipops even battery life.
For $160 used- like new still in warranty, it is a nice thing too keep as a backup. Probably among the last devices with Motorola's badge on it ( Lenovo about to kill the brand tho).
Nexus 6 is pretty cool but it's size really bothers me.
ATT truely suck, will never buy any phone with att on it.
It would make sense if they benefitted some how from our inability to unlock but they don't. What the he11 is the issue here.?
Sent from my XT1097 using XDA Free mobile app
timmypbass said:
It would make sense if they benefitted some how from our inability to unlock but they don't. What the he11 is the issue here.?
Sent from my XT1097 using XDA Free mobile app
Click to expand...
Click to collapse
For a crazy privacy reason I'm sure +
For each update rolling out, phone maker has to pay a certain amount $$$ to Carrier and in this case Motorola ain't paying--> bang the X.:angel:
wangminh12 said:
For a crazy privacy reason I'm sure +
For each update rolling out, phone maker has to pay a certain amount $$$ to Carrier and in this case Motorola ain't paying--> bang the X.:angel:
Click to expand...
Click to collapse
The Device is End of Life already for AT&T. These devices are not under warranty anymore. All 2 year subsidies should complete later this year on these devices as well. AT&T is grasping at straws at this point; looking for reasons to deny all owners of a bootloader unlock.
dirtykimchi said:
The Device is End of Life already for AT&T. These devices are not under warranty anymore. All 2 year subsidies should complete later this year on these devices as well. AT&T is grasping at straws at this point; looking for reasons to deny all owners of a bootloader unlock.
Click to expand...
Click to collapse
ATT: want security ,buy new phone
Att and moto did the same thing with the moto X 1st gen.
BTW, moto X 2014 is barely 1 year old flagship ( even younger than Galaxy S5 and LG G3)...6months ago, people paid 499 for the X and Motorola is still selling it now.
I read somewhere that Netherland's consumers filling lawsuit against SamSung for not updating that Galaxy S2/3??? Lol. I hope same thing happens to Att and MotoLenovo.
wangminh12 said:
ATT: want security ,buy new phone
Att and moto did the same thing with the moto X 1st gen.
BTW, moto X 2014 is barely 1 year old flagship ( even younger than Galaxy S5 and LG G3)...6months ago, people paid 499 for the X and Motorola is still selling it now.
Click to expand...
Click to collapse
FYI, The Moto X 2014 was released in September 26, 2014 as per this press release; it's more than One Year Old. The Moto X 2015 (Style & Play) was announced in July 2015 & released between August and September 2015, replacing the 2nd generation Moto X.
End of Life @ AT&T has nothing to do with Motorola's continued sale of the device.
I read somewhere that Netherland's consumers filling lawsuit against SamSung for not updating that Galaxy S2/3??? Lol. I hope same thing happens to Att and MotoLenovo.
Click to expand...
Click to collapse
Yes, there is a lawsuit in the works in the Netherlands pertaining to recent Samsung devices only, not devices as old as the S2/3.
Had a conversation with AT&T after ATTCares directed their DMs on twitter there:
AT&T: Hello! How may I help you today?
Brett: Hello! My name is Brett. I hope you are having a great day! How may I help you today?
Me: Been instructed to chat with one of y'all via the @ATTCares twitter account.
Brett: Sounds good to me How can I assist you?
Me: Have a Moto X2/ X 2014/X 2nd Gen, which is SIM Unlocked & already out of warranty that was recently bought second hand. Require the bootloader to be unlocked. Motorola's site states that the carrier is restricting the unlocking via their site, so is there a form or some kind of consent that AT&T can forward to Motorola to bypass this restriction?
Brett: Right! So AT&T's phones are locked at the time of purchase. but you can process an unlock on att.com/deviceunlock which will process the device itself to be unlocked from the carrier and usable with other carrier's SIM cards
Me: As stated, the device is already SIM unlocked. Bootloader is completely different.
Brett: Gotcha! Give me just a moment to check into that process for you
Me: Sure.
Brett: Alright so AT&T does not actually support unlocking the Bootloader. You can factory reset the device to load the default software.
Me: That doesn't help me at all. This device is owned outright (no subsidy remains on it), and as its owner, there should be no restrictions on the device as the obligation to the provider has lapsed.
Brett: I can definitely understand that, however AT&T does not support those therefore we would not be able to unlock that for you
Me: The device is out of warranty as well, so there is no chance of any warranty service at this point on it.
Me: Is there a link/page on your site that specifically states what you are stating here?
Me: Would like concrete clarification, moving forward.
Brett: Currently I am not showing any specific Esupport articles on the Bootloader and I do understand that I am checking to find the proper article to help you with this matter
Brett: https://www.att.com/global-search/s...st=FALSE&tabPressed=FALSE&q=bootloader#!/All/ There is Multiple Forums on the subject however and our policy and procedures to prevent us from doing that process for you.
Me: As a app developer, this is quite restrictive. As the device is owned outright & out of warranty, it is not consumer-centric to restrict what can and cannot be done to the handset. Especially since there is no expectation of Marshmallow on this particular handset. Despite its young age, AT&T doesn't seem to be allowing it to get the OS upgrade.
Me: Sending a search for the Bootloader is not providing a clear Company Issued Statement on this matter.
Brett: I do apologize for that, Software updates are sent to the provider and then the provider send those out to the devices capable for them.
Me: Had already did the appropriate searches on AT&T's site for this info.
Me: All global versions of the Moto X 2014 have received or are receiving Marshmallow, other than AT&T and Verizon variants. Verizon has made the concession and allowed users to unlock their bootloader, but AT&T remains the restrictive provider here.
Brett: Using that search, there is not any article pertaining to that subject.
Me: Guess, getting a Consumers' Rights Association involved in possible legal action is the next logical step for any user that has a fully owned device that is out of warranty.
Brett: While there are no legal repercussions for customers who choose to root their devices, AT&T does not support rooting devices, nor do our partner OEMs. In addition, rooting a device is a violation AT&T's wireless terms of service.
Me: Rooting has nothing to do with unlocking the bootloader.
Me: AT&T hasn't made a clear statement pertaining to OS upgrades for this device. It is globally upgraded thus far as well as domestically (the Pure Edition is already on Marshamallow), so what is the holdup via AT&T?
Brett: The Bootloader is there to keep the device from using unrecognized versions of Android that have not been approved from the carrier.
Brett: As for what is currently preventing that measure, I would not know if there is any plans for that device currently
Me: Where is the Company Statement to this?
Brett: The source of my information on this matter is from the Internal policies and procedures.
Me: Alright, thank you for walking the company line. Guess developers are not welcome on AT&T. Duly Noted.
Click to expand...
Click to collapse
As with the OP's convo, AT&T doesn't seem to care that they are tarnishing their customer relationships due to this 'blind' objective.