Android: Mapillary 6.9 open testing

Hey, I just submitted version 2025.06.11-6.9.44 to Google for open testing, so hopefully it will be available shortly.

How to join Open Testing
Download the app here

What’s included in this release

NEW

  • The current capture is now shown on camera map while capturing
  • You can now quickly access and adjust camera settings directly on the camera screen

IMPROVED

  • Reduced profile feed loading time by up to 60%
  • Implemented measures to prevent overheating issues during capture

FIXED

  • Fixed top crashes
  • Fixed bug where the Samsung One UI 7 screen could be corrupt after closing the camera

Please help us test capture as that involves most of the changes. We are especially interested if you notice increased battery consumption!

Thanks in advance,
Anders

5 Likes

Just recieved :melting_face: :melting_face:

2 Likes

This time I’m more worried then usual :slight_smile:

Many relatively heavy changes on the Camera screen.


BR, Yaro

2 Likes

I had a developer mode that was no longer available an hour later.

BR Louis

Am I correct that you were seeing a Dev options in settings ? Those are really ment for testing only, and shouldn’t be visible at an point.

cc @Anders


Br, Yaro

I really had them for the duration of 1 hour

1 Like

Thank you. That’s important thing as some features for testing can break the app. Not sure why did that happen :thinking:


Br, Yaro

1 Like

I recorded three sequences today. I didn’t notice any difference compared to the previous version of the app.

BR, Louis

2 Likes

I guess that’s a good sign. One of the changes is that during capture, your images will appear on the map (in red color). When you have many sequences, it can increase CPU consumption and overheat the device. It should not happen during most captures, but might if your phone is in direct sunlight, for example. Since Android has a diverse range of devices, this issue may impact some types of devices more than others. This is one of the things to check with this Open Testing build.


BR, Yaro

1 Like

Thanks for fixing One UI 7! Works fine for me! Not very critical, but I would prefer buttons to be visible straight, currently there is sliding animation that’s a bit frustrating, but it’s my personal opinion :slight_smile:

2 Likes

Thanks @Lowiekse and @ursus for the feedback!

Hide map while capturing setting doesn’t work anymore.

Thanks for catching that! The setting actually works as expected, it’s just that we forgot to rename it. It should be “Hide live map while capturing”. I’ll fix!

2 Likes

World it be possible to add a “Show 360° panoramas only” filter button ?
(I frequently capture using a 360 camera, unfortunately the app cannot be used to understand where 360 photos are missing and my effort are best focused…)

1 Like

Where is camera direction setup for vehicle now (forward, backward, left, right)?

As I remember this in the roadmap, but I don’t think there is an eta available at the moment.


BR, Yaro

We don’t have that anymore, right. The server has to detect the capture direction, plus phone should provide a normal azimuth mostly, but it doesn’t work all the time, right (in the car especially).

Am, I correct that you’re capturing to the side and have incorrect compass angles detected ?

cc @boris


BR, Yaro

Thank you, I have planned to use backward position but absence of settings have stopped me. Now I will try it.

1 Like

Yes @brunofilmklov - we’d like to add the 360 filter to mobile in the future. For now you can use the mapillary web application, which also works pretty well on mobile to filter for 360 only.

I would love to filter 360 to only show 360 images or filter it out.
on the web app you can filter to only see 360 but neither have the ability to filter out 360.

I take 360 pics now, thanks to the Mapillary 2.0 Grant :smiley:
So being able to filter to see what kinda data is missing is essential.
even tho now i have 360 capability i still take non-360 pics/videos because RealityCapture doesn’t support 360 imagery so i try to make sure i was still uploading data usable for photogrammetry.

another thing i’d like if we could flag images/sequences as bad gps tracks and have them filtered out of view by default (the track not the data it adds to the point cloud) i have deleted tracks because of bad gps tracks that were probably usable so im sure others have done the same for the sake of how the tracks appear on the map while in reailty we were getting rid of data that now might be lost to the sands of time.