Database Info

[Q] Auto Answer Speakerphone

Hi, Ive recently factory reset my phone and now cannot get the speakerphone to automatically come on when I use the autoanswer app. Ive got an S3 4G phone (GT-i9305T) with Version 4.1.2. Ive gone into the app setting and have ensured the FORCE SPEAKERPHONE option is checked. Can anyone assist? cheers John

i had a similar issue,what i had to do was press the volume key once at the biginning of each call to activate the speaker. its not great, but its one just click.

[Completed] Facebook Messenger screen off in calls, no speakerphone, can't end call : app broken?

My mom's phone and my P01v have the same version of Facebook Messenger. It works well on hers and use to on mine.
After a recent call I realized that FB Messenger now turned my screen off so I was not able to access the speakerphone feature as well as end the call. It did not do this before. I've uninstalled and reinstalled the app, I have also reset my phone but there has been no improvement. The proximity sensor on my phone does not work. I have tried to make and receive regular phone calls and Viber calls and I was able to get a speaker phone, end the call, and the screen did not turn off.
Is there something wrong with Facebook Messenger? Since I have not been able to get the missing features and keep the screen on I'm now thinking of editing the FB apk instead. I was able to extract the apk, can anyone help me out on how to hack this app?
Note : I've had a similar issue with Asus dialer app (screen off, can't turn it on again during call, cannot access speakerphone, cannot end call unless I press the power button) and its because of the proximity sensor. I uninstalled the Asus phone dialer app and installed 3rd party dialer and phone related apps, problem solved.

Hi !
Before proceeding into any "hacks" better go to a service center , you must be sure wether is a hardware issue or not
More feedback you may receive from here https://forum.xda-developers.com/android/help
Here is a general discussion for your device https://forum.xda-developers.com/ge.../asus-zen-pad-thread-accessories-dev-t3160795
Good luck !

Galaxy S6 Edge+ Bluetooth forcing speakerphone when phone screen is off w Nougat?

Hi all,
I am having an issue with my Galaxy S6 Edge+ with Bluetooth forcing the speakerphone when I am making a call and driving. This has just starting occurring since the Nougat update. If someone calls me I can still answer from the head unit and the Bluetooth works perfectly. The issue is when I make a call and press the steering wheel Bluetooth button. When I do this and say the name of the person to call I get the voice command saying "Calling so and so mobile...ON SPEAKERPHONE". It says it's calling the person but then says ON SPEAKERPHONE.
What is interesting is I played around with different settings, reset my phone, unpaired and repaired, and still the same issue since the Nougat Update. But what is interesting is that I found if I make a call while my screen is active (screen is on), and I make the same Bluetooth call, I can see the google voice icon pop up on my phone, the call is made CORRECTLY, through Bluetooth. However, if my screen is off and I make the call, it ALWAYS reverts to speakerphone. So as long as I touch my phone to make the screen active for 5 or 10 seconds or whatever I have the screen set to, as long as the screen is on the Bluetooth always performs correctly. I can not figure out how to prevent the speakerphone from being the primary source when the phone screen is off and I make a Bluetooth outbound call.
Again, if someone calls me, it doesn't matter if my phone is locked, screen is off or on, the Bluetooth always works fine. Any suggestions on how to fix this? Any help is very much appreciated. Thank you.

ItzTime said:
Hi all,
I am having an issue with my Galaxy S6 Edge+ with Bluetooth forcing the speakerphone when I am making a call and driving. This has just starting occurring since the Nougat update. If someone calls me I can still answer from the head unit and the Bluetooth works perfectly. The issue is when I make a call and press the steering wheel Bluetooth button. When I do this and say the name of the person to call I get the voice command saying "Calling so and so mobile...ON SPEAKERPHONE". It says it's calling the person but then says ON SPEAKERPHONE.
What is interesting is I played around with different settings, reset my phone, unpaired and repaired, and still the same issue since the Nougat Update. But what is interesting is that I found if I make a call while my screen is active (screen is on), and I make the same Bluetooth call, I can see the google voice icon pop up on my phone, the call is made CORRECTLY, through Bluetooth. However, if my screen is off and I make the call, it ALWAYS reverts to speakerphone. So as long as I touch my phone to make the screen active for 5 or 10 seconds or whatever I have the screen set to, as long as the screen is on the Bluetooth always performs correctly. I can not figure out how to prevent the speakerphone from being the primary source when the phone screen is off and I make a Bluetooth outbound call.
Again, if someone calls me, it doesn't matter if my phone is locked, screen is off or on, the Bluetooth always works fine. Any suggestions on how to fix this? Any help is very much appreciated. Thank you.
Click to expand...
Click to collapse
Seems to me that the wakelock for Bluetooth calling is set to be inactive while screen is off. See if you can find that wakelock or some other wakelock that would disable Bluetooth calling and switch it so that screen off does not interfere.
Sent from my SM-S903VL using Tapatalk

