I have an android app which uses sqllite, i have the apk files built in 2.2 sdk. It runs smoothly on the emulator, but when I installed it on the Samsung Galaxy Tab (Android tablet) it gets installed but wont run. It gives me error "my_app_name(my_package) have stopped unexpectedly. Please try again "..I don't know why this happens..
please help
Have you tried using DDMS to see what the error is? It should report the line of Java it crashed on and give you an indication as to the problem..
Related
I'm working on a project in Android Studio and I am using my Samsung Galaxy phone to test my application after every project modification.
My problem is that after I use one time my phone or the emulator to test the application, then I cannot run it again on the same device.
When I try it, the application don't show any errors, but the screen that appears on the phone or emulator is blank.
I tried to remake the project but after first try the phone and emulator showed the same problem.
How can I solve this? Thanks!
When I run my app on my Galaxy S7, nothing shows in the logcat in Android Studio. Not even while debugging. If I use another device, I can see the logcat. On one device (Asus Padfone Android version 4.4.2) I can run my app from Android Studio and everything works fine. When I run it on my S7(Different Android version: 7.0) the app crashes in some activities but since the logcat doesn't show I can't see what the problem is. How can I get the logcat to show so I can see the issues? I've tried killing adb processes and restarting the adb server. I've invalidated cache in Android Studio. Nothing works. I was able to see the logcat prior to my S7 updating. I'm using Android Studio 2.3.1. All sdk packages are downloaded and up to date.
Note: I posted this question here because I believe it to be more relevant to programming than hardware.
When I plug my S4 in and run eclipse, the logcat only displays logs from AndroidRuntime, dalvikvm, and Xposed Framework, but nothing else. There is no system messages, no errors, but more importantly, there is no output from any app, including mine. I downloaded a logcat viewing app on the phone and it read the logs just fine, but for some reason eclipse will not. I've reinstalled all the phone drivers and eclipse, as well as the android sdk. My nexus 7 and Transformer Infinity log just fine through eclipse. I can't figure out what's wrong with my S4.
It is rooted and has xposed installed, that is all.
I have encountered the same problem.
after long hours of reading and research, it seems that if you have a S4 running Android 4.3 - you might encounter Logcat problems. The reason is still unknown (to me, anyhow).
My S4 is rooted too, and I have a custom ROM installed running 4.3.
When the Logcat stopped working, I spent hours reading almost everywhere possible, and I found a post recommending to downgrade to earlier Android version.
So I installed 4.2.2 and everything worked fine.
Hope this will help you...
Cheers!
I have an android app that uses jsoup that runs fine on a motorola atrix phone running Android 2.3.6 and also works fine on a Samsung Galaxy Tab running 2.3.5.
However, I have tried to run it on my new phone: Samsung Galaxy S4 runnning Android 4.2.2. It can't run jsoup at all.
It chokes on this line of code:
Document document = Jsoup.connect(SPOT_SERVER_BASE).get();
Has anyone else encountered this problem for Android 4.2? (Or 4.1 or 4.0?) Is there something I need to do differently to get it to work?
Thanks for your help.
I haven't figured out what causes the problem, but I have figured out how to fix it.
In the manifest, I deleted this line:
android:targetsdkversion="xx"
where "xx" is whatever version you are using for the target in your build.
The only place where I indicate the project build targtet is where you edit the project properties by right-clicking on the package name and selecting "properties".
Why does this work? I have no idea.
I am trying to test a simple status bar notification program on Android 3.0 emulator.
When I try to run my application from eclipse, sometimes either I see a message that apk can't be installed when I check the DDMS log, I see java outOfMemory error. Though my application is fairly simple just one java file.
Sometimes when I launches my emulator it shut down my windows completely. I tested this on Windows XP and Ubuntu as well. In Ubuntu too when emulator was about to launch completely and showing home page my OS crashes.
Any other version of Android works well on my PC like 2.2, 2.3. I see this issue only with 3.0 (honecomb) version. Any resolution to this?
Thanks
Manish
Well when making an AVD from the AVD Manager , assign it maybe 200 -500 mb and this issue will be resolved.
I have noticed the resource usage while running 3.0 is much more than 2.3 and below. The error you are getting refers to the emulator/eclipse needing more memory not your application. How much memory and CPU do you have?