Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different firmware(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Update:
I found sth strange about the call issue by chance: when I lock the screen maybe for more than 5 mins,then wake it up and make a phone call soon,the receiver can't work every times.However, when I put it into use(light the screen) for more than 3 or 4 mins,and then the receiver works again during calls.
What I want to say is: maybe there are sth wrong with the cpu setting or the power management?
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
takooo said:
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different framekworks(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Click to expand...
Click to collapse
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Product F(RED) said:
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Click to expand...
Click to collapse
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Magik_Breezy said:
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yep!! Last time I had flashed the ripper rom and then I found this issue.First I thought it was the problems that come from the rom,but after several tries then I thought it probably due to the hardware issue that I cant solve....
Anyway,thanks for your suggestions!!
takooo said:
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Click to expand...
Click to collapse
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Product F(RED) said:
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Click to expand...
Click to collapse
Ok,thanks a lot for telling me these!!! I've sent a email to the customer service and hope to get respond soon.Anything news i will update it.
Related
Ok, first off I just want to say I have searched around the forums for a similar problem in hopes for a solution and to avoid reposting a question.
For information about my phone, see below the problem description.
Here is the problem:
This just started today, the phone will not play any ringtone or notification sound. I can confirm the speaker itself still works by playing music or choosing ringtones. Alarms do still work, just not call tones or notification tones(even using default ones).
Now that is only part of the problem, along with that, is the fact that when a text message is received, I can view it and dismiss it (Using Handcent as Default). But 30 seconds to a minute after getting the message, or usually while replying to it, the screen will go black and the capacitive buttons stay lit up. No button presses are registered and the only way to gain access into the phone is by removing the battery and putting it back in.
I am also not getting every message sent to me, some will come through while others don't.
Another unrelated issue:
If I wait an extended time between listening to music, usually 20+ hours, for the first minute or so I hear a little bit of static and then it clears up and doesn't happen until the next day.
Info about the phone:
I bought the phone new on eBay at the end of September, the 28th.
The only modification done to it is doing the latest VooDoo lagfix from the link below(I did this within two weeks of having the phone, and it worked fine):
http://forum.xda-developers.com/showthread.php?t=784170
Aside from that, the phone is completely stock running the latest OTA update.
I am using a GoPhone SIM card that has never given me any issues before.
Kernel Version: 2.6.29 voodoo_lagfix_3.0_v1.10
Firmware: 2.1-update1
Build: ECLAIR.UCJH7
Baseband: I897UCJH7
My Background
This is only my second Android phone, coming from the myTouch 3g. I have had the same SIM card for years. Now I have the Captivate, and this is the first time it has given me this kind of problem. I have experience flashing ROM's and all that, I just wanted to wait for an official update for the Captivate to see if GPS gets improved.
I hope I have provided enough information to diagnose the problem, let me know if there is anything else you need to know and thanks for your time.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
codyrt said:
[*]I bought the phone new on eBay at the end of September, the 28th.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
Click to expand...
Click to collapse
Probably why it was sold on Ebay in the first place. Just a shot in the dark, maybe the speaker connection is loose? There are a few threads about taking the phone apart if you are so inclined.
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Swyping...please read slowly!
cappysw10 said:
Just a shot in the dark, maybe the speaker connection is loose?
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Click to expand...
Click to collapse
I did think something like that at first, but every other sound works fine and when it is supposed to(startup sounds, games, etc.). And I would think if it's a loose connection that shaking the phone or moving it around would make sound cut out, but it doesn't.
I figured the manufacturer warranty wouldn't apply, but I have gotten warranty replacements in the past on other electronics from eBay. So maybe a little fibbing will be in order to receive another unit.
I'm thinking it is something software, I have no clue what, I haven't made any major software additions or changes since yesterday. But if all else fails I will try changing to a different ROM and if that fails, get a replacement from Samsung.
I would try flashing again.....and running that kernel....kinda makes your phone far from stock...
For some reason the issue has stopped. I only did a few things, I powered off the phone, turned it on with the 3-button combo, and then restarted the phone from that menu. After the restart, I reassigned the notification tones and ringtones to what they were(my personal choices, not system sounds) and it seems to work.
I will probably wait a few days to see if it occurs again, and if it does, I will move on to a ROM from the Dev section because I am convinced its just some apps conflicting with each other.
newter55 said:
and running that kernel....kinda makes your phone far from stock...
Click to expand...
Click to collapse
I figured that was a minor modification, so i just counted it as stock, but I see what you're saying.
Hoping someone will have an answer. Nexus One running CM 7.1 nightly #150
new nexus one - barely a month old. Rooted on the first day - so no warranty
All of a sudden, phone earpiece has stopped working - no sound at all. only way to make calls is to use a BT/wired headset or a speakerphone.
I've tried multiple reboots, wipes, and flashes to no avail. Also tried cleaning out the 3.5mm pin jack with a Q tip as suggested somewhere on the net.
Some people suggested that the phone might be stuck in headset mode.
Tried cleaning with qtip
With adb logcat, I can see teh phone switching from speaker phonet to handset and vice versa
Flashed back to various different CM 7 builds
Removed sim, sd card etc and booted
kept battery out
Is there anything else that I should try before I go the repair route?
Have others faced this problem?
I've seen people that their ear piece died although didn't think to ask for a logcat so I can't tell you but I'm pretty sure your going to need a repair.
just replace the earpiece http://cgi.ebay.com/EARPIECE-SPEAKE...998395?pt=PDA_Accessories&hash=item27bc302cfb
Thanks for the linky. Any idea if its OEM equipment? shipping location says HK - so not sure. So would be nice to hear if anyone's bought one from the ebay store linked above...
I'm checking with HTC support locally - but wanted to know if the repair is something that I should dare to venture on my own.
Reporting back... got my phone repaired at the HTC service center. Phone stayed 3-4 days in the shop since they need to get the parts - but now all is good and it cost just INR 400
Hi all, I'm wondering if anyone else has had this problem with the Note? I've seen it reported for other phones but in the Note forum, most complaints about the screen are about colour reproduction. It is extremely frustrating and I was hoping someone had any idea? I had already done a factory reset, took it to the Carphone Warehouse (the authorized Samsung service center near where I live) and they reflashed it with a Polish firmware, and it still has the problem.
Video of problem: http://www.youtube.com/watch?v=HAAWDwPVYmk
-------------Copy from subsequent post below-----------------
No problem. IIRC, *#0*# is the standard Samsung screen test code. (Personally I only tested this code on the Note and my SGS, which I used to film the video). I had also noticed that it usually happened after a bit of running (I ran an intensive flash video for 5-6 minutes). But then it started to happen just after I turned it on in the morning even when the phone was cold.
If this problem is really bothering you, I recommend you go straight to Samsung. The service I got here in the UK has been great so far. I sent it in and 2 days later, they told me they had replaced the screen and were testing it. If all goes well, I should have it back early next week. The phone number for the UK is 0330 7267864 if anyone is interested.
Click to expand...
Click to collapse
AETAaAS said:
Hi all, I'm wondering if anyone else has had this problem with the Note? I've seen it reported for other phones but in the Note forum, most complaints about the screen are about colour reproduction. It is extremely frustrating and I was hoping someone had any idea? I had already done a factory reset, took it to the Carphone Warehouse (the authorized Samsung service center near where I live) and they reflashed it with a Polish firmware, and it still has the problem.
I cant post links, but you can add this onto the end of Youtube...
/watch?v=HAAWDwPVYmk
Click to expand...
Click to collapse
Having similar problem.
On mine, the issue is intermittent. Luckily I can now reproduce the problem by pressing the top side of the phone corner here and there and screen jitters/scrolls down/un responsive.
Same problem on mine...
I'm experiencing the same issue on mine as well, but only intermittently. I noticed it happens after I've been using the Note for a while and when it gets warm. I don't know if it's heat related. I still have to do more testing, but it seems like the problem immediately goes away when I plug it into the charger.
Thanks for posting the video, now I know there's a built in utility for testing the LCD
No problem. IIRC, *#0*# is the standard Samsung screen test code. (Personally I only tested this code on the Note and my SGS, which I used to film the video). I had also noticed that it usually happened after a bit of running (I ran an intensive flash video for 5-6 minutes). But then it started to happen just after I turned it on in the morning even when the phone was cold.
If this problem is really bothering you, I recommend you go straight to Samsung. The service I got here in the UK has been great so far. I sent it in and 2 days later, they told me they had replaced the screen and were testing it. If all goes well, I should have it back early next week. The phone number for the UK is 0330 7267864 if anyone is interested.
Ghost Touch Issue
AETAaAS said:
No problem. IIRC, *#0*# is the standard Samsung screen test code. (Personally I only tested this code on the Note and my SGS, which I used to film the video). I had also noticed that it usually happened after a bit of running (I ran an intensive flash video for 5-6 minutes). But then it started to happen just after I turned it on in the morning even when the phone was cold.
If this problem is really bothering you, I recommend you go straight to Samsung. The service I got here in the UK has been great so far. I sent it in and 2 days later, they told me they had replaced the screen and were testing it. If all goes well, I should have it back early next week. The phone number for the UK is 0330 7267864 if anyone is interested.
Click to expand...
Click to collapse
I wish I could send it back somewhere. I'm in the US, and the Note was a gift from a relative in the Philippines, who bought it from an importer. It looks like it was originally meant for Germany, so Samsung USA doesn't want to repair it, even when I offered to pay. Same response from Samsung UK.
The problem seems to be more apparent now with ICS (stock). Just like before, the problem crops up after some use when the phone and/or battery gets warm. Oddly enough, the problem immediately GOES AWAY as soon as I plug it into the charger.
temp fixes?
Anyone come up with a work around to this.
I made a portable charger at first, but now it dose it when its plugged too
maybe disable finger touches and just use the spen?
My earpiece stopped working today. This is the second time the earpiece of my Xperia T died. The first time was in October when I had the phone replaced as it was within the one month period. The very same thing has happened again with me within a few months of getting my replacement handset. I was able to locate another person who had the very same problem on some forums. I definitely think that the build quality of this phone is not as it ought to be as it cannot be a coincidence that I got the same issue twice with two separate brand new handsets!
Have just booked a repair with Sony's authorised repairer (SBE limited in UK). Has anyone else faced the same problem here?
sshariff said:
My earpiece stopped working today. This is the second time the earpiece of my Xperia T died. The first time was in October when I had the phone replaced as it was within the one month period. The very same thing has happened again with me within a few months of getting my replacement handset. I was able to locate another person who had the very same problem on some forums. I definitely think that the build quality of this phone is not as it ought to be as it cannot be a coincidence that I got the same issue twice with two separate brand new handsets!
Have just booked a repair with Sony's authorised repairer (SBE limited in UK). Has anyone else faced the same problem here?
Click to expand...
Click to collapse
I had issues of people finding it hard to hear me..meaning mic volume isnt enough. Got it replaced within the one month period to a brand new one.
Issue seemed to have reduced then but now its there many times, thus I have to speak louder than usual. Yet couldnt be bothered to go for a repair.
Not many users seem to have this issue. When did you get your first handset? I got mine on end of Sept (more or less release day in uk..) I have a feeling its to do with a specific batch (similar to the peeling issue)
ruwsoft said:
I had issues of people finding it hard to hear me..meaning mic volume isnt enough. Got it replaced within the one month period to a brand new one.
Issue seemed to have reduced then but now its there many times, thus I have to speak louder than usual. Yet couldnt be bothered to go for a repair.
Not many users seem to have this issue. When did you get your first handset? I got mine on end of Sept (more or less release day in uk..) I have a feeling its to do with a specific batch (similar to the peeling issue)
Click to expand...
Click to collapse
I got mine at the release date as well! Then had it replaced after 3 weeks...
Solved the issue!
The exact details of this issue can be seen at talkDOTsonymobileDOTcomDASHthreadDASH56851?start=0&tstart=0
(Sorry for that bad URL as I am too new to copy links)
I did a factory reset, flashed ICS from JB Europe generic, then updated to UK generic JB via PC Companion. Still the problem did not go. Then just out of curiosity I checked if I could hear sound from my Sony supplied headphones, and I could. I then removed the headphones and bingo everything is back to normal.
I think there is an inherent software bug with the Sony software for this phone where under some odd scenario sound gets disabled. Maybe if anyone else gets into a similar situation they can take heed of the resolution. Saved a couple of weeks at the repair shop at least!
Same Problem
I had the same problem on more than one occasion in past plugging in handfree and unplugging would work but over the weekend i ended up doing a factory reset but still didnt work but strangly somebody rung me and ear piece now working! im still in warrenty should i send away?
sshariff said:
Solved the issue!
The exact details of this issue can be seen at talkDOTsonymobileDOTcomDASHthreadDASH56851?start=0&tstart=0
(Sorry for that bad URL as I am too new to copy links)
I did a factory reset, flashed ICS from JB Europe generic, then updated to UK generic JB via PC Companion. Still the problem did not go. Then just out of curiosity I checked if I could hear sound from my Sony supplied headphones, and I could. I then removed the headphones and bingo everything is back to normal.
I think there is an inherent software bug with the Sony software for this phone where under some odd scenario sound gets disabled. Maybe if anyone else gets into a similar situation they can take heed of the resolution. Saved a couple of weeks at the repair shop at least!
Click to expand...
Click to collapse
My phone's screen just went black suddenly while i was using the phone last night. Nothing i do will wake the screen up, i tried rebooting by holding the power button, tried power+volume down also to boot into recovery .. no response. However the phone seems to be functioning as i can hear the screen lock sound. I think im stuck on the pin screen (the one to pass the boot-up-encryption). theres some vibration and feedback when i randomly press on the screen too.
The device is running Stock 6.0.1 , unrooted , stock kernel. Has this ever happened to anyone else ? could it be a software issue ?
I believe the LCD panel just went dead ..
Thanks!
Have you hooked it up to a computer and tried to see if it's recognised by ADB?
moses992 said:
My phone's screen just went black suddenly while i was using the phone last night. Nothing i do will wake the screen up, i tried rebooting by holding the power button, tried power+volume down also to boot into recovery .. no response. However the phone seems to be functioning as i can hear the screen lock sound. I think im stuck on the pin screen (the one to pass the boot-up-encryption). theres some vibration and feedback when i randomly press on the screen too.
The device is running Stock 6.0.1 , unrooted , stock kernel. Has this ever happened to anyone else ? could it be a software issue ?
I believe the LCD panel just went dead ..
Thanks!
Click to expand...
Click to collapse
I had a nexus that had a faulty screen and randomly shut off or something half the screen will glitch out and one day it just stopped working but I could hear the lockscreen sounds. Your best bet would be to send it in for service maybe its a loose connecting or a hardware issue. When mine started acting up it was a loose connecting so if I hit the phone with my hand it would go back to normal and then it stopped working. Its a common issue if you do a google search many people have encountered this
That sounds to me like a return-under-warranty job. If you were in the UK you could quote the Sale of Goods Act, which specifies that an item must be of suitable quality and last a reasonable amount of time, but in my case when I returned my faulty N5 to Google after 18 months they were as good as gold, didn't quibble, simply replaced it with a refurbished one which appeared to me to be indistinguishable from brand new.
Since by definition your phone must be very close to its warranty period, depending on when you got it, I'd start with that. This is the link I used from the UK - maybe different if you're elsewhere, but you should find a link called "Get a call from a hardware specialist":
https://support.google.com/store/co...roid_help&cfnti=escalationflow.c2c&cft=5&rd=1
Didgeridoohan said:
Have you hooked it up to a computer and tried to see if it's recognised by ADB?
Click to expand...
Click to collapse
Havent done that yet. Only thing that would be good for is making sure its a hardware defect right ?
jazz995756 said:
I had a nexus that had a faulty screen and randomly shut off or something half the screen will glitch out and one day it just stopped working but I could hear the lockscreen sounds. Your best bet would be to send it in for service maybe its a loose connecting or a hardware issue. When mine started acting up it was a loose connecting so if I hit the phone with my hand it would go back to normal and then it stopped working. Its a common issue if you do a google search many people have encountered this
Click to expand...
Click to collapse
That makes sense. could be just a loose connector between the LCD panel and the MoBo ..
Problem is i live in Jordan and I got the phone from Dubai. Its still under warranty of the seller (Souq.com ; an online store .. kind of like Amazon of the middle east ), So i have to send my phone to Dubai to fix it. Now i could just go to a local phone repair shop and ask the guy to check the connectors, but im afraid that would void the warranty and not solve the problem ;( .
dahawthorne said:
That sounds to me like a return-under-warranty job. If you were in the UK you could quote the Sale of Goods Act, which specifies that an item must be of suitable quality and last a reasonable amount of time, but in my case when I returned my faulty N5 to Google after 18 months they were as good as gold, didn't quibble, simply replaced it with a refurbished one which appeared to me to be indistinguishable from brand new.
Since by definition your phone must be very close to its warranty period, depending on when you got it, I'd start with that. This is the link I used from the UK - maybe different if you're elsewhere, but you should find a link called "Get a call from a hardware specialist":
https://support.google.com/store/co...roid_help&cfnti=escalationflow.c2c&cft=5&rd=1
Click to expand...
Click to collapse
I submitted the form , although i live in Jordan which has no presence of Google whatsoever but what the heck !
thanks all for your suggestions.
Google is supposedly a global company...
Let us know how it goes, and good luck.
Well, if you figure out that it is just the screen, you can use this program for basic control with a lot of latency
http://forum.xda-developers.com/showthread.php?t=2786395
It's a little rough and confusing but, it's workable. If you need help setting it up feel free to shoot me a PM.