[whpalmer4]

I hadn't noticed this previously (don't use the BT keyboard often with OF) but had no trouble reproducing it.

I've proposed a change to the search behavior that should fix this, I think. The doubled characters only seem to happen during the part of the search where there are many candidates to match against. If you copy and paste a string into the search field, you get essentially instant results (in my database, it takes 18 seconds to get a response after entering a search string of "e", but if I paste in "ew" I get a result in less than a second). My proposed change is that the search facility not start searching until either two characters have been entered, or it has been half a second since the last character was typed. This would make the case of a search for one character take half a second longer, but make the interactive search as fast as a non-interactive one for the interesting case. If you want to vote for this idea, the bug number is OG #572190.