I finished my R2 and when powered up all went well with no problems. All of what you can do in manual mode works with no problems.

I'll start by saying I'm using a Pixel 2 phone. I've tried connecting directly and actually get connected to R2's network via wifi, but the app will not detect R2D2, it just keeps searching?

I've even tried to connect using the local wifi on my 2.4 network and get as far as R2 scanning the code, but nothing ever happens there either? I'm having a hard time getting the blue light to flash rapidly. It's hit and miss if it flashes slow or fast? I was wondering if there could be a camera issue, but I've noticed him turn his front light blue, turn his head and look at me when I'm sitting on the floor by him?

I've gone through trying to get him to connect multiple times both ways, I uninstalled the app and reinstalled the app. The only thing I question are his back lights? Sometimes they will flash yellow/green if he is in patrol mode or just sitting there?

I've read the entire users manual over and over, I've searched here and found people that had the same problem, but no one has answered what the fix is? Any ideas, I'm highly frustrated!

EDIT: I have tried again several times for direct wifi and the app still just searches for R2 even though my phone says it's connected to R2's network. In the local wifi setup I did get R2's blue light to flash rapidly when I hold the image in front of his camera and he appears to scan the image but comes back with a red light and he does not connect? Is there a certain distance the image should be from him?

I'm pretty positive that his camera is working. While sitting in front of him his blue light will come on and his head turns to look at me. He will even follow my face if I move in front of him.

I've tried holding the code on the phone screen anywhere from 2 inches to a foot away, in different lighting conditions, and different angles. It appears that the sweet spot is about 4 inches from his camera where he will consistently scan it and flash the red light once or twice saying he can't connect? I'm assuming that's what it means?

I even dug out my older Moto X phone with Android 5.1 on it thinking maybe my Pixel 2 with Android 10 on it might be the problem. That wasn't the case, he does the exact same thing as the Pixel 2 when trying to connect direct of local.

I have discovered a few other interesting things. The yellow/green light flashing is supposed to mean he's in Voice Recognition Mode, which he is. I found out when the lights are flashing he responds to voice commands like "raise light saber", "move forward", "lower light saber, and who knows what else he will respond to? He will also just start playing the "Luke Hologram" for no reason. All of this is happening while he is just turned on and not connected to any network?

This really has me puzzled, it's as if he's not transmitting, but yet I'm able to connect to his network, but the app just keeps searching for R2. Except for not being able to connect, everything works. I checked all the plugs making sure they were all connected properly, and fully plugged in. I made sure not to touch the PCB while installing it and only had to touch it to install the camera ribbon cable.

Interesting development: While typing the above response I left my phone on the table next to R2 and he connected directly. I was able to use the app to control him and can verify that indeed the camera is working and not a bad picture either. I disconnected and tried again to connect and the app is now searching again. He connected directly again and I found out that now if you close the app and reopen it he will connect immediately. All this is using my Moto X, I haven't tried my Pixel 2 yet, that's next. I'm going to try the local network and see if that started working?

I'm leaning towards a possible bad PCB from issue 99 as the problem?

Hi there Mark!

I just got through trying the Pixel 2 and had no luck connecting either way with it again. Using the Moto X you could clearly see from his video on my screen he'd be able to read the code for local network but still flashes the red light once or twice. After trying to connect him to my local network he's now being stubborn again and doesn't want to connect direct on the Moto X? Weird?

I'll give CS a call, but I'm still going to keep trying in the meantime.

Thanks, Charlie

EDIT: Just got off the phone with CS, they're sending me issue 99 with the PCB.

Interesting development:

1.Using a Galaxy S7 with Android 8, R2 can connect with both direct and local network wifi, but it keeps losing the signal and reconnecting in local network wifi. R2 did read the code from the Galaxy 7. which made him learn the network. He learned it really quick too!

2.The Motorola Moto X with Android 5.1 will connect occasionally using direct, and since he has already learned the password code, he will connect with the local wifi, but also keeps losing the signal and reconnecting.

3.I cannot get R2 to connect locally or direct using a Pixel 2 with Android 10 even after he has learned the local network wifi connection.

I tried walking away from R2 to see how strong of a signal he has and it drops off to almost nothing at 25-30 feet away. He has a very strong signal if you hold your phone about a foot away from him, but he'll still lose connection. When I was installing the PCB, one of the things I looked at was his antenna connection which appeared to be fully connected.

I'm thinking there are issues with the app that also need to be addressed. Android 10 was just released about 6 weeks ago or so and I'm wondering if that could also be an issue.

Either way, I'm hoping that a new PCB will correct the issue of connecting and him losing connection?

Hope it works out too. Have a great holiday and come back to it all refreshed. :)

You should be able to just connect the battery pack up again, just don’t take the batteries out the pack.

I got around to replacing the PCB and it works, some what?

I'm able to connect with "direct" using the Motorola Moto X, but not the Pixel 2, which is the way it was before. So, NO change

For "local wifi", there's where the "NEW" problem comes about? Now when you press the connection button on R2 to local the green light flashes fast and won't turn solid? According to the reference chart this is supposed to mean: "In Local Wi-Fi Mode but no router connected"

The one that I replaced would go into local with a solid green light without an issue when I changed connections, but it kept dropping the connection. No, it's not my network.

Everything on R2 works as it's supposed to, except this connection problem. what do I do now?

UPDATE: I got the green light to come on solid. I was doing something stupid and forgot to push the pairing button. I got to try my wife's Galaxy S7 and R2 works perfectly. He will connect direct and local without a problem. I'm still not able to connect either way using my Pixel 2. The Moto X will connect direct, but not locally. Everything is just as it was before, but at least the dropping of signal has stopped using the Galaxy S7.

I'm beginning to think the app or phone compatibility needs to be looked into. For me, it would be nice if my Pixel 2 with Android 10 worked seeing that it's my main phone. It's a good thing my old Moto X works with him at least connecting directly.

Any suggestions?????????

There are some Android devices that won’t work, such as the Amazon fire/Kindle. Although these have the basis of an Android OS, they use their own version of it. I’m assuming the devices you are using are probably the same.

Mark

I agree with you Charlie Dude. I have the Galaxy S5, so will see how that goes when the time comes!