With v20 release 5 or 6 older Android versions stop working

[Thiek]

After installing release 5 and 6 our 3CX sites are reporting the older version of the 3CX soft-phone client for Android they were running is no longer working. We have a large number of Android devices that running an older OS, and they cannot upgrade to a newer OS, which in turn means they cannot install a current v20 android soft phone client. But at least it was working and allowing them to make phone calls right up until update 5 or 6. Now the devices sit at "connecting", scanning a new QR code for the ext. does not help. Any suggestions or workarounds? Not in position to tell each site to purchase $30,000 in new devices.

 

[bitn2]

If they are that old that they cant use Android 8 its time for some new phones... Android 8 is released 2017 and the phones must be much older than that.

 

[Thiek]

Yes, I'm embarrassed to say how old BUT they were working fine for taking/making calls which is all we needed and after installing Update 6 they "broke". Actually, they still ring when called but can't answer it, call goes directly to v-mail and then shows up in call history. Odd. Of course they don't call out either, sits at "connecting".

Never know what is going to break after installing updates which is why I hate these updates that are mandatory with a deadline. Like in this case, it was mandatory, although I still question if it was needed as we use DigiCert as to 3cx certs.

This is a reminder that the current 3CX.COM certificate is set to expire in October 2025...

• If you're running version 20.0.5.551 or below, you must upgrade to Update 6 Final (20.0.6.724) before Friday, October 3, 2025.
• The new certificate is already embedded into Update 6 and once you’ve upgraded, no further action is needed

 

[SteveITS]

The certificate there is for the software to connect to 3CX and activate its license, update, and use other 3CX features. About once a year there is a required update for that reason.

re: phones, I just wrote a newsletter article on Technical Debt, and that unfortunately is one aspect. The developer ends up needing to choose between some improved function/new feature/new API, and maintaining compatibility with an old OS.

Android 8 EOL was close to 5 year ago. https://endoflife.date/android

 

[N_G]

Its not to do with the server version. Our Android App will stop working on these very old Android devices for many reasons. So you will have to buy new phones or use a product that has an app that supports very old phones.