For everyone interested: http://code.google.com/p/smslib/issues/detail?id=331
On Mar 11, 9:38 pm, Thanasis <[email protected]> wrote: > Thanks! > > Very interesting to see that this issue is PC oriented. Can't > understand why your mod works, but I will open an enhancement issue in > order to define an SMSLib switch (crash switch? LOL) which will > disable these commands. > > On Mar 11, 4:16 pm, Alex <[email protected]> wrote: > > > > > Hi Thanasis, > > > Sorry for being vague. I found the (Windows freezes completely, but > > keeps displaying) occurred consistently (every time) using > > SonyEricsson K800i on one particular PC. This phone was fine on > > another PC I tried it with. After removing the lines specified, the > > handset works consistently on the machine it previously crashed. > > > Alex > > > On Mar 11, 12:31 pm, Thanasis <[email protected]> wrote: > > > > Hi Alex, > > > > Can you please explain the "works in some cases" phrase? > > > Did you find that the problem persists with other modems or at "some" > > > times (i.e. the problem becomes more rare)? > > > > On Mar 11, 11:59 am, Alex <[email protected]> > > > wrote: > > > > > Hi Yogesh, > > > > > I've experienced similar problems to this, and I found a solution that > > > > works in some cases. In org.smslib.modem.SerialModemDriver, try > > > > removing the following lines: > > > > > getSerialPort().notifyOnOutputEmpty(true); > > > > getSerialPort().notifyOnBreakInterrupt(true); > > > > getSerialPort().notifyOnFramingError(true); > > > > getSerialPort().notifyOnOverrunError(true); > > > > getSerialPort().notifyOnParityError(true); > > > > > They should be located around line 70-80. -- You received this message because you are subscribed to the Google Groups "SMSLib User 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 at http://groups.google.com/group/smslib?hl=en.
