quortez

MLS please come and save us…

Humans may be made irrelevant in places, but you can’t say they’re bad at (broadly) recognizing patterns

I’ve done it; results are…flaky at best, YMMV

I can’t tell if it’s just my cable or my Pixels being… Pixels, but transferring from one to the other had frequent dropouts, elevated temps, high drainage, and sometimes disabled USB transfer until you plugged and unplugged again.

Might not be an issue on flagships or other OEMs but idk

Farewell to #HoloYolo - the last release of its generation, and the first of Android RunTime

Much appreciated

Fuck.

Oh my God Zenonia. I still miss 3 and 4 (never got to finish them 😔)

I basically see this going in 1 of three directions:

a) Sony will deliver the Q Lite as is, in this form - a barely unmodified Android (13?) Tablet handheld that presumably has Remote Play and PS+ preinstalled. I find this very unlikely, but probably the best case scenario to maximizing value/minimizing e-waste of this device.

b) Sony will deliver a heavily modified/locked down version of Android dedicated to a PS5 aesthetic/UX that only uses Remote Play/PS+. I find this the most likely option from a matter of cost and practicality. Android is extremely competent at scaling to various form factors and has 1.5 decades+ of application and hardware support. Other than embedded Linux (yes I know the kernel, shush) it’s one of, if not the easiest OSes to build up from, especially if you are running Qualcomm, which they are rumored to be in a partnership with. This will make things more difficult to modify/hack though.

c) Sony will ship a completely different, restricted scope OS likely based on a cut down Linux or variant of their PS4/5 BSD-derived Orbis OS. This is less likely than the modified Android, but far more likely than the naked Android tablet shown above. It would fit the branding and ethos that Playstation tries to exude and probably increase the difficulty of hacking even higher, but the design of this device does not strike me as being in the scope/budget of porting over their console OS to mobile ARM hardware. They are very clear about this being a companion device, likely just to test the waters of making handhelds again, with a lower scale target to reach (video and input streaming) than actually including another power target for their entire platform SDK (committing to a Switch style platform halfway through the console cycle or adding the equivalent of a PS Vita in an era of developers barely being able to target 1 console SKU competently, let alone 2).

Either way, this mf ugg-leee.

It would be so great if we could get Pixels to do the inverse (cast via Miracast).

Maybe one day…

I always got confused with percentage increases and whether they were relative to the original amount (going from 100% load to 300% load) or whether they were adding on top of the original amount (adding 200% on top of 100% to make 300%).

Regardless, that’s a ridiculous jump.

Over 200% markup in a single pricing change, yeesh

You think they’d gradually ease people into it at least. This app is always on something

Microsoft sells you as a product while also having the gall to charge you for it

Are we really going for a revival of 00s skeuomorphism? 💀

Back when Sony named their phones semi sensibly

8 years to not-remove a part of the spec AOSP supports natively.
8 freaking years to develop a solution for native video-out that isn’t the confusing, low-quality, barely recognized DisplayLink.
8 goddamn years to admit to themselves that Chromecast mirroring is a dog shit alternative to DP-AltMode.

But 8 years hopefully come to an end.

I like MY — I just wish I could design more of it on the user side.

Auto generated colorschemes are great and give Android a level of class it has been missing for a while. But I wish I didn’t have to rely on a third party app like Repainter to finely choose my palette rather than hope the theme engine makes a good one. I also resent my icon shape, font, and icon options being ripped away from me.

There was a section on the original MY Google IO announcement that implies that the padding and roundness could be freely adjusted throughout the system. I wish that materialized (rimshot) into the final product.

The only objective regression I can think of with MY, rather than just an annoyance, is the Quick Settings. A merged internet toggle that no one asked for, a further reduction in a available toggles from Android 11, and not even bothering to make the Bluetooth toggle one of the fancy expanding ones instead of sending you to settings or surfacing the audio playback toggle (why can’t I change the output before I play media, Google?). Ugh.

Fuck, I really hope this doesn’t turn the tides for other Red Hat projects.

Not even my Linux distros can escape the enshittiness. WTF man.

It’s looking great man, keep up the good work

Fingers crossed that this will be implemented well, im tired of having sleek electronics be irrelevant in 2 years when the silicon could go for 5 or six