The following opinion piece was submitted by Good and EVO reader Howard. Please contact us if you are interested in submitting a guest post of your own!

I just purchased a new Ford with MyFord Touch, which has the ability to read text messages over the speakers when connected to your mobile phone.  It’s a pretty simple feature when you think about it, but is amazingly useful in everyday life. The only thing is, your phone needs to support MAP (Message Access Profile) functionality. I was pretty surprised when I tried to setup my HTC EVO 4G LTE, only to find out that the phone does not support what should be such a basic feature as MAP.

To make things even more interesting, my old EVO 3D did.

I sent an email to HTC to investigate, and received this response:

Thank you Howard for contacting us in regards to the various features of the EVO 4G LTE Bluetooth. I’m glad you enjoyed the EVO 3D and have decided to move on up. I did a little looking around for any clue as to if the features you mentioned will be added to the updates planned for the EVO 4G LTE.
Unfortunately I was unable to locate anything definite. It is entirely possible but usually we don’t get any idea as to the content of an update until it’s released. I would suggest keeping an eye on the various blogs and social networks for further information.

I’m pretty surprised that neither HTC nor Sprint added this to their flagship phone – especially when their previous flagship phone had it. In fact, even Apple just added MAP support in iOS 6. How can we sit by and let Apple one up us?

I can only hope that HTC adds it soon to the EVO 4G LTE.

Editor’s update: As pointed out in the comments, many readers have been able to get this feature to work, while others are still having trouble with this specific feature, or with Bluetooth in general on the EVO 4G LTE. Howard (the reader who contributed the above post) notes that MAP is not listed as an officially supported Bluetooth profile in any EVO 4G LTE documentation, while it is for the EVO 3D. HTC’s online tech support obviously was not aware that this feature actually works, even if it is “unofficial.” In any case, thanks to those of you who corrected the original premise of this article!