Related
This seems like an internal message to T-Mobile employees.
http://mobile.engadget.com/2010/08/19/t-mobile-tells-reps-the-vibrant-gps-update-is-coming-soon/
cool. More info is good info.
People keep talking about samsung not updating or what not.
I hope these statements proves Samsung is trying this time. GPS fix and froyo and ill be a happy clam..
Yesssssir
Sent from my ROOTED VIBRANT using XDA App
If you squint to read the actual T-Mobile memo -- the first paragraph meant for internal consumption, not the quoted line to be given to customers -- it looks like the schedule for all end users to get the update may slip a bit past September (my emphasis):
The software update is expected to roll out beginning in September.
Click to expand...
Click to collapse
boomerbubba said:
If you squint to read the actual T-Mobile memo -- the first paragraph meant for internal consumption, not the quoted line to be given to customers -- it looks like the schedule for all end users to get the update may slip a bit past September (my emphasis):
Click to expand...
Click to collapse
They say that because OTA updates are rolled out in stages. If they pushed a large update to everyone on their network, the network would bog. Also, this is to make sure the update is tested in "packets" of people, so if there is a problem with the update, only 1 percent of your user base will be affected.
OTAs usually take 2-3 weeks to roll out to everyone. So that is why they say "beginning"
MMcCraryNJ said:
They say that because OTA updates are rolled out in stages. If they pushed a large update to everyone on their network, the network would bog. Also, this is to make sure the update is tested in "packets" of people, so if there is a problem with the update, only 1 percent of your user base will be affected.
OTAs usually take 2-3 weeks to roll out to everyone. So that is why they say "beginning"
Click to expand...
Click to collapse
I understand all that quite well. Just trying to get people's expectations grounded in reality. We should pay attention to what the memo actually says, not what we wish it says.
Many folks seem to be assuming they will get a "fix" in September for sure. What they can expect is sofware to "optimize GPS performance," whatever that means. And they might not get the update until sometime in October if the rollout begins at the end of September and takes several weeks. If it begins Sept. 1, it could be sooner.
When customers are dealing with 14-day return policies from T-Mobile, these distinctions are very important.
boomerbubba said:
I understand all that quite well. Just trying to get people's expectations grounded in reality. We should pay attention to what the memo actually says, not what we wish it says.
Many folks seem to be assuming they will get a "fix" in September for sure. What they can expect is sofware to "optimize GPS performance," whatever that means. And they might not get the update until sometime in October if the rollout begins at the end of September and takes several weeks. If it begins Sept. 1, it could be sooner.
When customers are dealing with 14-day return policies from T-Mobile, these distinctions are very important.
Click to expand...
Click to collapse
Well "optimizing" is what needs to happen. The GPS isn't broken, it just doesn't work very well. If it were broken, it wouldn't work at all. It does see your general location, however the performance of locating and tracking needs to be improved. Hence it needs "optimizing".
Actually in my case and a few others, the gps doesn't work at all. Never has a lock despite how many satellites are in view and how strong the signal is.
Sent from my SGH-T959 using XDA App
op·ti·mize
Pronunciation: \ˈäp-tə-ˌmīz\
"to make as perfect, effective, or functional as possible"
-----
It's the last part of the definition that bothers me "functional as possible". If it's a hardware issue then they are probably going to try to make it as "functional as possible" on broken hardware and therefore is not really fixed. We will see....
I am using unlocked samsung vibrant but I am not on T mobile network. So will I get the update ?
mohitmoudgil said:
I am using unlocked samsung vibrant but I am not on T mobile network. So will I get the update ?
Click to expand...
Click to collapse
Not OTA. Perhaps there will be a direct dl, but you'll have to wait for it.
I heard that i9000 in other countries always update through the Samsung software ONLY,
Do we need it for vibrant too or we have OTA in US
Emama said:
I heard that i9000 in other countries always update through the Samsung software ONLY,
Do we need it for vibrant too or we have OTA in US
Click to expand...
Click to collapse
The countries that have the I9000 have a different business model than the U.S. industry has evolved. The sales of phones and the sales of cellphone service in Europe are not so strongly linked. U.S. telecoms dominate the distribution of phones, and they provide updates to the firmware OTA. So U.S. Vibrant owners can expect to get an update that way.
boomerbubba said:
The countries that have the I9000 have a different business model than the U.S. industry has evolved. The sales of phones and the sales of cellphone service in Europe are not so strongly linked. U.S. telecoms dominate the distribution of phones, and they provide updates to the firmware OTA. So U.S. Vibrant owners can expect to get an update that way.
Click to expand...
Click to collapse
so basically we dont need the KIES (?) for vibrant?
Stupid questions about this issue?
OK, I understand that things move slow in the corporate world, but someone please explain? I can understand there may be strategic reasons for releasing FroYo in dribs & drabs, but that will be to make something decent, better. But, does anyone have an opinion about the alleged GPS optimization, from the standpoint of it being ready or not? What I mean is: there's a lot of upset folks NOW because of the problem. "If" the "fix" is ready, why not release it now-ish? Does the target date mean that they're hoping against hope that someone in-house will figure it out by then? I'm sure a developer who knows inner workings of development teams can explain why? I guess the disconnect is: if the fix is ready, and they know approximately when it will be released, are they just doing testing between now and then? How many people times how many times a day times how many days or months does it take to "test" it prior to release? Just asking...
Emama said:
so basically we dont need the KIES (?) for vibrant?
Click to expand...
Click to collapse
That is correct.
i just called tmobile they said the gps fix is coming out in september
wbexpress said:
OK, I understand that things move slow in the corporate world, but someone please explain? I can understand there may be strategic reasons for releasing FroYo in dribs & drabs, but that will be to make something decent, better. But, does anyone have an opinion about the alleged GPS optimization, from the standpoint of it being ready or not? What I mean is: there's a lot of upset folks NOW because of the problem. "If" the "fix" is ready, why not release it now-ish? Does the target date mean that they're hoping against hope that someone in-house will figure it out by then? I'm sure a developer who knows inner workings of development teams can explain why? I guess the disconnect is: if the fix is ready, and they know approximately when it will be released, are they just doing testing between now and then? How many people times how many times a day times how many days or months does it take to "test" it prior to release? Just asking...
Click to expand...
Click to collapse
Now-ish is a month. The bug fixes that will be rolled into the update are done and the final update packages are being compiled and tested (dont want OTA Bricks now do we?) and being sent to the carrier, this will probably take a week or two, and then the carrier will take the update, come up with a plan and implement the plan to distribute it OTA to users. This will also take at least a week to setup, then about 2 weeks to complete (OTA push).
As you said things take time in the corporate world. If the carrier is getting definite news of the update (evidence by the internal memo) they've probably received news of the update and its delivery date to them now. So a week or so till they actually receive it. With this guess, I'd say we're still 2-3 weeks at a minimum out till the update is 'out', which is beginning/mid Sept, and that is if there are no snags.
tissimo said:
Now-ish is a month. The bug fixes that will be rolled into the update are done and the final update packages are being compiled and tested (dont want OTA Bricks now do we?) and being sent to the carrier, this will probably take a week or two, and then the carrier will take the update, come up with a plan and implement the plan to distribute it OTA to users. This will also take at least a week to setup, then about 2 weeks to complete (OTA push).
As you said things take time in the corporate world. If the carrier is getting definite news of the update (evidence by the internal memo) they've probably received news of the update and its delivery date to them now. So a week or so till they actually receive it. With this guess, I'd say we're still 2-3 weeks at a minimum out till the update is 'out', which is beginning/mid Sept, and that is if there are no snags.
Click to expand...
Click to collapse
Fair enough. I just needed to vent
tissimo said:
Now-ish is a month. The bug fixes that will be rolled into the update are done and the final update packages are being compiled and tested (dont want OTA Bricks now do we?) and being sent to the carrier, this will probably take a week or two, and then the carrier will take the update, come up with a plan and implement the plan to distribute it OTA to users. This will also take at least a week to setup, then about 2 weeks to complete (OTA push).
As you said things take time in the corporate world. If the carrier is getting definite news of the update (evidence by the internal memo) they've probably received news of the update and its delivery date to them now. So a week or so till they actually receive it. With this guess, I'd say we're still 2-3 weeks at a minimum out till the update is 'out', which is beginning/mid Sept, and that is if there are no snags.
Click to expand...
Click to collapse
To add on to this, it is easier to add the "optimization" to the already planned update then to release two separate updates. You reduce the load on the network, reduce the chances of OTA bricks, reduced complaints of multiple updates (most users don't like to spend time worrying about that), less overhead of testing and planning each update. It's a lot different than the modding community where we can just say "I'm not responsible for what happens. At your own risk...blah blah blah."
I'm getting kinda frustrated by the lack of information I'm finding on this. I got a T-Mobile Tab for Christmas; I noticed there's no Software Update option in Settings. After some digging, I find in the Samsung User's manual (for the T-Mobile variant) that updates will be through Kies Mini, and that Kies is available on samsungapps.com. That site tells me that Samsung Apps are not available in the US. So after more digging, I find the Kies Mini app, install it on my netbook and fire it up. After switching from ADW back to the TouchWiz launcher to get Kies to recognize my device, it still says that my Tab is not supported for firmware updates.
If there's something I'm missing, please let me know. I understand that there's probably no official updates available yet anyway, but this is something I need to sort out before my 30 return period is up. I do not want to get stuck with a device that is going to be this much of a hassle to update, not to mention CES is in a couple weeks, and I know there's going to be many more, much more well-featured tablets being launched.
Thanks in advance guys and gals.
As that are no known issues with the tab at this time you can expect no updates for quite some time. The first and possibly only update will come if the go with the gingerbread update, if samsung provides it. This is a good mindset to be in if you don't want to get dissapointed later. I have the tmo tab and have gone with jmc eufopean firmware. If I am stuck here forever I will still be satisfied.
scottprotege said:
As that are no known issues with the tab at this time you can expect no updates for quite some time. The first and possibly only update will come if the go with the gingerbread update, if samsung provides it. This is a good mindset to be in if you don't want to get dissapointed later. I have the tmo tab and have gone with jmc eufopean firmware. If I am stuck here forever I will still be satisfied.
Click to expand...
Click to collapse
Well, I'm used to being disappointed when it comes to updates... I own a Droid X I would expect, however, there to be maintenance updates. With there being several unofficial firmwares floating around out there, you can't ignore the fact that Samsung is at least working on a bug fix update. I'm not really wondering WHEN I'll be getting updates, so much as HOW I'll be getting updates. Just frustrates me to no end that I haven't yet even found a way for my device to check to see if there's an update available. I don't care that there isn't one, just want to know how to get it when there is.
/rant
Like your experience, I had to hunt for Kies and after installing it discovered it said I had an unsupported device. I checked with T-Mobile and was told not to use Kies at all, but that any updates will come over the air instead. No need to "check in" like I did before this device, but it will just appear as a system notice when it is time. He didn't say, and I didn't think to ask at the time, whether the updates will come from T-Mo, Google, or Samsung, but maybe that doesn't really matter, any that are due will just appear.
At least your tab can do ota
Sent from my HTC Wildfire using XDA App
So according to this the Verizon Nexus 6 will come with 5.1 Lollipop. Does this mean that Motorola will rollout Lollipop to the DT around this time? And will it be 5.1 Lollipop?
Verizon's Nexus 6 could arrive very soon http://www.engadget.com/2015/02/27/verizon-nexus-6/ via Engadget Android
Update: Its been confirmed that the Nexus 6 will drop on Verizon tomorrow and with 5.1 Lollipop. No word on a locked down BL though.
Google's Nexus 6 will finally reach Verizon on March 12th http://www.engadget.com/2015/03/11/google-nexus-6-for-verizon/ via Engadget Android
While the Nexus 6 has been confirmed to have 5.1, no word has been given about the DT being upgraded to 5.1 or any other version of Lollipop as of yet.
So according to what?
Sorry forgot to attach the link - OP updated
I'm hoping we are updated by then, but I seriously doubt that it will be 5.1, most likely 5.0.2 which has been cycling through the Moto line.
kingersj1 said:
I'm hoping we are updated by then, but I seriously doubt that it will be 5.1, most likely 5.0.2 which has been cycling through the Moto line.
Click to expand...
Click to collapse
5.1 is already out for limited devices. We may get 5.1 after all said and done
True, we most likely get 5.1, I just don't think this update. Most likely the next update, which should be faster once we are on lollipop.
GreaterLesser said:
So according to this the Verizon Nexus 6 will come with 5.1 Lollipop. Does this mean that Motorola will rollout Lollipop to the DT around this time? And will it be 5.1 Lollipop?
Verizon's Nexus 6 could arrive very soon http://www.engadget.com/2015/02/27/verizon-nexus-6/ via Engadget Android
Click to expand...
Click to collapse
Motorola wont roll out anything the update will come from Verizon not Motorola.
sinclac said:
Motorola wont roll out anything the update will come from Verizon not Motorola.
Click to expand...
Click to collapse
lol! Nope... Verizon just approves the Update.. Rest of the work is done by Motorola! IF you look at the Logcat you will see the link from where the Update is downloaded off n its the Motorola Servers...
Gundabolu SC said:
lol! Nope... Verizon just approves the Update.. Rest of the work is done by Motorola! IF you look at the Logcat you will see the link from where the Update is downloaded off n its the Motorola Servers...
Click to expand...
Click to collapse
Keep dreaming, that update will come from Verizon just like all updates before, Verizon gets the update bloats the hell out of it and then releases it.
sinclac said:
Keep dreaming, that update will come from Verizon just like all updates before, Verizon gets the update bloats the hell out of it and then releases it.
Click to expand...
Click to collapse
Nope... U think Verizon sits n adds bloat n release the software? Nope.... They give the apps that need to be added to Moto's software Developers... the Verizon framework is allover the System partition on the turbo, so its not just adding a bunch of apps its integrated deep... Then Motorola makes loads of builds with one build a day n test the siftware on prototype phones... Once they feel the software is stable enough then send it to Verizon for approval... If Verizon is not satisfied with the bloat, they reject it and Motos gotta start adding the bloat n test it out again...
Not holding my breath on any updates soon on the Turbo. This phone has been out for over half a year now with nothing in the works. For a near stock phone I'm not sure why it's taking a back seat to all of these other devices that are getting Lollipop. So much for my decision to go with a Motorola device because of a so-called quick update schedule.
m4rk0358 said:
Not holding my breath on any updates soon on the Turbo. This phone has been out for over half a year now with nothing in the works. For a near stock phone I'm not sure why it's taking a back seat to all of these other devices that are getting Lollipop. So much for my decision to go with a Motorola device because of a so-called quick update schedule.
Click to expand...
Click to collapse
Nothing in the works eh? So there have been NO updates then?
Oh and its been 4 months, but what's rounding it up by another two gonna hurt? It makes it more dramatic.
Everyone wants Lollipop, but doesn't care that it is less stable than Kitkat. Lollipop is just another ICS repeat. ICS didn't start becoming truly stable until 4.1, which Google for some reason deserved a name change. It took forever for devices to update to ICS, and by the time some did, Jellybean was out. Lollipop is a full point release, and major Android overhaul. This is not a 4.0 -> 4.1 -> 4.3 -> 4.4 transition. This is a 4.4 -> 5.0 transition and major parts of Adroid have been reworked. It isn't just a theme. It hasn't been a smooth launch. Verizon is strict with their testing, and we all know that. They are not going to let an OS less stable than its predecessor pass testing on one of their flagship devices. Despite what you want to believe, the Turbo is their specific flagship and they will want it to be the most stable.
Hey, I want Lollipop too. However, Im willing to take the instability with it. Verizon apparently is not after seeing how it fared on the X. The truth has always been out there, no matter how much people want to ignore it: If you want the ultimate network and stability, you got Verizon. If you want bleeding edge software on your devices, you go elsewhere.
So to be frank, anyone who bought the Turbo expecting blazing fast updates should blame their own misconceptions.
You can get excited about two minor updates with imperceptible bug fixes but I'm referring to OS updates.
m4rk0358 said:
You can get excited about two minor updates with imperceptible bug fixes but I'm referring to OS updates.
Click to expand...
Click to collapse
Then you shouldn't be on Verizon. Verizon has had a few quick updates over the years, but it doesn't erase all the slow ones.
This is nothing new.
It sucks, but sometimes the bitter truth is what people need. I only stick with Verizon because I am potentially on call 24/7 and my phone at work is tied into my cell phone. I need a reliable carrier and due to where I live, where I travel, and where I work, Verizon is the most reliable.
adrynalyne said:
Then you shouldn't be on Verizon. Verizon has had a few quick updates over the years, but it doesn't erase all the slow ones.
This is nothing new.
It sucks, but sometimes the bitter truth is what people need. I only stick with Verizon because I am potentially on call 24/7 and my phone at work is tied into my cell phone. I need a reliable carrier and due to where I live, where I travel, and where I work, Verizon is the most reliable.
Click to expand...
Click to collapse
By far most reliable for me. Maybe I'm misunderstanding the concept of XLTE or how it ties in with VoLTE but since the DT had it's second VoLTE update I haven't dropped one call and with XLTE I'm on LTE 97% even underground here in Chicago. And I make a lot of calls everyday. We all want updates as soon as possible but as long as what we have works then I can wait.
Gundabolu SC said:
Nope... U think Verizon sits n adds bloat n release the software? Nope.... They give the apps that need to be added to Moto's software Developers... the Verizon framework is allover the System partition on the turbo, so its not just adding a bunch of apps its integrated deep... Then Motorola makes loads of builds with one build a day n test the siftware on prototype phones... Once they feel the software is stable enough then send it to Verizon for approval... If Verizon is not satisfied with the bloat, they reject it and Motos gotta start adding the bloat n test it out again...
Click to expand...
Click to collapse
Gundabolu is correct all Verizon does is test and certify the update. Motorola is the one to actually push it
Jweimn said:
Gundabolu is correct all Verizon does is test and certify the update. Motorola is the one to actually push it
Click to expand...
Click to collapse
Does not change the fact that Verizon releases it, then it is pushed to us.
Chicken/Egg
sinclac said:
Does not change the fact that Verizon releases it, then it is pushed to us.
Click to expand...
Click to collapse
No not at all nor does it change the fact that Verizon is slow to approve updates. I still feel this time around though that moto is being fairly slow at getting this update out but who knows
Jweimn said:
No not at all nor does it change the fact that Verizon is slow to approve updates. I still feel this time around though that moto is being fairly slow at getting this update out but who knows
Click to expand...
Click to collapse
Agreed, Verizon always seems to be the last to update.
Hey all I have a purely stock unrooted nexus 6p that I am trying to figure out why I am getting the monthly update a week before the release of the next update ever time. I am thinking its ATT blocking the updates. Can you please post the carrier, date and time when you received the May update please?
VZW and mine showed update on the 13th. Was starting to wonder when I'd see it, but it finally hit.
Still waiting here on Sprint for the update. This is taking forever.
Sent from my Nexus 6P using XDA-Developers mobile app
I have Project Fi and get my updates rather late too. It's not just you.
If you really want the update, then by all means flash it manually as soon as it comes out.
I don't think that the carrier can actually block the update, unless you somehow bought the 6P carrier-branded, and through the carrier. That being said, I've been on Tmo, Fi, VZW, and Straight Talk, and I have never actually received a monthly security update as soon as they are released. Usually I had to wait a couple of days. I think those updates roll out randomly, so I'd say just keep waiting, or flash it yourself.
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Yes I know I can side load the update. That is not the point of this post. Its to get an idea of timing of when people are getting the updates and what carriers they are on.
Google releases there updates in a phased approach. They first release it to 1% all the way up to 100%. 100% should be getting the update within 2 - 3 weeks. The 2 -3 week period I have yet to see!
What I was trying to determine is if this is the carriers blocking the updates till a specific time or its google just not pushing updates to the phones like they say they are.
Note ATT is notorious for blocking updates. And yes they can block the update as long as your using there network to check.
If Google is releasing security updates on a monthly bases and you don't get it before the next update is released, whats the use in a monthly update???
brichardson1991 said:
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Click to expand...
Click to collapse
How do you side load. I just saw that google has released images to do that. I too have a 6p completely stock. I want to keep the bootloader locked. I have never had a nexus device before. So this is new to me I always used Samsung. The problem with Samsung is you have to mod the hell out of it. this phone just works like it is supposed to. but I do want to try to update manually. So I followed the instructions in the general section and I am installing the sdk as we speak. So what is the process for side loading and where do I get the update? My phone gets its updates really late in the month and I hate waiting. Also I booted this phone into recovery and tried to do a factory reset but it didn't do it and there were all these options I am not used to. How do I do a basic factory reset from recovery? I would like to know just in case. I am not wanting to go crazy with this phone but I do want to understand it so when I get the nexus 7 I can play with this one when I get spare time.
Went through many news and YT videos, they are claiming that we will get Oreo 8.0 update till the end of this month i.e., May'18.
Can anyone verify this more accurately?
By the way I don't oreo update from Motorola/Lenovo since when we have XDA.
Using AEX ( Thanks @ishubhamsingh for the awesome work) from a long time.
While commenting mention your ROM too.
Anything other than official updates should be ignored. Other sources usually have no proof and are pretty much just clickbait.
Still waiting
Got the May OTA security update via TMO today. Still no Oreo.
I am inclined to believe that our phones will not be getting Oreo, ever. Motorola's strategy seems to be to kick the can down the road until they can say our phones are "no longer supported." They've left us at the side of the road for dead.
Eventually, when I get a replacement for this phone, it will not be a Motorola.
bikergeek1553 said:
Got the May OTA security update via TMO today. Still no Oreo.
I am inclined to believe that our phones will not be getting Oreo, ever. Motorola's strategy seems to be to kick the can down the road until they can say our phones are "no longer supported." They've left us at the side of the road for dead.
Eventually, when I get a replacement for this phone, it will not be a Motorola.
Click to expand...
Click to collapse
May update? What device are you on? So far I've seen people on either March or April update plus some rare cases where some haven't received even earlier OTAs
psychopac said:
May update? What device are you on? So far I've seen people on either March or April update plus some rare cases where some haven't received even earlier OTAs
Click to expand...
Click to collapse
Moto G5 Plus/potter. I just got a security update today, is that not the May security update?
bikergeek1553 said:
Moto G5 Plus/potter. I just got a security update today, is that not the May security update?
Click to expand...
Click to collapse
The month will be mentioned in the changelog. Just tap the update notification and you'll see which month's security update you've received. Let me know
psychopac said:
The month will be mentioned in the changelog. Just tap the update notification and you'll see which month's security update you've received. Let me know
Click to expand...
Click to collapse
Says "April 1, 2018." Silly me, I thought that I'd get a May security update in May.