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."
Related
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
As you probably know last Month that Samsung pulled-out the froyo Update files of the Samsung Galaxy S from its servers due to Many System Bugs that Made the Android froyo unstable and laggy. And Samsung UK confirmed on its twitter Status that the Froyo Update is Coming on November on its Final Version and to All Network operators and No More Delays...No More pulling-out!!
We Got Some Information that the Release Date of the Galaxy S Froyo update for USA Carriers and UK Carriers is somewhere around 11th November,2010 as a FINAL Release Date. Worldwide release will follow in few days after the Official Release of the Froyo ROM for Samsung Galaxy S, which Means that All Galaxy S users Worldwide (Include Middle-East and Arab gulf users) will get the update on November along with UK,USA Carriers too.
Froyo rolling out in UK Nov 4
So The Update is Coming Finally and NO More Delays AT ALL... More Stable... More Smoother, its a matter of time right Now. As I always say "Waiting for the froyo to come-out, better than waiting for it to load!".
http://www.youmobile.org/blogs/entry/Galaxy-S-Getting-Froyo-on-11-November-Final-Date-
To unsubscribe from these announcements, login to the forum and uncheck "Receive forum announcements and important notifications by email." in your profile.
You can view the full announcement by following this link:
http://www.samsunggalaxysforum.com/...es/final-date-for-galaxy-s-update-(nov-11th)/
Regards,
The Samsung Galaxy S Team.
Hmm. My read of the actual text that Samsung sent out is not actually any different than it was a week or so ago: the i9000 will probably have 2.2 sometime before the end of the month, along with the rest of the UK/Europe. I really don't see anything in the "official" Samsung notice that indicates Verizon, or any other US carrier.
However, since the blog posts cite "Some information" for "somewhere around 11th, November as a FINAL release date" (How's that for ambiguous, "somewhere around", but it's also "FINAL"...), I'll be guardedly optimistic.
Make that HEAVILY GUARDEDLY optimistic...
Verizon will decide when its released, not Samsung.
it says late in November for the carrier branded versions
adrynalyne said:
Verizon will decide when its released, not Samsung.
Click to expand...
Click to collapse
....Bingo!
/sigh
Sent from my SCH-I500 using XDA App
I don't care. Wait before you flame, please...
I spent the last year with an Omnia, and I tried every possible rom on it until I found the one I liked/could put up with the missing features. It wasn't perfect, but I knew that a sweet android phone was in my upgrade future so I dealt. WinMo has it's flaws, but you can't fault the dev community for everything they did to make an ok device better.
Now here I sit swyping on arguably the best hardware on the market (other Galaxy S offerings aside...) and I have to say I really like it.
Voodoo-ed, de-binged, de-odexed, and de-TouchWizzed is way easier than trying a dozen roms on a weekend and adding .cabs from 100 websites to come up with a phone that still half the time didn't know where my finger was trying to press!
What does FroYo have to offer? Apps that run off the SD card? Flash? Minor, although it is a bit frustrating that by the time we get it, it will just about be time for gingerbread.
Guess I'm trying to say, the best stuff about froyo is going to get too us sooner or later whether VZW or Samsung give it to us or the very talented dev community here makes it happen. News that comes from them isn't why I log in here.
Sent from my SCH-I500 using XDA App
Downers
adrynalyne; said:
Verizon will decide when its released, not Samsung.
Click to expand...
Click to collapse
Just trying to give some legit info for a change... A lot of wet noodles.
Ok so I was told 2.2 would be released the other day.... and YES I used the word NINJA. ... I was wrong. But do we gotta keep mentioning NINJAS? ? Hahahahahahaha : )
Sent from my SCH-I500 using XDA App
No ninja source? I have my doubts about this info...
As for Froyo, I am excited to have flash, but beyond that, voodoo seems to meet my needs. Sure, you can't get rid of voodoo without performing a animal sacrifice, but it does make my phone smooth and sexy.
Sent from my SCH-I500 using XDA App
jatilq said:
Just trying to give some legit info for a change... A lot of wet noodles.
Click to expand...
Click to collapse
Sorry man, I wasn't trying to pee in your cornflakes, it's just that I have more faith in devs than VZW & Samsung to get us what we want.
Sent from my SCH-I500 using XDA App
I don't know about you but I am waiting for my navigation to be fixed. Not to worried about the little extras but the major fixes that are, major.
Sent from my SCH-I500 using XDA App
Quoted from original post 'No More pulling-out!!' That's what she said! Ha Ha...
I'm sorry I couldn't help it. I wont do it again I swear.
Honestly I can't wait to see what magic the dev community creates with Froyo and the Fascinate. My thanks to all of you!!!
Hopefully what happened with all the Droid 1 releases is what will happen here:
Motorola (in this case Samsung) readies a build, gives it to VZW for testing.
VZW takes forever testing it, and either rejects or preps it for release.
The "hopefully" part is that, hopefully, in the meantime, the file gets leaked from the Samsung end and into our hands.
Not trying to be pessimistic, but if that first file didn't leak, Im doubtful that this one will leak early either
If Verizon decides to sit on the release at least we have US Cellular as a backup. In fact it seems like US Cellular does not waste their time with carrier customizations so they might just push it out the same day they get it from Samsung.
I used to be a US Cellular customer, my wife still is, they will not get in any hurry, I would not count on them for anything.
nitroxeno said:
If Verizon decides to sit on the release at least we have US Cellular as a backup. In fact it seems like US Cellular does not waste their time with carrier customizations so they might just push it out the same day they get it from Samsung.
Click to expand...
Click to collapse
You missed the point of the post bud.
Verizon, or any carrier, does NO customizations, they have NO development (read: coding) teams. They don't alter the file they receive from the OEM (in this case Samsung) in ANY WAY. The bloatware you see comes with the build straight out of Samsung's repository, with the specs that Verizon requested. They take their sweet time for a multitude of reasons, and somewhere in that timeframe its held up for internal testing. Each carrier is different, but Verizon is notorious for being an extensive tester, and rejecting builds pretty often.
Bloatware that Samsung did not code....VZW did or outsourced. Hence people are arguing with you. You aren't wrong, but neither are you entirely correct.
Sent from my SCH-I500 using XDA App
I made this post to give some indication of the progress of Froyo, sadly most people want more or are intent on offering some type of dark cloud.
I know Froyo might not be released on the 11th, but at least we have a legit source of its progress. Hopefully around that time or before we will have a leaked build for testing and or roms (like some other devices). I'm sure thats when the dev section will take off.
well if samsung releases it Nov 11, dont they post the source up too, so we could have a modded version running before vzw does anything?
Can someone post (or re-post) a link to where T-mobile or Samsung says the update is only via Kies?
This assumes that millions of Vibrant owners a) are PC-savvy enough to update that way, b) run Windows in the first place (unless there is a linux version of Kies that I don't know about, please post link if you do)... while not *utterly* outside the realm of possibility, when you step back and look this is a pretty ridiculous thought that doesn't pass the smell test for me until I see some kind of proof.
Which leads me to the point that unless you have gotten a text or update notification on your phone from T-mobile with layman-friendly (pre-noob) instructions on how to use kies to update your phone from stock eclair to stock froyo, I don't believe that what is on Kies necessarily corresponds to what will be pushed OTA.
In fact I think it's quite possible if not likely that last second changes/fixes may have necessitated a final KA7 last night to hit the airwaves with "today".
Anyone have a screenshot of an OTA *NOTIFICATION* having been sent to them, and what form that takes and what instructions it gives? That's the proof I want to see.
crap..dp
/10char
richiehd:
photo of their source:
http://yfrog.com/f/gy2nwxlj/
their tweet:
http://twitter.com/#!/TmoNews/status/28494230598979584
bradycl_84043 said:
Can someone post (or re-post) a link to where T-mobile or Samsung says the update is only via Kies?
This assumes that millions of Vibrant owners a) are PC-savvy enough to update that way, b) run Windows in the first place (unless there is a linux version of Kies that I don't know about, please post link if you do)... while not *utterly* outside the realm of possibility, when you step back and look this is a pretty ridiculous thought that doesn't pass the smell test for me until I see some kind of proof.
Which leads me to the point that unless you have gotten a text or update notification on your phone from T-mobile with layman-friendly (pre-noob) instructions on how to use kies to update your phone from stock eclair to stock froyo, I don't believe that what is on Kies necessarily corresponds to what will be pushed OTA.
In fact I think it's quite possible if not likely that last second changes/fixes may have necessitated a final KA7 last night to hit the airwaves with "today".
Anyone have a screenshot of an OTA *NOTIFICATION* having been sent to them, and what form that takes and what instructions it gives? That's the proof I want to see.
Click to expand...
Click to collapse
For the Mini Kies notification
http://yfrog.com/f/gy2nwxlj/
As I wrote in a couple of other threads. You are right. This is just a voluntarily upgrade. And I think it was mainly to shut up to angry power users. As proof we have the KA7 leak that just came out today and the version Kies is updating is KA6. The mandatory OTA will be coming some time later but this seems to be a move to quiet down the press about the whole Froyo update issue. If this was the official update from T-mobile we would probably have the source code today as well, which is what we here on XDA really want.
Interesting. This is the first time that I've seen any kind of documentation showing that TMO won't be doing distributing as an FOTA update. Thanks for the heads up KA7. Still running JL5 while I've been waiting for things to settle down somewhat. Hopefully KA7 will be the last official release for the next month or so now.
any word on what version KA7 is? 2.2.1?
swehes said:
For the Mini Kies notification
http://yfrog.com/f/gy2nwxlj/
As I wrote in a couple of other threads. You are right. This is just a voluntarily upgrade. And I think it was mainly to shut up to angry power users. As proof we have the KA7 leak that just came out today and the version Kies is updating is KA6. The mandatory OTA will be coming some time later but this seems to be a move to quiet down the press about the whole Froyo update issue. If this was the official update from T-mobile we would probably have the source code today as well, which is what we here on XDA really want.
Click to expand...
Click to collapse
Agreed... and personally I'm waiting for Nero 6 (7?). But I'm going to be very interested in what T-mobile says *externally* today.
A promise of an update today from someone that high up at T-mobile... I'm sorry, when average josephine-housewife who bought a pretty Vibrant from the nice man at the T-mobile stand at Wal-Mart finds out that it *isn't* just a click-click-click on their phone like JI6 was... there's going to be a *lot* of very pissed off callers (and T-mobile phone support techs).
This effectively makes it an update that isn't really an update for everyone who has a Vibrant, not even everyone who has a Vibrant on T-mobile, and if that's the way it's left I'd be very surprised. I don't think that that is the message they want to send right now. "See, we updated today. Sorta..."
*This* update isn't mandatory, isn't FOTA. There could be an OTA 2 hours later discussed in their "Community". Not in the scope of the update being discussed in that screenshot.
It's entirely possible, now that I think about it, that KA6 is where features and so forth freeze, and that KA7 (and higher) are more focused on fixing anything that could break during OTA update, which could be (supportably) from JI6 *or* JFD.
We'll just have to see, but right now all we have proof of is that there is an update, and it is on Kies. I think that there *has* to be an honest to god OTA coming. To not do so almost guarantees that you will end up having a very high number of customers still on 2.1, perhaps over 50%, out of sheer laziness or lack of information/confidence to update. That support nightmare, again, just doesn't pass the smell test.
Also Kies Mini is refusing to update my phone, and I'm not sure how many people will haev a similar issue but it downloaded a bunch of **** and told me my phone could not be upgraded 5 times in a row.
How many battery pulls do I have to do before the damn thing actually updates?
Terrible experience, IMO, and a huge waste of time seeing as how some of us don't have the fastest internet connections out there...
That software also tends to choke spectacularly on Windows 7 (both 32 and 64-Bit) and AFAIK it does not run on Mac or Linux computers.
On the flip side, T-Mobile's coverage is bad so they put themselves into a corner when it comes to FOTA updates. I'm not driving 20 miles just do download a smartphone update because they only have GPRS and Weak Edge (1-2 Bars) around me...
Hi,
I've just received my HTC One I just discovered that it has 1.27 firmware inside :| And OTA section doesn't show updates :\
What can I do? Can I update to 1.28 (HTC Stock) without flashing a custom rom?
simonepsp said:
Hi,
I've just received my HTC One I just discovered that it has 1.27 firmware inside :| And OTA section doesn't show updates :\
What can I do? Can I update to 1.28 (HTC Stock) without flashing a custom rom?
Click to expand...
Click to collapse
I think you can flash one of these that matches: http://forum.xda-developers.com/showthread.php?p=39588860, or just root and install a custom rom?!
wait this month and htc will release 4.2.2. This old version is working fine, so i didnt updated or rooted until now.
RoachPapa said:
wait this month and htc will release 4.2.2. This old version is working fine, so i didnt updated or rooted until now.
Click to expand...
Click to collapse
Where did you hear 4.2.2 will be out this month or did I misunderstand what you wrote?
daleski75 said:
Where did you hear 4.2.2 will be out this month or did I misunderstand what you wrote?
Click to expand...
Click to collapse
4.2.2 will drop for the One soon, I believe Football has sources to confirm it. Probably within the next two months.
anyone knows what are differences between the two firmwares?
Hunt3r.j2 said:
4.2.2 will drop for the One soon, I believe Football has sources to confirm it. Probably within the next two months.
Click to expand...
Click to collapse
Ahh cool hopefully it will fix the rather poor bluetooth connectivity with the bluetooth in my car then.
Can you elaborate?
Sent from my C6603 using xda premium
Mine came with 1.28... but its vodafone branded
daleski75 said:
Ahh cool hopefully it will fix the rather poor bluetooth connectivity with the bluetooth in my car then.
Click to expand...
Click to collapse
Hi,
I noticed too a weird bluetooth connectivity in my car, with sound skipping.
It seems that disabling wifi does help.
On this s600 Thread they said it will come end of april or may. 4.2.2 features a good performance boost.
If it gets updated to 4.2.2, would the camera app have the photosphere or something similar.
Sent from my GT-I9300 using xda premium
If any of you really think they're updating to 4.2.2 in the next 30 or even 60 days you're living in dreamworld. HTC's priority is the production and sale of this handset to get them back into the black. They're not going to rush to bring out a minor iterative update that few are desperate for and no-one needs.
paddylaz said:
If any of you really think they're updating to 4.2.2 in the next 30 or even 60 days you're living in dreamworld. HTC's priority is the production and sale of this handset to get them back into the black. They're not going to rush to bring out a minor iterative update that few are desperate for and no-one needs.
Click to expand...
Click to collapse
As long as they update to KLP and if they skipped 4.2.2 I wouldn't really care.
daleski75 said:
As long as they update to KLP and if they skipped 4.2.2 I wouldn't really care.
Click to expand...
Click to collapse
Agreed. The priority should be firmware updates to address any issues that early-adopters encounter and big, RELEVANT updates like KLP. HTC made an active decision NOT to use 4.2.2, so the idea that some are suggesting that they're going to release the phone with 4.1 and then scrabble to bring 4.2.2 anyway is a bit silly.
paddylaz said:
If any of you really think they're updating to 4.2.2 in the next 30 or even 60 days you're living in dreamworld. HTC's priority is the production and sale of this handset to get them back into the black. They're not going to rush to bring out a minor iterative update that few are desperate for and no-one needs.
Click to expand...
Click to collapse
Dreamworld? Just so you know every company has what we call "Departments" just because a company focuses on marketing doesn't mean their R&D department would also do marketing tasks and halt R&D(Research & Development).
paddylaz said:
If any of you really think they're updating to 4.2.2 in the next 30 or even 60 days you're living in dreamworld. HTC's priority is the production and sale of this handset to get them back into the black. They're not going to rush to bring out a minor iterative update that few are desperate for and no-one needs.
Click to expand...
Click to collapse
unless the firmware developers are doing the manufacturing of the handsets at the factories then what you say makes no sense
some people's logic is seriously lol funny, software development does not just stop b/c they need to speed up the manufacturing process in the plants, and if it did how would that help the cause when they do not even work there?
brainimpact said:
unless the firmware developers are doing the manufacturing of the handsets at the factories then what you say makes no sense
some people's logic is seriously lol funny, software development does not just stop b/c they need to speed up the manufacturing process in the plants, and if it did how would that help the cause when they do not even work there?
Click to expand...
Click to collapse
There's nothing wrong with my logic, this is just common sense combined with observational evidence from past handsets. I think you've got the wrong end of the stick here - and it might be my fault for not being clearer. I'm not suggesting they won't bring it out for reasons of available 'manpower.' I'm just suggesting they have priorities, and a bottom line - and you sir, being one of the 2% public (along with me) who know and care about things like .x android iterations are not a priority. They made an active decision to go with 4.1. New software updates mean software engineers to combine with Sense, licensing with google, training and updating customer service personnel in case of problems/bugs with the update. All this and more cost MONEY. Can they do it? Sure. WILL they do it for a tiny update iteration that's not important to anyone outside the 2% and something that's too irrelevant to market and advertise about? HELL NO.
Anyway I'll bookmark this thread - will give it 60 days and see if Im wrong. My guess is you'll never see it. They'll jump to KLP. It makes more financial sense and my 'funny logic' tells me their business is financially motivated.
You seem to labouring under the impression that HTC either allow all their code division to sit on their hands for months on end whilst each batch is shipped out and sold, only earning their keep ready for the next manufacturing run (either that or you're assuming they are laid off for months at a time, allowing the competition time to head hunt them!)
Sent from my Tricked out 2.3.1 HTC One via xda-developers application
paddylaz said:
If any of you really think they're updating to 4.2.2 in the next 30 or even 60 days you're living in dreamworld. HTC's priority is the production and sale of this handset to get them back into the black. They're not going to rush to bring out a minor iterative update that few are desperate for and no-one needs.
Click to expand...
Click to collapse
I agree people are delusional if they think HTC will release 4.2.2 anytime in the next 6 months. HTC has proven time and time again to lie about release dates and take their sweet time. They are as bad as Motorola. Nothing has changed with the one and if we do get key lime pie it will be 8 months after Google releases it if HTC hasn't folded by then. They are gambling the whole company on the one release. Hope it does pay off for them as their phone hardware look and build is nice.
First off let me say I Do Not intend for this to be another whine thread....
Just wanted to reach out and see if anyone has had any signs of an update. I recall from one of the previous now closed threads started one user mentioned the 5th as being a possible date. Though seemingly arbitrary date the 5th is here.
People chime in if you get the notification!
Nothing for me yet.
It probably won't come out until the new Google phones do. I know it's difficult for flashaholics, but be patient.
Now I'm waiting for the September security update for Marshmallow, maybe it will be late too. They seem to be in a huge work.
This thread is the best sign.
daimerion said:
First off let me say I Do Not intend for this to be another whine thread....
Just wanted to reach out and see if anyone has had any signs of an update. I recall from one of the previous now closed threads started one user mentioned the 5th as being a possible date. Though seemingly arbitrary date the 5th is here.
People chime in if you get the notification!
Click to expand...
Click to collapse
That's what intended mine to be, but it went south so fast! Lol no sign for me yet, I'm hoping maybe by tonight. It's REALLY behind said release date. Staying optimistic!
This is the only sign from Google I have seen.
Absolutely notting here. Not even the sept security update.
There will be a September in 2017,too
If I'm remembering the same post, a user speculated that the update would be tied to the September monthly security update. That seemed like pure speculation. I hope the updates are posted soon but I don't think today will be the day, since it is already the afternoon and a business holiday. Hope I'm wrong!
Hope it's soon.
theman22 said:
If I'm remembering the same post, a user speculated that the update would be tied to the September monthly security update. That seemed like pure speculation. I hope the updates are posted soon but I don't think today will be the day, since it is already the afternoon and a business holiday. Hope I'm wrong!
Click to expand...
Click to collapse
Maybe tomorrow then, I forgot it was a holiday. What gets me is how they got everyone all riled up that it was gonna be in August, and it's gonna be out at the same time haha
Yeah Im ready for the official build too, this NPD90G preview wants me to want more, or at least some minor fixes.
No updates.............there will be speculations.
No speculations.....probably updates.
From what I've heard Qualcomm needs to do some driver upgrades for full Android N Support. If that is the case, it would explain why Google hasn't released the update yet, they simply can't until Qualcomm delivers. I can imagine Qualcomm has their hands full at the moment with all the smartphone companies out their requesting driver updates to support Android N as well.
I don't have any references for this, as I read it in a post somewhere but don't remember where. Don't take my word for it. But of course it would be interesting if someone could confirm or deny this.
I don't expect the update any time soon, but at least the latest beta runs very smoothly on my device. Can't complain at the moment.
Thats what has confused me DP5 runs well so id have thought it was near release quality but I guess not with the update taking so long. As far as qualcomm surely google should be the highest priority for drivers/updates given that they build the entire base that all other android phones base off? So an N driver for a specific SoC should work for all devices using that SoC?
I'm pretty satisfied with the Uber N ROM as is.
What @onemandivision said is correct, driver updates are critical. It's not just the kernel and the android base.
I'm a little confused by the delay though since it is already clear that phones on chips older than snapdragon 800/801 won't get nougat (ie 65-70% of all android phones according to some surveys), so there should be very few drivers to update/fine tune? Am I wrong?
Sent from my Nexus 6 using XDA-Developers mobile app
september update , my s7 edge still has the july update , samsung are dam slow pushing updates , my nexus 6 has the latest dev update but hope oneday soon the real 7.0 comes out.
New Marshmallow Image up... (MOB31E)