There was a problem with but not limited to some mintmobile users on the P5. Most of the Reddit posts are from November and early December. The problem was that calls would either not connect at all or would drop mid call. I had the P5 for 2 weeks and never had that problem but that may be because I use a Google Voice number and app.
Did anyone use to have that problem and are still using P5 with mint? This they push an update to fix it?
Only problem I had was that wifi calling would work for a few hours and then later on, if you tried to make an outgoing call, it would attempt and immediately die. So far, it seems ok so I think it might be fixed.
Related
Hi I am using the ATT HTC VIVID from Nov 2011.
I bought this phone last Nov 11, and I stated noticing my phone was not receiving any calls if I stay at home(jersey city). If anyone calls to my number it will not connect at the same time it will not sent to voicemail also. It will say "call couldn't be completed".
After 2 months fight with ATT, they tried
1. they did a factory reset on my phone - it didn't help
2. changed the sim card - it didn't help
3. finally they replaced a another HTC vivid
even that didn't help
finally they said there was issue in near to my home and they fixed it.
now i a started receiving calls but now the new issue is, if I call to my number it will not connect first time it will go to voicemail, and second time if i try then it will ring. (First time also my phone is idle) This is happening randomly and ATT is not helping on this situation. As per them I am not able to replicate when they were testing on my phone.
Because of this issue I am missing calls which is making me really frustrated. After three week of research I found this is happening in not only near to my home its happening at my work place (NYC) and if I go around also its happening.
Can someone please give some advice to fix the issue that would be really great
Is there anyone else in or around your home with AT&T service? If so, do they experience the same problem as you? Can you receive calls everywhere else besides home and work? Do text messages get through? How about internet service? MMS?
Thanks for your response
The issue is not around my place
The issue is, if any one calls first time it will go to voice mail, if they call again it will connect to my phone. This behavior is happening randomly.
It is happening in my work place(NYC) and also if i go some where in new jersey also. I can't tell when its happening and how. In a day it may happen one or two time. I can't check constantly on a day when and where.
Sometime i feel I am not getting call, if i try from land line it may work or it may go to voice mail, after the second try then it will be fine for that day.
this issue look little weird. but because of that I am missing calls.
forgot to mention, that time my internet will work fine, how I am sure is one time i was browsing and trying to call my phone from land line it didn't connect. as usual second time if i try it did connected
Also the signal bar in my home and my work place its full
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
Over the past week, calls made while I'm on wifi using both T-Mobile Wifi Calling or Skype have been choppy and every 5 seconds or so, the voice of the person on the other line goes in-and-out. I've tried on multiple wifi networks so it's not the network. I can't tell if it's related to Lollipop or not because I recently updated to that. Calls made when I'm out and using cell network have no issues.
Any advice would be greatly appreciated.
EDIT: Found out that another user is having the exact same problem. He posted a video on YouTube here:
https://www.youtube.com/watch?v=e2XXFyieDAg
Thanks
My wife and I are having the same problems. We also have complaints of voice echoes from whomever is calling. I hope T-Mobile fixes this.
fatduke720 said:
My wife and I are having the same problems. We also have complaints of voice echoes from whomever is calling. I hope T-Mobile fixes this.
Click to expand...
Click to collapse
I also have the issue with the voice echoes occurring for the other callers! Do you think it could be related to any of the apps we have on our phones? I'm not sure what steps to take to rectify this issue because I don't think T-Mobile or HTC will be addressing this problem.
I was able to resolve the issues with phone calls by performing a master reset.
Regarding the echoes, I was able to circumvent the issue by lowering the volume and not speaking that loud.
I received an email from an HTC employee regarding my inquiry about the bug and was told to try disabling the Ok Google Detection set to "enabled on any screen" and it seems to have fixed the issue!! Let me know if this works for others as well. Not sure if those of you who have done a master reset re-enabled that setting or not, but perhaps you can try enabling it and see if the issue occurs again. Hopefully this can be patched by either HTC or the Google app itself can be fixed.
I have VoLTE and Wi-Fi Calling turned off. Sometimes when I answer an incoming call quickly (actually that doesn't matter), I just get silence and I can't hear the caller and they can't hear me. I have to hang up and try again; Anyone else encounter this?
Update: I think I narrowed it down. Apparently the first call I receive after rebooting my phone always fails (unless I've made an outgoing call first). Subsequent calls work fine until my phone is powered down or rebooted, then the 1st incoming call fails again. I can reproduce this 100% of the time.
I've had this happen a couple times, funny thing is I've had it happen on my S4 and S5 as well.. Im starting to think its Tmo's network.
It might be a glitch with T-Mobile's network, but I haven't encountered it on previous devices. For example, I just switched from the Nexus 5 and never had a problem with voice calls.
I've had this happen a few times also with my S6. Never happened before, and I've been with T-Mobile for over 2 years.
This only happens for me occasionally if one of the callers is on Wifi calling, but it's happened with every phone (not just the S6) so it's definitely a network issue
I found this related to the S4, http://thedroidguy.com/2013/06/gala...ting-incoming-calls-66029#jMqaFVvIYCDRQHse.97. I've disabled the mute function in motions and gestures. We'll see if that works.
ledvedder said:
I've had this happen a few times also with my S6. Never happened before, and I've been with T-Mobile for over 2 years.
Click to expand...
Click to collapse
Been with Tmo for 5 years now and I have had this happen on previous devices.. could be the area I am... lol, I also notice a delay when making a call out which I believe is the network
Never had this problem on S4, but since getting the S6 this problem has been bugging me. Very frustrating.
Ok, I've got a problem that just started happening the last week or two. When certain people call me, I can answer. However my phone always hangs up on them 1 second after the call. The behavior is the same, based on the number calling me.
For instance, if my wife calls me from her cell phone (Sprint iPhone 5S), it will always hang up immediately after answering.
If my wife calls me from our house phone, it always works like normal.
This so far as I can tell, only affects inbound calls. I have no issues calling out.
Running latest OTA. I've updated PRL and profile, and it made no difference. I've never rooted the phone or messed with S-on/off. Pure stock. I have rebooted the phone into safe mode, and the same behavior is present.
Interestingly enough, I'm also on Sprint, I have a Nexus 6 and my wife a Note 4, and we've had the same issue over the past week or two. She can call me and immediately after answering the call will end. This has happened with her calling from her cell phone and her office phone, both of which are attached to her contact. I can call out with no problem, and I've tested calling my phone from different numbers and had no problem. No clue whats going on.
Are one (or both) of you using Sprint's Google Voice integration?
shawndoc said:
Are one (or both) of you using Sprint's Google Voice integration?
Click to expand...
Click to collapse
I am having the same issues when my mom (S4) whose on the same contract as me, calls me (S6 edge) it always hang up immediately after I pick it up. I have no issues calling her though. I am using Sprint's Google voice integration but I do not believe my mom is.
It is the Google Voice integration that is causing the disconnects.
See here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=first_post_notification#!topicsearchin/voice/sprint$20integration|sort:relevance/voice/NxkMd3YpzSw
I'm having the same problem with a Metro PCS phone. I've seen it elsewhere on line - it's some Android issue.