Had some time to do some luggable research today. Wall of text incoming for people who might be interested in that kind of project and/or have any input:
When you start thinking about projects like this you first need to think about what your goal really is because it's very easy to get lost in "nice-to-haves" and lose sight of what you really wanted to do. I want a mobile system that works well as a linux almost-text-only, minimalist system with very long battery life. Minimalist graphic interface via X, very lightweight software. Emacs is about the heaviest software I wanna run. Network accesses do happen, but mostly on the level of ssh, APIs and server services = social media or internet browsing is not required/wanted. A little bit of multimedia would be a nice to have, as in viewing PDFs, creation of pixel art via lightweight programs like
grafx2, and looking at pictures. Old DOS/Amiga system emulation would be great. Video playback and streaming is not necessary. Most of the older SBCs top off at around 2-4 GB of RAM which is a bit tight but not impossibly so and not with a lightweight customized Linux, especially if you don't wanna do any webbrowsing or (modern) gaming. A SBC with onboard eMMC (min. 16 GB) and wlan chip would be ideal, as SD cards can be unreliable and suprisingly power hungry. I might want to add an USB modem later. The speed of the interfaces doesn't really matter much.
Some napkin math later and I don't think the S992X can be "it": It's too power hungry and also gets quite hot under load and in an enclosed space that's gonna be plastic, you'd need some active cooling to make it run stable under sustained loads in varying climates, which could happen, which again, uses power. I don't want to do this "edge of the seat" calculation many notebook manufacturers seem to do and want some more robust numbers that rather overshoot than undershoot, so I calculated with about 18 hours of runtime, 90% conversion efficency from 3.7V cells, with a margin of 20% (to account for cell aging/imperfections and misc. losses) and not even idle or average power consumption of the system, but 18 hours at full CPU load of all cores. This limits the SBC I can use to about 3W at full load with 3.7V ~40 Ah of battery which is in the ballpark of amount of battery I'd be comfortable using (You kinda don't wanna stack batteries endlessly even if there's space). If we consider the screen of the system to be always on and consume about 3-4W of power during that time, too. Again, napkin math. This number will increase with periphery hardware. An upside of ARM SBCs is that you can edit their device tree files and sometimes experiment with underclocking and undervolting, which might make it possible to shave off a few mAs here and there with no ill effect, power consumption also usually rises, sometimes quite dramatically, towards the top end of the clock speeds and there might be some measurable gains to be made here.
A possible SoC as of here and now is the Allwinner
H618 (28 nm, 4xCortex-A53 e.g. Orange Pi Zero 3, 4 GB of RAM, not fully mainline supported yet but Sunxi has a proven track record of making it happen) the RK3566, (22nm, 4xCortex-A55 e.g. Odroid-M1S, 4 GB of RAM, 64 GB eMMC, and also an m.2 slot which would probably consume too much power, the extend of the mainline support seems to be "full"? It is slightly unclear for me here right now) the Amlogic S905X3 (12nm, 4xCortex-A55 e.g. Odroid-C4, 4 GB of RAM, eMMC slottable) or Amlogic S905Y4. (8nm, 4xCortex-A35 e.g.
Vim1s - I fell in love with this thing and felt I could make 2 GB of RAM work before I realized it's vendor kernel only! Sadly no mainline support for that generation of Amlogic SoCs. Besides a one liner of "an ongoing effort happening" could not find a hint of it ever coming either, this thing idles at 0.5W!) These are low end ARM SoCs, meant for things like cheap "Android TV" boxes. Not an Option: Raspberry Pi 4-5 - too power hungry, too hot (shocked at the power consumption numbers under full load of the Pi 5. Seems to be easier to just use an x86 system at that point). Pi Zero 2W - only 512 MB of RAM. Rule of thumb: If an IC has a metal heatsink/"lid" glued from the factory, it's because it's hungry and gets considerably hot to the point of straight up dying without. I haven't fully looked at everything there is yet, and this odroid heavy list is that way because it's surprisingly hard to find any reliable power consumption numbers for ARM SBCs. Hardkernel are pretty much the only ones that seem to bother with making measurements and publishing them, which is odd considering usage scenarios for these often are critical in that department I'd assume. Must be the well-known chinese allergy re: publishing measurements of any kind. I noted the process sizes because these translate directly to idle power consumption as far as I can see. These all overshoot my budget of 3W by several hundred mW (except the S905X3/C4) the one closest of fitting into it is unsurprisingly the Vim1s, which actually undershoots the 3 W by all accounts I could find (~2.5-2.8W). I might wanna look into older SoCs, both for better mainline support and also for lower power consumption.
I'm also almost tried to attempt to use the Vim1s with vendor kernel just because of how snugly it fits into my power consumption bracket, even though I am sure I would regret it later. They're on some ancient 4.15 kernel that's not even LTS anymore and has a list of unaddressed CVEs. Practically, it already starts with having no 2D acceleration whatsoever in X, which might be fine for lower screen resolutions but doesn't exactly feel like a good idea. Then again, this thing is no server and runs no "webapps" so the attack surface for old kernel CVEs might be limited. Famous last words?
Brings me to the screen and some more napkin math. eink is most likely not an option and also conflicts with some of the goals so we'd have to go with an LCD. The best way to save power with a normal lcd panel is to reduce it's size. (= less backlight LEDs) The screen should at least feature 80 columns and 25 lines with a 8x16 bitmap font (A bitmap font is chosen because these are always sharp and readable, 8x16 because that is pretty much the standard size of old and would give me a wide array of fonts to choose from). This font should also be comfortably readable at 50 cm of distance without (GPU) expensive upscaling so the screen can't be too small or too high of resolution. All programs will be run without window decorations and full screen with a WM like ratpoison so text applications will fill out the screen. In your average book, a letter is about 2.5-4 mm tall. Aliexpress has cheap 8" 800x600 panels that according to datasheet, have a typical consumption of about 2 Watts + ~1 W for the control panel. On an 8" 800x600 panel, the pixel density would be ~125 PPI. a 8x16 bitmap character would be about 3.25mm tall on this screen. Very readable. 100 columns, 37 rows. Sadly, this is not a great screen otherwise. Color reproduction will be poor and there's also only one real angle you will be able to see anything at. PDFs and other "multimedia" will be hard to look at. Aliexpress also has 1280x800 IPS screens at 8". These have ~188 PPI. IPS has good color reproduction and angle stability, the resolution (and form factor) would even be good for videos. Downside: an 8x16 character would only be ~2mm tall. Over a prolonged period, this would be an eyestrain. We could double the size of the characters (16x32) which would make them nice and readable at around ~4mm, then we could fit the classical 80x25. Yes, I'm aware these would be very small screens, but honestly, I don't think I would mind much. Biggest problem would be covering the pdf requirement which doesn't scale well to such things, but I might drop it altogether.
Not that simple a project if you don't want to end up with some useless gadget with 2 hours of battery life. What's mostly making it difficult is the spotty linux support/documentation of many of the ARM SoCs. Even "good" support is often anything but, as important features are just plain missing or work poorly. The older SoCs you take, the better the support usually gets. Android is king with these things and almost all of these SoCs have flawless android support, but if I wanted that I'd just buy a tablet. It also needs to be stressed how inefficent these ARM SoCs are compared to an e.g. Apple M1. Well, it's low end, minimalist computing. Always fun to work with the limits.