viewer: use 'rfcomm -r' instead of explicitly invoking tty.setraw()
viewer: use 'rfcomm bind' to establish a persistent device

Using "rfcomm connect" on a per-connection basis seems kind of glitchy; the
rfcomm socket can go into a bad state.  It seems to be more reliable to use
"rfcomm bind" to establish a persistent device node.