I want to get performance analytics of my game using Profiler so I have exported build with Autoconnect Profile setting enabled.
After this process build installed within an Android device but it can't able to run the game, it just displaying black screen nothing else. Profiler can't able to connect with the connected Android device, I was getting this kind of list within Unity profiler:
Now android device showing just black screen and profiler not moving ahead, it just remains connected with Editor only.
I have tried to connect and disconnect my Android device multiple time but nothing changed in this. Please give me some suggestion into this so I can start my debugging process.
I have already gone through this post:
Profiler window
I believe you need to build in DevelopmentBuild enabled to be able to attatch profiler
Related
I've been learning and working with Flutter for a few weeks now. I used some of the Android Emulators that Android Studio provides and it was doing fine.
But recently, I opened an emulator to run a Flutter project while a memory card was connected with my laptop, and suddenly a notification was shown in the emulator of detecting a SD card and with that another notification was shown saying:
Serial console enabled
Performance is impacted. To disable, check bootloader
The notification is not clickable, and neither it removes even after I deleted all the emulators that I installed using the AVD manager. And as the notification says, it really is impacting the performance of the emulators. Before it showed up, I could see the changes in the app immediately after making changes to the code and saving it, but now, it takes so much time to show the changes even if I use hot reload or hot restart.
Is there any way to get rid of this? How can I disable the Serial console?
Enter engineer mode (*#801#) and disable the option that says serial. Google it how to access engineer mode if the code doesn't work for you.
Out of blue the android emulator with google play services API 27 did not unlock its screen. After I insert the password on Mac Mojave I get back the lock screen instead of accessing to the device. I try to swipe up but does not work.
I tried without success to uninstall the emulator, to wipe data, as I found in this other post My Emulator won't unlock. Is this a known bug? I cannot find official google list where people complain about this issue, so I am wondering what I did wrong. I have also tried to activate the camera, but does not work as suggested in the above mentioned post.
I expect that when I insert the just password the emulator is unlocked, the just password is 0000 and I do not get a wrong pin message, but a black screen for 800 milliseconds and then the lock screen with some notification.
Can you try wiping the data and reboot. Or try creating a new emulator with Nexus5X with Android28 or other.
When you try to start the emulator from Android Studio, in the AVD manager, select the drop down and Wipe Data.
Im trying to run the sample app provided in the daydream page on the google pixel phone.
1) I chnaged the build settings to android.
2) Went to player settings enabled Virtual reality support and selected google daydream as the platform.
3) I changed the Minumum API to API level 24.
4) I added the folder containing my adb to the path variable in windows.
5) I also set the path of the android SDk.
6) I enabled USB debuggin on Pixel
However when I run my app , I get the following errors:
Device daydream not supported in Editor Mode. Please run on target device.
And..
Failed to read from controller emulator app event socket.
Verify that the controller emulator app is running.
build the apk and start it on your device. build and play requires adb.
As I suppouse, you want to DEBUG your Daydream app on your Programming Environment (Unity in this case).
Note:This solution allows you to debug on your PC but you'll need one Pixel Phone connected to your PC, and one Daydream Controller.
First of all I recommend you to download the samples provided by Google on Github if you have not done it yet:
https://github.com/googlevr/gvr-unity-sdk/releases
When you load any scene you'll see that the Daydream basic set is composed for a hierarchy like:
The two selected components are key for your porpouse cause if you want to debug Daydream from your PC you'll need to "link" your daydream controller with InstantPreview App. Instant preview will downloaded instantly on your phone if you got in your scene the "GvrInstantPreviewMain".
InstanPreview Google Info: https://developers.google.com/vr/develop/unity/instant-preview
When the app has been opened, can happen 3 things on your pixel phone:
Everything works as it should.
Daydream Instant Preview infom to correct the device by USB.
Kind of Grey screen with some text.
If you're on 2.
This seems to happen when your Unity Project is desynchronized from your phone and you'll see something like:
Close InstantPreviewApplication on your phone, close your unity project (remember to save your progress), and open again your unity project. That has almost always solved me.
If you're on 3.
This seems to happens when instan preview is waiting for Unity Play Mode.
You only need to press Play on you Unity Poject.
Remember to press (and mantain) synchronize button on your Daydream controller if you can move the headset camera but can't find your controller reticle.
This works for me.
I also append my own Unity project with this scheme that works bought for Daydream and GearVR in case helps someone else to test my solution:
https://github.com/ls29322/VR_GalleryApp
i'm new into programming for android. And i have few problems with connecting and debugging my eclipse project on android device - which is my phone Samsung Galaxy SIII. According to this link I tried to launch my app on my phone. Saddly when i press run button it tells me that there's no android device connected. And as you may know im not that dumm to not plug it into my computer. Additionally i have USB Debug mode ticked in options. My PC recognises it as "SAMSUNG Android ADB Device".
Some of you might say that i should start using emulator to have better view how this app will work on other phones/versions of android/etc. Thing is that my PC is quite old, and running an emulator makes it respond so slowly that it's nearly impossible to do anything on this emulated device. Plus... im quite sure that i wont publish this app on play store so i dont need to know if it will work on other devices. I just want to make a weather widget for me since stock one that uses accuweather.com tends to fail weather forecast for my country (like it says heavy rain on sunny day).
So here are the things that i have done so far to try to launch:
1. Uninstalled device and set some new drivers that should have helped me - saddly not ;]
2. Tried launching it via command line
3. I found somewhere on the Internet that it is possible to connect and test your app via WiFi using tcpip over 5555 port... saddly it failed too.
Any ideas what else should i try to make it work?
Solution: Why is Eclipse's Android Device Chooser not showing my Android device?
THis is getting annoying. My device shows up in eclipse on all
platforms.. Except when I am on my Ubuntu laptop.. when I "run
configurations" with it set to Manual.. I can see that there is an
Emmulator running that I can Install the App to.
Problem is, the Emulator is a pile of horse crap when it comes to
testing on real devices like my Samsung Captivate.
When the Captivate is plugged in via USB.. it shows via ICON, except
the ID is set to ??????????? and nothing else seems to be registering.
I can highlight it, but I can't launch it.
The captivate I am using is Rooted and running the LagFix Kernal..
However this has never hindered me on Windows or OSX.
Help.. I am trying to go completely Linux.. if it kills me.
See screenshot below: http://img265.imageshack.us/i/sdkbugeclipse.png/
UPDATE: Device is showing in the manager even when not connected?!?!
This has to be some weird Eclipse bug.. PLEASE HELP!
Solution (in case you missed my edit) need to add the correct Samsung Device ID when using the SDK with Ubuntu: link