cylonid/NativeAlphaForAndroid

Fork 0

mirror of https://github.com/cylonid/NativeAlphaForAndroid.git synced 2026-11-05 00:47:30 +00:00

[GH-ISSUE #171] Android 15 enforces edge to edge mode #158

New issue

Closed

opened 2026-10-29 12:16:27 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-29 12:16:27 +00:00

Owner

Originally created by @Quackdoc on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/cylonid/NativeAlphaForAndroid/issues/171

Thanks to Android 15 enforcing edge to edge mode, native alpha now renders underneath the cut out and navbar and now needs windowOptOutEdgeToEdgeEnforcement https://developer.android.com/reference/android/R.attr#windowOptOutEdgeToEdgeEnforcement

Originally created by @Quackdoc on GitHub (Jan 12, 2025). Original GitHub issue: https://github.com/cylonid/NativeAlphaForAndroid/issues/171 Thanks to Android 15 enforcing edge to edge mode, native alpha now renders underneath the cut out and navbar and now needs windowOptOutEdgeToEdgeEnforcement https://developer.android.com/reference/android/R.attr#windowOptOutEdgeToEdgeEnforcement

bsakaguchi closed this issue

2026-10-29 12:16:27 +00:00

bsakaguchi commented

2026-10-29 12:16:28 +00:00

Author

Owner

@RPLgrime commented on GitHub (Feb 10, 2025):

This would be useful under the settings for each individual link a user has set up so it can be turned on or off as needed.
In the dev docs, I saw this statement.
"If this is true, the edge-to-edge enforcement won't be applied. However, this attribute will be deprecated and disabled in a future SDK level."
Maybe there is a better way, like a toggle to enable padding on top and bottom of layout?

@RPLgrime commented on GitHub (Feb 10, 2025): This would be useful under the settings for each individual link a user has set up so it can be turned on or off as needed. In the dev docs, I saw this statement. "If this is true, the edge-to-edge enforcement won't be applied. However, **this attribute will be deprecated and disabled in a future SDK level.**" Maybe there is a better way, like a toggle to enable padding on top and bottom of layout?

bsakaguchi commented

2026-10-29 12:16:28 +00:00

Author

Owner

@birkenfeld commented on GitHub (Feb 28, 2025):

Another vote for adding a setting for this. Websites with a search bar or similar elements in the top are currently unusable unfortunately.

@birkenfeld commented on GitHub (Feb 28, 2025): Another vote for adding a setting for this. Websites with a search bar or similar elements in the top are currently unusable unfortunately.

bsakaguchi commented

2026-10-29 12:16:28 +00:00

Author

Owner

@franco27 commented on GitHub (Mar 16, 2025):

I also have the display issue with Android 15. Recently, Motorola updated Android to version 15.

With Android 14, the app worked very well.

Now there is the Android top and bottom bar above the app (the main window is behind the Android bars) and also for websites.

When I was on Android 14, I had disabled immersive mode; otherwise, for some websites, the input area being at the bottom of the screen, the keyboard would cover the input area and I couldn't see the text in the input field.

Today, I was forced to enable immersive mode because otherwise there is the Android top bar at the top of the screen and the Android bottom bar at the bottom of the screen. These Android bars prevent me from clicking on buttons or menus on the website because they appear above the fullscreen window of the website.

The second problem with Android 15 is that when the keyboard appears, it hides the input area since the input field is located at the bottom of the screen. Previously, the input area would move above or to the top of the keyboard under Android 14. So I have to enable a floating keyboard.

This app is very useful, and I look forward to a fix for this issue.

@franco27 commented on GitHub (Mar 16, 2025): I also have the display issue with Android 15. Recently, Motorola updated Android to version 15. With Android 14, the app worked very well. Now there is the Android top and bottom bar above the app (the main window is behind the Android bars) and also for websites. When I was on Android 14, I had disabled immersive mode; otherwise, for some websites, the input area being at the bottom of the screen, the keyboard would cover the input area and I couldn't see the text in the input field. Today, I was forced to enable immersive mode because otherwise there is the Android top bar at the top of the screen and the Android bottom bar at the bottom of the screen. These Android bars prevent me from clicking on buttons or menus on the website because they appear above the fullscreen window of the website. The second problem with Android 15 is that when the keyboard appears, it hides the input area since the input field is located at the bottom of the screen. Previously, the input area would move above or to the top of the keyboard under Android 14. So I have to enable a floating keyboard. This app is very useful, and I look forward to a fix for this issue. ![Screenshot_20250316-192810.Native Alpha +.png](https://github.com/user-attachments/assets/f39e8db2-f958-4c33-b47c-03ec56e6564c)

bsakaguchi commented

2026-10-29 12:16:28 +00:00

Author

Owner

@ghost commented on GitHub (Mar 24, 2025):

app is dead because of that

@ghost commented on GitHub (Mar 24, 2025): app is dead because of that

bsakaguchi commented

2026-10-29 12:16:29 +00:00

Author

Owner

@cylonid commented on GitHub (Apr 13, 2025):

Sorry it took so long to fix, the problem was the old adblock engine was no longer available and I did not want to release an update with less functionality then before.

This issue itself is easy to fix by setting a flag, I am not really fond of this edge-to-edge enforcement and will postpone the change for the moment.

Everything is looking good now, if everything goes to plan the update should be online in a few days 🙂

Closing as duplicate in the meantime.

@cylonid commented on GitHub (Apr 13, 2025): Sorry it took so long to fix, the problem was the old adblock engine was no longer available and I did not want to release an update with less functionality then before. This issue itself is easy to fix by setting a flag, I am not really fond of this edge-to-edge enforcement and will postpone the change for the moment. Everything is looking good now, if everything goes to plan the update should be online in a few days 🙂 Closing as duplicate in the meantime.