[Connected Car] donaldta:
I disagree since the Bluetooth 2.0 stack on the Parrot isn't very power efficient. So, you can end up having to constantly change out the Bluetooth keyboard's batteries quite often especially if you accidentally leave it on. Logitech's Unify communication protocol is less demanding than Bluetooth stack and doesn't constantly check if the device is enabled. This allows the Logitech devices to maintain longer use on the batteries. And in fact, the keyboard that I use is rated for 3 years on batteries. So far, I haven't had to change it and have left it on for over two years and have used in on many different devices. That is something that I have never experienced with a Bluetooth keyboard.

Besides, the Smart is only capable of pairing two devices. And though I'm not sure about the availability of USB slots on the SCT, for the Smart there are plenty of them.

In order to pair a Bluetooth ODB2 device on the earlier ROMs of the Asteroid Smart, we had to use Bluetooth Auto-Pair. Not sure if it is the same with the SCT.

I don't like running find against "/" on a running system. A lot of the virtual directories get in the way. And although I know how to skim them out, its just not a practice I like to do in general. Besides, I've already modified my Smart that you cannot consider it "stock". However, I did modify my original file checker script to check the files between the Asteroid's PLF vs SCT's PLF. Maybe you can use its output to find out what you need. I'll include its output as an attachment to this post.

knoppix@Microknoppix:~/Downloads$ ls -ld */*/FileSystem/
drwxr-xr-x 4 root root 96 Nov 5 14:21 SCT/v1.47.88/FileSystem/
drwxr-xr-x 4 root root 96 Nov 5 14:25 SCT/v1.47.96/FileSystem/
drwxr-xr-x 4 root root 96 Nov 5 11:22 Smart/v2.1.2/FileSystem/
drwxr-xr-x 4 root root 96 Nov 5 11:22 Smart/v2.1.4/FileSystem/
knoppix@Microknoppix:~/Downloads$ cat check_diff
date > output_checkdiff.txt
for i in `find Smart/v2.1.2 -type f`
do j=`basename ${i}`
k=`echo ${i} | sed 's#Smart/v2.1.2#SCT/v1.47.88#'`
echo ---${j}--- >>output_checkdiff.txt
diff -q ${i} ${k} >>output_checkdiff.txt 2>&1
done
knoppix@Microknoppix:~/Downloads$ ./check_diff
knoppix@Microknoppix:~/Downloads$ grep differ output_checkdiff.txt | wc -l
152
knoppix@Microknoppix:~/Downloads$ grep such output_checkdiff.txt | wc -l
309
knoppix@Microknoppix:~/Downloads$

Basically, I have the Smart and SCT's PLF file uncompressed in their own directories. And the script will check for differences or missing files. From a brief overview there are 152 files on the Smart that differ and 309 files which do not exist on the SCT.

Here's an excerpt of the output file.

---dbcloned---
diff: SCT/v1.47.88/FileSystem/system/bin/dbcloned: No such file or directory
---watchprops.symlink---
---G711EncTest---
Files Smart/v2.1.2/FileSystem/system/bin/G711EncTest and SCT/v1.47.88/FileSystem/system/bin/G711EncTest differ
---umount.symlink---
---df.symlink---
---netstat.symlink---
---logwrapper---

In the above, you can see that the "dbcloned" file does not exist in the SCT version and the "G711EncTest" file differs from the Smart. The rest of the files; "watchprops.symlink", "umount.symlink", "df.symlink", "netstat.symlink" and "logwrapper" are all the same.