Can't recieve MMS about ubuntu-touch HOT 46 OPEN

I think I've tracked this down to somewhere in history-service. Running strace on it while sending a test MMS reveals that history-service is indeed receiving the message from telepathy-ofono:

[pid  2921] recvmsg(7, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1\250\1\0\0\246\1\0\0\356\0\0\0\1\1o\0i\0\0\0/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_2b312dc02f48316f1eaf805c6e0b24a2/MucChannel1\0\0\0\0\0\0\0\2\1s\0004\0\0\0org.freedesktop.Telepathy.Channel.Interface.Messages\0\0\0\0\3\1s\0\17\0\0\0MessageReceived\0\10\1g\0\6aa{sv}\0\0\0\0\0\7\1s\0\5\0\0\0:1.19\0\0\0\244\1\0\0\24\1\0\0\20\0\0\0message-received\0\1u\0\237\273\\]\0\0\0\0\16\0\0\0message-sender\0\1u\0\0\0\3\0\0\0\0\0\0\0\r\0\0\0message-token\0\1s\0\0\0\0?\0\0\0/org/ofono/mms/310260937569696/78d3c3d0040b5281b72741488090aef6\0\0\0\0\0\f\0\0\0message-type\0\1u\0\1\0\0\0\22\0\0\0pending-message-id\0\1u\0\0\0\22\0\0\0\7\0\0\0subject\0\1s\0\0\t\0\0\0NoSubject\0\0\0\17\0\0\0x-canonical-mms\0\1b\0\0\1\0\0\0\210\0\0\0\7\0\0\0content\0\2ay\0\t\0\0\0testagain\0\0\0\f\0\0\0content-type\0\1s\0\n\0\0\0text/plain\0\0\0\0\0\0\n\0\0\0identifier\0\1s\0\0\0\f\0\0\0<Attachment>\0\0\0\0\4\0\0\0size\0\1t\0\0\0\0\0\t\0\0\0\0\0\0\0", 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 680

However, that thread doesn't appear to show up in history.sqlite! Further digging needed to figure out why.

from ubuntu-touch.

Hi UniversalSuperBox,
I still cannot receive and send MMS to or from single person. There is a whole tread on ubports forum where i tried to debug this issue without luck. https://forums.ubports.com/topic/2532/cant-receive-pictures-through-mms/31. You can check there that there are several people affected by this issue. There is similar bug report [#276] so maybe indeed it would be good to do some clean up but definitely this issue with MMS from/to single person is not solved.

from ubuntu-touch.

@UniversalSuperBox If you know how to run ofono or/and messaging app in debug mode then it would be great if you could give us some hints how to do that. I can go back to debugging and provide additional information

from ubuntu-touch.

Fingers crossed, but my OPP just managed to receive an MMS!
@mariogrip I now have the intended Tele2/Comviq APN settings, so maybe this was also fixed in the stuff you did to fix #61 ? This is the first time in a long while that I have had two-way MMS working on an Ubuntu Touch device!

from ubuntu-touch.

I can send mms just fine now

from ubuntu-touch.

Fixed

from ubuntu-touch.

It seems we have to reopen this bug. I have my original Tele2 SIM in my OPO now, which I am trying out as a daily driver for the past few days. It turns out that sending mms doesn't work with the adviced apn settings from the operator (see above). Sending mms still works, though.

I have tried this on 15.04/devel r14 and r15.

from ubuntu-touch.

This bug is really bugging me! This afternoon I could actually receive a few mms from my girlfriends android phone, but earlier today mms from my daughter's iPhone failed to reach me. Is there anything I can provide to help find the problem here?

from ubuntu-touch.

Doing a forward from an android phone seems to work, but not sharing a picture from e.g. gallery. I have tried with and without text together with the picture, but no difference. Also tried 3 new mms from an iPhone, of which one a forwarded message - nothing. This is really weird.

from ubuntu-touch.

@tomoqv could you send me the log of /system/bin/logcat -b radio? I just pushed a new update that fixed adb so you can use adb shell to get this log

from ubuntu-touch.

you might need to run it with sudo /system/bin/logcat -b radio

from ubuntu-touch.

I am running that command right now, but it seems to be never ending. I tried to log the output to a file as well, which I have attached. I had to Ctrl-C out of the process though, so you need to tell me if it is incomplete.
logfile_mms.txt

from ubuntu-touch.

