Related
Yes this is the development thread, and all I really have is a problem, but I think it's something only solvable by you devs.
My phones sms has been completely Effing up lately.
I will get the notification up in the bar, and I can pull that down and read into the message, but if I open Handcent or the default app the text won't show up and will not be there.
So reasonably I stopped using Handcent, and Message widget and all sorts or things like that, wiped my phone, cleared the partition, flashed a new rom. Different firmwares [1.6 and the new open eclair]
But nothing really seems to help or work, apparenlty mms has been failing a lot which I know is more so on Tmobile's end then it is my phone but idk whats up, tonight I get this new Android notification
"com.android.mms a large number of sms messages are being send. select "ok" to continue of "cancel" to stop sending"
whenever I hit send, I haven't yet rebooted to see if it persists but it's a pain.
Is there any device log or collection I can submit so someone can look into it, possibly a bug? Virus? Somethin' stupid like that?
Thanks.
p.s. and my inbox isn't full or anything ridiculous like 1000+ messages, I've got about less than 50 currently, and when I said stopped using Handcent and MessageWidget, I mean uninstalled.
This happened to me on rare occasions while I was using Handcent. But it doesn't happen when I use the default messaging app. So I assumed it was due to handcent. Not quite sure why you're getting the other problems though... =/
This happened to me as well when I changed to a 2.1 rom. I chose to go back to Dwangs 1.6 rom until the 2.1 roms have been completely stable.
Hey try using ChompSMS. I think its better than Handcent SMS
Icebergxx said:
But nothing really seems to help or work, apparenlty mms has been failing a lot which I know is more so on Tmobile's end then it is my phone but idk whats up, tonight I get this new Android notification
"com.android.mms a large number of sms messages are being send. select "ok" to continue of "cancel" to stop sending"
whenever I hit send, I haven't yet rebooted to see if it persists but it's a pain.
Click to expand...
Click to collapse
That doesn't sound good at all.
Have you checked with t-mobile to see if you are sending a stupid amount of text messages? It could be someone is sending spam messages via your phone or something. It could explain why you are unable to receive messages.
I think you are from the government, trying to find out whom on here knows how to subvert there android espionage. I for one will state to you officer, that I know nothing about this, and am stupid to the whole concept of bugs.
PS Do not try to trace my post, as both me and my computer are wearing tinfoil hats (with the shiny side out).
In all reality, one trick I learned as a teenager to check if your phone may be bugged, is to find an old business that still uses a switchboard phone system (this was hard in the early 90's, and may be impossible now) and phone them. If your phone was bugged, then they would see two lines coming in as one and become quite confused.
Whoa guys, by "bugged" I meant viruses not I'm being spied on haha.
It's occured on the 2.1 build Open Eclair
and a Cyan 1.6 build.
With and without using alternative applications for messaging.
I got sick and tired of it so I decided to go back to my most solid rom I've ever used.
A Soul Life 1.5 build, and I haven't had any troubles yet.
When I preformed the nandroid backup however it still tried to act like my sd card was partitioned and the market was buggy for a few but the cache is cleared up and it's all good now.
Icebergxx said:
viruses
It's occured on the 2.1 build Open Eclair
and a Cyan 1.6 build.
Click to expand...
Click to collapse
Run for the hills it's the linux virus! Disperse!
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "registered on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
zimphishmonger said:
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "used on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
Click to expand...
Click to collapse
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
ItsDon said:
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
Click to expand...
Click to collapse
Doesnt work for me, and I've been working with support and tried EVERYTHING (uninstall\reinstall, re-register, all the suggested fixes, etc)
I signed up for the beta, downloaded the file and installed it. I could swype all day and nothing appeared in the text box. Installed one of the previous unreleased versions and it worked fine, uninstalled and tried the beta again with same failure mode. Swype doesn't make it easy to comply with their requests to use approved software.
Both Swype support and myself have no idea why, but we were finally able to get Swype up and running on my phone.
Huge thanks for Brian from Swype support for his help, and I recommend anyone having issue to contact their support to see if you can get the issue resolved.
The app has a somewhat complicated (encrypted) registration process, and somehow that was not completing successfully, so def let support know if you are running into similar issues
This happened to me too. I gather it happens every time I install a different ROM, I need to contact Swype to get my Beta account re-authed.
Stuff that, I can't be bothered, I'll just wait until the paid version comes out.
Thought I'd give it another try and still get the "Limited Functionality..."...As usual with restricted access, DRM, etc, it is the ones who try and follow the rules who lose...the pirates will always find a way. Back to the leaked version for me, I guess, though I do think the HTC IME keyboard is still faster and more accurate.
I also get the "limited functionality" message, but only occasionally.
I haven't tested this hypothesis, but seems like it only does this to me when I am at home--and when I'm at home, I'm usually on wifi.
Maybe there's some kind of DRM that didn't take into account that people may occasionally switch from 3G to wifi connections.
If I had more time I'd try messing with it a bit, but I'm just headed to sleep.
There's probably a call home check on first application start up. When you wipe or switch ROMs, that will be cleared, but their servers already have the product registered.
Try backing up the app-data for Swype in between wipes/ROM updates.
I got the "limited functionality" message every time, no ROM updates between download and install. I even reinstalled the installer, redownloaded, etc and it just doesn't work. Glad it didn't work, because it convinced me to go back to HTC IME which is faster and more accurate for me.
http://www.mediafire.com/download.php?toniw2xejzz
its from the other swype thread and this worked for me.
hope for the rest also
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
I have confirmed with a swype tech that there is a registration\call back home immediately following the install of the apk. If successful it will have a quick spinner stating "reristering swype" and the ask you to "enable swype".
I, unfortunately, seem to have major issues getting it to actually call back home, where it states "Swype has already been installed. please uninstall and try again" (I had previously uninstalled it).
In the end, had to revert back to the leaked versions
m_kayali said:
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
Click to expand...
Click to collapse
Ive tried MULTIPLE times to uninstall and reinstall swype w/o rebooting, so I think it wouldn't have a chance to zipalign until the next reboot.
Kind of sad that Swype hasn't gotten back to me yet
Somehow, I am using the Beta version I downloaded myself. I was trying out Super D for a week which is when the Beta was open, later I went back to Dwang and Swype broke when using the Beta installer but I got it working using AppMonster. Here's the steps I followed over that time:
- Wipe phone and install Super D
- Install AppMonster from Market
- Sign up for Swype Beta
- Download SwypeInstaller and install Swype Keyboard
- Perform backup with AppMonster
- Wipe phone and install Dwang
- Download SwypeInstaller and install Swype Keyboard
At this point I got the "Limited Functionality" message
- Wipe phone and install Dwang again
- Install AppMonster from Market
- Restore backup of Swype with AppMonster
Now I can go into Settings and enable Swype in the usual way. I have been using it without a problem for a couple of weeks now.
What solved it for me
I had Swype installed and working on a G1 with Cyanogen latest but after an uninstall it stopped working for me with the same error messages as described here in this forum.
What solved it for me is not pushing the done button on the touch screen after the package install but pushing the back key on the phone. This got me in the registering Swype screen after which the swype installer crashed. Swype is fully working however using these steps.
just go back to installer , log in and reinstall. Everytime i flashed a new rom i did this. I found out u can do this 10 times, before they cut u off. Obviously they know whats up?!
obviously i like the real beat with vibration option and more stable. im using now the final pre release that was made available in a couple posts above mine. no vibration, but it works. this keyboard is fantastic!
Hey guys, i have a pretty serious problem with SMS messaging. It seems like my Milestone refuses to receive SMS messages. I've been using FroyoMOD and now i have Cyanogen 7 RC3 from kabaldan. With both of them i've experienced this issue. And it's always the same.. after like a month or so from when i flash the ROM..it's happening again. It's really annoying and people are yelling at me for ignoring them So, if anybody knows what's the deal or has experienced the same issue.. i'll be more than glad if you had any suggestions. For now i pretty much think it might be something like kernel-related or whatever.. i don't really know
Thanks in advance and sorry for my bad english.
install advanced task killer, open the sms app, go to advance task killer and uncheck the sms app...with this setting you can receive sms...
forgot to mention that i use handcent or chomp sms..not the stock app. that also might be the problem. i tried rebooting and i don't think i have any task killer that kills my sms app. unless the task killer is integrated w/ the ROM. Anyway, gonna try this.
Got the same problem here and it's driving me crazy.
I've taken a look at the log and you can clearly see the sms arriving, because android is starting the sms app. But it get's killed before it can safe the sms. I believe it's due to a memory shortage. I've tried several different memory management settings and also tried to fix the sms app in memory by adjusting the oom_adj value (see thread here: http://forum.xda-developers.com/showthread.php?t=1012330)
But nothing realy helped for long. I still loose many SMS also Whatsapp mostly does not notify me about new messages. Push mail works most of the times. Gtalk notifications I'd say work only in 50% of all cases. I'll probably downgrade to CM6. The milestone simply has not enough memory for Gingerbread.
Is your data memory low?
there is a bug when getting lower than ~20mb of free memory,
(last time I ran in that problem was in 2.1, so i'm not sure if releavent to 2.2 and up)
Yes, it's quite low and can possibly be below 20mb at some times. When I look at it it's usually around 30 Mb. I can get more free memory by adjusting the memory manager settings, but that only means it kills background apps even more agressively, or so I understand it.
Astrowe said:
forgot to mention that i use handcent or chomp sms..not the stock app. that also might be the problem. i tried rebooting and i don't think i have any task killer that kills my sms app. unless the task killer is integrated w/ the ROM. Anyway, gonna try this.
Click to expand...
Click to collapse
Handcent seems impossible to run even on stock telus froyo http://forum.xda-developers.com/showpost.php?p=12675946&postcount=13
I'm going to reinstall it and test with minfree values of 6, 8, 26, 16, 16, 32.
Hancent is always in the 4th or 5th slot so maybe that will work.
well i just flashed latest MIUI, sent sms to my number and received it.. i think i had SuperCharged minfree from you zeppelinrox. well i guess it's always the same: i flash new ROM, it works and after some time it stops. what the hell.. the thing is i never used stock messaging app, that might be the cause.
I use supercharge script with aggressive 2...moreover i use advance task killer...i didn't lose any sms...before that sometimes I didnt receive any sms...you have to unselect your app for sms(stock one, handcent, chompsms)...I use stock sms app and everything is working...
Its seems you'be got me wrong, I mean applications data memory, not device ram.
Sent from my Milestone using XDA App
yosriz said:
Its seems you'be got me wrong, I mean applications data memory, not device ram.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
You're right. I got you wrong. I've got plenty of application memory. I've had low applications data memory a few month ago and it took me days to realize taht this causes the phone not to receive any sms. But as soon as you free up memory all SMS seem to be coming through.
mike-08 said:
Got the same problem here and it's driving me crazy.
I've taken a look at the log and you can clearly see the sms arriving, because android is starting the sms app. But it get's killed before it can safe the sms. I believe it's due to a memory shortage. I've tried several different memory management settings and also tried to fix the sms app in memory by adjusting the oom_adj value (see thread here: http://forum.xda-developers.com/showthread.php?t=1012330)
But nothing realy helped for long. I still loose many SMS also Whatsapp mostly does not notify me about new messages. Push mail works most of the times. Gtalk notifications I'd say work only in 50% of all cases. I'll probably downgrade to CM6. The milestone simply has not enough memory for Gingerbread.
Click to expand...
Click to collapse
by the way, What do you mean by "I've taken a look at the log"?
by the way, just got another problem... seems like everytime i flash MIUI ROM (and maybe any other ROM, idk) and recover my messages from backup with SMS Backup & Restore, the phone sends out by itself like 5 messages always to the same people. It happened like 3 times so far.. and it's pretty much possible that i flashed it 3 times.. but i think that might be more like the sms backup-related issue. The 5 msgs seem to have something like hasn't-been-sent-yet flag or whatever.. seriously, i just feel like throwing the phone out the window right now.
Maybe it's application issue?
I've been using "SMS Backup+" for long awhile (probably since november when I first flashed MIUI)
and never ran into problem.
yosriz said:
Maybe it's application issue?
I've been using "SMS Backup+" for long awhile (probably since november when I first flashed MIUI)
and never ran into problem.
Click to expand...
Click to collapse
i think so too.. gotta change my backup habbits i guess
thanks for the tip.. i used SMS Backup by Christoph Studer to backup my sms to gmail.. didn't know that there is also something that can restore the sms from gmail.
yosriz said:
by the way, What do you mean by "I've taken a look at the log"?
Click to expand...
Click to collapse
Is used the Debuger from the Android SDK. When you connect your phone to the computer you can log almost everything with it in realtime.
Btw. I've just migrated to MIUI to try if SMS arrive here more reliably. But I'm not yet sure I like the user interface. It's rather different from CM7.
Sent from my Milestone using XDA App
Thanks man!
you've just open a whole world for me..
is it done through adb?
yo can give me reference, that I can search about? thanks.
yosriz said:
Thanks man!
you've just open a whole world for me..
is it done through adb?
yo can give me reference, that I can search about? thanks.
Click to expand...
Click to collapse
You need to install the Android SDK from Google. Since you know adb I guess you allready have it. In the SDK there's a file called ddms.bat. That starts the debugger.
Same stuff here...
I´ve had similar issues relating the sms thingy. I´m going to try that app killer thing to see how it goes.
You may view my post here:http://forum.xda-developers.com/showthread.php?t=1112009
Hope someone figures out a way out of this.
Thanks.
Possible solution
Ricfil said:
I´ve had similar issues relating the sms thingy. I´m going to try that app killer thing to see how it goes.
Hope someone figures out a way out of this.
Thanks.
Click to expand...
Click to collapse
well i have an observation. after i stopped using all sms backup apps, the problem is gone. and by sms backup app i mean those that backup to gmail, not to sdcard. if you have an app that checks for new sms's and automatically backes them up, then get rid of it.. if you need an one time backup, use SMS Backup & Restore.
like i said, getting rid of automatic sms backup apps did the trick for me.
Dear xda users,
I have quiet some time a problem getting notification message in whatsapp and hangouts (even in the previously version on Google talk).
When i clear all apps with Task Manager. Exit to home screen. meaning, Whatsapp is not running in the background, I get no pushed messages, no notifications. Nothing at all.
I then launch the app and get all my "missed" message ,then exit back to the home screen and now I see the messages and notifications.
The same thing happen when the screen is off,actually it seem it start there.
I have no limitation on the background apps,surf only with 3g and it is happen also with hangouts,it is started a few months back before google update her app,in the old Google talk also.
The most strange thing is when i launch a game,because it uses the internet when i exit from it and not clear my task manger it seems like whatsapp and hangout getting the message for day or two and there again nothing,maybe i imagine i really do not know
My phone model is i9305 with official Samsung Nordic Rom.
i used avast anti virus until couple days ago.
By the way whatsapp+ that i saw here recently could help me in any way?
I really appreciate your help. :good:
want to clear it one and for all to enjoy my phone.
Thanks in advance,
David
Hi David,
you kinda answered yourself, the problem is with the task manager. I suggest reading the following:
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Chris Hoffman can explain better than me
BTW it's also says directly on whatsapp that it will not work well with task managers.
Cheers
Dear eytan123,
Thank you for your replay,I want to clarify myself and tell you that i do not use any external task manger,but only the built in one in jellybean.
In addition even when i do not "clear" my ram it still no working,i also compare it to others galaxy 3-i9300&i9305 that use and clear the ram with the built in task manager and still not suffer from this Phenomenon.
I guess Samsung keeps this app because it lets inexperienced users(unlike you and myself, or for that matter anyone in XDA ) the feeling that they can upgrade their performance...anyhow - It's strongly suggested that you don't activate\use ANY task killer.
Why not trying the suggested method for a couple of days? I'm sure your results will be much better
Thanks again for trying to help,but i already try this couple of times before open this thread.
Unfortunately not a single method that i tried was useful to me.
like to hear if you have another idea
upp
bumping a thread more than once every 24 hours is against the rules. don't post until you read them
Just noticed you asked about the whatsapp+ - it's not supposed to make things any better, only customizations. And you said the problem persists at the new hangouts.
If you're certain that your internet connection(cellular of course) is working good, before I suggest wiping and re-flashing or trying another rom I suggestthat you use the following app(it increases battery usage in a VERY MINOR way):
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5hbmRxbGltYXgucHVzaGZpeGVyIl0.
Try clear data
Make sure sync is on
Sent from my GT-I9305 using Tapatalk 2
Hi,
Thanks eytan123 but this app that you gave me it is just for rooted phones,i do not want to root my phone in this moment,about the rom,it is the same problem that i experienced in my previous official rom.
Still glad to hear about this app for future notice
Thanks hello5629,if you mean to clear app data i already try this also
You wanna tell me that only my phone suffer this problem?
Just making sure - have you tried to uninstall and reinstall the apps ?
yep,several times..
Well I guess that leaves you with factory reset your phone.
But since your'e not rooted keep in mind you'll lose all your apps..
ya i know,i do not really want to do it,i think i will open a thread in general android forum,maybe there when it is not only i9305 community,maybe some will have the answer.
Thanks again for your effort
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Update: I wasn't imagining things haha.
http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/
CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?
I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since
none
[/COLOR]
CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.
zelendel said:
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?
Click to expand...
Click to collapse
Was just curious if something was clearing Chrome and causing this to happen, and if maybe I had known about this and tried it the last two times I wouldn't have had to uninstall anything.
Gage_Hero said:
I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since
Click to expand...
Click to collapse
USMC retired said:
[/COLOR]
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.
Click to expand...
Click to collapse
Using the stock Google Messenger app. I tried using Hangouts as the default SMS app but it happened there too. I hate SMS/MMS so I really want to avoid downloading any additional apps haha. I usually try to force people into using an instant messenger but you know how people can be. It's just annoying because I usually don't even get a notification that I'm missing messages. I just open conversation and it says "tap to download" or "downloading..."
I'm working fine now so maybe the next time it breaks and Chrome as the default browser isn't the fix it I will explore some third party apps, it just seems like this is a "thing" with Marshmallow.
http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/
I had the same issue. Got my nexus 6, before even setting it up, I rooted and installed marshmallow pure nexus. I'm on T-Mobile. I had 3 apn's under settings. The fast-tmobile had mmsc blank. The 3rd apn had T-Mobile mmsc filled. I copied that, pasted it into the fast-tmobile apn, clicked save, then deleted the other 2 apn's. I use hangouts, and since doing that, I've had zero issues at all. If I change roms, its the first thing I do. I'm more inclined to believe it's in your apn. Many people have had the same issue. I went back to 5.1.1 and took the ota. Mms was broken and I had to apply the same fix. Still on the stock ota, and all has been well. Good luck
Sent from my Nexus 6 using XDA Free mobile app