I've just started to use the SmallApps API of Sony Tablet SDK. I need to show my small app always on the top but when user is opening the screen keyboard small app is making hidden. It possible to solve this problem?
Related
I have a request to reduce my app screen size and the rest of the screen space are still visible and clickable for user.
It means when my app is running, user can click some icons or buttons outside of my application.
What I found are using such as Dialogs or Multiple Fragments. However, those solutions are useful when all are in your main activity. But in my case, the rest of the screen is from Home screen or other screens, not from my app screen.
Could someone have an idea for this kind of concept?
Here is my request concept image
Searching from internet
You don't need to do anything for this. Android supports splitt screen since Android 7.0.
Alternatively you can enable Picture-In-Picture mode for your app which is supported since Android 8.
I am running an app built in Flutter on Pax A920 device with Android 7.1.2 installed.
Whenever the keyboard appears, the screen jumps down, and shows parts of the current view above the screen. When I dismiss the keyboard, everything goes back to normal.
This behaviour can be seen in the photo below. Sorry for the image quality, I cannot take screenshots on this device.
Photo of the unexpected behaviour
I cannot really show any code examples since this happens every time the keyboard appears, from different screens with different navigation stacks.
This works fine on iOS devices and on the Android emulators I have tried, so clearly this has something to do with the device/OS I'm running this on.
Has anyone experienced this or something similar and has an idea of how to prevent this?
I'm developing an Android tablet app where I need to show fullscreen content. Entering and closing the app is done using a dedicated physical button on the device. When the button is pressed I want all other traces of the Android UI to disappear, and then reappear when we press the button again. I.e., a fullscreen app that is placed on top everything else.
Any ideas on how to achieve this? I've tried various approaches to no avail:
* Adding SYSTEM_UI_FLAGS* doesn't work for this purpose, as the SystemUI will reappear when touching the screen. Ideally we would also not like the animation when opening our fullscreen app.
* Adding a separate layer on top of what we believe is all other layers, but the SystemUI is still shown
Some kind of layering must be preserved. I.e., I need to show incoming call dialogs on top of the fullscreen app.
Please note: This question is about development in the framework/system part of Android. I'm not looking for answers on how to do it in regular user apps.
Another app pop up a dialog in the center of my tablet suddenly and make my app not visible. Is there any way I can send any kind of api (like what we do in Windows ) to move (and also resize) it to the edges of the tablet but not close it?
And is it possible to close it also?
Thanks
Since you are using your Application and suddenly, you gets a popup on top of it which is being called from a different application. Basically, there is no way an application can interrupt another until there is permissions provided to the concerned Application.
However, You can check the logs and accordingly you can write a piece of code to dismiss any popup that appears on the screen, but for resizing an popup, I am not sure how to handle the UI.
Thanks!
I've got an android trigger.io app, which I'm using a custom splash screen on. Once this splash screen disappears, I sometimes am left with a black/grey gradient background while my webview has not loaded the content of my app (either a log on or a configuration page)
This seems to happen more often when I'm attempting to show a Kendo UI Modal Window immediately (I'm using one for a "Welcome to the app" first time message), and less frequently when this isn't shown.
Are there any known compatibility issues between Trigger and Kendo that I should be aware of to fix or work around this?
Does this happen on all Android devices, or only the ones with ICS (Android 4+)?
I had a similar problem on ICS.
It turned out that it was caused by CSS rule -webkit-transform: translate3d(0,0,0).