Android quotes a 70 s boot for a 4 s snapshot restore
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- android, typescript
- Domain
- mobile, performance
Research direction
Read src/drivers/android/index.ts around estimate() and the boot estimate constants, then check the snapshot selection described in src/drivers/android/AGENTS.md and the stalled-transition threshold in src/core/doctor.ts. Update the estimate and threshold behavior to reflect snapshot boots; done means snapshot boots are quoted near their measured duration and stalled snapshot boots are detected on an appropriate timescale.
Written by the indexing model from the issue text.
Description
What happens
The Android driver quotes 70 s for every boot, including a boot from the clean baseline snapshot, which it measures at about 4 s.
Where
src/drivers/android/index.ts:88COLD_BOOT_ESTIMATE_MS = 70_000;:124SNAPSHOT_BOOT_ESTIMATE_MS = 4_000.estimate()atsrc/drivers/android/index.ts:1347-1352returnsCOLD_BOOT_ESTIMATE_MSforbootwhatever the device's snapshot state; the 4 s figure is used only as a diagnostic threshold (:2038-2039).makeReadyboots fromsimlock_clean_baselinewhen the stored hash matches (src/drivers/android/AGENTS.md, "Boot" step 1).
What a user sees
A waiting requester is quoted estimatedBootMs: 70000 for a boot that takes seconds, and doctor's stalled-transition threshold for a snapshot boot is sized for a cold one (src/core/doctor.ts:1022), so a stuck snapshot boot is flagged late.
Found
Exploring the warm pool for #771 on 2026-10-20, at commit 97bc8eaf.
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 2
- Avg merge
- 8h
- Merged PRs (30d)
- 316
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstackincubator/simlock
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/simlock#817 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 · 1 comment ·
Maintainers usually reply within 1 day
-
task:draft
Difficulty 4/5 3-5 days Newbie friendliness 35/100
callstackincubator/simlock#839 ·
Maintainers usually reply within 1 day
-
task:ready
Difficulty 5/5 Over a week Newbie friendliness 35/100
callstackincubator/simlock#838 ·
Maintainers usually reply within 1 day
-
task:ready
Difficulty 4/5 3-5 days Newbie friendliness 57/100
callstackincubator/simlock#837 ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
zts212653/clowder-ai#1678 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Progressive-Victory/the-website#680 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100