I am developing a C# Windows app with feet32 library that is suppossed to initiate phone calls on a cell phone (in my case SAMSUNG S8) through bluetooth by passing ATD command. I have spent days trying to make it work. Unfortunately, I keep getting CME error message code 4 (operation not supported). I have tried different Bluetooth services including HandsFree etc. No success. What could be the reason? I am new to Bluetooth or AT commands topics and I got lost a little bit.
Related
I tried to install Openauto on my Raspberry Pi 3b+ and everything seems to start normal. But when I connect my old Samsung Galaxy S5 (Android 6) with it, sometimes Android Auto starts to work for some seconds and the quits. Most of the time it states an error message with "Unable to open MTP device".
When I run mtp-detect from the shell this is the result:
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) # bus 1, dev 47
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
I tried the Crankshaft Image on the Raspberry where Android Auto works without any problems. So I guess there is a configuration problem with the android smartphone and the Raspberry.
Did anybody had a similar issue?
Thanks in advance!
The error you are getting is LIBUSB_ERROR_BUSY, in documents it states that this error code is received when the resource you are trying to access is busy. This usually happens if a program or driver has claimed the interface, meaning that 2 processes try to claim the same interface at the same time.
Try to check the processes currently running on your raspberry pi, maybe you opened multiple instances at the same time, or you are trying to use multiple programs that use the same interface.
I have a big problem and I have searched thoroughly and found nothing... I'm using Android things as a central device in a system with other devices connectected. We are using the UART pins of the Raspberry Pi 3 Model B to communicate with the other devices.
When I use the default image burned with the Android Things utility and install the app through LAN connection, the app starts but it doesn't respod to any UART commands (as if nothing was being received). Note that the same code works if we burn a custom image with that app. The Raspberry also shows an error saying "bluetooth has stopped" even though I am not using the bluetooth... No error is shown in the logcat console so I don't know what is it causing it... I have tried reburning the image several times, but it doesn't work.
I have a Samsung Galaxy Gio and want to connect it to an Arduino Leonardo. I use the Stackable Bluetooth Shield 2.1 from ITead Studio.
It works with a Windows PC (I can send and receive strings with PuTTY), but my phone doesn't even recognize it - the Bluetooth device list is empty.
The strange thing is that a Galaxy S recognizes the Arduino immediately. And my phone can see all other Bluetooth devices - except the Arduino.
Why can't my Gio recognize the board, when all other devices work?
Well, I finally found the problem!
Apparently the Galaxy Gio with Android v2.3.6 has some problems with "special" Bluetooth devices - like Arduino boards.
I installed CyanogenMod (I think it's Version 7.1 or 7.2) on the phone and after that it had no problems recognizing the board. That's because CyanogenMod contains many fixes for Bluetooth and other problems.
Now I'm using ITEAD BT Debugging Assistant to send and receive strings from/to my board.
I am trying to run this USB Serial Monitor app on HCL ME U1 tablet (ICS 4.0.3, Kernel 3.0.8). I am connecting the tablet with a serial device using a FTDI FT232RL (USB to RS232) cable. When i connect the FTDI cable to tablet, notification asking permission to connect the device pops up and when I open device, Toast saying connected also comes up. But when i write some data, the data is not send. The TX Led doesn't blink. So the data doesn't get past FT232 IC.
I have tried same app on android x86 using oracle VirtualBox. It works fine on it. No errors.
I have tried Slick USB 2 Serial terminal on both x86 & ME u1. It works on both.
Please share if anybody has any ideas what the problem might be.
Source code
This Question have become obsolete. FTDI and prolific have released their driver jars for android. They are working fine.
I tried to connect an Arduino Mega ADK using Demokit sources to several phones in vain.
I compiled and upload the Arduino sketch "Demokit.pde" with arduino 0022. It looks ok as the board sends "start" on its usb client port.
I compiled Demokit app under Eclipse using Google API 10 (for phones running Gingerbread) and Android API 15 (for ICS ones). Everything fine.
On the phone side, I tried these setups :
samsung i9000 running CM 7.1 and after pushing android.hardware.usb.accessory.xml and com.android.future.usb.accessory.jar
samsung i9000 running ICS
nexus S running ICS
And nothing happened. There's only a warning in the eclipse logcat :
W/PowerUI(654): unknown intent: Intent { act=android.intent.action.ACTION_POWER_CONNECTED flg=0x10000010 }
Nothing else. I wonder if the board can have a problem on its usb host...
If anybody has an idea?
Thanks
There are couple of places where things go wrong.
First to check the board, try running a simple blink program, to make sure that the board itself is working.
Next when you connect your to the board, does your phone starts to charge? This will show whether there are any issues with the phone-board connectivity.
Out of the 3 phones, I would suggest you to try with nexus S, with stock ROM, since CM (even after pushing the jars) has issues enabling ADK.
The problem came from the setup procedure in the Demokit.pde sketch. I used a bread board to run it but I didn't connect all components and the i2c joystick initialization needs the component to be connected otherwise the procedure goes into an infinite loop. So if you try to run Demokit.pde without the demokit board be sure to connect the right joystick, or comment its init procedure call.
The demokit example is actually rather complex for an initial test. I would suggest after running the blink program to make sure your Arduino Mega ADK is working to try a simpler first test.
There are a couple of good examples that are much simpler than demokit.
http://allaboutee.com/2011/12/31/arduino-adk-board-blink-an-led-with-your-phone-code-and-explanation/
http://digitalhacksblog.blogspot.com/2012/05/arduino-to-android-turning-led-on-and_29.html
Neither of these target an Arduino Mega ADK so some changes will be necessary but they should be a good place to start.