Alljoyn Control-Panels Not Rendering in Dashboard 14.12 - raspberry-pi

I have Alljoyn Dashboard 14.12 on my Samsung Galaxy Note that I simply downloaded from the play store.
I've noticed that, while the dashboard is able to find and onboard Alljoyn devices, it does not render their control-panels.
I've found this to be true on both COTS devices (LIFX 1000 bulbs) as well as raw code that I've run on a Raspberry Pi 2B. Specifically, I can run the ACServer example and it shows up on the dashboard (just like the LIFX bulbs), but the control-panel does not render.
Is Alljoyn dashboard 14.12 not compatible with the most recent Alljoyn release?

Related

web ble connectivity with gatt_sensordata_app 2.0 firmware

I'm trying to interact with the gatt_sensordata_app firmware using the provided web ble and python client samples. Can anyone confirm that it is working with uptodate browsers and also using the >2.0 firmwares?
I'm using chrome 98.0.4758.109 on OSX 11.6.3. Also tried google chrome on Android without success.
I have been relying on working javascript code since a while for the default ble_std_services_ecgrr firmware ( 1.9 ). Only recently started working with gatt_sensordata_app and 2.0 firmwares in general.
I also tried to debug the failing gatt_sensordata_app index.html service lookup using parts of that "proven" code without success. Additionaly the newly installed default std_services_ecgrr firmware using 2.1.2 doesn't work anymore via web ble.
I uploaded Movesense-gatt_sensordata_app_w_bootloader.zip onto one device, Movesense-ble_std_services_ecgrr_module_w_bootloader.zip onto another and will try to verify my claims that the web ble ble_std_services_ecgrr 1.9 interaction works as soon as I can get hold of my third device.
Behaviour:
samples/gatt_sensordata_app/web_client/index.html after connecting:
Label: Device Movesense XY selected.
Table: Connection Status: false
No js output in console at all.
Further JS console debug:
Verified selectedDevice['Movesense XY'].gatt.connected == true after clicking "select device"
selectedDevice['Movesense XY'].gatt.getPrimaryService('34802252-7185-4d5d-b431-630e7050e8f0').then(service => {console.log('service', service)}).catch(error => {console.log('error', error)});
The promise never resolves, nor catches that error. For me it looks like it somehow remains stuck in gatt.getPrimaryService / gatt.getPrimaryServices call.
I also tried the provided python client gatt_sensordata_app/python_client/movesense_sensor_data.py on a raspberry pi ( Linux 5.10.17-v7l+ armv7l ) but without success:
concurrent.futures._base.TimeoutError
Task was destroyed but it is pending!
I also tried connecting to both movesense firmwares via nrf connect and that seems to work but I can't interact with gatt_sensordata_app

App Launch: The Huawei Lite Simulator supports only Lite projects

When trying to run my test app on a HVD emulator, I get the following error message:
App Launch: The Huawei Lite Simulator supports only Lite projects.
Meanwhile I've realized, that currently one can only use hardware or a remote emulator for such a project. But when trying to set this up, the Harmony OS Virtual Device Manager responds with 404:
Is there anything to do about it?
I haven't tried with DevEco Studio on Windows so far, but with Android Studio on Linux, which appears to be functioning now.
With HMS Toolkit version 1.0.5, it will ask for Huawei ID and then also lists devices in Düsseldorf or Ireland (where the one is a city and the other a country). However, there are currently only EMUI ROM available. It integrates better than before, but without an HarmonyOS 2.0 ROM, it still doesn't provide the expected environment.

Test Actions on Google app on Raspberry Pi running Google Assistant SDK

I created an Actions on Google app which I am currently testing. I was able to test it on my Pixel, but when I tried to launch the app on my Raspberry Pi running the Google Assistant SDK it responded by saying "(name of app) isn't supported on this device". Is there any way I can run the app on my Pi?
EDIT: Here is a picture of the surface capabilities.

Create Android Wear Emulator Without Google Play Services

I'm using Android Studio 2.3.3 and I need to test my app on an emulator without Google Play Services. I know that it was pretty easy to create one using the old device manager (as described in this question), but I can't figure out how to do it with the new one.
The SDK Manager tells me that the system images that I want/need (API level 25) are installed:
Android Wear Intel x86 Atom System Image
Google APIs Intel x86 Atom System Image
At the "Select a system image" step for my new virtual device, only images with the Google APIs are presented under the "Recommended" tab. I've checked "x86 Images" and "Other Images" but no options without Google Play Services are to be found anywhere. I've also looked through all the settings options available at the "Verify Configuration" step without finding anything useful.
Does anyone know how to do this, or is it perhaps in fact no longer possible?

Edge browser on raspberry pi?

Is it possible to get the Edge browser running on the raspberry pi 2?
I've seen that in some areas the edge browser greatly outperforms Chrome (dom manipulation/css transitions), and I am creating a public display "art project".
The Microsoft Edge browser app is not included on Windows 10 IoT core that runs on the Raspberry Pi 2. However the same web platform behind MS Edge is available on the RP 2 in UWP apps. If you have a website you can take advantage of it through a Hosted Web App or the WebView control.
The steps to deploy an app are listed here. Check out this blog that covers the entire process of deploying on the Pi 2 through VS 2015. You are able to do this through the free community version.
This video covers how to make a Hosted Web App. A fun project and demo app to deploy is here: https://github.com/MicrosoftEdge/JSBrowser. It's a tutorial JavaScript app browser built using the WebView control that is able to run on the Pi 2.