- Joined
- Feb 2, 2017
- Messages
- 221
- Reaction score
- 9
Android 5.1.1 on Samusung Galaxy SM-G530A (I think Galaxy S5 Prime) and same behavior on Galaxy S8
If 3cx is in focus (in the front) and the screen is turned off by the power button, incoming calls ring the phone and turn the screen on with the 3CX answer / decline option.
If I go to the android home screen (3cx in background now) and the screen is turned off using the power button, incoming call rings the phone and the screen comes on but not on 3CX but rather the locked screen (swipe to unlock) with no option to answer. If I swipe the screen to unlock, I'm presented with the android home screen while it's still ringing. I have to find the 3CX app either via running apps button or start the app from the screen and then I'm presented with the option to answer / decline.
I had tested the android client in a test environment with earlier versions and don't remember seeing any of this. Now we have gone live in 15.5.3849.1 in our live environment that we just turned up a month ago and I have this issue with a few android clients that I've deployed across various phones. Phone client version is 15.1.90.
Seems like a bug but I would imagine it would be more prevalent or noted on since I'm not using any hardware or software out of the ordinary.
Any one seen this issue before?
Thanks
Shawn
If 3cx is in focus (in the front) and the screen is turned off by the power button, incoming calls ring the phone and turn the screen on with the 3CX answer / decline option.
If I go to the android home screen (3cx in background now) and the screen is turned off using the power button, incoming call rings the phone and the screen comes on but not on 3CX but rather the locked screen (swipe to unlock) with no option to answer. If I swipe the screen to unlock, I'm presented with the android home screen while it's still ringing. I have to find the 3CX app either via running apps button or start the app from the screen and then I'm presented with the option to answer / decline.
I had tested the android client in a test environment with earlier versions and don't remember seeing any of this. Now we have gone live in 15.5.3849.1 in our live environment that we just turned up a month ago and I have this issue with a few android clients that I've deployed across various phones. Phone client version is 15.1.90.
Seems like a bug but I would imagine it would be more prevalent or noted on since I'm not using any hardware or software out of the ordinary.
Any one seen this issue before?
Thanks
Shawn