I have set up my DDMS to work with the emulator and display the processes running etc. but in the Dev Tools of my emulator it firstly wont let me tick the Show CPU Usage box, and secondly I do not seem to have an option to display the FPS which apparently, according to sources on the internet, is possible to do.
Has anyone had this trouble and know how I can solve it and display CPU usage and FPS as my android game is running?
Thanks
To get an idea of what CPU speed your emulator is emulating try this:
1) start a shell session (adb shell),
2) then run "cat /proc/cpuinfo" to get the BogoMIPS.
Here’s more information on this.
Related
I am attempting to learn to code via flutter (I'm a total noob) and I am having some troubles with my emulator when I am trying to test my code. I am using Visual Studio Code, and when i try to boot my emulator, the phone will appear but the screen is completely blank. the power button (on the emulator) is unresponsive and I get an error "emulator didn't respond in..."
I have literally been fighting with this for hours and I could really use a knowledgeable hand. Can anybody help me troubleshoot, by chance? I have searched here, but nothing matches exactly what I'm going through and I haven't been able to solve it yet.
errors with android emulator
My computer spec:
Processor Intel(R) Core(TM) i5-1035G7 CPU # 1.20GHz 1.50 GHz
Installed RAM 16.0 GB (15.7 GB usable)
Device ID 45818A1F-CFA5-4E12-AB9C-8192B75D2308
Product ID 00325-96713-52283-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Okay, so this probably seems obvious, but I seemed to struggle with this at the beginning since my course has me learning in VSCode, but I went into the android studio instead and I have deleted the old emulator and created a new one. It's taking a while to finish loading, but the screen is operating and I think my problems are likely solved.
So I guess no, I never figured out why it wasn't working, nor did I get it to work. but the end result is the same.
enter image description here
enter image description here
Please see the pictures in the link above.
I'm new to unreal engine. I've been trying to get Unreal Engine 4 to work on my linux machine ( 5GB RAM & 500GB Harddisk) but I couldn't get the viewport to work. It always shows blue or black screen.
Please I need assistance. Thanks in advance
I am also a UE4 user / game dev and use *nix. Usually the behavior you describe happens when there is a video display issue. In Window this is usually the Nvidia Game Ready driver, sometimes new updates break things, there is a common fix involving a registry edit called mpo_disable.reg - anyway, you are not using Windows, just for anyone else who lands here via Google-Fu.
In your case I would say it could be related to the video drivers. Which distro / kernel and video driver are you running? Nvidia card?
I have tried to export my game to mobile APK. When I'm export my game to 32-bit APK, everything is working fine and smooth
But when I'm trying to export as 64-bit APK, the gameplay is a delay (eg: when I click a button, it need wait few seconds or more to have a response, this case is not happening in 32-bit APK). But the sound effect and background music is playing fine, didn't have any delay for the sound.
Below is the setting for my 64-bit export
Setting:
I will get these warning message after I exported, are these may caused my issue?
Warning Message:
May I know have what issue or reason may cause this situation happen? Hope have someone able to helping me to solve this issue. Thank you
UPDATED:
I found reason is my script have to much FixedUpdate process in running to cause delay. So, I reduce the number of FixedUpdate to solve the problem.
May I know why 32-bit able to support the number of FixedUpdate, but 64-bit unable to support?
On what device are you testing this? An Android emulator? This could be just an emulation problem and not be an issue on a modern real-world device.
Try disabling stack trace option for debug logs.
You can find it in the player settings, at the bottom of "Other Settings"
Set "Stack Trace" for "Log" to "None"
I recently read about the HAXM , followed the steps, for first few days emulator used to get started in less than minute but now it gets stuck at this point - as shown below.. although it shows correct time & clock remains working . The worst part is all of the emulators I create show same problem .Any solution ?
You can try couple of things here
Check the RAM size allocated for Emulator. The best RAM size recommended is around 512MB for an Emulator. Make sure you have set the appropriate RAM size
Kill all your emulators, restart your machine and create fresh AVDs
Is this happening with the same application or different ones? a little bit detail on the application will help in suggesting more work around.
a. If it is an OpenGL application choose use Host GPU on your AVD and also install the correct graphics driver on your host machine
Every time I run a project from ADT to test on a virtual Android device it takes 90+ seconds to upload and another 15+ seconds to "install" it on the device.
Why does it take so long?
Any timeouts I should watch out for? (The eclipse console stays silent.)
Note: project.apk size is about 5MB and computing resources on the development machine are plentiful (i.e. CPU usage is around 5-10%, disk queue length about 0.05 and couple gigs of free RAM available during the "upload" and "install").
Not really a solution, but a workaround was found in a similar question:
Slow uploads to running Android emulator
It appears, when the Android emulator is idle its network connection is capped at 2 Mbps
and when you wake it by clicking and swiping around the bandwidth magically increases to around 10 Mbps! (At least so on my fairly modern system.)
This obviously makes a difference for uploading largish apps to the emulator.
Solution:
Go to Run -> Run Configurations... -> Target Tab -> Additional Emulator Command Line Options. Add there:
-netspeed full -netdelay none
After doing this the time for uploading went from 2 minutes to 8 seconds.
Edit:
I have also found that quitting Skype makes my emulator upload much faster.