Imported from yaap/system_update_engine (AGENTS.md). Install upstream with npx skills add yaap/system_update_engine. Copyright stays with the author.

Building and Running

m update_engine_nonetd to build
run scripts/reload_update_engine.sh to stop currently running update_engine and run locally built update_engine
If scripts/reload_update_engine.sh fails with .so errors, run adb push $OUT/system/lib64/*.so /data to push local .so to device.
python3 scripts/update_device.py <path to ota.zip> --no-postinstall to install OTA, look for onPayloadApplicationComplete(ErrorCode::kSuccess (0)) as an indicator for successful OTA install. If --no-slot-switch is passed to update_device.py, look for onPayloadApplicationComplete(ErrorCode::kUpdatedButNotActive (52)) instead.
On failed OTA install, use logcat adb logcat -d -s update_engine to inspect update_engine logs. logcat output tend to be long, so either pipe to a file or use tail command to check the last few lines.
Cleanup any install OTA with adb shell update_engine_client --reset_status

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install system_update_engine and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

system_update_engine

About

Building and Running

Use it

Install system_update_engine and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews