Another issue is semi-compliant ONVIF implementations for PTZ cameras and/or not having relative movement implemented. Or you know, just lacking RTSP and ONVIF entirely.

> Coupled with the fact that many brands are just using the same recycled white-label Chinese firmware, I'm not surprised.

SDKs for many of the SoCs not being available is really annoying as well. Some of the Ingenic, Sigmastar, Goke etc. are available, but I think many were just leaks from customers rather than intentional releases.

Soon?

I've already seen multiple of TP-Link's firmware engineers leave their LLM history public and indexed by search engines.

It's quite obviously them as well.

Australia has a national test of it's phone alert system in 10 days at 27/07/26, 2PM AEST. (People in North America would know it as Cell Alerts/Presidential Alerts etc.)

There have been warnings that hidden phones will almost certainly sound, and their recommendation is to ether power off the phone or put it into airplane mode at least an hour before the test...

Quite a few of the modules went out without their eeprom programmed correctly, and all of them appear to be plagued by quite mediocre performance from (alleged) inadequate RF shielding on the card.

It looks like they've revised the design, but it's peeved off quite a few of the Banana Pi/Sinovoip customers who have bought them with the intention of using it as a router/ap with their R4. (It's dual-PCIe fingers with unique spacing and requires out of spec PCIe voltages, so it's only practically usable with a BPi R4.)

At the very least, the customers using them as wired-only routers are likely to be having a slightly better experience.

It went down as well as about you would think it would.

[1] https://www.eff.org/deeplinks/2017/07/australian-pm-calls-en... (2017)

If I recall, I had a fairly decent view of their various checks because it was delivered completely unminified, including a couple amusing sections and unimplemented features. (A gesture detector with the middle finger gesture in the enumerable commented out, for example...)

Another attack vector that I speculated upon was intercepting and replacing their tflite model with ones own, returning whatever results required.

Additionally, I believe they had a check for virtual camera names in place, as checks would quietly fail with a generic message in the interface, but show the reason as being virtual camera within responses. (Camera names are mutable though, so...)

While I don't recall Sony issuing an advisory, I believe the users of their app would have started getting update notifications since they (quietly) released firmware updates.

> This means there is great opportunity for Linux users to control their Bluetooth headsets, which for example is quite nice in an office setting to toggle "hearthrough" when toggling volume "mute" on your machine.

I think most vendors are using custom services with their own UUIDs for settings such as this.

Regardless, I believe there are open client implementations for some of the more popular devices. Gadgetbridge comes to mind in regards to Android, not sure about any Linux equivalent.

Ark is a strange case. It compresses very very well. Most of it ends up with compression ratios of around 80%.

> Total size on disk is 628.32 GiB and total download size is 171.42 GiB.

From SteamDB's summary of Ark's content depots.

It did a great deal more than that. It also allowed the toggling of VoNR, which apparently affected the fallback behavior of some people's services. (Ie. It would fall back to LTE and not roam back to 5G data unless nudged manually)

However for me, it would enable backup calls over a secondary sim card's data, which would allow text and calls overseas without the usual extortionate charges. Oddly enough, I believe that toggle is enabled for my carrier... but only on iOS.

Eg. ALDI (yes, the German supermarket chain run a MVNO in Australia), have been saying esim support in the future since 2021.

If I imported one, the majority of the handsets released before this year wouldn't be able to register on a network, given that the networks have gone and blocked the IMEI TAC associated with most of Sony's handsets.[1]

This is due to Sony not having the correct carrier settings in order to roam onto them for emergency calls, and a ham-fisted direction to have working emergency calls post-3G shutdown.

[1] https://isthisphoneblocked.net.au/device-brands/sony

The paperclip was just the easiest way of triggering RCM, which is a standard feature on Tegra. The vulnerability lay in that they didn't bounds check certain types of USB requests properly.

I would have thought they'd do some mixing based on serial number or chip id as a baseline.

Or at least that's what the hash of their SBK implies.

I do enjoy seeing the boot chain on Tegra get broken yet again though.

You would have to drop the other ports instead, and then you would just have 2x 10G SFP and a gigabit switch. Which is exactly how the BPi R4 is configured.

Which tends not to be great for a tv one wants to use with a Chromecast or similar media box...