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
Related
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.
Hellow
I tried to get device information from mobile build version with Unity framework.
Calling the CreateAVideoDeviceManager(), CreateAAudioRecordingDeviceManager(), CreateAAudioPlaybackDeviceManager() apis always results in false. So the device information cannot be displayed.
However, in the standalone version, it works normally.
Do you have any solution for the above issue?
VideoDeviceManager and AudioDeviceManager are designed for standalone desktop environment only. It is in the documentation.
I have 5000 devices enrolled with EMM using android management API and recently I am getting issues with multiple devices out of nowhere and getting and error prompt after scanning the QR code on re-enrollment. All of my enrolled devices are Samsung Tab with the older version of android(7-9) and the issue doesn't seem to be related to the android version. Also, The issue has been experienced for the device which was earlier enrolled and was working fine but recently has this issue, we tried re-enrolling it but it gives us the same following error prompt after QR scan.
Cannot create a work profile - The security policy prevents the
creation of a managed device because a custom os is or has been
installed on this device
For your kind information, there is no custom os installed on the device and the device is not rooted or bootloader is not unlocked. I have researched a lot over the internet but cannot find a solution to the problem I have tried following approaches but it doesn't seem to work in my case
To fix this, you will need to update the time on the device by either connecting to wifi or cellular data (insert SIM-card), or by manually changing it in the set-up screen. After this is done you will be able to provision the device.
Tried DPC Identifier method for enrollment, When prompted to sign in on fresh factory reset device, enter afw#setup, which downloads Android Device Policy. Scan a QR code or manually enter an enrollment token to provision the device.
None of the above seems to work for me, I have also seen that its an issue related to Samsung Knox version, so can anyone from Samsung or google help me debugging and solving this issue, will removing the Knox app from the device work in my case.
Eagerly awaiting for the response as most of my device has started getting affected with this issue, please let me know your thoughts and resolution on this.
Not sure if that's an option for you as you have multiple devices, but on my single device, manually downloading and installing "google apps device policy" resolved the issue.
Been a lurker for a while and posting for the first time
Work as IT helpdesk and found a fix for us (context below)
We use Azure, InTune and Samsung Knox
Needing to assign a Knox profile so an application installs and runs
How we fixed this
Unassigned Knox profile
Ran tablet normally, skipping setup of Google, Samsung account and security
Running Samsung updates until current (24th Feb 2021)
Reassign the Knox profile
Factory resetting through settings
run through the setup process
Error has stopped at this point
You can either use Wi-Fi or SIM Card Data for OS updates through Knox
I had the same problems and this is how i fixed it. I have Samsung Tablet Android 10 and need to set it up under Enterprise.
Straight out of the box, you expand the OS, set up Network connection and than type in the google gmail space: afw#mobicontrol. This Does Not install the custom OS. Once expanded the OS has all the bloated software in tact plus the Mobicontrol app. I kept getting an error 'Can't Create Work Profile because Custom OS is installed on this device'. I did a factory reset but did so by powering it off than using the Power Button and Up Arrow to force it to the Android Recovery Screen. There is a factory reset option to choose from. "This Does Not Work". It still keeps the bloated software in tact.
You need to expand the Android OS first than do a reset. Go to SETTINGS. than ABOUT. at bottom is a RESET option. Choose that. Choose Factory Reset. This will delete all those apps. It reboots. Now you can enter afw#mobicontrol at the google email screen and it will install the custom OS and works under Soti.
Reset From the SETTINGS and do a Factory Reset. Than type in AFW#MOBICONTOL and the custom OS will work.
I need to troubleshoot an issue happening in a webview running within my app. This issue only occurs on Android versions lower or equal to 4.3. My app requires an up to date version of Google Play services.
In order to troubleshoot my webview, I usually can run my app under the Android Emulator (with the latest version of Android), then connect to the web view via Chrome (using chrome://inspect) - the web view appears in Chrome and I'm able to browse the DOM and debug.
To run the app under 4.3, I've created (under AVD) a new device from an existing device definition,
then picked the target Google APIs (Google Inc.) - API Level 18. I've then installed my app, but when trying to run it, I get the error message "This app won't run unless you update Google Play services.". There's an "Update" button on the previous dialog, but nothing happen when clicking on it.
I then tried to debug my issue using Genymotion. I've created a device under 4.3, followed these instructions to flash my device with the latest Google Play services and installed my app. I can now run the app and reproduce the issue within this simulated environment.
The trick now is to be able to connect to the web view from my local Chrome browser. I've enabled remote debugging as described here. Now my device appears in Chrome, but the web view is not showing up in the inspector. Similarly, if I open a new tab under the native browser, it won't show up in the remote inspector. If I open a new tab under Android Chrome though, I can see it showing up under my remote Chrome inspector.
I can see two way moving forward and successfully accessing to the DOM of my webview:
Fixing the "Update" issue under the Android Emulator running 4.3
Or
Connecting to my web view from my Chrome inspector while running the app under Genymotion
Any idea on how to solve one of these two problems?
I have been using weinre for sometimes. it's a pretty good tool to debug webview for android 4.3 and lower. It provides almost same interface as chrome debugger.
All you need to do are:
Install weinre
sudo npm -g install weinre
Client side:
Insert the following code to your webpage <head> section.
Note: it's better to put it at end of <head> section, otherwise there will be some strange errors and debugger won't show up.
<script src="http://<your server ip here>:8081/target/target-script-min.js"></script>
Server side
weinre --boundHost -all- --httpPort 8081
Debugger
open the debugger tool from weinre from your desktop browser:
http://localhost:8081/client/
Finally,
select any target in Targets part and then start debugging.
Remote debugging web views only works on devices with android 4.4 and above.
have a look at this :
https://developer.chrome.com/devtools/docs/remote-debugging
I have created a web application using the Google Web Toolkit that is able to receive some data by a mobile client via Http Post. The transmission of the data works well and also the server / client communication using GWT RPC is no problem at all.
However, I need to debug the webserver when receiving data from the mobile device. As I am using Hibernate and MySQL within the web application I do not use the Google App Engine. So if I deploy the web application in local host mode it is only accessible on the localhost:8888.
Now, if I send data from the mobile phone, I have to send it to the locally assign IP address as the localhost of the mobile phone emulator is not the localhost of the computer, where the web application is running. To ensure that everything works, I tried to do some posts outside the emulator (on the machine the emulator is running on). This works, but how can I post from the emulator to my web application?
How can I get access to debug my system? I've already tried to deploy the final application to a tomcat server and use remote debugging, but that fails too.
Best regards,
Florian
Well if I understand your question correctly, the real problem isn't debugging the app on the servlet, the real problem that you're looking at is debugging from a mobile phone. When the mobile phone hits your local network (I'm guessing you're pointing at 192.168..?) you are accessing the compiled GWT code that does not communicate with the debugger.
Put another way, when you debug locally using a browser, you are actually not running compiled GWT code, but instrumented code that is executed with the GWT Debugging Plugin, that happens to work exactly like compiled GWT code. (mostly). So while your local version has "?gwt.codesvr=127.0.0.1:9997" or the like, your mobile phone version cannot do the same, and cannot thus communicate with the debugger.
The best that I've been able to do is to use logging extensively. If you're using an iOS device and change the settings are your safari, it can output logs for you from mobile safari. Also, if you're using the Android debugger with a WebView app, you can attach a listener for log messages and then ferry them on to the ADB and view those in Eclipse. Definitely not as good as a debugger, but that's the best I've come up with so far, and if anyone has a better solution I would love to know it :)
Hope that helps!