@ droidriven, thank you for your reply. I have never heard of wake lock before, is this an option within settings on my Galaxy S6 Edge+? I never had this issue with prior OS's but with Nougat this issue immediately became present. If you could lead me in the right direction where I might find the wake lock setting for Bluetooth, I would greatly appreciate it. Thank you again.

it looks like you are on to something. I checked this again and anytime I make a call via Bluetooth voice command and where my screen is off, I hear the automated voice command say calling so and so....on speakerphone....but when it says this, the screen stays locked and does not activate on the voice/Bluetooth command to call. I am using google voice and see no settings for wake lock or anything similar but I have pinned this down to anytime the screen is off, the voice command/Bluetooth always go to speaker phone. If someone calls me, it always works correctly, but that is because when someone calls me, my screen automatically engages/turns on.
Anyone else have this issue? It's definitely a problem and dangerous to have to grab my phone to turn it on or unlock it before making a voice/Bluetooth call. Any help to fix this would be appreciated. Thanks in advance.

ItzTime said:
it looks like you are on to something. I checked this again and anytime I make a call via Bluetooth voice command and where my screen is off, I hear the automated voice command say calling so and so....on speakerphone....but when it says this, the screen stays locked and does not activate on the voice/Bluetooth command to call. I am using google voice and see no settings for wake lock or anything similar but I have pinned this down to anytime the screen is off, the voice command/Bluetooth always go to speaker phone. If someone calls me, it always works correctly, but that is because when someone calls me, my screen automatically engages/turns on.
Anyone else have this issue? It's definitely a problem and dangerous to have to grab my phone to turn it on or unlock it before making a voice/Bluetooth call. Any help to fix this would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Go to PlayStore and do a search for:
Wakelock Detector
Wakelock are system processes and don't have a "setting" to manage them.
Use this app to find the running wakelocks, if you track it down you can then look for a way to manage it the way you need it to work. It works with root and without, instructions for without root are in the link.
https://forums.androidcentral.com/showthread.php?t=571286
Then read this to understand wakelocks
http://www.guidingtech.com/45384/android-wakelocks/
Sent from my SM-S903VL using Tapatalk

Droidriven,
I have a little more info on this issue. I did more research and realized somehow my "S VOICE" app was disabled so I enabled it and right away this issue was fixed! With S VOICE enabled, anytime I use the voice recognition button to make a call the screen on my phone immediately activates and the call works without going to speaker phone. With S Voice I can at least use the voice recognition button to make a Bluetooth call while driving and not have to worry about the call going to speakerphone.
The only issue I have noticed is it appears S VOICE isn't as accurate as google voice and google voice worked perfectly for me before the Nougat update. Now that I've isolated this issue to google voice where the screen will not activate when using the voice recognition button on my steering wheel to make a Bluetooth call and which causes all calls to go to speakerphone.....is this still something this wakelock detector may fix? My phone is not rooted and I have downloaded the non-rooted version of wakelock detector, I just don't know if it's going to help or not. It's odd that google voice worked fine prior to the Nougat update, whether my screen was off or locked when using Bluetooth and now all of a sudden this issue is present.
Any suggestions on this now that we know it's only google voice that has the problem and not S VOICE?

ItzTime said:
Droidriven,
I have a little more info on this issue. I did more research and realized somehow my "S VOICE" app was disabled so I enabled it and right away this issue was fixed! With S VOICE enabled, anytime I use the voice recognition button to make a call the screen on my phone immediately activates and the call works without going to speaker phone. With S Voice I can at least use the voice recognition button to make a Bluetooth call while driving and not have to worry about the call going to speakerphone.
The only issue I have noticed is it appears S VOICE isn't as accurate as google voice and google voice worked perfectly for me before the Nougat update. Now that I've isolated this issue to google voice where the screen will not activate when using the voice recognition button on my steering wheel to make a Bluetooth call and which causes all calls to go to speakerphone.....is this still something this wakelock detector may fix? My phone is not rooted and I have downloaded the non-rooted version of wakelock detector, I just don't know if it's going to help or not. It's odd that google voice worked fine prior to the Nougat update, whether my screen was off or locked when using Bluetooth and now all of a sudden this issue is present.
Any suggestions on this now that we know it's only google voice that has the problem and not S VOICE?
Click to expand...
Click to collapse
According to this and many other links I checked out, this is a common issue due to G Voice and S Voice incompatibility.
https://www.androidpit.com/ok-google-is-not-working-here-s-how-to-fix-it
Sent from my SM-S903VL using Tapatalk

