MT3G can't receive phonecalls - PLEASE HELP! - myTouch 3G, Magic General

Hi!
My first post here....
I rooted my MT3G and installed CyanogenMod latest version. It was working fine for a week or so (except for "Force Close" issues, but I took care of that by removing task bar), and now since last Friday I'm not receiving most of my incoming phonecalls. My friends tell me they're trying to call me, but get disconnected right away. Phone doesn't ring, I get no missed calls, and it won't even go to voicemail. Occasionally though some calls will go through.... Outgoing calls and everything else seems to work fine. Also, when in the car and connected to bluetooth system and someone would call my phone, the bluetooth recognizes incoming phonecall, says "call from...", and doesn't even proceed with the number, just says "call ended".
I tried to reinstall CyanogenMod; called my phones several times from different phones, worked fine, but later in the day started getting messages from people saying that they can't reach me.... calls are dropping again.
Please advise if you have any ideas to solve this.
Or if someone can tell me how to reverse the upgrade I did, I would like to give it a try and see of it fixes my phone.
Thanks!

My phone works just fine with CM, maybe it's a hardware problem, if you don't get it fixed by next week I suggest unrooting it and seeing if the problem still persists. If it does, maybe take it back to your carrier and get a replacement.

Thanks, Anartic!
Yes was considering unrooting it. Could you tell me please how to do it? Or give me a link to that info?
Thanks!

Related

Cyanogenmod - cannot phone my phone, no SMS alerts...

Hi Everyone, I have searched for an answer to my problem but cannot find anything.
I have upgraded my G1 to Cyanogen, and everything works fine except I get no notifications to text messages, they just arrive, with nothing to tell me they have arrived.
Another problem is when I call my phone, it rings once and then gives an engaged tone. There is nothing coming up on the phone to say I have a call, however it does put the call in my missed call list...
I have checked GSM call settings but all forwarding is disabled.
I have just upgraded to the latest cyanogenmod with the updater software, however I still have the same problem.
Another thing that doesnt seem to work is the home button, and camera button, and the phone no longer locks.
I am at a loss for what to try, apart from trying to flash the phone back to its original state.
Any help would be greatly appreciated.
When you did the update did you wipe first? You can fix your problem, but you need to wipe your phone. So wipe, then reaaply the update. This does happen to people from time to time, and I've yet to see the direct cause or solution. A possibility is something in the dalvik-cache.

[Q] Unable to make calls?

I've been using my Nexus 4 as a phone by using Groove IP until I got my Straight Talk SIM. Now that I have the SIM, the native phone app won't work right. The first call will allow me to hear the other person, but they can't hear me. Every call after that, I can't hear them, and they still can't hear me, and unless I reboot, every other call is like that. Here is a logcat of the first call, and the second call. Groove IP still works. Any ideas on how I could fix this? Running bootloader locked stock rom.
I had a problem where I couldn't hear other people, and they couldn't hear me, and I could not for the life of me find out how to fix it. I was running rooted stock, it had been working fine, and then just one day this problem popped up. I assumed it was a problem with the phone thinking a headset was still plugged in, but all those fixes didn't work. Then I just reflashed the stock ROM on the phone (no wipes), and it worked again and the problem hasn't come back. Not sure if that will help you, but it might be worth a shot.

[Q] No Voice (incoming or outgoing) on Nexus 4?

OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.

Need Opinions And Thoughts Please

Ok ive been pulling my hair out for a while with this problem so im really hoping you guys can give me some answers or suggestions to help me fix it My Girlfriend has the Galaxy S5 SM-G900V. Baseband version G900VVRU2BOG5 So rooting or custom ROMS is out of the question so that leaves me with trying to diagnose and eliminate this problem without a easy way out.
Ok the problem is once she updated the phone to lollipop she had all the common problems that come with it over time i have slowly eliminated them with factory resets and cache cleaning and such although i have one problem that not even verizon can figure out. The phone itself with occassionally and randomly just refuse to make or receive calls its a very odd problem because the phone will send and receive sms and mms just fine when this happens but when we try to dial out it just sits at dialing and never connects, when calls are dialed into the phone it will ring 5 times or so then go to voice mail or just go straight to voicemail altogether without ever ringing the s5 shows no sign of anyone ever trying to call at all no ringing no records nothing. Once in a blue moon it will ring 4 times on the dial in and then the s5 will start ringing around the 5th ring which is extremely long time IMO. This happens very randomly and in all different locations i have disabled call blocking and auto reject i have tried safe mode to only experience the same problems, i have factory reset several times. Verizon opened a ticket with there tier 2 techs and network development team to check out the issue they tell us everything is completely fine and theres nothing they can see wrong. But they do not deny the problem is there they just cant explain it. Now get this, This is the second phone that has done this to her Ther first one had the same problem and was warranty claimed this is the second phone and same exact issues. Im not sure what else i can do i am a very tech savy person and this one has got me stumped the only thing i can see thats odd for me is the phone has 3 Phone services running in the background But I believe this may have something to do with the Touchwiz Easy Or Regular Home UI althought im not sure why it would use seperate apps. Anyway any input would be helpful Thanks

