-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MMS not working - unknown group "sailfish-mms" ? #42
Comments
Thanks for the detail report, def looks like the new sailfish group creation stuff so should be fixable, we;ve already done some similar fixes. I gotta ask thou, who is using MMS these days ??????? |
I am. It's dumb and therefore works on all phones, even feature phones. The big advantage is also it requires no installation at all, and no "add friend to group" thingie, so very convenient for sending stuff to people who do not belong to your usual groups/circles.
However, I am not getting the issues here. MMS actually never worked this well on Sailfish for me, works 100% of the time instead of 10% or less on Jolla, Jolla C and X Compact with the same operator (Freemobile).
…On 2020-08-11 19:09 Adam Pigg ***@***.***> wrote:
Thanks for the detail report, def looks like the new sailfish
group
creation stuff so should be fixable, we;ve already done some
similar
fixes. I gotta ask thou, who is using MMS these days ???????
—
You are receiving this because you are subscribed to this
thread.
Reply to this email directly, [1]view it on GitHub, or
[2]unsubscribe.
References
1.
#4
2#issuecomment-672103871
2.
https://github.com/notifications/unsubscribe-auth/ABWHHQ2LGSHVNQU
6RRSOX3LSAF3LZANCNFSM4P2JQ6OA
|
After some research, mms-engine should work for either theprivileged group or sailfish-mms group, and the service starts it with the privilieged group. could you add the verbose switch to the service file probably in /etc/dbus-1/..... and get more logs thx |
Hello Adam. Thanks for the quick feedback and tips. First of all, as I see some commits in mer-core/mms-engine from last month, I forgot to say that I installed the latest image available on gitlab (https://gitlab.com/sailfishos-porters-ci/t5-ci/pipelines?scope=finished&page=1), which is 3 month old : https://gitlab.com/sailfishos-porters-ci/t5-ci/-/pipelines/143699483, and chose the "run-build-testing" version according to Kabouik 's guideline. Anyway, I found the dbus file at location "/usr/share/dbus-1/system-services/org.nemomobile.MmsEngine.service" that matches https://git.sailfishos.org/mer-core/mms-engine/blob/master/mms-engine/org.nemomobile.MmsEngine.service I changed it to add the verbose flag as follows:
Then running "journalctl -f" as root, I see the same trace as posted before when run as user, but I see some additional messages interleaved from ofono:
The kernel line seems unrelated, as it appends some other times in the trace. So I am now trying to find details "Unexpected data call status 51" from the ofonod source code. |
Found it:
And the value 51 (printed as decimal, 0x33 as hexa) would be from this enum:
What ? In the settings "MMS access point" page, Protocol is set to "IP" (other choices are "IPv6" or "Dual"). By the way "Data Access Point" is also set to "IP" but shouldn't be related. I see that during all my tests to try to make it work, I tried switching Authentication to "PAP" (or "CHAP" ? I didn't write down which it was), and didn't put it back as I thought... I was connected to wifi, so tried to disconnect from wifi, and as I was in the menu, I also cut the data connection and restarted it. I reconnect to wifi, and it now fails. So, it looks like my settings are mostly correct. So, I have not yet understood all my mistakes, but seem to have found a way it works by setting it to IPv6 and disabling Wifi... |
I got to sent new MMS today from outside wifi coverage. It worked with the previous configuration (IPv6, Wifi activated but not connected). I will keep an eye on this, and if I find something new (bug or solution), I will come back here. So I am closing it for now. Thanks again for the help to troubleshoot and find a fix ! |
I have setup a new Pro1 with a SIM card that was previously in a Jolla1, and made a backup import from the Jolla1 so got my settings as close as possible to what was before on the (mostly) working Jolla1.
I have not been able to send or receive any MMS yet.
I already got sometimes some trouble with the Jolla1, where the trick was to disconnect Wifi and switch to 3G to make it work, so the problem may not be in the Pro1 port.
So I tried to find more info on the error (as there is only a 15 minutes wait, that finishes with a notification (popup and present on the event page) that the message cannot be sent/received. On TJC there are some commands : https://together.jolla.com/question/38555/mms-issues-hints-for-debugging-and-helping-us-to-improve/
Trying this, I get some access errors in the trace:
The trace goes on and on, retrying continuously but slowing (every 15 seconds, then every minute...), the part between "Retrieve[8342] SLEEP -> READY" and "Released /ril_0`". I also replaced some number that I wasn't sure if it was personal data by XXXX.
In this trace, I find the following 2 lines surprising :
[dbusaccess] WARNING: Unknown group "sailfish-mms"
[mms-ofono] ERROR: GDBus.Error:org.ofono.Error.AccessDenied: Operation not permitted
This looks like some group is missing, so there is a dbus call that fails, so can't activate the proper context and stops until next retry.
This could be due to changes in newer sailfish that this command cannot anymore be called from nemo user.
Do you have the same results ? Others ? Any ideas of commands to test to get more details ?
The text was updated successfully, but these errors were encountered: