Texting Bug Identified in Sync v4.1.3
10/11/12, 10:15 AM
#61
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
10/12/12, 05:01 PM
#62
Tasca Super Boss 429 Member
After I logged into the syncmyride website I was told I had an update waiting and I did the update to 4.1.3 myself on 07/5/12 and then texting stopped working.
10/15/12, 12:09 PM
#64
Ford In-Vehicle Technology Rep
Hi, all -
To clarify, 4.1.3 was released in late May. All 2013 Mustangs were released with this version and possibly some late build 2012s. There hasn't been an update to this version yet.
Jaclyn
To clarify, 4.1.3 was released in late May. All 2013 Mustangs were released with this version and possibly some late build 2012s. There hasn't been an update to this version yet.
Jaclyn
10/16/12, 01:30 AM
#65
Member
Join Date: October 16, 2012
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
Well I have been googling this problem for a day and found this forum.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
10/16/12, 08:15 AM
#66
Ford In-Vehicle Technology Rep
Well I have been googling this problem for a day and found this forum.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
Welcome to the forum! I'm the In-Vehicle Technology girl. You'll see me in and out of various threads. Our engineers are aware of the text messaging concern and are further investigating. Keep in mind, in order for a phone to work with this feature, it must support Message Access Profile, better known as MAP. This is a Bluetooth standard developed for the exchange of text messages. As I obtain new information, I'll be sure to pass it along.
If you have any additional questions, PM me any time.
Jaclyn
Last edited by FordIVTteam; 10/16/12 at 08:20 AM.
10/16/12, 01:43 PM
#67
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
Well I have been googling this problem for a day and found this forum.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
I don't have a mustang but do have a 2013 focus with ver Gen1 - V4.1.2.F according to the history report but I am having the same problem. all text say they have come from me and the reply get sent to me. This is with a galaxy 3 phone.
10/20/12, 09:26 AM
#68
Tasca Super Boss 429 Member
If i'm not mistaken, 2013 Mustangs started to be built on Feb 27th. So if 4.1.3 was not released until late May, then how does it get into the March, April, and early May builds?
10/21/12, 08:53 AM
#69
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
I tested v4.1.3 with an iOS 6 iPhone today. It just says "Unknown" as the sender. I'm wondering if this is because of the same issue described in the OP from Android, but Apple's bMessage doesn't include two TEL fields or something?
10/22/12, 10:22 AM
#70
Ford In-Vehicle Technology Rep
I just received word from engineering that it's possible for an early build 2013 to have left the factory with 4.1.2.
http://Support.Ford.com/sync-technol...atibility-sync
Stay tuned!
Jaclyn
Last edited by FordIVTteam; 10/22/12 at 10:23 AM.
10/22/12, 10:26 AM
#71
Tasca Super Boss 429 Member
Originally Posted by FordIVTteam
Hey, denlem -
I just received word from engineering that it's possible for an early build 2013 to have left the factory with 4.1.2.
10/25/12, 01:12 PM
#72
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
11/4/12, 05:50 PM
#74
Member
Join Date: October 28, 2012
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
Any more info on this fix? I've had my stang since April and have reported this to Ford in May, I can't believe there is no fix for this yet. 6 Months is an awful long time to fix a bug in software. One of the reasons I bought a Ford is to have this feature in my vehicle so I could keep up with work without taking my eyes off the road.
11/5/12, 04:43 PM
#75
Mach 1 Member
I hope an updated version will be posted soon... I've been following this thread since it started....
11/5/12, 05:26 PM
#76
Tasca Super Boss 429 Member
It's just the same old "i'm waiting for an answer from engineering".
Sounds like more of an excuse than support.
We also seem to be ignored rather than updated.
Sounds like more of an excuse than support.
We also seem to be ignored rather than updated.
11/10/12, 08:42 AM
#77
V6 Member
Thread Starter
Join Date: March 14, 2012
Location: Frederick, MD
Posts: 74
Likes: 0
Received 0 Likes
on
0 Posts
I know some of you are getting desperate here. As I said before, rooted Android users can work around this issue, but you don't have to go as far as compiling your own ROM. This variable switch can actually be achieved by smali hacking your ROM's Bluetooth APK. Samsung phones have BluetoothMap.apk, HTC phones have QctBluetoothMap.apk, and LG, Motorola and Cyanogenmod have it in Bluetooth.apk.
For anyone that wants to try it themselves, I have this batch script set up for doing it (there are some obvious dependencies, read up on smali hacking if they don't look familiar):
For anyone that wants to try it themselves, I have this batch script set up for doing it (there are some obvious dependencies, read up on smali hacking if they don't look familiar):
@ECHO OFF
ECHO Extracting zip...
unzip -o data-in\Bluetooth.apk -d unzip\
ECHO Generating smali...
java -jar bin\baksmali-1.4.0.jar -o smali\ unzip\classes.dex
ECHO Done. Make the changes in smali...
PAUSE
ECHO Rebuilding dex...
java -jar bin\smali-1.4.0.jar smali\ -o data-out\classes.dex
xcopy /Y data-out\classes.dex unzip\classes.dex
ECHO Rebuilding APK...
cd unzip
7z a -tzip ..\data-out\Bluetooth.apk *
cd ..
ECHO Signing APK...
REM keytool -genkey -v -keystore my-personal-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000
jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore my-personal-key.keystore data-out\Bluetooth.apk alias_name
ECHO Done.
PAUSE
ECHO Extracting zip...
unzip -o data-in\Bluetooth.apk -d unzip\
ECHO Generating smali...
java -jar bin\baksmali-1.4.0.jar -o smali\ unzip\classes.dex
ECHO Done. Make the changes in smali...
PAUSE
ECHO Rebuilding dex...
java -jar bin\smali-1.4.0.jar smali\ -o data-out\classes.dex
xcopy /Y data-out\classes.dex unzip\classes.dex
ECHO Rebuilding APK...
cd unzip
7z a -tzip ..\data-out\Bluetooth.apk *
cd ..
ECHO Signing APK...
REM keytool -genkey -v -keystore my-personal-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000
jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore my-personal-key.keystore data-out\Bluetooth.apk alias_name
ECHO Done.
PAUSE
Last edited by Zathu; 11/23/12 at 04:44 PM.
11/10/12, 11:51 AM
#80
I don't know why you guys have to receive texts while driving anyway. Do your phones make and receive calls? I can see a future where cellular phones no longer make or take calls because you antisocial people don't want to actually speak to someone anymore. :damnkidsalltheydoistext:
Last edited by 11SHELBYGT500; 11/10/12 at 11:53 AM.