Dave Nanian (Mastodon):
Since a given APFS container can hold multiple copies of the OS, Preboot and Recovery have folder structures that include UUIDs corresponding to the volume that “owns” that part of their shared volumes in the group. Inside that UUID-named folder are the files that “pair” with the system you’re trying to boot.
In Ventura and later, for some reason, one set of Cryptexes also appear outside this structure, at the top of Preboot.
[…]
On top of that, asr didn’t (and doesn’t) copy the Cryptexes. So we thought “well, there’s got to be a reason for this; they’re probably generating and grafting the right folder during the boot process”. And, indeed, that’s what it does.
But only sometimes.
Those extensions are necessary for some things I run, but they seem to interfere with boot. On the “plain” systems, you don’t even need the “root level” Cryptexes folder and yet it boots (using, I assume, the existing Cryptexes inside the UUID-based folder). But on others, you absolutely do need them at the top of Preboot, or you get a kernel panic.
[…]
We’ve decided to not wait for asr to be fixed by TBTB. […] Instead, to improve bootability, and save user’s time (not to mention sanity), we’re decided to copy over the Cryptexes to the root of Preboot.
Previously:
Backup Bug Kernel Extensions Mac Mac App macOS 13 Ventura macOS 15 Sequoia SuperDuper
Andrew Liszewski:
Amazon has released a software update for the current-generation Colorsoft and Paperwhite that lets you double-tap on the sides or back of your Kindle to turn the page. The new feature, as spotted by The eBook Reader, is listed in the release notes for the 5.18.1 update and can be found in Settings > Device Options.
[…]
The feature works well using relatively light taps anywhere on the Colorsoft, and since it requires two taps in rapid succession, it’s not easy to trigger by mistake. Unfortunately, it’s limited to just one direction. You can either use it to jump to the next page, or scroll down a long list of books. Perhaps a future update will enable triple-taps as a way to scroll up or go back to a previous page.
Sounds like a great idea, but hopefully it works more reliably than iOS’s Back Tap.
Previously:
Kindle
Ben Schoon (via Hacker News):
The Android Open Source Project (AOSP) has left most of Google’s work in developing Android as an operating system visible to the public eye. But, starting next week, Google is moving that work behind closed doors.
Google confirmed to Android Authority that “all Android development will occur within Google’s internal branches,” the publication says. This is a shift from how Android has been developed for a very long time, but also aligns with more recent moves Google has been making.
Mishaal Rahman:
Because Google develops large portions of Android in its internal branch, the public AOSP branch often lags far behind what’s available privately. This difference is apparent when comparing feature and API availability between a clean AOSP build and Google’s latest Android 16 beta, which was built from its internal branch. While the shift to trunk-based development reduced this discrepancy, it persists and continues to pose challenges for Google.
This discrepancy forces Google to spend time and effort merging patches between the public AOSP branch and its internal branch. Due to how different the branches are, merge conflicts often arise.
[…]
External developers who enjoy reading or contributing to AOSP will likely be dismayed by this news, as it reduces their insight into Google’s development efforts. Without a GMS license, contributing to Android OS development becomes more challenging, as the available code will consistently lag behind by weeks or months. This news will also make it more challenging for some developers to keep up with new Android platform changes, as they’ll no longer be able to track changes in AOSP.
Android Google Open-source Software Programming
