I am developing an application on android 3.1 Honeycomb. It force-closes on Asus epad.
I don't have an Asus Epad to check why it force-closes, so I want to try it on an Asus epad Emulator. I updated the ADK for eclipse but it doesn't provide an Asus epad Emulator or add-on for it.
In other words, my main problem is that I want to test my application on an Asus emulator.
Does anyone know how I can do this?
Update----
It's showing error on background process & it's a null pointer exception. But now I found another way to do this background code so it must work now.
Thanks for all your comment.
Still if any one find out plugin or package or a way to create emulator which work as Asus Epad.
Thank You.
I am pretty sure that it the app gets force closed on an actual Asus epad, it will get force closed on the emulator too.
You can try to debug your application using LogCat in Eclipse and look the stacktrace to figure out what is going wrong.
Could you post details about what exactly does it crash on? You could monitor the logs in DDMS and check the stacktrace to analyze what exactly is it crashing on.
Unless you post specific details about a problem, there's very little I or anyone else could help you out with.
Related
First of all I must say that I have been working around this issue for two whole days and I can not solve it. I googled it, I read this article from Donandroid, this thread from SO and many other reviews.
I have installed Samsung Kies3, Android sdk for windows, google_usb_driver on my windows 7 64-bit system. I also check the USB Debugging option in my Galaxy S5 and restart my phone. I also have restarted the ADT
Now when I check the attached devices in adb, I get:
$adb devices
$List of devices attached
4d0005444cc34139 unauthorized
I have tried to run my application on this device, but I have got this in ADT:
I have no idea what to do now. I am totally frustrated. Any help would be greatly appreciated guys.
Ok, solve the problem. I have unplugged/plunged the usb cable for 3 times and suddenly the popup authorization message showed up on my phone. I allowed that and now everything is fine. I can not believe I spent two days in this issue. Hope this thread will help someone.
I made example project, it's not big, but I think too big to post it here - so I uploaded it here
http://www.filedropper.com/logtest
Run from Eclipse on avd it works ok on device with Android version 4.2.2
My phone has Android version 4.0.4 and all I am getting is
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
What should I change/enable/set to get logs on my phone too. I want to let the app on a phone for "real life" testing and send logs back on my email.
(Any suggestions how to improve the code will be appreciated too)
That problem occur sometimes, you can close and run eclipse again it will work (This is in case if the debugging is working well with your phone).
Strange thing happened and the same code is working now. It usually happens right after posting on stackoverflow :)
I installed aLogcat(free)-logcat app, I checked my logs, then they started working in my app too ?!? After uninstalling aLogcat, my app was still working.
My phone has no physical sd card - so this app maybe created image and mounted it somehow.
I'm not sure what exactly happened, maybe this post can help someone with the same problem. Thank you #Chris Stratton and #Bousselham
i'm facing an interesting problem. My android application is running fine on Samsung Galaxy SII or HTC Desire, but running it on Samsung Galaxy Pocket is quite a problem. I was told, that everytime it was started, after few minutes it showed this:
Sorry! - Use *#9900# to take log - application was unexpectedly closed, try again.
I can't find satisfying answer about what could be causing this, so i would appreciate any help!
Thanks, Mike.
From what i can gather is usually a memory problem, cache maybe. You might find your galaxy or desire has a bit more memory or handles cache, ram, etc differently. Try and clean up the system, reset or restart and see what happens
The message was odd, but it was simply unhandled null pointer exception.
I have the same problem and my laptop detected that my phone is missing a driver that is why it is not working properly so downloading that missing driver will solve your problem.
I have created an application its working fine on HTC Wildfire but one of my application user having HTC Thunderbolt has reported that it is generating Application Force Close dialog.
As i don't have real device and i want to sort out the issue, i want to know is there any emulator available for HTC Thunderbolt so that i can test my application on it?
Hardware related bugs can't be tested with the emulator. So the answer is no, there is no such thing.
If the two phones have different Android versions and that is the source of the error then you can find the error with an emulator
An emulator won't help much to fix a problem with a specific device.
First of all you should acquire a stacktrace from the user using the Android Market or an EMail intent.
After that you can try to reproduce the problem using a service like http://www.deviceanywhere.com/ for example.
I'm developing a application that works on linux. I want to port this to the Android SDK Emulator. But everytime I start the application the emulator crashed with a segmentation fault.
Somebody has any clue why a selfmade program that's running on the Android Emulator could crash the entire emulator?
Can you post up some code examples / logs of what is happening? You don't provide enough information for us to suggest why it would fail.
Best thing I can advise is to create a new emulator (only takes a few clicks) and try deploying your app on that, possibly try a different version.
If you can post up some logs/code examples of what might cause this, we can provide better answers
Another debugging point to try would be launching a demo application/Hello Android on the emulator, to see if it is your application specifically.
Apparently there was a bug in the version of the emulator that I used. When I updated the emulator to the latest version, it was solved.