# Application covers Android Buttons

**URL:** <https://forum.juce.com/t/application-covers-android-buttons/67294>\
**Category:** Android\
**Created:** [October 4, 2025, 3:20am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294 "2025-10-04T03:20:46Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 4, 2025, 3:20am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/1 "2025-10-04T03:20:46Z")

</div>

In version 8.0.10

setFullScreen (true)

covers Android buttons.  
Same result in development version.

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [October 4, 2025, 2:03pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/2 "2025-10-04T14:03:21Z")

</div>

The expected behaviour of setFullScreen is that the application fills as much space as possible, including drawing behind the navigation bar and status bar. You can query the Display safe area to find out which areas should be reserved for the system UI.

- Do you mean that the buttons aren’t visible at all, or that they are drawn over the JUCE application? Can you provide a screenshot?
- Do you see the same behaviour in any of the example projects from the JUCE repository?
- What devices have you tested?
- What Android versions have you tested?

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 4, 2025, 2:23pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/3 "2025-10-04T14:23:29Z")

</div>

JUCE draws over the buttons

 ![setFullScreen](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/a/e/aef642116775e97f4b3726668ac26f9892267d3f.jpeg)

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 4, 2025, 2:33pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/4 "2025-10-04T14:33:08Z")

</div>

Is there a function setFullSafeArea () instead of setFullScreen() ?  
We have tested with 2 devices : Samsung A11 / Android 12 and Samsung S25 / Android 15

Did not test JUCE repository.

With version 8.0.8 and 8.0.7 everything is OK

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 4, 2025, 2:52pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/5 "2025-10-04T14:52:03Z")

</div>

setFullScreen(true) and Desktop::getInstance().setKioskModeComponent (this, true) have same functionality.

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [October 13, 2025, 4:21pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/6 "2025-10-13T16:21:35Z")

</div>

