I've made an Android app that it's causing a couple of problems to a few users. I can't reproduce those problems in my test devices (3 different devices with 3 different Android versions). I've been debugging the app with Eclipse and I don't see any kind of error where those users are having the problems.
The app is a Phonegap/jQuery Mobile app built with Eclipse.
How can I get the logs from those devices? I know the users so they would cooperate with anything I asked for to install or do.
EDIT
I'll give more info about the issues themselves. The app doesn't crash, it seems a jquery issue when changing pages, instead of showing the correct page the app gets stuck with the spinning thing. But it only happens in those 2 devices (Galaxy S4 and Note 3) that run Android 4.3. I've tried in other devices with Android 4.0.1, 4.2.2, 4.4.2 and no problems at all.
Oh, and I've already tried running the app in an emulator with 4.3, trying to replicate the S4 as close as possible in the emulation specs, and no problems there...
Related
I have developed an Android app and it's ready for launching , now i wanted to test it on different possible devices ,but unfortunately i can't afford all the devices physically and I can't download emulators for all the Android devices , is there any way to test my app in different Android devices and see how they work on that device's
Thanks for your time and help.
Use Genymotion, it is very light and clean, better than AVD (Android Virtual Device)
it's the android studio should be able to test almost every screen size you can also try testing on android emulators like bluestacks and others they'll help
My question today is about optimizing google Chrome browser in Genymotion android emulator. I've run my Selenium / Appium scripts just perfectly on my several real Samsung & HTC devices, even parallel. Since sometime I decided to try the same run on android emulators. To tell honestly, I've never tried original Android Studio virtual devices because they are extremely slow. When I run scripts on genymotion emulator custom installed google Chrome browser (means with the help of ARM translation and google apps zip files), the browser always behaves weirdly. Sometimes it randomly closes or just stuck. But the biggest problem is that browser is very slow. Text is being inserted into textfields slowly, pages are being reloaded slowly, images appears slowly as well. I've followed several advises from google search like https://www.youtube.com/watch?v=vZKiqJyLBkU and others, but they just about optimizing emulator itself, not the Chrome browser. So far I have tried different versions of Emulators: Android 6.0 / 5.0 / 4.4 / 4.3 / all of them have slow chrome browser once custom installed. My Genymotion menu doesn't offer to create emulator with preinstalled Google Play (I assume that's because I use free version). The result of slow Chrome browser is my script always throws me a different errors on different runs so it makes no sense for me to resolve them as those scripts run excellent on real devices. If anybody overcame this problem with slowness of google Chrome browser for Genymotion emulator, please post your solutions here. Thanks.
OK so I am trying out Genymotion for testing my app, so that I can reproduce the errors that my users are telling me they experience with my app, which leads me to fixing the issues. I guess that is the main reason for using Genymotion.
Real life example:
A guy says: "I'm using a Moto X (2013) on Android 5.1.1 and I can't do X with your app.
Me: Looks at Genymotions list of virtual devices and can't find neither the brand of phone nor the android system. I can only find android 5.1.0.
Does this mean that I Genymotion just doesn't have what I need, or is it because one of the other options are just as good? I really don't know. What am I missing?
Any help would be appreciated.
Brian
An emulator, be it the default android emulator or Genymotion or any other emulator will not be able to replicate a real physical device to the complete extent.
The devices available on Genymotion are just templates to recreate the device with values such as RAM, Screen size etc. You could try creating a custom device by using the values for Moto X.
One possible idea would be to get the stacktrace from your friend and see what's going on. The best way to do that would be to integrate crash reporting system like Crashyltics. You will automatically get crash reports in your fabric dashboard.
I'm having some problem with developing an android app. Everything runs smooth until a while ago. Lately I've been debugging on a couple of different physical devices and everything works great on all of them. The other day when I tried to run the application in the emulator I got an error:
ERROR/JNIHelp(313): Native registration unable to find class 'android/debug/JNITest'.
Is this something to worry about? The app is supposed to be released today on the market but it doesn't feel right to release something that wont even load in the emulator. Since the app works seemingly flawless on all physical devices I've tested it might not be a problem?
Try -wipe-data ... if it doesn't work, delete the emulator images .. and if that doesn't work re-install the SDK .. No other fancy solution, afaik.
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.