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."
Well apparently the End of September has come and gone. So my questions is this, When will we get any update? I say end of October for the minor update and November for 2.2. Oh and guess what, T-Mobile UK missed their deadline for 2.2:
http://phandroid.com/2010/09/30/t-mobile-uk-misses-end-of-the-month-window-for-galaxy-s-froyo/
Amazing phone Samsung. ..yet this is just another thread of disappointment.
yep,
Either Samsung, Tmobile, or both really let us down
I say Samsung..since it's not their first time...but then again T-mobile don't have a good history either...looks like both.
Why blame everything on Samsung? Give me one good helluva reason. While they should probably deserve partial blame, T-Mobile makes the final call. If T-Mobile says no, then we don't get the update. Simple. Oh, one more thing, T-Mobile UK != T-Mobile USA.
I have no idea what the hell is going on with T-Mobile on releasing updates, but if it's quality over speed, then I will gladly wait unlike most people.
I'm angry at T-Mobile for not giving us any of the possible updates that Samsung made. It makes no since that the Vibrant has been out the longest in the states and hasn't had a single OTA.
I blame Samsung for lack of Froyo. If they can make it run on the tab, they can make it run on the phones. I can't be mad a T-Mobile for that considering no Galaxy S phone has an official Froyo update on it yet.
I wonder what's taking so long, the Tab is basically an 'oversized' Galaxy S (relatively speaking here). If it is working on the Tab it shouldn't take much to port it to the phones.
unless of course, it is held out on purpose so it would not cannibalize the sales of the Tab. Purely my guess.
Its not so bad that its late, its that T Mobile and Samsung haven't kept us updated. A small status or progress update would go a long way.
clivo360 said:
Its not so bad that its late, its that T Mobile and Samsung haven't kept us updated. A small status or progress update would go a long way.
Click to expand...
Click to collapse
Second that
Do you not think them saying an OTA will be available soon, is keeping you posted? It was probably pushed back after that clusterfuck of an OTA for the Captivate.
I believe Samsung is full responsible of this situation.
Is not a secret that Samsung lacks on software support. Take the European Galaxy S the unlocked version. The devices came months before the Vibrant in the US and suffers the same stupid TouchWiz bugs and never got an update...
I believe we will be lucky if we see Froyo when Android 3.0 is available. (of course whoever still has a Vibrant by then).
For me that was my first and probably last Samsung device. Its a nice device but FULL of bugs with no a single sign of support... A complete let down for this high class hardware.
Imagine if we go.straight to 3.0?
Sent from my SGH-T959 using Tapatalk
iwillkillyou said:
Imagine if we go.straight to 3.0?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
We will be lucky if we even get 3.0
Samsung has managed to bork every single update for every US Galaxy S device. Even when they hit the deadline with the Captivate, it didn't fix the issue everyone wanted it to fix. Then, they release the update on other networks, only to tell people "Whatever you do - DON'T download this!". It's a joke.
Guys, relax! Samsung has been telling us that the update is coming "soon" for the past two months, so it's coming "soon"! In other news, the unemployment rates will go down to their normal levels "soon" as well!
/sarcasm
Yeah, its disappointing that the update has taken so long, but nothing to cry over yet imo.
Sent from my SGS Vibrant.
Honestly we should have all expected this after how they handled the behold 2. I felt that a phone that was on all the major carriers would get tons of support, but alas....
Phone didn't work right on launch so bottom line it's samsungs fault.
Agreed
Sent from my SGH-T959 using XDA App
I got my update via Kies!
Now I wait for 2.2 LOL
This is what EVERYONE who had bought a Beyond, or other Samsung phones kept saying...
Basically that Samsung either breaks their promises, or doesn't deliver on them until way late.
I am going to start looking for a new device. This 2.1 phone should hold me over until the 3.0/Gingerbread devices start coming out.
I am not upset enough to avoid Samsung in the future, but HTC and Motorola will be my first choices.
nMIK-3 said:
I believe Samsung is full responsible of this situation.
Is not a secret that Samsung lacks on software support. Take the European Galaxy S the unlocked version. The devices came months before the Vibrant in the US and suffers the same stupid TouchWiz bugs and never got an update...
I believe we will be lucky if we see Froyo when Android 3.0 is available. (of course whoever still has a Vibrant by then).
For me that was my first and probably last Samsung device. Its a nice device but FULL of bugs with no a single sign of support... A complete let down for this high class hardware.
Click to expand...
Click to collapse
Never going to buy a Samsung phone again.
Sent from my Samsung Vibrant Galaxy S
There's been a lot of speculation about just how Nexus-like the Galaxy S4 and HTC One Google Play edition phones will be, particularly from a technical / software update standpoint. Now, we have some relatively concrete information that sheds light on these issues.
First and foremost, Google will not directly handle software updates for Google Play edition devices. This has been reported as true, false, and generally disputed quite a lot in the lead-up to the launch. We know for a fact now (thanks to Anandtech) that while Google will supply the necessary Android builds to OEMs, the OEMs will be responsible for maintenance of kernels and all the various drivers and firmware pieces necessary for their specific device. The result is that Google gives the OEMs the Android build, and it's then up to the OEMs to make that build work on their Google Play edition device and perform the act of actually updating the phone. Google has issued an official statement that works very hard to not expressly deny that they won't be handling the updates (Droid-life):
What's this mean for you? It means that at the end of the day, the onus to update these phones will still be on Samsung and HTC. They will be able to circumvent the carrier certification runaround, and will in theory have much less work to do in maintaining these devices, but the responsibility still falls to them, not Google. This could mean any number of things. It could mean these phones will get updates within days of their Nexus counterparts. But more likely weeks, and possibly even months depending how much attention these phones are actually given by HTC and Samsung. I wouldn't say months is what we should expect, but I'm also saying such a gap is entirely within the realm of possibility. You have to remember, these phones will sell in miniscule quantities compared to their skinned brethren, and that means they aren't as high up on the value chain for software update attention. While it's certainly worth being optimistic about the update process, there's still plenty of reason to temper those expectations until we see these devices receive their first major Android release update.
he second thing we've learned is that Google will not host factory OS images for Google Play edition devices (see JBQ's post on this topic here). This will be up to Samsung and HTC, if they choose to do so. Google will also not be hosting any proprietary binaries (essentially, drivers) for these phones (again, see JBQ). Release of any binaries is, once again, up to Samsung and HTC. Taken together, all this information - as you may already have guessed long ago - means there is very little chance we'll ever see these phones supported in AOSP. It's not impossible, but it is extremely unlikely.
So there you have it: that's basically the nuts and bolts of what doesn't make the Google Play edition HTC One and Galaxy S4 Nexuses. Does this put a damper on the situation, or is it immaterial? Let us know in the comments.
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
welp this sucks !
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
H-Streety said:
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
Click to expand...
Click to collapse
Since we will probably be on 4.2.2 for a while you're going to be waiting.
Sent from my HTC One using Tapatalk 2
Possibly, but I am not losing my IR blaster and camera app for half-supported stock Android. If HTC will push out the update within a week or two after it comes out for Nexus devices, then I will definitely flash it, if not then I don't see the point of it. I would rather do S-OFF + Super Cid and still enjoy all these things than losing too many good things for basically just stock Android.
Nexus Experience Device not Nexus Device
That's really unfortunate.
Pretty ridiculous actually.
-Sent from Marino's One-
Did you really expect more? Google never said they would be Nexus devices or supported by AOSP. They are Nexus "Experience" devices... hence they offer the same feel without being the same.
Sorry to burst your bubble.... that said I think there will be dedication on the part of HTC and Samsung to get updates.. there isn't any excuse and you know if the device is on Google Play then el'Goog will be pressuring them to not delay
Sent from my Nexus 10 using Tapatalk HD
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Zero timeline given. It will get it. The second it's released? No. A month after? Maybe.
Yep, OP...sure this is stock AOSP, but if anyone thinks the S4 and One will be updated the instant the Nexus line is, they are smoking some serious ****.
Samsung and HTC still have a role in this, ala Verizon (CDMA) Galaxy Nexus. It will slow things down. It's on HTC and Samsung to instantly update their proprietary apps to play well with AOSP. We've all seen that movie before, now have we?
Sigh. Can of worms. I called it. Once you integrate manufacturer specific features into AOSP (Beats, Zoe, etc) it WILL slow down the instant (expected) release of AOSP to "OMG PURE GOOGLE) phones. Psst: they aren't Nexi.
Just deal with it. I cringe for the blasting posts from those who got the One/S4 AOSP editions once the newest Android OS is pushed out...to the Nexus line first.
I see it now:
"THE NEXUS 4 JUST GOT 5.0. WHERE IS MY KLP ON MY ONE/S4 GOOGLE!??? PETITION STARTED!!!!1111"
And so on. Grabs popcorn.
Edit: thought I'd paste in a quote I just read that summarizes this situation quite well:
I don't see the point of these devices anymore. You lose out on the few customization that OEMs provided that weren't useless (fully functional Beats, camera software, improved text messaging and browser apps, etc.) for a vanilla experience that is nearly indistinguishable from the OEM version running a custom launcher. And no guarantee of fast updates.
You'd have to be a dummy to buy these phones from the Play store.
Thankfully I have an unlocked T-Mobile One. I'll just use it or flash whatever, whenever. Paid $450 for it and am very happy with my gamble.
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version. I believe that more that others guessing about it.
Click to expand...
Click to collapse
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
BarryH_GEG said:
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
Click to expand...
Click to collapse
google is the only one who can update aosp devices..nobody else
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
david279 said:
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
you are a thick one aren't you lol
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
The first post says it isn't an AOSP device, Google isn't managing the proprietary drivers, they aren't posting the s/w images, and they aren't responsible for pushing out updates. So your statement is true; for Nexus devices. "Play Edition's" aren't Nexus devices.
The fact that it doesn't say the below which Google says about their devices probably means what OP posted is true.
M
Argenist said:
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
Click to expand...
Click to collapse
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands for resale and every day use. Hint. It isn't the Google or Dev one.
Unlock it for $7 and never look back.
Sent from my HTC One using Tapatalk 2
ericshmerick said:
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands. Hint. It isn't the Google or Dev one.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Understood, but would matter then to get the GE version over the Dev?
Argenist said:
Understood, but would matter then to get the GE version over the Dev?
Click to expand...
Click to collapse
They don't ship until July 9 so no one knows.
Sent from my HTC One using Tapatalk 2
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
Not true..
This situation has been done before. The OG Droid (Sholes) was not a Nexus but ran vanilla software. Updates came but abit later. They came from Motorola.
Sent from my HTC One using Tapatalk 4 Beta
I'm still thinking about getting this phone and wondering how fast Motorola will be with their updates. Being that they are owned by Google, it's kind of baffling to me that it ships with 4.2 instead of 4.3 right about of the box.
And with 4.4 on the horizon, I'm not expecting it to be updated like a Nexus device but hoping they won't drag ass and take forever and a day. This would be my first Motorola device and I've heard about them being terrible with updates in the past but that was before Google bought them out.
Unless someone here can tell the future....
Sent from my XT1058 using Tapatalk 4
Someone with an inside source said that their timetable for releases is 2 months after a new version is released.
Part of the requirements for the purchase of Moto was that they couldn't receive any special treatment when it came to code release from Google. Which means that they don't get the source code for new versions before any other vendor unless they have been chosen to build a nexus device. I that case they can only work on it in connection with the Google Android team.
The two month timetable isn't assume h that has been officially confirmed, so it may not be completely accurate.
Sent from my XT1058 using Tapatalk 2
I've read a few articles which mentioned that although Motorola is now owned by Google, they are in fact keeping a "firewall" between the two companies. This could explain why the Moto X was released with 4.2 instead of 4.3.
Also, based on what I've seen in recent trends, carriers will be releasing Android OS updates over the air as opposed the Motorola (at least here in the States). Some approach OS updates better than others. Verizon is known to take their time releasing updates to phones because of the extensive testing they do with an upcoming update for a particular device. Take for instance the Droid DNA, a device released close to the end of last year which is only now getting the update to 4.2 from 4.1. I sincerely hope the Moto X does not see such neglect when it comes to future updates but I also wouldn't be surprised.
Over the years I have learned one thing. If it's not a nexus, expect the absolute worst case scenario for ROM updates.
with the ability to flash roms coming soon this may not matter
Sent from my XT1058 using XDA Premium 4 mobile app
scorpion667 said:
Over the years I have learned one thing. If it's not a nexus, expect the absolute worst case scenario for ROM updates.
Click to expand...
Click to collapse
I'd like to believe that Moto offers better support than Samsung and HTC. The 4.3 update is still in the works but hard to put an eta on it as they probably still need time to make sure the moto apps and hardware is optimized to work properly. Other than improved performance and stability, I'm not missing anything by using 4.2.2 for now.
One good thing this phone has going for it is it's pretty much stock Android. No Touchwiz, Sense or any other overlay like Motoblur. This means it should be easier and faster to update since they just have to get the few things working on the next version. I wouldn't be surprised if Motorola skipped 4.3 and went straight to 4.4 since it's close to being released.
housry23 said:
One good thing this phone has going for it is it's pretty much stock Android. No Touchwiz, Sense or any other overlay like Motoblur. This means it should be easier and faster to update since they just have to get the few things working on the next version. I wouldn't be surprised if Motorola skipped 4.3 and went straight to 4.4 since it's close to being released.
Click to expand...
Click to collapse
The problem isn't necessarily the skins though; it's the US carriers.
NoNameAtAll said:
The problem isn't necessarily the skins though; it's the US carriers.
Click to expand...
Click to collapse
This. If it's going to take moto two months, expect longer because it will need to be blessed by the carriers before OTA updates are pushed out.
I wonder where the T Mobile X fits in then... Will it be updated straight from Moto? If not that might be a big problem because T Mobile obviously doesn't even support the phone.
NoNameAtAll said:
The problem isn't necessarily the skins though; it's the US carriers.
Click to expand...
Click to collapse
You're right. I actually had a big long post about how once Motorola gets the code, implements their features, at&t still has to test it and approve. Hopefully, since it's basically stock android, it won't take as long because the skinning process doesn't have to happen.
Sent from my XT1058 using Tapatalk 4
Motorola has a very mixed record so far with their updates. The OG Droid was actually quite good at getting updates in a timely manner and only trailed the Nexus by a few weeks. After Motorola switched to Blur though for all their devices they lagged behind by a few months and even though with Jelly Bean they removed most of the Blur apps in favor of stock, that was still nearly what 9 months after 4.1's source was released before the Razr, Bionic, Droid 4 all got it. In fact for a while there they were one of the slowest at releasing their updates.
Now the Moto X is a new beast though and different from what Motorola has done now so it's hard to say. All the previous devices were part of the "old motorola" and the X is the first device of the "new motorola". The X is almost pure stock so there is very little tweaking that will need to be done. They just need to add in support for their Camera App, Active Display and Touchless Controls, do any kernel updates/bug fixes and then test/resolve any new bugs that popped up in 4.3. Motorola has said that an update is in the works and will come out soon with many improvements for the Moto X. Is this 4.3 or just a newer 4.2.2 build? We don't know.
I'd like to imagine that we will see 4.3 released sometime between now and early October on all carriers considering Samsung announced they will begin to roll out 4.3 to the SGS4, SGS3 and Note2. If Motorola is the first to release a stable, solid build of 4.3 for their new X8 devices and continues to keep up with their updates in a quick and timely manner, it would do a lot to rebuild their name. Right now we just have to wait and see if Motorola is serious about getting better about releasing timely updates or not.
clankfu said:
I'm still thinking about getting this phone and wondering how fast Motorola will be with their updates. Being that they are owned by Google, it's kind of baffling to me that it ships with 4.2 instead of 4.3 right about of the box.
And with 4.4 on the horizon, I'm not expecting it to be updated like a Nexus device but hoping they won't drag ass and take forever and a day. This would be my first Motorola device and I've heard about them being terrible with updates in the past but that was before Google bought them out.
Click to expand...
Click to collapse
I'm in contact with Punit Soni (Moto X product Manager). He's very active on Google+ and he addressed the update and OTA of 4.3 questions. He said when they officially released the device to distributors, 4.3 just got announced. So it was either delay the Moto X and piss off many pre-ordering customers, or continue with the primary plan and push through with 4.2.2.
He said the update is "Coming soon" as they always say, and he promises many fixes like Camera improvements, Picasa or Google Photos sync for Gallery, and OS 4.3 very soon.
"When will then be now? Soon!"
EDIT: wrong thread.
linuxgator said:
Part of the requirements for the purchase of Moto was that they couldn't receive any special treatment when it came to code release from Google. Which means that they don't get the source code for new versions before any other vendor unless they have been chosen to build a nexus device. I that case they can only work on it in connection with the Google Android team.
Click to expand...
Click to collapse
Each OEM gets the source at the same time. Makes no difference. The only reason it takes so long is a mixture between putting loads of framework in. And wanting to get new hardware out.
Moto, working with next to stock android, will be much much faster. No they dont get special treatment per se. But time will be light speed compared to HTC and Samsung
Sent from my XT1058 using XDA Premium 4 mobile app
GR36 said:
But time should be light speed compared to HTC and Samsung
Click to expand...
Click to collapse
FIFY
If it goes the way the Tmobile nexus 4 goes than it will be updated right away. My son has the nexus4 bought directly from Tmobile store & it receives updates along with those bought directly from Google. I know its still a nexus and the moto x isn't but from what I understand the Tmobile version of the x doesn't have any carrier installed stuff on it, so hopefully it will be treated as a device like the Google editions.
Sent from my GT-I9505G using xda app-developers app
hey everyone
I opened this thread to discuss with you the ETA of grace ui to Note5 .
where do you think it will be available according to sammobile they said that it should be available in august august which almost finshed .
will it be available with android N ,what do you think ?
AlMaghraby said:
hey everyone
I opened this thread to discuss with you the ETA of grace ui to Note5 .
where do you think it will be available according to sammobile they said that it should be available in august august which almost finshed .
will it be available with android N ,what do you think ?
Click to expand...
Click to collapse
Don't hold your breath...
From my non-rooted AT&T Galaxy Note 5 (N920A)
I'm not holding my breath on seeing N on the note 5 until next year. Even if the Note 7 gets it (i heard a rumor Samsung was talking smack about an N update for it in the first 3 months) i don't know we can count on anything faster than historically demonstrated when it comes to any device NOT the current flagship...
Sent from my SM-N920T using Tapatalk
If you know the history of Samsung, you shouldn't expect anything this year.
Samsung sells the most phones out of any other manufacturer in the US, and somehow is the WORST WHEN it comes to updates. If there's no unlocked bootloader for the note 7 by the time the LG V20 is released, I'll be jumping ship to LG (and getting the nexus 6p or 2016 nexus as my side chick) LG' s are the only ones with a camera close to as good as Samsung's. And they all have unlockable bootloaders. If Samsung didn't start locking down their bootloaders I wouldn't mind the unexcusably horrendous wait times for software updates. They have a superior product for the most part. But they hardly give a craps about the customer. Just my opinion.
Mikekelso421 said:
Samsung sells the most phones out of any other manufacturer in the US, and somehow is the WORST WHEN it comes to updates. If there's no unlocked bootloader for the note 7 by the time the LG V20 is released, I'll be jumping ship to LG (and getting the nexus 6p or 2016 nexus as my side chick) LG' s are the only ones with a camera close to as good as Samsung's. And they all have unlockable bootloaders. If Samsung didn't start locking down their bootloaders I wouldn't mind the unexcusably horrendous wait times for software updates. They have a superior product for the most part. But they hardly give a craps about the customer. Just my opinion.
Click to expand...
Click to collapse
HAHA, I am sorry but, I must have a read a post like yours everytime a new Galaxy Device is released. I personally am patiently waiting for the update. I like the Note 5. I got mine alittle late in the game since they didnt release it in Europe. I would get the note 7 but, that curve screen is a no go for me. I have the S7 and trying to get a good screen protector for its slightly curved screen is hard to come by.
Anyways, I still think Samsung Flagship are the best among all smartphones and will continue to use their device.
Mikekelso421 said:
Samsung sells the most phones out of any other manufacturer in the US, and somehow is the WORST WHEN it comes to updates. If there's no unlocked bootloader for the note 7 by the time the LG V20 is released, I'll be jumping ship to LG (and getting the nexus 6p or 2016 nexus as my side chick) LG' s are the only ones with a camera close to as good as Samsung's. And they all have unlockable bootloaders. If Samsung didn't start locking down their bootloaders I wouldn't mind the unexcusably horrendous wait times for software updates. They have a superior product for the most part. But they hardly give a craps about the customer. Just my opinion.
Click to expand...
Click to collapse
I agree with your view, but Samsung might argue it that they care MORE for their customers and thus have locked the devices - to save the ignorant public from themselves- since most folks only know enough to come here, create a new login (since they forgot the old one made since the last device they rooted [or bricked]), then search for rooting instructions until they find something layman enough to follow, and finally root (or brick) their device smh lol i don't agree with that view but i can sooooooo hear some Samsung PR pencil pusher explaining it smh
"We've locked your million dollar device because we love you and want you secure......NOT because we want to shove SamsungPay down your throats!"
Kill me now smh lol
Sent from my SM-N930F using Tapatalk
Rx8Driver said:
I agree with your view, but Samsung might argue it that they care MORE for their customers and thus have locked the devices - to save the ignorant public from themselves- since most folks only know enough to come here, create a new login (since they forgot the old one made since the last device they rooted [or bricked]), then search for rooting instructions until they find something layman enough to follow, and finally root (or brick) their device smh lol i don't agree with that view but i can sooooooo hear some Samsung PR pencil pusher explaining it smh
"We've locked your million dollar device because we love you and want you secure......NOT because we want to shove SamsungPay down your throats!"
Kill me now smh lol
Click to expand...
Click to collapse
I agree. But at the same time, they could just go the HTC route. You request unlock keys from Samsung and agree to certain terms and conditions for the unlock. I'd gladly give up Samsung pay and Android pay for root. This dictatorship bull crap is ridiculous. Smh lol