16.3.0.21 (beta) Feedback

[nobody]

A good thing: At last I can now answer a call with the touch of a button on the screen, no fscking gestures which do not work immediately. Please keep this. Congratulations for this insight.
After installing the Version my settings were reverted to defaults (telecom api, Echo cancellation etc.) ok for a beta, but maybe not good if happening if released
My Sony XZ1 compact works fine with the telecom api (latest available android 9 from Sony) if the Microfone amplification is set to 8.
Whats is working not good (but this was the same in the previous releases) is the echo cancellation:
The call quality is ok if the hands-free speaker option is used plus echo cancellation. Also echo cancellation improves call quality - I checked that with several calls.
But If using the normal phone earpiece, call quality is worse when echo cancellation is enabled, fractions of the beginnings of a word are cut off. I also tried that out with several people. All voted against echo cancellation when not using the speaker.
So I would suggest to implement a switch where the echo cancellation can be switched on or off separately for earpiece or hands-free operation.

 

[nobody]

Followup: for an unknown reason the unloved "swipe to answer call" comes up again. When and why does the standard "push the button" method is used and when the (not working in most cases) gesture?

 

[nb]

I will help you - but what is your phone and what is your os?
Restart the phone and tell me if the issue persists.

There is some new permission found in some phones only - Allow user to interact withF***ing locked screen. I don't understand why some phones have it and most don't. Can you please confirm and put me a screenshot here with the permissions page in your Android. Because this to me is another Android development mystery.

And I am not buying anymore Sony's and Nokia's. I reported them to Google Android. I'm not going to buy these phones. They are a glorified mess.

Also mic gain should not be 8. The higher the gain the dirtier the tone. Which means that for you to set a gain of 8, then there is something very wrong in the gain vs master volume transmission.

Now About echo cancellation - you need to make sure you do not have double echo can.
Or triple - be careful.
So you have one hardware in android, one in 3CX APP (software based) and then you might have another one in the headset. No wonder they are either all cancelling each other out or all working against each other.

Switch 3CX ec off. get rid of that.

Too many issues on this phone brother. I don't like how this looks.

 

[nobody]

nb,
This is an Xperia Compact ZX1: 47.A.11.228 (android 9)
The permissions page looks very normal.
The extended permissions include "disable screen lock". There is no interact with locked screen permission.

I tried out:
phone on home screen, unlocked, no app running: able to push the answer/reject box
phone locked, screen off: the unloved "slide to maybe answer the call" comes up.
phone unlocked browser in foreground, able to push the answer/reject box
3cx app in forground, able to push the answer/reject box.
Even in the 3cx app the push button method is used, why does the slide to answer even exist? But I am no android developer.
Its not that the slide to answer is not working, it is not working good, its complicated. Please try yourself the slide to answer method using one hand.

Making Calls with Mic gain set to 4 is possible, but everyone when asked will tell me with 8 it is better. Disabling the Car BT/support will change the need for MicGain 8 to two (btw.: all yealink handsets are set to a level a little to silent!). I did not find the quality distorted with set to 8, but yes its strange that it has to be set to maximum.

Echo cancellation:
I dont use a headset, I either use the standard earpiece or handsfree speaker.
But I dont know if the Android system itselfs does echo cancellation. Still the call qualitity is better with 3cx echo cancellation on if using handsfree speaker. But much better with cancellation off when using the earpiece. If there is no setting to set this separately I can live with set to off.

 

[nb]

Thank you very much for your detailed feedback. I appreciate.
But still - we have too many issues with this phone. Can you try another android like a cheap Samsung? Can you try from an android of a friend.

Send me logs at [email protected] and put your name and forum link and I will see what I Can dig. I am promising nothing. But given your activity on the forums, I feel inclined to assist you. Set verbose, replicate 1 issue only (of your choice) and send me logs. Do not keep verbose active.

 

[nobody]

Thanks.
I have a spare Note8. I try that for the next days with this version and let you know if this behaves different.
Also, the Sony Xperia plus 3cx overall is working good (with the exeptions already told), but its still not like a real GSM phone or a DECT.

 

[nb]

Perfect - try it out and get back to us. and write the settings that work also.
Sony Xperia - Did they fix that keyboard bug on the edges? Still not working on our xperia. Anyway let us know what you find.

 

[nobody]

What kind of bug is this? how can I test if my phone also has it?
(I do not have problems with the xperia and the keyboard, however I use the Blackberry build theme including the blackberry keyboard)

 

[nb]

What kind of bug is this? how can I test if my phone also has it?
(I do not have problems with the xperia and the keyboard, however I use the Blackberry build theme including the blackberry keyboard)

I just type on my test phone. I notice with all sony phones that the keys on the EDGE of the device frame are very very sensitive to inaccuracy.
So the q, a, on the left and the o,p, and l on the right. Maybe my phone is faulty? But then how is it on all sony's I ever touched? This is nothing to do with 3CX. This is purely using the inbuilt messaging system of Sony Xperia.
Testing right now on Sony Xperia G3121 Android 8

 

[nobody]

Samsung Note8 Android9: No audio when using Telecom API.
Works with mic gain 2 (but sony does that also when Telekom API is off, 8 only has to be used then telecom api on)
Behaviour of slide to answer is the same as with sony (slide to answer is used when a call comes in and the phone is locked).
I still have to make a survey regarding echo cancellation.

 

[nobody]

Echo cancellation with note8:
Works good, Call Quality is fine, even ich echo cancellation is on when useing the earpice. But since note8 does not work with the "telekom api", the result cannot be compared to the sony.
I prefer the Telekom API variant since the bluetooth integration is much better.
Will client also support the note8 or other Samsung, or should this already work?

 

[nobody]

When i look at the call history in the andoid app, all incoming calls are displayed together with the name of the caller.
However, When I call someone back from the recent list, and later look into this list only the number is displayed.
The same happens when I dial a contact using the 3cx contacts.
I do not have email/contacts using the native android applications, I only use the 3cx contact list. Seems like the outgoing calls are not checked against the 3cx contacts.
Obviously, It would be better if after a call ends, the number would be checked against the 3cx contacts.

 

[nobody]

I experience random one way audio on outgoing calls since this version (I cannot hear the other party) on the Sony. with the previous version it work near to perfect regarding similar problems.
I cannot dial numbers starting with a "+NN" from the 3cx app. I guess, this problem is present in all versions, I found no option to replace "+" with "00", but fixing this would be a good thing.

 

[nobody]

I have logged myself out of the beta-program.
Now back to version 16.2.0.93. The Problem with one way audio is gone immediately.
Of course this could be also random problem by something else, but I think not. I will try now for a week again with the non beta version, then try again the beta.

 

[Vali_3CX]

I cannot dial numbers starting with a "+NN" from the 3cx app.

Why you cannot? What error do you get? I'm not involved in Android client, but you're already an experienced user, and you should know that the +/00 handling is solved - and highly recommended to be solved - at PBX level.

 

[nobody]

If you mean If have have dial out rules which convert from +NN to 00NN, yes, I have these - and normally it does work, and now back to the non beta version I am again able to call numbers starting with +NN.

 

[nobody]

Strange, I tried to reproduce the problem, by again installing the beta, restarting phone, dialing number. Works now with the beta too. So either this is a radom problem or it was some problem unrelated in the pbx or provider. Next time I will try to create a logile.