bluestacks android settings developer options

I switched it to 'Always'.Ģ) I have specifically chosen to create custom main manifest (AndroidManifest.xml) even though I should not need it. I thought this was specific to my game, but having tried URP and 3D templates without any scripts, I have seen that they all show a black screen.Īfter spending several days on this weird issue, I figured out that in build settings the following options may cause instability for BlueStacks:ġ) My blit type was chosen 'Auto'. Keep in mind that a lot of Unity games are working just fine on BlueStacks. This BlueStacks issue bothers me because there might be real devices out there that have a similar issue and since the scene does not crash you may never know how many real users see a black screen and can't play your game. On contrary,other emulators such as LDPlayer and Memu work just fine.

The opening scene shows a black screen without crashing. However, you can turn off developer options entirely - and that'll turn off 'allow mock locations'.

You're right, the option to turn this off isn't in the developer options. That’s a subtle quality-of-life improvement to easily debug apps without having to rely on Android emulators. Allowing mock locations is enabled by default in Bluestacks (to use the 'set location' widget on the left bar). WSA will show up as a device in the IDE’s device manager. First, like phones, you need to open the developer option - allowing USB debugging of the emulator.Some simulators may need to find Settings - About Phones. It seems like there is a serious problem when you try to run a game built with the default Android build settings on BlueStacks emulator. After enabling developer mode and setting up ADB, developers can use Windows Subsystem for Android to run and debug apps.

Bluestacks android settings developer options