Android 6.5.33 is out

Mobile apps Android
1

Full version name is 2024.11.21-6.5.33.

Intro

Hi there.
In this release we did some large improvements on the performance of the app when having a large amount of images captured. As this improvements influence the way we store images, after the update we’ll migrate your existing non uploaded captures to the new architecture.
Additionally we increased the capture limit from 300 to 1000 and made some additional improvements and bugfixes.

Changes

  • improved performance of the app when containing large number of images
  • increased capture limit from 300 to 1000
  • reduced the size of dots on the map for better UI clarity
  • added dark/light theme selection in the settings
  • removing failed sequences from the profile after 14 days
  • when zoom out and clicking locate me button, now it will zoom in to the default zoom level
  • updated number formatting to remove trailing zeros after the decimal

Bugfixes:

  • moved the position tracker on the map above selected path to prevent overlapping
  • fixed sharing of images on devices bellow Android 10
  • fixed wrong display of upload size when re uploading
  • fixed padding on cards for large screen devices
  • fixed a crash at app startup
  • moved snackbar above edit toolbar

If you have any questions, or suggestions - please report them here.

cc: @Yaro @boris
–
Best Regards,
Josip

2 Likes
2

O this interests me -.

So why was something like this added? Maybe some more info about it
Is it in the browser as well or does it only apply to android apps?

3

Hi @czecko, it was already implemented on the web browser and iOS. This is just a follow up from the Android side to sync with the other platforms. This applies only to the captures that have failed in processing after upload. This doesn’t impact your local on device captures that failed during upload.

4

That’s great, but either Mapillary Desktop Uploader, or the backend processing is still capping that to 500, so what’s the point?

5

@IreuN, Desktop Uploader and CLI tools have the limit of 500 images. They will increase this limit, but separately from an Android application.

At the same time Mapillary Android app has increased the limit to 1000 already now.

–
BR, Yaro

6

I prefer short sequences. If something is wrong, I am more inclined to delete the whole sequence. Deleting image by image is too much work.

1 Like
7

Longer sequences have its benefits starting from UI at the back end, which can display now longer sequences of images which are connected to a single capture session to those are usually cleaner in the feed. I would think we can address other problems without limiting the sequnce size. I have a few quetsions though:

  1. How often do you delete the entire sequnce?
  2. What’s the usual reason for this?

–
BR, Yaro

8

In the glory days of Mapillary, it was possible to split sequences.

9

Programmers are not able to combine sequences into a whole?
( it’s about merging already after uploading on the server)

Sometimes I do not have time to send everything at once. Therefore, I divide the sequences into smaller ones. Sometimes it takes me a week to send the whole of one route.
I will send myself 2000 photos in 10 sequences (200 photos each), for example, from today, and time will indicate that they are taken after each other and the location will indicate this, to this exif data. Don’t you embrace this?

You might as well add options for manual merging sequences, indicating which sequences are continuity. Well, but the panel in mapillary is so clumsy that even something like that is impossible.

And there is also a reason why I prefer to send small sequences - and that is that they sometimes get “Failed” when processing. It’s easier and faster for me to send 200 photos again than 1000.

2 Likes