Hey guys,
Just started to have this problem where the phone is always stuck with the speakerphone activated when i make or take a call. I've looked through the setting and i've searched through the forums with no answers. I did look through and saw that people with older models and older OSs have had this problem but no one yet with the skyrocket. As of now the phone is rooted on the stock rom with nothing crazy installed. The phone was rooted a couple of weeks ago and worked fine and then all of a sudden the speakerphone issue happened. I didn't update to the newest OTA update as well. Any answers would be great. If i need to return it so be it but i'm hoping there is an easier solution.
Thanks
JD
pulled the battery and let it sit for a bit and started it back up and it looks like everything is working now.
seems like a random bug
Related
Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...
Hi,
I tried to upgrade my ROM on my Motorola Defy, quite a while ago now. Once completing all of the steps and the new OS was installed everything seemed to work fine, however I couldn't get a signal from my phone. I reset to factory and still, no signal. Luckily I had just bought the phone, had a very friendly salesperson, and he just swapped the phone out for a new one, no questions asked.
I have recently been getting the bug to root my phone again. However, I'm scared to death that I'm going to fudge it and be left with the same issue. I never really found any info as to why the phone did what it did, or how easy it would have been to fix. I'm wondering if anyone has come across this problem?
Thanks!
Ted
I have been flashing roms and messing with stuff on my Galaxy s2 for a few months and haven't had any problems. So I decided to get my son the Nexus S. We have had it since July. When we got it it was running Gingerbread. I updated it to 4.0.4 without rooting from a thread on XDA. Everything has been working fine till a few weeks ago. I would call my son but he wouldn't have a missed call. It will ring and then go to voicemail, so he should be showing a missed call. I have his phone this week so I have been trying to figure it out. It seems to get into some kind of loop. If someone calls and it doesn't ring, I can call someone and it won't go through. Of course I have called AT&T but I seem to know more about android than they do. So last night I rooted it and flashed paranoid android 2.22. The same issue happened again this morning. I have changed to radio from auckj1 to aucke1 thinking that might help. Sorry for the long post but I was wondering if anyone else has had this problem? Could this be a kernel issue or radio issue? I know that there are programs out there that say you can put it back to stock for replacement but I don't know if that is true or not. I need some help from people smarter than me. Thanks!
Hey guys!
It's been a while since i visited these boards. Sadly I'm faced with a problem that may make me go back to some stock 2.3.3 ROM.
I've got the CM10 on my P500, used it for months, was quite happy with it (tho didn't really play around much with it).
Well, untill around 2 weeks ago when my phone stopped playing ringtones, making me miss calls when i was sitting right next to it. Quite annoying, tried changing all known setting that could cause this. It did vibrate on vibrate-only mode, except for that no results.
Finally today I got fed up with things, restored default settings and behold, now the phone doesn't even display incoming calls. Though they do show up later in missed calls. All of this is crazy :silly:
So, my questions are. Did anybody else get this problem? Any new version of the ROM or patch to fix this? Should I just find myself some old sure-proof ROM, cause I don't even play around with all the new 4.1.2 toys?
Anyways, I'm awaiting your replies. Thanks a bunch in advance.
Cheers fellas!
Hi! Until yesterday i was using Bytecode's ParanoidDroid 3.15 (nice JB 4.2 rom, thanks Bytecode!!!). Couple of days ago i had a ringtone problem also: the phone begin to ring, but only for a second, and then stopped (i keep my ringtones on my sdcard). I don't know the solution because i switched roms - for that bug and speaker bug - searching for a stable one. Now i'm testing 4.0.4 ICSPlus, and hope to be the "right" one.
Same prob.
scholarTD said:
Hey guys!
It's been a while since i visited these boards. Sadly I'm faced with a problem that may make me go back to some stock 2.3.3 ROM.
I've got the CM10 on my P500, used it for months, was quite happy with it (tho didn't really play around much with it).
Well, untill around 2 weeks ago when my phone stopped playing ringtones, making me miss calls when i was sitting right next to it. Quite annoying, tried changing all known setting that could cause this. It did vibrate on vibrate-only mode, except for that no results.
Finally today I got fed up with things, restored default settings and behold, now the phone doesn't even display incoming calls. Though they do show up later in missed calls. All of this is crazy :silly:
So, my questions are. Did anybody else get this problem? Any new version of the ROM or patch to fix this? Should I just find myself some old sure-proof ROM, cause I don't even play around with all the new 4.1.2 toys?
Anyways, I'm awaiting your replies. Thanks a bunch in advance.
Cheers fellas!
Click to expand...
Click to collapse
Hi there. Actually i have this problem too. I flashed Rashed's cm10 about two days ago and when somebody calls me it doesn't ring. I thought that the problem was my phone, but now if there are more people with that problem I don't know what to think anymore..
Calls drop often. Usually within the first minute, and then every time when Im calling back after 10sec. The phone itself does not lose signal. Strange thing is, if I'm getting phone call after first/second drop, phone continues connection without problems... But Only when Im receiving a phone call not when Im trying to re-call someone.
- I tried replacing my sim and the issue persists. No problems with other phones using this Sim (even in the same locations).
These are pretty annoying issues. Anybody else experiencing them? Is there a different radio I can try for the phone? Is there any log I can access showing a reason for the call drop, or any trouble shooting I can do? This seems to be independent of WCDMA Only/Preferred/GSM/WCDMA (Auto) settings. Or if, how to change these settings?
Note: This has nothing to do with the network. I've been with the same company (Orange Europe) for about 2.5 years, and have never had this happen before. This has been consistent since I got my OnePlus (about 1 week ago)
That's true. I'm experiencing this as well for quite some time now. At first I joked and said: Hey, the NSA joined our conversation.....again. But after some time it really annoys me. This has nothing to do with the ROM or kernel as I have tried out various combinations. What I found out is that it got better after I returned to stock CM 11s with stock kernel. But it's not gone completly.
Honestly I neither know how to fix it nor what is causing the problem. Try to reflash the CM11S 25R firmware and see if it gets better. I think something is wrong with the modem software since CM11S 22R,25R and CM11 builds are using the same modem software. Maybe the announced update for the end of this month or early next month will fix this. I really hope so because a phone which is not able to hold a call, can't be considered as a real phone.
Oh im pitty You, If You'll get something just please let me know. Any advices or help will be appreciated. Maybe waiting for new CM relase will solve the problem, I do rly like this OS even with so many bugs... there is always an option. Move to stock 4.4 published by OP on official website.
Anyone else facing the same issue? Was there ever a fix for this issue? I'm on 38R and still encountering this issue
Same here.
See this thread for answers and work around. No solution as of yet.
http://forum.xda-developers.com/oneplus-one/help/dropped-calls-weak-lte-signal-t2916659