I do not know how to explain to you but whenever I try to type anything to the code editor of Android Studio on Mac, it turns out to be very crazy and funny. To make long story short, what I type is not what I see in the code editor as you can see in the video linked below:
https://youtu.be/tYh5keNHmk8
Thank you so much indeed.
i think there is a problem with the circuit and voltage difference on your mac computer and the keyboard which leads to this issue. I researched thoroughly on the internet but could not find any similar issue. In this case I would suggest you to try a new keyboard to see how it goes.
Related
In my Unity GUI, some of the texts in the engine can not be seen. I have attached some screenshots from my Recorder and Package Manager. How can i fix this, is there anyone that experienced that kind of glitch?
I am using Unity 2020.3.21f1 on the latest MacOS.
Try restarting unity, and if it does not work, try restarting your pc. Any recently added unity mods might also cause this. Wish you luck!
I'm using opengl es 3.0 API with the android studio ndk to create apps.
But I've encountered a very huge problem. I've created a demo app, all it does it change the background color of the screen from white to black and vice versa, every frame. And so when I go to minimize this app, I still see it rendering the background, mostly at the edges of the screen, and not in full color but still very strongly apparent. And it doesn't go away when I close the app, when I restart the device, or when I run "kill apps" on it. Only a factory data reset fixes the issue, so it's not easy for me to debug this.
This is the relevant code that I'm using for when the app is minimized and receives the APP_CMD_TERMINATE event:
eglMakeCurrent(engine->display,EGL_NO_SURFACE,EGL_NO_SURFACE,EGL_NO_CONTEXT);
eglDestroySurface(engine->display,engine->surface);
engine->display = EGL_NO_DISPLAY;
engine->surface = EGL_NO_SURFACE;
I've error checked that eglDestroySurface() is successful.
And I've put debugging messages in to make sure that the main draw loop is NOT executing when the app is minimized. But the problem persists and I don't know what to do about it. Thanks for any help.
UPDATE: well, no one has responded, and I still don't know what to do. Could it be related to threads?
UPDATE: Still can't determine what it is, but for some reason it's messing with the System UI. Willing to upload my entire source code somewhere if someone would be willing to go through this with me, as I'd really like to be able to continue working on my game engine.
Is it the "Strict Mode" developer option on the device settings, perhaps?
That one flashes the screen if an app is blocking.
It would explain why a factory reset changes behaviour.
The answer is not a solution here. The above comment by the user columbo was correct.
I've demoed switching from black to white at high framerates on 3 different android devices, and also my Linux Desktop, all via the openGL api, and it has exhibited this issue on all the devices. So what he said must be correct: this is a problem with LCD monitor technology itself. Interestingly, doing completely random colors does not cause this problem.
I remember having fixed this by finding a value in the registry that appeared to be overriding the how the images were shown, but I can't remember where it was, nor the source that showed me. I'm getting annoyed again at having images such as these show up when I pin them to my Windows 10 Pro Start Menu:
I know that there was a fix for this, but for the life of me, I can't seem to remember what it was.
As a note, I had tried tweaking with the shortcuts found in C:\Users[me]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Chrome Apps
to no avail. I swear the fix was related to something simple in the registry, but I can't place my mind on what it was. Any suggestions?
I have installed Xamarin under Visual Studio 2015 Community Edition, including the intel HAXM hardware acceleration, but I have a problem with the emulator:
None of the default Xamarin avd's seem to have been installed
When I create one myself and run it, it doesn't look right.
The attached image should make it clear. As you can see the top bar takes up about 1/5th of the screen height, and the bottom bar about 1/4.
Does anyone know what is wrong?
I'm also confused by the buttons on the right hand side. Are they supposed to be there?
VS can use AVDs but it's better to use emulators for Android for VS. It is using Hyper-V virtual PCs.You need to download and run Visual Studio Emulator for Android, then download VMs
Because the screen display size is too small. You should use an AVD Device Template to get a normal size:
When you launch it, make sure that the display doesn't get scaled. You can scale this, but you might accidentally make it too small
The buttons on the right are due to the Skin you have selected.
Based on your screenshot, it looks like you potentially are using the old version of emulators. Make sure to update your Android SDK tools and then re-create an emulator to benefit from the 2.0 emulators:
https://developer.android.com/studio/run/emulator.html#dependencies
After a reboot things seem to be working which weren't before, so I guess something hadn't finished installing. I still find that when I use a skin I don't see any message about hardware acceleration HAXM working, but I think it probably is. With regards to speed, it improved dramatically when I selected the option to 'Use host GPU'.
The HVGA skin still looks wrong, but I downloaded some ones for the Samsung Galaxy which work well.
I get "Unable to activate Windows Tailored application" error in Metro app when I'm running it under debugger of Visual Studio 11. I installed Windows 8 x64 Developer Preview on my Dell E6510 laptop.
I googled it and found out many people saying it happens when screen resolution is smaller than 800x600 but it's 1920x1280 in my case.
The app itself contains nothing. It's just empty wizard created application which is nothing but windows with black background.
Any ideas? It seems like very common issue.
The solution was quite bizarre but I figured it out.
It turns out not a single Metro application works under Administrator account including my apps. I'm talking about built-in Administrator account that is disabled by default (but which I enabled).
It gives "Access denied" error so I suspect it's somehow related to the way WinRT COM objects were registered or something like that. Go figure.
I hope somebody from Microsoft is reading this.
Best solution is to wait 2 weeks for the next release. The developer preview is full of fun bugs like this. I've seen this error caused by invalid app.xaml. Double check that you really haven't changed anything. I've also seen this error sometimes resolved by rebooting. Have fun!