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
Related
Guys,
When I got my P3600 some weeks ago I didn't experience any problems with problems with calls dropping. But ever since I've upgraded to WM6 I am experiencing this problem... the calls drop at random, sometimes I can talk for hours without any disconnect, and sometimes the call drops and I cannot even call the person back... And even after downgrading to the shipped rom, I still have this problem... That made me wonder if maybe I have had problem when I got the device but at that point I was just lucky not to have calls dropping.
Yesterday was the last time a call dropped on me. I couldn't call the person back, the phone didn't establish a new connection. When I finally got the person back on the phone (2 minutes later) he/she said that the whole time she thought I was driving through a tunnel and that I would reconnect because... I stayed connected at the other phone... After 2 minutes, she said, the connection was finally broken and that's when I was able to call again.
So sounds to me that windows mobile disconnects me and that the operators network still keeps my number connected.
Well, needless to say, I want to fix this issue. I have a 3G Vodafone NL subscription but I read that 3G could be the cause of my issue. so I've just disabled 3G. Now I'm just running on GPRS... Which isn't how I want it to stay. Any ideas, same experience/ pointers how to solve this?
Thnx. Arend
Reply from HTC
This is the reply I got from HTC:
Try to remove it off 3G go to settings / phone / band - then select GSM from the top drop down menu.
Should now reset.
If it comes up with an error, turn on flight mode then do the above again.
Click to expand...
Click to collapse
So based on this reply it seems that 3G might be causing my issue.
I replied to HTC:
I have followed your instructions but now I can only use gprs... but I have a 3G subscription with my provider. So even if this workaround works, it's not to my satisfaction.
Pls advice.
Click to expand...
Click to collapse
I'll post their reply.
Further, if someone has more info on the subject please let me know.
Same problem here...
No issues before upgrading to WM6. Sometimes the call drops out after a few minutes, sometimes a few seconds, and sometimes already after a few rings. The other day I had to make a call 5 or 6 times to finish the conversation - very annoying...
I'm running the first official Australian WM6 release for Dopod/HTC, i.e. the one that got pulled off the web for a while. Possibly going to the newer release of the ROM update solves the problem? Even though I think both versions run on the same radio ROM.
I've used the same rom as you to upgrade to WM6. But in my case, even when downgrading to the shipped rom, I still had calls dropping. And like you, sometimes after minutes, seconds etc.
Still having no drops since I have turned 3G off. But I just wanted to look something up on the internet... took minutes to get the info on my screen with GRPS, so it's not much like a solution.
This is the reply of HTC:
Dear sir,
Regarding your situation with the device , I would suggest you, to? resolve your issue with the network coverage ,to practice a hard reset on your mobile with the following step:
START -> Setting->System->CLEAR STORAGE and follow the procedure, if you have already done this manipulation , I would direct you? to this service and check the right number on this area with your network ush the green button to call->then go to menu-> option ->Services->select the on the following list ->Voice mail etc-> and then get setting -> and check that the number is right with your network provider.
Click to expand...
Click to collapse
Needless to say, but I'll say it anyway, I have performed hard resets... indeed, multiple
The second action they adviced, sounded a bit strange to me. But when I retrieved the settings I saw that there was no number filled in for voicemail. So I've entered 1233 (Vodafone NL voicemailnumber).
So maybe the last action has nothing to do with my issue, but who knows.
So now I am running again on 3G. I'll keep y'all posted.
Just checked it on my device and there is already an entry under voice mail. So I severly doubt that it has anything to do with the voice mail settings, too.
No, I guess you are right.
Further, since I am running 3G my signal I noticed my signal is weaker then running GPRS-only. My calls have not dropped since but I do get complaints that people sometimes cannot hear what I say because my line goes dead, and a moment later it's back again.
I've got another reply from HTC:
---
If a hard reset didn't solve the problem and the problem only occurs when switching to 3G, than this can be caused by the following;
1. Problem with the device.
2. Problem with the network, ???
I would suggest to test your SIM in another HTC device with 3G and see what happens. If it happens again than it is a? problem with the network. If it works with that 3G device than it could be a faulty device. The experience is that it is related to the 3G network himself. If it is a network issue, than you can ask them to deactivate the 3G/HSDPA.
We can't find this out for you in the UK, you need to see if you could determine the problem yourself.
---
Thus the support of HTC.
So now I have written an email to vodafone. I'll keep you posted.
Same problem !
Try to flash your device with ROM_Radio 1.41.00.11,
Friendly
Barichon said:
Same problem !
Try to flash your device with ROM_Radio 1.41.00.11,
Friendly
Click to expand...
Click to collapse
Ok... but I'm somewhat confused... are you experiencing the same problem with 1.41.00.11? Or did you solve the problem by flashing to 1.41.00.11?
2----> solve by reflashing with 1.41.00.11
Ok, I've upgraded to 1.41.00.11.
So far, I've experienced no calls dropping on me.
Nevertheless, I've also made a phonecall to Vodafone explaining the issue. They acknowlegde the issue... SAY WHAT?!! Yes... they acknowledge the issue and recommend turning the device to GRPS only. WHAT?!!.. Chill, they can at least try that, who knows, maybe I would have said yes.
So, I explained GPRS only is not an option since it is a tiny bit slower then what I am paying for.
They've put the call through to their 2nd line and keep me informed. So as soon as I hear something I will get back to you.
ps. What I found very great is that they did not cut it off with "Ow, you are using the HTC P3600... I'm sorry, we do not support that device." Vodafone NL, keep up this great level of support!
Ok, so far I've heard nothing from Vodafone. And so far I have had one call that dropped. So although that is a huge improvement, it still sucks.
So... now what? The way I see it:
1. I want to have fast internet on my PDA (3G), so only GPRS is not an option
2. There are problems with the 3G network which make calls drop every now and then
3. Vodafone isn't going to fix this in a short period of time.
So the question is: what is more import to me: 3G or a reliable phone connections?
The answer is: reliable phone connection.
So I will switch my network to GSM instead of auto and when
I really need fast internet I will switch to 3G.
Case closed... well, not really... but still, case closed.
Hi
I think is not the operator problem and could be the phone problem, I am using the D810 in Singapore with Starhub and have the same problem with drop calls once I use 3G network. If I switch to GSM only than is perfect no drop calls and calls quality improve also.
So sad having a 3.5G phone and can't use 3.5G service
Could be, but HTC and Vodafone confirmed me that it has to do with the 3G network. And I do not want to know the technical details about all that so I'll leave it at that.
Hi,
I have a V1615 from one of our users which has a bit of an unusual problem in the while trying to connect to GPRS/3G the following message appears after a minute or so of trying:
The answering modem has disconnected. to check your connection settings and change them if needed, tap Settings
The voice function is also odd as while trying to call somebody, you wait awhile and then get three beeps and it hangs up. The signal strength mostly show no signal, but even when it does, the chance of getting through seems poor.
The problem is, this was happening when the device had WM6 as the O/S, I upgraded to WM6.1 from the voda website, and the same issue has occurred from the fresh install. The SIM works fine in another device, and the device still fails to work with a known working SIM in it.
Vodafone have taken all the services and re-applied them to the users number in case there is a server problem, this hasn't changed anything.
I would be inclined to think it's a faulty device - except that this is the second device the customer has had with exactly the same fault. The last one was changed a month ago and it seems to be happening on a monthly cycle as he's only been issued the device for two months.
Anybody any ideas? I know the user well and know he's careful with kit (& I don't think he has any significant magetic field that could cause this problem!! ).
Just seems odd that two devices with the same user has the same fault, despite fresh installs of the OS!
Cheers in anticipation.
Mike
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?
So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?
I am having the same problem. Started on 5.1.
Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.
darek65 said:
Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.
Click to expand...
Click to collapse
Not sure about OP, but in my case the numbers I'm pressing show up as being pressed on the screen, but they don't register with the call itself. When I try to call my voicemail I have to push a number several times sometimes to get it to actually register. I may see "3333333", but only the last one actually registers.
I don't use a screen protector. Also like the other guy said, the button is being pressed, I turned on dialpad sounds to be sure.
Same problem on 5.1.
Sent from my Nexus 6 using Tapatalk
Are both of you that are having the same problem on stock? Figured I would submit a bug report if no one has a solution, just want to make sure someone has tested it on stock first.
I had the problem on the stock T-Mobile OTA. I was rooted and unlocked, but otherwise stock.
Stock rooted 5.1M
Sent from my Nexus 6
Same issue. Stock ROM. Franco kernel.
Stock 5.1 Franco Kernel. Same issue. Anyone getting anywhere with this. I've tried changing the DTMF from normal to long, and tried touch sounds on and off, which seems to be the only "fixes" mentioned in various places.
Eetabeetay said:
So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?
Click to expand...
Click to collapse
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?
devilsmack said:
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?
Click to expand...
Click to collapse
Verizon Here
Fixed issue by turning off VoLTE. So that sucks. Turned it back on after I was done activating the card I was trying to activate.
Does switching to long tones do anything? I've had this problem since 5.1 and am on Verizon with VoLTE.
Same problem here. Have had it across multiple versions of Chroma ROM (includes Franco kernel). VoLTE on means no DTMF, VoLTE off makes DTMF work perfect. Have seen references to similar problems on other phones and other networks.
New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.
OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.
stevemw said:
OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.
Click to expand...
Click to collapse
LMY47Z fixes this on Verizon as well. I was having to wait a full second between numbers (which was a pita since I dial into a lot of conference calls every day)
swamp2 said:
New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.
Click to expand...
Click to collapse
Unfortunately the new M (preview) radio fixed this but also does not permit conference calls. The 5.1.1 Tmo OTA radio maintains this fix but also permits conference calls. Specifically, this one:
LYZ48E (5.1.1 T-Mobile - Extracted from OTA - 05/23/2015)
MDM9625_104649.09.05.14R
I've had an ongoing battle with my ability to make calls/text with this device, I initially thought it was at the carriers end but I was perplexed because my SIM works fine in other devices and they are unable to find anything wrong.
Last night I opted to try a full factory reset, I had already done multiple prior in an effort to find a resolution but this time I opted to do it without immediately connecting my phone to WiFi during the setup portion. What I found was two things, all the texts that had failed to come in did and my talk and text was now completely usable. Also the ZTE Locker, which is ZTEs embedded lockscreen wallpaper app was now functioning again. Prior to this it had stopped working and was stuck on one static image (it is suppose to change the lockscreen wallpaper every time you turn on the screen on your device and the images update everyday over Wifi). Unfortunately as soon as I connect my phone to WiFi without any notification I believe the phone does some form of update as within seconds my phones ability to make calls/text breaks along with the ZTE locker. I have attempted to disable any auto updates under the system updates in settings before connecting to Wifi, but unfortunately that does not work as it does not appear to be a full on OS change. Is there any way to disable any updates that are not manually approved when I connect to Wifi? I have reached out to ZTE support and they have escalated the issue to their senior R&D team. However I don't want to wait until a new update before I can have a functioning phone.
Just as a note, the issue appears to be particular to 3G calls (although I am not sure why I am failing to receive some texts). In Canada our carriers do not enable VoLTE with phones that are pretty much not Samsung/Apple or have been bought directly from them. Because of this any out of market phones like One Plus and ZTE that are unlocked and compatible only get calling through 3G, which is normally fine. I can get VoLTE briefly if I put my SIM in a carrier approved phone and switch it to my ZTE and it appears to work (until my carrier recognizes the IMEI and blocks it). So this may be why not everyone is experiencing this issue (if they have VoLTE). Anyways any help would be greatly appreciated as I am at my wits end.
I'm in the USA and have had zero issues on T-Mobile, but when I got the phone I had to manually put in the T-Mobile APN settings to make sure everything liked texts and data worked correctly. I have many T-Mobile devices so I know exactly how to set the APN. Are you sure that your APN is set correctly for the network you are on? I know that most phones set the APN according to the sim card you insert, but I have found many Chinese phones that DON'T. Once I set it manually that usually solves all the problems.
Also, how did you reach out to ZTE support? I'm trying to get ahold of them to give them feedback to DISABLE the obnoxiously loud camera shutter sound in the next software update, but aside from spamming their Facebook page, I don't know how to get ahold of them.
Thanks for the reply, oddly there is no option on my Axon Ultra to add APN settings. Only the default ones are available, although they do look to be correct for the most part I would love trying to add them manually. Someone in another forum who was also having issues (with another Canadian carrier) spoke with a rep and they stated that they would be releasing an update shortly with the manual APN option. My data and MMS appear to be working fine however so I am not too optimistic that will be the fix. You can contact ZTE on their website, if you go to their contact page you will see a little pop on the bottom right hand corner for chat. In reality it is mostly a messaging service as it never appears to be actually online but they do appear to be respond somewhat promptly to message sent via email. Just as a heads up, I don't recall specifically where I think it was a review but I do believe they have made a statement already saying they will patch out the loud shutter sound.
May I ask if your phone works fine with VoLTE disabled? Unfortunately since all non carrier approved devices are denied VoLTE in Canada my main experience has been with 3G calls failing.
I'm in Finland. Having so much problems with call's that i can't use the phone. Problems answering call's and phone also keeps cutting call's. I sent mail to Zte support. Probably have to wait for update and hope for the best.
Hey, they released an update today. It now allows you to input your own APN settings manually. Look up your carriers and add your own. Even though the automated ones were right making my own manual ones has fixed the issue for me it seems.