Bri the Tech Guy
Newbie
I've recently been trying to get a phone for my partner, and the first device I tried was a BLU Vivo XL3 Plus - two of them in fact.
Both had a major problem in that neither could make outgoing calls. As soon as you would dial an outgoing call the device would put itself into Do Not Disturb mode, with the little crescent moon icon showing in the status bar at the top, and the call would never complete. You could occasionally "trick" the phone into completing a call if you switched to speaker phone, even with the DND icon showing, but this result was wildly inconsistent. It was consistently able to receive incoming calls and to send and receive text messages. Calling from the Google Hangouts app also worked without issue.
I have never experienced such with any device in the past, and was wondering if anyone else has encountered this issue with this specific device from BLU? It appears to be a software bug, as this occurred on two brand new devices, though it could have been for a specific production run and been corrected by now. This all occurred within the past two weeks, and both devices were purchased via Amazon (and they were very good about taking returns and issuing a refund).
It's a spectacular device for its price point, but also a spectacular failure if you can't make calls on it.
Both had a major problem in that neither could make outgoing calls. As soon as you would dial an outgoing call the device would put itself into Do Not Disturb mode, with the little crescent moon icon showing in the status bar at the top, and the call would never complete. You could occasionally "trick" the phone into completing a call if you switched to speaker phone, even with the DND icon showing, but this result was wildly inconsistent. It was consistently able to receive incoming calls and to send and receive text messages. Calling from the Google Hangouts app also worked without issue.
I have never experienced such with any device in the past, and was wondering if anyone else has encountered this issue with this specific device from BLU? It appears to be a software bug, as this occurred on two brand new devices, though it could have been for a specific production run and been corrected by now. This all occurred within the past two weeks, and both devices were purchased via Amazon (and they were very good about taking returns and issuing a refund).
It's a spectacular device for its price point, but also a spectacular failure if you can't make calls on it.