Related
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Ziuck said:
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Click to expand...
Click to collapse
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
UTZorro said:
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
Click to expand...
Click to collapse
I have this same problem in my Chevy Volt. Sometimes the phonebook works (but very slowly) but the call lists never work. Also seems to take a very long time to pair initially.
Sent from my MB860 using XDA App
A lot of cars can only import the phone book from the SIM card. Not from any other application on the phone.
So if your phone book is in Google Contacts or some other application...you'll need to port it into the SIM card itself for most cars to be able to read it.
Return it. I have new A4 and atrix pairs fine. I actually think its the clearest device I've used in my car yet
Sent from my MB860 using XDA App
fade?
"I have new A4 and atrix pairs fine."
And do you know WHICH phone book your numbers are in, or which phone books the A4 can pair with?
If his BT is connecting, and the phone is working over BT, there's no reason to think the phone is defective. yet.
UTZorro said:
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
Click to expand...
Click to collapse
It's not a BT Stack problem...it's an Audi problem (or BMW, etc...). The manufacturers need to program their devices for Android. The ability to grab contacts and such isn't a standard bluetooth handsfree device option. It has to do something extra. How it *handles* that extra something differs by device...which is why some don't work with Android devices.
On top of that, there's a dialogue when you first pair the device that asks if it should have access to your contacts, call lists, etc...that you have to "Allow" or it won't ever be able to get those lists. It's been the same way on every Android phone I've ever used. If you don't hit Allow within 10 seconds the dialogue will go away and never come back...unless you unpair and re-pair the device. Try doing this and seeing if the dialogue comes up. If it doesn't, it's an issue with the way your Audi/BMW polls for contacts.
BTW works perfectly with my Kenwood receiver.
Ziuck said:
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
Click to expand...
Click to collapse
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I have the 08' audi a4 and my contacts sync just fine, as do the missed calls.
" my contacts sync just fine"
SIM card contacts? Google Contacts? Exactly which or what "contacts" ?
Hi, new user here to searched and figured it'd be better to post in this thread rather than starting a new one.
I'm another Atrix user who is having issues with pairing the Atrix to a bluetooth car kit. I've got the VW Touch Phone Kit (rebadged Bury CC9060) which used to work perfectly with my previous Samsung Omnia as well as my partner's Samsung S8500. The problem I have was that with the 1.57 firmware, I could initially pair the phone and it would sync the phonebook up fine so that I could make or receive any number of calls without a hitch. But the issue was when I switched the ignition off then back on, the Atrix appears to pair correctly, it'll grab the phonebook but cannot make or grab any incoming calls. When dialing from the phonebook, it will initiate the call then drop out while the call still goes through. Incoming calls just aren't picked up at all. If I deleted the pairing and paired the phone up to the car kit again, it'd work until the first ignition off and back on again.
After I updated to the 1.83 firmware, this no longer works for me at all even though it appears to pair correctly and syncs the phonebook as well.
I've looked into upgrading the software on the car kit but I'm already on v0181 which is the latest for the VW branded kit. The Bury CC9060 kit has available a v0235 update but won't load on the VW kit as it does a checksum check. I'm looking at possibly editing the flasher to bypass the checksum check.
Has anyone else used the Atrix with this car kit and experiencing the same issues?
Thanks in advance
fmflex
A quick bump.
I find it hard to believe that I'm the only one using an Atrix with this car kit...
I really wanted to buy a car kit, I was even willing to pay the rather high price. Then i saw tht the Atrix just "snaps it" with those two spring arms.
You know what happens in an accident? The phone will fly out as a missle. Good luck finding it, if you were doing 30 when you got slammed, the phone will still be doing 30 when it launches out of the clips.
If it doesn't hit you, you still won't be able to find it or call 911 on it.
So, nice dock, I'm holding off for something that can be used "in case of accident". For that price, I expect a more robust product, designed to survive. (Note to Moto, calls Mercedes and speak to crash safety team.)
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I am not sure that the blame can be directed to the car makers not suiting the android configuration.
I had concerns about Androids paring car bluetooth, so when my wife got her Samsung running Froyo before i purchased the Atrix, I tested it on my 2010 A4 and it all worked faultlessly. All phonebook, dialled, missed calls & received calls. All her contacts are stored on the Phone too, not the SIM. It actually worked better with it than my old Nokia's, and my old iPhone 3G. All of which had contacts stored on the phone not the SIM.
Being in my car all day, I had to make sure it the Atrix running Froyo would work too, and that's why I tested it with my wifes phone before buying the Atrix.
I would have to say that the problem does have something to do with how the Atrix handles bluetooth. I have been having all the same issues that other users are having.
To be fair to the Atrix, I had only one problem when I originanlly bought it and that was loading the contacts from the phones storage, all the other options were working and it never displayed the annoying error message and it never dropped the connection either.
This has only started playing up completely since I rooted it and installed HeLauncher with Fancy widgets (maybe it's just a coincidence, but its unlikely i think IMHO).
I have since uninstalled the HeLauncher and Fancy Widgets, and yet the problem is still there, so I have no realistic reason why it isn't working anymore.
Because i work for Audi, I will check at work why this issue might be happening ( just with the Atrix not all the other Android phones) and see if their is anything that can be done to fix the issue.
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
fmflex said:
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
Click to expand...
Click to collapse
Ok, I have tried connectivity with the current version of MMI and it seems to pair up with NO error messages at all. It would appear at this stage that the new MMI generation have the "issue" fixed. I am still waiting for a reply from Service Technical Support to answer why the issue exists on the older MMI generations. It would appear that Audi in conjection with Apple focused their MMI setup for iOS, not considering Android OS's.
Will keep you updated once I have some more information about previous versions of MMI.
Blame the cars not the phone.
My phone works 100% well and perfect with my Acura.
I've also had fun trying to get my E46 3 Series BMW ULF BT module to talk to the Atrix - has no issues speaking to an older Nokia phone. Anyway after a LOT of experimentation I've finally pinned down the root cause of the problem, text messages (SMS).
I've yet to figure out the specific trigger but it is either the number of messages or something in a specific message it doesn't like. I figured this out because I noticed the envelope icon coming up on the BMW screen for 5-10 seconds before the bluetooth would drop out each time after connecting the pairing. Each connection only lasts 15 seconds at most.
Anyway there were 193 SMS messages in the car memory, maybe the 194th message was upsetting it. I deleted almost all the 1150 SMS messages in my phone and it was only when I got rid of all of them that it connected. I then had to manually clear the SMS messages in the BMW one by one (took a long while).
I then did some testing whereby I sent an SMS or two to my phone. I noted that the Atrix seems to periodly get asked to upload messages to the car. You can delete them in the car but if they are still on the phone, they come back shortly after. They always show as unread on the BMW unless you read them on the car screen. Reading them on the phone has no affect. Maybe the SMS side of BT headset support is borked on the Atrix.
So my conclusion is that while I don't know the detailed trigger specifics, for BMWs at least the Atrix Bluetooth issue comes down to SMS messages. My large contacts directory uploads in its entirety without an issue. The solution for reliable BT connectivity to the Atrix and a BMW seems to be in SMS message management. Get yourself a copy of SMS Backup from the market when you experiment.
Hope this helps others!
Matt
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
I have a Sprint S3, and it will pair to my car stereo just fine, but it keeps disconnecting. Once paired, there is option boxes for "Call audio" and "Media audio"
It seems like if I turn one option on, it disables the other, and vice versa. Every time I start the car, the pairing is out of whack and I have to start over, enabling whichever one I want, and after a few times it works. I did get both to work one time, but as soon I turned car off then on, it was broken again.
My old phones have never had a problem connecting both Call and Media to my car, so I am concerned it is an issue with the S3.
I have 2010 Nissan Altima with the upgraded stereo. I have removed all previously paired devices so only the s3 shows up. I have removed and re-added the s3 several times. I have renamed the car's bluetooth name several times as well.
Is anyone else experiencing a similar issue, or can you test it with your car audio systems and let me know if it works for you?
Let me know if there some information I should provide to better understand the issue.
Thanks,
Rob
Hey robmtx, this might help you out. Theres an app in the market called bluetooth fix repair.
I had the same issue with my last two droids (1 and 3), and this solved the dropped connections. good luck
Thanks.
I'll give that a try.
I've also been reading how this might be more of an ICS issue than a device issue. It appears there are similar discussions in other device threads. I'll keep researching and also try this app.
I used my S3 in a rented car a view days ago and paired it with the installed Ford car stereo.
I played MP3 via Bluetooth and made some calls via Bluetooth. It all worked flawless. I also did not see any checkboxes for "call audio" or "media audio".
When I left the car and came back later it connected automatically. So I guess the problem is not a general problem.
this happens on mine as well from stock XALE8 to the latest XALF5. i went ahead and posted on samsung's FB page..but doubt we'll get a response
by the way, ive had this same issue whether im connecting to a bluetooth 2.0 or bluetooth 3.0 headset/car kit.
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using xda app-developers app
Motogp1 said:
Right I might know the answer to this as I had the same problem as few weeks ago.
If you have Facebook, twitter, whatsapp or anything like this best thing is to get rid of them if you don't want to go to your accounts and sync on your phone and untick the sync with contacts on any of the apps you have installed.
Then go to call log and clear your call history.
Delete the bluetooth pairing turn the phone off and back on, repair with the car, mine has worked perfectly since I did this.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Did you remove your Gmail account too when doing this? I plan to remove FB, stock e-mail (yahoo) but wasn't sure I wanted to go through removing gmail and removing Touchdown for Exchange.
ExTREmE99 said:
this happens on mine as well from stock XALE8 to the latest XALF5.
Click to expand...
Click to collapse
Sorry for the newb question - but what are these in reference too? Are they a firmware or similar version of something? I was looking under About phone but didn't see anything similar.
Robmtx said:
Did you remove your Gmail account too when doing this? I plan to remove FB, stock e-mail (yahoo) but wasn't sure I wanted to go through removing gmail and removing Touchdown for Exchange.
Click to expand...
Click to collapse
No Gmail is fine.
Sent from my GT-I9300 using xda app-developers app
I have no problems pairing the s3 with my Volvo. Streaming, skipping titels, switch to phone during streaming - everything is working fine. Syncing E-Mail via Exchange an Gmail makes no difference.
Robmtx said:
Sorry for the newb question - but what are these in reference too? Are they a firmware or similar version of something? I was looking under About phone but didn't see anything similar.
Click to expand...
Click to collapse
yes this is your firmware version. settings > about > build number > I9300XXALF5. this is the most current. stock should be I9300XXALE8. under baseband version is your modem (which should contain the drivers for your 3G radio/bluetooth/wifi (i think)
ExTREmE99 said:
yes this is your firmware version. settings > about > build number > I9300XXALF5. this is the most current. stock should be I9300XXALE8. under baseband version is your modem (which should contain the drivers for your 3G radio/bluetooth/wifi (i think)
Click to expand...
Click to collapse
My Build number is IMM76D.L710VPALEN which threw me off. Guess it is different for Sprint. Baseband L710VPLEN
I think I'll just buy a car without bluetooth and be done with this mess. It's so annoying playing the "will it pair" game. :laugh:
Some Sony Head Units tend to be a nightmare.
Sent from my GT-I9300 using xda premium
bluetooth bug
I have a strange problem with my bluetooth audio...I have a Denso radio in my Ford Mondeo and the nightmare starts whan I connect phone via bluetooth to it. Phone some time don´t wake up from sleep. The only way how to solve (partialy) this is to reset phone (long press of power button). Then phone connect perfectly and everything is working like a charm. This problem I had on every rom I´ve tried yet
Every other phone I´ve had before didn´t suffer such prblems (galaxy note, evo 3d...)
Somebody could help? I don´t know what to do...
Same Issue
I'm having the exact same issue with my SG3 (Stock, not rooted *yet*). The initial pair works great - phone and audio sync. Once I shut the car off and back on again, the Phone connection does not automatically initiate and I have to manually connect it on my head unit. I'm driving a 2013 Mazda CX5. It's not my headunit since both my HTC Inspire 4G and HTC One X connect without issue. Another annoyance is the lack of song titles or other ID3 info on screen. Even my old Inspire had that!
My connection is great, but I am having an issue with tags. I'm using PowerAmp, but my Alpine unit displays the wrong song info - it automatically uses the default app. Is there any way to fix this?
Robmtx said:
I have a Sprint S3, and it will pair to my car stereo just fine, but it keeps disconnecting. Once paired, there is option boxes for "Call audio" and "Media audio"
It seems like if I turn one option on, it disables the other, and vice versa. Every time I start the car, the pairing is out of whack and I have to start over, enabling whichever one I want, and after a few times it works. I did get both to work one time, but as soon I turned car off then on, it was broken again.
My old phones have never had a problem connecting both Call and Media to my car, so I am concerned it is an issue with the S3.
I have 2010 Nissan Altima with the upgraded stereo. I have removed all previously paired devices so only the s3 shows up. I have removed and re-added the s3 several times. I have renamed the car's bluetooth name several times as well.
Is anyone else experiencing a similar issue, or can you test it with your car audio systems and let me know if it works for you?
Let me know if there some information I should provide to better understand the issue.
Thanks,
Rob
Click to expand...
Click to collapse
i have the exact same problem, having before a Milestone/Droid 1 and a Galaxy S1, both have functioned flawlessly with my car...
By the way, my car is a Renault Fluence 2011, maybe it uses the same BT chip as your Altima as Renault and Nissan are pratically the same manufacturer...
SmoothB said:
My connection is great, but I am having an issue with tags. I'm using PowerAmp, but my Alpine unit displays the wrong song info - it automatically uses the default app. Is there any way to fix this?
Click to expand...
Click to collapse
PowerAmp does not send the Tags - Period
The devs may be working on it soon
---------- Post added at 03:29 AM ---------- Previous post was at 03:25 AM ----------
otakonx said:
I'm having the exact same issue with my SG3 (Stock, not rooted *yet*). The initial pair works great - phone and audio sync. Once I shut the car off and back on again, the Phone connection does not automatically initiate and I have to manually connect it on my head unit. I'm driving a 2013 Mazda CX5. It's not my headunit since both my HTC Inspire 4G and HTC One X connect without issue. Another annoyance is the lack of song titles or other ID3 info on screen. Even my old Inspire had that!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1732226
Not just you mate :crying:
Mazda CX5
otakonx said:
I'm having the exact same issue with my SG3 (Stock, not rooted *yet*). The initial pair works great - phone and audio sync. Once I shut the car off and back on again, the Phone connection does not automatically initiate and I have to manually connect it on my head unit. I'm driving a 2013 Mazda CX5. It's not my headunit since both my HTC Inspire 4G and HTC One X connect without issue. Another annoyance is the lack of song titles or other ID3 info on screen. Even my old Inspire had that!
Click to expand...
Click to collapse
Hi,
Did you get it working with CX-5 as I just spent 500pounds on this phone and have exact same problem. Thinking of getting an HTC One X instead.
gravyuk said:
Hi,
Did you get it working with CX-5 as I just spent 500pounds on this phone and have exact same problem. Thinking of getting an HTC One X instead.
Click to expand...
Click to collapse
So far I'm still in the same boat. I rooted today and used a market app called "Bluetooth fix" so next time I'm in the car I'll see if it fixed the issue.
Sent from my GT-I9300 using xda app-developers app
Hey guys! This is my first Android device, coming from the iOS Eco system. I am very happy with my purchase thus far! However, I'm having an unusual problem with the Hangouts audio call feature. I'm running 5.0.1 and the hangouts apps are up to date. During an audio call, I get disconnected with the person I am calling quite often, especially if I lock the screen during a call. But oddly enough it still happens if the device is awake. Is this a known glitch or is it something unique to my device? Any recommendations? I've already tried clearing the cache, but have not tried it again sense. I will also point out that calls are okay when I use the Hangouts app on the iOS devices.
Thanks for any help.
v/r,
KM
kenmillerjr said:
Hey guys! This is my first Android device, coming from the iOS Eco system. I am very happy with my purchase thus far! However, I'm having an unusual problem with the Hangouts audio call feature. I'm running 5.0.1 and the hangouts apps are up to date. During an audio call, I get disconnected with the person I am calling quite often, especially if I lock the screen during a call. But oddly enough it still happens if the device is awake. Is this a known glitch or is it something unique to my device? Any recommendations? I've already tried clearing the cache, but have not tried it again sense. I will also point out that calls are okay when I use the Hangouts app on the iOS devices.
Thanks for any help.
v/r,
KM
Click to expand...
Click to collapse
I don't get disconnected but i lose the microphone meaning the other person can't hear me, but i can hear them.
Is that what you mean by getting disconnected?
clubtech said:
I don't get disconnected but i lose the microphone meaning the other person can't hear me, but i can hear them.
Is that what you mean by getting disconnected?
Click to expand...
Click to collapse
Yes, I guess that is a better diagnosis. Have you found a way to revive the microphone once that occurs?
It happens on Skype and all voip apps as well, so not just hangouts.
Seems like an android software bug on this device.
I think plugging a headset and unplugging brings back the mic until it happens again.
Here is the same discussion o the Skype forums: http://community.skype.com/t5/Android/nexus-9-tablet-looses-microphone-during-call/td-p/3736171
Hopefully google will fix it in the next software update.
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.