after i did all the updates. (dcd new rom , 3.27 radio, gps finder, tomtom, vista phone dialer and the htc home plugin) i have trouble making a call.
It will just stay in the dialing screen and bam! call ended......its doing this so opften that i just spent a half hour tring to make a call..........no luck.......
i usually have 3 bars but sometimes 2 but that was always good enought before.
I've had this problem a few times as well.. even more often, I make a call and it calls out, but I have no audio (I can't hear them, they can't hear me). A soft-reset always fixes both these problems.
taxilian said:
I've had this problem a few times as well.. even more often, I make a call and it calls out, but I have no audio (I can't hear them, they can't hear me). A soft-reset always fixes both these problems.
Click to expand...
Click to collapse
thats not my prob.....my prob is the call wont get connected period it says dialing then goes straight to call ended.
have you tried a soft reset? that fixes it for me.
sure would be nice to find out what causes it, though.
(I meant that I have both the problem you mention as well as the other variation, each in its turn)
you need your msid number
authenticsketch said:
you need your msid number
Click to expand...
Click to collapse
nope i dont
Related
I've been trying to solve some intermittent probs with messages that may be due to radio probs or possibly probs with handcent SMS.
When using the quick reply usually the message appears to go then a few seconds later I get the red triangle telling me message not sent. If I then resend, the message goes without an alert, but it appears it doesn't get to the recipient, even though it shows still in my thread.
Just wondered if anyone else has had similar probs, with or without Handcent
I have also been experiencing probs like the number being "unavailable" to folks calling me when I know its not, and with calls dropping out
So I had been asuming it was possibly a radio glitch, and swapped from 2.3 to 2.2 MCR, then changed my radio to 6-18EU and then to 5-31BU and I'm currently on 5-15U which is seeming the most stable.
I'm on TMOB in UK
Dayzzz xx
Dayzee said:
I've been trying to solve some intermittent probs with messages that may be due to radio probs or possibly probs with handcent SMS.
When using the quick reply usually the message appears to go then a few seconds later I get the red triangle telling me message not sent. If I then resend, the message goes without an alert, but it appears it doesn't get to the recipient, even though it shows still in my thread.
Just wondered if anyone else has had similar probs, with or without Handcent
I have also been experiencing probs like the number being "unavailable" to folks calling me when I know its not, and with calls dropping out
So I had been asuming it was possibly a radio glitch, and swapped from 2.3 to 2.2 MCR, then changed my radio to 6-18EU and then to 5-31BU and I'm currently on 5-15U which is seeming the most stable.
I'm on TMOB in UK
Dayzzz xx
Click to expand...
Click to collapse
It seems there is a few issues.
I have confimed instances of not receiving incoming calls at random intevals, I cannot pinpoint what is causing them. People say they have been trying to ring me and its just going to voicemail. I tried it myself randomly and 1 in 10 times it would not ring, no reason, had full signal!
As for SMS, I do get (quite low) occasions where a text wont sent, but when retrying it sends straight away, not sure why this is.
I've also had issues when trying to ring someone, my phone will just hang up and not even get to the point of ringing / going to voicemail. This can happen about 5-6 times before actually getting a ring out.
I've tried all the radio's available and they all seem to be the same. Pretty poo as I use the phone for business and I cannot afford to be losing calls.
I'm on o2 uk and always have my mobile data on, not sure if this could be causing it.
Yes, I get that, and on occasion emails not sent. But assume that comes down to the not great signal of the phone. Also, the SMS can freeze on occasion and you have to wait before you can slide through the individual users messages to look back.
Hi,
since I'm having the same kind of issue and got answer from support an relatives, maybe if you follow that thread we'd all get the answer we need
http://forum.xda-developers.com/showthread.php?t=570436
I am having similar issues using the standard messaging app. I have also noticed more recently that I find my handset with no signal for extended periods, I often have to restart to get the signal back.
White hero, official latest ROM on O2.
i'm the same
Dayzee said:
I have also been experiencing probs like the number being "unavailable" to folks calling me when I know its not, and with calls dropping out
Click to expand...
Click to collapse
nicelad_uk said:
I have confimed instances of not receiving incoming calls at random intevals, I cannot pinpoint what is causing them. People say they have been trying to ring me and its just going to voicemail. I tried it myself randomly and 1 in 10 times it would not ring, no reason, had full signal!
...
I've also had issues when trying to ring someone, my phone will just hang up and not even get to the point of ringing / going to voicemail. This can happen about 5-6 times before actually getting a ring out.
Click to expand...
Click to collapse
I have exactly the same problems with stock radio on T-mobile uk so it seems its a problem with the phone rather then particular network if it appears on o2 as well... its quite annoying to be honest where someone is trying to reach me and it goes straight to voicemail 5 times in a row and I know that my phone has been on the desk all the time with good signal..
for t-mob uk try the 07-08 radio
ive got it and it works prety well
http://android.modaco.com/content/h.../09-10-hero-roms-radios-in-update-zip-format/
I already have 07-08 radio!!
i occasionally dont receive txts til about an hour after they are sent and sometimes the same person has problems calling me also on a rare occasion it says number not recognised when i call them back.
very strange and even more annoying as its my gf's number it doesnt like lol.
radio 07.08
UK T-Mobile
Hi all,
Looking for a bit of help/advice.
On occasions, probably between 1-3 times a day, when I try to make a call on the Hero, the call appears to look like it is dialing out but it just sits there saying 'dialing' but never connects to the destination which can be any UK number / Orange 150 etc. Either rebooting the phone or leaving it for 10 mins or so fixes the problem, but it does become annoying!
At the same time as this happening, when I try to send an SMS, I get the error 'SMS not able to send' in the notification bar. Again, I have to keep trying and it sorts itself out.
A final problem and I am not sure if it is related or not is I have had numerous people try calling me at various times, my phone doesn't ring or display a missed call, nor do I get a missed call SMS but the person who tried calling me said the line was actually ringing first and then went through to voicemail. I have witnessed this myself by calling my phone, getting a ringing line but the phone doesn't respond?
Any ideas of help would be appreciated. This problem has existed on Modaco Roms 2.2, 2.8 and 3.0 - I'm on Orange UK.
Thanks,
Nick
I have the same problem with the Orange Poland. When I logged on to the 3G sometimes you can not call or send SMS. When I switch to the 2G network problem disappears.
Yeah, it is strange, I have done that too, turn off the 3G to 2G and back to 3G which sometimes cures it, but not all the time.
I've tried various things, made sure the apps aren't closed with Taskkiller or anything like that. There is no specific time or occasion it happens, it just does now and again.
Well I have tried everything. I recieved all the settings from my operator , changed over 10 ROMs and gone back to the original too, i tried what you said to turn 3G off , i reset to factory , i unrooted.....Nothing works for me. I just get "Unable to send". I also tried 4 SIMs from different operators !!!
Is anyone else seeing an issue where they frequently can't hear the caller when receiving a call, but the other person can hear you? I'm seeing this very often (almost every call I receive, about 7-8/10), not every call, but most. It never happens on outgoing calls. I've rooted and applied the update.zip to fix the GPS. Come to think of it, I've only noticed it since applying the update.zip. Perhaps undoing that would remedy it. Just thought I'd check if anyone else has seen a similar issue
I know it sounds silly, but are you sure your voice call volume is up? Try pressing the volume up button while in a call to see if that works.
I don't always complain, but when I do, I #BlameWes
vinnydakid said:
I know it sounds silly, but are you sure your voice call volume is up? Try pressing the volume up button while in a call to see if that works.
Click to expand...
Click to collapse
That was of course, the very first thing I checked. I usually just hang up and immediately call the person back after first explaining that I cannot hear them. Good suggestion, but I'm fairly certain that's not my problem.
Then to be honest, I'm not sure. You may want to try to wipe back to stock, but that is a little extreme.
I don't always complain, but when I do, I #BlameWes
Just wanted to bump this post, as this happens on almost every call I receive... it's not volume, it's not google voice (which I suspected) because it happens on a direct dial to my cell #... and it happens inconsitently (one call I can't hear, they call back and I can).
The only common denominator is that they can always hear me.
Right now I'm running Trigger 3.2 with Bali 1.8.8uv kernel
Try muting and unmuting when this happens, it may very well solve the issue
sent from the xda app on my android smartphone.
Perhaps a problem with your speaker?
Maybe you have an intermittent problem with your speaker? Although it really doesn't sound like it since you can call back immediately and hear them.
Just a thought. I recently had to replace the back speaker in my phone.
mtburner said:
Just wanted to bump this post, as this happens on almost every call I receive... it's not volume, it's not google voice (which I suspected) because it happens on a direct dial to my cell #... and it happens inconsitently (one call I can't hear, they call back and I can).
The only common denominator is that they can always hear me.
Right now I'm running Trigger 3.2 with Bali 1.8.8uv kernel
Click to expand...
Click to collapse
If you can hear them through a headset (not BT for testing purposes) then you have an earpiece issue and should have it (the earpiece) replaced. If your problem does not change with or without a headset then it could be a rom or interfering app issue. I would back up and flash back to stock to see if it still happens. That will tell you what to do from there.
Strange issue, I could send/receive text messages, and I could also make calls, but when trying to call my phone from another phone or if anyone else called me it would just ring like normal and go to voicemail, but my phone wouldn't ring or indicate that I had a call / missed call. This was fixed after a reboot but has anyone else had this issue?
painkillaz said:
Strange issue, I could send/receive text messages, and I could also make calls, but when trying to call my phone from another phone or if anyone else called me it would just ring like normal and go to voicemail, but my phone wouldn't ring or indicate that I had a call / missed call. This was fixed after a reboot but has anyone else had this issue?
Click to expand...
Click to collapse
I have the same issue I tried a reboot but the problem keeps coming back did that fix it permanently for you? Sometimes calls come in other times it just shows up as a voicemail.
newb09 said:
I have the same issue I tried a reboot but the problem keeps coming back did that fix it permanently for you? Sometimes calls come in other times it just shows up as a voicemail.
Click to expand...
Click to collapse
My mom's G3 exhibited this issue over the weekend, waiting to see if it comes back.
newb09 said:
I have the same issue I tried a reboot but the problem keeps coming back did that fix it permanently for you? Sometimes calls come in other times it just shows up as a voicemail.
Click to expand...
Click to collapse
I haven't had the issue since, but then again I wouldn't know unless someone texts me that they've been trying to call (I don't monitor my voicemail that closely...probably should though).
I've seen the exact same issue as well. I won't even get the call but the voice mail will show up if the caller left a message. Hopefully this is just a bad connection to the cell towers at the time the call was trying to get through and not some other issue.
Lio37 said:
I've seen the exact same issue as well. I won't even get the call but the voice mail will show up if the caller left a message. Hopefully this is just a bad connection to the cell towers at the time the call was trying to get through and not some other issue.
Click to expand...
Click to collapse
Hi coming from the M8 forums and checking things out, and I had this issue and it was due to the tower being worked on in my area. I didn't have service for an entire month at my office or apt, which are less than a mile apart. Now I have poor data service but i can receive calls. You might want to contact Sprint and let them know ASAP
I cant receive calls but i can do outgoing and sms to others weird using international unlock lg g3 sprint
Same here...maybe 2 out 10 test calls I tried went through. I called sprint and they instructed me to re-provision the device using some ##7..something..something## dialer codes. My phone magically receives calls, but I have a feeling their re-provision crap didn't do anything to fix, it was just the re-boot part that "temporarily" fixed the incoming call problem.
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
mghtymse007 said:
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
Click to expand...
Click to collapse
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
pdqgp said:
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
Click to expand...
Click to collapse
Sorry to hear you have a&t. Connected remotely and call forwarding are two completely different things as you may know but regardless of the matter its not Samsungs fault. Your device showed that it was connected remotely therefore it was....the real issue is your wireless carriers crappy network not pushing your notifications plain and simple not your watch or your phone. Both are working just fine from what you've stated which leads to the fact that its your network connection. Only GSM networks are capable of auto call forwarding which as I stated is completely carrier network based. No offense but at&t sucks anymore and havent seen these issues with anyone but at&t customers. Its on at&ts end. Call and complain about your issue but unfortunately I doubt they will do crap which is why I left at&t 3 months ago. Hope you can get them to figure it out.
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
pdqgp said:
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
Click to expand...
Click to collapse
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
rickleasa said:
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
Click to expand...
Click to collapse
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
pdqgp said:
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
Click to expand...
Click to collapse
ok glad to hear but that didn't work for me as when i went to call setting on my phone i still received the sim network error until i did the restore but glad it worked for you
djc-wi said:
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
Click to expand...
Click to collapse
I finally figured out this only happens to me after I have Bluetooth paired to my car or a headset. Only happens every once in awhile. If I reenter my car and turn it on, as soon as Bluetooth reconnects it's back to working. The problem will come back if I don't reset my phone. Then all is fine for a few days. In my case obviously the bug is in gear S bluetooth not my phone or my car as the same thing at times will happen with a Bluetooth headset.
SaintCrispin said:
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Click to expand...
Click to collapse
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
foulmouthedruffian said:
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
Click to expand...
Click to collapse
Hah I'm glad it's working for you now.