Requires a cross-compilation fix for fbterm (nixos/nixpkgs#72107).
This may stop the display-manager from starting correctly, I think it
prevents X from automatically switching to the correct vt. Requires
some further investigation :)
Anchoring ourselves to an external project, at this point, is not
feasible. This does not allow us to explore making better use of the
capabilities of nix.
Though, a mechanism using third-party resources, like the postmarketOS
device information, is something that is desirable. The difference is
that it would need to *import* the information in the format used by
mobile-nixos, rather than mobile-nixos importing the information from a
"data dump".
* Move adb to a separate module. It used to be in stage-1, but it is no
longer stage-1 specific, as it is now started in stage-2 as well.
* After switching to stage-2 kill the old adbd and start a new one.
This is dumb... These are all android/google/qualcomm/asus "features"
added to the kernel with no concern about actually being compatible
with the kernel. They all assume no USER_NS stuff.
Fun!
libinput, which I believe, claims there is a kernel bug with the
synaptics driver touchscreen in use.
This is the recommended fix according to PostmarketOS.
* https://wiki.postmarketos.org/wiki/Troubleshooting:touchscreen#sec_touchscreen:_kernel_bug
I have not seen any issues from using this fix.
The error:
```
synaptics: kernel bug: device has min == max on ABS_MT_WIDTH_MAJOR
```
According to the touchscreen documentation of the kernel, I don't think
that it is an issue to remove this information from touch events.
The `-I` was accidentally left over.
I prefer assuming `<nixpkgs>` resolves to what is needed (a recent
nixos-unstable checkout) rather than forcing the users to checkout
nixpkgs into this project as I personally do.
Close#22Close#25
The gist of it:
* The "adb" function is not available (-22, EINVAL) on asus-z00t
* Enabling both adb and ffs breaks asus-flo
* Enabling ffs is fine with asus-flo.
So I guess it's ffs that enables adb!
