I miss having Ubuntu on my phone, and am interested in seeing where we are with VOLTE support?
Unfortunately I had to revert back to Android until support is added.
I may not be of much help, but if anyone would like to point out where I can try to help, I would love to at least try.
@standupmobile Thank you!!
Set to 3G with wifi on, rebooted...and I now receive notifications!
I then asked someone to send me an SMS...AND YES! I can now send and receive SMS!
Would like to have LTE...but I am fine with 3G and wifi 100%. Love it! Thanks for finding that. Now I can stick with UT for good! You will see me on the OpenStore soon 
@dobey I figured it wouldn't have a negative effect, but thanks for the clarification on which branch is currently being used!
@standupmobile interesting that you point all of that out.
On OTA16, I forced 3G because I was having issues with 4G...and at that time I had no major issues with consistent SMS. Now I am on solid 4G running OTA17...and can only send....not receive SMS.
As for push notifications...it is odd that you found you had better luck with push notifications on 3G, but not on 4G or even wifi. If I wasnt using my pixel 3a as my DD, and didnt want to risk mucking up my APN and losing 4G...I would totally force 3G to see if push notifications work.
I have been looking through the repos as of late...but have had no major findings that could cause the connectivity check to fail on 4G & wifi, but not 3G.
I did notice the move from TLSv1 to TLS1_2 in this commit, but the connectivity check endpoint is http, not https...so wouldnt think it would matter.
https://gitlab.com/ubports/core/lomiri-push-service/-/commit/7d7f8c2ef4283526587eb496c9964185f46e2f7c
@dobey @Flohack issue created:
https://gitlab.com/ubports/core/lomiri-push-service/-/issues/33
Let me know if I can be of any help. Trying to get started with contributions, but am just starting out and have only just begun looking through repos.
@flohack will do, thanks Florian!
@flohack
Here are my logs for reference. I tried posting links but they were being marked as spam, so my apologies for the dump:
pushclient (app):
From file /home/phablet/.cache/upstart/application-click-pushclient.christianpauly_pushclient_1.0.log:
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.124\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.Operations\" member=\"list\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4658 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.124\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.OperationsMonitor\" member=\"running\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4658 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.124\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.OperationsMonitor\" member=\"last_error\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4658 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.124\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"com.canonical.libertine.Service.OperationsMonitor\" member=\"result\" error name=\"(unset)\" requested_reply=\"0\" destination=\"com.canonical.libertine.Service\" (uid=32011 pid=4658 comm=\"/usr/bin/python3 /usr/bin/libertined \")"
lastError - no arguments?
qml: 🤖 ============PUSHCLIENT STARTED============
QObject::startTimer: Timers cannot be started from another thread
qml: 👍 Token changed to: cHVzaGNsaWVudC5jaHJpc3RpYW5wYXVseV9wdXNoY2xpZW50OjpiRnF3SDZNR3dkeExkcVZQMlZ3T2N1WDdaZ2gzRE5ZVjZ5TEEwUT09
[PERFORMANCE]: Last frame took 51 ms to render.
[PERFORMANCE]: Last frame took 43 ms to render.
[PERFORMANCE]: Last frame took 40 ms to render.
QObject::startTimer: Timers cannot be started from another thread
qml: 💬 Sending push notification ...
propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.294\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=1384 comm=\"NetworkManager \")"
nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.294\" (uid=32011 pid=9694 comm=\"/usr/lib/qt5/bin/qmlscene qml/Main.qml \") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=1384 comm=\"NetworkManager \")"
"Object path cannot be empty"
QObject::startTimer: Timers cannot be started from another thread
qml: ✍ Answer from push service: {"ok":true}
qml: 💬 Sending push notification ...
qml: 💬 Sending push notification ...
qml: ✍ Answer from push service: {"ok":true}
qml: ✍ Answer from push service: {"ok":true}
QObject::killTimer: Timers cannot be stopped from another thread
QObject::startTimer: Timers cannot be started from another thread
qml: 💬 Sending push notification ...
qml: ✍ Answer from push service: {"ok":true}
QObject::killTimer: Timers cannot be stopped from another thread
QObject::startTimer: Timers cannot be started from another thread
ubuntu-push-client:
From file /home/phablet/.cache/upstart/ubuntu-push-client.log:
2021/05/20 10:32:14 Unsolicited response received on idle HTTP channel starting with "H"; err=<nil>
2021/05/20 10:37:25.029321 ERROR while GETting http://start.ubuntu.com/connectivity-check.html: Get http://start.ubuntu.com/connectivity-check.html: net/http: request canceled while waiting for connection
2021/05/20 10:42:25 Unsolicited response received on idle HTTP channel starting with "H"; err=<nil>
2021/05/20 10:47:35.033831 ERROR while GETting http://start.ubuntu.com/connectivity-check.html: Get http://start.ubuntu.com/connectivity-check.html: net/http: request canceled while waiting for connection
2021/05/20 10:52:35 Unsolicited response received on idle HTTP channel starting with "H"; err=<nil>
2021/05/20 10:57:45.035909 ERROR while GETting http://start.ubuntu.com/connectivity-check.html: Get http://start.ubuntu.com/connectivity-check.html: net/http: request canceled while waiting for connection
2021/05/20 11:02:44 Unsolicited response received on idle HTTP channel starting with "H"; err=<nil>
2021/05/20 11:07:55.040633 ERROR while GETting http://start.ubuntu.com/connectivity-check.html: Get http://start.ubuntu.com/connectivity-check.html: net/http: request canceled while waiting for connection
@flohack I do not see that message.
Pings from terminal to that domain pass with 0% packet loss, and I am able to GET that page in Morph browser without any issues.
Hello all,
I recently upgraded from OTA-16 to latest, and appear to not be getting push notifications on my 3a.
I should be getting pushes from TELEports (receiving them on my other android phone), but not on my 3a running UT. I was getting them before the upgrade though.
I tried reinstalling all apps to no avail. Also tried the pushclient app on the OpenStore, and I do not receive those either.
I would like to avoid a full reinstall if possible.
Looking at logs for ubuntu-push-client, I see these messages:
Unsolicited response received on idle HTTP channel starting with "H"; err-<nil>
ERROR while GETting http://start.ubuntu.com/connectivity-check.html: Get https://start.ubuntu.com/connectivity-check.html:n et/http:request canceled while waiting for connection
Both messages appear while my android phone receives its push notification, leading me to believe its related...but I could be wrong. It is only an assumption.
I am able to open http://start.ubuntu.com/connectivity-check.html in Morph with no issues, and I am on a stable wifi connection.
Any ideas on how to troubleshoot?
Note...looking at logs for teleports... I see:
qml: Got push token:
Then
Registering device for push notifications
Followed by:
UNHANDLED: updateChatPinnedMessage
Not sure if the unhandled error is related to push notifications or not.
This could be completely unrelated and coincidental, but wanted to post some findings on the data/sms issue.
I am running OTA-17 on my pixel 3a. WingAlpha is my carrier (MVNO), who operates on AT&T (gsm) towers in the US.
My first go at using UT as my daily driver was short lived because of the data and sms issues. At that time I was running RC for OTA-17.
Typically, both 3G data and SMS would work for an hour or so before dropping.
Rebooting seemed to resolve it sometimes, but not always. I updated my APN with my carrier settings, and set data to 3G on first boot to no avail...so I ended up reverting back to Android for a few weeks because it just wasn't stable.
Fast forward to yesterday...I really wanted to use UT as a daily driver and move away from android...so I figured I would install UT again and poke around. I am a mobile app developer by trade, but am a complete novice when it comes to halium, and linux development for that matter.
Unlike my first attempt, this time I did not touch the apn settings. I also did not force it to 3G, as recommended.
I have been now running UT with consistent 4G data. I would like to point out though, that every time I enable anbox (anbox-tools enable), I do experience drops in connection (morph browser not resolving DNS). Disabling anbox and doing a hard reboot via terminal brings my connection back solid. Like I said above...it may be coincidence....but it happens to me every time I enable anbox.
As for SMS...there are still issues. Yesterday I was able to receive and send SMS. Today I was able to confirm that someone sent me an SMS, which I did not receive even 3 hours later.
I then used this site to send myself an SMS...and I did not get it.
https://www.bulksms.com/test/
I did a hard reboot...and used the same site to test again...and I did receive the SMS the second time. So its a bit spotty.
I know this isnt much to go on, but figured reporting any findings may help! If I can help debug in any way, let me know.