On Aug 11, 2011, at 11:08 AM, vsr28 wrote:
> This works fine with small database size but when i tries to do the same
> with 38MB size of SQLite database then it gives me error of Disk Full after
> running my application and hence application Unable to connect with
> database.

That's a rather large database. That said...

If this is the emulator, how did you launch it? If you're launching it yourself 
(command line or through the `android` app), then you should instead launch it 
through the command line and use the -partition-size argument:

        emulator -partition-size 512 -avd NAME

Increase -partition-size as appropriate; the default value is 64, which is way 
too small for typical development.

If this is a device, you're going to need to remove some apps or otherwise free 
up some space. :-(

Keep in mind that when you bundle a 38MB file asset with your app and extract, 
you're going to have two copies of the file: a (possibly compressed) version 
within the .apk, and the extracted copy. Add in the typical overheads of a 
Release Mono for Android app (~3.9MB for libmonodroid.so + your linked 
assemblies + the compressed copy of libmonodroid.so in the .apk + ...), and 
you'll be looking at nearly 50+MB of disk use (assuming ~80% compression of 
your SQLite DB).

(Also, if memory serves, older versions of Android have problems reading Assets 
larger than ~1MB in size...)

 - Jon

_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to