SMS and call audio not working
-
I have a Pixel 3a which I was running on the Development Channel. After creating the 2 APN's 1 for internet and 1 for MMS, I was able to send/receive SMS/MMS/Calls & data via LTE worked. I think that was on version 240, and it ran pretty stable for a few days. After updating to version 244 & then 246, I was unable to receive SMS/MMS although I could send SMS (I didn't tryp MMS). I was also only able to get about 18 hours of use with light to moderate use (mostly internet browsing and some texting, minimal calls).
I've since gone back to Android as I need my phone to work.
I'm in the U.S. using StraightTalk on AT&T.
I'm willing to re-install UBports to assist with troubleshooting.
Mark
-
@mark1250 The development channel is not suggested as that is, as the name implies, for development. I would go with stable if I was you. Anyway, this is strange because nothing has changed between those versions, at least not on the port side. Might be interesting what the radio logcat has to say:
sudo env LD_LIBRARY_PATH=/vendor/lib64:/system/lib64 /system/bin/logcat -b radio -
Update on my data situation: I have gotten cellular data to work with an APN edit, however it flickers from working to not working. MMS remains unfunctional and I am unable to edit its APN settings. Calling also does not work. I'm very happy to be making progress
-
@freefrog Does anyone have a working US Verizon mms APN that they would be willing to share with me?
-
@freefrog Sorry I got confusted with the acronyms, I mean sending texts is my problem
-
@fredldotme I re-installed UBports and am on the RC channel. SMS seems to be working. - (Has been working for more than 24 hours).
I tried to checkout the radio logcat;
sudo env LD_LIBRARY_PATH=/vendor/lib64:/system/lib64 /system/bin/logcat -b radioGives me:
CANNOT LINK EXECUTABLE "/system/bin/logcat": library "libtls-padding.so" not found.It seems that I'm missing something.
-
IDK if this info helps but for some reason I can't have the MMS APN without a MMSC value which is blank on android
-
@mark1250 You probably just need to run
unset LD_PRELOADbeforehand for the command to succeed. -
I had to reinstall and wipe to get onto OTA-16 for some reason, but I'm not having the issue where calls / SMS aren't coming in after not restarting for 8 hours. It's been receiving and sending SMSs for about 18 hours. So I assume the issue is resolved. My 4G is still intermittent for some reason after updating the APN settings for my Ting with my credentials. I haven't tried reverting back down to 2G / 3G.
-
@fredldotme The weird thing for me is that even on devel channels, I cannot even make or recieve calls. I've only ever recieved one call on my Pixel 3a with UT but I missed it and it was probably a scammer or telemarketer lol. When I attempt to make a call out at any point, I hear nothing coming through the speaker and the recipient's phone doesn't ring. It just says "calling" and thats it. Not even a dial tone. I also cannot send or recieve SMS or MMS. I havent been able to configure MMS in my APN settings. It just reverts my changes. I really wish the APN settings could tell you if/which settings are invalid and which ones you need. When I put my SIM card in for the first time, it auto-generated a config that didnt work. I've since copied over settings from Verizon's website and it still doesnt work. Where I live in America, Verizon has no towers less than 4G/LTE. This means that setting my device to 3G or 2G cuts out all my service. The device seems to connect to towers with 4G as I see a signal and an "L" icon. I have only gotten data to work twice by accident but it loaded a single webpage only and then stopped. It also could have been a cached webpage. I think service works periodically for a very small window of time. I am not sure why some people get service with the same phone and I dont but maybe theres differences in hardware between devices too...?
-
@triguy For me switching the "internet" APN profile from whatever it is to "vzwinternet" then restarting helped the data to work. Also I could edit the MMS entry but only after filling in a value in the MMSC field though no edits I made were able to fix the mms. Everything else works the exact way you've said for me
-
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
