Related
I have no speakerphone sound on my captivate. No 3g noise on boot, no speakerphone, no pandora, youtube, or ringtones... The phone will vibrate, and play music out of the headphone jack, or while in a call, but not in speakerphone.
This started while i was running Cog v5.5, but I did have sound initially in 5.5.
I am now running 8.1 and the same thing is happening.
I posted in that thread and 10+ pages later, didn't get a response.
I'm wondering if there is just a setting I missed, or if i need to do more of a factory reset when i install beta 9 tonight. by more of a factory reset, when i upgraded roms, my internal memory card still had all of its data on it from the previous installation.
Please help
Don't know if you saw my respose in the other thread.
I had this same issue recently. The fix for me was to take the back cover off and gently press the speaker back into the phone. Apparently it was just the slightest bit loose. Hopefully that is all that is wrong for you as well. I too did a system wipe an re-install for this issue, but the speaker being loose was the problem.
tried that, and same thing. If i cant figure it out soon, I may just restore it to stock, and trade it in with att
kwhee07 said:
tried that, and same thing. If i cant figure it out soon, I may just restore it to stock, and trade it in with att
Click to expand...
Click to collapse
My first one did this after about 2 weeks. I took it to AT&T and they swapped it out for a brand new one.
I hope thats not the case, but if I have to, it should be pretty easy to get back to stock config
speaker broken
my speaker is also not working properly. Works intermittently, requires lots of real hard pressing down on speaker face to get it to go, etc. it is not loose, so i think this could be something in the software of the phone....I am stock all the way, 2.1 and not updated. I am also beyond 90 days on my phone.....any ideas?
W
Wow, I had the exact same issue come up, and pressing on the speaker actually fixed it. Three cheers for percussive maintenance.
5 days old now and 2 recurring problems i have noticed.
1: Sometimes when i unlockthe phone the lock image stays halfway and then the phone hangsand then i have to hardboot it.
2: I travel a lot and change sim cards. So when i land and change a sim card and make a call the other side cant hear me. So i have to restart the phone and then all works well.
Both these issues are recorded not 100% but have happened to me 3 times in last 5 days.
Anyone facing similar issues.
I assume this is just Windows and maybe within the next couple of updates this MAY go
Can't quote on the multi-sim issue but having my phone sinmce 21st Oct i've never had the Unlock problem you're stating. I've had the phone crash on me twice i think, but that was simply the screen becoming unresponsive (both time whilst in the MarketPlace. Hmmm.....)
You could have a faulty unit.
I have had the loss of voice issue a few times now.
Phone someone up and they cant here me. Also if I go to put it on speaker phone it doesn't go very loud.
Take the battery out, put it back in and it all works again.
Is this a hardware or software fault ????????
My guess of it happens at random then its not hardware. Its a software glitch. Also for me it happens when the battery is low.
Yes the screen has become unresponsive and then had to reboot.
Don't remove your battery just keep the on/off button pressed for long. It works.
onewheel said:
I have had the loss of voice issue a few times now.
Phone someone up and they cant here me. Also if I go to put it on speaker phone it doesn't go very loud.
Take the battery out, put it back in and it all works again.
Is this a hardware or software fault ????????
Click to expand...
Click to collapse
This happened to me also, the speaker phone is very very soft, you can barely hear it I hope they fix this on the next update.
Market also crash on me earlier, just blank white screen, had to turn off and on again.
did you turn up the volume on speakerphone? or was it using the same level as everything else?
first couple of weeks I had several times where an incoming call I couldn't hear the other person talking. This happened about 4 or 5 times in the first week, but hasent happened for about 7 to 8 days now so I'm wondering if it was one of the HTC hub updates I've recieved.
If it happens again it's going back to the shop
who can help me ,my nexus one can not make any sound,
I'm not sure if i can help you.
But I'm pretty sure anyone who does needs a little bit more information.
Is your N1 rooted or not? If yes which Rom do you use?
What happened before it stopped making sounds?
I could imagine that could be usefull for people trying to help.
Make a complete wipe and see if it helps
Hi!
Initially had this issue when I bought my N1 (a store sample) and it re-surfaced a week ago. Now this is from experience only, so I'm not pretending to know whether "your N1 fails to initialize soundboard for reason X"....
Issue that I solved succesfully is this:
I had no sound from the phone speaker (no ringing, no alerts, no music) - and actually all phonecalls were also silent (and ended up rebooting the phone about 15 secs into the call). What's freaky is that I was able to play music, hear alerts, take calls etc. over my headphones!
I was suspecting something to be wrong with the ringtones from the SD card.
So before wiping your phone (even with nandroid recovery it's a b*tch of a job) try this: Reset all alert tones to some default tones (which are in the rom). Turn N1 off, remove SD & sim, then let it reboot. Then power down, insert sim, keep SD out. Reboot. You should get the tones/sounds/in-call audio back after a few tries of these combinations. You can also try unmounting/remounting the card repeatedly. Also, it may help if you have a second SD card ready (empty or without). When you get the sound back, you can again start using your custom tones off the SD card.
(I usually wipe any unused ringtones in the process, and have even removed the tones from my card, and then reinserted them on the SD, which also seems to work after a few power-down/power-up cycles.)
Sorry, it's totally "unscientific" but if you have, say, half an hour to a full hour to spare do the above and your N1 will be back on track.
Pistolero0 is right we could use a little more info. Another thing that I would like to know is can you play sound through the headphone jack or Bluetooth or is it just the phone speaker.
Uh-oh... Just when I answered, I got the same problem again. This time, it's taken me a day to cycle/recycle. I've gotten the sounds back twice, only to lose them due to a random re-boot. I'm still suspecting it's a question of the SD notifications/ringtones messing up something in the system. (Or it's due to a certain app getting installed or uninstalled.)
So, the sound sometimes comes back, sometimes doesn't.
So, I'm also asking for help on this one....
Symptoms
No in-call audio whatsoever
No audio through internal speaker (the ear-speaker)
No audio through the speakerphone-speaker (on the back)
No notification sounds, no alarm sounds, no ringing.
Music cannot play (the track doesn't seem to advance).
All audio works over bluetooth headset - I can hear notifications/ringtones/alarms, screenlock sound, and even music (winamp & stock).
However, I still cannot make a call over BT (I do hear the ringing, but the audio doesn't connect on an incoming call. Outbound calls are completely silent on BT phones as well.
No sound whatsoever over the standard plugin HF-headphones (the ones that came with the N1).
So my plea is also, how do I fix this? (Wiped & Nandroid-backuped once, but the problem resurfaced, so I don't think that's the thing, then).
EDIT: Now trying the passimg method (FRG83-->GRI40-->root-->GRJ22+SU.zip) - I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while
EDIT: Now trying the passimg method (FRG83/D/G --> GRI40 --> root --> install GRJ22 update + SU.zip via clockwork) — I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while
Click to expand...
Click to collapse
What a bummer... Froyo, but NO sound. [O]I guess it is a hardware thing then after all, despite all the evidence I've seen so far?[/O]
RESULTS
Some hours later am now back on rooted stock GRJ22, but still no sounds. This must then be a hardware thing - albeit one that doesn't manifest itself always.
Suspecting something is wrong with the 3,5mm plug? (Or a wire is crossed somewhere, which silences the ear-speaker and speakerphone speaker alike).
Still suffering. Anyone got an idea?
Did anyone get their problem solved?
Well I've never had this problem but can I ask you a question when you flash do you use 3X system wipe and 5X data/cache wipe because I don't really think this is hardware cause or else in theory if it is hardware the problem should stay even after a reflash unless it is consistent with something else (example every time you hit X amount of memory used, every time you hit X amount of run time, etc).
So try the 3X system and 5X data/cache and see what happens.
Dude Random21 said:
So try the 3X system and 5X data/cache and see what happens.
Click to expand...
Click to collapse
You mean first do the system + data/cache wipes, then flash?
By system wipe, you mean the usual reset-to-factory status kind of wipe?
And how do you proceed with the data/cache wipe? Like, with Titanium or some other choice?
Sorry for the n00biness, I try not to flash schtuff too often. Anyway, I'm going to try your suggestion out as soon as I can.
Sorry for the late reply I haven't had much free time lately but why I say system wipe I mean either use temasek system wipe (if on Amon RA) or the built in wipe system option in clockwork mod depending on your recovery. And for data/cache that is the factory reset.
Update - One Factory Servicing Later, a fix of sorts
Okay. After two weeks of consternation I walked to the service center.
6 wks later (that would be today) I got my N1 back....
Motherboard had been replaced, rigid flex had been replaced, antenna had been replaced. Warranty repairs on level 1 & level 2 had been done. Anyway, quiiiiite happy now.
And yes, I do have sound. Luckily, I was still within warranty, and will continue to be. Lovely.
(Presently going back the FRG83 - FRG83D - FRG83G - GRI40 (gingerbreak root) - GRJ22 route).
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.