Latest Beta harnesses Android 14 new car phone features and gets ready for V20.
Android 14, the latest version of Google's mobile operating system arrived on October 4. Hot on the heels of this was the fully compliant Beta release of the 3CX app for Android. Beta 2 - in preparation for the final release - includes fine tuning, additional testing and fixes. Read on for more details.
Support added for new Android 14 operating system
Beta 2 has been refined to ensure compatibility with Android’s latest operating system. Users can now expect a smoother and more responsive experience while using the 3CX Android app.
Support for Telecom API
The added support for Android 14 has also provided improvements to the support for Telecom API. This focus on reliability means users can expect a more seamless communication experience.
Ringtone replaced with subtle warning beep
In previous versions, whenever users received an incoming call while already on a call, they’d be notified with a ringtone. In this Beta, we’ve replaced the ringtone with a more subtle warning beep.
40% faster connection with JWT
JSON Web Tokens (JWT) have become the de facto standard for secure connections. V20 now enforces JWT. This new Android client has integrated support for it.
One of the nice side effects - connection time is now 40% faster!
- Current Android client connecting to a PBX V18 - 450ms
- Beta Android client connecting to a PBX V20 - 300ms
Google support on known Android issues
Good news! We’re happy to say Google has acknowledged it’s looking into a couple of Android issues we’d reported as requiring their attention. We appreciate all new releases are a work in progress so for now here’s a recap of known issues and how you can work around them.
Failing to switch to Bluetooth after moving from the BT device to another audio route.
Scenario: User answers a call via car bluetooth and switches to earpiece to have a more private conversation. If the user decides to switch back to Bluetooth, errors are thrown in the background by Android.
Solution: To solve this you first need to switch to an intermediary audio route - speaker for example - then move back to bluetooth.
Status: This issue was reported to Google. We’ve received confirmation that the bug is fixed and will be released in a future Android build: https://issuetracker.google.com/issues/302436283
Incoming audio from calls not being routed to bluetooth device
Scenario: When answering via a bluetooth device it may be that the incoming audio from the call is not being routed to the bluetooth device. We’ve checked our internals - which tell us we’re correctly routing audio to Bluetooth - but instead it’s routed to the earpiece, or no audio at all. In Android logs, it can be seen clearly that our app receives misleading information from the OS itself.
Solution: We suggest restarting your Android 14 device when connecting to a BT device. Although the issue might resurface at a later stage it will minimize the occurrence of the problem.
Status: We’ve opened an issue to Google and are waiting for their response: https://issuetracker.google.com/issues/310998067
Watch this space for more updates!
Try the Android Beta
Join our Beta testing program and try out the latest Android Beta update! Download the app from the Google Play Store.
View the complete changelog history.
