Texting Bug Identified in Sync v4.1.3
1/21/13, 09:13 AM
#102
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Here's some relief for those of us with recent Samsung Galaxy phones (root required). I've pre-patched these MAP profile APKs to be swapped out with the stock ones. They'll send the bMessage to SYNC out of spec to align with what SYNC reads so that the sender is correct. To install, browse to /system/app in ES File Manager and rename BluetoothMap.apk and BluetoothMap.odex (if present) to BluetoothMap.apk.backup and BluetoothMap.odex.backup. Cut and paste this APK. Long press the file, go to properties, and set permissions. Check the "read" permission for group and everyone so that it's "rw-r--r--". Reboot, unpair from SYNC, re-pair to SYNC.
Galaxy S3: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
Galaxy Note 2: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
*These were build from the AT&T versions of 4.1.1. They should work across all carriers. I haven't done a diff but I suspect that they're actually the same. The Note 2 APK was also reported to work on a Galaxy S2.
Galaxy S3: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
Galaxy Note 2: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
*These were build from the AT&T versions of 4.1.1. They should work across all carriers. I haven't done a diff but I suspect that they're actually the same. The Note 2 APK was also reported to work on a Galaxy S2.
Last edited by Zathu; 1/21/13 at 09:25 AM.
1/22/13, 04:05 PM
#103
MOTM Committee Member
Here's some relief for those of us with recent Samsung Galaxy phones (root required). I've pre-patched these MAP profile APKs to be swapped out with the stock ones. They'll send the bMessage to SYNC out of spec to align with what SYNC reads so that the sender is correct. To install, browse to /system/app in ES File Manager and rename BluetoothMap.apk and BluetoothMap.odex (if present) to BluetoothMap.apk.backup and BluetoothMap.odex.backup. Cut and paste this APK. Long press the file, go to properties, and set permissions. Check the "read" permission for group and everyone so that it's "rw-r--r--". Reboot, unpair from SYNC, re-pair to SYNC.
Galaxy S3: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
Galaxy Note 2: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
*These were build from the AT&T versions of 4.1.1. They should work across all carriers. I haven't done a diff but I suspect that they're actually the same. The Note 2 APK was also reported to work on a Galaxy S2.
Galaxy S3: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
Galaxy Note 2: https://dl.dropbox.com/u/50213/andro...uetoothMap.apk
*These were build from the AT&T versions of 4.1.1. They should work across all carriers. I haven't done a diff but I suspect that they're actually the same. The Note 2 APK was also reported to work on a Galaxy S2.
You've done a great service to everyone for helping correct the issue. Thank you sir
1/22/13, 04:21 PM
#104
Tasca Super Boss 429 Member
1/22/13, 04:23 PM
#105
MOTM Committee Member
1/31/13, 12:23 PM
#106
Member
Join Date: January 31, 2013
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
A couple of notes 1) didn't work on 4.0.4 Att android build for me so you need to upgrade to stock 4.1.1 rom.
2) those unfamiliar with ES Explorer, to rename and move apk, first time in you need to goto Root Settings and check Root Explorer and Mount File System as writable boxes. Then you can copy and change permissions. Make sure you undo these checks when done so you don't accidently delete something from system folder unless you really mean to. I would guess most of you would not want to always maintain root access to these dirs.
3/4/13, 02:41 PM
#107
Member
Join Date: October 28, 2012
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
Well after having my Mustang for a year now not one update to solve the Text Messaging problem. I just got off the phone with Ford Sync customer service and they don't know anything about the problem we have been describing even though I've called numerous times about it for a year.
She stated I had the current version which is 4.1.3, even though now the 2014 Mustangs have version 4.1.4.t
I am now going to give up on this since Ford isn't listening to me or anyone else on this matter just their wallets.
I have called, emailed and chatted to Ford about this for a year now and nothing, they even state over and over again that they've never heard of this problem but yet we have a member on this forum who works for FORD that let them know and still nothing.
Ford you have really let me and others down and you should be ashamed of yourselves. We give you our hard earned money and even if you can't fix the problem (which I highly doubt) you could at least acknowledge the problem.
Thanks for nothing. I'll think twice about buying from you again.
Just a quick note, thank you to the people on this forum who are willing to find a work around solution to this problem. It is greatly appreciated.
She stated I had the current version which is 4.1.3, even though now the 2014 Mustangs have version 4.1.4.t
I am now going to give up on this since Ford isn't listening to me or anyone else on this matter just their wallets.
I have called, emailed and chatted to Ford about this for a year now and nothing, they even state over and over again that they've never heard of this problem but yet we have a member on this forum who works for FORD that let them know and still nothing.
Ford you have really let me and others down and you should be ashamed of yourselves. We give you our hard earned money and even if you can't fix the problem (which I highly doubt) you could at least acknowledge the problem.
Thanks for nothing. I'll think twice about buying from you again.
Just a quick note, thank you to the people on this forum who are willing to find a work around solution to this problem. It is greatly appreciated.
Last edited by nebraskachers; 3/4/13 at 02:43 PM. Reason: Forgot something
3/4/13, 04:12 PM
#108
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
I'm starting to feel the same way. On the other hand, who has done it better than Ford? Ford has the best features on paper, but the execution is sloppy. In what I've seen, the other manufacturers don't have nearly as much on paper, so the more basic features inherently just work because they're not really breaking any new grounds. As much as I like to see the built-in car tech advance, to meet the expectations set by our other devices we need someone other than a car manufacturer to back the development. If aftermarket stuff could touch the integration that SYNC has I'd be sold.
You're welcome! Thank you for pushing Ford on this through their official channels. Do you have a rooted Android phone that you were able to apply the workaround to?
3/4/13, 06:04 PM
#109
Member
Join Date: October 28, 2012
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
Ill admit that I love the car and the features if they all worked.
No I don't have a rooted phone, I'm just not into doing that. It is a Samsung Galaxy S3 with Sprint. When I get a chance I will try it on a 2014 Mustang.
No I don't have a rooted phone, I'm just not into doing that. It is a Samsung Galaxy S3 with Sprint. When I get a chance I will try it on a 2014 Mustang.
3/6/13, 02:09 PM
#111
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
The social FordIVTeam representation has done all it can do for us, this isn't really what that mechanism is designed for. It's great to have resources like that around for the right questions. IMO the blame for something like this can only go to Ford's management for not properly funding and executing effective software maintenance.
Last edited by Zathu; 3/6/13 at 02:13 PM.
3/7/13, 02:01 AM
#112
Tasca Super Boss 429 Member
The social FordIVTeam representation has done all it can do for us, this isn't really what that mechanism is designed for. It's great to have resources like that around for the right questions. IMO the blame for something like this can only go to Ford's management for not properly funding and executing effective software maintenance.
I'm done with this and moving on.
Last edited by tom281; 3/7/13 at 11:50 AM.
3/7/13, 11:56 AM
#113
Legacy TMS Member
Denlem, some of your comments are unnecessary. I understand that you're frustrated and have been hoping for an update from the Ford team but apparently the few people in this thread that are upset with the problem aren't enough to justify it being corrected. Right or wrong, either way you don't need to make comments that are demeaning or insulting to the Ford team, so I edited your post.
I also am closing this thread until a Ford team member PMs me with an update, at which time I will gladly open it back up.
I also am closing this thread until a Ford team member PMs me with an update, at which time I will gladly open it back up.
10/2/13, 03:33 PM
#115
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Good news! Ford has fixed the bug. I have attached an official technical service bulletin that confirms a fix for "Incorrect caller ID displayed for text messages", among other things.
The update was not available for me on syncmyride.com, so I had my dealer install it. I found the following version numbers to change:
I also now have a description of 4.2.1.4 on the syncmyride website:
Show your dealer the attached bulletin to get the update.
Finally!
The update was not available for me on syncmyride.com, so I had my dealer install it. I found the following version numbers to change:
OLD VERSION (4.1.3)
Auto Version Number
EC02345.8.10349_sp0.
FPN Number
DR3T-14D544-AD
NEW VERSION (4.2.1.4)
Auto Version Number
ED11545.8.10349_sp0.
FPN Number
DR3T-14D544-AE
Auto Version Number
EC02345.8.10349_sp0.
FPN Number
DR3T-14D544-AD
NEW VERSION (4.2.1.4)
Auto Version Number
ED11545.8.10349_sp0.
FPN Number
DR3T-14D544-AE
DR3T-14D544-AE
This new software will provide the following enhancements to your current SYNC® system:
- Updated Bluetooth device connectivity
- Improved system stability
- Improved media player functionality
- Enhanced voice recognition capabilities
- Optimized for use with Apple iOS 6 for incoming text messaging
This update includes improvements from all previous SYNC updates such as flattened phone grammar, improvements in device indexing, text messaging capabilities with the implementation of message access profile (MAP), and more. For additional information on previous updates, visit SYNCmyride.com.
Please Read: This update may take up to 20 minutes to complete. About 1 to 3 minutes after you begin the installation, you will hear an Installation Complete message. DO NOT REMOVE YOUR USB DRIVE OR TURN OFF YOUR VEHICLE. You must wait up to an additional 20 minutes until you receive a second Installation Complete message before removing your USB drive. During this interval, while the update is loading, SYNC® will not recognize your mobile phone or media device. Be sure your vehicle's engine is running (not in Accessory mode) throughout the entire installation process. Although your vehicle must be in Park when you initiate the installation process, once the download process has begun, you may drive your vehicle.
This new software will provide the following enhancements to your current SYNC® system:
- Updated Bluetooth device connectivity
- Improved system stability
- Improved media player functionality
- Enhanced voice recognition capabilities
- Optimized for use with Apple iOS 6 for incoming text messaging
This update includes improvements from all previous SYNC updates such as flattened phone grammar, improvements in device indexing, text messaging capabilities with the implementation of message access profile (MAP), and more. For additional information on previous updates, visit SYNCmyride.com.
Please Read: This update may take up to 20 minutes to complete. About 1 to 3 minutes after you begin the installation, you will hear an Installation Complete message. DO NOT REMOVE YOUR USB DRIVE OR TURN OFF YOUR VEHICLE. You must wait up to an additional 20 minutes until you receive a second Installation Complete message before removing your USB drive. During this interval, while the update is loading, SYNC® will not recognize your mobile phone or media device. Be sure your vehicle's engine is running (not in Accessory mode) throughout the entire installation process. Although your vehicle must be in Park when you initiate the installation process, once the download process has begun, you may drive your vehicle.
Finally!
Thread
Thread Starter
Forum
Replies
Last Post