HMG-API 1.0.1

HMG-API 1.0.1 fixes one boot problem in 1.0.0. If you're on 1.0.0 with NEMESIS, update.

Fixed

• NEMESIS starts on time again. With 1.0.0, NEMESIS Manager showed "daemon not running" and no packages for up to two minutes after every start. Its services started late too, so packages that act at boot (for example one that dismisses the startup notice) could miss their moment. The cause was HMG-API's boot hook: it runs just before NEMESIS's own start, and one of its background jobs held it for two minutes. hmgapid no longer passes its open files to the commands it runs, so the boot hook returns at once. Thanks to @AwsomeFox for finding and fixing it (#74).

If the head unit was restarted during those two minutes a few times, HMG-API's boot guard may have counted those as failed starts and switched hooks off. The HMG-API app says so; Troubleshooting → The head unit restarted over and over has the reset.

Updating

From 1.0.0, either: put hmgapi-1.0.1-update.zip in HMGAPI/updates/ on a USB stick and use HMG-API app → Check USB updates; or unzip hmgapi-1.0.1-nemesis.zip onto a stick and update HMG-API from NEMESIS Manager's Package Store. Then restart the head unit. Your mods and settings stay. Nothing else changed: the mods, hook maps and catalogue are the same as 1.0.0.

Tested

• Diagnosed on a car: Hyundai Ioniq 5, US, 260507 (NEMESIS 1.16): NEMESIS's log and hmgapid.log showed the two-minute wait on every boot.
• Off the car: every test, including a new check that a background job can't hold hmgapid sh.
• The fix on a car: not yet. To check yours: after a cold start, NEMESIS Manager should list packages right away, and /data/nemesis/nemesis.log should show watchdog start early in boot again.

Known issues are the same as 1.0.0.

Reporting

Open an issue and attach a Car Report. Please don't post your VIN, serial numbers or phone numbers; nothing needs them.