I have an app in development that runs fine in the emulator but wont run on any android device, when the application icon is clicked the screen goes blank for a second then returns back to the device apps page, i have experimented with setting different permissions but it does not seem to solve the issue. Any ideas?
Related
I have developed a mobile application in ionic3 which appears and works fine on browser but when I connect it with emulator or install apk on android device, only black screen is displayed on application startup. Let me know the solution if anyone ever faced this problem.
I am making a game for android and after running my app on a connected device, I would press the home button to exit out of the app. But when I press on the app again, it would just be a black screen. I was wondering if I had to program the app to close? or if this is another problem? thanks!
May be your phone is running out of memory .. Try running it using a device with higher ram or in an emulator with high config ..
I have tested my application using ionic-serve and everything run normally.
But, when i tried it using device, the application will first run the splash screen (which is not run when using ionic serve) and nothing happen, only white screen.
Can somebody please help me with this situation?
I have no idea about what happen.
The white screen issue often occurs on devices and not in the browser when you are injecting something into a module that kicks off your app. Try to figure out which one, and remove it (if it's not being used) or update it.
First thing to do is to check for errors in the log. To see them, type the address chrome://inspect/#devices in chrome, and click on your app. You'll need to make sure your device has usb debugging turned on.
My app has an action bar tabs with 3 fragments (1-list fragment with the list of running processes, 2-battery and memory info, 3-just some text). It works fine, with no errors on the emulator, but on a real device it starts ok, I go through the tabs several times and then it unexpectedly force closes. My phone isn't seen among the adb devices, so I don't know if there are any errors in the logcat. What could be the problem?
First, enable debugging on your phone. This is found on Settings.
There are several things that can crash the app on the device:
for example: Screen orientation; on the emulator, your screen never rotates, but on a device the screen can be rotated unintentionally. If the app is a prototype, several things can go wrong on rotation.
You should start by enabling debugging so you can pin-point the problem
I'm using eclipse for Android development. Often I have several emulators (and devices) running in order to test my app.
LogCat magically switches to the log from the device I just launched the app on. This is fine most of the time, but sometimes I want to switch back to a different device without restarting an app.
I can't figure out where to select which device LogCat is showing. Where can I change it?
I'm using Eclipse Juno on OS X, if that makes any difference. Here's what my LogCat window looks like:
Go to Window -> Show View -> Devices.
Now you'll have another devices tab present, and in that you can select which device you want to see in the LogCat, as well as the running apps on that device in debug mode.