I have the International Note 5 (SM-N920C) with the Carrier T-Mobile in the U.S, I have had this Device for Over a year now and it always worked flawless, ever since T-Mobile started implementing changes to there System my Calls go straight to voicemail when anyone try calling me, also, when i try making out going calls it takes close to a Minute before i even here the phone start ringing on my end, its weird cause this never happened, and it not my device either, i called T-Mobile and they couldn't help me, Hence, I went on Vacation to Myrtle Beach and toke my Note 5 with me to see if it worked out there (I live in Brooklyn NY) and yes, of Course it started working Flawless again, Im writing this Post in HOPES someone can help me, I have Tried Many Custom Roms and CSC zips to No Avail, Im hoping someone out there went through what Im going through and Found a FIX, thanks in advance, Bless to everyone.. One Love, All we Have is One Life.
I'm having the same issues you're having. I recently switched over to TMobile with a SM-N920C. It takes a while to dial out and some calls are going to voicemail without even ringing. I'm in Jersey City so maybe it's something they're trying out in more congested areas.
I haven't tried any custom ROMs or kernels but I was wondering if it had something to do with Voice over LTE not being supported by the phone out of the box. Have you tried any VoLTE capable ROMs/kernels?
Hey S.G, first off, i got a Kick out your User Name, on another Note, i tried Various Custom Roms and Custom Kernels that allow me to turn on and Off VOLTE, nothing Worked, Like i mentioned in my post, i went on Vaction to South Carolina and my device worked Flawless like it should be working now, I Called T-Mobile and they couldn't help me, all i could ask is for you to also call tmobile to let them now its an issue on there end with the international devices, Now if they get enough calls from different ppl they will have no choice but to fix the issue, Ill do the same... Thanks for reaching out though. This really sucks cause i love this device.
Hi. I have exactly the same issue in NYC... Did you ever find the solution for your Note5?
Related
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?
Hey, guys. You may have noticed me lurking around these parts of xda, clicking thanks to many posts and not posting myself etc. It's because my main phone's not an Ri, but I've been a fan of xt890 for a long time, so I made two of my family members get them. :victory:
However, one of them is making problems. It's the white one, the one that my mom uses. She's having issues where in-call something would go wrong and the person she's talking to would not be able to hear her anymore. At first I thought it was due to the low 3G coverage where we live, making the call bug out while the phone's switching between 3G and 2G networks, so I switched her phone to GSM only mode, but it started happening again. I've experienced this in calls with her, so I know she's not making things up or anything like that.
The phone is running stock JB, has not been unlocked and is still in warranty. But before taking it back to the shop (where it's likely to spend a month or so), do you think there's anything I could try? I already did a factory reset once, it didn't help. I'll try reflashing her firmware with RSDlite one of these days, but I'm not even sure whether that reflashes the radio/baseband stuff?
Any hints would be greatly appreciated!
Cheers
In the last few days I've had at least one dropped call per day on my S6. It doesn't make any difference if my recipient is on a cellphone or landline nor does it matter if I'm in the car on bluetooth or using the handset elsewhere. I did some searches and found others having the same problem, not so much with AT&T (mine) as opposed to Verizon and T-Mobile. Some say a factory reset cured the problem, but I hate to do it unless I have to. Just curious how others on AT&T are faring. My previous S4 never dropped any calls nor did my HTC M7 so I'm thinking it's not a network issue, but something in the phone itself.
I've never had a dropped call in the month I've had the device. I had my chubby cheek hang up on my mom once last week, but that's as close as it gets. My area gets pretty good coverage for att and tmobile though. I've yet to drop a call since joining at&t
My Black Galaxy S6 Edge 64gb module was dropping calls like crazy, and was still within my exchange period so I switched it out. Haven't had any dropped calls since.
Call and connection quality have been stellar for me. Only dropped calls I've had are when going through known dead spots.
Looks like the factory reset fixed it for me so all is good now.
rmc69 said:
Looks like the factory reset fixed it for me so all is good now.
Click to expand...
Click to collapse
Have you had any dropped calls since your last post here? I'm having dropped calls often. I don't think a factory reset will help me because I wiped all data before flashing the rom I'm running. I may try a factory reset from within the settings menu if you haven't had any dropped calls since the 15th.
I've only had a couple dropped calls since then, but my problem now is that sometimes the other caller can't hear me, specially when I'm driving and on bluetooth through the car audio. It can't be the other caller because they were on a stationary, land-line phone. I checked out my mic by making a voice recording so the mic is fine. I just tried unchecking "Enable HD LTE Services" and I'll see what that does and report back. If it were not for the very nice camera, the annoyance of the dropped and muted calls plus the bad battery life would be enough to make me switch this phone. It's got to be a device-specific bug. My HTC M9 is running Android 5.0.2 and is rock solid and never dropped a call. Same with my LG G3. I would send in my S6 for repair, but I'm not sure what they would do. Not only would I get a refurb back, but it might do the same thing. If you've been following the threads, you might have seen that Sprint had to push a special update for it's S6 customers to fix dropped calls. Verizon customers are also having it bad (I'm on AT&T). It can't be all network issues though as like I said, my other devices including an LG G3 have never dropped a call.
Thanks for the response rmc69. I did uncheck the HD lte and it did not help me at all. Let me know if you have a different result. Thank you
The Sprint S6 and S6 Edge have the same problem. I have to turn off the LTE radio all together to have a usable phone. I couldn't send/receive text, I had dropped calls and a very poor signal. Once I turned the LTE radio off, all those problems went away. I realize this is not a fix but it's a workable bandaid for those that are having problems. Good luck to you guys.
Turning off lte did not work for me.
Robert, how did you turn off LTE? By going into the testing mode and changing it from there? Or were you simply referring to unchecking Enhanced LTE Services?
I think I figured it out from this thread, at least for AT&T
http://forums.androidcentral.com/samsung-galaxy-s6/518691-any-way-turn-off-lte-data-galaxy-s6-t-version.html
rmc69 said:
I think I figured it out from this thread, at least for AT&T
http://forums.androidcentral.com/sa...ay-turn-off-lte-data-galaxy-s6-t-version.html
Click to expand...
Click to collapse
I tried that, it did not work for me.
Sorry turning off LTE still didn't help. I guess the only alternatives now would be to wait for 5.1.1 and see what it fixes, or you may just consider asking for a replacement.
Sent from my SAMSUNG-SM-G920A using Tapatalk
rmc69 said:
Sorry turning off LTE still didn't help. I guess the only alternatives now would be to wait for 5.1.1 and see what it fixes, or you may just consider asking for a replacement.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Yeah that is what I'm afraid of. Every time I go to the at&t store it's a big hassle. Hopefully an update will fix our problems.
@rmc69, is your phone rooted and running a custom rom?
No; pure stock. It's also a 64 GB model. I'm wondering if there is a difference that could affect reception, i.e., is the antenna placement exactly the same. I changed my band to GSM Auto last night removing LTE and so far, I haven't had any dropped calls, but it's too early to tell. The biggest problem I'm having is that sometimes callers cannot hear me, especially in the car using bluetooth.
I am rooted running DennisRom. Yesterday I did a factory reset via the stock recovery and made 4 calls and did not have 1 drop. I'll see how it goes for a few days and report back.
Great! That's encouraging.
Bad news, I just called my wife and the call dropped before she could answer her phone. I think I may give up and get a different phone. I'm loosing hope.
Hey guys, Basically I live in Ireland and bought my friends nexus 6 when he got a new phone.
It was working great and I rooted 5.1.1 and when I saw The (only android 6.0 available) marshmallow update available on NRT I dirty-flashed it, after seeing a thread on reddit saying dirty flashing to marshmallow hadnt caused them any device defects
Had no complaints until I tried to call my sister today (admittedly the first call id made in the first two weeks of owning the phone) and it said "Sorry you don't have access to the service"
So I played around with some reboots and sim reinserting and was surprised to see that when I changed to 2g Mode, It could make the calls! Really strange, is there any chance that the marshmallow image released on NRT would've had bands specific to US carriers?
I can make calls via whatsapp for the time being I guess Lol, but if anyone could give me a headsup as to what I did wrong ( or even a solution) Id be pretty grateful!
Thanks,
Nick
wipe data/system then flash again. you should never dirty flash between 2 different android versions. and dont listen to anyone else, i bet they do have issues.
Thanks for the help but sadly this didnt work for me at all!
Was playing around last night after I reflashed and I went to system apps and on seeing telephone and phone (two seperate apps , normal?) I disabled 'phone' for a second and could place a call successfully over 3g - but obviously with no dialer interface whatsoever because the app was disabled. Ive rooted and custom flashed alot of my phones but this has me puzzled
I had this problem on a previous phone. What happened is that it was stuck on LTE only. I know this phone has volte, but try messing with mobile connection
Got today's update BQJA AT&T Note 8. Update completed and my phone came back fine.
After an entire day, I realized that I'm not able to make or receive calls... I'm so frustrated.
Anyone else having this issue?
Please help.
It may not be the update. My family down south has been having problems all day on AT&T. Family and friends up here in the Ohio valley area have had same problems. I think AT&T is having large-scale network problems. Didn't they have some across California last week?
why wouldnt you just call ATT and ask them to fix it for you???
AT&T just released a press update an hour ago telling everyone to restart their phones to make calls now.
I didn't get an update but I was not able to make calls so I rebooted. But now I don't have VOLTE.
Issues with towers. I work for att and have had customers coming in all day with calling problems still not sure what exactly the problem was or is.
Thanks all... As that night progressed, I did find out that it was indeed AT&T network problems nationwide. I attempted several restarts. One finally took and my phone is acting normally now.
Thanks again.