@aizac, yes, that definitely points to an issue while ofono is decoding the message with the MMS push notification. So we are really near to find the bug, I just need some more information to reproduce this locally. Could you do from a PC connected to your phone (with dev mode activated):
* send a MMS to the phone and wait a bit to make sure we have received the notification (you could grep for UNSOL_RESPONSE_NEW_SMS in ofono.txt from another terminal to know when that happens)
Press ctrl^C and either attach ofono.txt to the bug or send it to me privately if you have privacy concerns. Then you can reboot the phone to restore it to a good state.
You can also follow these steps using the terminal app if you prefer that (doing "adb shell" does not apply in that case).
Hopefully with this info I will be able to hunt down the bug and I will not annoy you with more log requests :-)
@aizac, yes, that definitely points to an issue while ofono is decoding the message with the MMS push notification. So we are really near to find the bug, I just need some more information to reproduce this locally. Could you do from a PC connected to your phone (with dev mode activated):
$ adb shell DEVICE= mtk OFONO_RIL_ HEX_TRACE= "" OFONO_RIL_TRACE="" ofonod -nd -P stktest, provision, sap,udev, dun,smart, hfp &> ofono.txt
$ sudo su
# stop ofono
# OFONO_RIL_
* send a MMS to the phone and wait a bit to make sure we have received the notification (you could grep for UNSOL_RESPONSE_ NEW_SMS in ofono.txt from another terminal to know when that happens)
Press ctrl^C and either attach ofono.txt to the bug or send it to me privately if you have privacy concerns. Then you can reboot the phone to restore it to a good state.
You can also follow these steps using the terminal app if you prefer that (doing "adb shell" does not apply in that case).
Hopefully with this info I will be able to hunt down the bug and I will not annoy you with more log requests :-)