* Pavel Machek <pavel@xxxxxx> [180508 21:53]: > Hi! > > I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0 > > > AT+CNMI=? > < +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1) > < OK > ofonod[3070]: drivers/atmodem/sms.c:build_cnmi_string() > ofonod[3070]: drivers/atmodem/sms.c:construct_ack_pdu() > > AT+CNMI=1,2,2,1,0 > < OK > ofonod[3070]: src/network.c:__ofono_netreg_add_status_watch() 0x5bbbf0 > > ... unfortunately, with that configuration no messages are comming to > ofono and the other phone sees them as "delievery failed". > > I had some luck with unicsy_demo using AT+CNMI=1,2 with text mode (not > PDU) messages. That works well enough for me. > > Unfortunately, if I force ofono to pass "AT+CNMI=1,2", it does not > work well, either. > > Any ideas how to debug this / what to try? Well you can try to see what Android is doing for SMS with: # echo 0x7fffffff > /sys/module/ts27010mux/parameters/debug_level # dmesg | grep ts27010 | grep AT To send SMS, looks like Android RIL first does: 2 AT+CMGS=327 where 327 seems to be the size of the whatever encoded message. Then the next packet to dlci 2 contains the encoded message that is of size 327. When receiving, mdm6600 sends these on dlci 1: ~+WAKEUP ~+WAKEUP ~+WAKEUP Then mdm6600 sends this on dlci 9: ~+CMT=372 And that's probably the incoming SMS size. But I don't see anything for what actually reads the incoming SMS. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
