Aren’t iPhones switching from AFU to BFU if you don’t unlock them long enough anyway? Or is BFU not the same state as entered if lock and volume down button are pressed for some time?
YSRCEABP
What?
You Should Really Considering Explaining Acronyms Before Posting, obviously.
The acronyms in question are defined in the article, ysrcrtabr, you should really consider reading the article before replying
I figured the whole thing out before reading the next sentence :(
From what to what?
BFU = Before First Unlock
AFU = After First UnlockBFU deez nuts lmao gottem
nice
That would be super cool if that was a feature instead of a bug because anything that makes law enforcement’s job harder is worth praising and doing properly.
GrapheneOS includes this feature
It would be nice if this feature did not disable immediately if you turned it off and would require like say 48 hours and two more reboot cycles. That way if a cop took your phone from you and had it and went into the settings and turned the feature off it still wouldn’t work.
Or just require your Apple password to turn it off.
I just heard this like yesterday or today and so that’s absolutely amazing. I don’t think lineage has it though, which is sad. Although it is less useful on lineage since you can’t re-lock boot loaders.
Tell that to my pixel
Yes, LOL. That is literally the only exception to that I know of.
Yeah, seems like a reboot every 24 hours you’re not unlocked would be extremely useful
Hardly ever have I seen an article so full of “could be”, “alledgedly”, “supposed”, “likely”, and “probably”.
It may be because I have stopped reading about UFO’s after the age of 15.
Because they have no actual proof of it, and direct evidence against it. They talk about phones communicating with each other to restart… yet a phone inside a faraday box restarted.
It’s almost certainly just a software bug in iOS which is why it’s inconsistent.
It’s also the most unlikely explanation of all, that phones brought in communicated with the ones in custody to reboot them. Even if it was a security feature to reboot phones under certain conditions, which is very likely TBH graphene OS does this, the best implementation isn’t going to be relying on other phones randomly passing near by, it’s going to be self-managed by the phone that reboots.
A remote command from some random phone to reboot does sound like the a wonderful vector for malware, though
I wouldn’t mind having the ability to schedule a reboot on my phone as an extra precaution.
I think graphene does this by default now? Like if you don’t unlock it for 24 hours it’ll reboot.
Its an aosp feature i believe, but its disabled on many phones. Graphene and calyx have it. With calyx its default off, but you can set it between 1 and 72 hours. Very handy feature.
Graphene is set to reboot after six hours of inactivity, ensuring that it reboots every night after I’ve gone to bed.
18 hours by default.
I thought it’s a standard feature (auto restart at set times). Maybe a samsung thing and not android.
It probably requires root, but I’m sure Tasker can do this.
Really, all phones should have the option to reboot into locked mode on certain conditions like being taken out of network or being unattended for a while.
The interesting thing is if the manufacturer is shipping them that way by default.
Could possibly also look at the motion sensors to see if it is in a pocket moving around or if it was sitting around for a while.
Good idea, but a motivated attacker could put them on one of those rocker tables like they use for mixing blood. It also wouldn’t cover the more common scenario of someone stealing it out of your hand.
There is a shortcut action to shut down the phone which you could trigger with an automation, I suppose.
I can put the phone in lockdown by press-holding the power button and select the “lockdown” option. Not bad, but an actual reboot daily at night wouldn’t be so bad.
That’s not what I mean, I’m talking about the Shortcuts app:
This had never occurred to me before but it’s great, thanks! I expect that alarms don’t run until after first unlock, so 3am wouldn’t be great if I use the phone to wake up but later in the morning should be good.
I believe it should still work, as alarms trigger for me even if my phone updated overnight or I put it on the charger dead before going to sleep, but I’ll have to test it
On iOS this is 5 quick presses of the power button, and it vibrates in a unique way to let you know it worked, so can be done in a pocket or just without looking, which is nice. But yeah an auto reboot would be swell.
You can, see my other comment: https://feddit.org/comment/3001525
Thanks, but that’s not rebooting and does not fill the need properly.
I don’t want to shut my phone down regularly, I want to reboot it regularly.
Shutting it down just means my phone is shut down and stays that way until I realize and boot it back up (which could well be hours depending what I’m doing), which is a much worse situation for an absolute homebody such as myself.
As the linked screenshot shows, you have the option to choose between shutting down and rebooting. There is no need to explain the difference to me, I demonstrated that the thing you want to do is possible.
Dont know what lhone you are speaking of, but on Samsung phones, the only thing that this does is disabling biometrics and notifications. Your phone stays in AFU and this does not protect you from law enforcement or other
It protects you from being compelled to provide biometrics to unlock the device. Since the courts have made a distinction between providing a password and biometrics to unlock devices for whatever asinine reason.
Biometrics are what you have and a password is what you know. I can record you and look at you or even grab a part of your body (e.g., for fingerprints) but it’s not possible to read your mind.
Samsung has this option.
GrapheneOS has the option for a scheduled reboot if the phone hasn’t been unlocked for a configurable amount of time.
GrapheneOS has an option to reboot your phone after being locked for X hours.
Check out GrapheneOS.
My phone rebooted occasionally on iOS18 and this was mentioned as fixed in 18.1 release notes so this story sounds plausible.
