为何MediaPlayer API需声明为全局实例变量？局部变量为何要求final？

Great questions! Let's break them down one by one to make things clear.

1. Why should the MediaPlayer API be declared as a global instance variable? #

There are a few key practical reasons for this:

• Lifecycle alignment: An Activity goes through multiple lifecycle stages (like onCreate, onPause, onStop). If you declare MediaPlayer as a local variable inside onCreate, it’ll get marked for garbage collection once the onCreate method finishes—even if audio playback is still running! This can cause playback to cut out unexpectedly, or leave hardware resources hanging around (leading to memory leaks). A global instance lets you tie the MediaPlayer’s lifecycle to the Activity’s, so you can properly release resources in callbacks like onPause or onDestroy.
• Efficient resource management: MediaPlayer uses underlying hardware resources (audio decoders, speaker access, etc.). Creating a new instance every time you need to play audio is inefficient and can strain the system. A global instance lets you reuse the same player for multiple playback actions, and gives you control over when to release those resources.
• State persistence: MediaPlayer has a state machine (ready, playing, paused, stopped, etc.). A global instance retains this state across different user interactions or Activity callbacks. For example, if the user taps a pause button, you can directly call pause() on the global player instead of having to reinitialize it and reload the audio file.

2. Why does a local MediaPlayer variable in onCreate require being declared final to call start()? #

This almost always happens when you’re trying to access the local MediaPlayer instance from an anonymous inner class (like a button click listener). Here’s the breakdown:

• In Java, when an anonymous inner class (or a lambda, which is shorthand for it) accesses a local variable from the enclosing method, that variable has to be either final or effectively final (meaning it’s never modified after initialization). The reason is that the inner class creates a copy of the variable—if the original variable could be changed later, the copy and the original would be out of sync, leading to bugs.
• When you declare MediaPlayer as a class instance variable (global to the Activity), the inner class doesn’t need a copy—it directly references the member variable of the Activity instance. Since member variables live as long as the Activity itself, there’s no risk of inconsistent state, so no final modifier is required.

Here’s a quick example that shows the scenario triggering the error:

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    
    // Local variable—needs to be final/effectively final for the lambda below
    final MediaPlayer mediaN = MediaPlayer.create(this, R.raw.my_audio);
    
    Button playButton = findViewById(R.id.play_btn);
    playButton.setOnClickListener(v -> {
        mediaN.start(); // Without 'final', this line would throw an error
    });
}

内容的提问来源于stack exchange，提问作者Nitish P