Android App 16.7.6.105 Not Vibrating Outside of App

[timmehb]

Another issue we are having reported by all of our CAT S42 Users.

This is on 16.7.6.105 and Android 10.
We have a user who is currently on 16.6 who doesn't have the issue, again on Android 10.

Vibrate is enabled within the Application Settings.
When a call is made to the device and the App is awake and in foreground, The phone vibrates.
When a call is made to the device and the App is in the background, the phone does not vibrate.

This is consistent across all CAT S42 devices without fail.

 

[VasilisV_3CX]

Hi @timmehb,

Thank you for reporting this, it is a known issue currently being looked at.

 

[petervale]

+1 - we're an MSP for roughly 1000 clients, and have this same fault reported by all of our 3CX clients using Android devices (including all of our internal users). Please let me know when this will be fixed as we are experiencing quite a bit of pushback from new clients we are trying to transition to 3CX from alternative packages so is costing us sales.

 

[timmehb]

I was just going to pop on to see if there was an update on this issue.

We run our Wifi phones on a Factory Floor so we rely on the Vibration - not having as such means the system is pretty much not working for the masses.

What is odd to me, the incoming call notification does not vibrate - whilst the missed call notification does.

What could be different between them?

 

[ghostzero]

I noticed the same, see: https://www.3cx.com/community/threads/android-app-16-7-6-105-not-vibrating-outside-of-app.82070/

 

[petervale]

Hi @timmehb,

Thank you for reporting this, it is a known issue currently being looked at.

Hi @timmehb,

Thank you for reporting this, it is a known issue currently being looked at.

Any update on this, trying to get some new deals across the line

 

[NickD_3CX]

Any update on this, trying to get some new deals across the line

Not yet, but we will update this thread once it has been fixed.

 

[ChrisC_3CX]

A new 3CX Android BETA (version 16.7.8.121) has just been released that should fix this issue!

Please try it out and let us know how it goes!