Update: Verizon has clarified their references below, and now states that the E815 does work with many in-car systems. Apparently, the device does support OBEX contact transfer for in-car Bluetooth systems, and that the hindered OBEX protocols are more directed at sending and receiving files. You can view an official PDF of the E815’s car kit support list >here.
We held off our coverage of Verizon’s launch of the Motorola E815 in order to see if it suffered the same fate as the V710 (hindered, crippled, and self-mutilated Bluetooth). For those of you that don’t know, the E815 is the EV-DO enabled successor to the V710.
Unfortunately, Verizon appears to have instated the same hindrances that plagued the V710, and even resulted in a class-action lawsuit. Quoting from vzw.com:
“The E815 supports Bluetooth Profiles for wireless headsets, hands-free accessories. Phonebook/datebook synchronization with optional Motorola Phone Tools or Verizon Wireless Mobile Office kit. It does not support all object exchange (OBEX) profiles.”
This is exactly the same situation the V710 on Verizon is in: forced to use cable options because they promote Verizon’s software+cable bundles, and disable those same options via Bluetooth. What’s even more odd is that after all this time, Verizon has not added that same statement to their V710 page, only making some vague reference to “certain profiles” being supported.
While Verizon may be out of the woods in terms of alerting customers as to what the E815 actually supports (since the V710 actually lists in device discovery profiles that have been internally disabled, hence the lawsuit), consumers will look to other options, such as the Samsung MM-A940, for more enabled options. Our suggestion to Verizon: don’t touch the SCH-A970 if you don’t want a mass CDMA defect to Sprint.