hey all,
I am not new to roms or kernels, etc. I have been addicted since my G2.
For the life of me, in the last two days, I cant figure out why my phone goes into speaker mode when I dial a number.
I am sure there is an easy fix. I was using Cognition 1.51 but went back to 1.42 and am using speed mod T27.
Is there a setting I am missing out on?
Thanks for you help, I am tired of having to remove from speaker mode and am close to doing a full wipe and install but would like to avoid this if possible
Edit: I cleaned the USB port and although it was clean, its seems to have made a difference, although it still happens on most calls. Could this be possible?
I am too having the same problem...this is frustrating
Hey there!
Same thing just started happening for me today
Although it doesn't affect all the calls and all numbers, but certain numbers, when they call me, I have this problem
Also, a reboot doesn't help, and the pattern is erratic.
Meaning sometimes the same number calls me, it happens, but sometimes it doesn't.
HEY GUYS!
Do you use GOsms pro? There is a bug report that the version dated 29 Aug messes around with the speaker calls, and the symptoms are consistent with what I'm experiencing, after just updating two days ago
I have updated to the 31 Aug version and will observe if there are anymore such symptoms. Keeping my fingers crossed!
rantzzz said:
HEY GUYS!
Do you use GOsms pro? There is a bug report that the version dated 29 Aug messes around with the speaker calls, and the symptoms are consistent with what I'm experiencing, after just updating two days ago
I have updated to the 31 Aug version and will observe if there are anymore such symptoms. Keeping my fingers crossed!
Click to expand...
Click to collapse
i use Go SMS....I will update it again right now..Hope it will fix
Check the Cognition thread folks,even after updating GO SMS it still happens, even people who don't use GO SMS have this problem which would lead me to believe it is a bug with this latest version of Cognition that needs to be resolved.
jonny68 said:
Check the Cognition thread folks,even after updating GO SMS it still happens, even people who don't use GO SMS have this problem which would lead me to believe it is a bug with this latest version of Cognition that needs to be resolved.
Click to expand...
Click to collapse
Cognition?
Thanks All!
Glad its not something stupid I had done
Updated goSMS and went back to using Cognition 1.40
All seems fine now, will recharge and reboot a few times and see if it happens again
I've had the same issue since i got the phone this monday.
I were ready to have it replaced and found this thread.
Updated go sms pro to todays version and it solved the issue.
Thanks!
Having the same problem too. I haven't rooted my phone (yet) so using standard Samsung rom. It happens on some (not all) calls and is annoying. Recently had other problems with the phone going into carmode by itself. Those seem to have stopped after cleaning the usbport. But the speakermode is persistent. Even after updating GoSms. It appears lots of users are having problems with the S2. This can't be a coincidence. Major flaw from Samsungs side imo...
Apparently after updating, it could happen again
Check out the changelog on GoSMSpro, it states:
2. Fix bug of call is defaulted to speaker(After update, if speaker is still on due to previous version's bug, turn off，it will be OK later)
Wtf?
For the record, it happened to me again today. Impacted one particular number, but subsequently same number called, the speaker was not activated..
Why oh why did they have to mess with calling
Mine is well and truly fixed now.
Back on Cognition 1.40 and Using Ragemod V2 T27 and the update to Go SMS and everything is perfect.
For me I think the GoSmS update was the fix but I reflashed before applying their update.
Problem solved is the main thing
Related
I might have found a bug in FreeX10 Beta 3. Have used this ROM a couple of days now and I'm very happy with it. However, today I discovered a quite nasty bug. All of a sudden I couldn't make a normal telephone call. The phone seemed to work normally, but was completely silent. Like you have a bluetooth headset connected and forget to use this. Nothing happened at all, and no call was made.
I could terminate the call and make a new one with the same (negative) result. I had to reboot the phone to solve the problem. By then everything was Ok again.
Has anyone else run into this problem?
( I had to formulate this bug report as a question in this thread since I'm not allowed to post in the development thread)
no, i'm using it for a few days now, and made several phonecalls. and all was very well. never had a problem with it
Hi
Since about a week ago my SGS2 answer an incoming calls with the speakerphone turned on by default, and there's no way I can change it.
I use lightning rom 1.5 for a few months and everything was perfect until now.
Please help!
TNX
Backup data>> factory reset .
jje
Oh I had this same issue just last week, out of nowhere. Here's what I did: plug the USB cord in & out the phone a few times, it should get okay. Just google it too, there's a bunch of HTC users who have reported the same issue but the plug in/out solution works for S2 as well.
Do you all use Go SMS Pro?....if so then its a software issue...
Update the application to the latest one and your issue will be resolved.
I used to have Go SMS pro, but I removed it long ago.
I heard about the problem it makes - similar to mine, so I tried to install and uninstall it again, but it didn't help.
I tried the USB connect/unconnect advice - didn't help.
I tried to install several auto-speakerphone apps to bypass the problem
Most didn't succeed, except from "save your brain" that worked OK for a while and than stopped. It also had annoying notification icon, and many Chinese notes, so I uninstalled it too.
Can't find the solution yet
I'd love more suggestions.
Thanks.
Lior
liorreem said:
Hi
Since about a week ago my SGS2 answer an incoming calls with the speakerphone turned on by default, and there's no way I can change it...
Click to expand...
Click to collapse
i had the same issue for about the same period, it started kinda a week ago, but in the past days i noticed that it just returned to normal
i updated gosms on 29aug to the last version, i guess this was all the fix i needed, stock 2.3.3 atm
Hi
I Managed to solved the problem using Elixir widget.
One of the possible widgets is Speaker widget.
Once I turned it off - the problem stopped.
Hurray.
Hi Guys,
Today i updated UnNamed V1.2.0 to 1.2.1 the problem i faced is when i call some one they cannot hear me and also i cannot hear them. Any solution to this problem.
That sounds like a pretty mean bug, for some reason I have not had that problem yet. If that happens everytime I suggest wiping the device and reflashing the rom. That will fix everything.
I updated last night and talked on the phone today with no problems. Try reboot or reflash.
sounds like you flashed a different modem prior to the rom flash
Audio
Fahimxda said:
Hi Guys,
Today i updated UnNamed V1.2.0 to 1.2.1 the problem i faced is when i call some one they cannot hear me and also i cannot hear them. Any solution to this problem.
Click to expand...
Click to collapse
Here is an easy step by step solution for you.
#1: be sure the phone is turned on.
#2: be sure to turn the volume up
#3: be sure the caller and callee are talking
#4: be sure the phone is not muted
#5: be sure you have an active sim card in phone
If all else fails you might want to visit AT&T
I updated last night and everything seems to be fine. Just made a phone call and they heard me.
I am on 1.3 today... no issues so far...
Sent from my SAMSUNG-SGH-I777 using XDA App
how to update
Hi Guys,
How do you guys do update. Just today i updated from V1.2.0 to V1.3.0 again i faced the same problem after few calls. I used to update not full only the files from V1.2.0 to V1.3.0. without wiping the cache. Any suggestions are welcome. Thanks in advance.
Fahimxda said:
Hi Guys,
How do you guys do update. Just today i updated from V1.2.0 to V1.3.0 again i faced the same problem after few calls. I used to update not full only the files from V1.2.0 to V1.3.0. without wiping the cache. Any suggestions are welcome. Thanks in advance.
Click to expand...
Click to collapse
after a few calls it stops working?
or calls dont work period?
it doesnt matter how you update the rom, i have used both the full and the updates, without wiping.
what does your baseband say in 'About Phone'?
the more INFORMATION you give people the easier it is for them to help you.
Pirateghost said:
after a few calls it stops working?
or calls dont work period?
it doesnt matter how you update the rom, i have used both the full and the updates, without wiping.
what does your baseband say in 'About Phone'?
the more INFORMATION you give people the easier it is for them to help you.
Click to expand...
Click to collapse
After few calls i the calls stop working. My baseband version is I777UCKH7. I am now back to V1.2.0 which works fine with small glitch (SMS trigger a sound)
Worked fine for me...now I'm on 1.3.0
I was on 1.2.1 yesterday and didn't have a problem with calls, and am on 1.3.0 now and again don't have any problems. And I only did the updates, not the full rom as well. It sounds like you somehow flashed a bad modem, I would try the full update which I believe now includes the modem and see if that works better for you. Its defiantly not a problem with the update packages or it would be a more prominent issue for alot more people.
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
Hi guys,
Kind of new to pocophone but I'm experiencing something really strange that I haven't on any other phone I've had before. Here's the background..
I bought the phone as a gift for my mum and she absolutely loves it but she's told me the phone will randomly make a call itself. I didn't believe it until I saw it happen. She can be on the phone (having made or received a call legitimately) and the call will automatically be put on hold waiting for her to answer a call from another person. The issue is, that person hasn't called her so when she calls back, the person is confused. This can also happen when she isn't on the phone
I checked her call waiting options (turned off and on, neither makes a difference) and reset the phone to factory settings but still getting the same issue. We haven't set up Google assistant or anything similar so the calls wouldn't have been made my a voice command either.
It's really strange and I've looked on the Internet but can't find anything reported on it. The phone is running miui 10 and she is on virgin mobile. The phone is less than 2 weeks old.
Any help is much appreciated.
Vik
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
melodystyle2003 said:
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
Click to expand...
Click to collapse
Thanks @melodystyle2003. I've tried a factory reset on the phone. When the phone does a factory reset, would that not install the latest stable miui ROM? It installed miui 10 and when I checked for updates on the phone, it informed me that there were no more updates available
I think the problem is, proximity sensor. This used to happen to older family member.
About phone->MIUI version, which version does it use?
green. said:
I think the problem is, proximity sensor. This used to happen to older family member.
Click to expand...
Click to collapse
Thanks @green. Did you ever find a solution to that proximity sensor issue?
melodystyle2003 said:
About phone->MIUI version, which version does it use?
Click to expand...
Click to collapse
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
vikz.t said:
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
Click to expand...
Click to collapse
This is the latest stable version.
Install the google dialer, and force stop the default one. Also, try switching your network connection, like if it's on 3G, shift it to 2G or vice versa, for some time.
And if proximity sensor is the cause (as mentioned by another fellow member), you can check the sensor wake up time through BBS or similar app. Proximity sensor does appear in the sesnor column of BBS app. And going through the wakelock's data, you might also be able to detect any other possible cause.
Have you tried switching off the 'redial automatically' option in the dialer options? That seems to be your problem.
vikz.t said:
Thanks @green. Did you ever find a solution to that proximity sensor issue?
Click to expand...
Click to collapse
It's not the hardware fault. Old people tends to keep the phone slight upwards while speaking, the proximity sensor wakes the screen and by accidentally registers the touch. This usually happens and the accidentally put the call on hold, accepts the second call or the add new call. You can try using the phone for a day.
Old thread, but just wanted to add that we have the same issue with a Pocophone we use at work. When you put away the phone after a call, then at random times it calls the last person you talked to before the current call. Does it about 1 out of 40 calls and is 100% a phone firmware issue, not some old lady holding her phone wrong.