![]() ![]() It seems like the only place tinder wants people using their app is on their phone, where they can be tracked very well, through google.Īnyway, I'm new to genymotion, after trying for some weeks to get it working, only to figure out that tinder is one step ahead of me. Its seeming like tinder really doesn't want people jumping the fence on them, interesting. There's some modded APKs which actually work yet they are sketchy in more ways than one. This is unlike a lot of apps which have apks floating around at worst an XAPK, which is interesting to me. Search tinder APK and you'll find apkpure page that just points you to the play store. What I learned about tinder is that there is no APK around. So here the catch I am wanting to try out tinder on here (I know right. It ended up fixing itself after purging at least a couple times and reinstalling, idek how I fixed it. I had this issue where genymotion wouldn't go past the booting splash screen before even entering genymotion credentials. Platform-tools$ adb push /home/nazmul/Downloads/Phonesky.apk /system/app/.So after a while of finally getting genymotion going. Platform-tools$ adb push /home/nazmul/Downloads/GoogleServicesFramework.apk /system/app/. Platform-tools$ adb push /home/nazmul/Downloads/GoogleLoginService.apk /system/app/. Platform-tools$ adb shell chmod 777 /system/app Platform-tools$ adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system emulator64-x86 -avd Kitkat -partition-size 566 -no-audio -no-boot-anim Playstore Google Play Services In Linux(Ubuntu 14.04)ĭownload Google apps (GoogleLoginService.apk, GoogleServicesFramework.apk )Īndroid/Sdk/tools$. When finished with your testing, to alleviate your conscience guilty of temporarily pirating the Google Apps from your device, you may delete the modified system.img and restore the original from system-original.img. I did not find it necessary to delete SdkSetup.apk and SdkSetup.odex - the Play Store and other services still work fine for me with these files present. Then start your emulator (in my case it would be Android 4.2 emulator with Intel Atom processor running under Intel HAX, super-fast on Windows machines) and you'll have Play Store there. Save your modified image as system.img in the original folder. Under yaffey, copy the APK files you pulled from your device to /app folder. Rename the original system.img to system-original.img. ![]() ![]() I modify most often the one in \android-sdk\system-images\android-17\x86. Now start yaffey on Windows or a similar utility on Linux or Mac, and open system.img for the emulator image you want to modify. You must have root-level access (run adb root) to the device in order to pull these files from it. Obtaining the Google Play app from your deviceĭownloading Google Apps from some Internet site may not be quite legal, but if you have a phone or tablet with a corresponding Android version, just pull them out of your device: adb -d rootĪdb -d pull /system/app/GoogleLoginService.apkĪdb -d pull /system/app/GoogleServicesFramework.apk Afterwards I can start the emulator normally, without messing with adb, and Play Store is always there. Copy GoogleLoginService.apk, GoogleServicesFramework.apk, and Phonesky.apk (or Vending.apk in older versions of Android) to the /system/app folder of the system.img file of the emulator. You will need Yaffey on Windows, or a similar utility on other systems, to modify YAFFS2 images. I do this in a more permanent way - instead of installing the APKs each time with adb, permanently add them to the system image that the emulator uses. ![]()
0 Comments
Leave a Reply. |