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!
I noticed a strange issue with my app on a Galaxy S4 LTE updated to Android 4.4.2.
If i go back to the launcher with the home button and try to reopen my application from the launcher menu, it restarts from the main activity instead of resuming from where it was send on background. Issue isn't present if I go back on my app from the task manager.
The issue isn't present on my Nexus devices (7 2012 with some months old CM11 build and 5 with last Cyanogenmod rom) and another Samsung Device (Galaxy Ace 2 I8160 running 4.1.2) I tested my app on.
Other apps behaviour are correct on the Galaxy S4 (IE: Facebook resumes correctly) so I think I'm missing some flags on my AndroidManifest.xml. Any help?
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.
Recently upgraded from API 16 to 17. Has been retaining all AVDs that were added before and they were working fine after the upgrade too. But today I deleted all old AVDs and added few new ones, each with each device specification available. Earlier, the booting time was around 5 minutes for AVDs with recent versions (4.1.2) and around 2 minutes for AVD with 2.3.3. But now, AVDs with 4.1.2 or 4.2.2 takes 10 to 15 minutes to boot. Moreover, it fails to load launcher. When I touch on the launcher button on the Home screen, it loads the list of Apps and displays a usage tip, "To add an app to your Home screen, touch & Hold it" over it. So far expected. But touching on "OK" for this tip leads to "Unfortunately, Launcher has stopped" error. Not touching on anything leads me back to the home screen.
Tried unchecking AVD options, "Hardware keyboard present" and "Display a skin with hardware controls". Still the issue remains.
It was a memory issue. Problem fixed on incrementing the default value of VM heap by a factor of 16. (16 to 32 and 32 to 48).
I know this should be more a comment then an answer, but I'm too new to StackOverflow. Hopefully a mod transfers this answer.
Are you using an Intel image? Because those ARM images are really slow. When you want to use an Intel image you should also install HAXM (https://stackoverflow.com/a/10772162/1741111). Be sure to select it the right settings. 768 RAM is the maximum on Windows.
These are my settings:
Yes, same issue on my latest SDK for Android 4.4. I am running the "ARMeabi-v7a", from the AVD (Android Virtual Device) Manager.
Every time I started the emulator, it would crash once you selected the apps screen, and tried to launch an app. The emulated app launcher would crash with
Unfortunately, the Launcher has stopped.
Really a pain.. I am running at the API level 19, so probably due to internal program bloat...
Once I raised the VM heap memory from 16 to 48, I noted that a special help program runs, with a big outline of a hand pointing at the "Downloads" app, and explaining that you can press and hold any app to move it to the main screen.
I am running on a WIN-XP (32-bit) old dual core Centrino Toshiba Satellite Pro, so maybe on newer 64-bit machines, the error does not show up. But thanks, Rajeesh.
I just used AVD Manager to edit the parameter screen for the ARMeabi-v7a emulated target device, and now the emulator launches successfully, and I can see (and run) my first "Hello World" app, built with the Eclipse ADT stuff. - Mark_L