New Android App Beta Available for Try-outs

Status
Not open for further replies.

Vali_3CX

Staff member
Joined
Dec 12, 2008
Messages
2,930
Reaction score
1,158
We’re on a roll: Our mobile apps team has just pushed out a new Android App Beta with major updates to connectivity, account switching and the app\'s all-around performance. This latest Beta joins the recently released v16 Update 5 Beta and iOS Beta, pushing the WFH (Work From Home) boundaries and capabilities to enable you to be productive no ma...
Continue reading the Original Blog Post.
 
  • Like
Reactions: jed and accentlogic
Did you bring back the "EXIT - Ignore PUSH"?
My custom statuses are already in use since we have been using 3CX for several years now, I don't have room to add a "Don't PUSH" status.
 
  • Like
Reactions: cobaltit
Did you bring back the "EXIT - Ignore PUSH"?
My custom statuses are already in use since we have been using 3CX for several years now, I don't have room to add a "Don't PUSH" status.

THIS! No idea why that was taken away.
 
@AE-IT and @cobaltit "EXIT - Ignore PUSH" will not come back... Reason is stated here:
https://www.3cx.com/docs/android-app-faq/#h.lcteeu5yq5kd

Quoting;

"Exit without push has been removed because Firebase servers do not like receiving high priority message requests.

When the user sets “Exit without push”, the app/device informs the Firebase server to unsubscribe. The 3CX PBX however, still assumes that it has to send requests on calls, so it sends an unwanted High priority message to Firebase global servers. In return, the server receives something to process even though the user has already requested not to be notified.

If this happens too often, Firebase has the right to block PUSH requests. This is the reason PUSH might not work, and why “Exit without push” has been removed."

Ling from Google's firebase statement https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message

Quoting;
High priority. FCM attempts to deliver high priority messages immediately, allowing the FCM service to wake a sleeping device when necessary and to run some limited processing (including very limited network access). High priority messages generally should result in user interaction with your app or its notifications. If FCM detects a pattern in which they don't, your messages may be de-prioritized. Android P introduced app standby buckets which limit the number of FCM high priority messages you can send to your app that don't result in the user using your app or viewing a notification. If, in response to a high priority message, a notification is displayed in a way that is visible to the user, then your app standby bucket quota will not be consumed by that message.

You have alternatives,
1. Use V16 Update 5 by configuring Automatic Profiles or Manual Profiles as you wish from your WebClient or App.Explained here;
https://www.3cx.com/docs/android-app-faq/#h.lcteeu5yq5kd

2. Android 10 has a new feature "Digital Wellbeing" https://wellbeing.google/tools/ named "Pause App", you can achieve this by pressing on the app long press. This basically will paused the app for the rest of the day. Using Android 10, this feature should satisfy your needs but I cannot guarantee that they come pre-installed :)
 
Last edited:
@MichaelB

I hadn't come across that article and I understand the technical reasoning. Is there not a way to make a button/setting in the app to reach out directly to the 3CX instance to disable push then? The profile trick will work for many users but if that's the recommended path then 3CX would need to make more profile slots or perhaps just add another fixed profile option for folks like @AE-IT
 
@cobaltit, Yes this is something which we are reviewing, thanks for your feedback.
 
Last edited:
  • Like
Reactions: accentlogic
I was going to open a feature request but apparently I don't have permission to post in that forum so I'll post it here and hopefully MichaelB will be kind enough to move it to feature requests (or fast-track it straight to the Development team ;)).

Feature Request: Status & Custom Status Upgrade.
1) Adding an additional "Available + Mobile App" status so there would be two default "Available" statuses.
2) Make existing custom statuses more flexible by allowing us to choose if they act as an "available" or an "away" status.
3) If PUSH is enabled for a given status, disable the option to "Ring my mobile simultaneously"; or make "Ring my mobile..." automatically disable PUSH for that status - No amount of user training is enough to stop a user with the app installed from also enabling "Ring my mobile..."

Thank you.
 
Is there some idea of a date for this update to be released?
Thanks!
 
Fairly certain it will be released this year :)
 
I have discovered two problems at least on Xiaomi Mi 9 Pro with Android 10 and the last beta version of 3cx:
1) frequently when the phone is in screen lock and a call is incoming i try to answer the call but if i press the button to answer nothing happen.
2) Frequently the phone is asking to give permission to the microphone to the 3cx App. If i don't give access to the microphone i cannot use the app. I gave permanently access to the microphone but the phone is still asking to give it. This is very annoying.
regards
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,991
Messages
590,167
Members
164,929
Latest member
Cloudstar