Genymotion 2.2.2 (June 2nd, 2014)
Genymotion Desktop
New features
- GPS Settings
The location defined in the GPS widget is now saved and retrieved at the next start.
Only available with Indie and Business licenses.
Corrections
- When starting a virtual device, a pop-up window could report that it was in an incompatible state. It can now recover and start correctly.
- Starting and stopping applications in the virtual device could lead to memory leak and heavy memory usage. This issue has been fixed. We are still investigating on memory leaks.
- Genymotion could crash on Microsoft Windows when some third party security applications were installed. This issue has been fixed.
- Double-clicking inside a maximized virtual device window does not minimize it anymore.
Improvements
- We’ve added more information in the log archive to help better diagnose problems.
- When starting a virtual device, OpenGL initialization problems are more detailed.
Virtual devices
Android 4.x versions
- Native applications debugging is fixed.
Android 4.4.2 version
- The ‘adb reboot’ command did not reboot the virtual device. This problem is fixed.
- It is now possible to connect to the virtual device adb daemon via multiple network connections (TCP).
Genymotion 2.2.0 (March 31st, 2014)
Genymotion Desktop
New features
- Genymotion Java API
Developers can now access a Java API that lets them control Genymotion sensors within their application code. This will help you develop unit tests and improve your Android application. It will allow you to keep your source code clean, without complex mocking proxy objects. For more information, refer to the API tab of the Genymotion website.
Only available with Indie and Business licenses.
Virtual device update
- We regularly add new features to Genymotion. These new features cannot work on virtual devices created with a previous version of Genymotion. This is why you see an annoying popup when you try to run them from a new Genymotion version. But rejoice! Today is the last day you will have to do it. In this release, we have introduced a wizard that automatically migrates old devices to new ones. So please, for the last time, delete your current virtual devices and create new ones using our new 2.2 Genymotion version. Next time, you will be able to automatically convert them.
Only available with Indie and Business licenses.
Log archive creation
- For a faster response from our support team, you can now generate a log archive directly from Genymotion. This log archive contains all the information we need to better identify your problem.
Corrections
- On Microsoft Windows, stopping a virtual device was not immediate when closing the window, making impossible to start it again for a short period of time. This issue has been fixed.
- When using OpenGL ES 2.0, some applications encountered progressive slowdown issues. This problem has been fixed.
- When closing Android applications, some memory leaks could occur. This problem has been fixed.
- Some textures could be corrupted or swapped in rendering. This problem has been fixed.
- To avoid false license activation renewal on Microsoft Windows platforms, the license activation process has been modified.
- When asked to do so, restarting your virtual device from the Remote control widget could lead to usability issues after reboot. This problem has been fixed.
- When running multiple virtual devices, the drag and drop feature could encounter issues. This problem has been fixed.
- An ‘incompatible ABI’ installation error occured for some malformed Android applications that do not contain native libraries. This problem has been fixed.
Improvements
- To avoid Genymotion installation issues, adb daemon now stops when reinstalling Genymotion on Microsoft Windows.
- Genymotion now warns you when ADB or AAPT binary files are not executable.
- Error messages regarding connection issues between the Genymotion software and the Genymotion website have been improved.
Genymotion 2.1.1 (February 5th, 2014)
Genymotion Desktop
Corrections
- Fix a crash at startup on Mac OS.
- Fix a bug making Genymotion exit while loading VirtualBox plugin.
Genymotion 2.1.0 (January 28th, 2014)
Genymotion Desktop
New features
- Copy/Paste
Genymotion now supports copy/paste from the host to the virtual device, or from the virtual device to the host using Android built-in copy/paste feature. Supported on 2.1.0+ virtual devices
- Genymotion ID widget
You can now edit Android ID and Device ID (IMEI/MEID number) values from Genymotion. You can also make Genymotion generate random Device ID or Android ID numbers for you. Supported on 2.1.0+ virtual devices.
Only available with Indie and Business licenses.
- Pixel perfect mode
A new “pixel perfect” mode has been added to help users with their UI developments. In this mode, each pixel of the device is displayed using exactly one pixel of your monitor.
Only available with Indie and Business licenses.
- Factory reset
It is now possible to reset a virtual device to its initial state (when first deployed): A new “Factory Reset” button is now available, next to the device settings button in the virtual devices list. This feature only works with virtual devices deployed with Genymotion v2.0.2 or earlier.
Only available with Indie and Business licenses.
- Cloning virtual devices
Users can now easily duplicate a deployed device from the available devices list.
Only available with Indie and Business licenses.
- CPU number and memory size modifications
Virtual device CPU number and memory size can now be modified from the device settings.
Corrections
- You can now resume virtual devices download.
- When downloading a virtual device, Genymotion could crash if a timeout occured. This issue is now fixed.
- The window size of the virtual device is now correctly resized to fit the host screen when rotating.
- When uninstalling Genymotion on Linux, the directory specified on installation was deleted, sometimes deleting non-Genymotion files. Genymotion now uses its own directory to fix the problem.
Virtual devices
- All Android versions
All virtual devices have been updated to 2.1.0 version to support new 2.1.0 features (Device ID/Android ID widget, copy/paste).
They now have a default device ID (000000000000000) instead of ‘none’.
- Android 2.3.7
The built-in timeout that makes the device screen unresponsive after 60 seconds of inactivity has been disabled.
- New Android version
All Android versions
- Android 4.4 is now available for Genymotion, supporting all 2.1.0 features. The following devices are available in 4.4 version:
- Galaxy Note 3
- Moto X
- Nexus 4
- Nexus 5
- Nexus 7
- Nexus 10
Genymotion 2.0.3 (December 18th, 2013)
Genymotion Desktop
Corrections
- If VirtualBox DHCP server is already configured, Genymotion will start correctly.
- Modifications of virtual devices settings were only applied to the first selected one. This issue is fixed.
Genymotion 2.0.2 (December 16th, 2013)
Genymotion Desktop
Migrating from v2.0.1 Genymotion comes now bundled with a version of ADB. You can still provide a path to an Android SDK if you want, and Genymotion will use Android tools from this SDK. If you previously set a path to a specific Android SDK version, Genymotion will continue to use it.
New features
- Genymotion automatically reconnects to ADB
- Many users reported that their IDE doesn’t detect anymore their Genymotion virtual devices after a period of time. Genymotion virtual devices are now automatically reconnected to ADB, avoiding problems when IDEs restart ADB daemon.
- Sound capture in screencast feature
- Sound emitted by the virtual device is now included in videos recorded with Genymotion screencast feature.
- Cache cleaner
- To speed up future deployments and optimize your bandwidth, Genymotion stores all downloaded virtual device files in a cache. As these files can represent a significant amount of disk space, you can easily remove them (as well as log files) from the Genymotion settings panel, in the miscellaneous tab.
- Confirmation email
- On Microsoft Windows platforms, Genymotion binaries are now digitally signed, avoiding some false positive alerts from antivirus software or confirmation warnings when launched.
Corrections
- Genymotion can now detect and work around the fact that VirtualBox installation path has changed.
- In the GPS widget, the map search field is now using the proxy configuration.
- The GPS widget works even if the network was unreachable at Genymotion launch.
- When deploying a new virtual device, the window listing its characteristics doesn’t show cropped text anymore on some platforms with a particular screen size.
- When using it without license, Genymotion window title do not blink anymore, making UI automation easier.
- Genymotion now reports network configuration in its log file, making easier to detect installation problems when contacting Genymotion support.
- Some typos and internationalization strings were fixed.
- Avoid CPU overheat while using remote control.
- Windows uninstaller only cleans required files.
- Users who were having white or black screen at start (with error message: “Unable to switch to context, eglGetError=3004”) will now start correctly without having to fullscreen, then un-fullscreen their Genymotion virtual devices.
- Virtual devices: HierarchyViewer, UiAutomatorViewer and DDMS file explorer are now working perfectly with Genymotion.
- Virtual devices: GeoFencing API from Play Services and GeoCoder API are now working.
- Virtual devices: Fixed some inconsistencies between xdpi/ydpi and logical dpi.
- Virtual devices: Correct handling of configured dpi of system drawable resources.
Added new devices
- Galaxy Note (2.3, 4.1)
- Galaxy S2 (2.3, 4.1)
- HTC One (4.2, 4.3)
- Moto X (4.2, 4.3)
- Nexus 10 (4.2, 4.3)
- Nexus 7 2012 (4.1, 4.2, 4.3)
- Nexus One (2.3)
- Xperia S (2.3, 4.1)
- Xperia Z (4.2, 4.3)
Genymotion 2.0.1 (November 14th, 2013)
Genymotion Desktop
Corrections
- Errors in SSL handshake could block user authentication with Genymotion Cloud
- Pressing Enter in authentication popup canceled user authentication process instead of launching it. Default focus have been updated
- Pressing Add new virtual device button could be inactive in some situations. This has been fixed