Settee shows its icon and name on older Fire TV Sticks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by checking the manifest's launcher icon reference and the resources in res/mipmap-anydpi-v26/, then review res/drawable/banner.xml and the linked Fire TV design constraints document. Add a launcher icon that resolves on API 24–25 and a raster TV banner that includes “Settee”; done means both assets are packaged for the older devices and the app tile and icon display in the Fire TV launcher.
Written by the indexing model from the issue text.
Description
Problem
Found while researching What does Fire TV require of an app's look, and what can its GPU afford? for the rebrand map (Map: Settee gets its own look).
- No launcher icon below API 26. The manifest's
android:icon="@mipmap/ic_launcher"exists only inres/mipmap-anydpi-v26/(an adaptive icon), but minSdk is 24. On API 24–25, e.g. a Fire TV Stick 4K 1st gen on Fire OS 6, there's noic_launcherresource to resolve. - The TV banner has no app name.
res/drawable/banner.xmlis a 320×180 dp vector with no text; Android's TV guidelines say the banner must include the app's name. It's also unconfirmed whether the Fire OS launcher draws a vector banner for a sideloaded app; a PNG banner inmipmap-xhdpiis the safe choice.
Expected
- A non-adaptive
ic_launcher(PNG or vector in plainmipmap-*/drawable) that API 24–25 resolves. - A banner carrying "Settee", as a raster the Fire OS launcher is sure to draw.
- Checked on a stick: the app's tile and icon show in the Fire TV launcher.
Notes
This is a stopgap with today's look; the rebrand map will replace the artwork later (logo, app icon and TV banner are in its fog). Details: docs/research/fire-tv-design-constraints.md on the research/fire-tv-design-constraints branch.
- Dominant language
- Kotlin
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 18m
- Merged PRs (30d)
- 73
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 neutraltone/settee
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
neutraltone/settee#157 ·
Maintainers usually reply within 1 day
-
Build Settee's lookOpenneeds-triage
Difficulty 5/5 Over a week Newbie friendliness 15/100
neutraltone/settee#172 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 15/100
neutraltone/settee#171 ·
Maintainers usually reply within 1 day
-
Remove Material 3Openneeds-triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
neutraltone/settee#170 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 57/100
neutraltone/settee#169 ·
Maintainers usually reply within 1 day
All issues in neutraltone/settee
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NucleusFramework/Nucleus#912 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
streetcomplete/StreetComplete#7364 · 7 comments ·
Maintainers usually reply within 1 day
-
assertions 🔍
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openwallet-foundation/multipaz#2161 ·
Maintainers usually reply within 1 day