Listner state navigation bar - Android Q&A, Help & Troubleshooting

I have an application closely associated with the system navigation bar. It is very important for me to know whether it is hidden or displayed.
The following code says it can tell whether immersive mode is enabled/off, which hides the navigation bar.
Code:
View decorView = getWindow().getDecorView();
decorView.setOnSystemUiVisibilityChangeListener(new View.OnSystemUiVisibilityChangeListener() {
@Override
public void onSystemUiVisibilityChange(int visibility) {
if ((visibility & View.SYSTEM_UI_FLAG_HIDE_NAVIGATION) == 0) {
Log.d("NavBar", String.valueOf("visible"));
} else {
Log.d("NavBar", String.valueOf("not visible"));
}
}
});
But he can not say if I gestured up from the bottom of the screen to the navigation bar, and after a while she disappeared again.
How do I make it so that I can track the visibility state?

---

Is there really no solution?

---

As far as I understand the docs ( https://developer.android.com/reference/android/view/View.html#SYSTEM_UI_FLAG_HIDE_NAVIGATION ), they say that the SYSTEM_UI_FLAG_HIDE_NAVIGATION flag will be cleared as soon as the navigation bar reappears in immersive mode. (Means the "immersive mode" is "closed".) As far as I can see, your approach is ok for immersive mode but not for sticky mode:
Please read carefully the difference between immersive mode (SYSTEM_UI_FLAG_IMMERSIVE) and sticky mode (SYSTEM_UI_FLAG_IMMERSIVE_STICKY). To get full control over the appearance of the navigation bar, you need to use SYSTEM_UI_FLAG_IMMERSIVE and not SYSTEM_UI_FLAG_IMMERSIVE_STICKY. In immersive mode (SYSTEM_UI_FLAG_IMMERSIVE), you have to take care yourself that the navigation bar disappears again after some user interaction (usually running an async task that reenters immersive mode after xxx milliseconds of time). If the behavior is - like you describe it - that the navigation bar disappears again by itself, this indicates that you are using SYSTEM_UI_FLAG_IMMERSIVE_STICKY. In sticky mode, the docs say that flags are not changed at all because in this mode the short appearance of the nagivation bar is not considered a view change.
There are very good examples how this is done on the android dev pages. Read carefully: https://developer.android.com/training/system-ui/immersive.html

---

Yes, I understand what you are writing about, but in fact it's a little different. I do not put SYSTEM_UI_FLAG in my application, but any other program and even the system. In these all programs the developer can establish how he wants, and I need to know this in order to correctly implement my application.
o you understand what my program is about - here's the video. But there's another problem on video. Just a video so you can see what the application is about.
https://photos.app.goo.gl/riaFIDumxyV2cTWx1
Now I instead of decorView substituted View, on which I draw HUD. Now I can track when the navigation bar enters and exits this mode. And I can not handle the appearance after the gesture and reverse immersion.

---

Bascially, you listen to the change with your listener (your code snippet). To reenter immersive mode again, run an async task that is launched after the user's interaction (e.g. responding to a touch-event) and that re-enables immersive mode after xxx milliseconds.

---

I do the same. For this, I have a data stream from getevent. I process touch from the navigation bar (in particular also from the bar status, because there are different immersion modes and gesture on the status bar also returns the navigation bar) as a gesture that returns the bar. The gesture must be completed within 1 second, then it returns. In general, I use getevent to process touches from the navigation bar. The system does not intercept the pressing of the navigation bar.
Therefore, you need to use the low-level command getevent, root and busybox.
https://photos.app.goo.gl/ywu6T2XopaHxlAnx1 - video