Error report: 2013-08-06 04:21:02
Status: Assigned
Report generated: VemsTune (Help menu/Error reporting by one-click)
Further to my last report http://vems.hu/vemstune/bugreports/reports.php?cmd=view&key=kH3GIJ
I have received a new Vems bluetooth adapter and dongle from the web shop.
Using the new bluetooth dongle, with the original Vems adapter, it still will not communicate with anything.
Changing to the new Vems adapter I now have wireless communication with the V3 and can run the BlueToothConfigSaver.exe application. bluetooth.cfg attached along with this report for the 'NEW' adapter. NOTE, this application will not work with the original adapter I am having communication poroblems with.
I suspect there is something wrong with the original adapter, what ever that may be. The original adapter does not have a 'Vems' name, and it does not have a sticker on the side like the new one does with it's name on it. It just does not work. I would like to return the faulty adapter for a full refund.
This is still not the end of it since I can still not achieve comunication with any android device in AIM or Triggerframe.
Aim
We heard a couple of cases where installation of otherwise working adapters on certain windows and android versions (among the great variety of kernel, firmware, hardware, whatever) was problematic.
Adding to that, in several cases the installation prevented the module from working or damaged it. (in one occasion the USB had negative supply that killed 2 modules before the installer realized the problem).
Please see http://shop.vems.hu/catalog/shipping.php and send return item according to
http://shop.vems.hu/catalog/repair-upgrade-p-103.html (marked as \"non-functional\").
To make the end-user experience (in this harsh environment of wild diversity of uncertain android hw,kernel,firmware and windows variaties) we improved the testing procedure of BT-RS232 modules eg. double-checking and also testing the supply (that we don\'t manufacture just purchase and are tested OK) so that. Luckily it works well for most users, and sorry to hear that it did not work for you for some reason. Although in most cases the exact combination of hw,kernel,firmware is impossible to reproduce - without also sending the android or notebook) we are attempting to apply any necessary workarounds so that it works even in unlucky corner cases.
regards,
Marcell