Android Studio Rabbit 1 Canary 4 Fixes Layout Inspector Deadlocks and Device Mirroring Quality

Android Studio Rabbit 1 Canary 4 has been released on the Canary channel, paired with Android Gradle Plugin 9.5.0-alpha04. After the broader feature introduction of the earlier Canary builds, Canary 4 narrows its focus to reliability. The release concentrates on a handful of targeted fixes, the most significant being a deadlock in the Layout Inspector that could hang an app being inspected on a foldable device, and a quality issue with native device mirroring on some setups.

Layout Inspector Reliability on Foldables

The headline fix resolves a layout inspector agent deadlock that could throw the inspected app into an Application Not Responding state. The root cause traced back to the foldable support logic, which would block the main thread while holding a view layout inspector state lock. On a foldable device, the engagement with fold state can trigger the deadlock, and once it struck, the app under inspection would hang rather than respond to the debugging session.

This matters most for teams that debug on foldable and large-screen hardware. Foldables are increasingly common as testing targets for multi-window and adaptive UI work, and an inspector that can deadlock the app defeats the purpose of the tool. The fix removes the main-thread blocking and the lock contention, so inspecting layouts on foldables no longer risks freezing the target app.

Beyond the Layout Inspector, Canary 4 clears up a native device mirroring problem where mirrored output could appear low quality or pixelated, resembling a low-bitrate video stream. Clean mirroring is important for demos, for inspecting rendering details, and for anyone who records development sessions, and the correction improves the fidelity of the mirrored device display.

Toolchain Housekeeping

The build also bundles a round of toolchain cleanup. The Android Gradle plugin now uses a Bill of Materials for its BouncyCastle dependency rather than pulling in versions implicitly, which reduces the risk of version drift and makes dependency management more predictable. There is also a fix for a Live Edit test that was failing under specific JVM threading assertions, ensuring the live update validation passes consistently in the test suite.

None of these changes expand the surface area of the IDE; they all harden existing behavior. That is typical of a cycle settling toward release maturity. The feature story of Rabbit 1 was read out in earlier Canary builds, and each subsequent Canary is about eliminating the friction that testers and early adopters surface as they exercise those features.

For developers working in both Flutter and the Android toolchain, Canary 4 reinforces the usual cautions. Preview builds remain unsuitable for production work, and anything real should be built on the stable channel. At the same time, the fixes here are generally positive for Flutter teams that also maintain native Android code or test on foldables, since the Layout Inspector deadlock and mirroring fidelity both touch work that cross-platform developers commonly do.

As the Rabbit cycle presses on, the steady stream of Canary refinements points toward Beta and eventual stable release. Canary 4 is a modest but useful step, one that values reliable tooling over new features. For anyone tracking Rabbit 1, the message is to keep validating against the previews, report bugs when found, and expect the cycle to keep tightening before it reaches a stable conclusion.