Hi,
I found that after a recent ROM upgrade (on my Galaxy S5) that I was no longer seeing text messages presented on the dash display of my BMW - this had previously been working. After some reading in various XDA threads and (primarily) BMW forums I discovered that someone else had resolved their issues via deleting all existing text messages and re-pairing with the car. This also worked for me...but I then restored all my backed-up SMS messages and I *think* (TBC) that it's stopped working again.
Rather than simply delete them all again, can anyone advise on available apps or debug capability which look into the operation of the bluetooth MAPI protocol which I believe is used to transfer the SMS messages to the car. I suspect that either the car or phone is somewhere maintaining an index of messages which have already been transferred and this may need to be reset.
Of course, I could just archive the messages and avoid this all!
TIA - longshot I know!
Craig
Related
I have a 2012 Volkswagen GTI with the RNS-315 nav system. I noticed the other day when trying to call my wife via the nav that somehow the directory the phone sends doesn't have her number - only her name. I tried via both voice commands, and from the navigation display. I tried unpairing/repairing the phone, power cycling the phone, editing the contacts, etc...I have a vague feeling it might have something to do with having the contacts linked (Google to Facebook and Skype, etc) but I don't know for sure. I know it isn't the nav system because it's worked before, and I can dial her number manually via voice or from the nav screen. Bluetooth works fine otherwise; I can place a call from either the phone or the car.
I haven't tried clearing out my contacts yet; I want to avoid that. I also haven't tried (but will) calling a non-linked contact vs linked.
I'm running CleanROM 4.5, stock kernel, nothing special.
Anyone else had issues with their phones sending names without numbers in contact lists?
Hi, all. Did a search, couldn't find anything on this, wondering if it's only me.
I've got the T-Mobile GS3. Use a bluetooth connection with a Pioneer AVH-P3200BT head unit (http://www.pioneerelectronics.com/PUSA/Car/DVD-Receivers/AVH-P3200BT).
My contacts and Missed Calls history syncs just fine with the head unit. However, on the head unit, my Received Calls and Dialed Calls histories aren't accurate. Mostly they're filled with 5 digit numbers and a just one of my contacts (who shouldn't be in the log at all) is repeated over and over. The call log that I bring up on the GS3 is accurate.
I don't have another head unit to try to sync with, so I'm wondering if the problem is with the phone or the head unit. I'm suspecting it's the phone, as my old Vibrant's logs were always correct, regardless of whether I was running stock or CM9.
So I was just wondering if anyone else was having this problem (or whether they've even checked).
I've tried deleting the pairing on both the phone and the head unit, rebooting both, and re-establishing the pairing to no effect.
Anyone?
Bump.
Let me ask this another way. Is anybody having no problem with their Received and Dialed calls being synced with their head unit? Is yours working well (if you have this feature on your head unit)?
No problems pairing the V10 to my Jeep and I can get Phonebook, Handsfree etc just fine, but it does not seem to support the reading or sending of TXT msgs from the Jeep. The TXT msg option on the Jeep is greyed out. It used to work with my G2/G3 just fine and I only noticed it was missing when after I did the TOT root on my H962 as I had to repair the phone.
Any ideas?
Thanks
Nathan
Got it working, did a UConnect update - removed the profile, added it again and made sure I selected that it was allowed to read my msgs during the pairing.
Funny thing i have similar issue and have done the pairing and deleting numerous times and no dice. So mu issues is its only one contact on my phone that doesnt come up but everything else does. Really dont know why?
Sorry if this question has been answered before.. I searched all over the internet without a specific and definitive answer.
Whenever I connect my phone to any vehicle via bluetooth, mobile numbers under one contact appear twice in the vehicle when that contact is selected. This is a pain in the butt when trying to make a voice call as the vehicle always says "there are multiple mobile numbers associated with this contact".
I technically know why this is happening but looking for a way to prevent it. You see, I believe the culprit is whatsapp or google duo, or any other app that uses phone numbers, and therefore link themselves to that certain contact.
Now, is there any way to prevent the number from showing up twice in the vehicle under that one contact?
I have tried:
1. Unlinking the contact, only for linking to reappear after a sync.
2. I tried turning off sync in whatsapp, but because Auto-Sync is on for all of android, it just turns itself back on.
3. Prevented whatsapp from accessing contacts, but this just turns all contacts into numbers in whatsapp which is not what I want.
4. Turning off Auto-Sync in android, works, but I don't want to use it because then I have to manually sync everything else including calendars which I update frequently.
Going in to contacts and selecting a customized view has no affect.
Now I technically know what the car is trying to do... one number for Phone dialing (cellular) and one number for Whatsapp (data) dialing, but I don't want that.
Any way to get just the cellular side of the contact to be shared with bluetooth?
P.S. This has nothing to do with specific phones. This is an Android issue as I've tried it with multiple phones across multiple vehicle makes. All have the same issue. However if you want this information too, I have a One Plus 5T and my wife has a pixel XL. I drive a 2018 Colorado with Chevrolet MyLink and she drives a 2013 Honda Civic with Handsfree Link.
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
GV00 said:
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
Click to expand...
Click to collapse
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
BigBossPlaya said:
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
Click to expand...
Click to collapse
Unfortunately, it was already off, so no dice there. Ulefone pushed an update I thought might have fixed it, but after about 18 hours of idle I sent a test message and it fell into the void. Opened up the messenger app again and sent another and that one arrived without issue, but no sign of the first.