Disappointed : No audio during call - Samsung Galaxy W I8150

Hi!
I'm experiencing a serious issue with my Galaxy Wonder.
Sometimes, my phone calls (incoming and outgoing calls) have absolutely no audio. I can't hear anything and also the reciever/caller can't ear me.
To solve this problem I have to reboot the phone and then it works.
Anyone else is having this issue ?

its also happen with my phone

Its a well known issue, but as far as i know no official update has resolved it yet
Sent from my GT-I8150 using XDA App

pac0mo said:
Its a well known issue, but as far as i know no official update has resolved it yet
Click to expand...
Click to collapse
Ok, I've read some forums and I understand that is a "common" problem (it shouldn't be!!).
Should I send my phone to Samsung o wait for an Update ?
It's hardware related or not ?
Does anybody ever understand why this is happening ?

err404 said:
Ok, I've read some forums and I understand that is a "common" problem (it shouldn't be!!).
Should I send my phone to Samsung o wait for an Update ?
It's hardware related or not ?
Does anybody ever understand why this is happening ?
Click to expand...
Click to collapse
I'm pretty sure it's not hardware related... hope samsung fixes it.

RE: update firmware
I think this issue could be solve by update firmware which release by samsung.
Just go to "setting", and "about phone" then "check update"
then i think these issue can be solve.
So far, I didn't face any issue after i update the firmware.

chunsum1988 said:
I think this issue could be solve by update firmware which release by samsung.
Just go to "setting", and "about phone" then "check update"
then i think these issue can be solve.
So far, I didn't face any issue after i update the firmware.
Click to expand...
Click to collapse
Yes, I got this issue as well. Already update to new firmware yesterday. See how it response first before I complain to Samsung.
Cheers:

If you have not updated do this :
During a call....
Press Vol- down all the way n Vol+ up to the max.
Unless you update your firmware from SGH OTA
Sent from my GT-I8150 using xda premium

andynroid said:
If you have not updated do this :
During a call....
Press Vol- down all the way n Vol+ up to the max.
Unless you update your firmware from SGH OTA
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Do you have this problem and does this method actually work? have you tried it?

Just a quick note that this has also happened on my wife's phone.
Along with not having any audio in call, the phone ringer and other alerts had no sound as well. Required a reboot to fix it.
On the latest official XEU firmware via Kies.

I have exactly the same issue.

err404 said:
Hi!
I'm experiencing a serious issue with my Galaxy Wonder.
Sometimes, my phone calls (incoming and outgoing calls) have absolutely no audio. I can't hear anything and also the reciever/caller can't ear me.
To solve this problem I have to reboot the phone and then it works.
Anyone else is having this issue ?
Click to expand...
Click to collapse
i think this problem persists with all samsung galaxy smartphones.i experienced this today morning when i installed an app called talking tom.previosly i experienced this just after i tried calling in nimbuzz.bit all these resolved when o restarted the phone.i think this has to do something with the apps which uses sound system of the device

Update ur FW to 2.3.6
Sent from my GT-I8150 using xda premium

already updated to 2.3.6.

saleelsalam said:
i think this problem persists with all samsung galaxy smartphones.i experienced this today morning when i installed an app called talking tom.previosly i experienced this just after i tried calling in nimbuzz.bit all these resolved when o restarted the phone.i think this has to do something with the apps which uses sound system of the device
Click to expand...
Click to collapse
Hey guys. after update to it2.3.6. Every thing smooth for almost few weeks d. No found any similar problem....

Sorry for this huge delay.
3 weeks ago I've updated to the last firmware and my Wonder it's just reborn as a new phone.
It's faster, better, and most of all it has phone capabilities with no issues.
Now waiting for an Ice Cream Sandwich...

saleelsalam said:
i think this problem persists with all samsung galaxy smartphones.
Click to expand...
Click to collapse
Never happened with my SGS2 - had it since launch.
BTW, this problem has not recurred on my wifes SGW since my last post.

I recommend my girl friend to buy SGW 2 weeks ago. It is already running GingerBread version 2.3.6, this device seem smooth within 2 weeks, but now this audio issue start to kick in... any practical and workable solution for this???

So is this issue resolved now ?
My gf is planning to buy this phone. I don't want her to have any troubles.
Peace brothers!

Maybe it is a solution to root the SGW and install cwm. In CWM then wipe cache partition and wipe dalvik cache. That often solves problems which appeared after some time of using!
Gesendet von meinem GT-I8150 mit Tapatalk

Related

Some times i cant pick up the.incoming call.

