Related
Im having a problem with the charge - im running Gummy 2.0 with EE4 Radio.
When im on calls i frequently get into a situation where people will stop being able to hear me. I can still hear them, but nothing i can do including re-dialing them will fix the outgoing voice from me to them. I have to reboot to make it work.
Has anyone experienced this and is it a known issue with a fix perhaps?
Thanks
cmdrfrog said:
Im having a problem with the charge - im running Gummy 2.0 with EE4 Radio.
When im on calls i frequently get into a situation where people will stop being able to hear me. I can still hear them, but nothing i can do including re-dialing them will fix the outgoing voice from me to them. I have to reboot to make it work.
Has anyone experienced this and is it a known issue with a fix perhaps?
Thanks
Click to expand...
Click to collapse
Try flashing the EE4 or EP1Q radios.
I've experienced this too, and there's another thread, http://forum.xda-developers.com/showthread.php?t=1210384 with more details.
VZW replaced my phone, and I'm still trying to determine if the issue is gone yet or not. It appears to be happening a lot less so far. I noticed that for the EP1Q leak, as well as now with GummyCharge 2.0 + 1.4Ghz OC
This was posted by a Verizon employee on the Verizon Community Forums.
I have some good news to share about the audio going out on these devices. I did a query in our trouble ticket system about the Charge losing audio and randomly muting the call. What I found was actually surprising to me. SOME Charges were affected by network element in their market, and how the Charge responds to a switch element. Because it was so widespread, we assumed it was only a software problem (Samsung is fixing this issue as well with a software update). Here's an abbreviated resolution from one of the tickets that had this problem resolved: "There was an issue with the Samsung Charge in markets that use the Tellabs 3700 PAEC and that was resolved on Friday 8/12 BY changes on the 3700 PAEC ECANS .. Customers should be fine since then .. In MD - the issue was fixed on the night of 8/19." So many customers have already seen improvements.
So, what this means is each person that is experiencing issues with audio going out randomly while in good coverage should call tech support directly at 866-892-7957 > 1 > Enter number > Choose the option for advanced devices and PDAs. This will get you connected with tech support. If you'd like to give them a ticket to reference, use NRB ticket 4574701 as a reference. It's possible that the network your Charge is connecting to did not receive the 3700 PAEC ECANS update. If your issue is not resolvable by the NRB, it will by fixed by the Samsung software update (of course I have no ETA on that other than soon).
Click to expand...
Click to collapse
Dear All.
My samsung galaxy s2 skyrocket had been working with ParanoidAndorid (v 2.55) for 2 months without problems, but since a week ago I couldn't place regular calls. I can dial the numbers and receive calls, but in neither case I can hear any sound. The rest of the functions work just fine (youtube, chrome, etc). After checking for sound configurations, such as noise reduction, the problem persisted. I have to say that the problem goes away after rebooting the system, but is happens again at random times. I've change to Cyanogenmod 10, but the situation holds.
I noted that two apps seems to be producing this problem: Viber and Line. Immediately after I receive a Viber/Line call the problem arises. This is strange as I've been using Viber from the beginning, but the problem has been happening only from last week.
I would appreciate any suggestions. Thanks in advance
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
hechoen said:
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
Click to expand...
Click to collapse
I'll try using the phone without Viber/Line for a couples of days just to be sure that is a app-driven problem. Given the popularity of these apps, I would be surprised if this is only happening to me.
Did the app update recently? I'd unistall it then clear caches and reboot. If the problem goes away it's the app.
Hi @MarceloR -
I am a rep. of Viber here on XDA.
Thanks for sharing the details of the problem.
First, please note that Viber does not officially support your device, s2 skyrocket (here is the full list of fully compatible devices: http://bit.ly/Hm5k9p). Furthermore, we (Viber) don't claim to fully support devices with Custom ROMs, since it is impossible for us to adapt our app with all of the Custom ROMs out there.
Both these issues may be the sorurce of the problem you're experiencing. Have you tested this issue on Stock ROM on your device? (though it's not fully supported).
Having said that, the problem still sounds odd - Viber should not affect your ability to use your phone for regular calls.
Same problem, different software
I'm having the same issue - no mic, no sound on phone calls. I do not have either of the above-mentioned apps installed. I'm running CM10.1, though (Rogers). Tried installing the CLI3 modem, and the stock Rogers modems to see if that might help.
I did notice that the ear speaker was getting quite hot when I tried to use the phone, and the phone app itself is performing tremendously slow.
If anyone has thoughts / suggestions about how to fix this, I'd really appreciate it.
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Update: pulled SIM card, battery. Reboot, shut down, insert SIM card. Everything works again. Using the same 3/3 nightly. No other changes.
lingowistico said:
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Click to expand...
Click to collapse
Common for whom I don't have these issues. I swear how do you guys have all of these crazy problems.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
http://forum.xda-developers.com/showthread.php?p=39678817
@lingowistico -
Thank you for sharing this valuable information, that will help us aide our users as well.
If you have any news in this matter, please do let us know
lingowistico said:
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
Click to expand...
Click to collapse
I circumvented this problem by installing an old version of viber (one from Dec 2012). I found the old version here: http://www.androiddrawer.com/
So far, no problems. Everything seems to be back to normal.
I have a T-Mobile 8X and when I turn on the speakerphone the other side can't hear me but I can still hear them. Both sides can hear when speakerphone is off.
Has anyone else had this issue? I've hard reset and still have the same thing so it leads me to believe it is a hardware issue.
And just to clarify this has nothing to do with the voice command to dial using speakerphone. I place the call normally and turn the speaker on and the other party can't hear me but I can hear them. If I do the voice dialing which is the thing I find on Google then I have the same issue as others online (no one can hear anyone) but I don't care about that.
That is a bizzare issue if you can give voice commands but not be heard on speakerphone. They should use the same microphone, right? That would lead me to believe the hardware works fine, and there may be a software issue.
Do you have a case on your phone? Sometimes those interfere, though I doubt it with what you described.
Have you tried doing a call over Skype? That would help you confirm that whether or not the speaker phone mic hardware works, then we'd know the issue is software.
You've probably already checked this, but make sure that the mute button is not getting pressed when you switch to speaker phone.
waraukaeru said:
That is a bizzare issue if you can give voice commands but not be heard on speakerphone. They should use the same microphone, right? That would lead me to believe the hardware works fine, and there may be a software issue.
Do you have a case on your phone? Sometimes those interfere, though I doubt it with what you described.
Have you tried doing a call over Skype? That would help you confirm that whether or not the speaker phone mic hardware works, then we'd know the issue is software.
You've probably already checked this, but make sure that the mute button is not getting pressed when you switch to speaker phone.
Click to expand...
Click to collapse
EVERYTHING works except my voice when on speakerphone. Skype, voice commands, everything. I can record audio with a voice recorder and play it back. Mute button is not pressed.
I've hard reset the phone and it didn't fix the issue. I think I'll send it in for service soon.
Also, I noticed we have different firmware and bootloader versions. Mine are:
Firmware: 1532.20.20004.531
Bootloader: 0.0.1532.20(160093)
I'm on T-mobile too, my phone is only a week old. Your post made me worried, so I tried out a speaker phone call and it worked fine.
Looking at your OS version, I know there is an update available. I haven't gotten it yet, but you might try it to see if your problem clears up.
waraukaeru said:
Also, I noticed we have different firmware and bootloader versions. Mine are:
Firmware: 1532.20.20004.531
Bootloader: 0.0.1532.20(160093)
I'm on T-mobile too, my phone is only a week old. Your post made me worried, so I tried out a speaker phone call and it worked fine.
Looking at your OS version, I know there is an update available. I haven't gotten it yet, but you might try it to see if your problem clears up.
Click to expand...
Click to collapse
My phone is on the latest OS available to it. There is an even newer firmware that some people have (20010).
petard said:
My phone is on the latest OS available to it. There is an even newer firmware that some people have (20010).
Click to expand...
Click to collapse
Odd. I have the same version number and my phone is pestering me to install an update.
waraukaeru said:
Odd. I have the same version number and my phone is pestering me to install an update.
Click to expand...
Click to collapse
You have 20010? You said in the previous post you have 20004. I have 20008.
petard said:
You have 20010? You said in the previous post you have 20004. I have 20008.
Click to expand...
Click to collapse
Same OS version number: 8.0.10211.204
I have the older firmware. Maybe that's what it wants to update. I figured it was an OS update.
Calls drop often. Usually within the first minute, and then every time when Im calling back after 10sec. The phone itself does not lose signal. Strange thing is, if I'm getting phone call after first/second drop, phone continues connection without problems... But Only when Im receiving a phone call not when Im trying to re-call someone.
- I tried replacing my sim and the issue persists. No problems with other phones using this Sim (even in the same locations).
These are pretty annoying issues. Anybody else experiencing them? Is there a different radio I can try for the phone? Is there any log I can access showing a reason for the call drop, or any trouble shooting I can do? This seems to be independent of WCDMA Only/Preferred/GSM/WCDMA (Auto) settings. Or if, how to change these settings?
Note: This has nothing to do with the network. I've been with the same company (Orange Europe) for about 2.5 years, and have never had this happen before. This has been consistent since I got my OnePlus (about 1 week ago)
That's true. I'm experiencing this as well for quite some time now. At first I joked and said: Hey, the NSA joined our conversation.....again. But after some time it really annoys me. This has nothing to do with the ROM or kernel as I have tried out various combinations. What I found out is that it got better after I returned to stock CM 11s with stock kernel. But it's not gone completly.
Honestly I neither know how to fix it nor what is causing the problem. Try to reflash the CM11S 25R firmware and see if it gets better. I think something is wrong with the modem software since CM11S 22R,25R and CM11 builds are using the same modem software. Maybe the announced update for the end of this month or early next month will fix this. I really hope so because a phone which is not able to hold a call, can't be considered as a real phone.
Oh im pitty You, If You'll get something just please let me know. Any advices or help will be appreciated. Maybe waiting for new CM relase will solve the problem, I do rly like this OS even with so many bugs... there is always an option. Move to stock 4.4 published by OP on official website.
Anyone else facing the same issue? Was there ever a fix for this issue? I'm on 38R and still encountering this issue
Same here.
See this thread for answers and work around. No solution as of yet.
http://forum.xda-developers.com/oneplus-one/help/dropped-calls-weak-lte-signal-t2916659
Hi guys
I just got new u11 from sprint. I was very excited about this phone until I started to notice that the phone goes on mute while I'm on a call. The mute icon is not pressed. I usually click it to activate then deactivate it and it brings it back. Sometimes I hit that and speakerphone until the caller can hear me again. It's pretty frustrating. I searched online and it appears to affect many phones with 7.1.1, so I'm not sure if replacing the phone will cure this issue. I'm still within my exchange period but wanted to check with the community if there's a solution to this annoyance. It looks like it's affecting many phones and the users are pretty pissed off about it. Is there a fix from either sprint / HTC or Google ? Any advice is appreciated!
Yaboc
yaboc said:
Hi guys
I just got new u11 from sprint. I was very excited about this phone until I started to notice that the phone goes on mute while I'm on a call. The mute icon is not pressed. I usually click it to activate then deactivate it and it brings it back. Sometimes I hit that and speakerphone until the caller can hear me again. It's pretty frustrating. I searched online and it appears to affect many phones with 7.1.1, so I'm not sure if replacing the phone will cure this issue. I'm still within my exchange period but wanted to check with the community if there's a solution to this annoyance. It looks like it's affecting many phones and the users are pretty pissed off about it. Is there a fix from either sprint / HTC or Google ? Any advice is appreciated!
Yaboc
Click to expand...
Click to collapse
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
AarSyl said:
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
Click to expand...
Click to collapse
Hi I did the factory reset without restoring any apps settings and the problem remains where during the call it goes on mute in and out. I called sprint and requested a new phone since this is either a hardware problem or bad sprint rom flash from factory. I went with a new phone route since I didn't want to waste the 14 day return/replacement period. Hopefully the new unit will work as expected out of the box. It's funny that a lot of people seem to have this issue on different brands.
AarSyl said:
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
Click to expand...
Click to collapse
yaboc said:
Hi I did the factory reset without restoring any apps settings and the problem remains where during the call it goes on mute in and out. I called sprint and requested a new phone since this is either a hardware problem or bad sprint rom flash from factory. I went with a new phone route since I didn't want to waste the 14 day return/replacement period. Hopefully the new unit will work as expected out of the box. It's funny that a lot of people seem to have this issue on different brands.
Click to expand...
Click to collapse
Nothing to do with HTC and/or Sprint specifically. It seams to be a new feature if Android and is bound to the OS version 7.1.1 and upwards. OEMs can't do anything about it. Got it as well on my unit, bit when I activate knock on feature when in call it still does work as on previous versions, thus I don't care about the automatic DND during call in any way.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Nothing to do with HTC and/or Sprint specifically. It seams to be a new feature if Android and is bound to the OS version 7.1.1 and upwards. OEMs can't do anything about it. Got it as well on my unit, bit when I activate knock on feature when in call it still does work as on previous versions, thus I don't care about the automatic DND during call in any way.
Click to expand...
Click to collapse
What knock on feature are you talking about.
yaboc said:
What knock on feature are you talking about.
Click to expand...
Click to collapse
You can activate a knock feature for a second incoming call when talking on the line already. Sorry the knock on should try to describe this one.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
You can activate a knock feature for a second incoming call when talking on the line already. Sorry the knock on should try to describe this one.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
im still not sure what you mean by knoc on feature. I will search the forum but this has nothing to do with another incoming phone call. i'm having in and out sound issues with the first call that's coming in.
yaboc said:
im still not sure what you mean by knoc on feature. I will search the forum but this has nothing to do with another incoming phone call. i'm having in and out sound issues with the first call that's coming in.
Click to expand...
Click to collapse
You guys are talking about 2 different things.
One is micrpohone mute in call (seems like a bug) and the other one is DND mode while in call (seems like a feature).
I don't experience the behaviour you experience with calls on European model.
velimirchek said:
You guys are talking about 2 different things.
One is micrpohone mute in call (seems like a bug) and the other one is DND mode while in call (seems like a feature).
I don't experience the behaviour you experience with calls on European model.
Click to expand...
Click to collapse
yes it's DND while on call, but it's not pressed/activated. i'm getting new phone anyways and will see if the issue persists. it's very annoying and not a good first experience with U11. i'm not sure if this is a software or hardware bug but this shouldn't be happening with a new device out of the box.
yaboc said:
yes it's DND while on call, but it's not pressed/activated. i'm getting new phone anyways and will see if the issue persists. it's very annoying and not a good first experience with U11. i'm not sure if this is a software or hardware bug but this shouldn't be happening with a new device out of the box.
Click to expand...
Click to collapse
So what is it then?
1. DND while on call? It's nornal, you got your answer and new phone will act the same. It's not a bug.
2. Microphone goes on mute automatically and caller can not hear you? That's what you said in first post. It might be a bug.
velimirchek said:
So what is it then?
1. DND while on call? It's nornal, you got your answer and new phone will act the same. It's not a bug.
2. Microphone goes on mute automatically and caller can not hear you? That's what you said in first post. It might be a bug.
Click to expand...
Click to collapse
I receive a call and after some time ( varies from few seconds to a min) the caller can't hear me. I put them on speakerphone they can hear me. Switch speakerphone off they can hear me again via normal call. It's ****ing frustrating. It's happening with a new replacement phone from sprint. I'm thinking about giving up on this u11 and getting galaxy. Its unlikely that it's a hardware issue on two new phones twice in a row
I have this same issue I also have several people tell me that they've called me several times yeah I have no missed calls I also have a strange text messages from the number 9479 and their blank
yaboc said:
I receive a call and after some time ( varies from few seconds to a min) the caller can't hear me. I put them on speakerphone they can hear me. Switch speakerphone off they can hear me again via normal call. It's ****ing frustrating. It's happening with a new replacement phone from sprint. I'm thinking about giving up on this u11 and getting galaxy. Its unlikely that it's a hardware issue on two new phones twice in a row
Click to expand...
Click to collapse
Hi Yaboc,
John here in Ireland and I'm having the same issue with my European HTC U11 and I feel your pain. I've been doing some Googling on the issue and have seen that (on previous HTC models anyway) it may be if you have Bluetooth on, the phone tries to connect to devices to pass the audio through and this is what causes the muting of the call. Do you have bluetooth switched on when the problem occurs? I have Bluetooth permenantly on for connecting to my Moto 360 watch so will try when I get home from work today to see if the problem still occurs if I switch Bluetooth off.
I'll be sure to let you know how I get it and just thought I'd share with you what I've read elsewhere online.
Here's the article I was on about earlier:
https://thedroidguy.com/2015/08/how...-cannot-be-heard-other-related-issues-1047469