Ai2 Companion 2.16 Running using the emulator or USB, waiting to get blocks...

[tech...@blsyw.org]

After updating from 2.12, this is all Companion shows. I have reinstalled using the apk and from Play store to no avail. I have also restarted computer and tablets. I have tested the port and Chrome is able to bring up the webpage. Any hep would be appreciated.

[Enis]

Here is a group of things to check:

Most of the emulator connection problems we have seen are a result of not having the most current version of the App Inventor setup software, or that software having been incompletely installed.

Still, there can be many other issues that could cause the connection to the emulator to fail.  Please read and follow the document below on connection issues:

Click here for Emulator Setup and Trouble Shooting Instructions

If you still cannot get the emulator running after following that document, please post in the forum and we'll try to help you out.

[tech...@blsyw.org]

I installed Ai2 Companion on a fresh install of Android on a tablet and I immediately am presented with the message "Running using the emulator or USB, waiting to get blocks..." when I open Ai2 Companion.  This was not happening when I was previously using 2.12 on a similar tablet.

[Enis]

First, verify the version of the companion you're using please.

If you run the companion on a device, first, you should see a screen similar to the one below:

If you connect from AI's menu "Emulator,"  you will NOT see this.  You will see a gray window that says it's waiting for the blocks.  This is because the UI started the companion and it's waiting to receive the blocks from the block editor.

[Tech Class]

That screen does not appear.  It loads onto the gray window that says waiting for blocks even though it has never been connected to a computer.

On Fri, Mar 14, 2014 at 4:13 PM, Enis <shadow...@gmail.com> wrote:

First, verify the version of the companion you're using please.

If you run the companion on a device, first, you should see a screen similar to the one below:

If you connect from AI's menu "Emulator,"  you will NOT see this.  You will see a gray window that says it's waiting for the blocks.  This is because the UI started the companion and it's waiting to receive the blocks from the block editor.

On Friday, March 14, 2014 3:18:24 PM UTC-4, tech...@blsyw.org wrote:

[Enis]

If it's waiting for the blocks, you should see a screen like the one below.  Do you see this?  If so, what version does it say you're running?

 

[Tech Class]

That is the screen that shows up immediately after install.  I am using the current version, version 2.16ai2zx1.

On Wed, Mar 26, 2014 at 12:17 AM, Enis <shadow...@gmail.com> wrote:

If it's waiting for the blocks, you should see a screen like the one below.  Do you see this?  If so, what version does it say you're running?

[zza...@blsyw.org]

This is a fresh install on a tablet that has never been used for App Inventor before and it is showing that screen.

[Enis]

That IS the correct screen to see... And that's the correct version.

What's happening?  It should be waiting to get the blocks... this is normal operation.  Does it ever get past that screen?

[Tech Class]

It boots to the screen where its says "Running using the emulator or USB, waiting to get blocks..." and then never gets past it even on a new install. It never offers a screen where I can connect.  I have tried installing from Google Play, from the App Inventor website and sideloading the app.  I have also reset the tablet to factory to ensure that it wasn't a software conflict.

[Enis]

Sorry, but I'm confused... You say it "boots" to that screen.  What exactly do you mean by that?

The screen you see should be invoked by the User Interface which you click on Connect, Emulator, or when you connect via the Companion through the code or the QR scan.

Tell me the exact sequence you're going through to try to connect to your device.

[Tech Class]

The app always opens to that screen.  Even if I install it on a tablet that has never had AI2 Companion on it and has never been connected.  I never see the Connect screen. 

Sequence:

1. Install AI2 Companion

2. Click on shortcut

3. First screen I see is "Running using the emulator or USB, waiting to get blocks..."

This happens on tablets that worked fine before updating and tablets that have never had AI2 Companion on them including one I reset to factory to ensure it was clean.

[Enis]

Sorry, but I'm still confused.

Let's take this step by step....

1.  Are you able to run your app on the Emulator?  The sequence for this would be:

• Click on Connect in the User Interface, and choose Emulator.
• Does that run your app on the emulator?

2.  If you're trying to run your app on an external device, you have two choices... but the sequence is always the same:

• You start the Companion on your device.
• In the User Interface, choose Connect, then AI Companion.
• From there you have two choices... to enter the code manually, or scan the QR code shown on the screen with your device.  In either case, you have to choose whichever option you want to use on the companion.  If you want to scan, on the Companion on the device, choose "Scan QR Code" and hold it to the screen to scan the code that appeared after hitting the Connect/AI Companion link.  If you want to manually enter the code, you'll see it in the QR Scan screen that comes up on the computer, and you have to choose "Enter Code" on the Companion and type in the code.

Is this what's you're doing?

Tech Class wrote:

The app always opens to that screen.  Even if I install it on a tablet that has never had AI2 Companion on it and has never been connected.  I never see the Connect screen. 

[tech...@blsyw.org]

The Emulator works.  The problem is with connecting the tablets over WiFi.  The Ai2 Companion app on the tablets immediately shows the "Running using the emulator or USB, waiting to get blocks..." screen when it is opened.  It never shows the Connect screen.  This happens even with fresh installs on new tablets that have never been connected.

[Enis]

Are you manually opening up the Companion on the device/tablet?  When you start it from the shortcut on the device, it goes directly to the waiting screen, bypassing the startup screen?  Is it possible you're triggering that second screen by a double touch?  Are these reasonably fast tablets?

[tech...@blsyw.org]

In order to connect over WiFi, I have to open the app manually.  These tablets are dual core A9s so not fast but not slow either.  It goes directly to the waiting screen on every tablet(30 of them), every time so I am very certain that it is not a double touch.

[Enis]

OK, I'm going to forward this to one of the developers who actually created the companion and maybe he can shed some light on what's happening there..  Please be patient... hopefully we'll get answers this afternoon for you...

[tech...@blsyw.org]

Thank you very much.

[Enis]

We'll get it straightened out for you...

On Monday, March 31, 2014 12:59:57 PM UTC-4, tech...@blsyw.org wrote:

Thank you very much.

[jeffrey.schiller]

What model tablet are you using. Even better would be a capture of a "logcat" output from when you start the Companion. I suspect the problem is that the mechanism we use to determine if the Companion is running via the emulator is being fooled by the way your tables identify themselves.

If this is the case, I will need to fix the Companion to do a better job of recognizing your tablets. We are planning to release a new Companion near the end of the week.

If you need a solution sooner, and don't mind installing a special Companion on your tables, I can build a version just for you that won't get fooled...

-Jeff

[Tech Class]

How do I capture a "logcat" output?

My model is Rockchip rk30sdk.

[Tech Class]

I can wait.  My students are building apps that are due next Friday so I will ask them to use the emulator until after the update.

[Enis]

Thanks! The info you posted about the model number was enough for Jeff to figure it out!  When you say "next" Friday, you mean April 11th, correct?

BTW, Jeff is truly a magician when it comes to this stuff...

[Tech Class]

Correct.  Thank you both for the help.

[Enis]

That's why we're here ;)!  Thanks for sticking with this until we figured it out for you!

On Monday, March 31, 2014 1:59:25 PM UTC-4, Tech Class wrote:

Correct.  Thank you both for the help.