How Can A Gpiocallback Register "false" Twice In A Row?

I have a very simple setup android-things setup where a GPIO (output) generates very short (10u) pulse, and I'm trying to read that pulse through another GPIO (input). However, my

Solution 1:

Yes, this is fairly common with noisy input signals like pushbuttons, relay contacts, and "wiggly wires". The signal bounce that occurs during contact closure can happen very rapidly such that not every edge trigger event is captured by the input registers.

This is true of all GPIO systems (not just Android Things), and one reason why signal debounce is such a common practice. The debounce code in the button driver was actually written to handle cases like this to ensure they didn't generate false events.