[Captivate Android Development] no driver:
This is working with a previous backup of JH2 before I did any lagfix. As you can see, the chown at the end works. I did ls -l calls at each step to see what was different and it appears to my untrained eye that ownership of the file is always system.system, so maybe that last chown isn't necessary? I haven't noticed any problems with my current setup, where the chown failed, but I'm not sure what I should or shouldn't be able to do if there is a problem with the file ownership. Please let me know what to test to see if there are any problems.

>adb shell
$ ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw---- system system 49152 2010-08-19 10:31 settings.db
$ exit
exit

>adb pull /dbdata/databases/com.android.providers
.settings/settings.db
failed to copy '/dbdata/databases/com.android.providers.settings/settings.db' to
'./settings.db': Permission denied

>adb shell
$ su
su
Permission denied
$ su
su
# chmod 666 /dbdata/databases/com.android.providers.settings/settings.db
chmod 666 /dbdata/databases/com.android.providers.settings/settings.db
# ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw-rw- system system 49152 2010-08-19 10:31 settings.db
# exit
exit
$ exit
exit

>adb pull /dbdata/databases/com.android.providers
.settings/settings.db
3072 KB/s (0 bytes in 49152.000s)

>echo update secure set value = 1 where name = 'i
nstall_non_market_apps';|sqlite3 settings.db

>adb push settings.db /dbdata/databases/com.andro
id.providers.settings/settings.db
3072 KB/s (0 bytes in 49152.000s)

>adb shell
$ su
su
# ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw-rw- system system 49152 2010-08-19 11:14 settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw---- system system 49152 2010-08-19 11:14 settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.
db
chown system.system /dbdata/databases/com.android.providers.settings/settings.db

# ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw---- system system 49152 2010-08-19 11:14 settings.db
#

Finally, the OP states that we shouldn't use someone else's settings.db because of potential problems with the android_id. I've read up on this a little and it sounds like the android_id is set on the first boot of the ROM and should remain the same barring a new ROM being installed.

When I was trying to get the lagfix to work I had to start from scratch with a fresh JH2 flash, but the file I manipulated above is from a previous JH2 installation. Will there be a problem if I use the settings.db from the previous JH2 installation with the current JH2 installation?

ETA: This is the status of the file I worked with after the lagfix was applied, which can't be chowned to system.system:

>adb shell
$ ls -l /dbdata/databases/com.android.providers.settings/settings.db
ls -l /dbdata/databases/com.android.providers.settings/settings.db
-rw-rw---- 1 1000 1000 46080 Aug 19 17:08 ←[0;0m/dbdata/databases
/com.android.providers.settings/settings.db←[0m
$