Smart Remote Boots up to a Blurred Screen

Sonnie wrote:

I'm having this same issue of the remote booting to a blurred screen. I don't think I have the remote communicating correctly with the server. It's fairly confusing. 

I've also tried starting a new project in myDesigner but nothing happens after naming a project. 

Any help is appreciated. I could not find a step by step guide on setting up the remote... maybe I missed it. I remember seeing some fields with username, remote name, project name... something like that, and I changed a couple of them, but maybe I shouldn't have. I can't get back to it because of the blurred screen, and I see no instructions anywhere on resetting the remote to default, which would be a very helpful feature.

Here are the documentation steps that it sounds like you have not seen.  The last link is where the current problem is, but you need to follow the instructions step by step.

allonis.com/support/documentation?view=category&id=412

allonis.com/support/documentation?view=a...server-configuration

allonis.com/support/documentation?view=a...rver-configuration-2

allonis.com/products/smartremote/smartremote-gettingstarted

 

I'm thinking this may be a bit more than I expected it to be. 

Assuming you are referring to this section:

If the project launches "to a white page", then that's likely because you don't have your myServer IP and the smartremote folder properly configured.  You can wipe all of these settings by clearing data/ cache in the smartremote.apk in the Android Desktop's Apps page.You might not be able to reach the AndroidOS desktop to clean data.  If this is the case, myServer Pi needs to have ADB access.  This can be done within myServer's AndroidTV app (add the SmartRemote IP to the list of Android devices - which adds ADB connection to it).  You can also from a terminal session, type: "adb connect 192.168.1.48:55055" (use your IP address). Then, in Chrome (on the myServer controller), go to "chrome://inspect"  You should see the SmartRemote listed in the list of ADB connected devices.   Click "inspect" link in the SmartRemote's Remote Target section.

I am, in fact, unable to open the AndroidOS (assuming you are referring to reaching it on the remote). So... where exactly do I go to access the myServer's AndroidTV app? Is this in the Dashboard? I'm not seeing anything labeled AndroidTV. 

 

Sonnie wrote:

I'm thinking this may be a bit more than I expected it to be. 

Assuming you are referring to this section:

If the project launches "to a white page", then that's likely because you don't have your myServer IP and the smartremote folder properly configured.  You can wipe all of these settings by clearing data/ cache in the smartremote.apk in the Android Desktop's Apps page.You might not be able to reach the AndroidOS desktop to clean data.  If this is the case, myServer Pi needs to have ADB access.  This can be done within myServer's AndroidTV app (add the SmartRemote IP to the list of Android devices - which adds ADB connection to it).  You can also from a terminal session, type: "adb connect 192.168.1.48:55055" (use your IP address). Then, in Chrome (on the myServer controller), go to "chrome://inspect"  You should see the SmartRemote listed in the list of ADB connected devices.   Click "inspect" link in the SmartRemote's Remote Target section.

I am, in fact, unable to open the AndroidOS (assuming you are referring to reaching it on the remote). So... where exactly do I go to access the myServer's AndroidTV app? Is this in the Dashboard? I'm not seeing anything labeled AndroidTV. 


 

Hi sonny,
You have not set up myServer yet.  Getting the SmartRemote online is one of the last steps.
You MUST follow the installation instructions line by line or you will not get this working and will have a ton of questions.
AndroidTV is a driver within myServer.

Sorry... not sure what you mean. I have installed myServer per the instructions, otherwise I would not see the Dashboard... or is there some other myServer that needs to be installed that I am missing?

1. You can (and should) change the computer name to whatever you want (keep it simple with no symbols) by clicking on the computer name field in Dashboard.  Hit the "Play" button to the field left after you edit the command with your wanted name.  System will reboot post updating.  This myServer function also updates the TeamViewer alias to the same as Computer name which helps Allonis manage Remote Assistance.  Changing the computer name via the Raspberry OS directly, doesn't update TeamViewer so use the SetHostName command in myServer instead.Download and install latest myServer.  Once done, you can update the Operating system by clicking on Dashboard's Utilities Tab / Linux OS updates.  Click on Check for Updates. If there are updates, you can update them by clicking Apply Updates.  You should then click on Utilities / Reboot Host for all updates to be applied. DONE
2. Once the system is back online, complete the Dashboard / Configuration / Owner information section.

Sonnie wrote:

Sorry... not sure what you mean. I have installed myServer per the instructions, otherwise I would not see the Dashboard... or is there some other myServer that needs to be installed that I am missing?

1. You can (and should) change the computer name to whatever you want (keep it simple with no symbols) by clicking on the computer name field in Dashboard.  Hit the "Play" button to the field left after you edit the command with your wanted name.  System will reboot post updating.  This myServer function also updates the TeamViewer alias to the same as Computer name which helps Allonis manage Remote Assistance.  Changing the computer name via the Raspberry OS directly, doesn't update TeamViewer so use the SetHostName command in myServer instead.Download and install latest myServer.  Once done, you can update the Operating system by clicking on Dashboard's Utilities Tab / Linux OS updates.  Click on Check for Updates. If there are updates, you can update them by clicking Apply Updates.  You should then click on Utilities / Reboot Host for all updates to be applied. DONE
2. Once the system is back online, complete the Dashboard / Configuration / Owner information section.

Did you configure users/ rooms add drivers/ configure drivers / add driver devices to rooms?

I'm still stuck... moved this to a new topic:  allonis.com/forum/raspberry-os-64bit/263...figuration-and-setup