Related
EDIT:
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
That post fixed my problem, as well as fixed the problem which the data connection turns off after a call.
Hey guys, sup?
I have a huge problem with my TELUS Touch Pro. Great phone, but just one problem...
Whenever somebody calls me, I can't answer the phone. The onscreen "Answer" button doesn't work, the Talk button doesn't work, pressing the Select button doesn't work...pressing the headphone button does, but sometimes my headphones are in my pocket, or sometimes they're not with me at all!
The only way I can answer them is by ignoring the call, and calling them back. It sucks big time.
Anybody have a solution? And no, I'm not hard-resetting my phone. It started doing this for my first call, so I'm pretty sure it's not my fault.
HEEAAALLLPPP!!!
Is this the stock ROM?
Do you have BT on and connected?
Mine started doing that yesterday. I did a hard reset and so far everythings back to normal. Still do not know what it was tho
I just had my TP replaced and the new one did the same thing, I did not notice until a few days later as I use a bluetooth headset and pushing the answer key on the headset worked. I had to RTN the device to make it work properly. Have not had a problem since. it has been aabout a week and a half.
Sometimes I've noticed this happens when my memory is tied up elsewhere, ie media player or something. Try soft resetting your phone every morning that might help clear it up.
I have had this happen with me on my Titan which I recently traded in for my Touch Pro, and also on my Touch Pro. I noticed it coincided with installing iGo8 GPS software on both. A hard reset was the only way I found to fix it. Uninstalling the software did not do the trick. I could be wrong about the software title I am blaming, but I have everything reloaded on my phone except that, and all is well. I do have a Slide To Answer incoming call screen now with the MightyRom 4.9.5 rom installed, maybe this is a work around, don't know for sure. If anyone else has more feedback, let me know. I would love to find a fix for it so I can use my GPS software.
Mine started doing this crap last night. I reinstalled the S2A cab and just let it go.
I am starting to think it might just be the telus network being a boatload of suck. Mine does it with the stock rom without any programs loaded from time to time. I am thinking it must be the tower failing to acknowledge that you want to answer the call, so the phone keeps ringing becuase it sees there is an incoming call but the tower ignores that you are trying to answer it. This is just my guess based on what I have read about CDMA, I wonder if any GSM users have the same issue.....
Do any of you have Advanced Configuration installed? This is what caused this problem for mine and my brother's TP. Uninstalling didn't fix it. Had to hard reset.
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
I can tell you that this will more than likely fix this for you. Mine was doing the same thing, applied this, done and shut! Good luck.
OMG OMG OMG thanks!!!! That also fixed the problem where it ended the data connection after the call.
Sorry I took so long, I THOUGHT I was subscribed to the thread...
Thanks again!
So I recently just rooted my droid and I'm running the evileris firmware atm I'm really happy with everything except that my phone can no longer make phone calls. The sound during phone calls does not work and I think it may not work sometimes in the music player as well. It works when I plug in the headphones but when i take them out no sound.
Airplane mode and resetting do not fix this problem and the updates that I've tried flashing from [FIX] Audiofix. NEED TESTERS FOR NEW KERNEL in the Hero CDMA forum do not work either.
This phone worked fine before rooting and flashing and the problem is present on all the roms I've used. The update above simply hangs my phone at the bootscreen, no matter which one I use. (Maybe its written just for hero?)
Anyways I was hoping one of you guys could have a fix or maybe have also had this same problem? Thanks!
(from what I've read in the thread above it seems the issue is a bad kernel that hangs up or fails to reset so you have to do it manually, but resetting doesn't fix the issue for my. My problem is constant phone call audio loss)
UPDATE: I have done some more experimenting and it seems the only problem is from the in-cal speaker, because when I put speakerphone on it works fine. The problem lies with the front speaker (part that goes to your ear).
maybe your phone is broken?
I went back down to 1.5 root, works fine. Its an issue with 2.1 :/ So currently I have 2 nandroid backups, 1 of 1.5 and 1 of 2.1 so I'm just switching in between the two.
did you try....
Did you wipe before flashing? After flashing did you try *228 opt 1? This may help as it sorted my audio issues with another Rom.
im having this same problem and i have no clue why i have tried everything knows possible to fix this.
I wipe before each flash as well as each recovery haha. atm my setup is 2.1 evil eris for the weekends and 1.5root for the weekday when i actually need to make calls
*228 opt 1 did not work btw
I just make a new backup at the end of the week and recover to the other one, works like a dual-boot pc or a bootcamp mac. It works, but its getting kidna old I'd rather just have 2.1 for good haha.
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
brianwin33 said:
longtime lurker.....1st time poster....i just installed leak v2 (i was one of those that was too impatient to wait for root)...i had the same problem that everything worked fine except the phone had no in call sound. Went through all the setting and found that tty was set to full...i unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
yesss thank you this worked for me.
BrianWin33 said:
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
I'm having the same problem... During a phone call, I get no sound / can't hear the person I am calling from the "internal speakers" (i.e. the one you hold to your ear during a call). If I switch to external speakers (i.e. loudspeakers) I can hear the person I'm calling...
What is this "TTY" setting that fixed this problem for you? Where can I find it and uncheck it?
I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?
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
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.