We have a raspberry pi 4 based device with a display, and when it is booting, it should start our program (which is does as init.d service). It boots up to console and then starts the program as it should. While booting, it should show nothing but a splash screen. However, when booting, it shows different text output on the screen, and the splash screen (set at /usr/share/plymouth/themes/pix) only shows up for a few seconds, to make place for even more text output, before our program's display appears. It does not look nice. It should show the splash screen image as soon as it can, and do not show any text output, before the program starts. Any idea how to do this?
Related
I have some performance problems running my Flutter application inside iOS simulator installed inside a VirtualBox OSx machine. The simulator run and the application is deployed without any problem. But there is lag when the screen has to be redrawn. For example, when I click on a button which opens a modal sheet, the image is stuck, I can unlock it simply dragging the IOs bottom bar of a few pixels. It's difficult to test the application since every time I have to move that bar a few pixels in order to update the phone image. This is an example of my problem:
As you can see the image is redrawn just after I click and move the iOS bottom bar.
Here a simulation of a native iOS app:
Here as you can see the screen has to redraw, I don't need to move the bottom bar.
Any suggestion?
I have to display a splash screen which resides on a server. Using a web service, I have to get it displayed in my SplashScreenViewController. So it's obvious that when my app launches, it will display a blank screen (img is being downloaded) and after a few seconds, it will show my splash screen.
I know that the splash screen image should have to be in the main bundle, and locally it should be seen as a splash image. But the client wants us to get it loaded from a server.
So can I use an activity indicator in that duration until my splash screen gets loaded?
That is a very bad implementation of a splash screen, but there are no other ways, you will need to use an indicator view, until the image has been downloaded,
Also consider to add a default image its much better than a white view
You will have to deal with some issues, like what would you do if internet connection is very slow or you are not connected, and what would you do if you dont recieve the image you asked for any reason
I've got a strange bug going on that seems to be OS related : If I give a sleep interrupt to my device while the OS controlled splash screen, Default.png, is displayed, and then immediately wake the device, I get a black screen until applicationDidFinishLaunching: is called and the OS passes control to my app.
It would be nice if upon waking the device, Default.png still displayed properly. I put some logs in to see when the interrupt handlers (applicationWillResignActive: etc.) get called, but they never do - I think the interrupt is happening too soon.
Any ideas on how to avoid returning to a black screen?
Thanks in advance!
You don't have any control over the splash screen how long it will display. The Default.png file will show while the app is being set up, but will disappear as soon as the app is ready to launch.
If you need more time to finish loading, you should create another view that looks like the splash screen that you have control over.
Just know that Apple is prickly when it comes to how the splash screen is used. They are of the opinion that your app shouldn't have one anyway. So be careful how long you sit on an empty/splash screen. Display a progress view or activity indicator to let the user know that you haven't crashed and are still working.
I know that android emulator is to slow, and I read a lot about that here in stackoverflow.
My problem is that sometimes when I run the emulator, instead of going to android home screen it shows me a an screen with to button, one look likes a 'Lock' and other looks like a 'Speaker'.
And sometime (Like the moment i am writing this question), the screen just shows 'Android' text and nothing happens.
When it says 'Android', it's booting. Just wait. It can take a few minutes.
When it's a lock and a speaker, it's just the lock screen. Slide the lock to the right to go to the home screen.
Dragging the lock downward as far as it could go worked for me..for whatever reason and resulted in the camera getting launched :). Eventually the camera stopped responding and I could get to the home page.
Update: Dragging it upward causes the screen to get unlocked. Note that this was on a Ubuntu machine.
When i start my app for the first time after installing it and exit before the splash screen disappears, from then on launching from the multitasking menu it comes up with a black screen. If I click on it from the home screen it loads fine but every time I try from the multitasking menu it is a black screen until I terminate it. If I add the UIApplcationExitOnSuspend property to the properties list the black screen continually appears until i restart the device. Any help is appreciated.
Thanks Sj
A couple things:
You probably don't want to suspend your app prior to the splash screen disappearing. applicationDidFinishLaunching is running code (you know, like adding a window to the app) while the splash screen is showing. If you suspend it early, it doesn't have a chance. This may not be the case after the first time install but if I were you, I'd give it the time it needs to do initial install instead of interrupting it.
Another less likely scenario: Are you doing this while the debug is still running? I've only had an issue similar to this (black screen after suspend) if I leave debug running and then suspend the app to the background. As soon as you bring it back out of the background, you get a black screen, so in that case it's a bug. If you hit the stop sign button in XCode to kill the app, it worked fine after that.. but you have to kill it before suspending it.
My guess is your likely cause is #1. Give the app more time to do the initial load. After that, it should be fine. For whatever reason, the first time installing/loading is always the slowest.