No mention has been made on a lot of the installs as to if they installed via the store, or an apk. The store looks at device type (tablet, phone, etc.), Android version, and perhaps other things to d

I said that they are a layer away - apps go through the system shared libraries to access kernel functions in most cases, so reallynare well isolated. 36 years in *nix as a professional, including Sys

Not really . . . apps need to be compatible with the runtime libraries (try to run something too new on a Linux based system, and the errors you getvare almost always symbol errors from libc, not incl

Failed to download, or failed to install/run? (The store/download does not care about the kernel, nor does much software other than drivers).

Loaded from the store, or an APK? The store restrictions have nothing to do with the APK, they are separate.

Likely just a setting in the store, and nothing to do with the program compatibility whatsoever.

Working here on Android 13, so that appears to be the cutoff.

That acts exactly the way I would expect a failed battery to behave, esp. since DFU mode does not eun anything that you flashed . . . Somewhat odd that it won't stay on if plugged in, but the charge c

Sounds normal. If Windows, have you loaded the DFU mode driver (It's not native in Windows) and as you have noted, DFU mode does notuse a COM port.)

ST Micro's Cube programmer is the mfg. supported programmer for the procesors in the Nano, and seems to work on any Linux I have tried. A bit larger footprint, but another excellent code load solution

Have you read the manual for DfuSeDemo? (If not, it's short, and I suggest that you do so . . . ) The direction of transfer is confusing . . . Despite 99.7% of the world thinking that an update would

The programmer will likely require you to open the unit and attach a cable internally (possibly install a header - not sure if there is one in all -H4 devices or not). What problem are you having prog

Does it still boot after this, or ??? If it does boot, it's not successfully starting the erase, as opposed to failing while doing it.

I'm not a fan of huge devices, but there is a bottom limit. The me, the H4 is "Tiny" and the H "borderline microscopic". Either of these would benefit from being a bit bigger, within reason, as i see

My apologies - those details were either absent from your post, or I missed them.

Mouser has about 10,000 of that exact part in stock . . . Can't get much more "drop in" than that . . . <https://www.mouser.com/ProductDetail/STMicroelectronics/STM32F072CBT6?qs=xf9JV0PLFEfBqXx8wKtR8A

If you do not have the NanoVNA in DFU mode (switch on with the rocker held) it will only come up as a COM port by design. The STM32 devixe is *NOT* a serial device . . .

Likely more would say that about Whinders . . .

Did you install the driver that came with dfuse demo? If not, that's the issue . . . Non-load uses a different driver, and not sure what Win11 sees without it . . . Cube is, though, a viable option, a

"provided drivers" Uh, by who and with/from what? I'd be very surprised if STMCube didn't support Win11, and it loads Nano code just fine. (If you are talking about the dfuse driver/tool, that has bee