• 4 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle
  • You can use a USB hub dongle which passes through power via USB C with a Google TV (4K) device. That’s what I do for mine to connect it to the rest of my GbE VLAN via wired ethernet connection and avoid Wi-Fi packet drops when streaming or casting 4K HDR content. A dongle is also handy to connect any USB web cam so I can use the TV for large family video calls with the grandparents in the living room, via Android apps like Google Meet or Zoom.

    Here is the one I use that also has a combo headphone jack with GbE Ethernet and passthrough charging, so also nice for Moonlight gaming on modern android 120Hz HDR tablets where I don’t want to use low bitrate HFP Bluetooth for discord calls while also listening to game audio and music. Note, when used with the Google TV, I don’t use the USB Hub’s HDMI, opting for the Google TV’s international cord to maintain Consumer Electronics Control (CEC) functionality.

    Anker 655 USB-C Hub (8-in-1), with 2 USB-A 10 Gbps Data Ports, 100W Power Delivery, 4K HDMI, 1 Gbps Ethernet, microSD and SD Card Slots, 3.5 mm AUX, for MacBook, and More (Charcoal Gray) https://www.amazon.com/dp/B09MF6TJLW







  • Just like modern cars… I wish there was some kind legislation that would limit phone-home telemetry to emergency service telecommunication frequencies, and be opt-in only. That way any OEM operating under commercial cellular frequencies would thus be unlicensed, and subject to FCC violations and import bans. Like what OnStar was originally pitched as; only auto dialing to 911, and 911 only, if you were unresponsive after airbags deployed. OEM couldn’t use the telecommunication frequencies for anything other than networking with emergency service endpoints on the same VLAN.

    Anything recorded by the vehicle would be required to stay on the vehicle due privacy regulations, like the black box recorder for warranted forensic investigations. OTA updates could also be distributed offline for users to download and flash via USB, like any motherboard bios, so transactions would be write only.














  • I would also guess the smaller range of hardware revisions is easier to keep track of when considering something as device specific as microphone frequency response curves or approximate intrinsic camera calibration values, thus simplifying the post-processing or data ingestion from an aggregate deployment of recording equipment.

    While Android devices are probably significantly cheaper, they’d vary quite a bit in terms of microphone, camera, and lens manufacturers, not to mention ADCs, gain to noise ratios and cheapest firmware, depending on what the OEM felt like swapping to for that minor product revision.

    Not sure how precise these researchers are trying to calibrate and rectify field measurements, but if they’re using internal phone sensors rather then external AV peripherals, then homogeneity across field computers would simply matters of data uniformity.