My defy is having one problem. Its actually random. Sometimes when a call comes, i am not able to pick it up. The touch simply wont work. Then i have to cut the call using the power button and call them back.
Sent from my MB525 using XDA App
Are you using SetVSel? If yes then what settings are you using?
Im getting rid of mine because of the same issue. It seems to randomly break during some incoming calls. Sometimes the touch sensors stop working, sometimes it fails to to bring up the answer/reject lock screen and just brings up the normal one. Other times it goes into a frenzy of randomly pressing the buttons and touch screen all by itself while ignoring anything I do to try and prevent it. Its a great device, but as a phone its been crap for me.
I dont use setvsel because it caused issues with the graphics on my defy, even at 850 it caused corruption and freezing on anything 3d. I had the call answering issues before rooting and unstalling setvsel btw
Sent from my MB525 using XDA App
LetoKynes said:
Are you using SetVSel? If yes then what settings are you using?
Click to expand...
Click to collapse
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App
obscurant1st said:
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeap that's what I meant.
Well I'm not entirely sure, but I remember someone mentioning he had trouble picking up calls because his frequency was too low but yours seem fine.
Have you tried disabling SetVSel to see if it works OK without it?
XDA app? where did you get it?
Sometimes i cant able to lift the call
even i am not able to lift the call sometimes the touch is not working at the time by clicking the power button then the call is ending.
Yeah, i got it from the market.
Sent from my MB525 using XDA App
But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?
obscurant1st said:
But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?
Click to expand...
Click to collapse
happens here too, no root, no overclocking tools. plain stock defy but happens
with launcher ex as well. mostly when on the charger or been not in use for a
few hours.
oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/
obscurant1st said:
oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/
Click to expand...
Click to collapse
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.
philofax said:
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.
Click to expand...
Click to collapse
Wow, thats a real relief. Thanks man.
Sent from my MB525 using XDA App
I have this problem with mine. Totally stock and it didn't happen until AFTER I updated to Froyo. It has happened about 5 times now.
You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|
vikrambharadwaj said:
You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|
Click to expand...
Click to collapse
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?
someAZdude said:
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?
Click to expand...
Click to collapse
, then it could be something else.
And well, I am not using or will ever use a screen protector! I simply don't like them. idk why!
I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk
D3rR0fl3r said:
I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
But tbh i don't think Indian defy has motoblur installed in it! At-least I haven't seen it yet on my phone!
i have indian rom , but i have faced this issue...and i dont know why it happend....faced 2 to 3 times now...hoping to get an solution.....one solution is just lock and unlock it again by press and release pow button i think it solves the issue of random screen freeze

Annoying clicking sound!

