Database Info

MMS selectively working on Nexus 5

So I think they weren't working at all because my IMEI wasn't updated with AT&T when I got my replacement phone. Got that addressed.
Since then, I was able to receive old MMS, but even new ones sometimes get hung up on trying to retrieve them. exiting app and going back in doesn't fix it.
Starting the phone up again does though..
Made sure APN settings are good to go, unchecked 'mobile data' in sms settings and re-enabled within Hangouts.
I'm on stock rooted 4.4 (and franco kernel)
any idea whats going on? It seems like other people are having this problem too but I don't understand it. Thanks.

I am seeing the same issues here.. Stock play store purchased and rooted on Sprint, sometimes it works sometimes it doesn't, sometimes even SMS sits forever and wont send or receive until I restart the phone, trying to find someone with a Sprint purchased N5 to compare APNs with
Its almost 2014, you would think someone would be able to straighten out the massive amount of MMS issues with android phones :/ It should "just work" to the customer

I have a feeling it has something to do with Hangouts app itself..

I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app

Teczeus said:
I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
That's interesting you're also experiencing it with other apps.
I haven't tried anything but Hangouts.
Maybe it's a Kit Kat issue? no clue.

Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app

Teczeus said:
Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is true.

Running on metro pcs and my mms is perfect with hang out and sliding messaging pro. Metro runs gsm off T-Mobile towers.
Sent from my Nexus 5 using Tapatalk

Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.

tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.
Click to expand...
Click to collapse
Thanks for the update! More knowledge into my brain housing group to share now lol.

FuMMoD said:
Thanks for the update! More knowledge into my brain housing group to share now lol.
Click to expand...
Click to collapse
No problem I hope it helps some of you guys out!

tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
Click to expand...
Click to collapse
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!

jonzr said:
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!
Click to expand...
Click to collapse
For sure! adaway had been working well for me.

Same issue here on Tmobile
tyrellcorpnexus said:
For sure! adaway had been working well for me.
Click to expand...
Click to collapse
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.

jamjr74 said:
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.
Click to expand...
Click to collapse
Same here but with hancent and hangouts

SMS not sending, but able to receive. MMS + Data Working.

Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.

AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SCSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!

tonybahr said:
Not sure if I'm doing this right usually I use the app but since I can only text on touch wiz based Roms xda app keeps crashing. Anyway I have this issue too mine seems to have started on 2-20 but same thing reboot or toggle airplane mode and I can send one that's it till next reboot. Was running carbon kit Kat. Hopefully Odin tomorrow will fix it touch wiz sucks!
Click to expand...
Click to collapse
Odin does not fix...
Sent from my SCH-I535 using Tapatalk

Dex954 said:
Odin does not fix...
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yeah I figured that out.

Having the same problem....just wondering if anyone tried unrooting and rerooting?

mamill66 said:
Having the same problem....just wondering if anyone tried unrooting and rerooting?
Click to expand...
Click to collapse
Yes doesn't fix anything.
Sent from my SCH-I535 using Tapatalk

Just kinda bumping to see if anyone found anything?
Sent from my SCH-I535 using Tapatalk

I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535

AnTiDoWn3r said:
I talked to Verizon again yesterday night, my support ticket is still open, meaning they're looking into the possibility of it being an issue on their end, so nothing new. I'm convinced it's something with them, because of the timing. I'll keep you posted.
Sent from my SCH-I535
Click to expand...
Click to collapse
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?

AnTiDoWn3r said:
Hello Internet, I just thought I'd chime in on the sms issue many seem to be having.
For me it started in the morning on the 21st. The day before everything was peachy. That morning I woke up and sent my normal texts that I usually do. The first text sent fine like usual, but anything after would fail to send. One quick-fix I found was to toggle airplane mode before sending a message, which would allow me to send another text or two before failing. The most interesting thing about this issue is that my brother, who is on cm 10.2 started having the issue at the exact same time and we aren't even running the same versions of android.
So I called verizon today and after about a half our I was able to get some information. I told the guy that I had tried rebooting, clearing cache, factory reseting, updating my SMSC number, etc. He said it's probably an issue in their end, which makes sense due to the timing of the issue occurring. He said he would do some behind the scenes stuff and call me back on Monday. I guess we'll see if the issue gets resolved. Keep me posted if you find a solution.
Click to expand...
Click to collapse
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.

Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
I'm in Hershey pa as well... interesting
Sent from my SCH-I535 using Tapatalk

