Fix kitkat SMS MAP (bluetooth) originator

@thuddome, I've uploaded a version 1.0.debug of the module to the xposed repo. It's flagged as "Experimental" (because it can spam the xposed log.) To get it, go into the xposed installer, tap on "download", find "BTSMSMapFix" and tap it...swipe from right to left a couple times until you see the "settings" page, and change that to "experimental".

You should then be able to download the updated 1.0.debug version. After ensuring that it's selected, reboot so it takes effect, and then try again with your head unit.

Here are some key things to look for in the xposed log:

BTSmsMapFix successfully hooked setVCardFromPhoneNumber -- this means that the hook took place. If you don't see this line, it means that Samsung renamed the package from the standard "com.android.bluetooth" (which wouldn't surprise me.)

BTSmsMapFix set originator phone number to XXXXX -- You should see this after getting an incoming SMS message while your phone is connected to your head unit. "XXXXX" should be replaced with a phone number that starts "+1" (Assuming your in the US), and then 10 more digits. (If you post your log, please leave the +1 in there, but remove the rest of the phone number.)

BTSmsMapFix reverting to original code with incoming set to (true|false) -- You might see these, but hopefully not when you get a new incoming SMS.

Take care
Gary

No +1s on anything. I had a bunch of texts, I deleted all but a few for this. None had a +1 and still getting "no number available".

Damn. Okay, I'll see what I can do again tonight. Assuming a phone number of "(123) 456-7890", how is that phone number showing up in that xposed log when you get a message? (What I'm trying to find out is if the number is just a string of 10 numbers, or if there is ANYTHING else in the string.)

I might throw together a quick test that just prepends a hard coded "+1" to the number to see if that works (as I'm guessing that you aren't getting any SMS messages from outside the USA.) If it does, I can dig deeper for a more proper solution...

Damn. Okay, I'll see what I can do again tonight. Assuming a phone number of "(123) 456-7890", how is that phone number showing up in that xposed log when you get a message? (What I'm trying to find out is if the number is just a string of 10 numbers, or if there is ANYTHING else in the string.)

I might throw together a quick test that just prepends a hard coded "+1" to the number to see if that works (as I'm guessing that you aren't getting any SMS messages from outside the USA.) If it does, I can dig deeper for a more proper solution...

Take care
Gary

It's just straight numbers "BTSmsMapFix set originator phone number to 3031234567" (This is exactly how it shows up)

I'm in Denver, area code is 303

I do get some SMS from overseas but don't worry about them. They are rare, maybe once a month. Not sure if it matters but I'm using Verizon's Messaging+ app right now, it's their customized version of the kitkat messaging.

xposed repo updated with version 1.1: adds support for CDMA devices.. tested on verizon Samsung Galaxy S5. Also corrects recipient vcards to use proper E164 phone numbers (instead of whatever slop might be in a user's contact list.)

Thanks to @thuddome for testing the changes. It's currently listed as a "beta" release type. As soon as someone tells me that I didn't break it between thuddome's last test and the cleanup I did afterwards, I'll change that to be a normal (stable) version.

xposed repo updated with version 1.1: adds support for CDMA devices.. tested on verizon Samsung Galaxy S5. Also corrects recipient vcards to use proper E164 phone numbers (instead of whatever slop might be in a user's contact list.)

Thanks to @thuddome for testing the changes. It's currently listed as a "beta" release type. As soon as someone tells me that I didn't break it between thuddome's last test and the cleanup I did afterwards, I'll change that to be a normal (stable) version.

Take care
Gary

I just tested 1.1, worked great! Verizon SGS5 with Jeep 430N RHB, text messages now announce sender's name instead of "no number available".

Man, I WISH my car would read text messages. I have a 2014 dodge dart with the uconnect 8.4 head unit and Samsung galaxy s5. I connect to Bluetooth fine, it shows who's called and I can load my phonebook, but whenever I try to select "messaging," it just says that my phone is incompatible.

Man, I WISH my car would read text messages. I have a 2014 dodge dart with the uconnect 8.4 head unit and Samsung galaxy s5. I connect to Bluetooth fine, it shows who's called and I can load my phonebook, but whenever I try to select "messaging," it just says that my phone is incompatible.

Yeah... I tried to figure out what was going on with the Dart, but the guy closed his garage door and just kept saying "don't touch my dart!"... Whatever...

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?