Related
Losing my mind here.
This may be CM related (August 17th nightly ATM, but happens on the 10.1.2 release as well), or it may be app related, but it's driving me up the wall.
My phone will occasionally play a sound I have never heard before... With good speakers/headset, there is a low hum at first, then regardless of speakers, I get the high pitch beeps, ascending tone. This happens regardless of sound status. (On vibrate or silent, I still hear the beeps) and with no notification icon to go with it.
If anyone has any idea what this could be, I'm all ears!
Thanks!
** I posted this in the T989 device forum, but it is also happening on my Nexus 7, and on both a Cyanogen 10.1.2 and a Hellybean ROM so I'm confident it's not device related, and likely not ROM related. MODs feel free to delete the post in the device thread **
SOLVED Beep Annoyance
FINALLY!!!!
Ok, so I found the problem.
I was randomly reading my Google+ feed (yeah, I know, who does that right?) and saw a post in the Text+ circle. Someone had joined as a beta tester, and wanted to know how to turn off the beeping. Turns out, Text+ uses a series of beeps to calibrate their echo cancellation. I opted out of the beta, reinstalled Text + and all is good in the world.
Hope this helps someone else avoid repeatedly wiping their phone to try and find the problem!
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app
I have a galaxy s6 edge+ with a newly installed ROM (SmokkieROMv4) which I absolutely love because it's so snappy and battery life is awesome! It's like a brand new phone. Props to the makers!
Specs:
Android 7.0
Kernel: 3.10.61 SmokkieKERNEL_v2
Build number: SMOKKIEROM V4
Phone Model: SM-G955F (Galaxy s6 Edge+
Here is my problem, everything works great besides being able to talk to people!!! If I call my voicemail it automatically hangs up after exactly 6 seconds, if I call any other numbers it has no dial tone or any noise whatsoever but I think it does connect...just no sound.
Things I've tried:
1. Factory reset
2. Clearing all app data/cache/dalvik
3. Installed various phone/contacts .apk's and set them to my default calling app, and disabled the ones it came with. I did set all the permissions for the newly installed .apks with the same results when I call someone.
4. Disabled S voice and google assistant (Unable to toggle "Ok Google detection" in the google app because it's grayed out(disabled) for some reason.
5. Tried a different ROM with 7.0
Please if anyone knows how to fix this it would be very much appreciated as I do love this new update very much and everything else works flawlessly!
TheRealDgk said:
I have a galaxy s6 edge+ with a newly installed ROM (SmokkieROMv4) which I absolutely love because it's so snappy and battery life is awesome! It's like a brand new phone. Props to the makers!
Specs:
Android 7.0
Kernel: 3.10.61 SmokkieKERNEL_v2
Build number: SMOKKIEROM V4
Phone Model: SM-G955F (Galaxy s6 Edge+
Here is my problem, everything works great besides being able to talk to people!!! If I call my voicemail it automatically hangs up after exactly 6 seconds, if I call any other numbers it has no dial tone or any noise whatsoever but I think it does connect...just no sound.
Things I've tried:
1. Factory reset
2. Clearing all app data/cache/dalvik
3. Installed various phone/contacts .apk's and set them to my default calling app, and disabled the ones it came with. I did set all the permissions for the newly installed .apks with the same results when I call someone.
4. Disabled S voice and google assistant (Unable to toggle "Ok Google detection" in the google app because it's grayed out(disabled) for some reason.
5. Tried a different ROM with 7.0
Please if anyone knows how to fix this it would be very much appreciated as I do love this new update very much and everything else works flawlessly!
Click to expand...
Click to collapse
Interesting... Well, atleast i now know im not the only one with this issue....
the only somewhat fix for this is(and its not really a fix) and you can actually use the phone. Is to make sure you are connected to wifi and have wifi calling enabled and set as a priority use. It really sucks cause if your on the road or not home or whatnot that wont work, obviously.. I use skype alot with my data,which is somewhat ok for me.. IDK if Whatsapp would work as a bypass or not? ive never used it so im not sure with that. But theres definitely a major glitch somewhere in the samsung software or drivers for the phone itself. Cause unlike yours, mine is stock. No root,Roms etc.. just apps..
Im running 7.0 SM-G928T
Ive also talked to the tech guys for my carrier (T-Moblie) with no prevail what-so-ever... Question, is your phone in mint condition? .
Whatsapp
Yes whatsapp does work for me and is what I have had to use the past couple of days. Everything besides the actual phone app works correctly lol. But of course after playing around some my phone screen just shot out on me for some reason. It just blinks random colors and stays black most of the time. The last app I installed was called "Root Essentials" and shortly after my phone starts doing this. I have no idea how to fix. Can't afford a new phone at the moment either. Definetely need it to work though as it is used for work. Thanks for the help anyways.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.
When on calls and using Bluetooth (Lg FP8) if i get a notification the audio on the call becomes robotic and I can't make out the words of who I am speaking with. I have to toggle speaker on and back to BT to get it to stop. Doesn't happen with every notification, and isn't isolated to just one app afaik. Anyone else have this issue?
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Try a network reset.
If that doesn't work try a hard reboot (soft reset).
ah0y said:
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Click to expand...
Click to collapse
Here's a list of bugs as of Nov. 27 and their status:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com