Hello,
so I'm with my 3th GNex now! with the 1st one the USB Port suddently stopped working properly. The 2nd one had a flawed display (had it for only 3 days but did notice the same problem with my 3th one)
My 3th one is okay but there is one problem: After 3 secs of any sound being played I can here a clicking/poppping sound coming from my speaker. This is very annoying when I've the normal Touchsounds on (I disabled them because of this...)
So I searched on google a bit and many users seem to have the same problem ( http://code.google.com/p/android/issues/detail?id=22307 ).
It seems to be unclear if this is a hard- or software issue.
So I wanted to ask you guys do you have this issue aswell? Is there a fix for this? Hard- or software issue, what do you think? Should I again exchange my phone for a new one risking it to have a even louder clicking sound?!
lukasb9000 said:
Hello,
so I'm with my 3th GNex now! with the 1st one the USB Port suddently stopped working properly. The 2nd one had a flawed display (had it for only 3 days but did notice the same problem with my 3th one)
My 3th one is okay but there is one problem: After 3 secs of any sound being played I can here a clicking/poppping sound coming from my speaker. This is very annoying when I've the normal Touchsounds on (I disabled them because of this...)
So I searched on google a bit and many users seem to have the same problem ( http://code.google.com/p/android/issues/detail?id=22307 ).
It seems to be unclear if this is a hard- or software issue.
So I wanted to ask you guys do you have this issue aswell? Is there a fix for this? Hard- or software issue, what do you think? Should I again exchange my phone for a new one risking it to have a even louder clicking sound?!
Click to expand...
Click to collapse
I had this same issue and I can safely say its software related. If you flash Francos latest kernel he has this issue fixed. If your unrooted I'm not too sure what options you might have (apart from exchanging the device again?).
RTContent said:
I had this same issue and I can safely say its software related. If you flash Francos latest kernel he has this issue fixed. If your unrooted I'm not too sure what options you might have (apart from exchanging the device again?).
Click to expand...
Click to collapse
I read about the fix on francos kernel....the problem though is, that I already use his kernel...last version r110...the fix doesn't work for my phone
Weird. I don't use his nightlies, have you tried M2?
Sent from my Galaxy Nexus using Tapatalk
m2 doesnt even have the fix.
What's your software version? I'm on stock 4.0.2 and have no issues.
Sent from my Galaxy Nexus using XDA
are you sure you dont have it? play any sound in a quiet room and listen closely. i only noticed it after reading about it and checking for it... shouldnt have done that. and the volume seems to vary from day to day
Nope didn't have it. Played some music tracks and listened to the touch sounds. Didn't got any clicking sounds after that.
Sent from my Galaxy Nexus using XDA
This has been discussed at length here:
http://forum.xda-developers.com/showthread.php?t=1490335
Keep in mind that this happens on many devices. For the people who say they don't hear it, perhaps they don't know what to listen for or perhaps they are just lucky and their particular device isn't affected by the problem.
Sent from my Transformer TF101 using Tapatalk
cyanoviper said:
m2 doesnt even have the fix.
Click to expand...
Click to collapse
If that's actually the case then it must have been fixed in CM9 as I definitely had this issue.

[Q] Continous Vibration

Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
l_daruwala said:
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
Click to expand...
Click to collapse
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
jamidodger1 said:
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
Click to expand...
Click to collapse
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
l_daruwala said:
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
Click to expand...
Click to collapse
It hasn't done it for SMS for me but yeah it never did it on my previous phone either ZTE Blade
When my profile switch app change profile and take phone to silent mode sometimes makes my W too...
The only solution reboot...
Looks like this affects all GALAXY W's
l_daruwala said:
Looks like this affects all GALAXY W's
Click to expand...
Click to collapse
Yes, and it happens always the best time... meetings, driving...etc.
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Happens to mine, seems like it was only when Whatsapp and something else had a notification at the same time.
soulbkd said:
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Click to expand...
Click to collapse
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
soulbkd said:
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
Click to expand...
Click to collapse
Unfortunately mine too. No more idea.
Damn, mine is also REV 0.6 as well.
Still same problem
Mine also rev 0.6
Tried Rebel Rom, Bagux, Bionic Cow 2 v 7, stock DXLM3, stock XXLM8 , all still has the same random vibration.
And the vibration won't stop until you reboot.
Probably hardware related?
This happens to me since the first day I got this phone...
Honestly, it's annoying me !
Cause the only way to Stop it, is a reboot..
Sometimes it starts to vibrate in school, and as Im using a TPU SoftCase it's even more uncomfortable...
I thaught I was the only one, but seems like it affects all Wonders..
No matter which Rom I use, everytime the same Problem
A random time.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
same problem

Several issues with JB

Recently I bought myself a Galaxy Nexus after owning a Nexus S for 1,5 year.
I never had issues with the Nexus S (even with JB), however this seems a different story on the GNX.
My issues:
- Youtube doesn't play videos and crashes
- Gallery crashes when looking at videos. I get a black screen when playing a video but it doesn't start to play, when I press back the system doesn't react, pressing home returns me to the home screen.
- Face unlock doesn't start it's process and I'm redirected to enter my PIN
Any ideas? I noticed the factory JB 4.1.1 image is released, maybe I should place a clean image on my GNX?
Thanks for all comments!
Are you currently on a stock or custom ROM?
I have this problem here many and many times too with a stock rom.. Yesterday I reinstalled the factory ROM 4.1.1 but the problem persists, I think it's a bug in this version because in 4.0.4 doesn't have this problems..
I don't have this problem and I very much doubt many do. I suspect you may have a hardware problem. Probably faulty memory.
Sent from my Nexus 7 using XDA Premium HD app
Dr.Paul said:
I don't have this problem and I very much doubt many do. I suspect you may have a hardware problem. Probably faulty memory.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think is a problem of faulty memory, it is difficult to reproduce this bug, you must open a video in the gallery or on youtube, watch the video and pause, after a few minutes reopen a video and do that sometimes and you have the problem ..
I've never had anything like this happen on jb.. .
I don't have this problem - did you try deleting the Youtube app and reinstalling it?
It might be worth trying to do a total hardware reset if you have a couple hours.
superdx said:
I don't have this problem - did you try deleting the Youtube app and reinstalling it?
It might be worth trying to do a total hardware reset if you have a couple hours.
Click to expand...
Click to collapse
I've done it already, I've deleted the cache's app and the problem continues, it does not happen right the first time, occurs after about 10 times you watch a video and then watch again ..
It's a new phone. It came with ICS 4.0.1 which went to the OTA upgrade path: 4.0.2, 4.0.4 and then 4.1.1. So completely stock.
I also notice that the camera app doesn't come up (the same problem which does occur when unlocking with face unlock).
Pictures from the gallery show up without problems.
What are the best steps to have a complete hardware reset? Flashing the stock JB 4.1.1 factory image via fastboot?
If it's hardware defect, is there a offline diagnostic tool I can run on my GNX?
I appreciate all replies!
For me the only way to solve that is using the 4.0.4 stock ROM
RicardoSul said:
For me the only way to solve that is using the 4.0.4 stock ROM
Click to expand...
Click to collapse
I dont have problems on my nexys with 4.1.1
knudsen81 said:
I dont have problems on my nexys with 4.1.1
Click to expand...
Click to collapse
Today I returned my Galaxy Nexus to the shop. I will get a new one as soon they're back on stock.
I returned to my Nexus S which has JB, unfortunately it seems JB is still not as stable as ICS. Had some Google Talk crashes today.
Never had a crash on my Nexus S on ICS.
Edit: Nevermind I didn't read your last post completely.
Glad to see you're getting a new one
I'm also waiting for a replacement for mines (kept crashing randomly). It will arrive on thursday.
xanadu.dm said:
Today I returned my Galaxy Nexus to the shop. I will get a new one as soon they're back on stock.
I returned to my Nexus S which has JB, unfortunately it seems JB is still not as stable as ICS. Had some Google Talk crashes today.
Never had a crash on my Nexus S on ICS.
Click to expand...
Click to collapse
I think I figured out how to solve these bugs, here they stopped to occur after disabling facial recognition, use another way to unlock your phone and make sure that they stopped
Sent from my Galaxy Nexus using xda app-developers app
Probably the people who reported not having the bug doesn't use face recognition, I think this is the reason for very few people reporting this bug.
Sent from my Galaxy Nexus using xda app-developers app
I've never had these issues and I used face recognition since the first day I got the phone.
Meanwhile I got a brand new Galaxy Nexus, however after one week of use the same problems returned!
I wonder if an app or something else is causing these problems.
I have not had these issues, you probably have a faulty phone.
It can't be that I have two times a faulty phone? First one was delivered with the Google ROM, the second one with the Samsung ROM which I changed immediately to the official yakyu ROM.
xanadu.dm said:
It can't be that I have two times a faulty phone? First one was delivered with the Google ROM, the second one with the Samsung ROM which I changed immediately to the official yakyu ROM.
Click to expand...
Click to collapse
Turn off face recognition and test again..
Sent from my Galaxy Nexus using xda app-developers app

Xperia M touchscreen stops responding randomly

Hi, Im new to the forum but used roms for another device in the past.
I wasnt able to find information regarding to this trough days, my phone touchscreen stops working randomly on stock rom [15.1.c.1.17], have anyone had this problem? Is it sw or hw related?
Thanks, phone is awesome when the ts works but this is driving me crazy... thanks
If you haven't modify the software then it must be hardware related.
What modifications did you do? Did it have the problem from the start(when you bought it)?
matroxtube said:
Hi, Im new to the forum but used roms for another device in the past.
I wasnt able to find information regarding to this trough days, my phone touchscreen stops working randomly on stock rom [15.1.c.1.17], have anyone had this problem? Is it sw or hw related?
Thanks, phone is awesome when the ts works but this is driving me crazy... thanks
Click to expand...
Click to collapse
If it doesn't happen under specific conditions (for instance, while playing the game, or during the call), it is most likely hardware related, my best bet is that screen digitizer is either faulty or not connected properly to the motherboard. Have you dropped/spilled something on your phone? If not, you should return your phone for a warranty repair.
Its randomly occuring, its fixed after reboot or it will work itself again after a while, sometimes a couple of minutes others a couple hours, phone is new, bough on jan 17. Havent dropped it or spilled anything on it... problem is I updated from stock rom from the provider to an official by sony and dont have a backup of it :/.
Update to the newest version ends in 2.8 that's the newest one see if that helps
Sent from my C1905 using xda premium
dunc4n88 said:
Update to the newest version ends in 2.8 that's the newest one see if that helps
Sent from my C1905 using xda premium
Click to expand...
Click to collapse
Did that yesterday... worked for a while, almost for a full day, then dissaster happens again
Loos like it might by the digitizer at fault I would get it into a Sony shop for them to check it
Sent from my C1905 using xda premium
apparently is a physical problem... will have to left phone up to 10 day in service :/
thanks for the fast replies

Categories

Resources