Activity与Fragment可重写函数差异及onKeyDown失效问题

1. Why Your Fragment's Overridden Functions (Like onKeyDown) Aren't Working, & How to Fix It #

First off, the core issue here is that Android doesn't directly pass system-level events (like key presses) to Fragments by default—those events go straight to the hosting Activity first. That's why your onKeyDown works in Activity but not in Fragment.

Here are two solid fixes for this:

Option 1: Pass the Event from Activity to Fragment #

In your hosting Activity's onKeyDown method, check if the current Fragment is the one you want to handle the event, then call its custom method:

@Override
public boolean onKeyDown(int keyCode, KeyEvent event) {
    // Get the currently visible Fragment
    MyFragment currentFragment = (MyFragment) getSupportFragmentManager().findFragmentById(R.id.your_fragment_container);
    
    if (currentFragment != null && currentFragment.handleKeyDown(keyCode, event)) {
        // Fragment handled the event, return true
        return true;
    }
    // Let the Activity handle it if Fragment didn't
    return super.onKeyDown(keyCode, event);
}

Then in your Fragment, create the handleKeyDown method to add your logic:

public boolean handleKeyDown(int keyCode, KeyEvent event) {
    if (keyCode == KeyEvent.KEYCODE_BACK) {
        // Do your Fragment-specific action here
        return true; // Indicate we've handled the event
    }
    return false; // Let the Activity take over
}

Option 2: Use View-level Key Listener in Fragment #

Since Fragments are tightly tied to their views, you can attach a key listener to the Fragment's root view in onViewCreated:

@Override
public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
    super.onViewCreated(view, savedInstanceState);
    
    view.setFocusableInTouchMode(true);
    view.requestFocus();
    view.setOnKeyListener((v, keyCode, event) -> {
        if (event.getAction() == KeyEvent.ACTION_DOWN && keyCode == KeyEvent.KEYCODE_BACK) {
            // Your Fragment's key press logic here
            return true;
        }
        return false;
    });
}

Just make sure the view is focusable so it can receive key events.

2. Key Overridable Methods: Activity vs. Fragment #

Let's break down the most useful lifecycle and callback methods each component supports, including why some work only in Activity:

Activity-Exclusive & Core Methods #

These methods are tied to the app's window or system-level events, so they're handled directly by Activities:

• onKeyDown(int keyCode, KeyEvent event): Receives key press events (no direct Fragment equivalent by default)
• onBackPressed(): Handles back button presses (modern Fragments can use OnBackPressedCallback too, but this is the original Activity method)
• onCreateOptionsMenu(Menu menu): Creates the app bar menu
• onOptionsItemSelected(MenuItem item): Handles menu item clicks
• onConfigurationChanged(Configuration newConfig): Responds to device rotation/configuration changes
• Core lifecycle: onCreate(), onStart(), onResume(), onPause(), onStop(), onDestroy()

Fragment-Exclusive & Core Methods #

Fragments have extra lifecycle steps tied to their attachment to an Activity and view creation:

• onAttach(Context context): Called when the Fragment first connects to its Activity
• onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState): Inflates the Fragment's layout
• onViewCreated(View view, Bundle savedInstanceState): Perfect spot for view setup (like attaching listeners)
• onDestroyView(): Clean up view references here when the Fragment's view is destroyed
• onDetach(): Called when the Fragment disconnects from its Activity
• setHasOptionsMenu(boolean hasMenu): Lets the Fragment contribute to the Activity's options menu
• Core lifecycle: onCreate(), onStart(), onResume(), onPause(), onStop(), onDestroy() (matches Activity, but with extra view/attachment steps)

Quick Note on Modern Fragment Back Button Handling #

If you're using AndroidX, you don't need to rely on Activity onBackPressed anymore. Use OnBackPressedCallback to keep Fragment logic self-contained:

@Override
public void onCreate(@Nullable Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    requireActivity().getOnBackPressedDispatcher().addCallback(this, new OnBackPressedCallback(true) {
        @Override
        public void handleOnBackPressed() {
            // Your Fragment's back button logic here
        }
    });
}

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