Hi again,
It's not about the certificates, it's the protocols themselves.
On Android 4.4 or less, only SSL and TLSv1 security protocols were available by default (
https://developer.android.com/reference/javax/net/ssl/SSLEngine#protocols).
But now, more and more websites only accept TLSv2 and/or TLSv3.
If you have some tech knowledge, there are a few things you can try (it may help but there is no guarantee). In the app, go in the installed maps list, click on "Add more maps" and select "OSM maps". It will add a config file of the OSM maps on your device that will be used instead of the built-in config file. This way you can edit the file (
here is some doc).
- First, try to replace all "https://" occurrences by "http://" in order no to use any secured connection. Some servers may accept this, some not (they will redirect requests to the https version and not give you the map).
- Add the
insecure="true" attribute to none working maps. Replace:
Code: Select all
<zoom-levels z="3,5,7,8,9,10,11,12,13,14,15,16,17">
<server><![CDATA[https://a.tile.openstreetmap.org/{$z}/{$x}/{$y}.png]]></server>
</zoom-levels>
by
Code: Select all
<zoom-levels z="3,5,7,8,9,10,11,12,13,14,15,16,17" insecure="true">
<server><![CDATA[https://a.tile.openstreetmap.org/{$z}/{$x}/{$y}.png]]></server>
</zoom-levels>
It will disable all certificate checks, and try to add all available protocols (including the ones not activated by default because it was too early at that time, depending on your device/system/rom you may have TLSv2 support).