In the case of iPhone, this does the job without powering off: simply hold the volume-up and the right button simultaneously to get to the power-off/medical-id/SOS/911 screen. After that, the phone is locked (i.e., needing PIN to unlock). On iOS 18, swiping to the control panel screen and pressing the 0/1 power icon in the upper right corner also leaves the phone in a locked state.

I had the exact same experience. I even went so far as to install the maps app on my iPad. Still no dice. If this is limited to Android devices (which I have no way of checking), they are going out of their way to avoid stating this.

Ignoring privacy for a moment, Google and Facebook, and the parasitic targeted advertising industry surrounding them, have sold business leaders on this idea that âoepreciseâtargeting of ad messages is worth paying high premiums for. Iâ(TM)m not sure that the return-on-investment data truly supports this. However, the idea that there is a âoeneedâ for privacy-invasive ad targeting appears to have achieved the status of a tribal/religious belief.

A back-of-the-envelope calculation could have told anyone that the one extra “G” should take (5-4)/4 = 25% extra power. A-duh.

I wholeheartedly agree. The recycle/re-use story at this point on standalone batteries is pretty bad, but researchers are aiming to improve it. Hardwiring batteries to motherboards makes the problem even worse, for both product and battery recycling.

Life imitates art, indeed: https://www.imdb.com/title/tt3...

I have the exact same symptom using the -109 update, i.e., attempting to boot that kernel ends up doing a system reboot. Said reboot happens after I've successfully entered my full disk encryption password.

A simple "emergency beacon" is a reasonable requirement. Having that same cellular radio be able to provide user input to critical vehicle systems? Bad idea. Nobody wants to thing they'll be the driver who runs off the edge of the road into a ravine in the middle of the night with no one around. But if it happened to be me, I'd be glad of the automatic emergency beacon.

Could the extra attention on GitHib be due to developers being very lax about having licenses applied to the work there? I'm not hearing here about a similar plague at SourceForge, which has always required there to be a license for every project.

It sounds to me like the CEOs have been eating their Wheaties and reading up on their Ayn Rand... Seriously, though, I love how the letter makes it sound like all the brouhaha is coming from a "concerted publicity campaign by some advocacy groups". I just looked at the FCC's public docket for response to Wheeler's previous proposal, and there are at least 10,000 responses. Even my state of Tennessee, not necessarily the most friendly to to Federal regulation, had 500 comments. I looked at a random sampling from TN, and couldn't find one posting with any particular love for the current regime of large ISPs. Words like "oligarchy" and "monopoly" were quite common.

Sounds like the leaders of the ISPs have been reading a lot of Ayn Rand lately...

TFA mentioned these advantages of the C-family as well.

Whatever happened to designing for accessibility?

I find this disturbing. I'm a latecomer to the Android phenomenon. As it turns out, I bought my daughter a Pantech Marauder phone (http://www.pantechusa.com/phones/marauder) in late 2012, which runs 4.1-JellyBean, and my sons just received Kurio 7 tablets for Christmas (4.0-IceCreamSandwich). Both devices are unlikely ever to get an official update to 4.2+. As far as I can tell, the patch in Android 4.2 is described here: https://developer.android.com/...

"WebView.addJavascriptInterface requires explicit annotations on methods for them to be accessible from Javascript"

Google appears to have treated this as an API issue. I.e., "the API up to 4.1 was insecure. We now will require method annotations going forward for the JS to execute them." I could care less if backporting this change to earlier versions broke a bunch of apps. It's an easy enough change for those apps to go and insert the explicit annotations. I think Google has made a conscious choice here to not cause apps to break in the name of security, so that their platform can appear to be "more stable".

You mean an ATO, obviously.