430 karma · joined October 28, 2020
Obviously, this isn't perfect, especially since Google removed the internet permission and allowed all apps to access it. Allowing advanced users like us to toggle off internet access in the "App info" permission page would be a good compromise, and I hope and Android team does so to match Apple on their security efforts.
Background: HEC uses 3 pins. Those pins can be used for 3 different protocols: HEC (100Mbps differential signal slightly modified from the Ethernet standard)(1), ARC (1 Mpbs SPDIF signal over a single wire)(2), and eARC (~40 Mbps SPDIF differential signal)(3).
Modern computers with integrated graphics send the HDMI signal from the CPU pins. But in all the examples I could find, those pins are all Displayport (4)(5)! This is because DisplayPort supports HDMI video data wthin its signal. This allows manufacturers to convert that to HDMI with a cheap IC (that is mostly a redriver and level shifter). So they just have a DisplayPort signal exit the CPU/GPU and convert it to HDMI if necessary.
At this point I should note that DisplayPort does not support high-bandwidth auxiliary channels. So higher bandwidth features like HEC would require the converter IC to have a separate data channel to the CPU/GPU. But I couldn't find a DP-to-HDMI IC that supports HEC or eARC. I guess there's just not enough interest.
In theory, some computer/GPU manufacturer could connect the HEC pins to an FPGA that has a high-bandwidth connection to the CPU/GPU to support eARC. But even with that, your hacker would need to reprogram the FPGA to stop being a SPDIF encoder and start being an ethernet bridge. And this hypothetical FPGA can't support just ARC - it would be way too slow to be reprogrammed for Ethernet.
Of course, this leaves out home theater devices. They support eARC, and if their ICs are flexible enough, might be able to speak Ethernet with a lot of programming. But since no devices support HEC, you would have to reprogram devices on both sides of the HDMI cable. And at that point, you could just transmit data over SPDIF.
In short, there's a 99.9% chance that HEC pins are physically disconnected in any computer's HDMI port. Even if they were connected, a hacker wouldn't be able to establish an Ethernet connection unless the device under attack is using a very obscure IC or is ridiculously over-engineered.
1: https://patents.google.com/patent/US20110096793
2: https://www.ap.com/technical-library/more-about-arc/
3 (PDF warning): https://www.latticesemi.com/-/media/LatticeSemi/Documents/Wh...
4: https://www.reddit.com/r/Amd/comments/gzkxux/the_am4_pinout_...
5: https://images.anandtech.com/doci/14657/ASUS%20Pro%20WS%20X5...
In Android, Google often hides advanced functionality under overflow menus. These menus have a 3-dot icon (implying more menu options) or a settings gear, so most users will check them when the visible options aren't satisfactory. In recent Android releases, a lot of settings have clear and concise descriptions so users can understand their impact.
In Windows, Microsoft prefers to use a "properties" or "advanced options" menu, which also works well. If you can't find a desired option in the surface menus, you can dig into those menus.
Both of these approaches do a good job of offering more settings when needed while also warning users that the options can cause undesired effects. Android has clear settings descriptions so it's difficult to make a mistake, and when important settings like a debugging dump are triggered, will also display a clear warning about private information or breaking apps. Windows uses an "advanced" menu that can warn away "mom and pop"/novice users who could dig themselves into a hole. In both cases, there's some precautions to prevent users from mistakenly changing critical settings.
But why would it be waking up so much? Usually the wake requests originate from some other app, but I didn't see any associated wakeups in the stats dump. After a while I remembered that I installed GasBuddy recently, and a Google search revealed that other people had Bluetooth battery drain issues after installing it. Apparently GasBuddy had an ads SDK that aggressively scanned for Bluetooth beacons. Removing the app stopped the drain.
I was shocked that no battery stats screen showed GasBuddy was the culprit. Even the Battery Historian tool (which requires the user to run a Docker image and dump a bugreport) only hinted that there was some Bluetooth wakeups, but didn't show which app they originated from.
This AirTag seems to be a similar issue, especially if a less experienced user doesn't realized all the "Find My" wakeups are caused by nearby AirTags.
I think Apple needs to make the "deep sleep" states of their devices more strict so they can minimize drain when sitting (both when sitting overnight on a nightstand, or for a week in a living room). Notifications (besides calls) can usually afford to be batched since users are asleep or not nearby. As for AirTags, if one is being carried through an area, there's probably other iDevices that are being actively used nearby. They're already awake and using RF, so they can handle the AirTag ping with virtually no additional power consumption.
Cruise AVs are much different. They appear to use LIDAR, radar, and camera data to understand their surroundings including intersections, pedestrians, and road hazards.
The existence of technologies are fine, but we need to set strong social norms, laws (and resilient enforcing institutions), and smart design limitations to protect against abuse.
So I'd say Elk Grove's sprawl was driven by NIMBY-style regulation that encouraged low density housing and failed to address the effects of hopscotch development. Within those failures, Elk Grove has a few gimpses of higher density and urban planning, as well as anecdotes about the benefits of mixing different socioeconomic classes.
This could also enable removable battery modules. I could envision an EV with 150-200 mile range for everyday driving, with additional batteries kept at home connected to energy storage (like a Tesla Powerwall). When you want to go on a road trip, you just disconnect the modules and install them in the lower part of the frunk and trunk. The packs could also have other uses - you could load one into an electric motorcycle (much like the Zero Motorcycle already can). If you're desperate for a charge but don't have a plug near a parking spot, you can lug a module to a wall outlet. And we've seen how additional batteries enables additional current (and therefore performance), so EV sports cars could be lower-horsepower "daily drivers" until you install the batteries for a weekend drive.
It appears you can instruct it to avoid connecting to the internet to do stuff while in standby. I hope this works since my Surface Book has bad standby drain after sitting on my desk for 2-3 days off charge.
There are EV equivalents too, like the Chevy Bolt and Hyundai Kona EV that offer range in the 200s of miles with make driver assists as an optional upgrade. Even with complicated powertrain electronics, EVs are still more reliable than ICE cars because any iffy software is made up for by lack of mechanical parts. The repair procedure is the same as mechnical parts - just swap the faulty part out for a working one, and the "upstream" supplier will probably take the broken module to reflash software or frankenstein together half-working PCBs to make another refurbished module to sell.
If you're worried about remote compromise, it's pretty easy to avoid IMO. Open the dashboard and yank the cellular antenna, and never pair the infotainment to Bluetooth or Wi-Fi (or just yank the 2.4 GHz antenna). Those are basically the only avenues for wireless attacks into a vehicle unless you count the TPMS and key fob radios, which seem too simple and low-bandwidth to offer an attack surface. And if an attacker can access your car's physical ports, they could already attack you in other ways like by weakening the brake lines. Other new electronics, like MOSFETS instead of relays in the BCM, have actually made the car more reliable so they should be fine. Other newly standard features like blind spot monitoring are (1) solid state, so they won't fail often and (2) tolerate failure or complete removal.
With Chromecast, the dongle is actually just a remote-less streaming stick. So it streams directly from the server and the streaming app on your phone is the remote.
So Android Automotive OS is an improvement over this, since Google will be updating the system (or mandating some updates) and system apps will be receiving updates decoupled from the OS. Cars are already insecure and connected.
I wish Google Contributor could live up to the same promise, but Google killed it and replaced it with a different version. It made you a participant in the bidding process for your own ad views. So unless an advertiser was bidding a crazy amount of money, you would win the bid and an empty ad (or no ad at all) would load instead. Like YouTube Premium, this took advantage of the existing ad payment infrastructure while removing almost all the ads from your pages and videos.