I'm on TMO (US). About a month or two ago I noticed my Voice over Wi-Fi functionality disappeared. At the time I was running Lineage (Oreo). VOWIFI quit working everywhere (i.e. both home, work, etc.)....don't think the problem was with my home network. I'm on the latest firmware.
I factory reset my phone (a number of times). I ended up switching ROMs (first to Skydragon Oreo) and now on to Nitrogen (Pie). I even went through a ton of TMO support, including taking my 3T into the store and testing other SIMs. I even installed a Magisk module to enable it. Nothing works.
I've got a workaround (Google Voice integration) but would really prefer having native Voice over WiFi natively again.
Does anybody have any suggestions about how to fix this?
Related
XT1060 on Verizon; right now on one of the later CM nightlies but I know I tried several other ROMs in the past (probably all CM based) to no avail. MMS messages sometimes send/download immediately, most of the time they take at least 30 seconds to send and received ones fail download several times. This happens regardless of mobile data settings, WiFi, 3G, LTE, Hangouts, Messaging, etc. I've yet to correlate anything with the success or failure.
I've been digging through logs and the CM sources and the issue seems to stem from initiating the mobile data connection for MMS. At this point I'm deep in the telephony stack and well out of familiar territory. I'm hoping that someone can verify that they're seeing the same issues on Verizon with non-stock ROMs and also hoping that there's someone out there more familiar with the whole telephony stack that can perhaps guide my search in more productive direction. APN settings look correct and the logs confirm that once a data connection is made the right APN is used and messages get sent/received. I've found some "unrecognized command" type errors in RIL logs during the connection setup phase, but haven't sorted out what they are yet.
I can't be of any help to you with the programming stuff but I can say I have two DE cm12 exhibiting the same bugs.
I also get a soft reboot, where I lose 4g and I have a '!' next to the signal. I don't know if they're connected.
The MMS taking forever is annoying though. I've been considering going clean to a newer nightly than I'm on now and see if it's any better.
Sent from my Nexus 7 using Tapatalk
I had the same issue on a 1060 DE running Nexus Experience (CM based) and what worked for me was to disable the stock mms application and I believe MMSService. Then installed textsecure and all worked well. I can't remember 100% if I kept MMSService disabled or not as I'm back on stock Lollipop, but some combination of the above will definitely work.
TextSecure doesn't appear to use the same channels to send SMS/MMS as the stock app. As I understand, it's more of a mobile data thing than a true SMS/MMS app, which would explain why it worked for you. I'm 100% sure the issue does not lie in the stock CM MMS app, I've traced it well outside of there and the app appears to function just fine once it gets the notification that a MMS capable network is available.
I also sometimes run in to the service indicator giving a network that is strings of numbers like "00000" or "31000". I don't know if both of these are symptoms of the same problem or something completely different.
Apologies for the mis-categorization of the thread, thanks for moving it.
It would appear that APNs do affect this. CM's apns-conf has a "Verizon" "internet" APN that's listed for MMS. Not sure what it's there for and the stock 5.1 apns-conf does not have it. Logs showed RILJ messages of SETUP_DATA_CALL attempting to access this "internet" APN instead of the "VZWAPP" APN that stock would try for. Running the stock 5.1 apns-conf and then also manually removing the "Verizon" APN in settings has allowed first connection MMS messages to download and send fine i.e. ones that result in a SETUP_DATA_CALL RILJ message. It appears that if the MMS connection is already open, however, that it fails until timeout on a RILJ message of RIL_REQUEST_ALLOW_DATA. After 5 retries, we get another SETUP_DATA_CALL message and everything works fine. I am currently running a build of CM with Motorola's 5.1 proprietary binaries though, I'll have to verify that the older ones shipped with CM do not function differently.
This may be related and not a device-specific issue but either a google play services or back-end issue. Reported here because of the mention of these appearing to be data services, not text services having issues.
VZW 1060 DE unlocked but not rooted and took the OTA to 5.1. Did not feel like I experienced any of these issues prior to the update
Now, in addition to tethering problems, having hangouts issues similar to the OP description... messages sometimes take forever to show that they sent, or to come in. I sent a photo 3 times and some text but never could tell from hangouts that I had sent them or got a reply until after I rebooted the phone.
Asus Zenpad: Same issue for hangouts, some hangouts NEVER get some messages - this is a wifi only device. On lollipop
friend's new iPhone: Same issue as OP for hangouts
friend's Droid Turbo: Same issue as OP for hangouts. Reports she leaves the hangout and comes back in to see updates
Edit: Found the LG-G3 is reporting the same issues after updating to Lollipop
http://forum.xda-developers.com/tmobile-lg-g3/general/lollipop-tethering-t3071188
This is 100% a RIL issue with this phone's chipset and vendor binaries. It may carry over to other hardware but it is certainly not a Google issue.
It appears that the libril binaries supplied with Moto's 4.4.4/5.1 do not support RIL_REQUEST_ALLOW_DATA. It looks like they support an older method, perhaps involving RIL_REQUEST_SET_DATA_SUBSCRIPTION.
FYI, i recently fastbooted back to stock 5.1, and MMS working quickly for me.
I'm able to get fully functioning normal MMS on CM 12.1 by hacking the DdsScheduler a bit. If I force it to transition to Idle after MMS releases its networkrequest, everything works fine. I'm confident this is a hacky way of doing it, but it at least narrows the issue down further.
As a side note, the whole DdsScheduler portion was added to telephony in 12. CM 11 appears to work fine, as do all stock versions, of course. As far as I can tell, this bug should affect Galaxy S3 users (probably among others?) as well. Can anyone weigh in on that? I don't have access to one with CM for testing. Anything running a Qualcomm RIL with a version less than 10 should be affected?
Hey guys, Basically I live in Ireland and bought my friends nexus 6 when he got a new phone.
It was working great and I rooted 5.1.1 and when I saw The (only android 6.0 available) marshmallow update available on NRT I dirty-flashed it, after seeing a thread on reddit saying dirty flashing to marshmallow hadnt caused them any device defects
Had no complaints until I tried to call my sister today (admittedly the first call id made in the first two weeks of owning the phone) and it said "Sorry you don't have access to the service"
So I played around with some reboots and sim reinserting and was surprised to see that when I changed to 2g Mode, It could make the calls! Really strange, is there any chance that the marshmallow image released on NRT would've had bands specific to US carriers?
I can make calls via whatsapp for the time being I guess Lol, but if anyone could give me a headsup as to what I did wrong ( or even a solution) Id be pretty grateful!
Thanks,
Nick
wipe data/system then flash again. you should never dirty flash between 2 different android versions. and dont listen to anyone else, i bet they do have issues.
Thanks for the help but sadly this didnt work for me at all!
Was playing around last night after I reflashed and I went to system apps and on seeing telephone and phone (two seperate apps , normal?) I disabled 'phone' for a second and could place a call successfully over 3g - but obviously with no dialer interface whatsoever because the app was disabled. Ive rooted and custom flashed alot of my phones but this has me puzzled
I had this problem on a previous phone. What happened is that it was stuck on LTE only. I know this phone has volte, but try messing with mobile connection
On Nitrogen OS Pie version. Calls in and out suddenly stopped working today. ROM installed weeks ago. On T-Mobile.
SIM card works in another phone, SIM from that phone changes nothing when inserted into my phone.
Texting in and out works. Cellular data works.
Cleared Dalvik cache. Tried exdialer app, doesn't work either.
Calls in go right to voice mail, call out attempts simply hang silently until they time out.
Rebooted numerous times. Confirmed Phone was the default dialer.
Anyone have any ideas?
Can't imagine why this would show up suddenly, but double check that the phone app is set as the default phone app.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Thanks, I had the same thought and checked that already.
ktmom said:
Can't imagine why this would show up suddenly, but double check that the phone app is set as the default phone app.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
So just as suddenly, it's working again. I did, however, leave the house, and probably hit another tower. Much to my surprise it worked about a 5 minute drive from here. Upon returning home I retried and it was still working. My wife's phone, also on T-Mobile, never had an issue. A total guess, could my IMEI have been blocked or stuck on the local tower? It's a far-fetched idea but I don't have a clue why it started working again.
I believe that calls are broken on 4G in all N6 pie roms. Instead, the phone is supposed to drop down to 3G during the call, but if that somehow didn't work either, you cannot do any calls.
Try searching the rom thread for T-Mobile to see if there has been problems with that company.
I have this exact same issue since I've tried Android 9 from either Nitrogen or Bliss OS, no phone. Went back to LineageOS or Paranoid Android, works fine again, so not the hardware. T-Mobile as well. Is there any decisive cause or fix for this rather than hoping it eventually works?
I don't use T-Mobile myself, and don't have the problem. But I've read that people have worked-around the problem by selecting preferred network type = 3G in settings, Network & internet, mobile network, advanced.
That will disable all 4G connections, so it's a heavy price to pay.
As to a fix, it will depend on a developer to solve it. Most things don't solve themselves, unfortunately. wavedashdoc has looked into getting VoLTE (required for 4G calls) working, but has been unsuccessful so far.
See https://forum.xda-developers.com/ne...n-substratum-11-10-2016-t3478365/post78666645
I installed Carbon ROM Oreo 8.1 on January 1st on 2 Shamus. It is the most stable ROM I have ever used! Everything works and zero crashes. Never used any ROM that something didn't crash.
Pie sucks ass with what they did to the volume controls. I had to install 2 apps to "fix" the volume controls. And cell data never worked with any Pies that I tried. Just forget Pie ever existed!
https://get.carbonrom.org/device-shamu.html
I am having a strange issue that I can not find the reason for.
I am on a NON-ROOTED, Not Unlock Note 9 with Tmobile. Current running Pie Beta DRL7.
Using Samsung Messages 10.0.10.5 I am not able to send MMS to other (Newer) Galaxy Devices. Sends fine to J7 and iPhones but not to S8 and up so far. If I use Android Messages it goes through so it is not a Data/Wifi problem. I have tried it with Data only, Wifi On, Wifi On w/Wifi Calling. It tries to send it twice and holds each time at the last few 0.# MB. Even toggled RTT on and off as well as Wifi Calling Cellular/Wifi Preference. Just at a loss.
Since I am not rooted and on the Beta, I can not simply uninstall the 10 version or upgrade/downgrade. Is there something I am missing maybe or are others having a similar issue.
I have a Pixel 4xl on Spectrum. Since my phone updated to Android 12 I have been unable to make phone calls on cellular and data randomly drops, you can watch it flash off and on several time, randomly. I get a Verizon error message. I can make calls on wifi only. After security and bug fix it worked for a short time then back to not working. My wife has the same phone and hers worked but dropped calls randomly anywhere between 1-10 minutes. Hers works a little better now but still has issues sometimes. After all this I rooted mine so I won't keep loosing data while working on it. In rooting I had to reinstall the factory ROM. I can now make calls on cellular but now drops calls between 1-10 minutes. Has anyone else seen this? Should I just go back to 11, if so which factory image do I use and how do I install it. I am rooted but not custom recovery installed.
iluvdroid said:
I have a Pixel 4xl on Spectrum. Since my phone updated to Android 12 I have been unable to make phone calls on cellular and data randomly drops, you can watch it flash off and on several time, randomly. I get a Verizon error message. I can make calls on wifi only. After security and bug fix it worked for a short time then back to not working. My wife has the same phone and hers worked but dropped calls randomly anywhere between 1-10 minutes. Hers works a little better now but still has issues sometimes. After all this I rooted mine so I won't keep loosing data while working on it. In rooting I had to reinstall the factory ROM. I can now make calls on cellular but now drops calls between 1-10 minutes. Has anyone else seen this? Should I just go back to 11, if so which factory image do I use and how do I install it. I am rooted but not custom recovery installed.
Click to expand...
Click to collapse
I seem to have faxed it. Contacted Spectrum for the second time and they had me reset the network settings and it seems to have fixed it. Settings->System->Reset options->Reset Wi-Fi, mobile & Bluetooth