iPhone does the same thing. MacBooks too if the screen is open and you haven’t turned it off with Terminal.Then why not the same behavior for iPhones & Macbooks? Not challenging you, just curious.
iPhone does the same thing. MacBooks too if the screen is open and you haven’t turned it off with Terminal.Then why not the same behavior for iPhones & Macbooks? Not challenging you, just curious.
Not a big deal but majorly annoying and perhaps hindering when you have turned your phone off because of low energy and need every percent you can get once you’re near a charger, just that it’s not up to you that the phones fire back on the moment it sips the smallest amount of power. THAT IS very annoying and potentially a big deal, because boot takes a lot of energy, being on and being turned off again, too. All while you need to charge and keep every % you can get for later.It’s the same with the iPhone. Really not a big deal.
Unlikely. It charges the same when turned off. Also, the device will be in BFU, so not much else is accessible.Probably so background system processes can do the battery management
No, that works when off as well, I am pretty sure.I did not test, but I thought iPhone or iPad needs to be on for optimized charging. These devices have lot of algorithms to regulate charging, monitor temp etc. not sure if they will run in the background when device is off.
Sure, but how can they manage the battery when you plug in and turn the device off then?
Exactly, processes concerning battery management. So why do you have to boot when these processes can obviously run in the background anyway?Some background processes should still be running. Even when ‘off.’
Yes, they do stay turned off. Which makes it all the more confusing why it doesn’t work when the device is already off.This is how iPods, iPhones and iPads have been for as long as I can remember. I believe if you plug in the device and turn it off after plugging it in, it will stay turned off until you turn it on manually.
No idea, but the reverse is not true. A plugged in iPad when switched off won't switch back on.Anyone understand Apple's reason why an iPad will automatically turn on (from an off state) when plugged in for charging. I'm not sure why this behavior is a 'feature.'
Pretty easy, as iPhone/iPad/Mac/Watch never actually run fully out of power, and thus don't "power down" 100%:Sure, but how can they manage the battery when you plug in and turn the device off then?
I chalk it down to design philosphy.
Because the device will wait until it has a minimal charge for basic operation before powering (back) on, there’s a delay after plugged in (when the battery is critically depleted) before (re)boot. By having the device automatically (re)start, the user doesn’t need to guess, continually try to boot device. Rather, it’s ready to go (again) ASAP. In other words:I assume the reason for this behavior in general is that a device which has its battery exhausted can power on and the user can get “back to work.”
I would hate to turn on my devices every time it runs out of battery and then baby sit to turn back on.
Troubleshooting/maintenance also seems like valid reasoning.This is in place for a few reasons. For one, allows you to power on your device if the power button is not functioning. Also, should any volume buttons not be working, it allows you to place the device into recovery mode by holding the power button and plugging in the device while it has been powered off.
Just tried it and indeed, when plugged in, the unit powers up. I guess it's for the way it manages its battery?
The SMC handles that. However -- in the little bit I’ve analyzed the specific aspect -- it appears the device must be powered on and have been initially unlocked to log the battery state of charge progress (i.e., there will be a blank/empty period in the battery usage graph).I did not test, but I thought iPhone or iPad needs to be on for optimized charging. These devices have lot of algorithms to regulate charging, monitor temp etc. not sure if they will run in the background when device is off.
But the iPad would be in the BFU state (Before First Unlock). In this state, the user's data is still encrypted - meaning iPadOS wouldn't be able to index, nor would it able to connect to Wi-Fi to check for updates. The user would have to wait until it's booted up and enter in their passcode in order for it to do these things.