Skip to content
Apple tested a ‘complication column’ for the iPhone Duo Lock Screen, per leakMappleCare Community ↗

Apple tested a ‘complication column’ for the iPhone Duo Lock Screen, per leak

By admin • • 3 min read

The iPhone Duo’s dual-display topology necessitates a fundamental restructuring of the Lock Screen’s spatial rendering pipeline. Traditional single-plane complication layouts—governed by the LockScreenPlugin extension point and WidgetKit timeline providers—assume a contiguous rectangular canvas. The reported “complication column” architecture introduces a dedicated vertical strip anchored to the hinge-adjacent bezel region, effectively partitioning the Lock Surface into primary content and persistent metadata zones. This column leverages a new DualDisplayLayoutEngine subsystem that calculates safe-area insets dynamically based on hinge angle sensor fusion data, ensuring complication legibility across folded, flat, and tented postures without occluding the time/date cluster or notification stack.

Engineering the column required modifications to the SpringBoard’s SBLockScreenViewController composition hierarchy. The column renders as a separate UIWindowScene layer with independent trait collection overrides, allowing complications to adopt compact horizontal size classes while the primary canvas retains regular width. Data freshness is maintained via a dedicated ComplicationColumnTimelineScheduler that prioritizes high-frequency providers (weather, activity rings, live activities) at 30-second intervals, while deferring lower-priority widgets to the standard 15-minute budget. Touch handling routes through a new UIGestureRecognizer subclass that discriminates between column taps—launching the associated app via LSApplicationWorkspace—and swipe gestures reserved for notification dismissal on the primary surface.

Key Engineering Takeaway: The complication column decouples persistent metadata rendering from the primary Lock Screen canvas, enabling glanceable data density without compromising notification hierarchy. This spatial partitioning is a direct architectural response to the dual-display form factor’s asymmetric bezel geometry.
← Scroll table horizontally on small screens →
Subsystem / Parameter Baseline / Previous Updated Implementation
Complication Layout Engine Single LockScreenPlugin canvas; grid-based placement Dual-layer DualDisplayLayoutEngine; dedicated column UIWindowScene with hinge-aware safe insets
Timeline Scheduling Policy Unified 15-minute minimum refresh via WidgetKit Tiered scheduler: 30-second high-priority tier for column; 15-minute standard tier for primary canvas
Touch Event Routing Global UITouch hit-test on SBLockScreenViewController Column-scoped gesture recognizer with discrete tap-to-launch; swipe reserved for primary surface notification dismissal

Actionable Diagnostic & Implementation Steps

  1. Validate hinge-angle sensor fusion calibration by querying IOHIDService for AppleEmbeddedAccelerometer and AppleHingeAngleSensor streams; confirm kIOHIDPrimaryUsagePage 0xFF00/0x0001 reports map to UIDeviceOrientation transitions within ±2° tolerance.
  2. Profile column timeline scheduler latency using os_signpost intervals around ComplicationColumnTimelineScheduler fire dates; verify high-priority providers execute within 500ms of scheduled wall-clock time under thermal pressure.
  3. Stress-test gesture discriminator by injecting synthetic UITouch sequences via XCUITest at hinge boundary coordinates; assert column tap launches target bundle identifier while swipe gestures propagate to SBNotificationCenterController without false positives.

Ecosystem Compatibility & Support Notice

  • Requires iOS 19.0+ with DualDisplayLayoutEngine entitlement (com.apple.springboard.dual-display-layout)
  • WidgetKit extensions must declare NSExtensionPointIdentifier com.apple.lockscreen.complication-column in Info.plist for column eligibility
  • Hinge-angle sensor fusion available only on iPhone Duo hardware (device identifier iPhone17,5 / iPhone17,6)
  • Third-party complications limited to two column slots per developer team ID to prevent metadata crowding

Source and technical reference: 9to5Mac.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Still running into this issue on your iPhone or Mac?

Share your OS version, device model, and exact error code in our independent peer Q&A rooms.

Ask in Community Forum →
Ağ Bağlantıları:MacBook • Teknoloji • Donanım Rehberi • Elektronik • Soru Cevap
\n\n