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.
Related
I use a custom PNG for the splash screen in my MAUI app. It works fine on all of the IOS emulators I run the app on. It works fine on the Android emulator it runs on. However, when I connect my physical Android device to my computer and deploy to it, the splash screen does not appear.
I've tried looking at the device log, but there are literally thousands of entries in there which make it problematic for troubleshooting. What are the recommended debugging or diagnostic steps I can realistically use to track this down?
EDIT:
I managed to grab the device log entries during the splash screen loading and thought I would paste them here to see if anyone can make any more sense of what's going on. Here's a color coded version of it that I formatted in Excel:
This is an issue that happens to me just sometimes, most of the times the emulator works ok.
screenshot of the problem with the emulator
The thing is, that the emulator starts but it can not be maximized. It doesn't matter if you click on its "window" from the Tasklist at the bottom or you try to force it to maximize/make it go to the front from the Task-manager; it just doesn't react to it.
In the little window that appears when you have the mouse over the task (see screenshot), you can even watch the emulator starting and waiting for the interaction with the clock and so on, but it is not accessible.
Any ideas?!
I had the same issue after forcing the emulator to close during debugging.
To fix the problem, try changing the screen resolution of the virtual device under Edit in the AVD manager and then launch the virtual device.
This fixed the issue for me and I was able to revert to the original resolution without any problems.
I would like to get tap to focus in my app and the controls are hidden
Supposedly this is impossible but I know its not. I have a simple iAD dragged into an overlay, no code or anything. When I click on the iAD nothing. but when I close it with the home button I get a modal exit of the nonexistant iAD and the camera apps relaunches but in the top left with only a small portion viewable. But this time the tap to focus is enabled.
So how can I do this without the bug?
Thanks!
Guess no one got it? I just showed the controls to take a snap and zoom and focus came up!
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.
Trying to finish up an app I've been developing and have hit an odd bug that I'm not sure if it's on my end? a bug on apple's end? or perhaps the underpinnings of multitasking showing themselves.
My current app is doing this weird thing when you press the home button to quit the app, and then immediately relaunch the app. You see the Default.png image as the app starts up, but when it goes to display the window/view it briefly shows the screen as it was just before you quit the app, then goes to black for about 2 seconds and then displays the correct screen as if you were starting up fresh. I'm see this on all devices, iPods, iPhones, and iPad.
This is not just me, however, I've been trying other apps to see if they do it, and have found that the Air Hockey ( http://itunes.apple.com/us/app/air-hockey/id286106725?mt=8 ) is an example of an app that does this same thing. My instinct is that there are many apps that do. But the bulk of apps dont seem to have this issue.
I've done everything I can do make sure all views and view controllers are properly released, but it's almost like the device is taking a while to truly shut down even though the app has visually disappeared, and if you restart the app within probably 3 seconds or less then it still has something in the window buffer, or tht the full on view controller hasn't truly been released yet.
Anybody seen something like this and been able to solve it?
I'm the dev of that Air Hockey - It looks like it's probably Flurry that's causing it. I have a version without Flurry & it doesn't do it.
I solved this problem by updating my Flurry files to the latest version. http://dev.flurry.com/iphone_uploadNewVersion.do