In addition to that, other Android distributions have also moved “child process limit” to developer options, which may forebode them removing it, and breaking termux entirely. This is pretty scary IMO.

Can’t you toggle the child process limit in those android distributions you speak off?

Because, this is the data they saved in the super partition. You cannot dynamically change that on a production device.

You mentioned Bootloader Unlock so I was going to day Pixel. But, then I remembered they use Tensor instead of 8 Elite.

Your options will be limited to 8 Elite smartphones supporting phones which allow that.

Super cute

TL;DR

• Google announced that the next major version of Android (Android 16) will be released in Q2 of 2025, which is several months earlier than usual.
• Google’s VP and GM of the Android Platform told me in an interview how the company was able to move the release forward by so much.
• The Android trunk stable project gave Google confidence that it could roll out updates faster and more frequently without breaking things.

Interview video link: https://youtu.be/ODqTy903fZM

Basically, the Q4 minor release will be the QPR of pixel smartphones for other android users and Q2 will be the major android release with ground breaking changes as usual, just early going forward 2025.

It’s implied. How else would the magnetic part work? I can’t comment on magsafe but it should be Qi2. Unless, they didn’t certify and made a proprietary implementation just for oneplus 13 series smartphones.

I don’t know how notebookcheck measures. But, xiaomi lists the display as supporting PWM at 3840hz. Notebookcheck had written 120hz for oneplus 12 but official oneplus also lists a higher PWM frequency than the one measured by notebookcheck.

https://www.mi.com/global/product/xiaomi-14t-pro/specs/

The use-after-free vulnerability is tracked as CVE-2024-44068, and it affects Samsung Exynos mobile processors versions 9820, 9825, 980, 990, 850, and W920. It received an 8.1 out of 10 CVSS severity rating, and Samsung, in its very brief security advisory, describes it as a high-severity flaw. The vendor patched the hole on October 7

This is the most important paragraph. This bug was already exploited in the wild and affects select few exynos smartphones. If you have a affected device make sure it is updated and you should be fine.

Interesting, seeing penti keyboard being recommended in the wild. Are you also familiar with picolisp?

Even if they don’t. Android 14 itself is not outdated. Even though his phone and its firmaware may be. The list of changes are incremental at best. To take advantage of them all you would need newer hardware anyway. He won’t be missing much if at all.

Thanks for the heads up. This will make sure we never commit such criminal activity ever again.

I know. I did not expect them to switch from Mali to PowerVR. This is an interesting surprise.

deleted by creator

The core and process node upgrades are more noteworthy than ram speed upgrade. This should boost efficiency and performance significanty.

Them switching to PowerVR GPU is also interesting. Not sure if itis related to Qualcomm-ARM lawsuit.

It’s ferro fluid with an array of magnets.

The smart outfit will be available next year. You can watch the video here: https://youtu.be/rZ0KVloLxJw

Wallpapers (3 of them) can be downloaded on the HMD blog post.

Realme will release Android 15 in Q1 of 2025, next year and it will be buggy. So, I will wait either way. Only pixels and a select few OEM devices have android 15 now.

Disappointing, you’d think this wouldn’t happen with Google controlling both hardware and software

Perhaps, the testing folks thought the same thing as you, and skipped testing a thing or four. 🤣/s

Anyway, the 1st gen pixel users suffered the most. The latest gen pixel 8 series (and perhaps pixel 9) are not critically hit and have less heating problems. It sucks being early adopter for beta hardware and software. Google should compensate the affected users with upgrade to pixel 7/8 or even 9 series if possible.

What’s your workflow for syncthing & applying wallpapers? Do you use tasker alongside synthing to sync and auto apply a new but same wallpaper on all your devices?