Step 4 - In Unity under preferences set the path to the Android SDK. C:\Program Files (x86)\Android\android-sdk or something similar.
Step 5 - Close Unity
Step 6 - On your android device ensure that in Application Settings that USB Debugging, Stay Awake and Allow Mock Locations are all enabled.
Step 7 - Connect via USB and launch the remote app.
Step 8 - Launch Unity
Step 9 - Run your game in the editor
Step 10 - Enjoy
Each time you restart the Unity Remote app you must restart Unity or the app will not pick it up. If I am in for a long dev session I plug in device and run remote and then begin work. Means I dont have to keep restarting Unity.
I hope this helps everyone who has a problem with Unity Remote on Android.
Anyway this driver will only work for Samsung devices but if you’re having the same problems with your own device and Unity Remote, go to your Device Manager on Windows and make sure in the other devices branch (when your device is connected) there are no yellow “!” indicating problems with the drivers you currently have installed, if so then try find your device manufacturers official drivers and hopefully this will solve your problem.
I was fed up with this problem for 6 hours or so and then i found the following solution :-
BlueStacks (android emulating software) interferes with Unity’s ability to communicate with a cable connected android device. So even if bluestacks is just installed on your system and not even running, it will interfere with Unity’s remote app and it won’t be able to run on your physical device connected via a cable. This is valid for android but I dont know about iOS because i don’t use it.
Solution - Open windows task manager and kill all tasks with the name “BS” or “Bluestacks” written on them. Then connect your device with Unity remote and follow the normal procedure as mentioned in all threads and tutorials. It shall work like a charm.
This might not be valid for everyone who’s unity remote is not working but I thought I’d just share my personal experience so it could help someone out.
Apart from the things mentioned one thing to remember is that checking “Error Pause” option in Unity Console. If Error pause is on and if there are any errors, Unity remote 4 doesn’t work.
Last time, It was nightmare recognising this option for one of our developers.
My problem was my computer wouldn’t recognize my phone (Crappy Ole’ Galaxy S3) when it was in MTP mode. I set it back to camera mode, along with all the crap in the troubleshooting guide, and boom. Works good!
Under Unity Remote: Device choose “Any Android Device”.
Connect your android device through usb cable.
Run unity Remote on your android device.
Now press play button in unity.
It will launch your game in android device.
I hope your query will be resolve after this.
If you have any query related to java you can post your query at Java questions and answers forum and get answers instantly from the experienced members.
,Please follow all steps below then check.
Here are the steps you might be missing
Go to Edit Menu:- Project Setting:- Editor.
Under Unity Remote: Device choose “Any Android Device”.
Connect your android device through usb cable.
Run unity Remote on your android device.
Now press play button in unity.
It will launch your game in android device.
I hope your query will be resolve after this.
If you have any query related to java you can post your query at Java questions and answers forum and get answers instantly from the experienced members.
For me everything works. I have Win10 x64, tablet NVIDIA Shield K1 with android 6.0. But sometimes something goes wrong - For last week everything works ok, but today I click “play” and nothing appears on screen tablet. Solution for this (for me) is wipe tablet. After that everything is ok, again, for some time (week, maybe more).
I observed something interesting:
If everything is ok, when I unplug usb cable and plug again (several times even) and type “adb devices” in cmd, I see “[device_id ] device”.
But if remote is broken, when I unplug and plug again cable as before, I see this result after type “adb devices”: “[device_id] offline”.
I have tried everything - restart pc, adb, tablet. Toggle debug usb, revoke usb authorization - nothing help me. Only wipe table is solution.
For those of you who are still struggling with Unity Remote 5, I have a solution. I found this after 4 stressful hours. Once your adb drivers are installed and your device is listed in “adb devices” command output, do the following:
Go to Edit > Project Settings > Editor and choose Any Android Device.
Now do this one time. Go to Edit > Build and Run. This way, your game will be compiled and pushed directly to the device.
Next time, when you open Unity Remote 5 app and click on play on Unity editor, the scene will appear on your device.
On Unity 5.4.1f1 it is working on my OnePlus One.
I installed Unity Remote 5 (Version 2.0).
It doesn’t matter wich USB Protocol i have activated (only loading, MTP and PTP are all working).
The only thing i have to do if it displays nothing is:
The ANNOYING Problem is that windows ADBexe manager may not be detecting your device. Go into task manager - services and end the process tree of the adb.exe. Restart unity and hopefully it will work. This worked for me - sometimes you have to do this with android studio!
I have tried everything listed here but une Edit > Preferences I dont see any sdk path or something similar did I miss something or did it juste disappear in unity 5 ? Edit > Preferences ?,I tried all the steps listed here but nothing seems to work, I have my LG G5 running Nougat, Unity remote 5, I have installed the USB google driver, But under oreferences there is no path to the SDK, did I miss something are we talking about Edit > Preferences ?