Google Pixel Keeps Hanging and phone Reboots every time i Receive or Make a Call!

Google Pixel Going Crazy after 8.0 Update!
It does not let me answer any calls or make any calls, when ever the person on the other end picks up the phone it freezes, or when ever i answer the call the app freezes, crashes, then my pixel restarts, This also happens on any Application which u can make a call on such as Whatsapp, Viber or even facebook messenger.
I have sent so many bug reports, Still no news or luck, Two weeks back an update of 50.2MB was there, i updated and it was ok for 2 or 3 days and this started happening again,
I also notice when ever im watching a video or playing a song on my pixel, and i try to increase or decrease my volume i cant play with the "Media" volume with my volume key on the side of my phone, i can only increase or decrease the volume of 'Call' option.
Also i have noticed that when this happens the phones mic/speaker is having some issues since i tried tuning my Guitar with a Guitar tuner app and the mic wont pic any sound from my guitar.
This is starting to get really annoying and frustrating!!!
Google Please don't Disappoint us,
Hope this issue gets solved Soon!

Hardware mic issue "hairline crack in the audio codec", it is known and my previous pixel had this issue, and I bought a new one since I couldn't send it back for replacement, check Google for RMA.

Made any headway with this problem?
I'm copping it as well, and not very pleased. I use my phone for business, and this is quite debilitating & unprofessional not being able to take a call, obviously.

I had a crash/reboot issue on my pixel xl
I booted into safe mode
then restarted in normal mode and seems to have cleared it
may not cure, but worth a try
are you on stock? beta? custom rom?

Google Pixel Keeps Hanging on phone calls After Android 10 Update
I have Google Pixel 1- Sailfish-128 GB. I am having problems with using the Phone app functionality. When I am receiving any call and I answer it, the phone app crashes and the phone is not usable. Entire system UI crashes and the only option I have is pressing the power and volume down button to force shut it down. Same thing happens when I place any outgoing call through phone app or making/receiving call on any 3rd party apps like Whatsapp, Instagram etc.. I have tried factory reset from settings, Resetting from recovery.. but nothing helps.
Phone works somewhat fine as long as there is not outgoing/incoming calls.
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
I have Google Pixel 1- Sailfish-128 GB. I am having problems with using the Phone app functionality. When I am receiving any call and I answer it, the phone app crashes and the phone is not usable. Entire system UI crashes and the only option I have is pressing the power and volume down button to force shut it down. Same thing happens when I place any outgoing call through phone app or making/receiving call on any 3rd party apps like Whatsapp, Instagram etc.. I have tried factory reset from settings, Resetting from recovery.. but nothing helps.
Phone works somewhat fine as long as there is not outgoing/incoming calls.

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.

beejuan said:
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
Click to expand...
Click to collapse
If you don't have issues with the Pixel 2 and do have issues with the Pixel 2XL, why don't you ask in the Pixel 2XL forum?
Sent from my Pixel 2 using Tapatalk

ajrty33 said:
If you don't have issues with the Pixel 2 and do have issues with the Pixel 2XL, why don't you ask in the Pixel 2XL forum?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Quite simply, I missclicked into the wrong forum. Ta!

beejuan said:
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
Click to expand...
Click to collapse
Hey, did you get any answers on this,. I'm having the same frustrating issue.

I just started to have this problem a few days out of nowhere. Some on Reddit are having issues too.
https://www.reddit.com/r/GooglePixel/comments/80qh32/pixel_2_xl_dialer_problems/
I found that plugging the phone into charge or computer fixes the issues for a little bit...

Had similar issues with my Verizon Pixel 2. After some searching, I restarted the phone in safe mode and the problem went away, meaning it's a non-stock app interfering with the phone app. I restarted in 'normal' mode, uninstalled Facebook (it's always f'ing Facebook), and have had zero issues since.

thibadude said:
Had similar issues with my Verizon Pixel 2. After some searching, I restarted the phone in safe mode and the problem went away, meaning it's a non-stock app interfering with the phone app. I restarted in 'normal' mode, uninstalled Facebook (it's always f'ing Facebook), and have had zero issues since.
Click to expand...
Click to collapse
Thanks for the fix! Phone.app was killing me!