Improve "Fix WiFi" app

[CRImier]

I just added ( db27713 ) a "Fix WiFi" app. Here's what it can do:

• Check if DKMS module is compiled, if not, show instructions on compiling it
• Check if esp8089 kernel module is loaded, if not, try to load it

Here's what else it should be able to do:

• [x] Distinguish between Zero+ESP and Zero W setups
• [ ] Add Zero W hooks:
  • [x] rmmod&modprobe the WiFi driver
  • [ ] Test
  • Disable power management - doesn't seem to be necessary on Zero Ws anymore
• [x] Add /boot/config.txt parsing
  • [x] Edit /boot/config.txt depending on which combo (Zero+ESP or Zero W) is used
• [x] Add dmesg parsing
  • [ ] Detect SDIO errors
  • [ ] Detect module failures
  • [x] Detect the "ESP not reset after reboot" bug ( https://github.com/ZeroPhone/Discussion-and-Research/issues/4 )
  • [x] Detect low-level MMC errors
• [ ] Add automatic DKMS driver reinstalling
  • Need to run apt install --reinstall esp8089-dkms, what's the best way to do that from ZPUI?
• [x] Add kmodpy to requirements.txt
• [ ] Attempt enabling 1-bit SDIO (can only help in case ESP is actually detected, need to test that)

[Fnux]

<_CRImier_> fnux: app inspired by you =) Will need to add config.txt and dmesg parsing to it
[...]
<_CRImier_> fnux: can add your dmesg log to the issue? IIRC there isn't any personal info there

Context: I had some wifi issues after soldering my first zerophone, see the attached dmesg log.

zp_dmesg.txt

[CRImier]

Thank you! To add some context, we couldn't fix @Fnux 's issue: config.txt is correct, the ESP pinout is also correct, and I didn't see any soldering mistakes on the board. So, this issue will have to be shown as "Unknown hardware/SDIO error" for now.

[CRImier]

Funnily enough, the behaviour of @Fnux 's ESP is the same as the behaviour of an after-reboot ESP. Wonder if that could be related in some way.