I succesfully implemented the Code described here.
I do find my phone (Samsung Galaxy A51) or my portable radio transceiver (Bluetooth 4.1)
But somehow I can't seem to find my optical read-out head (Bluetooth 2.1). Is it because of the Bluetooth version? How do I fix this?
Related
I am working on a Xamarin Form Mobile App for handsets used for scanning barcodes and a lot more.
The barcode scanners currently implemented are working correctly for:
iOS device using a scan jacket
Zebra handset device (Android)
Now, there is a request to use new handset devices (Android) called ASCOM Myco 3 and I had no luck finding drivers or DLL files or documentation on how to get it to work on my Xamarin/C# App.
Does anyone have experience with that? All I need is to be able to scan a barcode.
Thanks
Android Management APIs are supposed to be "compatible with any device running Android 5.1 or above that has Google Play installed." I really want that to be true, but am having trouble with Android TVs. (Specifically, a NexBox A95x and a TX3mini I'm testing with.)
My stumbling point is how to enter the enrollment token into the device when provisioning it? I had no problem with a Samsung tablet. But, the Android TVs don't use the same startup wizard after hardware reset, so there doesn't seem to be an opportunity to trigger a QR reader, or manually enter the token. I've tried entering the enrollment token into Google Play app (in lieu of the email or phone number to log in), but no luck.
Any ideas or insight how to make this work? If anyone knows a definitive reason why this can't be made to work (e.g. Management APIs don't work on AOSP) that'd be helpful information too.
Clarification (Updated 26 Dec 2017)
Here's a minimal, complete, and verifiable example of the Google Management APIs. The Quickstart exercise from Google, themselves.
Problem: The Quickstart exercise doesn't seem to work with Android TV (tested on a NexBox A95x and a TX3mini). The blocker appears on this step: (Provision A Device). The Android TVs have their own setup wizards that do not accept an Android For Work enrollment token. (I have completed the Quickstart on a Samsung tablet without problem.)
Google's documentation says the Management APIs are "compatible with any device running Android 5.1 or above that has Google Play installed" so it seems these Android TVs should qualify.
Has anyone found a workaround to do complete the Management API Quickstart on an Android TV?
As far as I know the Android Management API doesn't supports Android-based OS's like Android TV, Android Wear, Android Auto or Android Things. It just supports standard Android for phones and tablets.
I want to work in HMI domain and have started learning it.
In first stage I want to develop Qt GUI based touchscreen application for ARM9 board. Can anyone please suggest how to go for it and any budget ARM9 Dev board with integrated touchscreen LCD for this purpose? I want to use opensource platform as much as possible.
I know I can do it with more ease on an ARM board which support some OS like (say) embedded linux or may be Rasberry Pi with java or Qt based GUI. But I do not want to use OS rather want to develop just a simple touch screen GUI application to (say) turn a LED on the ARM board (without running any OS).
My next step of learning will be using touch screen GUI, Rasberry Pi with raspbian, where I have already found numerous resources Online.
Thanks
It may be better to just get a low end tablet or why not even a phone, much cheaper than a dev board with additional touchscreen. Plus Android is open. It may be a good idea to get an Ubuntu touch compatible device. The Pi, while cheap, is also very underpowered. A cheap tablet or phone will be more applicable, especially since official Android support in Qt is looming on the horizon. So why spend more money on a lower spec'd device with very narrow application range? Not to mention the wide range of sensors you get with a market device - cameras, compass, gyroscope, GPS, accelerometer - those could come in handy in a HMI scenario. Last but not least, graphics drivers are usually better in production devices than prototype boards.
I was curious to know if someone had an experience of porting OpenCV to Nokia C5 series cell phones. Probably via Qt, is it possible to port OpenCV to Nokia, are there any know ports for OpenCV such as we have for Android and Apple iPhones.
Thanks for the guidance.
There is opencv-symbian, but it's last update is 2010-07-12.
Nokia provides an alternative to OpenCV for the Symbian platform, it's named NCV: Nokia Computer Vision library
The Nokia Research Center has released the Nokia Computer Vision Library (NCV). NCV builds on Symbian OS on S60 to provide additional imaging related functionality to developers for use in third party applications. The library includes motion sensing from the camera (for use in games), advanced image capture functions (algorithm constructions, panorama) and image post processing functions (morphing, image compositing).
I have to develop an application which requires Bluetooth and profile change functionality for Symbian phones. After spending sometime I found that following options:
Java: but java does not allow to change profile
Symbian C++: I read basics for Symbian C++ and created some basic stuffs. Symbian extended APIs provide simple APIs for Profile and Bluetooth (I haven't tested yet). But its required lot of efforts to grab these. Specially certificate singing problem. I want to test my application on different devices and wish to give my friends whom having different cellphones. But couldn't due to signing problem.
QT: I am still confused on this. Whether this platform capable to fulfill my requirement or not. Secondly which phone supports QT or not...
Honestly, I am bit frustrated while writing this. I am looking someone, experience in these matter, to guide me in this situation.
You can combine native C++ with Qt. Though you'll lose some of the cross-platform nature of Qt by mixing native C++ with it.
See the XQProfile example on Forum Nokia Wiki for mixing Qt and native Symbian C++ for profile changing.
Qt can be installed to practically all devices from S60 3rd Edition FP1 (S60 3.1) onwards. Newer device models ship with Qt preinstalled. Forum Nokia has device specifications that you can filter based on Qt availability.
QT (+ QML) is the language of choice going forward. I believe it is currently on the following phones: N8,C7,C6,E7. i version 4.6.1 with version 4.7 which has the QML support due shortly.
However if you need to target current and older devices then your only choice is Symbian C++.