Android Open Testing: Android 16 (6.14.2)

Included in this version:

  • Updated target Android version to 16
  • Fixed bug where the location permission was being asked erroneously on map explore screen
  • Fixed bug where automatic uploads would not resume when a WiFi connection was restored

Google require us to bump the target Android version to 16 before Aug 31. Please let us know if you find any issues regarding uploading and UI/UX as those areas are the most affected.

Thanks in advance for testing new builds before they go live for everyone!

2 Likes

Does this mean that the Mapillary app will no longer work on older versions of Android?

Old versions will still work, but we will not be able to submit new updates for older Android versions after August 31.

1 Like

Perhaps I’m misreading the Google page. What I’m reading is that your app must support at least Android 16. If the app doesn’t support that, it won’t be available to users with Android 16. The app may still support earlier versions of Android.

2 Likes

Hello @Anders

With this version, uploading still doesn’t seem to be working properly. I’ve had to restart the upload several times and regularly received the message ‘waiting for Wi-Fi’, even though I was connected to my home Wi-Fi.

BR Louis.

Thanks for the feedback! If I interpret your message correctly, you had uploading issues before this beta version?

Yes, that’s exactly right.

This beta hasn’t solved the problem in my case.

The only improvement is that I can restart the upload. In the previous version, I had to download the interrupted sequences to my PC and upload them using the desktop uploader.

1 Like

Oh wow, that sounds terrible, but at least it didn’t get worse with this update. I’ll look into it, thanks for reporting!

1 Like

Right, Google’s app review process and AOSP license for large scale licensees are broken, not the user’s phones or the users themselves. Besides, it is not like nobody could have known or imaged for how long phones can be used and that

  • they have tons of cryptographic code that may have vulnerabilities
  • the OS can have bugs and vulnerabilities too
  • they continue to be used long after production has ended.

However, not only Google is to blame but also regulators too for being passive about requiring vendors to provide at least security updates long after software enabled devices have become EOL. While phones might sound quite trivial, just think about cars, trains, construction equipment, or power plants etc. Apparently, it is gonna have to take disasters for regulators to finally take notice and action. Sadly, this situation is pathologically unbearable.

Anyway, thank you @Anders for further Mapillary app updates. :+1:

3 Likes

Hey @Lowiekse, I just published a new version which hopefully solves the upload problems for you, see Android: Maps 2.0 and upload bug fixes (6.14.13 is out)

1 Like

Thank you @anders , but unfortunately the update is an hour to late. :sweat_smile: :+1:

I’d just had the same problems again and had to download the files to my computer first.

I’ll be making some new recordings tomorrow and will let you know if the issue has been resolved.

1 Like

Hello @Anders

As things stand, the update seems to be working. I deliberately disrupted the Wi-Fi to trigger it. It takes a long time for the upload to restart, but eventually it does and uploads all the recordings.

BR Louis.

2 Likes

Great! Yeah it can take up to 30s for the operating system to detect/forward that the WiFi connection has been restored, but hopefulle you don’t have to worry about having to restart uploads manually.

1 Like

It took longer than 30 seconds, but that doesn’t matter as long as the system picks up where it left off.

1 Like