AudioManager mAudioManager = (AudioManager) getSystemService(AUDIO_SERVICE);
mAudioManager.setSpeakerphoneOn(true);

			case TelephonyManager.CALL_STATE_OFFHOOK:

5. About hardware/software

If I have support issues it would be helpful to get user phone information like manufacturer, model, android os, even things like battery life, ram, processor speed.  A user might not know this, so is there a good way to generate a View that displays this kind of information, to make support easier?  I can't find a way to determine the android os of the host device, nor these other items.

	mStartRegisterButton.setOnClickListener(new View.OnClickListener() {

			@Override
			public void onClick(View v) {
				C2DMessaging.register(FMPMain.this, FMPConstants.APP_REG_EMAIL);
			}
		});

From C2DMBaseReceiver I see:
        // Use a naming convention, similar with how permissions and intents are 
        // used. Alternatives are introspection or an ugly use of statics. 
        String receiver = context.getPackageName() + ".C2DMReceiver";
        intent.setClassName(context, receiver);
        
        context.startService(intent);

	<receiver android:name="com.google.android.c2dm.C2DMBroadcastReceiver"
		android:permission="com.google.android.c2dm.permission.SEND">
		<!-- Receive the actual message -->
		<intent-filter>
			<action android:name="com.google.android.c2dm.intent.RECEIVE" />
			<category android:name="nz.co.juliusspencer.android.xxx" />

</intent-filter>
		<!-- Receive the registration id -->
		<intent-filter>
			<action android:name="com.google.android.c2dm.intent.REGISTRATION" />
			<category android:name="nz.co.juliusspencer.android.xxx" />
		</intent-filter>
	</receiver>

you said earlier "
So I think that I need to name my Receiver C2DMReceiver in order for it to be called"

		<service android:name=".C2DMReceiver" />

I can't figure this out.  I have a preference icon in a view.  When pressed I would like the next View to slide up from the bottom of the screen, and when the user saves or cancels by button press I would like View 2 to slide down revealing the original screen.  This  intentionally overrides the stock android view-transition-animation to give the user the idea they are filling out a temporary preference screen and the other screen is right "behind" it.
I played around with custom animations, but the closest I could get would be screen 1 dissappears, black screen appears, screen 2 slides up.  Note that I am targeting 1.5 - 2.2, although if there is a good solution that excludes 1.5 that is OK, I just need to know the best practice for deploying an app for 1.5-2.2 that has some code sections that do not work on 1.5 (can you if statement for the platform version of local device and execute different code accordingly, or do you have to deploy separate apk's?)