Android: milestone 1 device runbook
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, csharp
- Domain
- mobile-dev, testing-qa
Research direction
Read Android plan task B8 and the related platform roadmap (#100), along with dependency issues #255–#261, to find the plan where the runbook and results belong. Record the requested device details and run each listed lifecycle and sustained-run scenario on a Galaxy S24 FE. Done means the runbook and filled milestone 1 results are committed to the plan.
Written by the indexing model from the issue text.
Description
Current State
Milestone 1 requires a textured scene that survives backgrounding, surface recreation and relaunch on the Galaxy S24 FE.
Tasks
- Write the runbook: background/foreground x20, rotation x10, lock/unlock, notification shade, relaunch after force-stop, 30-minute sustained run with FPS and thermal notes
- Record model, GPU and driver per run
- Fill it for milestone 1
Acceptance Criteria
- Runbook and filled results committed to the plan
Related
- Android plan task B8 · seniority Jr · local-only on
feat/android-platformuntil .NET 11 GA and CI support - Depends on: #255, #256, #257, #258, #259, #261
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:engine c:scripting p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:assets c:platform p:low size:M t:feature
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
c:platform c:scripting p:low size:M t:task
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:docs good first issue p:low size:S t:docs
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
area:re1 bounty help wanted needs-game
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
StackExchange/StackExchange.Redis#3274 ·
Maintainers usually reply within 1 day
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days