Closed jackokring closed 12 years ago
Well, why not but I'm honestly clueless on developing a bluetooth serial connection on Android :p
The rfcomm function encrypted one is the right one to use to keep API level 7 or lower. make the pairing not in the app and then BLUETOOTH_ADMIN permission is not required. I suppose best is to set up a server client which serves times of bit state changes, but this depends on the baud rate. Seems the way to go if the ROM is left independent. Not sure if intercepting a particular Saturn instruction is relevant, but it may be more effective. Anyone know which Saturn instruction is relevant for IR, and the serial for that matter?
An Xmodem notepad receiver and sender anyone? Just to complete the feature set? Would that be backed up on say Google? Is the network backup idea the best use of the serial?
I thought much about this, but a simple {home} file dump to a form load file could use would be best and most general. This file could be bluetoothed via the file browser application. It achieves backup and so I will close this issue, and raise another.
Not sure how easy this would be, but serial com seems to be in jni native files. Maybe the serial connection should be done the same too, or make the cable serial be a service for other android apps.
One other thing that may become a problem is the save in ondestroy(). What happens on battery fail within a call or unplug? maybe onpause() save would be better...