In order to exit apps' full-screen modes (i.e. video playback), you need to execute any gesture once and only then are you able to actually execute the desired gesture. This is terrible for consistency and consistency is key when it comes to gestures, so this needs to stop. I want a single back gesture in an app to cause the app to receive a back button event, no matter what state said app is in (full-screen or otherwise). Same for home or app switcher events. The notification bar can remain in the double-pull mode though, I think I'd prefer that actually. I'm open for any sort of hack to make this happen as long as it's open source and applicable to AOSP Android and/or LineageOS. It wouldn't be the first time I had to patch android_frameworks_base to my will but I'd rather do this in a less invasive manner (i.e. a Magisk module). (Specs: Fairphone 4, LineageOS 20 (Android 13), µG)

When an app uses Immersive Mode, Android will often issue a large prompt (on a blue background) instructing the user to "Swipe down from the top to exit full screen". Is there a way to prevent Android KitKat from displaying this message? I performed some research, and the only answer I could find involved installing an Xposed Framework module. I would prefer not to install the Xposed Framework. Answers requiring a rooted device are fine (please just specify in your answer whether or not your solution requires root).

How can I enable immersive/fullscreen mode in Termux? I want to hide the bars at the top and bottom of the screen so that the entire screen displays the terminal. In summary, I'm looking for *either* a configuration option for enabling fullscreen mode in Termux, without reconfiguring (or rooting) my device and without connecting an external device, *or* an explanation of what happened to the fullscreen option mentioned in some parts of the documentation, if it has been removed.

I upgraded to Android 11 without knowing that it broke compatibility with existing immersive mode and window manger overscan adb commands. Are there new alternatives to these commands in adb now? I was specifically using:

shell wm overscan 0,0,0,-136 (reset: 0,0,0,0)

shell settings put global policy_control immersive.status=*

For reference I'm running GrapheneOS on build number RP1A.200720.009.2020.09.25.00 on a Pixel 3 with Android 11 on Kernel version 4.9.223.

Some games in portrait mode will enter immersive mode automatically, and my navigation bar and notification bar will be hidded, and it is really annoying for me. Is there a way to prevent that from happening? Root, Magisk and Xposed(Edxposed) is acceptable.

I recently upgraded my OnePlus 6 from Android Oreo to Pie (OxygenOS 9.0.8; **rooted**). This release came up with a restriction that only the apps listed under *Settings → Display → Apps to display in fullscreen* can use edge-to-edge display (full immersive mode including notch area). As of now, YouTube app (using YouTube Vanced v14.21.54) is not shown in that list, and when I enable immersive mode that app doesn't make use of the notch area at all. Here's how immersive mode looks like with and without notch area: (Images edited. Courtesy of OnePlus) " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> One thing I noticed is that, for the apps in the list if they are set to be launched in fullscreen (including notch area) the appops operation APP_SCREEN_COMPAT is set to *deny*, while in default state, it is set to *ignore*. Manually changing it via adb to *allow* further reduces the immersive mode screen estate. I tried adding that operation (op) manually for YouTube app but it didn't make any change, including when I force-stopped the app and even restarted the device. The op is reflected in appops query though. I used this command: adb shell appops set com.google.android.youtube APP_SCREEN_COMPAT deny I also tried changing *policy_control* global settings property to immersive.full=com.google.android.youtube but it didn't make any difference either. I came across some forums where users shared similar problem with their choice of apps with no solution in sight. I also looked for some related Magisk and EdXposed solution but found none. GravityBox [P] doesn't have any feature either. So, how do I make sure any of my app can use edge-to-edge display in immersive mode?

Here's what a video frame looks like on CM browser: Here's what a video frame looks like on Chrome: That upper black border is for the status bar(the status bar is not there, but that's its place). The borders on the sides are for nothing... probably the video is fitted with respect to height. This doesn't happen with YouTube videos on Chrome, But that's the only site where Chrome works fine. How can I fix this please.

I recommended purchasing android smart phone (moto e 2015 with android 5.0.2) to a non-technical savy friend of mine and he did. Few UI aspects of android always annoy newcomers. One such is incoming call arriving as heads-up notification. I want to disable heads-up notifications for incoming calls or maybe system-wide. Is there any way to do so. The device is not rooted and runs stock android 5.0.2. I already tried this HeadsOff app and it doesn't allow me to select Phone app in free mode. Also the device has on-screen navigation buttons alone, like in nexus devices. Whenever any app, say a game takes immersive mode the navbar is hidden and the user feels crazy. Is there any way to disable immersive mode for any or all apps? The device is not rooted and runs stock android 5.0.2.

There are several applications able to force the so called immersive ("full screen") mode. (Power Toggles being one of them) My problem is that, in that configuration, Tasker and similar applications seem to be unable to detect which is the foreground running application: profiles based on that kind of state doesn't trigger until full screen mode is toggled off. I'm looking for an alternate way to detect the foreground app (Tasker Plugin would be fine) which doesn't have that limitation.