Anyone know how to enable the speakerphone by default? I used to use Auto Speaker (https://play.google.com/store/apps/details?id=com.hanan.android.ramkol&hl=en) on my previous phones (Note 3, Note Edge, S7 Edge and now Mate 9) and have no problem getting the auto speaker to work but somehow Mate 9 doesn't seem to work.
I'm having the same problem. Lost a weak tring to find a way or a workaround. Tried every app there is. Tried tasker, tried auto response, android wear integration, autoinput, quick settings, nothing seems to work. Im going crazy and nobody seems to care. Posted my issue on every forum I could find, no help there. Have you found a solution?
Related
Brand new OnePlus, unlocked and rooted. I am unable to get the Android share/bump to work with LG G3 or Samsung S4.
Have researched around quite a bit.
Have tried File Beam, so it will send a file (bluetooth), but will not receive.
Any known fix for this NFC bump bug? My searches have turned up nada.
Thanks.
Well, SuperBeam works, but still no direct luck with NC Beam, even OnePlus to Oneplus, seems to 'beam' the file, until at then end, says unsuccessful at the end. The NFC beam, though saying NFC, turns on the bluetooth on both OnePlus'es, and at the end of the beam, turns off the bluetooth. Just having the bluetooth on, despite the NFC Beam, does not change the success.
I like the SuperBeam success, but it is a menu selection/more user active process.
Any help to solve the simple NFC 'bump' would be appreciated.
We now have 3 OPO's. I can NFC from any of them to a G3, but not between the OPO's themselves!
Anyone with similar issues or it's working well for you?
Please, does anyone have an idea on how to fix this?
I've tried nfc beam from opo to nexus 5 and it works OK. Don't have other devices to test though. Are you on stock ROM ? Did you try a clean wipe and reflash?
Yes, have tried full reset. All 3 phone on 44s. All rooted and all other systems working well.
what is odd is that I can NFC to other non-OPO phones. Just not to another OPO. I can Bluetooth bump share between them, it's just more cumbersome, and WI-fi bump share as well.
I think the NFC bump outta work straight forward. All three phone work great with other, non-OPO phones.
Is there anyway to track down this issue?
So what seems to happen is that with the NFC bump, with no bluetooth, the OPOs, with each other, fail the transfer. If I turn on bluetooth, and then NFC transfer, I am able to transfer.
OPO to other makes of phone, no need for bluetooth.
Is this all making any common sense about how this should/does operate?
hi guys
im not getting any option to answer calls..
only option to reject from the watch
i know the watch has no speaker.but i thought it woudl allow me to answer like android wear..and then i speak on my phone
i tried googling..some said it worked before an update..does anyone know which version of the gear app allowed this?
or is there a way to fix it
i've checked and all permissions are given to the app
Mayur
mayurh said:
hi guys
im not getting any option to answer calls..
only option to reject from the watch
i know the watch has no speaker.but i thought it woudl allow me to answer like android wear..and then i speak on my phone
i tried googling..some said it worked before an update..does anyone know which version of the gear app allowed this?
or is there a way to fix it
i've checked and all permissions are given to the app
Mayur
Click to expand...
Click to collapse
This thread suggests that the option to answer calls on BT-only watches works only with Samsung phones: http://forum.xda-developers.com/gear-s2/help/question-answering-call-watch-t3251133
tstreete said:
This thread suggests that the option to answer calls on BT-only watches works only with Samsung phones: http://forum.xda-developers.com/gear-s2/help/question-answering-call-watch-t3251133
Click to expand...
Click to collapse
thanks for your reply and help. i did read that..but some people said it used to work..was wondering which version worked..
silly of samsung to disable this feature.
I still have an option to answer a call on my s2 classic. I hope it wouldn't just disappear like the messaging on the 4 app shortcut widget.
I recently went between an s7 edge and a pixel with my gear s2. I noticed I was no longer able to take calls on the watch when I went over to my pixel, but it was not a problem when using my s7 edge.
I figured it out. I don't know why, but I can say for certain that when a gear watch connects to a samsung phone, it defaults to the connection being a media and phone device (rather than the low-powered mode that, say, android wear watches do). Automatically. Always. On my pixel, the connection as a media and phone device must be initiated manually.
On my pixel I went to bluetooth devices and connected to my gear s2, which connected as a media and phone device. After that, the watch will answer phone calls on the watch directly. This all makes sense. The only difference is that on my pixel (anything other than my samsung phone actually), it does not default to connecting to the watch as a media/phone device (only low-powered peripheral).
Hope that helps.
I know this is old, but I wanted to offer a solution to the same problem I faced with a ZTE Blade Max. Goto bluetooth settings and click S2 in paired items then settings or options, then tick the option for phone audio. Problem solved!
cellfonepimp said:
I know this is old, but I wanted to offer a solution to the same problem I faced with a ZTE Blade Max. Goto bluetooth settings and click S2 in paired items then settings or options, then tick the option for phone audio. Problem solved!
Click to expand...
Click to collapse
Hi there! I've tried to use this solution but I can't find any kind of option as the one you suggest. I have a Xiaomi Redmi note 7. Is there any other option you can offer? Thank you so much for your time!
you have to change your build.prop to show a samsung device. cent remember where it is in the build.prop, but im fairly certain that this is the issue. This popped up pretty frequently back when the watches first came out and i had to do this myself as i was running an AOSP ROM on my old S5 when i got my first smartwatch (Gear 2 Neo) until i flashed android wear on it and no longer had the option to answer calls at all on my watch
Setting the phone to vibrate from the switch still allows notifications and ringtones to play through. Ive checked every setting I can find and haven't found a solution. Is anyone else having this issue? Silent mode seems to work as intended. I hope there is something ive over looked., also tried search and couldnt find anything.
Im using the tmo branded version on latest software update for them.
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
I'm so glad someone else also has this issue!
I was about to start a similar thread.
I have a lot of issues scanning my libre and it hardly ever works!
Can anyone help locate the exact location of the NFC sensor. I have watched Jerry rigs everything teardown but he did not mention where exactly it is located.
If someone could give me the exact grid number from this grid I've created I'd be very grateful!
CheopsChefren said:
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
Click to expand...
Click to collapse
Is this issue still present on Android 11 for you? My issue still persists even on a factory reset
Have you found solution. I have the Same problem with OPPO reno 4 z
I have bought an Oppo Find X3 Lite this weekend. Same issue. Anybody has a solution already for the above? I imagined only NFC would be enough but why is it that the Oppo phone does not connect with the scanner? Any idea anybody?
I got the Android 11 update for Oppo Reno 10x Zoom, and my Freestyle Libre 2 Sensors stopped working with the phone. When I try to scan, the NFC service hangs and NFC will not work anymore untill phone restart.
Oppo told me it is a known problem and they will try to fix it in a new firmware update. God knows when.
THANX A LOT, OPPO! Now I have to carry around the ****ty Freestyle reader all the time!
Hi Everyone. I had this issue and called ABBOT. Got a fix which now works. In your phone settings go to the libre link app and clear the cache data. Restart your phone and voila it works!
Hi all,
I pre-ordered my S22U and got it last Wednesday.2/23/22. (USA)
Had a couple issues when using android auto:
1. When replying to a message after its been read to me, I dictate the message it says its sent, but it never gets sent. Once I've stopped somewhere and talk to the person the message was supposedly sent to they say they never got it. Its not my vehicle because its happening to my boyfriend who also got the S22U, and he has a totally different brand of vehicle than I do. Super frustrating when I think I have sent a message, and an hour or so later find out it didn't go through like it said it did. This happens for text messages and also with Facebook messenger messages.
2. When android auto is reading me the messages, or reading me waze directions, the first portion of the reading has an annoying echo then it stops echoing. Same for my boyfriends vehicle and his S22U. We are both using our phones connected via an OEM USB cable (the only way to use android auto in both vehicles it has to be connected with the cable). I've had android phones for years and never had either of these issues before.
Any help is appreciated. Thanks!
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
TheNewGuy92 said:
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
Click to expand...
Click to collapse
There is no error code........
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
malikin said:
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
Click to expand...
Click to collapse
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
LadyGamer955 said:
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
Click to expand...
Click to collapse
just try an older version from APKPURE
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Denyo2 said:
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Click to expand...
Click to collapse
Glad to know its not just me. Another friend also has an S22 Ultra and a different type of vehicle than I do and same problems. And so many times I dictate a response to a message it reads it back says it was sent and it never sends it. Also never had this issue with Note 20 Ultra
LadyGamer955 said:
There is no error code........
Click to expand...
Click to collapse
you don't need an error code. Error submission using the samsung members app is manual submission that users do when the phone shows an issue but does not recognize that there is an issue.
If you see something and think it's an issue regardless of error code or messages, you can submit/report issue.
Any fix to this stupid issue yet? Im experiencing it with my s23+
kevindd992002 said:
Any fix to this stupid issue yet? Im experiencing it with my s23+
Click to expand...
Click to collapse
I have just got a Samsung S22 and have the exact same issue....Google haven't replied and Samsung just say its probably the phone.... My old S20 FE never had the issue
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
SLS1972 said:
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
Click to expand...
Click to collapse
Could you please upload some screenshots ?
Change the equaliser to normal.. and turn adapt sound to none. This cured the echo in my car for Android auto. I have custom setting on my S20 and it doesn't affect it.. but the S22 does.... its weird how two phones can behave differently with AA.