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
My SGS2 stopped vibrating. Tried flashing, un-rooting, restoring stock and factory settings. None of these worked.
I am inclined to think that it is a hardware problem.
Has anyone else been dealing with issue? I read some posts on XDA regarding this matter but they were software related as opposed to hardware. Can anyone post instructions on how to fix it or provide any solutions for this issue?
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
UpInTheAir said:
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
Click to expand...
Click to collapse
Cannot get jig in Palestine. Bought the phone from the UK. Sending it back will be problematic. I will look for a repair shop.
Thanks for the quick reply
That's a "bummer" (bad luck). You could make a jig, but as you said that it would be problematic to return. Hope you can sort it easily. Sorry, can't think of anything of use right now.
Sent from my GT-I9100 using xda premium
hey there,
i got the same problem. no more vibrating at all. not with calls or notifications and not as haptic feedback. it started today (was still working in the morning), though i did not drop the phone or anything.
i am still hoping too find that it's a sw-problem. but all potential solutions i find do not help. so i guess i have to contact samsung.
but before i do that i have to get rid of all "hacking".
could you plz tell me what i have to do?
i have now cm9 20120402 nightly.
but i still have a cwm-recovery-backup of the original touchwiz (gingerbread).
-so first i make a backup of my current rom via cwm and of all my apps via titanium and store everything on my pc.
-i flash my touchwiz-backup
-i get one of those: http://www.amazon.de/s/ref=nb_sb_no...ld-keywords=Samsung+Galaxy+S2+USB+Jig&x=0&y=0 , plug it in, wait til its done and remove it again.
after that, samsung will never know i "messed" with the phone??
or do i have to consider/do something else?
tyvm!!
kws
I have the same issue.
When I was on my stock 2.3.5, I found a workaround:
- go into test mode (dial *#0*#)
- find the vibrate button, when you press it, it shouldn't work like you expect
- go back
- plug in your headphones and push the cable a bit to the left
- test vibrate again - this time it should work
- pull the cable out while vibrating, still pushed to the left, vibrations should stay on
I know it sounds crazy but it seems the hardware part that controls the vibrations is near to the jack port - excessive use of headphones, like it was case, must have damaged it somehow.
However, now I'm on CM9, so no test mode for me, I'm achieving the same effect by bashing the back button, so I get semi-constant vibration. I know, It's ridiculous.
Have the same problem here, I think it's software related because the shut down vibration stopped working when I flashed CM9 ICS, I can't remember if it was working anywhere else though. But now I'm back to 2.3.5 and it's not working at all. Did a Factory Reset, Cleaned Cache before and after the flash. Also used the Jig to reset my counter. Any clues?
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
dajomas said:
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
Click to expand...
Click to collapse
I saw something similar on CM9 thread, they said it could be a "bad flash", not a corrupted rom but the lack of proper cleanup before and after the flash. But I cleaned up everything before and after and I don't like reconfiguring the whole phone again for nothing.
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
kweso said:
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
Click to expand...
Click to collapse
I assume since your posting in xda developers that you are rooted?
If so, just back up data with titanium backup app and factory reset, setup system and then restore USER apps and data only.
Sent from my GT-I9300 using xda premium
kweso said:
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
Click to expand...
Click to collapse
Did you install another rom?
My vibration for example didn't work with some cm10.1 nightlies
it started in cm10.1 20130203. then i tried wipe cache and dalvik. nothing. then i updated to 0206 (wiped cache and dalvik again) > still nothing. went to bed. got up. everything ok! its vibration again! i am 100% sure, it did not work, when i left it on my desk last night. this morning, i checked for missed calls and it took a moment until i realized: i got haptik feedback back on patternunlock and keystrokes! checked ringtone-vibration: fine as well!
dont ask me how! would still like to know for myself.
thx,
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
call me stupid!
suddenly this evening my phone stopped vibrating again. then i realized: quiet hours! i turned off haptik feedback at night.
could slap myself. at least ill find this thread again, next time i screw it again....
nite,
kws...
...tapatalking
Girls can use it again then. Good news for them!
Sent from the little guy
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 Everyone,
I have switched over to the Galaxy S2 a little over a month ago. I moved from a Blackberry because of its own issues and having to reboot the phone etc.. but that is neither here nor there...
Before i updated the phone with ICS my Sms and Email notification sounds would work, all the time from what I remember. But now the phone sometimes plays the notification sounds and sometimes it doesnt. All my sounds are turned up full.
I am waiting on a loaner phone from my provider but until then I was hoping to fix it myself.
So today I did a factory reset and the phone did its thing. The notification sounds were working for the most part of the day and now I have a recieved a few texts and emails and the notification sounds didnt sound.
I have searched this problem and really have came up with nothing on this issue.
A few things i did notice though, after i did a factory reset on the phone that when it completed it still had the ICS op on the phone, shouldnt the factory reset have "re-formated" the phone and brought it down to gingerbread?
I apologize if this is lengthy but it is better to tell the issues and what I have done to try and rectify the issues incase some of the things that I have done is what would be suggested.
Thanks for any suggestions and help
Ok i figured out the problem... in the developer options i had selected kill processes after use. When i unchecked it the sound notifications for sms worked properly again.
Problem solved.
Sent from my SGH-I747M using xda app-developers app
Hey everybody.
My girlfriend is having a terrible problem with her new Xperia Go. It's running the latest Stock Firmware and Kernel without Root and every time she gets an incoming call, the phone won't react for about 15 seconds and then a FC Popup appears. This happens as soon she tries to answer the call. We rebooted it and it worked as it should after a fresh boot, but as soon she uses apps like Whatsapp, Facebook and so on, the problem persists and it's kinda of frustrating. A smartphone should be able to handle those things and she's really disappointed. Thinks I've tried:
-Clear data and cache of Contacts and Phone.
-Hard Reboot
-Recently installed the latest update via OTA (I hoped the problem would get fixed, but unfortunately it's still there)
-Tried using the stock launcher since she uses Nova Launcher
If someone has got an idea of what's going on please reply this post. I don't know if I should root her phone or maybe install a custom ROM. Honestly I wouldn't like to do that since she's a Noob in Android and basically in Technology Stuff. But if that's the solution, I would do that. It's really frustrating.
Thanks! Hope anybody could help
EDIT: SOLVED!
I tried to limit the background processes in developer settings and set the maximum to 4 processes and it magically solved the problem!
Moderator please delete this thread
Sent from my GT-I9305 using xda premium