Apple Releases Minor watchOS 4.2.3 Update With Bug Fixes

Discussion in 'iOS Blog Discussion' started by MacRumors, Feb 19, 2018.

  1. MacRumors macrumors bot

    MacRumors

    Joined:
    Apr 12, 2001
    #1
    [​IMG]


    Apple today released a minor software update for the Apple Watch, upgrading watchOS 4.2.2 to watchOS 4.2.3. The watchOS 4.2.3 update comes one month after the release of watchOS 4.2.2, a minor update focusing on bug fixes.

    watchOS 4.2.3 can be downloaded through the dedicated Apple Watch app on the iPhone by going to General --> Software Update. To install the update, the Apple Watch must have 50 percent battery, it must be placed on the charger, and it must be in range of the iPhone.

    [​IMG]

    Today's update addresses minor bugs discovered since the release of watchOS 4.2.2, and it includes a fix for a bug that causes device crashes when a specific character in the Indian language Telugu is sent, received or input into an app. Similar fixes have also been released for macOS High Sierra and iOS 11.

    watchOS 4.2.3 will be succeeded by watchOS 4.3, an update that's currently in beta testing and slated for release in the spring. watchOS 4.3 introduces portrait orientation support for Night Stand mode, and it reintroduces support for controlling music played on the iPhone with the Apple Watch.

    Article Link: Apple Releases Minor watchOS 4.2.3 Update With Bug Fixes
     
  2. Truckondo macrumors regular

    Joined:
    Jun 4, 2009
    #2
    I won’t call it a minor update when they take as long as they do.
     
  3. BasicGreatGuy Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #3
    I hope that Apple gets to the point where updates can be done directly from the watch, without having to go through the phone. Good thing I don't have anything pressing for the next 20 - 30 mins. :)
     
  4. Radeon85 macrumors 6502

    Joined:
    Mar 16, 2012
    Location:
    South Wales, UK
    #4
    And stop the requirement of it being at 50% whilst needing to be on the charger. I always just put it on the charger for a second to start the update then wear it again while it's doing the update. Have done this since the very first watch update on S0, S2 and S3, never had an issue.

    Being placed on a charger should not be a requirement unless under 50%.
     
  5. scrapesleon macrumors 6502

    scrapesleon

    Joined:
    Mar 30, 2017
    Location:
    Jamaica
    #5
    The update doesn’t take long something wrong with your watch then
     
  6. BasicGreatGuy, Feb 19, 2018
    Last edited: Feb 19, 2018

    BasicGreatGuy Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #6
    I think he is talking about in general. In general, the bigger updates do take a long time.
     
  7. Tubamajuba macrumors 68020

    Joined:
    Jun 8, 2011
    #7
    And it takes around 2 minutes for the Series 3 to boot up- the fastest watchOS has to offer. Series 0 is something like 4 minutes.

    I'd blame the sluggishness of those things on the fact that the S3 processor is only about as fast as the A6 in the iPhone 5, if even that. Also, has anyone figured out how fast (or slow) the NAND chips in the Apple Watches are? I doubt anywhere near as fast as the ones in recent iPhones.

    Eventually Apple's "S-series" processors will be able to handle booting and updates much quicker, but we're likely still some ways away from anything approaching the 30-second bootup time and 5-10 minute OS updates that the iPhones enjoy.
     
  8. Shirasaki macrumors 604

    Shirasaki

    Joined:
    May 16, 2015
    #8
    Not sure if latest watchos beta has this fix implemented already. I hope it does. There is no way to downgrade the watch to this version from beta.
     
  9. Westside guy macrumors 603

    Westside guy

    Joined:
    Oct 15, 2003
    Location:
    The soggy side of the Pacific NW
    #9
    His watch - and just about everyone else's watch other than yours, apparently. :D
     
  10. TiggrToo macrumors demi-goddess

    TiggrToo

    Joined:
    Aug 24, 2017
    Location:
    Out there...way out there
    #10
    They may say they require it, experience shows it's not necessarily enforced. I started an update on my Series 1 once, then quit quickly when I slipped on my Series 3.

    The following morning I noticed my Series 1 was in the final stages of completing the update as I wore it; looks like the autoswitch kicked the update into action again and it proceeded to complete whilst I was wearing it overnight!
     
  11. Rychiar macrumors 6502

    Rychiar

    Joined:
    May 16, 2006
    Location:
    Waterbury, CT
    #11
    not being Indian I could care less about some Indian character bug for something my watch will never see. def don't need an hour long update for it
     
  12. Strelok macrumors 6502a

    Strelok

    Joined:
    Jun 6, 2017
    Location:
    United States
    #12
    So start the update when you go to bed or aren't using the watch.
     
  13. TheQuest89 macrumors member

    TheQuest89

    Joined:
    Jan 25, 2018
    #13
  14. Mainyehc macrumors 6502a

    Mainyehc

    Joined:
    Mar 14, 2004
    Location:
    Lisbon, Portugal
    #14
    I believe you are confusing the update process itself with the first boot right after the update (maybe you just weren’t paying attention?).

    Rather uncharacteristically, my watch asked me for the passcode again after the update (and yes, it was updated because I got an alert on my iPhone saying so) and also displayed the circular progress bar around the Apple logo – which it usually doesn’t – and even though it took slightly longer than a regular boot sequence, it was obviously much faster than the update itself. Maybe that’s what you actually saw instead?
     
  15. Benjwri macrumors newbie

    Benjwri

    Joined:
    Feb 19, 2018
    #15
    You realise if your watch runs out of battery while updating you could kill it right? It’s better for Apple to be safe because if they weren’t you can imagine the lawsuits if someone’s watch was killed by an update.
     
  16. DeepIn2U macrumors 601

    DeepIn2U

    Joined:
    May 30, 2002
    Location:
    Toronto, Ontario, Canada
    #16
    This is a critical next round feature for the upcoming watch. It'll also be staging the first round update for it's own 'app store' in a major future update ... I'm pinning for August 2019 prior to v5 of the Watch. The goal of course ... is to have a MAJOR hardware technology improvements and a potentially sync to a future new product .. Apple VR glasses (Windows .. no that's taken, Panes .. doesn't give the right positive association to marketing, how about Apple View).
     
  17. AmbitEnergyMEcom macrumors newbie

    AmbitEnergyMEcom

    Joined:
    Nov 10, 2017
    #17
    Just updated mine, took about 10 minutes. I’m assuming internet connection may have something to do with length of update.
     
  18. imronburgundy macrumors regular

    imronburgundy

    Joined:
    Nov 1, 2013
    #18
    Will this bring my AW0 back from the dead? Siri was never so slow as it is now. "Hey siri, set a timer for 10 min." "I'll tap you when I'm ready...."
     
  19. RedKite macrumors regular

    RedKite

    Joined:
    Dec 19, 2017
    #19
    The update caused my watch display to show a white image for around 5 minutes. During this time it went warm.... but not hot at least.... to the touch. I left it on the charger and went out. 30 mins later and it was back to normal? Never had it behave like that before.
     
  20. PR1985, Feb 20, 2018
    Last edited: Feb 20, 2018

    PR1985 macrumors 6502a

    Joined:
    Jun 16, 2016
    Location:
    Germany
    #20
    Strange things happened. Series 0 and iPhone X: First my phone could not find the update. I´ve rebooted my phone still nothing. Once the message that my watch can not be found. After some tries it showed, finally, up. I could not see the "Download bar", even no message that the download was in progress. After some time I heard the Taptic Engine of my watch, Which was and is now on the charger. Tapping the watch showed a message, on the watch, if I wanted to proceed with the update (after unlock) It asked for the code. After some time... Download and Install again on the phone, in my watch App. Tapped it, entered my passcode and preparation started immediately. The update started and is still in progress. Any ideas what might have happened? Thanks!

    Edit: Update finished... It asked for the code (watch). I´m spastic so I typed the wrong code. And? Apple logo with the circle. Progress more than a half circle then it fired up.

    Strange!
     
  21. RedKite macrumors regular

    RedKite

    Joined:
    Dec 19, 2017
    #21
    That’s interesting! My wife has my old first gen watch. When I owned it it was slow like you said “I’ll tap you when I’m ready” but since she had it it’s back to a normal speed. It’s a genuine first gen one with the slowest CPU too. It made me think an app I had paired to it was causing it problems. I transferred everything over to my Series 3 Cellular model and that didn’t and hasn’t lagged yet!
     
  22. pat500000 macrumors 604

    pat500000

    Joined:
    Jun 3, 2015
  23. TheQuest89, Feb 20, 2018
    Last edited: Feb 20, 2018

    TheQuest89 macrumors member

    TheQuest89

    Joined:
    Jan 25, 2018
    #23
    don't update to 4.0!! 3.0 was last best update apple watch has gotten imo. plust that play from iphone feature is still baked into that firmware, and you don't have to install some bugged out beta to use it.

    just gonna let these test rats update to 4.2.3, so i can read the horror stories. already got a few already on this page.
     
  24. pat500000 macrumors 604

    pat500000

    Joined:
    Jun 3, 2015
    #24
    Thanks, man! I heard 3.0 was better.
     
  25. DanBassett macrumors newbie

    DanBassett

    Joined:
    Feb 20, 2018
    #25
    --- Post Merged, Feb 20, 2018 ---
    We’ve had a lot more calls about software issues and fixes lately at RepairZoom - not yet the normal Apple Watch Repair stuff like cracked screens etc. It’s probably just a blip and likely to be solved with this new software update.
     

Share This Page