I have another question for you:
Is there a way to hide a specific virtual button from android navigation bar?
My particular case is hide recent apps button. I've searched in some posts about this, but they mention how to hide or disable navigation bar. I just need to hide one virtual button from navigation bar.
I hope that you can give me an answer, thanks!
Update:
Somebody told me that Airwatch app from VM-Ware does this customization
It is currently impossible to make an App-specific customization, but it is possible to make a device-specific modification on Navigation Bar, starting from Android 8.0 (Oreo) by unlocking System UI Tuner.
However, do consider the limitation as both Navigation Bar and System UI Tuner ability is pre-defined by OEMs. Which means we cannot customize more than the given customization choices, and different device might introduce different customization capabilities.
You can not change the navigation bar from your application; you do not have access to these settings. Instead, what you can do is using adb to hide the navigation bar and use only the navigation inside your app. You can follow this tutorial of XDA-dev and their application called "Navigation Gesture", you will find the adb command.
Related
When pulling down the notifications, the gesture navigation bar on the bottom slides down, some apps like the PlayStore handle this well, while my app (and others like WA) is resizing, what is this about? Do I have to recompile with newer AndroidX version or do something in the manifest?
Couldn't find anything on this
(Take a close look at the bottom here ⬆️
First of all, I could not reproduce the issue on the official Android 31 emulator image.
Secondly, it appears that the Google Play app layouts fit the system window and use translucent system bars. Since your app doesn't implement such behaviour, the app layout needs resizing when the navigation bar re-appears. On the other hand, the Play Store layouts don't need resizing because the navigation bar will overlay on top of it. You can implement a translucent navigation bar using the instructions provided in this answer.
fullscreen hides both the Android navigation and status bars (requiring you swipe from the bottom to show the navigation bar over the app), and standalone hides neither, when it comes to the display property of the PWA's manifest.
Simply, I want the bottom Android navigation bar to always show but without showing the top status bar. I wonder if I am missing some HTML meta or manifest JSON property or some other way to accomplish this?
I will expect most users to install the PWA via the web, not via the Play Store (so no TWA, Android application wrapper, etc.)
As far as I know this is not possible.
With the web-manifest you have different choices: default, standalone, fullscreen (see screenshots below):
On the Google docs page, also a "minimal-ui" value is available:
This mode is similar to fullscreen, but provides the user with some means to access a minimal set of UI elements for controlling navigation (i.e., back, forward, reload, etc).
Note: Only supported by Chrome on mobile.
Reading the description it seems this is what you are looking for, but unfortunately the top status bar and also the page address (read-only) is displayed. Therefore I do not think you can achieve what are you looking for with the standard display values of the web manifest.
I would like to test my app in android 4.2.2,I know certain device comes with system bar along screen and others don't.I would like to know how to test those system bar that doesn't come along screen.Please provide your assistance in fixing the emulator for this,thanks a lot.
This is an old good question. If changing theme does not fits your needs, please refer to these question asked before:
Easy way to hide system bar on Android ICS
Is there a way to hide the system bar in Android 3.0? It's an internal device and I'm managing navigation
is it possible to hide the system bar
and others.
Note that for some HW Devices/Android version, the system bar can't be hidden at all! You need to root the device and manage some complex operation to get the system bar off...
Good luck!
You can change the theme of the Project from manifest file..it will solve your problem
I would like to know if it's possible to remove/hide/disable the bottom menu bar that always shown on android 3.x .
if not - at least if it's possible to hide the opening of the widget bar or disable the core widgets.
programatically or not - I must deny access to the bottom menu when my app is foreground.
please help.
thanx in advance.
I would like to know if it's possible to remove/hide/disable the bottom menu bar that always shown on android 3.x .
No, you cannot remove/hide/disable the system bar.
if not - at least if it's possible to hide the opening of the widget bar or disable the core widgets
There is no concept of a "widget bar" or "core widgets" in Android, so I do not know what you are referring to here.
I must deny access to the bottom menu when my app is foreground.
Fortunately, this is not possible, for obvious security reasons.
You are welcome to build your own custom firmware that you load on your own custom hardware that contains this "feature".
I have an app that's built for Android 2.2, so I'm not using the 3.0+ built-in ActionBar class but rather building my own custom ActionBar implementation using Google's older UI recommendation that was introduced a couple of years ago.
All of my screens have between 1 and 3 actions that can be performed, so they all fit very nicely into the ActionBar UI (which Google recommends has a maximum of three buttons). The problem now is that none of my screens have a regular options menu and so they do nothing when the user presses the hardware Menu button.
According to Google's interface guidelines, this is correct behavior. If your activity doesn't have an options menu then it should do nothing when the Menu button is pressed. I've found during user testing, however, that users are quite perplexed when they press Menu and nothing happens (and every single user has tried, usually multiple times). They say that they appreciate the actions being exposed on the screen through the ActionBar, but at the same time they want the Menu button to do something.
I've been looking at Google's first party apps and it looks like they just always have enough options available to be able to load up the options menu with stuff after the ActionBar is full. Google+ seems to use the Menu button in the traditional way for overflow options on phones that have one, and they show a dropdown menu in the ActionBar for phones that don't. That would work if I had more than three actions but I currently don't.
It seems that the only way to meet my user's expectations is to put some junk options that have no value into the Options Menu just so that something happens when they push the button. I really don't want to do that. Does anybody know of a good way to deal with this problem? Should I just leave the menu button alone and expect people to figure out that it doesn't do anything?
I think it's safe to assume that most users don't know the menu button exists and having all of the actionable items displayed on screen is best. User testing by Google has revealed this and it is why they have chosen to eliminate the menu and go with the built-in action bar starting with Android 3.0 and culminating in the recent 4.0 release.
Something to think about would be added a single "About" item to the pre-3.0 options menu/post-3.0 overflow menu. This could just popup a dialog with simple info about the application (e.g., version, licensing, link to website, author, etc.). This way there is something there should they happen to press the menu button but it is not required in order to properly use each activity to its fullest potential.
I have an app that's built for Android 2.2, so I'm not using the 3.0+ built-in ActionBar class but rather building my own custom ActionBar implementation using Google's older UI recommendation that was introduced a couple of years ago.
As an author of an action bar library this sentence disturbs me. It's fairly trivial to use a custom action bar implementation on pre-3.0 and the native one post-3.0. Take a look at Google's Action Bar Compat sample.
...or, you know, you could also go with a library like ActionBarSherlock that does this for you! </shamelessPlug>