> [@CavitVURAL](#):
>
> JUCE draws over the buttons

In your screenshot, I can still see the Android buttons (back button in the bottom right, circle button in the middle) and statusbar items (wireless reception, date/time) so it looks like JUCE is drawing behind the system UI, which is the expected behaviour.

> [@CavitVURAL](#):
>
> Is there a function setFullSafeArea () instead of setFullScreen() ?

No, there’s no such function. This is deliberate - the application should still draw a background in the ‘unsafe’ area to ensure a seamless appearance.

A simple way to achieve this is to separate your main content component from the top-level component. The top-level component is then responsible for drawing a background that fills the entire screen area, including the area behind the status and navigation bars. The top-level component should also position the content component so that it doesn’t overlap with the status/navigation bars.

This is the approach we take in the DemoRunner application bundled with JUCE. The content component is positioned in `MainComponent::resized()`, shown here:

> <https://github.com/juce-framework/JUCE/blob/3af3ce009f6a02f6fa651008fffb5b41743a9fab/examples/DemoRunner/Source/UI/MainComponent.cpp#L363-L373>

> [@CavitVURAL](#):
>
> setFullScreen(true) and Desktop::getInstance().setKioskModeComponent (this, true) have same functionality.

These functions should have slightly different behaviour, as follows:

`setFullScreen` resizes the component so that it fills the largest possible area. This is generally the full screen area, but may be smaller, for example if split-screen mode is enabled. `setFullScreen` does _not_ hide the navigation and status bars.

`setKioskModeComponent` additionally hides the navigation and status bars, and requires the user to swipe from the top/bottom of the screen in order to reveal the system UI. In this case, the ‘safe area’ no longer includes the navigation and status bars (because they’re not shown) but may still include space for a notch or other display cutout.

If this doesn’t match the behaviour you’re seeing, please let us know and we can investigate. Please provide as much detail as possible - we need to know at least the JUCE version, the Android version, and whether the issue is present in the JUCE DemoRunner, before we can investigate.

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 14, 2025, 6:50am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/7 "2025-10-14T06:50:59Z")

</div>

Hi reuk,

Thanks for detailed reply.

 ![uygulama_ana_sayfasi_d](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/3/d/3d3b27e866c79183fd2e5e09e2e7aa35cbad59fd.jpeg)

 ![uygulama_ana_sayfasi_y](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/3/d/3dd4d45af52612849efd51cce74d1457c1943d00.jpeg)

Using safeBounds resolved almost everything.

But after opening a custom dialog and closing it , safeBounds being smaller.

 ![uygulama_open_dialog](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/3/3/33ac47edfb7f43973031deaa2dd59cbade517de0.jpeg)

 ![uygulama_yeni_d](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/b/6/b682d2811232384a792e70f760afa03a09ff26c0.jpeg)

 ![uygulama_yeni_y](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/c/6/c6b504db5a90dcaf12990831790b65a4deb8a84b.jpeg)

We have also tested dialog windows with “DialogsDemo” and “WindowsDemo” examples .  
safeArea remains same after closing dialog window.

Almost everything are same with examples. Do you have any idea ?

Regards

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 14, 2025, 8:03am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/8 "2025-10-14T08:03:41Z")

</div>

On iOS safeArea remains same after opening and closing custom dialog window.

It’s an Android issue

---

<div class="post-metadata">

**Author:** ![aamf](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aamf/32/19941_2.png) [@aamf](https://forum.juce.com/u/aamf)\
**Post date:** [October 14, 2025, 9:00am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/9 "2025-10-14T09:00:08Z")

</div>

It seems that adding any window to the desktop messes up the safe areas on Android.

There’s a similar problem with the MIDI Bluetooth pairing dialog. If it is added to the main component instead of the desktop everything is fine.

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 14, 2025, 9:48am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/10 "2025-10-14T09:48:03Z")

</div>

To add to main\_component “launch\_options.componentToCentreAround = main\_component;” must be enough.

Or not ?

Result of checking in Dialog with isOnDesktop : 0

---

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [October 21, 2025, 12:57pm UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/11 "2025-10-21T12:57:16Z")

</div>

> [@CavitVURAL](#):
>
> But after opening a custom dialog and closing it , safeBounds being smaller.

It’s difficult to guess at the problem without being able to reproduce the problem locally.

Unfortunately I can’t currently produce the same behaviour in a JUCE example project, so it’s difficult to guess at the problem. From the screenshots, it looks like the system is applying the insets to the top level component as well as forwarding those insets. So, maybe we need to put the window back into edge-to-edge mode after closing a top-level window. I can’t easily test this theory without first triggering the problem, though.

It would be helpful to know:

- What `minSdkVersion` and `targetSdkVersion` are you using? You can find these in the build.gradle for your app. Are these values the same between your app project and the JUCE examples that you tested?
- What is the Android version of the device that you used to take the screenshots? Do you see the same behaviour on both Android 12 and Android 15? Do you see the same thing in the Android emulator?

---

<div class="post-metadata">

**Author:** ![CavitVURAL](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cavitvural/32/21327_2.png) [@CavitVURAL](https://forum.juce.com/u/CavitVURAL)\
**Post date:** [October 28, 2025, 9:19am UTC](https://forum.juce.com/t/application-covers-android-buttons/67294/12 "2025-10-28T09:19:02Z")

</div>

minSdkVersion 24 , targetSdkVersion 35  
With Android 12 and Android 15 behaviour does not change.

Here is a workaround. I hope it may give you some clue.

```cpp
// Starting Dialog
#if defined (JUCE_ANDROID)
    dw->enterModalState (true, callback, false);
#else
    dw->enterModalState (true, callback, true);
#endif

// Closing Dialog
m_close_button.onClick = [this] {
    if (DialogWindow* dw = contentComponent->findParentComponentOfClass<DialogWindow>())
        #if defined (JUCE_ANDROID)
            dw->setVisible(false);
            this->~DECONSTRUCTOR();
        #endif
        dw->exitModalState (0);
    }
};

```
