Android – Genymotion 2 – No Connection on Google Play Store

As of Genymotion 2.10.0 and onwards, GApps can be installed from the emulator toolbar. Please refer to answer by @MichaelStoddart.

Next follows former answer kept here for historic reason:

Genymotion doesn't provide Google Apps. To install Google Apps:

1. Upgrade Genymotion and VirtualBox to the latest version.

2. Download two zip files:
   - ARM Translation Installer v1.1
   - Google Apps for your Android version: 2.3.7 - 4.4.4 or 4.4 - 6.0 (with platform and variant) You can also find the GApps list in the wbroek user GitHubGist page.

3. Open Genymotion emulator and go to home screen then drag and drop the first file Genymotion-ARM-Translation_v1.1.zip over the emulator. A dialog will appear and show as file transfer in progress, then another dialog will appear and ask that do you want to flash it on the emulator. Click OK and reboot the device by running adb reboot from your terminal or command prompt.

4. Drag and drop the second file gapps-*-signed.zip and repeat the same steps as above. Run adb reboot again and, once rebooted, Google Apps will be in the emulator.

5. At this point 'Google Apps Services' will crash frequently with the following message google play services has stopped working. Open Google Play. After providing your account details, open Google Play and update your installed Google Apps. This seems to make Google Play realize you have an old Google Play Services and will ask you to update (in my case, updating Google Hangouts required a new version of Google Play Services). I've also heard that simply waiting will also prompt you to update. The 'Google Play Services' app doesn't seem to appear otherwise - you can't search for it. You should then see an offer to update Google Play Services. Once the new Google Play Services is installed you will now have stable, working access to Google Play

It is not a very good idea to use PGPoolingDataSource, as JDBC documentation explains.

The base problem is that the call for getConnection() will be blocked until a connection is closed when the limit of connections has been reached.

You've set the value 30 as the max amount of concurrent conections, so if a 31st is intended to be opened, it will cause a block on the Thread making the call.

Possible solutions:

• Increase maxConnections, if you are certain about the real amount of concurrent connections upper limit. You should also check the server-side connection limit in postgresql.conf.
• Use PGSimpleDataSource. Depending on the type of application, not using a pool of connections (thus creating the connection each time) will not be a problem.
• If you really need a pool of connections, simply implement your own at Java level.

EDIT: You can check the amount of opened connections by simply running:

SELECT * FROM pg_stat_activity

Each row is a connection (including the one from pgAdmin and the query analyser). If you are certain that the number of connections should not raise up to the upper limit (but nevertheless it does), maybe you are having some sort of connection leak problem.