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?
Related
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..
Hey guys,
I updated my SGS to Froyo 2.2 yesterday and it all went smoothly (at least I thought it did). i used Odin to flash the Froyo 2.2 update and it did. Everything was going fine and I rooted the SGS and applied the one click lag fix (via the OCLF app).
The problem lies with answering incoming calls. When someone calls me it disconnects the call before it comes up on the screen, and shows a no-service icon. This then disappears after a few seconds and the phone returns to its "normal" state as if the phone call never took place. i then get a call reminder text from my carrier (Orange) which says I have a missed call from whoever rang me.
I have searched for hours and not come up with anything useful so I am really hoping you guys will be able to shed some light on the situation.
Thanks for your time,
Charles
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Are you going through a SMS app, like Handcent, or using the stock messaging program? I had a huge delay in sending/receiving texts when I used those programs. If you are using a non-stock program, try using the stock one to see how it responds first.
Yeah, i am using the stock app, but ill try using handcent and see if it works like that
Sorry, Handcent was the one giving me problems, not the stock app. How is the other data flowing, like browser and what not? Seen any drop in data coverage or anything? Do you have the newest baseband radio?
jlopez512 said:
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Click to expand...
Click to collapse
Do you have a "low space" warning? I know I've had problems receiving mms/texts when I'm low on internal space. Once I cleared up the space (>19MB Free I believe) by uninstalling a bunch of apps I never use, all the texts came in
Just a thought
Well, i got it fixed, went to the sprint store, (unrooted of course) and they fixed it within an hour, they reset the entire phone, not the same reset as Settings>Privacy>Factory Data Reset.
text and phone calls not getting through
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Azag Thoth said:
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Click to expand...
Click to collapse
You might have better luck asking on the dinc forums.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
not just a dinc issue...!?
yea, i know, i put it here because, it seems like same issue this guy was having and i have been searching around and have found many instances of the same problem on many different android phones.
i am un-rooting it and reinstalling the original software and taking it into Verizon tomorrow to see if they can do anything. should have done it sooner but every time i would try a fix it would seem like it was fixed for a day or so and then back to the same thing.
i will copy it over there just for posterity, and hopefully i can amend it tomorrow evening with the fix and a solved!
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
Hello guys
Ran into a snafu yesterday, clicked home a N6 demo-ex from one of the internetstores here, it was cheap and I've always wanted one. Of course it came with a pre-unlocked bootloader and everything else you'd expect from a used Nexus, but I wasn't too bothered about that, I would have unlocked it myself anyways. Flashed MM on it as soon as the images were available. I played around with it for a few more hours, then late last night I decided I should move my simcard to the N6 and try Speedtest and a few other goodies. Speedtest went just fine, got the usual 64 Mbit over LTE, then .. I'll call my automated bank just to check the earpiece and speakers. "Dial .... call ended". Try again. "Dial... call ended". Put the simcard back into my Nexus 5, dialed the same number, worked perfectly. Back into the N6, same number, it dials, then just as it's supposed to start ringing, "call ended". Has anyone got any ideas as to what could be wrong here?
Done so far to find the error:
*Reboot *duh*
*Reflash MM
*Flashed 5.1.1, thinking it was a new modem and my simcard didnt like it. Sim is about 2 weeks old by the way.
*A couple of factory resets, just to be sure
This is the very last Nexus 6 these guys had on the shelves so I would really, really rather not have to return it but of course a phone that you can't use for phonecalls .. I already own a Nexus 7, don't need a miniversion of it. Bright ideas or even far fetched guesses appreciated!
Hey bud, I had a similar issue with my phone as well and the way to fix it is by rebooting exactly 6 times in a row....literally. Power on, power off power on power off etc........ Ive encountered that issue several times, it usually happens when i left my phone die and then reboot after full charge. I could only use data, no voice/text and sometimes it would be backwards, no data, voice text only