Whisk_33 said:
I'm having the same issue that you are. I've already posted a thread. http://forum.xda-developers.com/showthread.php?t=2657822
Are you on a version of CM? I was on mastamoon's 10.2 and moved to his CM11 and still have the problem. The only other fix I have heard/seen is that you can turn your mobile network to just CDMA and the problem goes away. (Its slow, but it works).
You are from Hershey Pa. I am in the Wilkes/Barre Scranton area. Anyone else experiencing this problem and in this area?
Do you have voice+ or google voice in your app drawer? I've seen some people who have had it in their app drawer who have been able to open that and select disable which remedies the problem. Hopefully Verizon gets back to you.
Click to expand...
Click to collapse
Yes, I'm from Hershey PA, my brother and I both have GS3s, but he's running 10.2 RC2 and I'm on the latest D2 nightly. The issue started in morning on the 20th. From what I can tell, it's only Verizon customers in our area that have been affected, my buddy on AT&T with a CM Nightly hasn't had any trouble. I tried disabling Voice+ but it didn't help anything. As of this point, my ticket is still open, so no new news yet. I'll keep you posted.

Dex954 said:
Do they know you are running a form of CM? Or are you just saying your texts aren't working?
Just for my own info?
Click to expand...
Click to collapse
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.

AnTiDoWn3r said:
I haven't told them I'm running a custom rom and I won't unless I actually need to. They don't seem to take kindly to people who like to get the most out of their phones.
Click to expand...
Click to collapse
That's why I think this is going to be a hard road..
Sent from my SCH-I535 using Tapatalk

This is actually quite fascinating. All of those who seem to be having this issue are in Central Pennsylvania, started having the issue around the 20th, and are running a version of Cyanogenmod. I'll be sure to bring that up in my next chat with Verizon. Stay posted.

Hershey PA here
Cm11 m3 d2vzw
I've been having the same problem since ~20th as well. In glad I found this thread as I couldn't find much else when searching. I've temporarily switched to a TW ROM and it worked fine but any aosp seems affected. I even got Verizon to give me a sim but it didn't help.
My cell number starts 570-57*-**** (Scranton area number ) though I now live in Hershey pa.

This is where I wish I knew someone who worked at vzw and was a reasonable person.
Sent from my SCH-I535 using Tapatalk

I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app

bass0324 said:
I am just outside Philly, I started having this issue on the 20th as well, occurred on both paranoid android beta 4 from notta and slim kat stable 3.0. Seems to be intermittent for me as there is times where it works freely and times I need to toggle airplane mode for every text
Edit: my number is from northeast pa (Hazleton Area). I'm wondering if it is an area code issue or something because I know people with s3s down by philly who don't have this issue with Verizon.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Been having the same issue. I live in mountaintop so maybe you're right

Central PA 570 here as well. Both my mom and I's phones are experiencing the same. What baffles me is that it happened to be people who had already flashed the ROM prior to the 20th, which means it isn't an AOSP specific SIM activation issue, because that happens on first boot. Touchwiz works fine, although I can't stand it. Whatever it is, I desperately hope it's fixed soon.

Issues with calls and text

Hey xda! Man it's been a while.
I have the lg g3 in AT&T. I've had it sense release. I had it rooted at the beginning when ideas theming roms and having fun on xda. Life changed and I stopped, unrooted, and been that way sense.
The past month I've been having issues with calls and texts. Some calls are not coming through and going straight to voicemail. The text issue is the most annoying. I'll recieve some but not most of the text people send me. Especially in a group message.
I just did a factory reset on the phone. In hoping that will help. But as I typed this a message from earlier got sent to me twice. Wtf lol. So, anyone else hear of this issue? Would you think rooting and using a stick rooted rom help? Everyone in the house and around me are not having issues on a variety of phones on AT&T.
Btw I have tried third party text apps. I really don't want to purchase a new phone yet. I rather enjoy this one.

