Database Develop

issues with messaging - not sending mms

hi guys,
I rarley follow this forum as my wife wont let me touch her moto x, so this is a non-rooted unlocked addition bought direct from Motorolla and used with T-mobile US.
Her issue has been intermediate and not always reproduceable, sometimes when she sends MMS they arent recieved but about 70% or more are. and about 99% of here SMS are recieved when sent.
Issue has been present since day one (about 6 months ago now) and she only now has gotten fed up and wants a fix. She mostly uses hangouts but issue is present when using defult android messaging app as well.
APNs look correct, T-mobile blames Motorolla and Motorolla blames T-mobile.
I was hoping someone would know if this is a common issue or know of a fix or know if there is someone who really is at fault (other than me for only doing minimum searching before posting this thread - at work now but pregnant wife needs a fix now...)
any help would be much appreciated!
thanks

You could try this: Settings > More > Mobile networks > Access point names > T-mobile US LTE (touch this one) > APN type (scroll down to get to) > add ,dun to the end of the string after fota. APN type should read 'default,mms,supl,hipri,fota,dun'. Restart and try mms again. Also, there are a number of good mms apps besides Hangouts or stock Messaging. I'm using 8sms from Play store and I really like it. I have it set up as the default messaging app and have it active for Active Notifications. At home, Assist reads out my incoming texts and lets me reply or not all by voice. I don't have to touch the phone or see the display.

Thanks for the reply,
Still haven't had a chance to dig through this any further but I will for sure test out your suggestions when I get a chance.
Mostly was just curious if this was a common issue or is this one more unlucky cell phone thing that my wife has to deal with (seems like every phone she has had has had issues)
I'll post back with the results,
Thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Thanks for the reply,
Still haven't had a chance to dig through this any further but I will for sure test out your suggestions when I get a chance.
Mostly was just curious if this was a common issue or is this one more unlucky cell phone thing that my wife has to deal with (seems like every phone she has had has had issues)
I'll post back with the results,
Thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had a problem with that APN setting to on my razr M once when it was a fairly new phone refused to send my text messages had to add a new APN don't remember exactly but it did fix the problem never had issue again.. google it you should get some info there that's how I fixed it

Moto X Not sending MMS fix.
Clear Cache Partition.
1. Turn the phone off.
2. When the phone is off, hold the volume down button 2-3 seconds and TAP the power button. You will see a few options on the screen.
3. Use the volume DOWN key to highlight RECOVERY.
4. Use the volume UP key to select it.
5. The device will display the Motorola logo and then the Android in distress ( logo with Exclamation mark).
6. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key.
7. The device will display additional menu options (Text will appear in BLUE).
8. Use the VOL DOWN Key to scroll to wipe cache partition and the POWER Key to select this option.
9. The device will then perform the partition wipe, this will take a few min, don't be alarmed. The phone will reboot on its own when done.
My non sending MMS's were fixed instantly by doing this and you will not lose ANY of your settings or pics or music or contacts... it just wipes the Cache. I hope this helps any and or all of you with this issue.
Stock Moto X XT1058 Unlocked on T-Mobile.

Issues with my nexus 6

I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.

Yes, most of them are common.
Capri72 said:
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Click to expand...
Click to collapse
Most of these are common gripes, none can be corrected natively, but some can be corrected through different Rom's and such.

so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.

ripped85 said:
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
Click to expand...
Click to collapse
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).

That opens a big can of worms.
simms22 said:
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
Click to expand...
Click to collapse
MMV, but the update should make things more definable. What apps a user may have and whether or not they are updated to work on lollipop should not be such a drastic issue, In a perfect world, Google should provide for backward compatibility or come out with a whole new version of their operating system; I.E. Windows 7 as opposed to Windows 8.

I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.

[email protected] said:
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
Click to expand...
Click to collapse
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.

runekock said:
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
Click to expand...
Click to collapse
Sorry lol had to hook it to laptop and run Nexus toolkit

Problem with OK Google recording

Hi All,
I just recently encounter the following error on my Huawei P9 Plus, when I use an application that requieres the need to record (Shazam, cámara, sleep as Android) I pop up message appears showing that "com.android.googlequicksearchbox:interactor" will not be able to record right now, I read in other forums that the main problem is with the OK Google functionality to identify in any screen, if I turn it off the message disappears, the thing is that I use the OK Google functionality heavily, so the solution does not work for me, I have cleaned the cache of the apps, uninstalled and installed and even wipe cache partition with no help...
Anyone with the same problem?
This just recently started, noticed it yesterday
I have attached a image for your reference.

