deleted by creator

As @Treeniks@lemmy.ml pointed out, the author considers something as small as spawning a separate process for each window to mean a “non-native experience” (wait till they see how web browsers work)

It’s likely the same sensor that is included in the rest of the Pixel 9 Pro Fold.

I see proofreading the first paragraph is too hard these days.

Don’t know about the rest, but…

Does reflashing a ROM fix it?

The phones appear to be simply dead with no response to anything. No way to connect ADB, no way to connect fastboot, nothing.

Also the bootloader allows flashing over the cable only when it’s unlocked (at least on Pixels; I couldn’t find anything relevant in the Android documentation). The vast majority of Pixels should have their bootloaders locked, and it is only possible to unlock it through the system settings, so it’s pretty safe to say that most Pixels cannot be recovered if Android fails to boot because you cannot unlock the bootloader if you can’t get into settings.

To be fair, giving a company that’s been failing to get themed icons to work on Android for almost four years now less than a month to make a significant change to a core part of their software is… quite weird?

Like, the EU usually gives companies at least half a year to comply with smaller demands than this, because companies with such a huge bureaucracy load wouldn’t even be able to change an app logo in such a short amount of time.

Maybe developers will finally start implementing predictive back now that it’s not hidden behind developer options. It’s kinda nice when you can just peek at where the app wants to take you when you go back, and it currently ironically tends to be implemented only by apps that already have decently made navigation.

Also private space seems nice, finally a way to use the work profile sandbox natively without having to install third party apps that pretend to be work profile managers.

It is for their non-flagship devices - those were always kinda left behind with software support.

This is the a model, it won’t have optical zoom either way.

Yay for another boring slab with zero distinguishing features!

No, it will fast charge to 80%, then restart charming just in time to hit 100% when your alarm goes off (or when it thinks you’re going to wake up). There’s no automatic slow charging other than thermal throttling.

If you don’t sign into a Google account, you will never arm this mechanism at all.

How much Doritos dust are you willing to inhale?

In my very limited experience with my 5400rpm SMR WD disk, it’s perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.

40 MB/s sustained is weird (but maybe it’s just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn’t even slowly fill the cache)

Sounds like most of that would be handled by the kernel with non-Deck-specific modules - it won’t forget to notify the userspace that a device has disappeared just because it was in sleep mode at the time it was physically disconnected.

The only problems I ever had with sleep on Linux were all inability to wake up some part of the motherboard or the GPU because of crappy firmware, never with connecting/disconnecting external stuff.

Seems more like a featureless slab to me

apps that are programmed by a 13 year old that wants to scam people.

That’s a weird way to spell “project manager who doesn’t let developers waste time making efficient apps when they could just add more marketable features”. The competition won’t hesitate, and users will always flock to apps with more features and nicer UI over optimizations.

People need to learn how to close apps.

If you have enough RAM, there’s no reason to - it’s not like they are actually running and consuming CPU cycles. If you don’t have enough RAM, you also don’t need to - Android will do it for you. My phone with 3 GB of RAM could barely handle maps and a browser at once, so there were plenty of times when the map app restarted and recentered on my current position when I came back from checking the website of whatever company I looked at.

The recent apps screen is really just a history of open apps, with some of them maybe still in memory, and with some opaque mechanism for automatically removing old entries. You can reboot your phone and the apps will still be there with a screenshot of their last state. Doesn’t mean they will get back to that state when you switch to them.

The huge amount of RAM on Android in general is less about supporting a single hungry app and more about keeping as many apps as possible in memory so that you can multitask between them without any of them losing their state. If one app manages to eat most of the memory, then it’s already too little for the intended experience.

Also the memory is supposed to be enough for at least the 7 years this phone will be supported for - that’s plenty of time for apps memory footprint to grow.

Maybe I’m biased by always having used devices with RAM size in the lower end (which is always also coupled by a not-so-great CPU so when you do run out of memory and the system starts killing apps you want to multitask between, you’re going to notice it that much more), but I’ll always take more RAM in a device that might survive a decade with a couple of battery swaps.

But it’s a design for designs - it tells you how to design your own UIs, it doesn’t dictate what for example a calculator app should look like. You can follow Material Design and still end up with a terrible UI design.

Surely that’s enough for some distinction, right?

Your mileage may vary - your experience might be different for one reason or another