Re: [fpc-pascal] fpcjvm code for examination

2019-08-23 Thread Mgr. Janusz Chmiel
So I have found out my bug. Why WIFIlock did not work as expected. I have put wrong number. So The right lines are:   WifiManager := ANWWifiManager(getSystemService(ACContext.WIFI_SERVICE)); WifiManager.createWifiLock (3,'WIFI_MODE_FULL'); Wakelock number is correct. __

Re: [fpc-pascal] USB Human Interface Devices

2019-08-23 Thread Stefan V. Pantazi
Thanks for pushing on this. I think any pending timeout/transfer must be explicitly canceled before closing the USB device, so that the thread can end gracefully. The only way I see is to use something like libusb_handle_events_timeout_completed http://libusb.sourceforge.net/api-1.0/group__

[fpc-pascal] fpcjvm code for examination

2019-08-23 Thread Mgr. Janusz Chmiel
Because my Java knowledge are very very very weak my attempts to call new Android API functions consists of GOogle search engine which shows Me some code examples from various WEB pages. And after that, I do my best to adapt those samples so it would be compatible with FPCJVM Android target. I

Re: [fpc-pascal] USB Human Interface Devices

2019-08-23 Thread James Richters
Stefan , Do you get the following errors when you exit your program? Is there some way I should shut down the read thread so I don't get this error? I've been using a timeout of 0 libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still