This is normal, logcat is logging as long as you let do it ;)

from ubuntu-touch.

The MMS functionality on Ubuntu Touch seems to depend on telecom operator. I recently switched from Tele2 (Sweden) to Telenor and now MMS works on my OPO.

from ubuntu-touch.

I can confirm this bug on my OPO. I' managed to send and receive few MMS messages after reapplying APN configuration. Unfortunately after phone restart MMS has stopped to work and i had to reapply them again. Currently after system update to 15.04(r14) even this trick doesn't work. On my second ROM LinageOS MMS are working fine so APN configuration is correct.

from ubuntu-touch.

Also related to #276 probably.

from ubuntu-touch.

I already sent log output of unsuccessful MMS in #276 but that ticket is not even assigned. That's why i decided to paste it also here. I'm running 16.04(2018-W28) on OPO.

Published using Logviewer for Ubuntu Touch
From file /home/phablet/.cache/upstart/application-legacy-messaging-app-.log:
file:///usr/share/messaging-app//Messages.qml:459: TypeError: Cannot call method 'sendMessage' of null
file:///usr/share/messaging-app//Messages.qml:459: TypeError: Cannot call method 'sendMessage' of null
file:///usr/share/messaging-app//Messages.qml:459: TypeError: Cannot call method 'sendMessage' of null
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QList, ) to property: "attachments"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QVariantMap, QMap()) to property: "chatRoomInfo"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 1) to property: "count"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-07-16") to property: "date"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-07-16T07:37:53Z-1") to property: "eventId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "informationType"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-07-16T07:37:53Z-1") to property: "lastEventId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QDateTime, QDateTime(2018-07-16 09:37:53.000 CEST Qt::TimeSpec(LocalTime))) to property: "lastEventTimestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "") to property: "message"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 3) to property: "messageStatus"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 1) to property: "messageType"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(bool, false) to property: "newEvent"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-07-16T09:37:53.766") to property: "readTimestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "self") to property: "senderId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "") to property: "subject"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QDateTime, QDateTime(2018-07-16 09:37:53.000 CEST Qt::TimeSpec(LocalTime))) to property: "timestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "type"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "unreadCount"
file:///usr/share/messaging-app//Messages.qml:74: TypeError: Cannot read property 'length' of null
file:///usr/share/messaging-app//Messages.qml:1561: TypeError: Cannot read property 'length' of null
file:///usr/share/messaging-app//ComposeBar.qml:186:5: QML Row: Binding loop detected for property "width"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
"ofono/ofono/account0" "2018-07-16T07:39:01Z-2" "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_e6222efab56e49d59e5181acc97e2dc4/TextChannel0" QMap(("chatType", QVariant(int, 1))("participantIds", QVariant(QStringList, ("xxxxxxxxx")))("threadId", QVariant(QString, "xxxxxxxxx"))("x-canonical-tmp-files", QVariant(bool, true)))
adding channel "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_e6222efab56e49d59e5181acc97e2dc4/TextChannel0"
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//Messages.qml:1185: TypeError: Cannot read property 'accountId' of null
file:///usr/share/messaging-app//Messages.qml:1458: TypeError: Cannot read property 'type' of null
file:///usr/share/messaging-app//ComposeBar.qml:512: TypeError: Cannot read property 'accountId' of null
file:///usr/share/messaging-app//Messages.qml:729: TypeError: Cannot read property 'active' of null
file:///usr/share/messaging-app//Messages.qml:736: TypeError: Cannot read property 'active' of null
file:///usr/share/messaging-app//Messages.qml:119: TypeError: Cannot read property 'title' of null
file:///usr/share/messaging-app//Messages.qml:60: TypeError: Cannot read property 'active' of null
file:///usr/share/messaging-app//Messages.qml:52: TypeError: Cannot read property 'active' of null
file:///usr/share/messaging-app//Messages.qml:44: TypeError: Cannot read property 'active' of null
[PERFORMANCE]: Last frame took 33 ms to render.
[PERFORMANCE]: Last frame took 46 ms to render.
[PERFORMANCE]: Last frame took 54 ms to render.
QObject::startTimer: Timers cannot be started from another thread

from ubuntu-touch.

Hi,
Unfortunately on 16.04 OTA-4 (2018-W35) issue is still nut solved but the output log looks different.
In first lines of the log file you can find info regarding AppArmor policy issue.
Besides that one library is missing:
library "/vendor/lib/egl/libGLESv2S3D_adreno.so" not found

