First, what is the best way to resize and scale an image dynamically at runtime,
for device density, considering memory and performance?

Yes, I've pre-typed and am ready to go:

I'm using WakefulIntentService.  

My first question, if I set private variables in my WakefulIntentService class, I can't rely those values to be there when the AlarmManager triggers because the thread may be gone and get re-created, correct?  I know this because everything is fine when the interval is short, but if it's a longer interval things go wrong.  Am I on the right track?  

If so, is SQLite the way to go for persisting three or four values for a WakefulIntentService, or are there other options?

I have an application which needs to be deployed twice with different branding for each.  Is there a way to manage the code so if I make changes in the future they will stick across multiple versions? (I can only think of using SVN)

I have an application which uses a Camera application to take a photo as such: 
Intent i = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
i.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(new File(fwyPhotoRoot, filename)));
startActivityForResult(i, VIEW_TAKE_PHOTO);
In doing this a full sized photo should be store in the location provide. The problem is that the photo is not full sized but scaled down. It would appear to be the same problem as noted here:
http://code.google.com/p/android/issues/detail?id=1480#c10
Just wondering if you've come across this and maybe have a slick solution. I don't want to write a full Camera app (I looked at the source code for Camera). I'm also creating videos from the camera and would like to know how to create a thumbnail from an mp4 file… (oh on 1.6 unfortunately)

Notification note = new Notification(R.drawable.playbackstart, text, System.currentTimeMillis());
        note.flags |= Notification.FLAG_NO_CLEAR | Notification.FLAG_ONGOING_EVENT;
        note.tickerText = text;