SMS and call audio not working
-
I think all of UT phones will downgrade to 3g for calls.... So if Verizon has no towers supporting 3g, it explains your experience. on 4g, you need working Volte ... Which is a big challenge at the moment due to lack of standards/ documentation.
-
@standupmobile I think you can still use 4G/LTE without VoLTE enabled. I know my Android has VoLTE diasabled by default and so did my iPhone. Most people in my area don't even know it exists. Is it just required to have the device support it or something?
-
Hmm ... Good point ... I am not sure. I understand VoLTE to be "Voice over LTE" ... or in other words: Voice over 4G ... rather than downgrade to 3G for calls. My understanding - (probably wrong!): was that on 3G, voice and data was on separate networks (Data is IP switching and Voice is Circuit Switching), and on 4G, voice and data are merged both to IP switching... or if not, voice gets sent back over the legacy 3G. I know that when I my UT is on 4G and a get or make a call, my indicator switches to 3G. I should however let someone more knowledgable chime in....
-
@standupmobile Yes your understand is correct. Whats also important to know is that when in VoLTE mode some daemons in the Android OS take over parts of the modem´s work, up to the point where they have to handle the raw VoIP stream ^^
-
@Flohack @StandUpMobile Are either of you developers who could possibly get 4G/VoLTE working? There's over $250 worth of a bounty in the Google Pixel 3a post.
-
@triguy no its far beyond that money. 250.000 would be a potential amount, but maybe not even that is enough
-
@flohack lol
-
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.
-
@azraelpwnz Get a look at here : https://forums.ubports.com/topic/5100/the-mms-lost-story/123
-
@azraelpwnz note that SMS is now 100% reliable in and out. MMS photos work in and out with wifi OFF. Wifi ON is a problem, but broader than the P3a.
https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271
-
This post is deleted!
