<luca020400>
some weird shit is going on with a11y
<luca020400>
does he use some kind of screen reader?
<LuK1337>
maybe?
<luca020400>
it dies on virtual display handling
<luca020400>
maybe the fod layer?
<LuK1337>
eh
<LuK1337>
i think that's looking for "what causes it to look for accessibility paths"
<LuK1337>
rather than why would accessibility related code be broken in this way
<luca020400>
that's why I asked if a11y was enabled
<luca020400>
if it wasn't no idea why it went there
<LuK1337>
yeah, it only happens with screen reader
<LuK1337>
just repro'd
<LuK1337>
tho
<LuK1337>
i'm crashing in different place...?
<LuK1337>
09-27 17:27:57.981 6120 6120 E AndroidRuntime: at com.android.internal.widget.LockPatternView$PatternExploreByTouchHelper.getBoundsForVirtualView(LockPatternView.java:1636)