Related
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
Anyone else having issues with wifi calling? Initially people were complaining they could not hear me or constantly telling me to repeat myself. I left myself a voicemail on my work phone and was surprised how low the volume was. It's as if the mic gain was turned all the way down. I had to turn the volume to maximum just to makeout what I was saying. Additionally, the earpiece volume is also a tad low on my end. I'm assuming it's safe to say there is nothing I can do till Tmobile updates the phone, right?
tibere86 said:
Anyone else having issues with wifi calling? Initially people were complaining they could not hear me or constantly telling me to repeat myself. I left myself a voicemail on my work phone and was surprised how low the volume was. It's as if the mic gain was turned all the way down. I had to turn the volume to maximum just to makeout what I was saying. Additionally, the earpiece volume is also a tad low on my end. I'm assuming it's safe to say there is nothing I can do till Tmobile updates the phone, right?
Click to expand...
Click to collapse
I just did a test on wifi calling to my voicemail at home and the volume was fine, sounded like a normal call. There was another voicemail on there as well from someone else and it was the same volume as theirs.
Robertsonland said:
I just did a test on wifi calling to my voicemail at home and the volume was fine, sounded like a normal call. There was another voicemail on there as well from someone else and it was the same volume as theirs.
Click to expand...
Click to collapse
Hmmm...weird. I have no issues with mic volume during regular cellular calls and Skype calls (tested these two by leaving myself voicemails also).
I will call technical support and see what they have to say.
Thanks for the reply Robertsonland
I haven't had any issues (I had latency and sound issues on my Samsung Vibrant and Blackberry Curve before that using UMA) on my Sensation using Wifi calling yet. I used my friends phone while making a wifi call to it, and there was no delay at all, and the sound is great.
Bump. No one else is having low mic outgoing volume issues with wifi calling?
tibere86 said:
Bump. No one else is having low mic outgoing volume issues with wifi calling?
Click to expand...
Click to collapse
Happens to me sometimes, but not too often
Sent from my HTC Sensation 4G using Tapatalk
tibere86 said:
Bump. No one else is having low mic outgoing volume issues with wifi calling?
Click to expand...
Click to collapse
Constant. Wifi Calling is unpredictable. I have no network reception and the phone struggles to keep on wifi calling. I have tried most available roms all the patches and three devices. WIFI Calling is unreliable while using the phone. It works fine when left alone 90% of the time. However those times you pick up the phone and it doesn't show Wifi Calling, or it just then kicks in; you are catching it in its moment of sudden tmobile retardation. And i have tried it will all sorts of access points, obsessed over dd-wrt settings for weeks. Even ended up bricking a couple devices (JTAG ftw).
S-OFF Sensation LeeDroid 1.2 1.3 TMO-US Wifi Calling v1.0
If it's going in and out of WiFi calling like that it's the Sensation's WiFi reception causing the issues.
Do you put your hand over the top part of the phone when you're on a call?
My friends complain that they can hear themselves. Like an echo effect.
Sent from my HTC Sensation 4G using XDA App
Happens all the time with me and my wife...to the point that I don't use wifi calling anymore. It is certainly a problem.
echoing on speakerphone has happened to me, solution.. don't use speakerphone.
Well I'm glad I found this thread because I am having the exact same issue and was going to return my Sensation. I have no regular cell signal in my house so I have to rely on the Wifi calling and it sucks from time to time. I have to repeat myself and sometimes the other person can't hear me even if I'm yelling in the handset. So from what I've been reading, it sounds like this is a normal (abnormal) wifi calling issue with Tmobile. That sucks!!! Is there any fix or possible bandaid for this problem?
Does this only happen with the Sensation or are others having this problem with other phones?
Bumb
Anyone have found a solution to this issue ?
I just joined Tmobile and i an having the same issue .
Microphone seems to be very week and i sound far away when i call using wifi .
Tried to hold the phone in different positions and i am using a case but no changes .
Tinofet said:
Anyone have found a solution to this issue ?
I just joined Tmobile and i an having the same issue .
Microphone seems to be very week and i sound far away when i call using wifi .
Tried to hold the phone in different positions and i am using a case but no changes .
Click to expand...
Click to collapse
I have the same issue sometimes too, If i try to turn on speaker phone the mic cuts off all together. Using Revolution HD
You know .
I truly do not believe its a reception ( wifi reception or anything ) .
I ran packet capture and it all look`s "ok" no drops or resets .
This thing looks like a poor VOIP decryption , either on the phone or the Tmobile servers.
IT IS a software issue . And defenitly need to be attended to .
what i did notice that i have a sensation and so do my wife .
I get the issue she doesn't .
The difference i rooted my machine ( still uses original ROM i have a trust issue regarding running some unverified kernel`s ) .
Any thoughts ?
I have called Tmobile about the issue. The tech I talked to said there were no other reports of low mic volume. My mic volume works perfect when using Skype or SIP. But when on Wifi calling, the mic gain is way too low. I have left myself test voicemails, and I have to have the volume cranked all the way up to hear myself. Hopefully the issue will be resolved with the next software release.
Man that sucks .
This Wifi calling is cool and i like it , but if it doesnt work whats the point .
Any way to contact the development team of this product ?
Calling and talking to some dude in India at Tier I do not help here...
I have used several custom ROMs and Kernels and have had no issue with sound volume or quality using the WiFi calling app. It may be a simple hardware difference during manufacturing. Just as some people's phones work flawless while OC'd and others crash even though they all have the same model CPU. I would try to get a replacement phone to see if it works better.
I actually have another 2 new phones next to me .
Any way to clone my OS (including the config and everything ) to the other phone ?
Then i can move my SD and SIM .
My phone is giving a loud ticking static noise when I call people (I hear it on my end, don't know if people hear it on their end)
It happens every other call.
I'm on Infused 1.5.0 and the gtg's community kernel that comes with that rom (I'm assuming that is the kernel that comes with infused anyway).
Any solutions besides trying to flash back to stock or flash a different rom or something to see if it happens there?
edit: ok, friend's phone who is also on at&t (but is an iphone) is having the same issue. Probably the tower being dumb. We did have a thunderstorm earlier.
Definitely a network issue, if it didn't stop, I'd report it to AT&T
Sent from my SAMSUNG-SGH-I997 using XDA App
i had that recently when i called 611. haven't heard it since tho.
hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.
I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!
help, anyone?
i'm stuck with this, and a bit clueless.
Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?
just u can't hear other one while calling u?
thanks.
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
it's quite obvious, unfortunately it doesn't work.
cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.
tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.
any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...
Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium
I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).
I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).
If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA
Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.
What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.
Hello,
I've been a user of the xda ROMs for quite some time and i appreaciate all the work that's been put into the community.
Sadly, i have stumbled onto an issue i cannot solve myself, so i am seeking your help.
Description: When receiving a call and answering it (phone vibrates and rings), i cannot hear the other person, but they can hear me. (Speaker on/off doesn't do a thing, volume rocker up/down either). If the person calls back within a few minutes, i can almost always hear them and have a normal conversation. This does not happen in 100% of the cases, but in more than 50%. I have switched ROMs, kernels and radios (ATM i have CM7.1 RC, mar1x bfs v4,5, and XXKB3)
Is there any hope?
same issue on i9020t
I been having the same issue, but not quite as frequent, on my I9020T. I've experienced it with Cyanogenmod 7.1RC1 and NSCOLLAB (also based on CM71). I think I had it with CM7.0.2 and CM7.0.3, but can't remember for sure. The problem does not occur when I revert back to stock 2.3.4 rooted.
A somewhat related post in this forum, http://forum.xda-developers.com/showthread.php?t=1188264, got me thinking. The OP had a similar problem on an I9023 when bluetooth was enabled. I've noticed on NSCOLLAB that DSPManager is running a "Headset" service. I do not have DSPManager installed on my stock install.
Can someone more knowledgeable tell if its possible this service could be related to the problem with callers not being able to hear me. FYI, my bluetooth is normally off and I don't use a headset. I'm back to running NSCOLLAB 1.3.8, but I've disabled the Headset service. If the problem doesn't occur for a couple days, I think I may have something.
dinuvali, is the Headset service running on your build?
Removed DSPManager earlier. Just answered a call where they hear me but I can't hear them. They called me back, all normal.
Oh well, rolling back to stock for now.
Sent from my Nexus S using XDA App
Thank you for the reply,
Yes my CM 7.1 is running the DSPManager service.
Also, my neighbour who has the exact device as me, but stock unrooted, has never experienced this problem.
Along with this problem of not hearing the other person on the first call, i also get the dropped call once in a while (not only after 3 mins of talking, but also while the phone is ringing and they still haven't picked up yet)
From all the posts i've read concerning this issue, i think it's mainly a hardware issue, but maybe it can be bypassed with some sort of tweak.
Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!
dinuvali said:
Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!
Click to expand...
Click to collapse
Great find! Come to think of it, I never had it happen when I answered someone and immediately hit speakerphone, something I do alot when in my car mount.
I think I'll reload NSCollab, new version just came out today. When it happens again (unless they fixed it) I'll try this out. Thanks!