Has anyone else experienced this problem.
Although the phone shows it is connected to the Orange network quite often voice calls to the phone go straight to the voicemail, it seems that the phone is taking so long to process the call that the network assumes it is switched off and then diverts the call to the voicemail. a text then arrives notifying me of a missed call. Any ideas.
Incidentally I put the sim card back in my Artemis and everything worked OK
alanwesty said:
Has anyone else experienced this problem.
Although the phone shows it is connected to the Orange network quite often voice calls to the phone go straight to the voicemail, it seems that the phone is taking so long to process the call that the network assumes it is switched off and then diverts the call to the voicemail. a text then arrives notifying me of a missed call. Any ideas.
Incidentally I put the sim card back in my Artemis and everything worked OK
Click to expand...
Click to collapse
I too, seem to experience the same issue.. :\
It only seem to occurs after a while that the phone is in "extended sleep mode" (aka press the power key).
Now I'm trying a few things, I've switch the phone to GSM only network to see if THIS might be the issue... but if someone knows anything about this I'd be more than glad to be able to fix the issue
By the way my Kaiser is unbranded, the original HTC one!
You say you get a text re missed call, as opposed to a missed call notification. That would normally mean that the network couldn't see your phone - as normal internal missed calls (ie where you didnt asnwer) wouldn't send a text but would use an internal missed call counter.
So... do you have really weak 3g signal where you are and although the device thinks its connected, it isnt really?
Or is your device faulty...
unwired4 said:
You say you get a text re missed call, as opposed to a missed call notification. That would normally mean that the network couldn't see your phone - as normal internal missed calls (ie where you didnt asnwer) wouldn't send a text but would use an internal missed call counter.
So... do you have really weak 3g signal where you are and although the device thinks its connected, it isnt really?
Or is your device faulty...
Click to expand...
Click to collapse
Well I can say for me that the signal is always allmost full bars.
and I get txt msg saying either I have missed a call or that I have a new voicemail msg (Those are service provided by my carrier) So it's NOT "missed call notification" by WM.
So the network can't see your device when its trying to route a call to it...
Have you tried the device on GSM only? (settings, phone, band, change it from auto to gsm) to see if its a 3g network problem?
unwired4 said:
So the network can't see your device when its trying to route a call to it...
Have you tried the device on GSM only? (settings, phone, band, change it from auto to gsm) to see if its a 3g network problem?
Click to expand...
Click to collapse
Yeah that's what I mentionned earlier, so far it seems to be okay.
But what could cause this? The device switching between the networks?
I've got it as well, but I have to say I have experienced this on the Wizard also, and that's not a 3g phone. Also had it on the Universal, and that's why I used a Tornado for a year as it didn't occur on the smartphone version of WM5.
I had high hopes of such bugs being ironed out in WM6.
I use the power key to put it in standby, as I didn't want to leave the screen using power whilst it decided to go into standby by itself. Is this extended sleep/standby that I am activating the wrong thing to do? What should we do to get it into a light sleep?
Joe
joebongo said:
I've got it as well, but I have to say I have experienced this on the Wizard also, and that's not a 3g phone. Also had it on the Universal, and that's why I used a Tornado for a year as it didn't occur on the smartphone version of WM5.
I had high hopes of such bugs being ironed out in WM6.
I use the power key to put it in standby, as I didn't want to leave the screen using power whilst it decided to go into standby by itself. Is this extended sleep/standby that I am activating the wrong thing to do? What should we do to get it into a light sleep?
Joe
Click to expand...
Click to collapse
Well I dunno if it's cause by that, but this settings is located in the Power options of the setttings pannel... in the advanced tab you can tell it tu activate it or not and after how long u want it to *turn off the device* (which is what I call gently the "extended power saving")
Just spoke to Orange, apparently the 3G network went down yesterday this coincided with us getting the 3 tytn's so has probably made the problem worse. We were going to send the phone back under the 7 day return policy but have now decided to change them onto the gsm network as suggested by orange and see what happens when the 3G network re-appears.
I had the exact same problem with my Hermes on Orange about 14 months ago - just for a couple of weeks - as they were having network issues on 3g in my area.
3G masts are quite temperamental and if your local 3g provision keeps failing, they will replace them.
I haven't had any repeats of the problems for over a year.
The only annoying things about having to switch down to GSM are 1) no simultaneous data and voice, 2) slower surfing over GPRS and 3) you will get used to the massive battery life increase and switching back will hurt!
unwired4 said:
I had the exact same problem with my Hermes on Orange about 14 months ago - just for a couple of weeks - as they were having network issues on 3g in my area.
3G masts are quite temperamental and if your local 3g provision keeps failing, they will replace them.
I haven't had any repeats of the problems for over a year.
The only annoying things about having to switch down to GSM are 1) no simultaneous data and voice, 2) slower surfing over GPRS and 3) you will get used to the massive battery life increase and switching back will hurt!
Click to expand...
Click to collapse
Just now I had a second round of this problem at work, and I had the same thing yesterday here. Very f***ing frustrating and since the primary function of a phone is to make calls, it's particularly ****e that it doesn't do it well.
No calls and only one out of 6 SMS's were delivered. I had to do a soft reset and then I had two voicemails and 5 unread SMS's pop up.
If the calls/SMS's were retrieved after a soft reset does this mean that it's the phone and not the transmitter? I use my phone for work and this is becoming a real problem.
I can foresee this phone being off to HTC for 'repair' getting a new unit, flogging it and going back to WM smartphone edition.
No - it sounds like a network issue.
Switch to GSM for a week. Then switch back and it should be fine.
unwired4 said:
No - it sounds like a network issue.
Switch to GSM for a week. Then switch back and it should be fine.
Click to expand...
Click to collapse
Yeah, I did some searching on the subject and saw it occurred on many different WM phones, and switched it to GSM only.
It didn't fix it, and it simply wouldn't ring. I checked by calling from a colleague's phone and it displayed: 'warning active call divert on' or something like it.
I was most pissed off, as per my previous post.
When I got home, I activated (via network codes) call divert to my car phone number, then sent the cancel network code to deactivate it.
Tested via home phone and it rang. It was active (screen on) and rang withing one ring on the home phone. So I pressed the power button and tried it. Same result, imperceptibly slower if it was slower.
I work in a pre-fab unit made from corrugated steel on top of a hospital (obviously some sort of rapid office space 'solution'), and whilst I get 2 to 4 bars of 3G in there, and seeing the issues whilst on GSM only, I am totally and utterly confused as to the cause of the problem!
The Kaiser is however, on probation. For now
Cheers,
Joe
joebongo said:
Yeah, I did some searching on the subject and saw it occurred on many different WM phones, and switched it to GSM only.
It didn't fix it, and it simply wouldn't ring. I checked by calling from a colleague's phone and it displayed: 'warning active call divert on' or something like it.
I was most pissed off, as per my previous post.
When I got home, I activated (via network codes) call divert to my car phone number, then sent the cancel network code to deactivate it.
Tested via home phone and it rang. It was active (screen on) and rang withing one ring on the home phone. So I pressed the power button and tried it. Same result, imperceptibly slower if it was slower.
I work in a pre-fab unit made from corrugated steel on top of a hospital (obviously some sort of rapid office space 'solution'), and whilst I get 2 to 4 bars of 3G in there, and seeing the issues whilst on GSM only, I am totally and utterly confused as to the cause of the problem!
The Kaiser is however, on probation. For now
Cheers,
Joe
Click to expand...
Click to collapse
Hmmm really weird! keep us posted on your experiences
Running stock rooted. Does anyone else on Sprint notice that it takes sometimes up to a minute for SMS messages to send? I have this issue regardless of location and signal strength. Happens on both the messaging app and hangouts.
There's a few threads touching on this topic. But there is an issue with the LTE/3G/1X hand off. So you either take a long time to send texts, or send multiple duplicate texts etc while on LTE. Some people also miss phone calls while on LTE.
The only work around is to put the phone on 3G. But of course that sucks. We're all awaiting Sprint to make some change on their network.
I recently changed to H2O, which is an AT&T reseller for those who are unfamiliar, and I'm having a very peculiar problem.
When I go to make a call, as soon as I tap the green button to make the call, sometimes my signal drops to 0 bars and I can't make the call. Sometimes this happens repeatedly and it's impossible to call anyone. But sometimes the call will go through after the 2nd, 3rd, or 4th try. However, sometimes it drops to emergency calls only after the call fails, or sometimes it drops to no service.
Additionally, when I go to change the conditional call forwarding under dialer - settings - calls - call forwarding, as soon as I tap call forwarding, the signal bars vanish and I get a call settings error. This happens almost all of the time. And again, sometimes it will drop to emergency calls only, or a several times I've had it drop to no service.
When I give up trying to make a call or change call forwarding settings, the signal strength will return after a minute or so, which is currently fluxuating around -112 dBm 28 asu, -116 dBm 24 asu, 110 dBm 30 asu. Not sure what any of that means though.
Frequently, incoming calls do not reach my phone. Often I'll get a text message asking me why I'm not answering my phone, but it never rang. There's no indication that my phone was out of service as there is always at least one bar.
I can send text messages with no problem at all. My data also works just fine. In fact, one of my friends gave up calling my phone number and instead calls me on WhatsApp because that's the only way he can get a hold of me. He would call my number, have it fail, and then immediately call me on WhatsApp and that goes through because my data doesn't usually have any issues.
I've tried changing APN settings according to different information I got from H2O. I've tried changing the preferred network type to 3G and 2G. Changing to 2G seems to help my ability to make calls, or maybe it just seemed that way. I've contacted H2O numerous times about it. They opened multiple tickets on it and finally said that there's no problem on their end getting service on that sim card. I sorta verified this because the sim card doesn't display this problem in my 1st gen Moto X, an XT1053.
Two other people in my house are on the AT&T network, one on Cricket with a Galaxy S6 (G920AZ), and one on H2O with a Galaxy S3 (T999) and they never have any issues here at home or elsewhere.
My phone is an XT1095 pure edition. I run stock 6.0, 24.11.18.victara_tmo.tmo.en.US, kernel 3.4.42-g389e46b, rooted, TWRP, with no apps that modify call behavior except Google Voice which is set to never use GV to make calls. This phone worked flawlessly on several different T-Mobile resellers. I'm about to switch back to another T-Mobile reseller but I thought I'd post here about this strange issue first because I don't want to always be limited to the T-Mobile network.
Any advice or input is greatly appreciated.
Hello,
I need help diagnosing whats going on with my HTC desire 626s. The phone is unlocked, rooted, and has TWRP installed.
Problem: I can't make calls while I'm at my home. I have excellent signal strength being I'm within visual range of the cell tower.
The phone has always worked at my home in the past then about a two months ago I wasn't able to make or receive calls. The internet works fine, and texting works fine. When I try to make a call nothing happens then there is a beep and the phone says call ended. This is an unlocked phone on att go phone service. After this issue started I called att and created several trouble tickets and every time they state the service is working fine. When the phone was working normally during calls the 4gLTE indicator would swap to 4G and make calls on an hspa network. After att was unable to fix the issue I bought a new sim card. For a month I was able to make calls just fine but then on Halloween night the problem came back. I highly suspect that someone is blocking my ability to make and receive calls. I need help from someone that knows more than me on how to diagnose exactly why the calls are not goign thru. I really need help. I have swapped the sim card into a new phone was able to make a call or two then the service was again unable to make or receive calls. I just need help on how to diagnose exactly whats stopping the calls from going thru. Thank you.
PS. Another att go phone works in the same location that mine does not so it is not a issue of the walls blocking the signal.
I am getting calls that go straight to voicemail. This does not happen all the time, but when it does there is no call log, just a voicemail notification. Searching the web and support calls to T-Mobile seems to indicate that it is because the Mate 20 Lite does not support VoLTE, even though the phone has the band support. When a call comes in, T-Mobile will try and drop the call from LTE to 2G/3G, fail and then send the call straight to VM. Cannot find a solution and it seems there are many people having this issue across many different brands of unlocked phones on the T-Mobile network.
Here is the odd part and why I think it might be the phone. I am getting insane battery life on the Mate 20 Lite. I charged the phone to 100%last night, went to bed and 8 hours later it was still at 100%. Last night I missed an important call that went straight to VM. No forwarders, call blocks, airplane mode etc. I also noticed that these straight to VM calls happen when the phone has been sitting/immobile for a while. Like the aggressive battery management is killing some service. This does not happen with a Xiaomi A2 that my wife is using.
BTW, I am connecting to band LTE band 4 and get near 40Mbps down when testing, so I assume I am getting 4G LTE.
The phone is still within the return window and if I cannot solve this, I have to send it back.
Anyone have a solution?
No solution. I have a similar problem where I live there is nearly no cellular reception and the only way to get calls is to be connected to WiFi which activates VoLTE / Voice over WIFI. Huawei Mate 20 Lite does not do it though. Why not?