Hello, I am making an Android game, and since 1 month ago I am using the Unity Remote.
As time has passed, the Unity Remote has had more problems to work the Touch (the half of the times I tried it, didn´t work).
But now, I can´t get it to work. I was using in the code “mouse events”, and I am changing it to Touch events. But now it don´t work.
I read that mixing these two input modes can make it to fail, but now I made a test proyect from scratch, and don´t work (using only Touch input).
I follow this process to connect to the PC:
I start Unity Remote,
I plug the phone to the PC,
Open Unity,
Press Play button.
And the image is showed in the phone but the touchs don´t work.
Any hint?
I am using:
Samsung Galaxy S DUOS
Windows 7 Professional 64 bits
Unity Free 4.3.3
This is my personal opinion, but honestly, the Unity Remote is… Ahem I’ll try to keep my words and feelings in check, but let’s just say it’s really buggy.
And I have a S4, by the way, with Unity Free (4.3.2). Many events do NOT work, but Touches work for sure (as I set GUI Textures that only worked via touches, which was a mistake I’ve definitely amended. Had to use the PC to press the GUI Buttons, then use the phone to use the GUI Texture buttons).
All I can say, is double check your test project. Touches are the ONLY thing I rely on for the Unity Remote- I even use the PC screen while using Unity Remote. There’s a good chance you may be doing something wrong, but there’s also a really good change Unity Remote isn’t simply working in your case. A bug report would probably be helpful.
(Also, I apologize if that didn’t really flow too well together)
Can you try this small test?
It is only a button that changes its rederer on/off when you touch it. When I compile the apk and build to the phone it works correctly, but using Unity Remote don´t works.
Thanks.
1550409–90881–$TOUCH TEST FOR UNITY REMOTE.rar (1.09 MB)
Just tested right now (yay for waking up 10 minutes before you posted), and works quite well. However, I get this error every frame:
I would try this myself if I actually had enough time, but try to make it far more simple. If a touch is ever detected, no matter its position, send a message to the console. Then you can try working from there to see if it works at all and/or its accuracy.
Edit: The error doesn’t come up every frame, but every tap. Typically, one comes up when hiding it, 3-4 come up when showing it. Here’s the second repeated error: (the less common one actually)
It probably has something to do with “BroadcastMessage”, I’ve actually never used that in C# to call a function, although I used it when I began to use US. Typically, if it’s simply a non-static function, I use objectName.GetComponent().functionName()
I use “BroadcastMessage” to send the message to all childs of the camera at once.
I did send a bug report, to see if they can reproduce the problem.
Thanks you, I will post here what happen.
Regards.
If you add a “//” to the follow lines in the “DetectarTouchGUI.cs” script, it will not give any error:
…
//gameObject.BroadcastMessage(“UnSelected”);
…
//gameObject.BroadcastMessage(“Pulsando”);
…
I got it work today. I think that if I didn´t compiled it at least one time to the phone, the touch with Unity Remote will never work. Maybe was something related to “magic”… or the planet positions, but today it worked.
The strange thing is that it are talking about to the old location of my proyect folder "DetectarTouchGUI:Update() (at **D:/PROYECTOS 3D VARIOS/**PRUEBA DE TOUCH MIO PARA UNITY REMOTE/Assets/DetectarTouchGUI.cs:9) "
Black magic, maybe? Maybe Unity snuck something in there when you weren’t looking.
By the way, did it work with or without the comments? And I think BroadcastMessage is different in C#, as the errors kept stating there was no “receiver”.
In the end, yay? 
Guessing it works here on out?
(Also, is there a possibility that you just recently added the driver(s) for your phone, so now the drivers have been fully implemented [Unity3D/computer/something similarly important restarted?] and it works as it should? Complete guesswork on this part though)
It did work without the comments, and later I did put the // and the error messages go out ( and did work too).
I didn´t installed any drivers of my phone, it is identical as 1 month ago (when the Touch did work ok).
I received response from Bug Report´s Team :
We are creating a new Unity remote which will be much more stable. It will be released together with a Unity update since editor changes are required for it to work.
Adb.exe issue is already fixed in the internal Unity version and the fix will be included in the upcoming Unity updates. For now you can workaround this issue by manually starting adb.exe process every time after restarting the computer and before starting Unity editor. You can do that by running the ‘adb start-server’ command.
I will close this case now. If you will still experience Unity remote issues after we will release a new remote, please submit a new bug report. If you have further questions regarding this case however, feel free to reply to this email.
There is a bug remaining with the ADB.EXE process, that was marked as Fixed in the 4.3 Update but it isn´t (Freezes Unity at close, or when you try to open other proyect. You must to force ADB.EXE to close manually in the task manager).
I executed the “adb start-server” before run Unity and seems to work fine in several try I did now. And Unity closes correctly and open other proyects.
Nice, guess problem’s “solved”. 
I’m actually surprised - for some odd reason - that they’re going to improve the Unity Remote- just not too optimistic about how improved it’ll be 
By the way, it’s odd how Unity says it’s up to date even though I have version 4.3.2 and not even 4.3.4. As I don’t think I can subscribe to update notifications, I guess I’ll have to frequently check from now on for the next update. Just hoping it’s 4.3.5 so I don’t have to do too much guesswork/research of what’s in the 4.3.4 updates
Great 4.3.4 update… (only 2 things):lol:
I have the same problem, since 2 or 3 Unity versions, Unity don´t notify me of a new Update is available. They must solve it…
Regards.