Hi,
I purchased a new Moto X pure a couple weeks ago and it is dropping my Plantronics Voyager Legend ear piece when I am on a call and a new one comes in (regardless if I let it go to voicemail, try to send it to voicemail, rings in the background or I try to switch callers and pick up the new call); when a call comes in (no other call already on the phone) and I depress the call answer button on the Voyager Legend, it picks up and immediately drops to the phone handset. It is also dropping the earpiece at other intermittent times. I have to turn the ear piece off and back on to pick up a call in progress already but, doesn't always work.
Initially I thought my ear piece had just gone bad, even though it worked normally with my Galaxy S5 and I purchased a new Plantronics Voyager Legend and the new unit also has the same issues but, also works great with the Galaxy S5. I am now convinced this is a software issue on the Moto X Pure.
Has anyone else had this issue and does anyone know how to possibly fix the issue?
Thanks,
Chris
I purchased a new Moto X pure a couple weeks ago and it is dropping my Plantronics Voyager Legend ear piece when I am on a call and a new one comes in (regardless if I let it go to voicemail, try to send it to voicemail, rings in the background or I try to switch callers and pick up the new call); when a call comes in (no other call already on the phone) and I depress the call answer button on the Voyager Legend, it picks up and immediately drops to the phone handset. It is also dropping the earpiece at other intermittent times. I have to turn the ear piece off and back on to pick up a call in progress already but, doesn't always work.
Initially I thought my ear piece had just gone bad, even though it worked normally with my Galaxy S5 and I purchased a new Plantronics Voyager Legend and the new unit also has the same issues but, also works great with the Galaxy S5. I am now convinced this is a software issue on the Moto X Pure.
Has anyone else had this issue and does anyone know how to possibly fix the issue?
Thanks,
Chris
No comments:
Post a Comment