Push does not work on ZTE Blade V10 (Android 9) - 3CX App 16.1.0.41

[berl]

Hello!

The setup at our customers side:

Device Info
-------------------------------------------------------
Phone Model: [ZTE Blade | Android 9 || Samsung S9]
Firmware Version: [A!_Alpha_EEA_B10]
App Version: [16.0.1.41]

Additional details
-------------------------------------------------------
Handset: [Phone]
Contacts: [Local]
Connection: [WiFi|3G|4G]
Server Information: 3CX Server hosted at the proivder
Server OS: [Linux]
Server version: 16.0.3.676
-------------------------------------------------------

Our customer told us, that he has huge problems with the push-feature. Even the 3CX App is openend, it does not signal an incoming call.
He has several ZTE Blade mobilephones, they have only 3CX App on it - no other apps or firewall or antivirus app etc. He has some groups (they are intended for kindergartens), each handy of the same group is set up with the same google-account (there are between 3 and 6 mobilephones in on group).
If he is re-provisioning one of the mobilephones, then all (defintly ALL) other 3CX apps are working - but only for about 10 minutes. After this time the 3CX app does not react anymore.
He also tried the 3CX app with an Samsung S9 and he determined the exact same behavior.

I have two Huawei mobilephones with 2 extensions of this 3CX installation (I am approximatly 100km away from our customer) and with my mobilephones it works without problems...

What we have done till now:

• own google firebase project
• 3CX google push account
• another own google firebase project
• deinstallation of the 3CX apps and reinstallation and reprovisioning
• deinstallation of the 3CX app and installation of the new beta-app and reprovisioning
• deleting some extensions, recreating the extensions, reprovisioning the app
• deactivating the "acceppt push" in the extensions forwarding rules
• activation of this button again
• we created some logs on 3CX server - where you can see, that the push is sent
• we created logs on the android phones - where you can see, that no push is coming
• we deactivated the battery usage optimisation

We don't have any idea, what we can test anymore....

Does anyone have any ideas????

BR Christian Tanzer

 

[nb]

Hi Lets do the following:

1. Use 3CX Push. Dont stay moving push keys on google servers up and down. there is a confusion now.
Configure using 3CX inbuilt push
Restart all the services of the pbx so we can be sure that any push api keys from the portals you made are gone.

1. Get 1 ONE ZTE blade phone. Connected to power. Charging. Install new beta 3CX and QR provision it and reprovision. Provision this and tell me the extension number.
2. Give me an account - - send me a welcome email to [email protected]. I will connect and see your problem. I will c all the extension number in 2.

This needs to be restarted from complete clean slate.

Push WILL WORK. Must work. But some phones, are very sensitive and get confused if they are presented with multiple push api's.

Also another question - make sure on your zte that you have a reliable application like whats app or telegram. Can you confirm if you receive puish from these apps? So is it device issue, or app issue?

 

[nb]

Plus I made a whole list of things to check when you have push issues
https://www.3cx.com/blog/docs/android-push-issues/

 

[berl]

Hello nb,
thanks for your fast answer! Please check [email protected]-Mailbox .
We've done steps 1 and 2, so we are looking forward to your call tests!

 

[nb]

This is a ZTE phone issue.

Contact their support. Notifications are not coming in.
(Explain all the steps you did with push, unlock the screen and whats app)

We reviewed the log and there are some suspicious lines.

10-31 07:14:27.948 W/Firebase-FcmSer(20536): type=1400 audit(0.0:43742): avc: denied { read } for name="ubject_r:jsonweb_system_prop:s0" dev="tmpfs" ino=12149 scontext=u:r:untrusted_app:s0:c121,c256,c512,c768 tcontext=ubject_r:jsonweb_system_prop:s0 tclass=file permissive=0
10-31 07:14:27.948 W/Firebase-FcmSer(20536): type=1400 audit(0.0:43743): avc: denied { read } for name="ubject_r:jsonweb_system_prop:s0" dev="tmpfs" ino=12149 scontext=u:r:untrusted_app:s0:c121,c256,c512,c768 tcontext=ubject_r:jsonweb_system_prop:s0 tclass=file permissive=0

Looks like firebase service cannot read some temporary file. There is nothing at user level that can be done. And there is nothing we can do as devs of app. This is something that needs to be checked by ZTE development team as they are the ones that package android to the phone.

https://source.android.com/security/selinux/validate
https://stackoverflow.com/questions/53590540/avc-denied-kotlin-android-studio

This is a manufacturer issue.