cwhitney24 said:
Hey xda! Man it's been a while.
I have the lg g3 in AT&T. I've had it sense release. I had it rooted at the beginning when ideas theming roms and having fun on xda. Life changed and I stopped, unrooted, and been that way sense.
The past month I've been having issues with calls and texts. Some calls are not coming through and going straight to voicemail. The text issue is the most annoying. I'll recieve some but not most of the text people send me. Especially in a group message.
I just did a factory reset on the phone. In hoping that will help. But as I typed this a message from earlier got sent to me twice. Wtf lol. So, anyone else hear of this issue? Would you think rooting and using a stick rooted rom help? Everyone in the house and around me are not having issues on a variety of phones on AT&T.
Btw I have tried third party text apps. I really don't want to purchase a new phone yet. I rather enjoy this one.
Click to expand...
Click to collapse
That really sounds a lot like a network issue. If you have already factory reset, next step is get a new sim. If they don't fix it it would only ly to being a network issue.
Sent from my iPhone using Tapatalk

Hi cwhitney24- did you flash a new ROM for your lg g3? If you did you should flash your stock ROM via backup and that should help or reflash the entire phone with odin it self don't worry you wont lose anything. Solution if none helps then bring the back and see what's causing the problem.

hyelton said:
That really sounds a lot like a network issue. If you have already factory reset, next step is get a new sim. If they don't fix it it would only ly to being a network issue.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Awesome. Thanks. Glad to see xda is still helping out. I figured that would be the answer, but second opinions are always great to have.
Also nice to see an RC helping. ? I was an rc and an rt back in the day. I was also in the xda Google helpout team. On man those were the days. Fun times.
Thanks again.

mvp-flasher said:
Hi cwhitney24- did you flash a new ROM for your lg g3? If you did you should flash your stock ROM via backup and that should help or reflash the entire phone with odin it self don't worry you wont lose anything. Solution if none helps then bring the back and see what's causing the problem.
Click to expand...
Click to collapse
I haven't rooted it. I did when it first came out then unrooted it. Been non rooted over a year. I just facorty reset it. Will see how this goes then try a new sim as suggested above. Thanks!

cwhitney24 said:
Awesome. Thanks. Glad to see xda is still helping out. I figured that would be the answer, but second opinions are always great to have.
Also nice to see an RC helping. ? I was an rc and an rt back in the day. I was also in the xda Google helpout team. On man those were the days. Fun times.
Thanks again.
Click to expand...
Click to collapse
Your welcome I usually to to keep up with the LG stuff stock wise anyway. I still own a G2 as my 2nd line. I honestly had a lot of problems out of my D850 but that was when running custom roms or my want to run stock international. Never liked How AT&T tinkered with the firmware.
Yeah try a new sim or try someone else's sim in it. I did have call issues on my D850 but that was due to running a D855 stock based rom.
Or you can also try my back to stock tot method as well, but if your already stock it might not make a difference.
Sent from my iPhone using Tapatalk

Issues with Wi-fi and Bluetooth radios

Hello XDA!
I'm having some issues with the wi-fi, and bluetooth, connectivity on my GM-930F S7 (Non-edge) phone.
The wi-fi issue is that it occasionally disconnects, and when I try to re-connect, it either doesn't work (quickly goes through the motions, but doesn't connect), or lists the hotspot as "disabled". I had no issues with this on my backup Note, nor on my older S5.
The bluetooth issue is that if the phone doesn't seem to have a direct line-of-sight to the earphones then the audio almost immediately drops out and begins to stutter/drop seconds of audio, like somebody is bashing the mute-button.
I think both of these issues are related, potentially they share the same radio. I do have a HDSPA+ connection when I'm out and about, so that works, but I do think perhaps I've got a mismatched radio/setting somewhere which is screwing with those two.
I've already tried to return to stock, twice, using two separate ROMs flashed through Odin (BTU-G930FXXU1DPLT-20170117160813, & G930FXXU1DQE7_G930FEVR1DQD1_EVR) (I'm with EE), and I've also tried a myriad of other roms, (AOKP, AOSPExtended, ResurrectionRemix, SlimRom, Linage 14.1), however none of them seem to solve the issue.
My question is has anybody experienced an issue like this before? Are there any specific radios or things you'd recommend I flash, either via TWRP or Odin? Any more details I can provide?
Just so I'm clear, the wi-fi and bluetooth worked beautifully on my S5, so I have no reason to believe that hardware is at fault, it's very likely the phone.

