Database Info

[Q] WP7 and Audi MMI Bluetooth Issue

Hello Everyone,
This issue has been bothering me for over a month. I have searched several "MS support forum" threads, XDA Dev threads and multiple Audi forums, but all in vain.
I am not sure if anyone in here has had any issues with the Audi MMI while using a WP7 Handset. I hope that some smart person will have a word of advice for myself. Provided below is the process that I followed for pairing and testing:
1.Cleared all the existing paired devices from the MMI.
2.Cleared all the pairings from the cellphone. (Just to start with a clean slate).
3.Paired cellphone to MMI.
4.Check marked the prompt on cellphone, to Allow MMI to access my phone books and other cellphone data.
5.Call logs and telephone directory is accessible on the MMI.
6.Outgoing Calls from the MMI work without a hitch.
Up to here, everything is good. However, I am unable to answer the call from the car's MMI. If I may paint a scenario:
A call comes in.
The audio system gets paused.
I can hear the call ring, and Caller's ID is displayed in the car.
I click "Answer" from the MMI.
The call gets answered, but the only way to get the audio onto the car's system is to pull over and yank the phone out of your pocket and click the bluetooth button on the call menu.
But 1 in 10 times it would work just by clicking answer from MMI.
I have never had any issues with my Blackberry. Is anyone else aware of a similar issue or a resolution to this?
Thank you very much!
Details:
Cellphone : Nokia Lumia 800
OS Version: 7.10.8107.79
Vehicle: Audi S5
Audi MMI Version: HNav_US_P0110_D1 (Third Generation, HDD based)

is ur phone locked by any chance (I mean have u kept a lock on the screen) if you have than try once after removing the lock

I thought of exact same thing. Tried it both ways, same result.

Stealership!!
Well, took the car to the dealership, to check for any MMI updates that might be available. In the end, the guy said that there are no updates available, and they charged my 90 bucks for the labour . Gotta love Audi. And the car has "New car warranty" till 2015. Glorified car wash.

[Q] ICS update and Car-Dock issue

Hi Guys, Forgive me if this has been asked before, but I sure could not find it.
Anyway, My problem is: I recently updated my SG Note to ICS (India). After the upgrade I am unable to receive or make phone calls when my phone is connected to the Car Dock (Original Samsung Accessory). When I get a call with the phone connected to the car dock I am unable to see who is calling (blank screen) but can hear the ringing and then after a few rings I get an error message that says - "Phone Application Failed to Load". By the way, all was perfectly alright before ICS update.
Is anyone else facing this issue?
Please help with a solution, as I'm unable to receive or make calls or charge the phone (for fear of missing important calls) while travelling.

Hi Guys, No body has a clue to this issue. 54 reads and not a single reply!?!

[Q] Caller ID (name + surname) not show when in use with Lexus NX infotainment

Hello everybody,
I'm experiencing some troubles when I use my Google Nexus 5 associated to Lexus NX infotainment.
Basically when I someone call me on display of infotainment system I can see just the phone number of caller but not its name and surname also if they are saved on phone's contact list.
In that phase, when the phone is ringing, caller's name appear on Nexus display but not on infotainment display.
I did some tests and I discovered that the problem is present with release from 4.4.4 to last one of Android s.o. (I did some downgrade of my phone S.O. with the goal to test various release).
I did also a test using an older china-phone with Android 4.2.2 and all has been OK (name + photo + phone number show on infotainment display); using a newest Mototola Moto G with Lollipop the problem is the same like with my Nexus 5.
Any idea about way to solve? I'm still waiting an answer from Lexus's costumers service about the problem...
Thanks to all for reading.

Unbelievable. Oneplus claims that a bug is now a feature.

Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!

I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie

MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.

nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!

nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all

kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.

So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders

problem with bluetooth

hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks

nobody got the same problem then

Relax, someone will come eventually... And no, I don't have.

westentertainer said:
hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks
Click to expand...
Click to collapse
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.

nabbed said:
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.
Click to expand...
Click to collapse
Thank you. What would I loose disabling phone audio on watch ?

westentertainer said:
Thank you. What would I loose disabling phone audio on watch ?
Click to expand...
Click to collapse
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.

nabbed said:
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.
Click to expand...
Click to collapse
Thank you