3CX phone for Android problems

[Rémy Faure-Vincent]

We recently deployed around 20 Samsung Galaxy Xcover for use with our new 3CX phone system, and they have been randomly unable to receive calls even after re-doing the entire Firebase configuration and checking twice that everything should be running fine.

• "no network" issue (while phone is running over reliable 4G mobile access)
• phone that doesn't ring at all, or does so a minute later (probably when finally acknowledging the firebase push)
• touchscreen accepting input from users' ear while on a call (what is the proximity sensor option for, really ?)
• application not restarting properly when asked to quit or quit without push
• application not coming to front when call is received on some phones (only the notification appears)
• calls take one to several seconds to be connected when touching the accept button
• bluetooth headsets have audio and microphone routing issues, not working at all in most cases

we tried a variety of solutions including switching from wifi to 4G, removing the lockscreen pattern, automating an application restart every minute but none worked reliably.

all the phones are running the same official Samsung Android build, with all Samsung system apps disabled via Gsuite admin (ensuring a nearly pure Android OS), with the same lack of restrictions.

Please take a look at Zoiper for something that works and take example.

We are extremely disappointed in this system, given that we switched to those smartphones because our old Aastra DECTs "have not been tested" by 3CX and thus are "incompatible".

We would also appreciate the application to be allowed for install on Chromebooks, since it is still locked out on the Play Store.

I am available for any inquiry and/or test on our deployment, before we switch back to the reliable SIP/DECT solution we had before.

 

[LeonidasG_3CX]

Hi nitrox,

In an hours time you can download the latest beta 196 where we've included the following fixes:

• Fixed an issue where answer and reject buttons were not visible during PUSH calls.
• Fixed an issue where a DTMF tone could get stuck playing forever.
• Fixed an issue where the device would get stuck in a "No Network" state and would need a restart.
  
  Read the changelog for more details.

 

[nitrox]

Hi nitrox,

In an hours time you can download the latest beta 196 where we've included the following fixes:

• Fixed an issue where answer and reject buttons were not visible during PUSH calls.
• Fixed an issue where a DTMF tone could get stuck playing forever.
• Fixed an issue where the device would get stuck in a "No Network" state and would need a restart.
  
  Read the changelog for more details.

ok, thank you

 

[countrycomp]

I've just updated to 196 with no configuration changes and now the app will not register with the server unless the WiFi is connected. The 3G is enabled but is not working at all. I hope my users don't update until this is fixed as we rely on 3G/4G for our Oncall staff.

 

[LeonidasG_3CX]

-196 is a beta, so your users won't be updating to it.

-Also can you provide a bit more information on the issue you're facing? You enable 3G and it doesn't connect? What do you see exactly? Can we have a screenshot? Also make sure that in the More > Settings > Advanced Settings > Allow 3G is enabled.

Let me know.

 

[jed]

Just for info, my Samsung 6 Edge was updated to 196 yesterday, and I just tryed to call it (after 10 hours sleep), and the phone is ringing instantly
Btw. the Phone is running on WiFi.

I have had customer complains that when they go from 3/4G to Wifi (and the phone is locked) the app wont register - they have to close 3CX and reopen it to register. I do hope all the latest fixing has solved this as well..

Seen from here (with WiFi) the App works like a charme

 

[LeonidasG_3CX]

Just for info, my Samsung 6 Edge was updated to 196 yesterday, and I just tryed to call it (after 10 hours sleep), and the phone is ringing instantly
Btw. the Phone is running on WiFi.

I have had customer complains that when they go from 3/4G to Wifi (and the phone is locked) the app wont register - they have to close 3CX and reopen it to register. I do hope all the latest fixing has solved this as well..

Seen from here (with WiFi) the App works like a charme

Nice. The "No Network" issue had nothing to do with 3G to WIFI switching. It could occur even when only WIFI is enabled. Glad to hear that it's possibly fixed. Lets see by Monday what more feedback we get before we close this off.

About your customer, lets see what happens once this client is fully released. We have a few more fixes and improvements to do before it's fully released, but you'l for sure see at least 1 more beta update before that.

 

[countrycomp]

Mine works fine with WiFi turned on but does not connect if WiFi is turned off or out of range. The 3G is definitely enabled. With no WiFi the status is "disconnected" and 'initializing" in the top right hand corner. This is on a Moto Z Play.

 

[LeonidasG_3CX]

Mine works fine with WiFi turned on but does not connect if WiFi is turned off or out of range. The 3G is definitely enabled. With no WiFi the status is "disconnected" and 'initializing" in the top right hand corner. This is on a Moto Z Play.

So you first see "disconnected", after a short time it says "initializing" and then back to disconnected?
Which version are you running? You can find this in More > Settings > About

 

[countrycomp]

15.5.196 .

 

[nitrox]

i have the same problem of countrycop with version 15.5.196.

 

[LeonidasG_3CX]

Trying it now with 196, not having this issue. Are you working with 3G 4G?

 

[nitrox]

Trying it now with 196, not having this issue. Are you working with 3G 4G?

It's already 196. The app doesn't connect to the pbx and i am not able to open Settings when i am connected via 4G. No problem in wifi.

 

[LeonidasG_3CX]

Interesting, we're looking into it right now. We've found that it works on one phone but not on another.

 

[LeonidasG_3CX]

Yep this is a bug related to the attempt to fix the "No Network" issue. We'll fix it and in the mean time remove the beta.

 

[LeonidasG_3CX]

The beta has been updated with a few fixes.

The few things pending are:
-Slowness to connect in some cases.
-No Network
-Audio Routing

You can expect these fixed in the next several weeks. No further updates until then.

 

[Peter Richardson]

same issue here:

https://www.3cx.com/community/threads/android-soft-phone-stuck.53061/#post-217440

 

[LeonidasG_3CX]

Please upgrade to 201, it's fixed in the latest beta.

 

[net-products]

I got many issues with the app too, i will test today again at customers side with a higher version to see if the Beta is solving my issues.

All my issues are related to connectivity with version 170.
App dont ring when they receive calls
App dont ring when the phone is locked
App stop ringing after 15 minutes of being idle.

Will let you know the outcome today.

 

[LeonidasG_3CX]

Keep in mind that 208 was released as a beta moments ago. You can try it out if you like.
There's still a few more issue to be fixed until a final release.

 

[net-products]

Yep, got it installed.

My phone just dont want to connect the email attachment anymore with the 3CX app. Will let you know how it goes with 208.