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.
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
I recently bought a Moto X and was following the online instructions for setting it up to test my android code. I installed the USB drivers and got to the place where it tells me that the phone is unlockable. I quickly returned the phone at this point before activating it and subsequently porting my number over.
Can I test code on the Moto X specifically even if it is NOT bootloader unlockable? Is this the case for all android devices?
Unfortunately I don't know anyone that is a developer or even anyone that owns a Droid phone that I could experiment with.
You do not need to unlock bootloader to test your Android applications. Please refer to Using Hardware Devices for more information regarding setting up any Android device for testing. Following is the relevant part quoted for your information:
You can use any Android-powered device as an environment for running, debugging, and testing your applications. The tools included in the SDK make it easy to install and run your application on the device each time you compile.
This is a general answer, not specific to Moto X. I do not see any reason why it should not apply to Moto X.
I'm a newbie for Android development. I want to run a Hello World on the emulator in Eclipse as my starting point, but the magic words never show up. I just follow the tutorial, Launch the Android Virtual Device Manager, Create a New AVD and Click Run.
But Everything is fine if it runs on a real device. Is there any special setting on Mac?
Please help.
You have to wait a long time util it appears. I'd advise you to use USB debugging and a real device. It works much faster than the emulator. In addition you can use the app with the normal gestures and all the sensors like camera etc.. But as I said: it's much faster than the AVD.
Check Console tab in Eclipse for information about APK upload and installation progress.
Is there any special setting on Mac?
No there is not. Settings are pretty much the same on all platforms.
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.
Emulator --- Device
Hey people. I'm not very experienced in Android development, so I would like to know what I have to expect.
I wrote an app of about 1000 lines of code, which is running perfectly fine in the emulator. So what will it be like when I install it on a physical device? Ain't got one here at the moment, but I will get my hands on one on the next days. Will there be a bunch of nasty errors? Just some design stuff? Errors, that cant be reproduced in the emulator?
Thanks in advance
EnflamedSoul
Note: emulator runs the real Android code. It emulates ARM device and runs the whole stack on top: linux kernel, libs, android code. It is the same as device sans some hardware (camera, mobile network stuff, gps) and much slower.
So what will it be like when I install it on a physical device?
Will there be a bunch of nasty errors?
No problems really. It should work ok.
Just some design stuff?
If you set your emulator to the same resolution and pixel density of your device, then it should look identical.
Errors, that cant be reproduced in the emulator?
There ares some thing that you can not do in emulator: primarily make calls and use camera. Otherwise emulator behaves like a plain phone.
My Android apps have all been very simple, but I have really only had to make small changes to their layouts when I tried them on my phone. Over-all, the process of moving to the phone was a rather painless one.
I had a code that took 4 minutes on the emulator to complete, and on the real device it is just 10 seconds.