Using the serial example I have found following behaviour.
1) if Bluetooth is NOT enabled on Galaxy TAB then app installs fine and asks me to enable Bluetooth and then all runs fine.
2) if Bluetooth IS enabled on Galaxy TAB then app times out on installation to device and suggests I abort install. The Galaxy TAB is then hung and in some weird state. Have to hold the power button to OFF device a few times and then eventually it powers down and re-boots.
Maybe not a bug but a limitation.
Once app is installed it works fine... so just have to turn Bluetooth off between installs during development and it is stable.
1) if Bluetooth is NOT enabled on Galaxy TAB then app installs fine and asks me to enable Bluetooth and then all runs fine.
2) if Bluetooth IS enabled on Galaxy TAB then app times out on installation to device and suggests I abort install. The Galaxy TAB is then hung and in some weird state. Have to hold the power button to OFF device a few times and then eventually it powers down and re-boots.
Maybe not a bug but a limitation.
Once app is installed it works fine... so just have to turn Bluetooth off between installs during development and it is stable.