Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
1
Found in
2018.4
2019.3
2019.3.1f1
2020.2
Issue ID
1251622
Regression
No
[Android] Unity Remote doesn't work with Android devices
Unity Remote 5 is using HKEY_CURRENT_USER\Software\Unity Technologies\Unity Editor 5.x\AndroidSdkRoot_h2651068356. Instead, it should use the value from Unity Preferences > External Tools > SDK
Steps:
1. Install Unity via Hub and select the checkboxes for the built-in Android Build Support SDK/NDK/JDK
2. Install and open Unity Remote 5 on the Android Device (https://play.google.com/store/apps/details?id=com.unity3d.genericremote)
3. Connect the Android device via USB
4. Open CMD and enter
taskkill /f /im adb.exe
(if it doesn't work, then enter "adb kill-server")
5. Now enter
reg add "HKEY_CURRENT_USER\Software\Unity Technologies\Unity Editor 5.x" /f /v "AndroidSdkRoot_h2651068356" /t REG_BINARY /d 0
6. Create and open a New Project in Unity > Change Build Target to Android
7. In Menu bar: Edit > Project Settings > Device to use > Any android device
8. Click the Play button in the Editor
Expected: project appears on the device.
Actual: nothing happens - project does not appear on device.
Reproduced with: 2018.4.23f1, 2019.3.16f1, 2020.2.0a13
Reproduced with:
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
with
Windows 10
WORKAROUND:
Edit HKEY_CURRENT_USER\Software\Unity Technologies\Unity Editor 5.x registry and set AndroidSdkRoot_h2651068356 to the path of built-in SDK path.
-
ienconor0
Aug 31, 2021 05:56
I recommend you to read this article - reddit.com/r/Unity3D/ - here you can find information on how to develop a successful taxi app, cost and how to compete.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
fixed in 2021.1.0a2.727
Resolution Note (fix version 2020.2):
Verified fixed in:
Version: 2020.2.2f1