https://www.tomshardware.co.uk/raspberry-pi-4-everything-we-...
It seems like the issue is current spikes, and those can occur under far more conditions (HDMI, external USB devices, etc.).
I suspect that beefing up the power system filtering would reduce the power supply maximum current requirements quite dramatically.
The Beaglebone Black guys seem to work inside a 5V 500mA envelope quite well. At the very least, they don't seem to have anywhere near the issues that the RPi folks seem to.
Can you be more specific? "Full HD" usually refers to 1080p, which all Raspberry Pi models can easily handle for h264 video due to their hardware decoder. The Raspberry Pi 3 can handle most other formats through software just fine, though it may struggle with more intense formats like 10 bit h265. For that, an Odroid C2 may be what you're looking for. They advertise:
>H.265 4K/60FPS and H.264 4K/30FPS capable VPU
It doesn't have that much RAM but they have models with 8 core CPUs, USB3, and one with SATA. They're around $50.
In my opinion they should severe ties with Broadloom and open up to global competition.
Given the complexity of the modern software stack, there have been a zillion bugs that have ruined someone elses day and have been hopefully fixed.
Although, I have no idea of the support quality of the Pi foundation since I have not used their products.
The platform is sufficiently beefy to run lot of non-trivial applications. It's not like those applications have magically increased in complexity.
We've just been brainwashed in the consumer space to always demand bigger numbers so that the vendors have something new to sell. There is really no need for a certain category of desktop applications to get any slower with time, or, to be able to provide any more value regardless how fast they are run if the interactivity level is already so fast that improvements would be undetectable by humans.
Note: this is not an argument that the current Pi "is fast enough for everything". I'm saying it's fast enough for some things, and the mature software stack is considerable added value.
The big ones, in my opinion, are the write-limited, slow SD card interface, the microUSB power connector, the 1GB maximum RAM, Ethernet that shares bandwidth with USB, and ever-increasing power requirements.
I think the Pi Foundation wants to churn out more new units by increasing the CPU speed, but with the super slow SD interface and the capped-out RAM, performance hasn’t made significant improvements in a long time.
I also think it was a bad decision to not focus on open-source software with the Pi. They have been including proprietary user space applications forever (Mathematica, for instance), the GPU boots a proprietary ThreadX operating system that has DMA and complete CPU control, and the thing requires lots of binary blobs to boot. The education aspect (particularly as a low-level programming platform) would have been made more accessible without such an opaque boot process.
Not that I disagree, but as a counterpoint learning programming with Scratch has very little to do with getting to know the implementation details of the underlying computational substrate. I'm a software professional and I can't bother with that stuff! I'm far more interested in fiddling with my programs than tweaking the underlying substrate. I don't think this is a stance everyone should take but I don't feel a worse person because of it. I can administer my own machine but I don't enjoy it.
I don't by contrast program on my phone because it just feels like a gimmicky toy.
I'm not saying the raspberry pi is anything like a phone in this regard, but in does have a limit to how far you can dig, and that's a real shame.
Is it limiting to the scratch programmers? Probably not, but the Scratch programmers read about and move on Python, who then move on C. But if the boot process isn't open, there isn't anyone to write about it, so people don't discover it. Which for an educational endeavour is problematic.