Coffeehouse Thread

14 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

WP7 update bricking some phones ?

Back to Forum: Coffeehouse
  • User profile image
    Srikanth_t
  • User profile image
    magicalclick

    Don't know, but, I think it is weird as AT&T didn't let me update on my HTC Surround.

    Leaving WM on 5/2018 if no apps, no dedicated billboards where I drive, no Store name.
    Last modified
  • User profile image
    Srikanth_t

    The point is - This is embarassing.

  • User profile image
    magicalclick

    Point taken, I don't like Samsung anyway.

    Leaving WM on 5/2018 if no apps, no dedicated billboards where I drive, no Store name.
    Last modified
  • User profile image
    Charles
  • User profile image
    kitron

    How does this even happen. We only have a couple of handsets and you would think Microsoft would test on all firmware configurations.

    The only reason is affecting only 10% of the handsets is because they havn't pushed this out to everyone.  As far as I know no carrier branded phone has got the update. Imagine if AT&T allowed the update, how many Samsung Focus units would've been affected. We would be talking 50% or more failure rate.

     

     

     

  • User profile image
    magicalclick

    Ekkk, didn't thought they will backup my phone on PC before I do update. It is reasonable action, just didn't expect it. Good thing my HDD is full of spaces. I have like 11GB of data in my phone. It is gonna take a long time to backup.

    Leaving WM on 5/2018 if no apps, no dedicated billboards where I drive, no Store name.
    Last modified
  • User profile image
    Minh

    Sheesh...

    Now the carriers will have a reason to delay upgrades... Hey MS... here's some open source code... free of charge

     

    // Begin Update Checks

    HardDrive hd = GetFreeHardDrive();

     

    if (hd.FreeSpace > Phone.Capacity) goto DontBrickThePhone();

     

    if (Phone.Model in GetPhonesMModelsWeTestedOn) goto DontBrickThePhone();

     

    BrickThePhone:

       // Your stuff here

     

     

    DontBrickThePhone:

      // Do updates here

  • User profile image
    daSmirnov

    @Minh: it already does that.  It fails gracefully like it should if there isn't enough space to back the phone up.  It doesn't attempt to install the update, which is classed above as a "failure" when of course in reality the press are reporting it as if it was the number of unbootable phones.

  • User profile image
    Minh

    @daSmirnov: That's good to hear that they do handle that scenario gracefully... but

     

    Of the 10 percent who did experience a problem, nearly half failed for two basic reasons—a bad Internet connection or insufficient computer storage space. Luckily, both are easy to fix.

     

    That leaves 5% of phones BRICKED

     

    5% is a HUMONGOUS # for bricked phones... and if you assume that Samsung phones make up a majority of phones out there, that number is an even bigger %...

     

     

  • User profile image
    daSmirnov

    5% aren't bricked.

     

    They just needed to be hard reset.

  • User profile image
    Minh

    @daSmirnov: And the carriers would say... 5% will call them up for support... and that will cost them $$$... And that's why they'd want to delay upgrades even more than the 1 cycle they are allowed to...

    Regardless, a hard reset is taking out the battery... a farcry from a good user experience... MS isn't playing in the field like they're the underdog... ie, they should strive to provide a better user experience than the other 2 guys

  • User profile image
    AndyC

    , Minh wrote

    @daSmirnov: That's good to hear that they do handle that scenario gracefully... but

     

    Of the 10 percent who did experience a problem, nearly half failed for two basic reasons—a bad Internet connection or insufficient computer storage space. Luckily, both are easy to fix.

     

    That leaves 5% of phones BRICKED

     

    Well, no. It just means that 5% failed for a reason other than the two given. What percentage suffered to the extent it required hard resetting or worse isn't specified.

     

    And given that I've seen no sign of the update (HTC Mozart on Orange) it's not even 5% of all WP7 devices, but 5% of those to which the update has been released and the customer has attempted to update (given the news reports, it's likely some Samsung handset owners have held off I'd imagine).

  • User profile image
    Minh

    @AndyC, sometimes what's not said says a lot... But this Samsung Focus owner is gonna wait a few weeks before pulling that trigger to run the upgrade

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.