No Call Notification

Haven't had a lot of luck with questions here for the last little while, but maybe someone has an idea as to why this would happen. My wife tried to call me 6 times yesterday. Not a single call came through or registered on my S7 Edge. She said all calls immediately went through to voice mail. When she got home, she stood right beside me and tried again and again, I was not notified of the call and it went right through to voice mail.
The phone had recently been rebooted. DND was not on. All sounds were on. The phone is not rooted and no apps like Greenify or anything like that running. After her last unsuccessful call to me, standing right beside me, I called her and it went through without an issue. She then tried to call me back and it worked. A minute or so later I received notification of her 2 voice mail messages from her previous calls. It's like the phone was in an extreme deep sleep. Which is pretty annoying considering I use the phone as a phone and I need calls to come through when they are made.
I took the phone into my carrier and they gave me a new sim card to try. I didn't have any issues with the previous sim card other than the issue from time to time of the first call I place being dropped and then the second call going through without issue. The signal is not fantastic in our condo, but I've never had someone tell me they have tried to call me and simply gone to vm before, so I don't know of any time of this happening previously. My wife had never had problems calling me before at all.
Anyone know what might have caused this?
No answers to this post,. Guess no one knows. Just another bizarre Samsung issue. Had it happen again today. My wife had to send me a Whatsapp message saying she couldn't call me. She said she called over and over again. No voice mail, no nothing. Never rang on my end or registered a call at all. Phone just didn't work until I called her and then she called me back and it worked. So sick of this thing working when it feels like it. Checked signal Not great, but no better than her signal and she never has any issues. She said she would call, it would just drop. No ringing, no voice mail, no nothing. Just call and then drop sound. Over and over again. Good thing this phone is only a $1000 device. Works great.
I don't have a solution for your problem, but had a similar issue when phoning my wife. It would ring on my side, but not on her side, then goes to voicemail. 2nd or 3rd time the call would go through to her to answer. Her phone wouldn't show any of the other calls. She was with a specific service provider and I moved her over to my provider. That is when the problems started as she was ported over to my provider. In the end it was on the provider's side where the problem was. They made some changes on her number profile and she could receive all calls and not random ones. Don't know the technical side of what the provider did, but they did admit they created her "call profile" incorrectly. Perhaps it's the same with you, that there is a setup on your profile that is not correct.
Thanks for the post, but I have contacted my provider. We use the same provider. Same settings. They reset everything for my phone and I reset everything on my end too. Still no solution. She does not have the same issues. Same phone. Same provider. Just sucks when you don't know if someone is trying to call you or not and if the phone actually works or not. I just want a phone that works all the time without having to worry about it. At the end of the day, that's all this is....a phone. If people can't call, well, that's an issue. I'm currently looking for work so it's even more important now than it's ever been.
Sorry to hear that you went the route of the provider and still no resolution. Maybe someone else can give light on the subject...
Deleted
wtwo2 said:
Solved
Click to expand...
Click to collapse
Huh?
No it isn't.
TheIgster said:
Huh?
No it isn't.
Click to expand...
Click to collapse
Sorry..solved my problem by flashing stock..first doesnt work..but now all is good
wtwo2 said:
Sorry..solved my problem by flashing stock..first doesnt work..but now all is good
Click to expand...
Click to collapse
OK...What does that have to do with this thread that I created about my issue? I feel drunk...I think I need another drink. WTF?
What do you want? I had the ****ing same issue..solved it and deleted my message..
Try to flash some stock firm with Odin.. solved the very same issue for me!!!
So why did you delete the message then?

Categories

Resources