SayEZB only works on Android. On ios it comes out of its speaker.

Not all features of the PC are supported on mobile due to limited hardware, processing capabilities and operating system features.

Also, please ensure you are using the latest ARC before requesting support. When ARC loads, it will flash a window informing you of an update. Your ARC is out dated. It's difficult for anyone on the forum to assist when outdated ARC is used.

DJ,

I do have an android device and SayEZB worked on earlier versions. I have a couple of projects where SayEZB worked great in mobile app on android and these same apps don't work with SayEZB after updating. If you could look into this it would be great ! Thanks again...Rick

Hi DJ,

ARC is updated and SayEZB still isn't working on my android mobile app. It used to work in earlier versions as you said it should. It looks like something has changed since the earlier versions. Any help on resolution of this problem is much appreciated. Again this worked in an earlier version. Thanks much DJ.....Rick

Hello DJ,

I updated the mobile app on my Samsung Galaxy S4 and S7. Say EZB works on the Galaxy S4 but still doesn't work on the Galaxy S7. Is there anything you can think of with the Galaxy S7 that would keep the SayEZB command from working? Thanks again. Also wondering if anyone else has this issue? Rick

Due to Android devices having inconsistent OS versions and features between manufacturers and models, EZ-Robot is unable to support all features across all Android devices.

Please update ARC to the latest release before requesting support.

Hello DJ,

My ARC and mobile app are updated. Has anyone else reported this issue with the samsung s7. It is a pretty popular samsung android phone. Is there any chance you can look into this? Thanks again ! Rick

Due to Android devices having inconsistent OS versions and features between manufacturers and models, EZ-Robot is unable to support all features across all Android devices.

EZ-Robot does not have every Android phone ever made. EZ-Robot does not have the phone you mentioned for development.

Rick, post your project and later tonight I'll try with it and one of my own. I have an S7 Edge, but also have a couple of other Android 6.0.1 devices (Nexus 7 2013, HTC One M8).

What carrier is your S7? T-Mobile and AT&T have started pushing Android 7. Have you upgraded yet? (I am on Verizon and still waiting, but the version could be relevant).

Alan

Hello Alan,

Thanks for your help. I do have T-Mobile and the version of software for my galaxy S7 is 6.0.1. Same as some of your phones. I have my project in the cloud but have not made it public. I will make it public within the hour so you can take a look at it. Thanks again for taking a look/see ! Rick

Hello Alan,

I made the project public in the cloud so you should be able to access it now. It works on my samsung galaxy s4. The software version is 4.4.4 on the s4. Thanks again for your help and looking forward to hearing what you find....Rick

I'll need to look at it tomorrow evening. Need to get to bed since I go to work early.

Alan

Alan,

Can you think of any settings on the s7 that could affect the SayEZB command, like security, etc.? I looked and couldn't find anything obvious....Rick

I have confirmed there is a bug with SayEZB() when running under Android 6.0.1

Your project, and one of my own that consisted simply of a single line script and a script button fails to work on both the Galaxy S7 edge and Google Nexus 7 (2013).

All of my devices are currently running Android 6.01. Verizon has not released Android 7 for the Galaxy S7 Edge yet, and the Nexus 7 will never get it. I have nothing running an older version to compare with.

Alan

Alan,

Thanks much for checking and verifying the results. You truly are a valued member of this forum ! I have a Samsung Galaxy S4 running version 4.4.4 and it does work with the SayEZB() command. I will use this phone with my projects for the time being and make sure I don't update the software. I let DJ know but they didn't have any S7 or S7 edge phones around to check. Let me know when and if you get new software for your phones and have a chance to check it out and I will do the same. Again thanks much ! Rick

Has the SayEZB problem been resolved for the mobile app? SayEZB does not work on any of my mobile devices. I find this very frustrating as I do not want to be locked into controlling my robots with Windows devices.

Unfortunately the feature that sayezb used for android has been discontinued in their api. It only worked in android and no longer does. Mobile is not a pc, as the os is designed for phoning, cameras, and games. The technologies that Synthiam has attempted to implement in mobile has been either discontinued or difficult to work with. Maintaining the free mobile app is very difficult for us and we try our best. Apologies if it can’t do more than you want, but as you know the way we work, we want to help everyone. Mobile is the weak point

Thought that might be the case. It's a pity the Mobile App has gone backwards with the audio. To not be able to get your robot to talk with it, is a major flaw.  I just hope if enough people comment on it, perhaps things will improve. And that's the purpose of any comment I make. Thanks. Oh I almost forgot, the doco for the Interface Builder still has sayEZB as being supported...  https://synthiam.com/Support/Skills/User-Interface/Interface-Builder?id=16063

I understand your concern -  sayezb() is still supported for android but only on "certain" android devices it will work. It's not that we don't want to support it - because if it was possible we'd do it. It's just not possible for all android devices because they've removed the functionality from the operating system itself (OR the specific device has it remvoed). We're not holding out on you. You know I'd have every feature that is asked, but its just absolutely impossible to implement on all android devices and impossible to predict what devices it will work on (which makes it more challenging). Some Android will, some wont - and it's impossible to know because there's sooooo many different android versions and hardware versions.

The code is still there - it just works if it's supported by the device but there's no way to know without trying