Here's the deal.
I had CyanogenMod 5.0.6 installed, and two days ago I installed Froyo.
It was smooth sailing until today evening when I try to call someone and hear dead space, although the phone indicates that the other party picked up.
It worked just fine a few hours before, nothing changed.
I reboot it, just in time for an incoming call which I take.
I haven't been able to make a call anywhere (including voicemail) except, for some strange reason, to google voice (and it appears I am able to call anything through google voice "to place a call, press 2").
I tried flashing the 2.1 radio and going back to CyanogenMod 5.0.6, but that didn't help.
I then flashed the update to 2.2 again, but it's the same deal.
What's going on, and what should I do now? I got the phone 5 days ago, rooted and unlocked the bootloader and now, of course, have no warranty so I can't really send it in.
It appears that the Froyo update isn't at fault here.
Please help...
It appears that the problem fixed itself. I woke up to find everything working purrfectly. I don't get it - was there a problem with AT&T yesterday night or something?
About a week ago I noticed this problem happening and I'm not sure why.
Every time I answer my phone it answers in Speaker mode.
So for example if my phone is sitting on the table and a call comes in I swipe left to right to pick up the call. Normally at this point I would put the phone to my ear.
But over the past week I have noticed that when I answer the call the speaker is on and I have to answer then turn off the speaker then put it to my ear.
Can anyone help with this problem!!!!
Not sure if it's relevant but I have the following on my modded SGS
Go Launcher EX
Go Dialer
Go Contacts
Go SMS
They have all been on the phone for over 3 months with no problems.
The rest of my phones details can be seen in my sig.
I too have been experiencing this problem! ANd it too just started recently, I ahd no problems before as well, Im running Darky 2.3.4 though, but I too have Go SMS, perhaps its a recent update? Im going to uninstall and see.
It appears that the problem has sorted its self out ... for now !
I turned off the phone and back on again and it stopped answering the calls with the speaker on.
Lets hope it stays like that
ive read thaat the problem at least for some disapeared after updating gosms or gocall app or somrthing like that so keep your apps up to date
Yes the problem is fixed, just update; and then restart your phone.
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...
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840
I have been having troubles with my O2X ever since I did the LG online upgrade to baseband 0725-V10? with Froyo.
The main problem was dead periods for approximately 3 to 4 seconds while on calls.
I tolerated this and waited for the official LG Gingerbread update thinking it would fix the problems.
After upgrading to Gingerbread, not only did the dead periods continue, but I had a few new problems:
- people were sending me SMS messages which never arrived
- people would try to call me and get a disconnected signal
- I would occasionally get failed SMS messages when trying to send
- I would occasionally get a dead tone when trying to make a call
- people were complaining that they could hardly hear me during a voice call
Last weekend I decided to try fixing it myself.
I followed Paul's instructions and back-graded to the old 0622-V20a baseband for Gingerbread to see if this would fix things (I left LG Gingerbread on the phone).
I thought I had smashed the problem until today... when I had the phone tethered to my notebook, the phone "locked up" and would not allow me to call or send an SMS.
Going in and out of airplane mode was enough to fix this... but it was very disappointing that the phone is still not working properly.
In addition, for some reason, the phone now sometimes switches to a strange screen after sending an SMS.
I am afraid to forward-grade to 0725 again because it seemed to be worse than 0622.
Does the problem sound like the baseband, Gingerbread or other?
I have downloaded 0725-V20l and 0725-V20q and am toying with the idea of installing one of them.
Judging by the symptoms, does anyone know whether one of these two basebands would cure the problem?
If not, do I have to bite the bullet, root the phone and lose warranty, and maybe install Modaco or another version of Gingerbread?
Thanks