Does your adapter work at 120Hz without updating the firmware? If it does, does it support HDCP?

To get around this, Google put in the TI TAS5825M smart audio amp. By measuring the speaker parameters through V/I measurement and a model, it drives the speaker in a closed loop way with far more power than it would actually be able to handle nornally to compensate for the resistance from the enclosure air pressure, and throttles to maintain the coil at a safe temperature. The chip also does DSP to compress the audio signal, cutting the peaks off the bass as needed when the volume is turned up so volume is maintained at the cost of bass.

One way to explore could be to just feed I2S audio from an I2S ADC i.e. PCM1808 to the digital input of the amplifier. The processing is internal to the amp so theoretically you won't lose the tuning. However this may turn out to be a relatively annoying reverse engineering project with fine magnet wire involved.

Note: I2S is different from I2C - the amp will likely have both. You will likely need to keep the original system around to program the amp over I2C (or capture the transaction and replay it) - otherwise you will likely get no audio.

The "raw" audio performance of this device (just an amplifier connected directly to the internal speaker and dsp on the computer) is impressive, kicking out bass down to 40Hz. It will, however, not last long like that. Reports online are that these blow speakers easily even when used with the default amplifier.

I would recommend that if 3.5mm input is desired, to replace them altogether with the IK Multimedia iLoud Micro Monitors. These have sound quality just as good as the Google at similar size, with the same DSP tricks, but have regular inputs and no smart features.

The second track is more obviously AI, mostly due to the high frequency "dullness". Likewise, the second link iBT051 seems to have the same issue, it's low fidelity (but in a different way than the lo-fi style is).

Perhaps the most interesting (though sort of irrelevant) part from a linked page on the site is that "cloud" storage is being sold as a one-time cost. A great deal (depending on price) if you ask me!

Overall, they found that the improvement was much smaller than I'd originally anticipated.

[1] https://www.rtings.com/microwave/learn/research/microwave-in...

[1] https://www.youtube.com/watch?v=Z0ZoCYXmF0Q

For example I remember amplifying the sound appeared to introduce some kind of extra delay and quality reduction that wasn't there before. I no longer have an iPhone to try this out with but I do wonder if someone knows whether these new features are still subject to this limitation.

It is very nice in that it gives you a handy diffing tool before you accept, and it very much feels like it puts me in control.

The command in question is ```bcdedit /set {bootmgr} bootshutdowndisabled 1```.

https://www.tenforums.com/antivirus-firewalls-system-securit...

I wonder how limited the preboot BitLocker screen environment really is. Could there could be some flag set by the UEFI that says "I'm a laptop and the lid is closed without power connected, shut down after a timeout".

I cannot imagine what the benefit of receiving notifications and other information like this on a Windows system would be. As far as I know, very, very few apps are programmed for the native "App" development flow (or even to use the notifications api) as opposed to "desktop" apps, and the number only gets smaller as you go into long tail enterprise apps. Perhaps this was designed for Outlook, but I think the use case is dubious.

Of course, there are millions of laptops in the wild, many of which are undoubtedly used by the people who work on Windows. Every time I find the laptop closed and running its fans, or find a computer in a bag that is slightly warm near the CPU (expected behaviour of working Modern Standby), I wonder whether it's just my computer or if it's every single one of them out there. Do people just accept that their computer has to be either shut down or will have an unknown amount of remaining power? It seems like there would have been a huge push to get this fixed if it was really broken, but I rarely hear users talking about it.

Of course I do wonder whether with the advent of the new Qualcomm ARM CPUs, whether they have finally managed to get Modern Standby to be a good clone of what Android devices do...

While it would be nice for the protocol to be documented (would realistically only be used by a very small number of users), the only real way you would be able to get a standard for something like this to work is if you went the Bluetooth route and did generic scenario-based profiles (e.g. HFP, A2DP, SPP), and optionally some "GATT" or "generic attribute" parameters. However, as we see with Bluetooth LE, everyone just uses GATT and implements their own little proprietary thing over it and you're back to the same problem.

Some of these systems attempt to be "smart" and just use the 24V C/W/Y1/Y2 etc protocol as a "standards compliant fallback". You don't necessarily lose ALL of the smarts, but the unit has to essentially use physics magic to make an educated guess about the information (for example, if you use a on-off thermostat, you can't really measure the temperature of the setpoint, so you don't know how close you are unless you somehow make an observation over many cycles.

I think that reasonable attempts to address this problem could involve some kind of extension to the old 24V interface - say, by offloading the actual "policy" part of system control to the "thermostat" i.e. have something that goes from 0-10V where 5V is off, 0V is full cooling and 10V is full heating. This allows you to choose your own temperature sensor situation, but complicates setups where more than one zone or thermostat is required. Of course, it will be very difficult for the industry to settle on a solution to this. Qualcomm's Quick Charge 2.0 was a very simple protocol similar to this, which was essentially self-documenting and not something that needed versioning, but of course, needs changed, 3.0 came and went, 4.0 came and went, and by the time USB C and USB PD came around you ended up with a full on data protocol API with all the OSI layers and of course, vendor specific extensions.

You could define some complicated protocol where you don't conform to a standard but you publish an API for your system (of course, there is no incentive to do this), and larger vendors like Control4 or Lutron, Crestron can program their products to interface with it. Unfortunately this doesn't allow the customer full choice over thermostats, because now you have to deal with N vendors x N thermostat vendors, which isn't scalable and you'll end up in dependency hell.

The closest thing I can think of to a standard, and the way it is solved in larger buildings, is through something called BACnet. It appears to use the Bluetooth model of "scenario based profiles", with all of the disadvantages that come with that, but the primary disadvantage is that it has to be to some degree manually configured to route data where it needs to go - and I don't think this is something installers are currently equipped to do at home scale.

Realistically, the "thermostat" is just a vestigial component in modern terms and really, it's just a user interface and thermometer now. Without getting into the wish to have open sourced app control or whatever, it's hard to define what the "thermostat" does and what the "system" is doing, and whether the device that sits on the wall is really a "thermostat" deserving of being interchangeable anyway. I have heard from a friend that does home automation integration that many clients don't like the default thermostat because it doesn't look very aesthetically pleasing. In this case, I'm definitely sympathetic to the need for customizability but it seems difficult to achieve in practice.

It's now out of warranty, but most of these units are built by either Gree (some Trane, Tosot, Gree, some Lennox iirc) or Midea (MrCool, Eco-Air, Senville, Pioneer, Carrier), so searching for the "canonical name" of your system can be helpful in finding parts. (usually, its of a pattern like "M5OG-48HFN1-M", can be found with meticulous googling for catalogs). There is a lot of parts commonality between units. You have to be creative with finding parts on AliExpress as they go by any number of names that you wouldn't expect, and a lot of this stuff is bought by eye (or random dimensions, of which there are some canonical ones for each part) and not by part number unfortunately.

The content of the course appears to be widely distributed for free elsewhere on the internet now on GitHub (unofficially). At least the last time I checked, there also exists cross references to LeetCode questions equivalent to their questions.

This may be useful information in case you decide you feel like cleaning the condenser fan, which may help the fridge work better and more efficiently.