Related
I haven't found anyone with a Surround on AT&T that has gotten the update. If AT&T does to WP7 like they have continued to do with Android, it will be the last branded phone I ever buy from them.
God, I hate AT&T.
lol dude ... did you readed thread with update at all ? update was removed from ms site in 23 feb . due problems with samsung devices (c) captain oblivious
Appreciate your response, I guess. But they only removed it for Samsung phones, newb.
http://www.winrumors.com/microsoft-temporarily-disables-windows-phone-7-update-for-samsung-devices/
And regardless if they removed it or not for all phones, the question still stands:
DID ANYONE WITH AN HTC SURROUND RECEIVE THE UPDATE?
Why is this so difficult for you to understand? Jeesh...
I was under the impression that they only turned off the update for Samsung as well, according to Engadget.
I have yet to receive any update notification either for my Surround.
However, I'm not sure if ATT would have anything to do with this, because you should be able to just update the phone via Zune, bypassing any carrier influence, correct?
McHale looks like you born 1 min ago .. or you first time own PDA ..
1. update nature .. anyway .. will require carrier assistance .. will they support 1 year old devices ? more likely not
2. update was NOT intended for all devices .. they said that right from start . also no one said future updates will be for all devices as well .
3. as far as you may know chevron will be fixed in nodo ( future update ). and NO LONGER WILL UNLOCK PHONE. you will NOT be able jailbreak your phone .. i rly dunno why so many exclamations and despiration in update process at all .. since right after update you gonna FLood forum with = HOW COULD I FALLBACK INTO 7004 ??? QQ OMG BBQ
in the end of sentence you could clearly see main idea ... - update process will be via old way ( cooked roms ) wish you or not .
i just wish you luck in finding OUT FROM EMERALD DREAM . and begin monitor USEFUL things Like HARDSPL . since only them could extend device lifecicle
Wow, such hostility...
But in any case, after reading up on a few things, I'm going to clarify my previous statement.
Carriers can block the update, however, they can only block one update. So basically if ATT did in fact block this update from the Surround, they will have no choice in the matter when NoDo hits. That update will include this minor update plus that one.
Also to consider, it could just be a staggered update and it just hasn't made it to the surround yet.
there is no hostility or something personal . dude just in emerald dream ..
teoami
that problems nothing .. ms does not know themselfs some MAJOR things. they just keep silence about that
1. each MS product have limited lifecicle . updates which implement new major functionality counts as - SERVICE PACK HAVE DIFFERENT LIFE CICLE . and when RTM version does not suppurted SP still on support ( or Adaptaion Kit update if it is for mobile segment ) . will update policy cover that or updates limited bt family ? that part still unknown at all
in more easy words - updates under Os CURRENT STATE till new sp or what ?
2.
Carriers can block the update, however, they can only block one update.
Click to expand...
Click to collapse
there is NEW problem unclasified by ms as well
they could postpone all updates if phone does not longer supported by manufactuter or carrier . HTC LIFECICLE for example 1 year . carrier phones could have 2 years as exeption ... how they will update things if they does not supported by manufacturer ?
ps .i just not in emerald dream about unlimited support .. i know all that gonna end in custom roms coz update will not gonna work or will wprk pretty limited time
mo3ulla said:
there is no hostility or something personal . dude just in emerald dream ..
teoami
that problems nothing .. ms does not know themselfs some MAJOR things. they just keep silence about that
1. each MS product have limited lifecicle . updates which implement new major functionality counts as - SERVICE PACK HAVE DIFFERENT LIFE CICLE . and when RTM version does not suppurted SP still on support ( or Adaptaion Kit update if it is for mobile segment ) . will update policy cover that or updates limited bt family ? that part still unknown at all
in more easy words - updates under Os CURRENT STATE till new sp or what ?
2.
there is NEW problem unclasified by ms as well
they could postpone all updates if phone does not longer supported by manufactuter or carrier . HTC LIFECICLE for example 1 year . carrier phones could have 2 years as exeption ... how they will update things if they does not supported by manufacturer ?
ps .i just not in emerald dream about unlimited support .. i know all that gonna end in custom roms coz update will not gonna work or will wprk pretty limited time
Click to expand...
Click to collapse
How do you manage to have 32 GB in your HTC Surround?
mo3ulla said:
lol dude ... did you readed thread with update at all ? update was removed from ms site in 23 feb . due problems with samsung devices (c) captain oblivious
Click to expand...
Click to collapse
Hey look. Microsoft is starting the updates for SAMSUNG phones again...
http://www.coolsmartphone.com/2011/03/03/windows-phone-updates-start-again-for-samsung-handsets/
still LOLING .. kinda late .. but THX anyway
Uploaded with ImageShack.us
I had Mango developers beta since it first came out, then about a week ago I update to the 7720 version. My battery life was predicting 13 hours right after charging. My sons 7720 was showing 1 day 3 hours. This weekend I got an update notice, updated last night now my phone reads 20 hours. Does anyone know what was in this update? So far I haven't found anyone else having been notified. Is this only the original Focus' maybe?
oldtech said:
I had Mango developers beta since it first came out, then about a week ago I update to the 7720 version. My battery life was predicting 13 hours right after charging. My sons 7720 was showing 1 day 3 hours. This weekend I got an update notice, updated last night now my phone reads 20 hours. Does anyone know what was in this update? So far I haven't found anyone else having been notified. Is this only the original Focus' maybe?
Click to expand...
Click to collapse
From beta to 7720 you get 3 updates:
7720
cleanup
samsung update
Probably the one you refer to is Samsung Update, which improves the radio and camera. It's not for Focus only, afaik.
Btw, it seems that battery life is also affected by multitasking in official Mango, there are several reports of that in the forum.
Now that HTC Surround is a discountinued model, what chance do you think that we'll ever see updates from WP7 7.10.7720? Given that HTC and the orriginal carrier (in my case, Telus) control the relase of updates, why would they bother testing anyhting new on the Surround?
Are we stuck on 7720 for ever?
Don't think so. Regardless of the device status, Microsoft is still interested in providing a positive user experience and will do what's necessary to make sure relevant updates get pushed through. OEM firmware updates are also a possibility. Things like the dissapearing keyboard will get fixed.
While this is all speculation, all devices should continue to receive support/updates for at least 21-24 months from date of release, or the length of a typical (2 year) contract. At some point the hardware will not have the capability to support new features, but that's to be expected.
Let's hope you're right
the latest is 8779 but still couldnt find any free download on it so i just found 8773 which is the 2nd latest probably.
link: http://forum.xda-developers.com/showthread.php?t=1685058
At&t Update coming.....
On their site said that an update for Windows Phone 7 and 7.5 phones it's coming, and the Surround is listed so here's hope I think
http://www.att.com/esupport/article.jsp?sid=KB117823#fbid=K3TISJ0o9c9
This is not as question, but as discussion about our phone official support. And yes Mi A1 won't get Android Q:crying: According to Google answer Pixel/Android One phone receive at least 18 month for OS upgrade support. And as today (March 2019) it's already passed. It's about OS upgrades. Now about security updates. According to Google in past the Android One should have at least 3 years security updates support. But on October 2018 Google gave an official mandate about taking 2 years of security updates for popular Android phones (later in December 2018 Google change rules for Android One as well to 2 years). But since Xiaomi doesn't really care about Mi A1, it shows that the end of support is near (maybe 1 or 2 months).
Links:
https://www.reddit.com/r/Android/comments/724ij3/android_one_update_period_18_vs_24_months_and_who/
https://www.theverge.com/2018/10/24/18019356/android-security-update-mandate-google-contract
https://www.indiatoday.in/technolog...e-is-deleted-from-its-site-1418261-2018-12-27
Time to move to a custom ROM
At least, means it will get no less than 18 months new OS releases.
On the other side, i think it will sure get the new ''whatever-iteration-may-have'' Q version of android because there will be no major difference in OS and will be easy enough for developers to adapt.
punktnet said:
At least, means it will get no less than 18 months new OS releases.
On the other side, i think it will sure get the new ''whatever-iteration-may-have'' Q version of android because there will be no major difference in OS and will be easy enough for developers to adapt.
Click to expand...
Click to collapse
Not sure for it. 18 months has passed just now. I don't have any hopes for xiaomi to make new update, just because they already showed how much quality they put in upgrate of phone (Android pie for exp.) Making android Q doesn't makes them any profit. And in their interest to get customers buy new devices.
Skoll91 said:
Time to move to a custom ROM
Click to expand...
Click to collapse
Yep. It is. There are already new march security update out. Customs get it almost instantly. While official there's no any guarantee to even get any further updates at all.
I'm already on LOS. 9.0 push me to LOS 15.1 and I'm sure I will never come back to stock.
Never_Sm1le said:
I'm already on LOS. 9.0 push me to LOS 15.1 and I'm sure I will never come back to stock.
Click to expand...
Click to collapse
I am on stock. No root. No nothing. And I really love my Mi A1. But every time I see people talking about loving custom ROMs I wonder what am I missing?
Does anyone have a solid official confirmation from Xiaomi that they won't be continuing to support the Mi A1 in terms of major OS updates? I'm thinking about moving to a custom ROM but I want to ensure that there won't be any major official updates coming anymore.
caolan said:
I am on stock. No root. No nothing. And I really love my Mi A1. But every time I see people talking about loving custom ROMs I wonder what am I missing?
Click to expand...
Click to collapse
you miss a lot, but not need per se a custom rom, is enough root + all the goodies will come with root and customization.
force doze, custom kernel, magisk modules, google camera and so on.
caolan said:
I am on stock. No root. No nothing. And I really love my Mi A1. But every time I see people talking about loving custom ROMs I wonder what am I missing?
Click to expand...
Click to collapse
To others, there is a lot. But to me, there is only 1 thing: stock doesn't support Ex-fat sd cards, and the only kernel that offer true Ex-fat support is custom roms only. On stock 8.1 I can live with a Magisk module that support Exfat but 9.0 is the main reason I jumped ship.
The unofficial los 16 by flex is an amazing rom don't let the unofficial bit put you off, it's the perfect daily driver, more customisation than stock but not ott like some roms
I am happy to have gotten 2 major updates, previously at this price point we would have been lucky to get 1, so android 1 program has increased value with updates. I was hoping to get 3 years of security updates, so disappointed Google has changed the requirement, but perhaps Xiaomi will honour the expectations when the device was released.
Even at 2 years I would still have bought the phone, but annoyed if it's changed after purchase.
I currently use Stock unrooted Rom, the first phone I haven't at least rooted, but I am sure the community will keep the phone going for another couple of years at least.
I bough this phone on Nov 2017 (if note mistaken) and I'm quite satisfy with the update from Nougat to Pie. But if you buy the phone later than that you probably feel not enough update (because you only receive Oreo to Pie update) but I believe you have received price drop compare to the initial release.
I prefer stable rather than updated OS. This device is already more than 1 year and new android OS will optimize new hardware, smartphone hardware obsolete very fast compare to PC or other device. There's no other choice if you want to optimize your phone to the latest android OS except buying new phone. I like to stay to the stock rom (with Magisk of course) till the end just to get full experience of Android One. I'm not gonna denied that Android One is a bit mess up either from manufacture side and Google itself. I will probably buy Android One device again in the future (few years from now) and see how much Android One will improve.
Feriol said:
... I currently use Stock unrooted Rom, the first phone I haven't at least rooted, but I am sure the community will keep the phone going for another couple of years at least. ...
Click to expand...
Click to collapse
Same here, first ever un-touched stock. I'm still satisfied with this mid-low budget phone and that the OS is (pretty) free from "customization".
It is (was) a good bang for the buck when bought in Nov. -17 and still does it's job.
Features like GCam and similar were never promised or supported so that wasn't an issue for me nor a reason to root...
I have the AT&T branded version of the S10+ , meaning I bought it from AT&T. So if you are on another carrier or have the unlocked version, this post might be of no use to you!
I have had the phone a little over a month. Since I have had it, it has gone thru several firmware updates that are confusing the hell out of me. Here's my trek log:
Phone came with firmware SD3.
About a week later it updated itself to SD7.
Some weeks later SD9 came around (I think).
I noticed the security level patch was being updated to a semi current month and that is it aside somewhere I read something about night mode on the camera (which I have) and also found a new QR scanner icon.
After that, it updates to firmware SR7 or S something 7 (I forgot the middle letter).
I was on this firmware until yesterday when it updated to SG8. I was on SG8 about 5 minutes before it said another update was available. What gives!?!? So many updates! AHHHHHH!
I read that the Sxx update (I forgot the middle letter and end number this time) just fixes some bug about the lock screen. I wasn't even experiencing said bug! Why do I need the update!?!?
So this morning after connecting to my wifi last night my phone yet again updated itself, (even though I kept telling it to remind me later) this time to SGB.
I am freaking confused Mr. Bigglesworth!
Can someone help and enlighten me here? I come from the S3 and S4 days of the galaxy line, back then only serious updates (like the patch for stage fright) and OS updates rolled out. These new seemingly random and nonessential updates are very new to me.
I'm not on AT&T and people with Samsung phones almost invariably complain about not receiving updates so your complaint is novel.
SGB is the latest Samsung build--unlocked S10+ phones got it this week (after several months with no updates) and Verizon got that update last week.
Your many intermediate updates might be coming from AT&T and be updating or fixing the carrier specific stuff they added to your phone.
StoneyJSG said:
What you said
Click to expand...
Click to collapse
so the interesting part of the firmware's are the last 6 letters on my phone those are U3ASG8.
the u3a part is the version of the bootloader you are on (this is not downgradable), so I am on the 3rd version of the bootloader.
the last 6 letters in my case SG8
-S is for the year, so in 2020 it will become T
-G is for the month (A for January, B for February and so on)
-8is the build number (they test internally find any problems then increase the version...)
if you want to find what the updates improved check
http://doc.samsungmobile.com/SM-G975F/LUX/doc.html
just change SM-G975F to your model and change LUX to your region. This is everything they say in the changelog for the update on the phone too. If it repeats the same stuff as last month that most of the time means that it was just a security update.
jhs39 said:
I'm not on AT&T and people with Samsung phones almost invariably complain about not receiving updates so your complaint is novel.
SGB is the latest Samsung build--unlocked S10+ phones got it this week (after several months with no updates) and Verizon got that update last week.
Your many intermediate updates might be coming from AT&T and be updating or fixing the carrier specific stuff they added to your phone.
Click to expand...
Click to collapse
Hey that makes sense! Thanks!
suljo94 said:
so the interesting part of the firmware's are the last 6 letters on my phone those are U3ASG8.
the u3a part is the version of the bootloader you are on (this is not downgradable), so I am on the 3rd version of the bootloader.
the last 6 letters in my case SG8
-S is for the year, so in 2020 it will become T
-G is for the month (A for January, B for February and so on)
-8is the build number (they test internally find any problems then increase the version...)
if you want to find what the updates improved check
http://doc.samsungmobile.com/SM-G975F/LUX/doc.html
just change SM-G975F to your model and change LUX to your region. This is everything they say in the changelog for the update on the phone too. If it repeats the same stuff as last month that most of the time means that it was just a security update.
Click to expand...
Click to collapse
You know I did read somewhere that the firmware letters and numbers meant the bootloader, month, year, and build number. I didn't know I could check a site to see what the updates did/do, thanks for the post but I tried changing the lux to US and 975F to 975U but it came back with a 404 error.