I have a problem running my app on a device.
Not on all devices!
On many devices(Lenovo android 4.2.2, Lenovo 4.4, Nexus 4 android 4.4 and more) it's running perfectly!
Unfortunately on some devices, such Samsung with android 4.4(upgrade to 5.0), Wiko android 4.4.4 app crashes without any message.
When I click on the app icon, the app opens then it shows a white screen for less than 1 second before the app closes.
I've made a apk file like this: In Android Studio I press "run" triangle, after it finished building I copy apk from "appname\app\build\outputs\apk". app-debug.apk
Does anyone have the same problem ?
Thanks for any helpful information !
Important:
The device is for 2,500 kilometers from me
UPD:
I try to launch "empty" app and it works!
Related
I am working on an Android app with Android Studio using Kotlin. The app was working fine until yesterday when it started showing white screen when I relaunch the app.
If I delete the app from the emulator and run the app, it installs and works perfectly fine.
But if I stop the app and relaunch either from Android Studio or from within the emulator, all I see is a white screen.
I am using Pixel 3a XL API 28 virtual device.
I allocated 512 MB VM Heap, and 1 GB Internal Storage. The app itself occupies only 35 MB.
I setup Log statements in MainActivity onCreate, onStart, onResume methods. None of them execute during the relaunches. They run only on the new install.
Has anyone seen this problem?
Any suggestions would be great.
please add this line into your app theme
<item name="android:windowDisablePreview">true</item>
Instant Run in Android Studiosometimes issue when running app while white screen appears to try to disable Instant Run in Android Studio.
I think there is problem with the emulator, try running the app on a physical android device.
If the contents in your app requires internet then also check whether you internet
is on or not, sometimes white screen can occur due to no internet also if your app requires active internet connection.
I have downloaded android studio and now i am trying to run an app.I haven't changed anything in code or design.I am using version 2.2.2
When i click on run it gives me an error
init: Could not find wglGetExtensionsStringARB!
But emulator opens.Then there is blank black screen for 2-3 minutes,then androidtitle for another 5 minutes.This is what i get.
But i don't know where is my app?
What you're running is Android version 7.1 (Nougat MR1). You can see the list of apps (app drawer) by clicking on the small ^ (caret) icon above the opaque area highlited as a red circle in the picture below
emulator opens.Then there is blank black screen for 2-3 minutes,then androidtitle for another 5 minutes.
This is normal. You should wait until the emulator fully boots and run your app again. If your development computer has an Intel processor, be sure to install HAXM. It will greatly increase the speed of the emulator.
I'm asking this because it's only happening in nexus 7 device. I had an Asus nexus 7 2013 .
Issue is when my app goes into background [clicking home button] i go back to main menu and click my app icon. It simply Restarts from Splash Screen and no other app is open in background, RAM is 1.3 GB free.
This should be happening if system is running on low memory and kills my app while in background.
I had tested my apk in other tablets it's working fine as it should work.
But Specifically in Nexus 7 it is showing rouge behavior.
Android version is 4.4.3
Is this a generic Bug or just Specific case.
I currently work on an Android application with two developpement phones :
1 SGS GT I-9000 with Android 2.3 at first, then Cyanogen 10.1.3 with Android 4.2
1 SGS III GT I-9300 with Android 4.0.4
My problem is that when my application triggers an unhandled exception while testing my code, the behavior is radically different on the two handsets : The old Galaxy S displays a force close popup (either on Android 2.3 or 4.2), but the Galaxy S III completly crashes and I have to reboot it each time.
Is there a parameter that i have missed ?
Edit : I also tried to run the app on AVD with a deliberate NullPointerException. It is correctly trapped.
I finally managed to get rid of this problem : I downloaded a new ROM for SGS III and flashed the phone with ODIN 3.09. Exceptions don't crash the handset anymore and the force close popup is correctly displayed.
(For those who wonder why i didn't simply update the current ROM, the response is : I tried, but it changed nothing)
I created a new emulator device & AVD on my Android development environment. I had one working for the Galaxy Ace 2. I created a new device & virtual machine for the Samsung Galaxy S3 (Icre Cream) but it doesn't work.
It first shows the emulator window with a plain text ANDROID on the upper left or so. After a while it changes to the next phase (same as in the other emulator) which displays the word ANDROID with funky letter type and an animation on the letters. But it never gets past that.
On the working emulator it goes to the next phase which displays the Android screen unblocking , which after unblocking loads the app being tested.
So why is the S3 emulation NOT starting? My S3 is targetted at Android API Level 15 and in the Android SDK Manager I have the following in the Android API 15 (4.0.3):
SDK Platform (installed)
ARMEABI v7a System Image (installed)
If I try the Nexus 7 emulator that was already installed by default, it does not even show the emulator screen, it only says "This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information." and that's it.
So basically the only emulator that works is the Ace 2 I created.