Same thing happened to me. In order to resolve this, i've disabled the "Ok Google" detection from any screen.
Somehow with recent updates of Google Play or whatever it is might have triggered this error.
Clear cache & Reset Factory doesn't solve this either.

I got the same problem on P9 lite. With some search I found that almost all the guys reporting this error seem to be using Huawei phones. I would also like to see a fix, hope someone comes up with something like disabling "ok Google" detection when another app starts recording audio.

Seems to be due to an update with the Google app, as it happened to me all of a sudden (a few months back), without any changes other than app updates. All i've managed to find on it are from fellow Huawei users as well.
For a phone that is aiming at other, more established, flagships, they really do seem to **** up on the little details (not counting the 'shoot with a DSLR and claim it's a P9' debacle or the more recent emmc/ufs outright lie, which aren't so 'little'). After paying so much, why should I have to choose between having OK Google available on all screens (as it was designed to be), but have to deal with error messages, or disable the feature (basically making it next to useless) just to clear the errors?

[Solved] Calling issue from the Call Log P10 Lite

On all my previous Huawei devices (Ascend P6, G7 and P9 Lite) with various iterations of EMUI, when I went into the call log, I would press on one of the entries, and it would automatically dial the number of the contact.
On my P10 lite (WAS-LX1C02B120), when I press on a call log entry, it opens the "Edit before call" screen, so I need to press the call button in order to call my contact. I have checked in the call settings for a way to turn this off, but I couldn't find anyway to change this.
Is this new behaviour from EMUI 5.1 and up normal, or is this a bug? I'm really hoping it's the latter, and that it will be fixed in a firmware update. If not, then I hope there will be an option to turn this behaviour on or off, since I find it a bit tedious, especially since EMUI 5.1 is supposed to be more intuitive, using less steps to do various actions.
I would prefer not using a third-party dialer, so am hoping for a solution to this.
EDIT: I've solved the problem! After doing a factory reset, restoring my backup, and still having the issue, I uninstalled each and every one of my apps, to check which app what causing it. It turns out it's my RCS+ messaging option that causes this bug! Disabling this option fixes the issue!

Ok, so I have no idea what changed, but it seems to be working as expected now. I had no updates, and I definitely didn't change any settings! It's the craziest thing! [emoji848]
Anyway, I'll see if it changes again.
Sent from my WAS-LX1 using Tapatalk

I just tried to make a call from my call log, and it's doing the same thing as before, where I need to press the green dial button before it makes the call! It's so frustrating!!

I've solved the problem! After doing a factory reset, restoring my backup, and still having the issue, I uninstalled each and every one of my apps, to check which app what causing it. It turns out it's my RCS+ messaging option that causes this bug! Disabling this option fixes the issue!
First of all, I noticed that I was able to make a call directly from the call log, immediately after a restart, but a few seconds later, it would go to the "Edit before call" screen, which made me realise that it had to be one of my apps that are loading in the background. Anyway, long story short, it's fixed now! I don't use RCS anyway, so I'll just keep it disabled until it gets fixed. :good:

Question Mi 11 - MIUI 13.0.8 Very weird bug please help.

Hello,
For weeks now i have been trying to figure out a very weird bug on my Mi 11 but i can't seem to find the cause.
What is happening is that the navigation buttons go crazy in some apps. For example when i press on one of the 3 navigation buttons in lets say Edge web browser the buttons register like 10 presses in a single second and send me all the way back to the home screen even though i hit the back button once to try and go one page back.
I thought that maybe there was a hardware problem or a problem with the screen protector but even without one i still have the same issue. And the issue only appears in certain apps or certain places in certain apps. For example in YouTube the home/back/navigate buttons work fine and register a single press until it is playing a video then when i press one it goes mental. I really hope to solve this issue because now i cant navigate back in apps because it just yeets me all the way back to the homescreen with a single press.
Things i have tried with no success
- Change the refresh rate and resolution
- Remove screen protector / clean phone
- Try out different launchers
- Reboot phone
- Remove apps that used a overlay / on screen widgets
- Update to MIUI 13.0.8 i ran the version prior to 13.0.8 and that is where the problem initially started out of nowhere.
I am trying to avoid a factory reset because that would take me a lot of work to get everything back.
I have uploaded a video to make the problem a bit more clear as you can see in the video in Google Play store the buttons function correctly but once i open Edge or Reddit they go crazy.

I just tried Edge and it works fine for me.
But also i got the "official" 13.0.4.
Which ROM do you run with V13.0.8?
And (this seems to be one of the important point for xiaomi devices) did you make once a factory reset after(!) you flashed the ROM?