#POKEMON GO GENYMOTION ANDROID#
Unfortunately basically no one actually uses Android on PC hardware for anything, so not a lot of people have an interest in making this work. This would seem to be the most promising way to run Android on a PC, because it’s the fastest. I would leave it there and move on, but in the interest of getting some kind of value from the time I wasted on these attempts, I’ll write down some of the problems I encountered. This entire class of activity is too niche to be supported well. Only the last one of these allowed me to successfully run Pokémon Go and isolate the traffic from it, and then only briefly.
#POKEMON GO GENYMOTION WINDOWS#
Bluestacks Android ARM emulator on a Windows guest VM.Bluestacks Android ARM emulator on a Windows host.Genymotion Android VM on a Windows host.Standard x86 build of Android in someone else’s pre-made VM.Standard x86 build of Android installed by me in a Virtualbox VM.This is wrong, but never mind, here’s what I tried: I figured cleartext packet captures might be easier to come by if the source was a VM on my laptop. Even with root, you have to jump through more hoops, and there are more tools available on a PC. Initially I wanted to do all my experiments on a PC, since it’s easier to mess around on a “real” computer than on a physical Android device. Don’t touch any variant of Android on an x86 host Maybe Microsoft’s own upcoming port of the core Linux utilities will be better, or maybe I’m just not good enough at computers to immediately get the hang of this version.
#POKEMON GO GENYMOTION INSTALL#
I went so far as to even install a Windows version of bash to try to improve the shell experience on the work laptop from my summer job that I used for this project, but that didn’t really help. But when you’re trying to do anything UNIXy, like talk to an Android device over adb, Windows isn’t going to help. You certainly can do anything on Windows that you can on another other computer. This is neither here nor there, since people already have plenty of preferences about OSes, but it ended up getting in my way in this case. Since I spent some time on it, I figured I’d write up what I learned from the experience. The more dedicated ones are still working over at /r/PokemonGoDev.
This is probably a losing battle for Niantic, but it sufficiently discouraged casual tinkerers like me. It would definitely be fun to find any glaring security holes that were now suddenly affecting a huge number of people.Įventually I gave up on this after Niantic caught up to the reverse engineers and made it more difficult to decrypt the traffic. Practical applications of this include finding the exact location of nearby Pokémon, reporting security bugs, and of course cheating. While they had their hands full, I thought it would be fun to try to reverse engineer their protocol and try to mess with the app.
So have tens of millions of other people, so many that the developer Niantic was completely unprepared to handle this level of interest at first.
0 kommentar(er)