Published using Logviewer for Ubuntu Touch
From file /home/phablet/.cache/upstart/application-legacy-messaging-app-.log:
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.204" (uid=32011 pid=11801 comm="messaging-app ") interface="com.canonical.libertine.Service.Operations" member="list" error name="(unset)" requested_reply="0" destination="com.canonical.libertine.Service" (uid=32011 pid=3694 comm="/usr/bin/python3 /usr/bin/libertined ")"
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.204" (uid=32011 pid=11801 comm="messaging-app ") interface="com.canonical.libertine.Service.OperationsMonitor" member="running" error name="(unset)" requested_reply="0" destination="com.canonical.libertine.Service" (uid=32011 pid=3694 comm="/usr/bin/python3 /usr/bin/libertined ")"
lastError - no arguments?
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.204" (uid=32011 pid=11801 comm="messaging-app ") interface="com.canonical.libertine.Service.OperationsMonitor" member="last_error" error name="(unset)" requested_reply="0" destination="com.canonical.libertine.Service" (uid=32011 pid=3694 comm="/usr/bin/python3 /usr/bin/libertined ")"
lastError - no arguments?
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.204" (uid=32011 pid=11801 comm="messaging-app ") interface="com.canonical.libertine.Service.OperationsMonitor" member="result" error name="(unset)" requested_reply="0" destination="com.canonical.libertine.Service" (uid=32011 pid=3694 comm="/usr/bin/python3 /usr/bin/libertined ")"
lastError - no arguments?
library "/vendor/lib/egl/libGLESv2S3D_adreno.so" not found
file:///usr/share/messaging-app//MainPage.qml:413: TypeError: Cannot call method 'forceActiveFocus' of null
QQmlExpression: Expression file:///usr/share/messaging-app//FavoriteChannels.qml:89:25 depends on non-NOTIFYable properties:
QQmlSettings_QML_2::category
QQmlExpression: Expression file:///usr/share/messaging-app//FavoriteChannels.qml:89:25 depends on non-NOTIFYable properties:
QQmlSettings_QML_2::category
[PERFORMANCE]: Last frame took 32 ms to render.
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QList, ) to property: "attachments"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QVariantMap, QMap()) to property: "chatRoomInfo"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 110) to property: "count"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-08-22") to property: "date"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-08-22T20:55:57+0200-1") to property: "eventId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QList, ) to property: "groupedThreads"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "informationType"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-08-22T20:55:57+0200-1") to property: "lastEventId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QDateTime, QDateTime(2018-08-22 20:55:59.000 CEST Qt::TimeSpec(LocalTime))) to property: "lastEventTimestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "last message") to property: "message"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "messageStatus"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "messageType"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(bool, true) to property: "newEvent"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "2018-08-22T20:55:59.405") to property: "readTimestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "xxxxxxxx") to property: "senderId"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QString, "") to property: "subject"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(QDateTime, QDateTime(2018-08-22 20:55:59.000 CEST Qt::TimeSpec(LocalTime))) to property: "timestamp"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 0) to property: "type"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:708:9: QML PageWrapper: Could not assign value: QVariant(int, 1) to property: "unreadCount"
file:///usr/share/messaging-app//Messages.qml:74: TypeError: Cannot read property 'length' of null
file:///usr/share/messaging-app//Messages.qml:1561: TypeError: Cannot read property 'length' of null
file:///usr/share/messaging-app//ComposeBar.qml:186:5: QML Row: Binding loop detected for property "width"
[PERFORMANCE]: Last frame took 54 ms to render.
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//ComposeBar.qml:574:5: QML AttachmentPanel: Binding loop detected for property "height"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Content/ContentPeerPicker13.qml:194: TypeError: Cannot read property 'peers' of null
[PERFORMANCE]: Last frame took 34 ms to render.
QObject::startTimer: Timers cannot be started from another thread
QObject::killTimer: Timers cannot be stopped from another thread
QObject::startTimer: Timers cannot be started from another thread
QObject::killTimer: Timers cannot be stopped from another thread
qml: 2
"ofono/ofono/account0" "2018-09-02T06:27:59Z-1" "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_48c2817caa65ae883d4a0421c9142b4f/TextChannel1" QMap(("chatType", QVariant(int, 1))("participantIds", QVariant(QStringList, ("xxxxxxx")))("threadId", QVariant(QString, "xxxxxxxxx")))
adding channel "/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_48c2817caa65ae883d4a0421c9142b4f/TextChannel1"
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//RegularMessageDelegate.qml:43:5: QML Loader: Binding loop detected for property "active"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//MessageDelegate.qml:48: TypeError: Cannot read property 'lastItem' of null
file:///usr/share/messaging-app//Messages.qml:642:13: QML Action: Invalid shortcut:
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageDelegate.qml:48: TypeError: Cannot read property 'lastItem' of null
file:///usr/share/messaging-app//MessageDelegate.qml:48: TypeError: Cannot read property 'lastItem' of null
file:///usr/share/messaging-app//MessageDelegate.qml:48: TypeError: Cannot read property 'lastItem' of null
QObject::startTimer: Timers cannot be started from another thread
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
QObject::startTimer: Timers cannot be started from another thread
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//AttachmentsDelegate.qml:23:1: QML AttachmentsDelegate: Binding loop detected for property "attachments"
file:///usr/share/messaging-app//Messages.qml:118:32: Unable to assign [undefined] to QString
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"
file:///usr/share/messaging-app//MessageBubble.qml:137:5: QML Label: Binding loop detected for property "width"

