Related
A few days ago I bought a device called GMATE ($80), a type of smallcell without display or keyboard which is inserted a normal simcard and communicating via Bluetooth to the Samsung Galaxy Player, which means an application is integrated with android, receiving and making phone calls, and SMS, in addition to allowing internet access GPRS.
It's a perfect combination that increases the possibilities of Our Player
IPhones must be jailbroken, a repo is added to Cydia, and then the Gmate app is installed for the integrated Gmate functionality. How does this work in Android?
In GooglePlay you can download a Gmate aplication that integrates the gadget with your android player (also convert your android phone in a double sim phone) and uses android phone's features like dialer, contacts, or any thirtd party aplication likes rocket Dial.
Received and Make calls don´t need special features, if you uses the Gprs/edge to internet (in places with no WIFI) need to be rooted.
The application is not compatible with my U.S. 5.0 Player.
CreekDirt said:
The application is not compatible with my U.S. 5.0 Player.
Click to expand...
Click to collapse
Go to skyroam webpage and ask for a .apk file, i have Intl 5.0 and working great, sometimes any aplication in GooglePlay seems to be incompatible for my SG player but, on a external apk source works fine.
Dutch 5.0
Thank you for the info! I will definitely buy one if it works in The Netherlands.
That does look interesting.
Anyone using it with the USA version?
Is there something similar that i can connect it to my player or to put it in the galaxy player? So this wey i dony have to worry if i get out of 10 neters or jf i fodget it at home
Sent from my YP-G70 using xda premium
Wow, wonderful find. I was looking for exacly something like this. Unfortunately, With ICS CM9 installed on my GP5 Bluetooth doesn't work =( (neither does the camera or hardware acceleration. They really need to fix that.)
So I can make phone calls/sms without having wifi?
oncaribe said:
A few days ago I bought a device called GMATE ($80), a type of smallcell without display or keyboard which is inserted a normal simcard and communicating via Bluetooth to the Samsung Galaxy Player, which means an application is integrated with android, receiving and making phone calls, and SMS, in addition to allowing internet access GPRS.
It's a perfect combination that increases the possibilities of Our Player
Click to expand...
Click to collapse
With the Gmate app, can your SGP connect to a regular cell phone with bluetooth or it can only connect to the Gmate?
testrider said:
With the Gmate app, can your SGP connect to a regular cell phone with bluetooth or it can only connect to the Gmate?
Click to expand...
Click to collapse
Gmate only.. I tried it with my other android phone and it doesn't work.
I came further when I changed my phone's Bluetooth id to "Gmate". It didn't connect because of a password failure
It's seems good
I don't quite understand... So besides buying the Gmate, would i need a sim card as well? secondly so would i practically be using a sim card with a data plan to use with gmate? but wouldnt that defeat the purpose of just using a smart phone with a card in it?.... these are all continuation Q's if the first is a yes lol.
This seems like a stupid question, but I'll ask anyway. How well does the device actually work? Does it keep a connection throughout the day, sending and receiving text messages without too much delay? I'm considering using this to replace my old dumbphone, but I'd rather not plunk down a sizable chunk of change with little indication as to how well this thing actually works.
Gmate calling speaker sound
Question: Does the sound come out of the front speaker while calling?
(I don't like to call everywhere with loud back speakers)
crowelfly said:
Question: Does the sound come out of the front speaker while calling?
(I don't like to call everywhere with loud back speakers)
Click to expand...
Click to collapse
I don't know about GMate, but on Groove IP (and probably others), the front speaker on the 5.0 is quite functional and is used for calls.
Mevordel said:
I don't know about GMate, but on Groove IP (and probably others), the front speaker on the 5.0 is quite functional and is used for calls.
Click to expand...
Click to collapse
Thank you for the info!
P.S. I like your rom a lot!
Cool!
Sent from my YP-G70 using xda app-developers app
EDIT: I HAVE FIXED THE MAIN ISSUE WITH MY GMATE, MORE INFORMATION BELOW
Well, my Gmate+ came in the mail today, and I've been playing with it for a little while now and am able to give first impressions. First off, the device is much smaller than I imagined, it easily fits in my palm, the vibration (on the plus version) is very loud. As for the function itself, it works. You can call and send and receive text messages (haven't tested the web access yet) with a few minor (and one major) annoyances. My device is currently a US SGP 4.0 running Terrasilent 1.1 and EtherealRom 2.3.
Minor annoyances I have found with the Gmate+:
- Notifications (read: texts) do not make noise/vibrate while the screen is locked. Once the screen goes on, if you do have a new text, it notifies you, kind of ruining the point of the notification.
- Text messages you send have proper time stamps, for some reason, the ones you receive are off by a few hours, as if the sender is in a different time zone
- Seems to be no way to delete contacts from the address book, even uninstalling, wiping data, reinstalling didn't do anything about this.
Major annoyance with the Gmate+:
- It disconnects, and by that I mean it disconnects ALL THE TIME, the device is pretty much useless because of this, it will be fine for a few minutes, then disconnect, regardless of how close the Gmate is to my SGP. Every few minutes, I'd check it, and guess what? No connection. Sometimes it would reconnect, sometimes I'd have to manually do it, sometimes I'd have to restart one or both devices to get it to work again.
Seeing as everything the device does it actually does quite well when actually connected, I want to rule this problem to some battery saving tweak in my kernel/rom. As such, I'll be returning to stock and trying the Gmate again to see if any of these issues are cleared up. As it stands, I have a 75$ paperweight that buzzes occasionally.
EDIT: After flashing back to stock and noticing no change, I began searching around and found other people having similar problems with similar devices, mainly connecting their smartphones to the bluetooth sound system in their car. Turns out in Deep Sleep, the device has issues keeping constant bluetooth connection. After downloading an app (Bluetooth KeepAlive: ~$1.30) on the market that keeps the device from entering this mode, the Gmate no longer disconnects, and has remained connected for several days, having no problem with calls or text messages at any time. In summary, with this app, I am now happy to recommend the Gmate to anyone who is looking for this kind of functionality. Guess it goes to show that non compatible apps are listed in the Play Store as non working for a reason
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Thank you!
Paladin13 said:
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Click to expand...
Click to collapse
Wow, thank you, I didn't know this option exists. I am running NeatRom v4 Lite and that option you mentioned is still there. (it is also JellyBean)
Lol got same problem as OP and tried similar things including chmod 0000 to cm3663 folder but no success.
Any ideas?
I’m coming from an EVO 4G and I forget how I finally got it working but I was able to use Voice Search or the Bluetooth headset to make calls by name from the folks in my contacts list.
I do remember that the voice search for making calls or sending text will not use your phone contacts but only your Google contacts. That was the only real gotcha I recall. I had to export my contacts, then import them into Google contacts and then link the two contacts together. Then the voice search would finally work.
I had done this on the DNA but the Voice Search would still not work. I finally had to go into the Voice Search settings under Phone Search and remove everything but “People”. Now when I say “Call: Bob” it pops up Bobs contact info and dials him instead of doing a Google search for “Call: Bob” or whatever. By default it has 4 or 5 things checked including People but it just did not work for me. ???
This did not however affect the Bluetooth headset dialing. It still just says “I didn’t catch that.” or tries to dial voice mail or random numbers. So, it’s still acts like the contacts list is empty.
Any ideas?
The Hotword detection is also not working. “Say Google to launch voice search.”
Thanks.
Hmm… Just me then?
Just over 250 views and no one can say they do or don't have the issue?
I did speak to a few tech support folks at Verizon and HTC but they could not tell me anything. I think I'm taking the phone back in the next few days. I like the phone but a phone that can’t dial from the headset is kind of a big deal.
I am curious about this too.
nabbed said:
I am curious about this too.
Click to expand...
Click to collapse
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
syler2012 said:
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
Click to expand...
Click to collapse
I can confirm the same problem on GS3 running CM10 latest nightlies. It's a Gapps issue....We need a way to force gapps to listen to bluetooth mic....
I think it is a problem with Bluetooth, Jellybean, and Google Now/Voice. This same type of issue was reported on the Galaxy nexus once it had been updated to Jellybean.
Some GN users installed alternative dialers/voice assistants and had success over BT.
I think Android 4.1 has some issues with BT. Android 4.2 switched to a completely new stack, and that too is experiencing problems, or perhaps growing pains. The fact that Android switched bt stacks from 4.1 to 4.2 leads me to believe that Google engineers ran into some deep issues with 4.1, and decided it was better to start from scratch with 4.2 (related a whole host of BT issues, including BT 4, low power modes, AVRCP etc., and interfacing them with the microphone for google voice search/now.
I just took it back and of course the Verizon rep had never heard of any issue with JB. So I showed it to him.
Of course I still had to pay the restocking fee.
Hi Folks,
This was the closet forum I could find for my phone. I actually have the GS2 HD LTE (i757) from Bell Mobility in Canada. Monday I finally received my Jelly Bean Update (4.1.2) I wish I could say I an excited however it has caused me so much stress, Ever since I installed it my phone has been terrible laggy. ICS gave me no troubles but after seeing the huge performance boost in my Wife's i9100m last month when it was available to hers I did not hesitate to update mine. Below I will list my symptoms, as well as the steps I have done to resolve this. I have search everywhere for an answer and have come up with nothing. Also to note, my Friend in the office has a Galaxy Note with a different provider (Telus) who received the update the same day, we can put our phones side by side and we both experience the exact same issue.
Setup:
i757 (S2 HD LTE)
Not Rooted
Symptoms:
Swiping to unlock is choppy
Opening Messaging to text takes three part (Loads the body, loads previous message and then keyboard loads in the middle of the screen and works its way down.
30-45 second pause to open the dialer
when clicking the power button to get to the lock screen it shows the desktop for a second, then god to my lock screen wallpaper then my lock screen icons appear. After this I can swipe.
loading apps
at startup RAM is 558MB/737MB. I hit clear memory right away it goes to 394MB/737MB. But open any app I am back up to to 550MB-600MB
Things I have tried:
Install install was Down with Kies as a regular update with all my Apps still installed.
I Wiped Cache and down a Factory Reset
Reloaded the Stock ROM with Odin3 v1.85
In developer options I disabled animation for Window, Transition and Animator
I disabled ripple effect for lock screen
I disabled Google Now
Tried to Wipe Cache then resume use without reloading OS
Tried Disabling GPS, Bluetooth, WiFi and sync.
Installed Android assistant to clean up startup
Did another Factory Reset/Cache Wipe then install OS from MSD
None of these options have made a difference. The phone worked flawlessly on ICS, I don't know what else I can do. Has anyone experienced this issue? and if so have they fixed it?
At this point I will try anything before I take out the hammer and fix it for good. Any assistance would be greatly appreciated.
- Boots!
Also my Current status is Factory Reset/Wipe Cache OS Installed from SD Card nothing install.
* * * COULD MOD PLEASE MOVE TO APPROPRIATE FORUM I MUST HAVE OVER LOOKED THE i757 FORUM * * *
Moved
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
windex23 said:
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
Click to expand...
Click to collapse
windex.
Please keep this thread in mind, Anything I can find I will post it here. If you could do that same that would be great. My S2-i9100 was amazing with the Official JB release also. I am surprised more people are not complain online about this as I know my friend with the Note on Telus is having same issue (Update was released the same time for him) I also called Bell and their Tech support said they were receiving alot of the same issues since the May JB update..
Damn Lag has got my phone!
AH! damn update lag has got my phone and my girlfriends too! We both have the samsung galaxy HD LTE I757M phone and have exactly the issues all of you guys have. From extremely slow response to flickering and its just a pain in the ass. My girlfriend tried a factory reset which worked for about a week with no lag or anything but then just started the same lag issues we all have. A lot of people apparently are reporting that a factory reset does the charm but its only a matter of time before the issues creep back to your phone. Right now I am going to try a custom rom for our phones and hope that it works. If it does Ill post the results for you guys to hopefully benefit from.
sean
I was having the same problem with my I757M. This phone is fine on ICS 4.0.4.
I don't know the real solution but, the phone is fine (for now)
Used Forever Gone app
Did a factory reset before upgrading to JB 4.2.1 (Maybe?)
Removed Ripple effect on Screen lock
Set the transitions to 0.5x
Power savings enabled (Screen only)
Disabled these system apps
100% HD Games
AllShare Play
Asphalt 6
Google Play Magazine
Google Play Movies
Google Play Music
Google+
GPS navigator
Let's Golf 3
Self-Service
Update software
Google Play Books (or Play Books)
Social Network
Ringtones and Applications
Sympatico.ca
Talk
Talkback
TV mobile (bell)
Y! Finance
Yahoo! Finance Daemon
Yahoo! News
I installed JB 4.1.2 today, saw some improvements, hope it is fixed for good !
The ram usage on boot (369MB / 737MB)
Sorry to post again !!
Okay, it started to lag as described by others. So I went back to 4.0.4... The battery life is better on Jelly Bean because it can reduce the screen's power (not just brightness)
I did this today, my last attempt with JB...
In Dial :: *2767*3855# (it formats everything, even sdcard, so backup your things before doing this !!!)
I configured ICS from the welcome screen (no gmail configuration, etc.)
Installed JB 4.1.2 from Kies.
I disabled the programs mentionned at my previous post...
There was still a lag when unlocking the phone. Tried Holo Locker and didn't do anything... still lags.
Then, I searched on the net :
http://forum.xda-developers.com/showthread.php?t=2224906
It seems TouchWiz has problems rendering Widgets on homescreen, so, I installed Nova Launcher to replace it.
For now, when receiving a SMS, after unlocking, the wallpaper can become black, but there is no lag like before. :good:
Same situation
My wife‘s i757m has the same situation. I wiped to factory and uninstall like "let's golf", google play music. Then it turned much better for about 1week and then be back lag lag lag again.
I have no idea why it is so ridiculous , cause my friend's I727(GS2HD rogers) is very good after he updated his in March.
Please help me SGH-1757M
I have the same Issues.
After upgrading the Phone to 4.1.2 bellow issues identified.
1) When Incoming call comes the Phone Frezes and Green and Red button on the screen does not work
2) Some times it works but when I get any call the Phone rings with black screen and after some time it comes with number and then caller id and then answer button
3) Every time when I went to Messaging it loads the messages with number and next updates the Caller ID and then body of the messages and text editor
4) Morning when alarm rings phone Freezes and does not allow me to stop the alaram and force restart the Phone.
I am having so amny problems like this .
Please suggest what we can do here to resolve these issues.
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.