simulink android package is not recognising my samsung s8 during the package set up setup

I have completed the steps required during setup but when i get to the stage of recognising the drive it shows nothing even after efreshing can someone help please?

[Sruthi Yenugula]

Can you try again and if you still face the same issue, please provide the following information: Please execute the following commands in MATLAB prompt. Replace the username with your system username while executing. First command would be the path of the Android SDK in your system, that is default location. If you had changed the location please use changed location.

sdkPath = 'C:\Users\username\AppData\Local\Android\Sdk'

[s,r] = codertarget.android.internal.runAdb(sdkPath,[' devices'])

[Matthew Bigelow]

Hi Sruthi Below is the execution of the commands you asked for. Im assuming this means there is an issue with the white space in the username? How do I fix that without messing up all the other apps on that path?

sdkPath = 'C:\Users\Matt McDonald\AppData\Local\Android\Sdk'

sdkPath =

    'C:\Users\Matt McDonald\AppData\Local\Android\Sdk'

>> [s,r] = codertarget.android.internal.runAdb(sdkPath,[' devices'])

s =

     1

r =

    ''C:\Users\Matt' is not recognized as an internal or external command,
     operable program or batch file.
     '

[Sruthi Yenugula]

Thanks a lot Matthew for your patience and providing the information. We got to know the root cause of the issue. Space in your username is causing the issue. Will provide you the patch(fix) shortly.

[Matthew Bigelow]

Thank you Sruthi I look forward to your response it has been a frustrating couple of days. Just for further information, I did manage to connect my device on the same computer using 2017b although when I tried to run a simulink model on the android device I received the following error.

"Android build tools don't support folder names that contain spaces. Use a folder name that does not contain spaces."

Im assuming that is referring to the same folder where the sdk files are held and should also be fixed with this patch you are generating. Your help is much appreciated the project I am involved in is quite urgent.

[Sruthi Yenugula]

This error is due to your working directory, it has space and not because of sdk path. Can you change the path which does not contain space. Basically your project directory. Don't use the patch for 17b

Answer 1

[Sruthi Yenugula]

Hi Matthew,

Use this work around for now to get started with Android Support Package. Attached the Androidpatchfor18b_name.zip file. It contains 4 files. In MATLAB, go to path where you have placed that unzipped folder and then open the pluginfix.m file and click on Run button. Now try Hardware Setup again. If copy files, start MATLAB as administrator. Thanks for your patience. Let us know if you face any issues.

[Matthew Bigelow]

Hi Sruthi I can connect now but during the verification process at the build app stage i get this error:

"Build App Unexpected error : 'C:\Users\Matt' is not recognized as an internal or external command, operable program or batch file."

so it seems the issue is now happening at this stage as well. I am running matlab as administrator and ran the pluginfix.m before i started the hardware setup.

[Sruthi Yenugula]

Hi Matthew,

As quick fix, you can copy the whole sdk folder to a path which does not have space. Run hardware setup again with new sdk path. Please note this is for only R2018b.

For R2017b,

Your working directory i.e project directory has space. Please remove the space and try again.For 17b sdk path doesn't effect build as we use our own downloaded sdk. Don't use the patch providedfor 17b

Meanwhile we will work on space issue and provide you new patch

Answer 2

[Sruthi Yenugula]

For R2018a and R2018b,

If the device is not detectable even after installing USB drivers, the issue is with sdk path having space.

NDK Build tools doesn't allow space in the folder path, to overcome this issue install the sdk in a location which doesn't contain space and run the hardware setup again with new sdk location.(this issue will occur if your username has space)

Answer 3

[Sruthi Yenugula]

Hi Matthew Bigelow,

Make sure you have installed USB drivers for your Samsung s8 device.

[Matthew Bigelow]

Hi again Sruthi, I have managed to connect on the same computer using 2017b so I am assuming the correct drivers must be installed for that to happen. The issue is in 2018b