Hello Brian,

I think it's amazing enough that Galaxy S2 can be used, even if only from 
its standard cable. These smartphones don't usually support modem 
operations. Maybe androids are different, don't know, I haven't yet joined 
the Android revolution. I am afraid I don't have a solid answer for the 
bluetooth. Maybe Androids do not support the usb serial profile...

I am gonna be honest here: I originally thought that you are completely 
crazy to use such an advanced phone for sms messaging as well as bother 
with bluetooth connections. Hell, there are some $20 usb sticks that can be 
used for this.

Then I saw your web/project site.
What a *great idea*! I really hope your project takes off!


On Tuesday, May 29, 2012 6:11:09 PM UTC+3, Brian O Carroll wrote:
>
> Thanks Gaurav, 
>
> After more testing, I've also managed to use SMSlib with a USB cable 
> (also standard usb drivers that come with Kies), but I still can't 
> find any way to connect to SGS2 with bluetooth. There is no specific 
> Samsung driver for Windows 7 bluetooth (that I can find - Kies even 
> has a message when you try to connect to your phone via bluetooth to 
> say that it doesn't support bluetooth connections to Android phones 
> which is pretty shocking!). You can use a generic windows "standard 
> serial over bluetooth link" as the driver for the bluetooth but it 
> SMSlib service can't connect using the serial port (simple file 
> transfer is about the only thing it can do via bluetooth). I don't 
> think there's going to be a solution but if anyone comes up with one, 
> please post it here. 
>
> By the way, I'm working on a computer program to allow people with 
> physical disabilities to use SMS, email, speech generation using a 
> modified tablet computer. http://www.aacireland.com/ 
>
> Thanks again, 
> Brian 
>
> On May 29, 1:51 pm, Gaurav Malhotra <[email protected]> wrote: 
> > Brian, 
> > 
> > I am using windows 7 but i am connecting to my SGSII using the 
> > datacable. I havent tried the bluetooth though. I would try to connect 
> > using bluetooth and see if i can use smslib 
> > 
> > When i installed the Samsung Kies software , it also installed the 
> > Samsung USB driver for mobile phones. maybe the kies package also has 
> > some drivers for bluetooth. 
> > 
> > I will post back after i try the bluetooth route. 
> > 
> > Thanks 
> > Gaurav 
> > 
> > On Mon, May 28, 2012 at 8:24 PM, Brian O Carroll <[email protected]> 
> wrote: 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > Hello Guarav, 
> > 
> > > Can you tell me: 
> > > 1. Are you using Windows 7? 
> > > 2 If so, how did you connect your SGSII via bluetooth. 
> > 
> > > I know it sounds like a stupid question but a lot of people (including 
> > > myself) seem to have trouble with SGSII bluetooth setup on Windows 7. 
> > > I have SMSlib working with an old Nokia phone but can't get it working 
> > > with the I9100. It seems to be missing drivers required to communicate 
> > > using bluetooth and from Googling it, those drivers don't seem to be 
> > > available for Windows 7. 
> > 
> > > Thanks, 
> > > Brian, Dublin 
> > 
> > > On May 10, 12:14 pm, Gaurav <[email protected]> wrote: 
> > >> Hi , You could replace the below line in the example to connect to 
> agalaxy 
> > >> s2. 
> > 
> > >> SerialModemGateway gateway = new SerialModemGateway("modem.com7", 
> "COM7", 
> > >> 230400, "Samsung", "I9100"); 
> > 
> > >> I was able to run all examples with the above change. Need to add 
> I9100 to 
> > >> the list of compatible phones. 
> > 
> > >> On Thursday, February 23, 2012 7:58:40 PM UTC+5:30, Greg wrote: 
> > 
> > >> > Hello everyone, 
> > 
> > >> > We actually have some problems to read the messages sent on our 
> > >> > gateway (a SamsungGalaxyS2). The issue is that the device doesn't 
> > >> > appear to respond when we run the ReadMessages class (found in the 
> > >> > examples in the documentation, modified for our gateway of course). 
> > >> > Here is the debug log after we run it : 
> > 
> > >> > 52108  2012-02-23 15:13:39,610 [Thread-3] DEBUG 
> > >> > org.smslib.modem.AModemDriver  - GTW: my modem: Buffer contents on 
> > >> > timeout: 
> > >> > 52108  2012-02-23 15:13:39,610 [KeepAlive [my modem]] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52108  2012-02-23 15:13:39,610 [CNMIEmulatorProcessor [my modem]] 
> > >> > DEBUG org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52108  2012-02-23 15:13:39,610 [SMSLib-AsyncNotifier : my modem] 
> DEBUG 
> > >> > org.smslib.modem.AModemDriver$AsyncNotifier  - GTW: my modem: 
> > >> > AsyncNotifier thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [SMSLib-AsyncMessageProcessor : my 
> > >> > modem] DEBUG org.smslib.modem.AModemDriver$AsyncMessageProcessor  - 
> > >> > GTW: my modem: AsyncMessageProcessor thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [SMSlib-ModemReader-my modem] DEBUG 
> > >> > org.smslib.modem.AModemDriver$ModemReader  - GTW: my modem: 
> > >> > ModemReader thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [PortReader() [/dev/ttyS0]] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52112  2012-02-23 15:13:39,614 [Thread-3] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > >>> Gateway Status change for my modem, OLD: STOPPED -> NEW: 
> RESTART 
> > >> > 53030  2012-02-23 15:13:40,532 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53030  2012-02-23 15:13:40,532 [DelayQueueManager] DEBUG 
> > >> > org.smslib.queues.AbstractQueueManager$DelayQueueManager  - 
> > >> > DelayQueueManager end... 
> > >> > 53130  2012-02-23 15:13:40,632 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Running... 
> > >> > 53130  2012-02-23 15:13:40,632 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager running... 
> > >> > 53231  2012-02-23 15:13:40,733 [WatchDog] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Stopping gateway... 
> > >> > >>> Gateway Status change for my modem, OLD: RESTART -> NEW: 
> STOPPING 
> > >> > 53231  2012-02-23 15:13:40,733 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Gateway stopped. 
> > >> > 53331  2012-02-23 15:13:40,833 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Running... 
> > >> > 53332  2012-02-23 15:13:40,834 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager running... 
> > >> > >>> Gateway Status change for my modem, OLD: STOPPING -> NEW: 
> STOPPED 
> > >> > 53332  2012-02-23 15:13:40,834 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53432  2012-02-23 15:13:40,934 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > org.smslib.TimeoutException: No response from device.53433 
>  2012-02-23 
> > >> > 15:13:40,935 [main] INFO  org.smslib.modem.ModemGateway  - GTW: my 
> > >> > modem: Stopping gateway... 
> > >> > 53433  2012-02-23 15:13:40,935 [main] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > 53433  2012-02-23 15:13:40,935 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Gateway stopped. 
> > 
> > >> > A step by step debug showed that the function 
> > >> > Service.getInstance().startService(); never finish and thus a 
> timeout 
> > >> > error appears. 
> > >> > The weird thing is that the SendMessages class works great (we are 
> > >> > able to send messages with it by using the -Dsmslib.serial.polling 
> and 
> > >> > -Djava.library.path=[...] arguments as we run it) and the code to 
> > >> > connect the gateway seems to be the same as the one in the 
> > >> > ReadMessages. Plus, the CommTest finds our gateway (not for all 
> > >> > baudrates but we are using one of the baudrates that is working 
> with 
> > >> > CommTest)... 
> > 
> > >> > Does someone have an idea of what is the issue here ? We installed 
> the 
> > >> > RxTx library instead of the JavaComm one, can it be a problem ? 
> > 
> > >> > Thank you for your help. 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups "SMSLib Discussion Group" group. 
> > > To post to this group, send email to [email protected]. 
> > > To unsubscribe from this group, send email to 
> [email protected]. 
> > > For more options, visit this group athttp://
> groups.google.com/group/smslib?hl=en.


