Featured

The Not-So-Pretty Side of Big Tech

on
Most of us grow up thinking that the things we buy and store online are ours. Games, apps, files, even the email addresses tied to our names. But big tech companies like Microsoft remind us that nothing in their ecosystem really belongs to us. Recently, Microsoft suspended my Outlook account. They claimed that my OneDrive contained “child porn.”  Let me be clear: I download adult videos from the open web. I am not a pedophile. Yet Microsoft’s algorithms, terms of service, and opaque enforcement systems flagged my content as illegal, locked me out of my account, and informed me that I cannot appeal for six months. When you use Microsoft services, you’re not really buying a product; you’re renting access. Their terms give them permission to scan files on your computer, in your cloud storage, and across your account. The moment something doesn’t fit their rules, they can revoke everything: your email, your purchased games, even the apps you’ve paid for. Microsoft’s policy is blun...
0

Experimenting with Android 16 DP2

on

So, I recently took the plunge and flashed the Android 16 developer preview on my device, hoping to push the boundaries of what’s possible. One particular tweak that caught my eye was enabling support for 16KB page sizes at the kernel level. I’m always interested in exploring these low-level adjustments, especially when they’re not widely documented yet. 


Flashing the developer preview wasn’t too different from past experiences—if you’re comfortable using android flash tool. The real intrigue began when I switched the kernel to 16KB page sizes instead of the standard 4KB. This is the kind of low-level tweak that can spark some intriguing performance conversations down the line.


The immediate problem? Most apps just aren’t ready for 16KB page sizes. The majority of them are firmly rooted in a 4KB world, and my device’s stability and compatibility took a hit because of that. In everyday use, this meant frequent force closes, hangs, and a general “not ready for prime time” vibe.


You might wonder why anyone would go through the trouble of messing around with something as fundamental as kernel page sizes. For me, it’s about exploring what’s possible and understanding the guts of the system. Being on the cutting edge means learning firsthand where the current limitations lie. And who knows—maybe down the road, as Android continues to evolve, larger page sizes could mean more efficient memory usage, smoother performance, or new optimization strategies.


At this point, if you’re curious enough to try 16KB on your own device, be prepared for a bumpy ride. Keep an eye on the Android developer community forums and GitHub repos. Sometimes, a handful of talented and persistent devs manage to patch kernels, refine code, or at least offer guidance on which apps can play nicely with these experimental features. It’s an evolving story—just don’t expect overnight miracles.


In the meantime, I’m settling back into the familiar stability of 4KB pages, but I’m definitely not giving up hope. The fact that these hidden switches and experimental kernels exist means there’s room for growth and innovation. Sometimes just knowing that you’ve tried something cutting-edge—even if it didn’t pan out perfectly—is half the fun.


If you’re the type to push boundaries, explore beyond the well-trodden paths, and don’t mind a bit of trial and error, then experimenting with 16KB page sizes on Android 16 might just pique your interest. Sure, it’s not primetime-ready, but it’s a glimpse into what future versions could bring.


For now, I’m chalking this one up as a learning experience—one that reminds me that being a part of the Android developer preview world is as much about embracing what doesn’t work as celebrating what does.

Comments

Post a Comment