Not all of British Columbia can make the change. BC's northeast and much of the Columbia-Kootenays are presently on Mountain time, which means that the Province of Alberta holds the choice of when/whether their own and those BC areas go to a permanent time. Then AB would have to sync with Saskatchewan along their borders, but SK is already on a permanent time zone system. Decisions, decisions.
Maybe a buying trip north of the border might suit some U.S. folks alarmed by the TPMS blabbermouth data. Although Canadian-spec new vehicles usually have TPMS monitoring, it is not mandated, so some vehicles will display a dashboard icon or menu warning if no TPMS signal is seen, while others will just ignore the issue. Given that many Canadian consumers have dedicated sets of winter and summer tires/wheels, this is sensible to not require TPMS systems. Caveat emptor: I have no idea whether recertifying a new Canadian vehicle for the U.S. (i.e. changing kph speedo to mph, etc) involves flashing such different software.
A lot of new cars use tire rotation to detect a low tire now. So no need for TPMS sensors unless you need precise pressure data for some reason. Its much cheaper to do it this way so I suspect most TPMS sensors will be going away soon anyways.
I live in the Midwest and have a car with TPMS and winter and all season tires and it's a $10 thing to tell the car to pair with tires when I swap them. Most mechanics have these too as they service wheels so it's not an issue really. Yeah it messes with the tracking but my car also has wifi I can't turn off without ripping out OnStar.
In the context of the OP the TPMS sensors are culprits, and on U.S. cars the software requires that TPMS modules be present. I've read about Ford owners in the U.S. using FORSCAN to disable the TPMS software components and then removing the TPMS modules from the tires. No idea if this is still possible of if similar solutions are workable for other manufacturers. Having said that, I mentioned Canadian-spec vehicles that don't have TPMS enabled in the first place.
Haven't Google stopped publishing device-specific trees, hardware definitions, and drivers in AOSP so newer pixel are not that easy to use in GrapheneOS anymore?
The other Pixel 10* devices seem to already be GrapheneOS-ready, so I wouldn't be surprised if the 10a follows suit as soon as the GrapheneOS devs get their hands on one.
A cheap and dirty alternative to this excellent effort is to use an old VCR. Run your content into its input jacks, but instead of cabling the VCR directly to an analogue TV, use its RF output fed into an antenna, and use the analogue TV's tuner to receive. On most North American VCRs, that would mean selecting either output channel 3 or 4. For larger coverage areas, cut two dipole antennas to the appropriate size for the selected channel (one antenna for TX, one for RX). If you were to put a low noise VHF-LO amp inline between the VCR output and the TX antenna, you'd be able to cover a much larger area, but would probably have legal issues with governmental authorities in charge of telecommunication spectrum.
F-Droid itself is great, but I find that the NeoStore front end to F-Droid is superior because it has multi-repository capability, offering a long list of alternative apk sources that can readily be verified for quality.
Neo Store looks interesting, but the readme in the GitHub repo includes emojis in the feature list, which is a bit of a red flag for me, especially since the project appears to have started only two years ago.
reply