[Miscellaneous Android Development] Nephatiu:
Dude, it's the stock ROM, I didn't flash any other Android on it. I rooted and modded the one that was on it completely by myself, so anything done to it was done by me. So I know what's been done and what hasn't and I didn't mod anything for Google Play, since that was one of the first things I added after rooting. The exact procedure I used was putting Play Store and the GoogleSyncAccounts-apk in /system/app with root explorer and installing the Play Services in data/app with the Android build-in Installer. Maybe there was another file involved, which I'm forgetting at this time, but I can asure you, nothing was changed to the Android itself, certainly nothing camera-related.

Correction, Google knows every model device out there it has encountered. Android is open source, People like you and I can make Android-devices, if we had the tools for it. In that thought, there are thousands of cheap Korean a.o. Android devices created new every day, I would think it to be very hard to be able to have a list of every possible device. And it would take an infinite longer and longer time every time it had to check your model against it's ever growing list...

lol! Did you just say Play Store doesn't look at your dpi? Why does 90% of all Play Store hacks only do 1 thing then? Fake a dpi. :p dpi is actually one of the main things it looks at to see f your device is compatible with apps. ;)

First of all: it required another dpi setting, you could set your dpi to something arbitrary or just 1 off and you'd have that effect... Just try it, and then you'd need to reset the dpi to something standard to get all the apps back... And second, I'm sorry, but the Vending.apk I first installed on my Kindle Fire was the Market and not the Play Store,... It even had the green shoppingbag back then. This due to me picking the wrong zip file in a list of downloads, selecting a very old copy instead of the freshly downloaded,... It did however work, and on first reboot even update itself to Play Store. I then copied the new play store over the old Market I originally placed in /system/app and haven't had any problems since...

Try setting your dpi to 160, 240 or 320 on the ones that don't show those apps ;)

Even more reason not to sell apps that are questioned to work on your device.

You did say the backwards facing camera was a requirement (as in 'it does not work without'), although my Play Store works on devices without one out of the box. No hacks, no magic.

There's installing, and installing... ;) Google Play Store isn't just any app you can just 'install'.

Defaults now are that GT-I9100, as we've all agreed, I'm just saying it's not there because of the Play Store... That works whatever you put there.

I joined in at 0.6.3, eventually always got Play Store to work, but as I mentioned before, it gave much more problems in 0.7 (and below). It has always been identified as BlueStacks here, and Since 0.8.x I got a new device saying T-Mobile GT-I9100, which was my first experience with the fake SII. :p Thought it was funny, but didn't really question it at the time.

Flashing in recovery mode can be done in Terminal Emulator if you know a little bit of UNIX, though. install.zip's are just zips with files and an install script not much unlike an sh-script, which can just be done yourself inside of Android (you'll have to reboot after it though. :p). The recovery install is for devices with a locked root.fs filesystem, but that's not the case with BlueStacks as long as you use the unlocked initrd.img ;p

Yeah, Google isn't fragmented at all and everybody knows every hack to any Google thingie over there... Suurrreee... :p Excuse me for that not making any impression as I know how deep the fragmentation of Google goes and you don't even seem to know DPI is an important part (but definitely not the only, as location plays a part too, and since for short if the device is a tablet or not) of the decision if apps are compatible or not. ;) (As seen here.) (even though 90% of all Android apps are scalable,...)

EDIT: Oh, and for the new SuperSU, I've been meaning to get to it, but as you can see at the time between my reply's, I nearly have just enough time to check my browser for updated sites. Even now I do have a bit of free time, but I've also been awake since yesterday morning (a little over 38 hours right now). It being 1:48am here now, I should actually say awake since 2 days ago, but it hasn't been 48 hours yet (and I hope it won't become either :p).

I did try once, to no avail, but I think I overlooked to do some things as I didn't really have the time for it then either. :D

EDIT BIS: I had an idea of what was wrong as to why SuperSU can't update, so instead of going to bed, I reinstalled the last SuperSU with binaries in a new rooted BlueStacks, holding in mind what I thought was wrong. After booting my first time rooted, not only did root work as it should, the /system mount was actually mounted read-only again with a modded rw initrd.img, meaning Android now even gets access to the su binary while booting, like on any regular rooted device. (Before /system always just mounted rw) This makes me believe that this could also be the reason it couldn't update itself. Can't say for sure of course, until it updates again, but I hope it's fixed now and it will be able to update by itself... Worst case scenario I fixed the su access on boot anyway, so fingers crossed... ;p

The new SuperSU v1.80 BS v0.8.2.3018 rooted files are uploading as I'm writing this, so expect them in a few. ;)

Grtz,

~ Nephatiu ;)