On Tuesday, May 29, 2012 6:11:09 PM UTC+3, Brian O Carroll wrote:
>
> Thanks Gaurav, 
>
> After more testing, I've also managed to use SMSlib with a USB cable 
> (also standard usb drivers that come with Kies), but I still can't 
> find any way to connect to SGS2 with bluetooth. There is no specific 
> Samsung driver for Windows 7 bluetooth (that I can find - Kies even 
> has a message when you try to connect to your phone via bluetooth to 
> say that it doesn't support bluetooth connections to Android phones 
> which is pretty shocking!). You can use a generic windows "standard 
> serial over bluetooth link" as the driver for the bluetooth but it 
> SMSlib service can't connect using the serial port (simple file 
> transfer is about the only thing it can do via bluetooth). I don't 
> think there's going to be a solution but if anyone comes up with one, 
> please post it here. 
>
> By the way, I'm working on a computer program to allow people with 
> physical disabilities to use SMS, email, speech generation using a 
> modified tablet computer. http://www.aacireland.com/ 
>
> Thanks again, 
> Brian 
>
> On May 29, 1:51 pm, Gaurav Malhotra <[email protected]> wrote: 
> > Brian, 
> > 
> > I am using windows 7 but i am connecting to my SGSII using the 
> > datacable. I havent tried the bluetooth though. I would try to connect 
> > using bluetooth and see if i can use smslib 
> > 
> > When i installed the Samsung Kies software , it also installed the 
> > Samsung USB driver for mobile phones. maybe the kies package also has 
> > some drivers for bluetooth. 
> > 
> > I will post back after i try the bluetooth route. 
> > 
> > Thanks 
> > Gaurav 
> > 
> > On Mon, May 28, 2012 at 8:24 PM, Brian O Carroll <[email protected]> 
> wrote: 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > Hello Guarav, 
> > 
> > > Can you tell me: 
> > > 1. Are you using Windows 7? 
> > > 2 If so, how did you connect your SGSII via bluetooth. 
> > 
> > > I know it sounds like a stupid question but a lot of people (including 
> > > myself) seem to have trouble with SGSII bluetooth setup on Windows 7. 
> > > I have SMSlib working with an old Nokia phone but can't get it working 
> > > with the I9100. It seems to be missing drivers required to communicate 
> > > using bluetooth and from Googling it, those drivers don't seem to be 
> > > available for Windows 7. 
> > 
> > > Thanks, 
> > > Brian, Dublin 
> > 
> > > On May 10, 12:14 pm, Gaurav <[email protected]> wrote: 
> > >> Hi , You could replace the below line in the example to connect to 
> agalaxy 
> > >> s2. 
> > 
> > >> SerialModemGateway gateway = new SerialModemGateway("modem.com7", 
> "COM7", 
> > >> 230400, "Samsung", "I9100"); 
> > 
> > >> I was able to run all examples with the above change. Need to add 
> I9100 to 
> > >> the list of compatible phones. 
> > 
> > >> On Thursday, February 23, 2012 7:58:40 PM UTC+5:30, Greg wrote: 
> > 
> > >> > Hello everyone, 
> > 
> > >> > We actually have some problems to read the messages sent on our 
> > >> > gateway (a SamsungGalaxyS2). The issue is that the device doesn't 
> > >> > appear to respond when we run the ReadMessages class (found in the 
> > >> > examples in the documentation, modified for our gateway of course). 
> > >> > Here is the debug log after we run it : 
> > 
> > >> > 52108  2012-02-23 15:13:39,610 [Thread-3] DEBUG 
> > >> > org.smslib.modem.AModemDriver  - GTW: my modem: Buffer contents on 
> > >> > timeout: 
> > >> > 52108  2012-02-23 15:13:39,610 [KeepAlive [my modem]] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52108  2012-02-23 15:13:39,610 [CNMIEmulatorProcessor [my modem]] 
> > >> > DEBUG org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52108  2012-02-23 15:13:39,610 [SMSLib-AsyncNotifier : my modem] 
> DEBUG 
> > >> > org.smslib.modem.AModemDriver$AsyncNotifier  - GTW: my modem: 
> > >> > AsyncNotifier thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [SMSLib-AsyncMessageProcessor : my 
> > >> > modem] DEBUG org.smslib.modem.AModemDriver$AsyncMessageProcessor  - 
> > >> > GTW: my modem: AsyncMessageProcessor thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [SMSlib-ModemReader-my modem] DEBUG 
> > >> > org.smslib.modem.AModemDriver$ModemReader  - GTW: my modem: 
> > >> > ModemReader thread ended. 
> > >> > 52109  2012-02-23 15:13:39,611 [PortReader() [/dev/ttyS0]] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 52112  2012-02-23 15:13:39,614 [Thread-3] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > >>> Gateway Status change for my modem, OLD: STOPPED -> NEW: 
> RESTART 
> > >> > 53030  2012-02-23 15:13:40,532 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53030  2012-02-23 15:13:40,532 [DelayQueueManager] DEBUG 
> > >> > org.smslib.queues.AbstractQueueManager$DelayQueueManager  - 
> > >> > DelayQueueManager end... 
> > >> > 53130  2012-02-23 15:13:40,632 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Running... 
> > >> > 53130  2012-02-23 15:13:40,632 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager running... 
> > >> > 53231  2012-02-23 15:13:40,733 [WatchDog] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Stopping gateway... 
> > >> > >>> Gateway Status change for my modem, OLD: RESTART -> NEW: 
> STOPPING 
> > >> > 53231  2012-02-23 15:13:40,733 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > 53231  2012-02-23 15:13:40,733 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Gateway stopped. 
> > >> > 53331  2012-02-23 15:13:40,833 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Running... 
> > >> > 53332  2012-02-23 15:13:40,834 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager running... 
> > >> > >>> Gateway Status change for my modem, OLD: STOPPING -> NEW: 
> STOPPED 
> > >> > 53332  2012-02-23 15:13:40,834 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.notify.NotifyQueueManager$NotificationQueueManager  - 
> > >> > NotifyQueueManager end... 
> > >> > 53432  2012-02-23 15:13:40,934 [NotifyQueueManager] DEBUG 
> > >> > org.smslib.threading.AServiceThread  - Stopped. 
> > >> > org.smslib.TimeoutException: No response from device.53433 
>  2012-02-23 
> > >> > 15:13:40,935 [main] INFO  org.smslib.modem.ModemGateway  - GTW: my 
> > >> > modem: Stopping gateway... 
> > >> > 53433  2012-02-23 15:13:40,935 [main] INFO 
> > >> > org.smslib.modem.SerialModemDriver  - GTW: my modem: Closing: /dev/ 
> > >> > ttyS0 @115200 
> > >> > 53433  2012-02-23 15:13:40,935 [main] INFO 
> > >> > org.smslib.modem.ModemGateway  - GTW: my modem: Gateway stopped. 
> > 
> > >> > A step by step debug showed that the function 
> > >> > Service.getInstance().startService(); never finish and thus a 
> timeout 
> > >> > error appears. 
> > >> > The weird thing is that the SendMessages class works great (we are 
> > >> > able to send messages with it by using the -Dsmslib.serial.polling 
> and 
> > >> > -Djava.library.path=[...] arguments as we run it) and the code to 
> > >> > connect the gateway seems to be the same as the one in the 
> > >> > ReadMessages. Plus, the CommTest finds our gateway (not for all 
> > >> > baudrates but we are using one of the baudrates that is working 
> with 
> > >> > CommTest)... 
> > 
> > >> > Does someone have an idea of what is the issue here ? We installed 
> the 
> > >> > RxTx library instead of the JavaComm one, can it be a problem ? 
> > 
> > >> > Thank you for your help. 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups "SMSLib Discussion Group" group. 
> > > To post to this group, send email to [email protected]. 
> > > To unsubscribe from this group, send email to 
> [email protected]. 
> > > For more options, visit this group athttp://
> groups.google.com/group/smslib?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"SMSLib Discussion Group" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/smslib/-/BUbg-8xKq_8J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/smslib?hl=en.

Reply via email to