cursor = getContentResolver().query(Email.CONTENT_URI, null, Email.CONTACT_ID + "=?", new String[] { id }, null);

I am receiving "database is locked" errors from time to time. I use the following process to access the database
		mReadableDb = new XXXDbHelper(this).getReadableDatabase();
I find it hard to replicate this error. I looked at your approach to accessing a database in the latest version of tutorials and saw you have something that looks like:
	helper = new XXXDbHelper(this);
and then use "helper.getReadableDatabase();" when you need to use the database. I don't really understand why I get the "database is locked" issue and I am having trouble replicating it so I'm not sure if this would help but I thought it might. Without being able to replicate the issue consistently I thought I'd ask whether the former approach (reusing mReadableDb) might create the possibility of locks occurring.

I have a list which is accessing images on the (an) SDCard. The thing is that some rows have images (most) but the odd one doesn't. So I check for these currently using something like this:

String filename = getFilenameUsingCursorAndDisplayDensity(c,dd);

ImageView iv = getYYYImageView();
	if(null!=iv) {
		File yyyFile = new File(filename);
		if(yyyFile.exists())
			// show file
		else
			// show default

I'm wondering how to make this more efficient so the list isn't too jerky. It's not really bad, but it could be better and it shows up when fast scrolling.