Re:Using a Linux phone as a secondary monitor
by squarefoot on Tuesday May 17, 2022 @09:27AM
(#31410230)
That low latency is an impressive achievement, makes me want to attempt to convert all my old tablets to a real Linux install (no chroot jails etc), but the risk of bricking them is really high. I wish there was some tool to probe the hardware under Android, possibly against a distributed database, to know at least if the device is similar to a more known one (it could be the case among no name cheap Chinese tablets) and if there are chances of success before a blind attempt.
[ Parent
| on HN ]
Most SOCs have a mode you can put them into with just the hardware switches that runs firmware in the mask ROM which waits for a bootloader over USB. It's pretty hard to actually brick modern devices.
Re:Using a Linux phone as a secondary monitor
by mschuster91 on Tuesday May 17, 2022 @11:01AM
(#31411718)
Yeah, but most non-brand manufacturers don't release the tools, driver packages or the full firmware images at all - meaning you have to rely on questionable third party sites, hackers and leakers to obtain them to recover your device. I don't even want to know how many people ended up with malware from shoddy SEO-spam domains advertising Samsung's ODIN tool.
If Google had forced everyone to use the aboot boot loader and to allow rooting, we wouldn't be in this damn mess of people using all kinds of highly questionable stuff.
Re:Using a Linux phone as a secondary monitor
by bitwize on Tuesday May 17, 2022 @11:28AM
(#31412135)
The carriers wouldn't allow that, though. The carriers only permitted the iPhone because Apple guaranteed it would be locked down.
I am, of course, talking about the USA. I believe EU law forbids cellular carriers from being so thickheaded.
Re:Using a Linux phone as a secondary monitor
by xen2xen1 on Tuesday May 17, 2022 @10:40AM
(#31411392)
"distrubted database". What XDA isn't good enough?
Re:Using a Linux phone as a secondary monitor
by imtringued on Wednesday May 18, 2022 @02:52AM
(#31419941)
I get 100-200ms including network latency to a faraway server that has no hardware for encoding or decoding video via webrtc in a browser with vp8 without even trying. Anyone who can freely choose their encoder and decoder including hardware acceleration should be well within 50ms on a local network.
In fact, the biggest problem for me isn't the lack of HW encoding, it is the lack of HW decoding because it makes 60fps videos on YouTube unplayable.