I don’t understand what you mean by what you wrote, but fragments should have manager activities. You can put these two fragments into the same activity management. When jumping, you only need activity operations. But!
The back button will only return to the previous activity. If the current activity is the main page, the application will return to the background. Fragments are operated on the activity to which they belong. The back key will not return to the previous fragment. If there is such a need, you can override onKeyDown() to set pressing the back key to return to the previous fragment. I don't know if that's what you mean.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
I don’t understand what you mean by what you wrote, but fragments should have manager activities. You can put these two fragments into the same activity management. When jumping, you only need activity operations. But!
The back button will only return to the previous activity. If the current activity is the main page, the application will return to the background. Fragments are operated on the activity to which they belong. The back key will not return to the previous fragment. If there is such a need, you can override onKeyDown() to set pressing the back key to return to the previous fragment. I don't know if that's what you mean.
The response method of the return key is onbackpress in 'activity'. The fragment itself does not support the physical return key
It may be a problem with the fragment life cycle. Try saving the view in onCreateView instead of drawing it every time.
Maybe the Fragments are overlapping