Motorola G2 phones - scan only finds one controller at a time

[FTC8668]

A team in our area bought the new Motorola G2 phones. But, something weird is happening when we try to scan to create a config file. If we have more than one controller plugged into the core power module, the scan will only find the LAST device plugged in. If we have only one controller plugged in, the single device is found no problem. I've tried uninstalling the app and reinstalling but no change. Resetting or power cycling the robot makes no difference. Changing the devices around to different ports or connecting them in different arrangements or orders makes no difference.

BTW - I know the problem is not the hardware/electronics as I have used the Modern Robotics Core device discovery software and everything checks out fine. Also, the scans work just fine on the ZTEs the team used last year. - scans will show multiple devices So, the problem appears to be on the Motorolas only.

Has anyone who used Motorolas seen this behavior or have any ideas what could be going on?

[dmssargent]

Are the phones up-to-date with their system firmware (Android OS)?

This sounds like a known problem with the early versions of Marshmallow; it should have been fixed a few months ago in an OTA patch.

[FTC8668]

The team with the issues described above has Motorolas with Lollipop.

But, now, we have another rookie team with a similar issue except their Motorolas are fully upgraded and updated to the latest version of Marshmallow. For this team, everything works just fine with our ZTE phones. However, when we hook up to the new Motorolas, only one controller at a time can be controlled.

I'm wondering if there is some setting in Motorola that we are overlooking. By the way, both teams' hardware and programs have been fully checked out using the Modern Robotics Core Device Discovery and the programs work just fine with our ZTEs. It's just when we use the Motorolas that we have issues.

[dmssargent]

I mixed up Marshmallow (API 23) and Lollipop (API 21-22).

Lollipop (5.0) has the issue, Lollipop (5.1) and Marshmallow (6) doesn't. This thread may be helpful: http://ftcforum.usfirst.org/showthre...to-G-to-KitKat. It is regarding the same issue you are describing.

What is the exact version of Android this is occurring on? (It should be something like "5.1") and can you also include the "System version" (that should be something like "25.11.26.sumia_boost.Boost.en.US sprint")

[FTC8668]

The first team has Lollipop 5.0.2. This was the phone set that would only acknowledge one controller at a time - whichever was the last controller we connected. Question: If this was a known issue with lollipop, how did the other FTC using lollipop this past season get around the problem?

The second team has Marshmallow 6.0. Wednesday, we unboxed the phones and updated everything before attempting to use it. This phone set will acknowledge all the controllers (although it can take multiple scans to find everything when configuring), but only one motor at a time on the controller will work. We know it's not a program or hardware issue as we switch to the ZTEs (everything else the same) and the system works just fine. Then, if we switch the phones back to the motorola, only one motor will work again.

[FTC8668]

Forgot to give the system version. On the phone with Android version 5.0.2, the system version is 22.46.4.titan_retuaws.retuaws.en.us.retus.

On the second phone set, I don't have the phones here at my house so I'll have to email the team to ask. Be back with you shortly....

[FTC8668]

The other coach was monitoring this thread, saw your question, and emailed me the answer.
android version 6.0, system version 24.41.34.titan_retuaws.retuaws.en.us retus
This is the phone set that will acknowledge all controllers but only 1 port/controller is functional.

[FTC8668]

Based on your earlier comment, I am updating the Lollipop phones now to 6.0.

[cev]

We have the same problem running Android 5.0.2. Trying an upgrade.

FTC 11096

[cev]

Problem was fixed by system update:
22.46.12-titan_retuaws.retuaws.en.us retus

[Tom Eng]

I mixed up Marshmallow (API 23) and Lollipop (API 21-22).

Lollipop (5.0) has the issue, Lollipop (5.1) and Marshmallow (6) doesn't. This thread may be helpful: http://ftcforum.usfirst.org/showthre...to-G-to-KitKat. It is regarding the same issue you are describing.

What is the exact version of Android this is occurring on? (It should be something like "5.1") and can you also include the "System version" (that should be something like "25.11.26.sumia_boost.Boost.en.US sprint")

dmssargent is correct - the issue was with Android lollipop. Updating the phones to Marshmallow should remedy this issue.