iOS: hinge control and fold state for leased iPhone Duo simulators
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 45/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- ios, typescript
Direzione di ricerca
Start by reading the input socket handling for hinge control (0x10) and the existing fold support through agent-device described in the issue, along with related issues #1013, #1019, #1531, and #1534. Trace how stream size changes reach clients and where input and stream metadata are defined. Done means leased iOS Duo simulators accept hinge control and report hinge support, pose or angle, and active screen to clients.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The problem
A client that shows a leased iPhone Duo can't control its hinge, and can't tell which pose it is in.
- Hinge control isn't implemented. The input socket answers hinge control (
0x10) with{ok:false}on every platform (#1013), and #1019 left "Duo devices and their hinge" out of scope. - Folding works, but only through agent-device.
agent-device fold open | closed | half-openworks through the agent-device front, and since #1531/#1534 the stream follows the panel in use and changes size on a fold. - The stream reports only the picture's size. It doesn't say that the device is foldable, its pose or hinge angle, or which screen is in use.
As a result, T3 Code's Device panel turns its iPhone Duo 3D view off for pool devices, and draws the unfolded inner panel (720×506) into a portrait frame, squeezed about 2× (pingdotgg/t3code#38343). T3 Code's own device hub gives it these fields for local simulators: supportsHingeAngle, hingeAngle (0 to 180), hingePose (closed, book, open, laptop, tent) and screenId.
Who runs into this
A developer building an app for the iPhone 18 Pro and the iPhone Duo. A Mac mini M1 runs Simlock 0.8.0 (gateway and worker side by side, with one slim iPhone 18 Pro and one slim iPhone Duo kept warm). A T3 Code environment on another Mac leases from it over Tailscale, and builds and serves the app (Metro) from there. Agents drive the devices with agent-device. People review the UI in T3 Code's Device panel, which is where folding by hand and seeing the true unfolded shape matter.
What you would like to happen
-
Hinge control on iOS foldable simulators.
0x10sets the pose or hinge angle on a leased iPhone Duo and answers{ok:true}, asagent-device foldalready can. -
Fold state reported to stream and input clients:
- that the device supports a hinge;
- its current pose or angle;
- which screen is in use.
This would ride beside the existing mid-stream size change, so a client can draw the right frame and its own fold controls.
-
Optionally, a flag on the lease or device saying it is foldable, so a client knows before the stream opens.
Anything else
- Versions: Simlock 0.8.0, agent-device 0.21.36, Xcode 27.2 (27B52), runtime
iOS-27-2-iPhone19-4(24B91016s), macOS 27.0.1 on the worker. - Today's workaround: fold with
agent-device foldfrom the agent's machine. For a person to fold by hand, or for a 3D view, use a local Duo outside Simlock. - Related: #1013, #1019, #1531, #1534, #1559, #1539 (orientation on an iPhone Duo through the agent-device front).
- Lingua principale
- TypeScript
- Stelle
- 705
- Fork
- 40
- Merge medio
- 12h 9m
- PR unite (30g)
- 376
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di callstackincubator/simlock
-
request:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
callstackincubator/simlock#1806 ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
callstackincubator/simlock#1780 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
task:draft
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
callstackincubator/simlock#1441 ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
callstackincubator/simlock#1805 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
callstackincubator/simlock#1804 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di callstackincubator/simlock
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Update project links after the repository renamesForse già presa @JonathanTSilva l’ha presa oggi. Apertaai-generated priority: p2 size: xs type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
JonathanTSilva/jts-website#119 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
promplate/code-review#158 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existForse già presa @franpts2 l’ha presa oggi. Apertadocs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 3 giorni