Simlock ships its own Android device profiles
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- android, typescript
- 領域
- devtools, mobile-dev
調査の方向性
Start by reading the Android driver and the existing simlock doctor checks to see how profiles and SDK or devices.xml definitions are currently resolved. The issue names src/drivers/android/profiles/ and its index.ts as the new entry points; define the shipped profile set there and add the listed consistency and completeness tests. Done means shipped profiles are complete and unique, conflicts and missing recommended images are reported, and devices retain their creation-time config.ini.
索引モデルが issue の本文から書いたものです。
説明
The problem
Simlock has no Android device profiles of its own. A model name such as "Pixel 9" is whatever the installed Android SDK ships (avdmanager list device) or whatever the user's Android Studio ~/.android/devices.xml defines. That causes four problems:
- The same name can mean different hardware on different hosts, or not exist at all. A model is present only when the SDK is new enough, and
devices.xmlis per machine. A gateway routes by model name, so it assumes a name means the same device on every worker, and that is not guaranteed. - The default models for each class (
Pixel 9,Pixel 8, ...) work only if the installed SDK happens to ship them. - Two sources can define the same name, and they disagree (#341).
- A device created from a profile defined by properties starts from a seed SDK profile, and any hardware key the profile does not set keeps the seed's value. The device then depends partly on which seed was used.
Who runs into this
Operators who run more than one worker, or upgrade the SDK on one of them. Agents that ask for a model by name and expect the same device every time.
What you would like to happen
Simlock ships a small library of Android device profiles:
- One TypeScript file per profile in
src/drivers/android/profiles/(pixel-9.ts,medium-phone.ts, ...), plus anindex.tsthat imports them all. Listing the folder shows which devices Simlock ships. - Each profile gives the name, its other names, the class, and the complete set of hardware keys written into the device's
config.ini(screen, density, RAM, cores, keys, sensors, cameras), so the device never depends on the seed profile. Values are copied from the SDK's own profiles, so a name means the same as in Android Studio. - The library covers the default models for each class plus a few common screen sizes. Any other model still comes from the SDK or
devices.xml. - Library names win. A name that the SDK or
devices.xmlalso defines is reported bysimlock doctorinstead of being resolved silently. - A profile may name a recommended system image. It is only a recommendation:
simlock doctornames a missing one, and nothing is downloaded implicitly. - A device keeps the
config.iniit was created with, so changing a profile affects only devices created after the change. - Tests check that the folder and the index list the same profiles, that each file is named after its profile, that no name appears twice, and that every profile sets the full list of hardware keys.
Anything else
Planned Android slim emulators will want per-model values here, such as the guest RAM size for a slim device; that work is not filed yet. Related: #341.
Written by an agent.
- 主要言語
- TypeScript
- スター
- 19
- フォーク
- 1
- 平均マージ
- 7時間 21分
- マージ済み PR（30日）
- 247
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
callstackincubator/simlock のほかの issue
-
bug:new
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
callstackincubator/simlock#673 ·
メンテナーはふだん 1 日以内に返信
-
bug:needs-info
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
callstackincubator/simlock#657 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
callstackincubator/simlock#639 ·
メンテナーはふだん 1 日以内に返信
-
bug:new
難易度 3/5 1〜2日 初心者へのやさしさ 70/100
callstackincubator/simlock#672 ·
メンテナーはふだん 1 日以内に返信
-
Flaky console lane: CLI auto-launch's fixed 5 s deadline expires while a daemon starts on a loaded runner (ENOENT daemon.sock)対応中かも @V3RON が今日担当しました。 オープンbug:ready flaky-test
callstackincubator/simlock#663 · コメント 1 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
callstackincubator/simlock の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
polarsource/polar#15580 ·
メンテナーはふだん 1 日以内に返信
-
accepted bug via-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 69/100
pingdotgg/t3code#20931 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug/1-unconfirmed kind/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 83/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ranxianglei/billion-context#3583 ·
メンテナーはふだん 1 日以内に返信