Hi everybody.
I'm having this strange issue since FROYO update (first one that came with radio). Everytime I put a new update (or anything involving going to Recovery), when my phone boots up, I can get no sound during a call (I can't hear and can't be heard also) and more, the proximity sensor is not working either (screen remains lighted when close to ear).
If I put the phone on speaker, I can hear the other and I can be heard. Looks like the upper part of the phone is not working. The only solution I found until now is to turn the phone off, take out the battery for a minute or two and then, when I start the phone, everything is back on its track.
I've tried everything, going back to stock, getting the new (now old) FRF85b signed from Google (with radio in it). I received no errors during updates, I did wipe everthing, but the problem is still there.
Today I've updated to FRF91 and after the phone booted up, same problem.
Could be the radio of FROYO? Anyone else have this issue?
Regards,
Alin.
I'm having this exact same problem and I'm kind of freaking out because I have an unlocks bootloader and no warranty, however this just happened to Me today and I've been on froyo for almost two months
ok so i just solved my problem... by smacking the speaker end of my phone on my hand a few times..
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.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
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...
First time poster, so please excuse this thread if it's posted in the wrong section. I tried looking for a trouble shooting section.
It all happened yesterday after playing Duel Links. Audio working fine on my speakers. I put my phone to sleep, and went to work. Started getting to worked, I noticed my phone had no audio coming out of the speakers. I then tried plugging in headsets; nothing. However, bluetooth seems to work just fine with no problems.
It wasn't dropped prior to the problem, no water damage, didn't overheat. I believe it's a software problem, and could be a virus due to the 5 different Skype versions I downloaded trying to downgrade.
I've already factory reset my phone (5 times in a row; same for cache), the problem still occurs. Safe Mode doesn't get it working either. I have found a sort of temporary fix though, which involves plugging in a headset and restarting my phone. Audio will come out of the speakers, but never the headsets still. This only works for like a minute before audio cuts out again.
I thought trying to test it with USSD codes might work, but none of them will work besides the IMEI one. All the others give me "Unable to process request". The last thing I want to do is RMA my phone, because I already have once, and it was a pain having to deal with Alcatel. Took a month from sending to receive my phone only to find I had to pay full price for a new one. I'll probably try rooting my phone and flashing it to see if that will work.
Any other thoughts on what to do/try? RMA will be a last resort.