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.
Related
Hi All.
I've persevered with this problem long enough and I'm reaching the point where I'm ready to send my phone back and ask for something else.
The problem is, seemingly at random, the phone loses the notification settings for SMS, MMS and reminders and silences them all and turns off all display messages.
The only way I catch a message coming in these days is to have the phone on the desk and watch for the screen turning on.
It leaves the volume up for the phone ringing etc but switches off messages.
It's absolutely doing my head in. I've googled but noone else seems to be reporting similar messages so I'm wondering if there is something really easy I'm missing or is it a hardware thing some how.
Anyone got any ideas? Filaing that, has anyone got a backup of the original UK T-Mobile ROM that I can put back on?
Cheers,
Smiffy.
Exactly the same is happening to my dual, after I upgraded to WM 6.1! It's really annoying.
I reported the problem to Customer Support, but they only recommended to perform a hard reset
Of course I did, but nothing happens.
I found the registry keys which are supposed to control this, but it's useless for me - Maybe someone can find a way to keep the settings in read-only mode or something
I hope HTC release a hotfix for this problem asap!
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!
So, I went to make a phone call earlier and realized I hit the wrong number. I ended the call immediately and then immediately tried to call the right number and the call just ended before it even rang. Now I am unable to make phone calls as every time I try to call any number it says calling and then the call just instanly ends. Anyone have any idea what is going on?
First option would be to power off and pull the battery. If it doesn't work after trying that, than second option would be to perform a hard reset.
Regards,
Tom
are you running the stock rom, or are you rooted with clockwork recovery installed, and running a different rom?
I have definitely tried rebooting, removing battery, sim, etc. I have now discovered that this only happens when I am at work. I am going to have to do more extensive testing to figure out exactly where I can make calls and where I can't but could it have something to do with which tower I am connected to? I have full signal and data and sms work fine.
*edit* I have not rooted it yet or installed a custom ROM.
Okay, well. Now it appears to be working. Now I'm really confused. Anyone have any ideas what is going on?
nope, it sounds nuts to me.
i would recommend using the phone a lot and trying to recreate the problem under specific circumstances. perhaps its a faulty piece of hardware.
As the title says, I have no sound from the earphone during voice call. Also, when trying to call somebody, it shows on their phone but they can't hear anything from me.
The problem appeared suddenly, without any intervention from me.
I've tried, without any luck, the following:
- battery pull (several times, to be exact);
- SIM change (also switching operators);
- nandroid backup + data wipe + restore;
- I was running the SAFE 1.37 ROM and had it rooted. I flashed to "not so safe" 1.37 ROM from shipped roms, still nothing.
EVERYTHING else works perfectly on the phone: SMS, mobile data, etc etc.
I'm quite desperate at the moment as I feel I've tried everything I know and I'm thinking it might be a hardware problem that will require me to go back to the seller with it.
Has anyone else experienced this and solved it? I've tried searching on google and here on the forums, couldn't find anything.
Thanks for all your help.
Well I did go with it to the service center.
Should take them no more than 15 days to tell me something...hope it doesn't take that long, though....
In the meantime, if anybody knows anything about this problem, please do post...
It may not help me but it may help others.
Got it back from the service centre today.
Apparently it was just a hardware problem : they've replaced the earphone.
Everything back to normal now, topic can be closed.
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.