• thorbot@lemmy.world
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Never had this, but my phone does do updates on its own at night so occasionally I have to enter my passcode. Honestly I don’t really care as long as it doesn’t affect my alarms!

  • chriscl000@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I had this, last night. My iPhone 13 Pro appeared to go off around 0100 and was still in „Sleep“ Focus in the morning (my Apple Watch, fortunately, woke me up).

    The iPhone stubbornly thought it was still in „Sleep“ mode (including blanking the wallpaper off the Lock Screen) until I rebooted it at about 0900.

    I wonder what will happen tonight?

    (iOS 17.0.3, of course).

  • kobra@lemm.ee
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    I chatted with Apple support and they seemed to think the gap in the battery graph was normal if the screen was off?

    I have suspicions that Focus modes also have some impact as to how the graph is displayed but haven’t confirmed it yet. The support rep seemed to think the passcode prompt was a coincidence as it’s something iPhone will prompt for after 6.5 days of not using a passcode.

    I had an iPhone 15 plus that was showing a last status of “10 hours ago” in Find My. Once I called it, it immediately checked in and the battery graph on that phone showed a gap right up until the moment I called the phone.

      • kobra@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        A crash makes sense actually, and for whatever reason it never crossed my mind but that would explain what we’re all seeing.

        Wonder what could cause a crash on so many iPhones on the same night? 🤔

    • kobra@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Potentially, yeah. I have an iPhone 8 Plus on 15.7 and it did not experience a power down or restart last night but my 15 Pro on 17.0.3 did.

  • 2Xtreme21@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Had_ it last night— 2am on Oct. 11th— on my work iPhone SE2. On a wireless charger in Sleep Focus. My 14 Pro was fine both nights (Sleep focus, wired charging). Both on 17.0.3.

    Wonder if Apple will make a statement as this seems to be super widespread. And it doesn’t seem like there’s any particular pattern for who it happens to.

  • hogunner@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Didn’t happen to me on my iPhone 12 Max running the iOS 17 beta but did happen to my SO’s iPhone X running the latest, non-beta of iOS 17.

  • whynotzoidberg@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I can’t find my source for this memory, but I recall several years ago reading about Apple introducing automatic device resprings / restarts overnight. I think I still had my iPhone X at the time.

    In my experience, it only happens while charging. I might have to cruise the old jailbreak subreddits to find whatever I think I’m remembering here.

  • CarlosCheddar@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    This is happening on my 14 Pro on iOS 16. I just thought it did an overnight restart to fix any memory issues. I only started noticing it a few weeks ago.

  • Gorgeous_Sloth@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Also happened, 15 Pro Max 17.0.3. I was also asleep but iPhone turned off between 2h and 7h. It was forced to restart at this exact time because of my alarm going off at 7h. I noticed instantly something unusual was happening as the ringtone wasn’t the usual one. I’m in France so it didn’t happen at the same time it did in the USA.

  • LazaroFilm@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    1 year ago

    Could be to save up on battery charging overnight but the passcode in the morning sucks plus what if someone tries to force a call to you (double call and such)?