I've also just tried it with a MM rom (G930FXXU1APAW_G930FOXA1APBA_BTU) and the same issue occurs.

Seems like faulty hardware. I am using superman ROM and no problems so far. I mean, i doubt you will fix it by changing ROM. You should bring it to the service.
Sent from my SM-G930F using Tapatalk

pakidermo5000 said:
Seems like faulty hardware. I am using superman ROM and no problems so far. I mean, i doubt you will fix it by changing ROM. You should bring it to the service.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I don't think it's hardware, if it was then the wi-fi/bluetooth would either work, or not work. I mean if I keep the phone close to the earphones the bluetooth is fine, but if it's arms length away, or there isn't a line-of-sight, it drops, the wi-fi is similarly spotty, but not working/broken. I had a similar issue on my old S5, I ended up solving it but I can't remember how, it was years ago. However it certainly was a software issue. Either ROM, or Kernel, or Modem/CP, etc.
I see lots of comments from people about the issue occurring once they upgrade to Nougat, so I'm very sure it's software. Possibly an issue with the Kernel or Modem, or a combination of both.

Would it be possible (minus the EFS of course) to get an upload of your setup so I can try with your exact settings? I've tried the SuperMan ROM before, but I'll give it another go now.

Also (Although it isn't 100% solved), I've found trying out the ROM "[ROM] S8 FULL PORT FOR S7 & S7 EDGE by ambasadii [AQEB] [v3.1]" noticeably increases the range that the bluetooth works over. It still isn't a large range, but it more than doubles it. I've gone back to previous ROMs I've tried, speaker and phone in the same place, and it doesn't transmit that far, back to the S8 Port, and it does. I've no idea what could be causing this and it's really bothering me. I know the S8 has upgraded bluetooth software, but this speaker worked fine with my S5.

BarrettBear said:
Would it be possible (minus the EFS of course) to get an upload of your setup so I can try with your exact settings? I've tried the SuperMan ROM before, but I'll give it another go now.
Click to expand...
Click to collapse
What do you need exactly? I have the exynos version.
Sent from my SM-G930F using Tapatalk

pakidermo5000 said:
What do you need exactly? I have the exynos version.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
As do I
Ideally just a snapshot of your system, minus all the personal information and such - if your bluetooth works fine with your modem/rom/bootloader/etc and it doesn't on mine, then at least I can be reasonably sure it is a hardware issue, in which case I'll have to try to get it mended.
The reason I'm not 100% sure is the S8 ROM extended the BT range to what other S7 ROMs haven't, so I'm still not 100% sure.

Question OP9 global dropping phone connection until restart.

Le2125 on Nameless, however previous le2127 (converted to global) also had this while on OTA update....
Verizon network.
Every other day I'll suddenly get immediate dropped call when trying to dial out, anyone calling goes straight to VM.
Phone restart fixes it for a day or so and then it happens again.
Any ideas on where to start?

bigd2442 said:
Le2125 on Nameless, however previous le2127 (converted to global) also had this while on OTA update....
Verizon network.
Every other day I'll suddenly get immediate dropped call when trying to dial out, anyone calling goes straight to VM.
Phone restart fixes it for a day or so and then it happens again.
Any ideas on where to start?
Click to expand...
Click to collapse
Custom roms are just that. Imperfect. I love using Lineage 20 I'm also on op9 global Na unlocked. It's almost perfect really though. Rcs working flawless and network. I find some small issue and msm back. Anything that is still receiving builds by the manufacturer is usually better than custom. Now after we stop getting sec patches and updates . I will indeed go to Lineage if device is still working. We still get A14 though. And A13 isn't bad at all rooted and pixel dialer features !!

This was the case with the OTA update as well.
I actually switched to the custom ROM hoping maybe there was something different.

bigd2442 said:
This was the case with the OTA update as well.
I actually switched to the custom ROM hoping maybe there was something different.
Click to expand...
Click to collapse
There is. A worse cam to start.

mattie_49 said:
There is. A worse cam to start.
Click to expand...
Click to collapse
I'm not following