from ubuntu-touch.

@mariogrip i noticed that you asked at the begining o this ticket to run command:
sudo /system/bin/logcat -b radio.

Below you can find output of this command after try to send MMS

/RILQ ( 26): (0/26): RIL[0][main] qcril_data_request_setup_data_call: qcril_data_apn_based_profile_look_up failed
D/RILC ( 26): RequestComplete, RIL_SOCKET_1
E/RILC ( 26): Send Response to RIL_SOCKET_1
E/RILQ ( 26): (0/26): RIL[0][main] qcril_data_request_setup_data_call: qcril_data_apn_based_profile_look_up failed
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: invalid dsi_net_ev=17 [-1236867584]
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: ASSERTION FAILED (soft)
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: Cond 0 [validate dsi_net_ev]
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: *********************************
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: qcril_data_event_hdlr: EXIT with err
D/RILC ( 26): RequestComplete, RIL_SOCKET_1
E/RILC ( 26): Send Response to RIL_SOCKET_1
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_iface_ioctl: Invalid qmi_wds_hndl found in this info_tbl_ptr b63f9dfc
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_event_hdlr: Error registering for Physlink Events
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_DATA_CALL_LIST_CHANGED length:344
E/RILC ( 26): Send Response to RIL_SOCKET_1
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_util_is_partial_retry_allowed: Not a Dual-IP call cid [1]
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_DATA_CALL_LIST_CHANGED length:344
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_DATA_CALL_LIST_CHANGED length:344
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_DATA_CALL_LIST_CHANGED length:344
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
I/RILC ( 26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC ( 26): Send Response to RIL_SOCKET_1
D/RILC ( 26): RequestComplete, RIL_SOCKET_1
E/RILC ( 26): Send Response to RIL_SOCKET_1
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_iface_ioctl: Invalid qmi_wds_hndl found in this info_tbl_ptr b63f9bb0
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_toggle_dormancy_indications: Request to toggle Dormancy indication failed.
E/RILQ ( 26): (0/26): RIL[0][event] qcril_data_toggle_dormancy_indications: qcril_data_toggle_dormancy_indications: EXIT with ERROR

from ubuntu-touch.

We are currently experiencing this issue with the latest Stable branch on a OnePlus One running Ubuntu 16.04 (OTA-5)

Currently it is possible to send out MMS messages but when receiving any MMS, no notification appears. Looking at the APN settings there were some differences but when I match it to the android settings I am unable to add a few configuration settings.
MCC, MNC numbers.

Any logs I can provide?

from ubuntu-touch.

I have the same issue with the bq E5 HD. It worked at the really beginning of ubuntu touch (with canonical). But after a canonical update, a couple of year ago, it didn't work anymore...
For each new system version, I hope that this problem will be fixed, but still not, unfortunatly.
I have the Ubuntu 16.04 (OTA-5) version now.

from ubuntu-touch.

Hello,
It seems to be similar to #276 and #975.
I have the same issue with LGE Nexus 4 (OTA-5 and OTA-6).

from ubuntu-touch.

i have a nexus 5 (hammerhead) and i am able to send/receive sms & mms but GROUP mms is all wonky. more often than not i am able to see certain people's replies (but not others) while everyone else is able to see all replies. where do i go from here?

from ubuntu-touch.

I've experienced similar issues with group MMS. In general MMS from a single number seems to work reliably.

My device appears to receive the message:

I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_RESPONSE_NEW_SMS length:668
E/RILC    (   26): Send Response to RIL_SOCKET_1
D/RILC    (   26): RequestComplete, RIL_SOCKET_1
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_RESPONSE_NEW_SMS length:472
E/RILC    (   26): Send Response to RIL_SOCKET_1
D/RILC    (   26): RequestComplete, RIL_SOCKET_1
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
I/RILC    (   26): RIL_SOCKET_1 UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:60
E/RILC    (   26): Send Response to RIL_SOCKET_1
D/RILC    (   26): RequestComplete, RIL_SOCKET_1
E/RILC    (   26): Send Response to RIL_SOCKET_1

...but nothing was logged at all in the messaging app's logs when this happened.

from ubuntu-touch.

Hey all,
I have similar experiences on my Nexus 5, ATT plan in the USA, OS Build number is 2019-08-17. I hope I can provide some extra useful information here.

I have experienced the red failed status on sending mms messages previously, but disabling and enabling the APN in system settings > cellular > carrier & APN, seems to have resolved that for me. I believe i read that on someones comment on one of the issues in this github.

The main issue I am having is not receiving group text messages. I am testing this out with a second phone of my own, and my wife's phone. Both android. I have found so far, if I do not have the group already created in my messaging app, i do not receive any group texts from that group. I tailed the nuntium log and see the notification received for a group text, yet messaging app did nothing with it. Once the group was created manually from within the messaging app, i can then receive future messages sent within that group. I have just discovered this today, so I am not sure if this is the proper fix for everyone or not. If i start missing out on group messages again I will report back.

from ubuntu-touch.

Did a little more debugging: it does appear that these messages are getting to telepathy-ofono as I'm seeing the message appear in dbus logs. This is a message that never made it to the UI:

method call time=1566350677.698848 sender=:1.33 -> destination=:1.19 serial=566 path=/org/freedesktop/Telepathy/Connection/ofono/ofono/connection_2b312dc02f48316f1eaf805c6e0b24a2/MucChannel1; interface=org.freedesktop.DBus.Properties; member=GetAll
   string "org.freedesktop.Telepathy.Channel.Interface.Messages"
...
method return time=1566350677.709521 sender=:1.19 -> destination=:1.33 serial=189 reply_serial=566
   array [
      dict entry(
         string "DeliveryReportingSupport"
         variant             uint32 2
      )
      dict entry(
         string "MessagePartSupportFlags"
         variant             uint32 0
      )
      dict entry(
         string "MessageTypes"
         variant             array [
               uint32 0
               uint32 4
            ]
      )
      dict entry(
         string "PendingMessages"
         variant             array [
               array [
                  array [
                     dict entry(
                        string "message-received"
                        variant                            uint32 1566350677
                     )
                     dict entry(
                        string "message-sender"
                        variant                            uint32 3
                     )
                     dict entry(
                        string "message-token"
                        variant                            string "/org/ofono/mms/310260937569696/23c6c5bc22231118daf472b23bc71f95"
                     )
                     dict entry(
                        string "message-type"
                        variant                            uint32 1
                     )
                     dict entry(
                        string "pending-message-id"
                        variant                            uint32 0
                     )
                     dict entry(
                        string "subject"
                        variant                            string "NoSubject"
                     )
                     dict entry(
                        string "x-canonical-mms"
                        variant                            boolean true
                     )
                  ]
                  array [
                     dict entry(
                        string "content"
                        variant                            array of bytes "testagain"
                     )
                     dict entry(
                        string "content-type"
                        variant                            string "text/plain"
                     )
                     dict entry(
                        string "identifier"
                        variant                            string "<Attachment>"
                     )
                     dict entry(
                        string "size"
                        variant                            uint64 9
                     )
                  ]
               ]
            ]
      )
      dict entry(
         string "SupportedContentTypes"
         variant             array [
               string "text/plain"
            ]
      )
   ]

from ubuntu-touch.

Hi everybody,
I don't know if it links with this issue, but my wife and I have noted some stange mms behaviors: when a picture arrived, if the text below is too long, there is no line break, the text is written outside its frame. It is impossible de move the screen to read the text, so we have to copy the mms and then paste it in a new message or in an app to be able to read it. This behavior appears with the OTA-8 I think (not sure) and the OTA-10 doesn't fixe the problem. I have a bq E5-HD Ubuntu Edition and my wife a OPO so it is not device dependent.
Another very strange mms behavior, but this time only on my wife's OPO: sometime, she received new sms mixed with old sms. That is crazy!
Tell me if I have to open new issues for this two problems, and thanks so much for all!

from ubuntu-touch.

Definitely a different issue since you are actually receiving the mms. the issue you describe is tracked in the messaging-app repo here: ubports/messaging-app#110

Hi everybody,
I don't know if it links with this issue, but my wife and I have noted some stange mms behaviors: when a picture arrived, if the text below is too long, there is no line break, the text is written outside its frame. It is impossible de move the screen to read the text, so we have to copy the mms and then paste it in a new message or in an app to be able to read it. This behavior appears with the OTA-8 I think (not sure) and the OTA-10 doesn't fixe the problem. I have a bq E5-HD Ubuntu Edition and my wife a OPO so it is not device dependent.
Another very strange mms behavior, but this time only on my wife's OPO: sometime, she received new sms mixed with old sms. That is crazy!
Tell me if I have to open new issues for this two problems, and thanks so much for all!

from ubuntu-touch.

Ok thanks!

from ubuntu-touch.

From Aug 19th 2019:

I have found so far, if I do not have the group already created in my messaging app, i do not receive any group texts from that group.

Once the group was created manually from within the messaging app, i can then receive future messages sent within that group.

It's been 4 days now, I have been sending and receiving lots of group text messages from friends and family alike (mostly iPhone users, some android). Current issues I face now:

• If someone includes me in a group text that I have not foreseen to create, i won't know they texted me unless they reach out to me via sms, or my wife is included as well and she will ask me if I received it.
• no notification push when group texts are received. (going to open a new issue for this in messaging-app repo)
• x-ofono-unknown message not found happened about 16 times yesterday, with a total of about 60 messages received. Uneducated assumption: I am not sure if this is something related to ubuntu or not, google search shows it happening a lot on androids and iphones and sounds like its carrier related or device/protocol related.

from ubuntu-touch.

A log entry from an mms I missed that my wife sent to me and one other person today. Both exist as contacts on my device. The mms group was not created by me, so I didn't receive a notification, nor see it in the messages.

dbus.log:
Error creating channel for incoming message "org.freedesktop.Telepathy.Error.InvalidHandle" "MMS Group not found in cache."

Here is more context from the log file before the error line (phone numbers redacted)

ADDED TO Q
REGISTER OBJ
message added "/org/ofono/mms/310410840635059/99b4699f65d7df1658b3fe5d6e8897c2" QMap(("Attachments", QVariant(QDBusArgument, ))("Date", QVariant(QString, "2019-08-23T16:10:58-04:00"))("Recipients", QVariant(QStringList, ("+1[my-number]", "+1[other-recipient-number]")))("Sender", QVariant(QString, "+1[sender-number]"))("Smil", QVariant(QString, "<smil><head><layout><root-layout/><region id=\"Text\" top=\"0\" left=\"0\" height=\"100%\" width=\"100%\"/></layout></head><body><par dur=\"5000ms\"><text src=\"text000001.txt\" region=\"Text\" /></par></body></smil>"))("Status", QVariant(QString, "received")))
oFonoConnection::onMMSAdded "/org/ofono/mms/310410840635059/99b4699f65d7df1658b3fe5d6e8897c2" QMap(("Attachments", QVariant(QDBusArgument, ))("Date", QVariant(QString, "2019-08-23T16:10:58-04:00"))("Recipients", QVariant(QStringList, ("+1[my-number]", "+1[other-recipient-number]")))("Sender", QVariant(QString, "+1[sender-number]"))("Smil", QVariant(QString, "<smil><head><layout><root-layout/><region id=\"Text\" top=\"0\" left=\"0\" height=\"100%\" width=\"100%\"/></layout></head><body><par dur=\"5000ms\"><text src=\"text000001.txt\" region=\"Text\" /></par></body></smil>"))("Status", QVariant(QString, "received")))
addMMSToService  "/org/ofono/mms/310410840635059/99b4699f65d7df1658b3fe5d6e8897c2" QMap(("Attachments", QVariant(QDBusArgument, ))("Date", QVariant(QString, "2019-08-23T16:10:58-04:00"))("Recipients", QVariant(QStringList, ("+1[my-number]", "+1[other-recipient-number]")))("Sender", QVariant(QString, "+1[sender-number]"))("Smil", QVariant(QString, "<smil><head><layout><root-layout/><region id=\"Text\" top=\"0\" left=\"0\" height=\"100%\" width=\"100%\"/></layout></head><body><par dur=\"5000ms\"><text src=\"text000001.txt\" region=\"Text\" /></par></body></smil>"))("Status", QVariant(QString, "received"))) "/org/ofono/mms/310410840635059"
ensure handle "+1[sender-number]" 3
oFonoConnection::inspectHandles contact (19, 3)
oFonoConnection::inspectHandles  ("+1[other-recipient-number]", "+1[sender-number]")
Error creating channel for incoming message  "org.freedesktop.Telepathy.Error.InvalidHandle" "MMS Group not found in cache."```

from ubuntu-touch.

@parksjr Oh interesting, that looks very relevant. Where did you find that log file? I searched my OPO for a file called dbus.log but can't seem to find it.

from ubuntu-touch.

@jfrederickson /home/phablet/.cache/upstart/dbus.log

from ubuntu-touch.

Oh nice they forgot to create incoming groups when they dont exist. Work in progress lol

from ubuntu-touch.

Excited to see a potential fix for group mms issue! Has any progress been made on this?

from ubuntu-touch.

Sorry maybe was misleading, but work in progress was directed towards the initial app devs in Canonical. I do not think that we started it here right now.

from ubuntu-touch.

I think we might need to clean up the MMS issues on the repository. There are several, but none describe a specific problem, and most are now taken to mean a problem that was previously fixed.

For example, this issue was originally taken to mean sending or receiving MMS to or from a single person. This now works (with caveats which I'll file), while recent discussion is all about MMS group messages. These are much different code paths which don't intersect very much. From looking at the results of my experimentation, single-recipient MMS is supposed to work while group texting was... a work in progress.

I propose we close this issue to collect the information about sending and receiving group messages in one place.

from ubuntu-touch.

Hello,
I agree with trickyut. That issue is not solved in my case as well.

from ubuntu-touch.

Sending and receiving MMS from a single person does not work for me either.

from ubuntu-touch.

Sending and receiving MMS doesn't work for me either
Device: FP2
Channel: RC
Build: 16.04

from ubuntu-touch.

nuntium and dbus logs somewhere in .cache/upstart can give you some informations if something went wrong with the MMS provider
It is known bug that if anything wrong to retrieve the mms, we don't have a notification and mms is lost.
Hopefully @sergiusens will work on that aspect soon. Finger cross

from ubuntu-touch.

Still an issue on PinePhone. Can't send or receive MMS.

from ubuntu-touch.

Still an issue on PinePhone. Can't send or receive MMS.

Can you please be more verbose about "Can't receive MMS" ? Do you have the message saying you received one but it can't be downloaded? Do you have no message at all? Did you set the APN correctly? Do you have 4G connection enabled? Which version of UT are you running, stable or devel?

from ubuntu-touch.

@Flaburgan hi this is still an issue with my FP2, I get a text message saying, "Oops, there has been an error with the MMS system and this message could not be retrieved. Please ensure Cellular Data is ON and the MMS settings are correct, then ask the sender to try again." I don't usually have 4G on.

from ubuntu-touch.

@LDovic

So that is normal behavior currently, if cellular data is off, you will have that notification. This is not a perfect solution but t least you're noticed now ( before MMS was lost and without any notifications ).
Jezek is hardly working on providing a more complete solution now, but not yet ready

from ubuntu-touch.

@Flaburgan hi this is still an issue with my FP2, I get a text message saying, "Oops, there has been an error with the MMS system and this message could not be retrieved. Please ensure Cellular Data is ON and the MMS settings are correct, then ask the sender to try again." I don't usually have 4G on.

Yes but that issue is known, you can follow progress there: https://forums.ubports.com/topic/5100/the-mms-lost-story/79
@sadtank was implying that the problem was bigger, especially if he / she can't send MMS with celluar data on and good APNs, this is surprising so we need more info.

from ubuntu-touch.