![](https://programming.dev/pictrs/image/385658d9-e355-4571-a811-b0d61d6dbc9d.jpeg)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
Figured I’d do the math on the power required.
In the article, they show a iPhone 15 Pro, which has a 3274 mAh battery, so let’s go with that. Assuming a 3.7 V battery and a 1 minute charging time, that’s 3274 mAh × 3.7 V / 1 min ≈ 727 W
.
Figured I’d do the math on the power required.
In the article, they show a iPhone 15 Pro, which has a 3274 mAh battery, so let’s go with that. Assuming a 3.7 V battery and a 1 minute charging time, that’s 3274 mAh × 3.7 V / 1 min ≈ 727 W
.
I used to use it, but then I switched to MPV, as it works a lot better with hardware acceleration. MPV supports more methods for hardware decoding (e.g. nvdec), and also MPV will keep the frames in VRAM when doing hardware decoding, and do additional processing and presentation using the GPU, while VLC copies everything back to system RAM and processes the frame on the CPU.
At the time I switched hardware decoding with copy-back would actually result in twice the CPU usage compared to software decoding, but that was a long time ago. Also, I would get tearing in VLC and not in MPV.
Something with OpenWRT. Turris Omnia is pretty good.
You’re right, that might work
That requires root
Motorola and Nokia have phones with 3.5mm jack, and they come with pretty clean Android, without a bunch of bloat, aggressive task killers and whatnot. Though I can’t speak for camera, photosphere or repairability.
Pixels are good in some ways, but of course, those don’t come with a 3.5mm jack.
So it’s not really a 4K 1000Hz screen then, if it’s just togglable between being a 4k 240 Hz screen and a 1080p 1000 Hz screen.
A310 is the cheapest.
I wonder how well it does for transcoding on older computers without ReBAR, since apparently gaming on it is straight out broken without ReBAR. As in, it would actually freeze for a second or so every now and then.
It’s better in one way, in that updates are applied on reboot rather than pulling the rug put from under running applications. But I agree that it doesn’t go all the way, as it doesn’t provide a verifiable base system with clearly separated modifications. OSTree would be great.
Another possibility would be to distribute a base image as a btrfs send stream (possibly differential against previous versions) containing a compose-fs image and associated files. And then OS extensions could be installed with systemd-sysext.