So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
Does anybody else have this problem? Just got this phone. It's not rooted yet and I'm using the stock Touch Wiz SMS app. When texting back and forth with somebody, I'll receive a normal plain old text from the person and at any given time, one of the newly sent messages I receive from them will contain part of an older message that's still in the thread. It's like part of an older message got hijacked and inserted into the newly sent message, and sometimes part of the newly sent message has been omitted. Very strange...and very annoying... Anybody have any ideas?
Is it with only certain people? Sounds like someone you're texting with has a strange SMS program that's doing this.
I asked what phones these other people have and they have the Motorola Razor Maxx, Samsung Galaxy SIII, Motorola Droid 4, and the Motorola Droid Maxx HD. All are also on Verizon with non rooted phones and are using the stock SMS app. No idea why it happens but I'm wondering if the problem is on my end or on their end. Any ideas? I'm stumped for right now...
Hello, have a question and was wondering if any one else has had this issue with the infuse. My wife's phone some times will not receive calls, but will get a notification that she has a voice mail. Can receive text's, she will try to send a picture and will have to shut off phone and turn it back on in order to get it to send the picture. The phone is not rooted or any thing, it is stock. I am wondering really two things, first if any one has had this issue if so how to fix it, or if maybe if i root the phone and flash a custom rom on it would that maybe fix the issue. Thanks for any help with this any one can give in this matter.
I have an issue that I have no idea what causes it. Every few weeks or so I am not able to text a specific person or call them. I can be on any Rom and kernel combo and the issue will still arise. The messages will send but they never receive them and when I call, it doesn't show that I called on their phone. The only way I have found to fix my issue is to flash a TW Rom at which point we can call and text again then I flash back to AOSP and it will be fine for a few weeks. My friend has an iPhone, which I believe might have something to do with it. When this happens I can call and text any other contact and they can call and text any of their contacts but we can't contact each other. I don't know if the issue is me, them or Verizon, which we both have. If anyone has any insight or has heard of this, any info would be greatly appreciated because it gets annoying having to flash a new Rom every month. (Sorry for any grammatical errors, I'm typing this on a tablet.)
My buddy and I both have androids, he can get my texts but the ones sent to me will not go through. We can call though but the text issue has been happening on three phones. I think it's an issue on his end. He's bone stock.
Sent from my SCH-I535 using xda app-developers app
Recently updated my T-Mobile LG G2 to the the 4.4.2 update. Before then update, anytime I got a text message, my screen would light up. However, after the updated it doesn't do that anymore. Anyone know why or having the same problem?
At work I use wifi-calling since I don't get service and if I need to send a MMS, I use the stock app. I know I can get a 3rd party app, but those apps don't send MMS since there isn't data available.
Thanks for your help. Would love to get the screen to light up again!
I just updated today and am having the same issue. Tech support thinks it may be a glitch but not 100% sure.
Same issue here. I haven't found a fix.
It's a little off topic, kind of, but have you tried acdisplay? It's like how the moto x reacts when you get a message.
Sent from my LG-D801 using Tapatalk
I think they removed that feature in KitKat. Kinda sucks because I liked it.
Sent from my LG-D801 using Tapatalk