Texting Bug Identified in Sync v4.1.3
9/10/12, 04:42 PM
#41
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
9/14/12, 05:30 PM
#43
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Hey guys, I've come up with a workaround if you're comfortable compiling your own Android ROM from Cyanogenmod.
CM7 (Gingerbread) & CM9 (ICS) have a MAP profile built in. This can be modified to work-around the SYNC MAP bug. You need to trick the ROM to use the FROM: field as the TO: field, since Ford mixed it up on their end and reads the TO: field into SYNC. I've got a working port of this feature in review for CM10 (Jelly Bean) right here that I'm running with.
Once you've got your build environment setup with CM7, CM9, or CM10, open up
packages/apps/Bluetooth/src/com/android/bluetooth/map/MapUtils/MapUtils.java and find this line (It's on line 539 as of today):
sb.append("TEL:").append(bmsg.recipient_vcard_phon e_number)
Replace it with this line:
sb.append("TEL:").append(bmsg.originator_vcard_pho ne_number)
So all you're doing is changing the word "recipient" to "originator". This line exists twice in this file, once for SMS and once for MMS. I just fixed the first one since I don't care about MMS in SYNC.
*This forum seems to be adding a space in the middle of my code lines. Make sure you're looking for a line without a space and replacing it with a line without a space.
CM7 (Gingerbread) & CM9 (ICS) have a MAP profile built in. This can be modified to work-around the SYNC MAP bug. You need to trick the ROM to use the FROM: field as the TO: field, since Ford mixed it up on their end and reads the TO: field into SYNC. I've got a working port of this feature in review for CM10 (Jelly Bean) right here that I'm running with.
Once you've got your build environment setup with CM7, CM9, or CM10, open up
packages/apps/Bluetooth/src/com/android/bluetooth/map/MapUtils/MapUtils.java and find this line (It's on line 539 as of today):
sb.append("TEL:").append(bmsg.recipient_vcard_phon e_number)
Replace it with this line:
sb.append("TEL:").append(bmsg.originator_vcard_pho ne_number)
So all you're doing is changing the word "recipient" to "originator". This line exists twice in this file, once for SMS and once for MMS. I just fixed the first one since I don't care about MMS in SYNC.
*This forum seems to be adding a space in the middle of my code lines. Make sure you're looking for a line without a space and replacing it with a line without a space.
Last edited by Zathu; 9/14/12 at 05:42 PM.
10/5/12, 06:38 AM
#46
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Haha, awesome. What I wouldn't give for a decent open source infotainment system.
But in all seriousness, this is getting pretty neglectful. It's now been over two months since Jaclyn confirmed that Ford is aware of the issue. I've spent a great deal of time testing this issue and trying to make Ford aware of it through various avenues, when the fix will take a significantly less amount of time. I've gone as far as compiling a modified Android ROM from source to prove how simple the bug is. I believe that someone with access to the SYNC repo just needs to do the following:
Jaclyn, is there anything further we can do to help expedite this update? I believe it will be a very simple fix once someone looks at it. Give me the code and an NDA and I'll fix it!
But in all seriousness, this is getting pretty neglectful. It's now been over two months since Jaclyn confirmed that Ford is aware of the issue. I've spent a great deal of time testing this issue and trying to make Ford aware of it through various avenues, when the fix will take a significantly less amount of time. I've gone as far as compiling a modified Android ROM from source to prove how simple the bug is. I believe that someone with access to the SYNC repo just needs to do the following:
- Checkout the SYNC Gen1 v4.1.3 tag
- Find the bMessage parser function
- Change the originator variable to parse from the correct TEL: line from the bMessage (Needs to read the first TEL: and NOT the second)
- Run the build process and distribute update
Jaclyn, is there anything further we can do to help expedite this update? I believe it will be a very simple fix once someone looks at it. Give me the code and an NDA and I'll fix it!
Last edited by Zathu; 10/5/12 at 07:09 AM.
10/9/12, 02:57 PM
#47
MOTM Committee Member
Zathu has done great work here! Unfortunatley there is likely a vast amount of red tape at both Ford and Microsoft that must be overcome before this simple fix can be attained 
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
10/9/12, 03:04 PM
#48
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Zathu has done great work here! Unfortunatley there is likely a vast amount of red tape at both Ford and Microsoft that must be overcome before this simple fix can be attained
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
10/9/12, 04:04 PM
#49
Tasca Super Boss 429 Member
Zathu has done great work here! Unfortunatley there is likely a vast amount of red tape at both Ford and Microsoft that must be overcome before this simple fix can be attained
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
On a slightly related note, I wish more phone manufacturers would adopt MAP. I think I have to root my Nexus S just to enable it
Red tape or not, there is an issue here that needs to be fixed. We have the Ford In Vehicle Support Team here to help us, and they have done very little to keep us informed as to the status of getting an update or any information for that matter. Makes me wonder why they are even here.
Deysha is here several times a day updating people on their orders and what I feel is going above and beyond to keep people updated, but yet the In Vehicle team just sits back and does nothing.
I want a refund.
[/soapbox off]
10/9/12, 04:27 PM
#50
MOTM Committee Member
Actually, it's interesting because almost all of the Android device makers bake MAP into their flagship device ROMs, such as the Galaxy S phones, RAZR, Droid, HTC, etc. That said, Google has yet to add MAP upstream to AOSP which is why you don't see it on the stock ROM of Nexus devices. I'm hoping the introduction of MAP to the iPhone in iOS 6 drives Google to put it in AOSP so that all of the Android devices use the same standardized implementation so I don't have to do things like port iffy code into Cyanogenmod :P.
Red tape or not, there is an issue here that needs to be fixed. We have the Ford In Vehicle Support Team here to help us, and they have done very little to keep us informed as to the status of getting an update or any information for that matter. Makes me wonder why they are even here.
Deysha is here several times a day updating people on their orders and what I feel is going above and beyond to keep people updated, but yet the In Vehicle team just sits back and does nothing.
I want a refund.
[/soapbox off]
Deysha is here several times a day updating people on their orders and what I feel is going above and beyond to keep people updated, but yet the In Vehicle team just sits back and does nothing.
I want a refund.
[/soapbox off]
I just know the Ford In Vehicle Support Team kind of has their hands tied. Since they're not the acutal ones doing the fixing they can't really help other than to relay info back and forth between us and the engineers. They probably don't have good news yet which is why nothing is being said.
10/10/12, 02:10 PM
#51
Ford In-Vehicle Technology Rep
Haha, awesome. What I wouldn't give for a decent open source infotainment system.
But in all seriousness, this is getting pretty neglectful. It's now been over two months since Jaclyn confirmed that Ford is aware of the issue. I've spent a great deal of time testing this issue and trying to make Ford aware of it through various avenues, when the fix will take a significantly less amount of time. I've gone as far as compiling a modified Android ROM from source to prove how simple the bug is. I believe that someone with access to the SYNC repo just needs to do the following:
But in all seriousness, this is getting pretty neglectful. It's now been over two months since Jaclyn confirmed that Ford is aware of the issue. I've spent a great deal of time testing this issue and trying to make Ford aware of it through various avenues, when the fix will take a significantly less amount of time. I've gone as far as compiling a modified Android ROM from source to prove how simple the bug is. I believe that someone with access to the SYNC repo just needs to do the following:
- Checkout the SYNC Gen1 v4.1.3 tag
- Find the bMessage parser function
- Change the originator variable to parse from the correct TEL: line from the bMessage (Needs to read the first TEL: and NOT the second)
- Run the build process and distribute update
Red tape or not, there is an issue here that needs to be fixed. We have the Ford In Vehicle Support Team here to help us, and they have done very little to keep us informed as to the status of getting an update or any information for that matter. Makes me wonder why they are even here.
I just know the Ford In Vehicle Support Team kind of has their hands tied. Since they're not the acutal ones doing the fixing they can't really help other than to relay info back and forth between us and the engineers. They probably don't have good news yet which is why nothing is being said.
I followed up with engineering again today and provided them a link to this thread; I'm just waiting to hear back.
Jaclyn
Last edited by FordIVTteam; 10/10/12 at 02:11 PM.
10/10/12, 04:27 PM
#53
Tasca Super Boss 429 Member
07/24/12
09/10/12
09/12/12
10/10/10
Seriously? You've been promising updates and waiting to hear back from engineering since the end of July. Here it is nearly the middle of October and you keep giving us canned responses from your training manual. 
Time to get this escalated.
Time to get this escalated.
10/11/12, 08:31 AM
#55
Ford In-Vehicle Technology Rep
You're welcome, stangfoeva!
I wish I had more info, denlem, but I'm just the middleman here. I've escalated this issue as a whole, but I can get you directly in touch with a case manager. PM me your VIN, mileage, and the name of the dealership you typically work with.
Good call, Zathu, thanks!
The second I hear something, I'll post.
Jaclyn
The second I hear something, I'll post.
Jaclyn
Last edited by FordIVTteam; 10/11/12 at 01:22 PM.
10/11/12, 08:43 AM
#57
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
10/11/12, 08:46 AM
#58
Legacy TMS Member
Guys be sure to interact with all fellow forum members in a respectful way. If you're unsatisfied with the lack of updates or feel that you're not getting satisfaction then feel free to contact your local dealer; let's not pile on fellow forum members unnecessarily.
10/11/12, 10:08 AM
#60
Tasca Super Boss 429 Member
Originally Posted by Zathu
v4.1.3 is the initially shipping version for the 2013s, I don't believe it's posted for other years.