Is using a phone's wide angle camera possible?

How do you do that though? I couldn’t find anything for this

From the main screen, press the gear, select Timer, scroll all the way down to 1, 2, 5m. Could be better with the option to specify a number. Or just 10 and 20 m. Also set Repeat to unlimited in the same settings menu.

It only shows 1/2/5 minutes for me… Is this just a translation error in my language’s localization files or did you mis-interpret the unit m?

i set repeat to unlimited and the timer to 1s which is roughly the same as what the mapillary app does. (repeat is another menu above the timer option)

you can also get to these settings quicker by tapping the 3 dots from the camera screen and scrolling down the menu that pops up

I’ve considered that too, but honestly I’m just too lazy to sort out the pictures taken while standing at traffic lights.

However, I’ve just successfully tested this with Tasker! I use my integrated camera app though, as I’ve recently got a Xiaomi Mi 9 and it doesn’t seem to give any other camera app access to the wide angle lense. It works with open camera too though, in case OC detects the wide angle camera on your device.

So what I did is the following (easier and with pictures explained at the bottom): First, I’ve created a profile thats if statement is the camera app. So the profile will become active when I open the camera. The first action of this profile is to start GPS search, while checking the options “immediately continue with task”, “continuous search” and “continue task after error”. Note that the options might be labeled differently, I’m using Tasker in my locale so the English option labels might be different. This profile was just for testing purposes but I’ll keep it in case my camera app fails to update GPS frequently enough. After this action I’ve added another one, that is plugin > AutoInput > UI query > app package: (for open camera use com.sourceforge.opencamera). That generates a variable with the app name, so @aiapp will be “Camera” or “Open Camera” or whatever camera app you’re using. After that I added task > if > %aiapp ~ camera, and below I added go-to action > action number 1 (= if the camera app is still open, repeat the profile, i.e. continue scanning for GPS) and else stop the task (=don’t scan for location anymore)

Then I added another profile that is variable > variable set > %CurLoc. I’ll explain in the next profile why I didn’t use the built-in %LOC here. The action of this profile is taking a picture. I accomplished that using AutoInput again. In my stock camera app this is Type=Id,, Action=click. So basically this means as soon as a new location is set (that isn’t the same as the last one, hence the %CurLoc instead of %LOC) to take a picture.

Next profile is setting up %CurLoc. The if statement of this profile is event > variable > variable set. So every time a location is reported (no matter if its the same one or a new one) this profile will trigger. Since I want this profile to update the %CurLoc variable as soon as a different location is reported, the action list is the following: First, set %CurLoc to %LOC (so %CurLoc will start with the current location). Now an If statement; if %CurLoc ~ %LOC, wait one second, then go-to action number 2. That means if %CurLoc is still the same as %LOC (= I haven’t moved since the last location update), do nothing, wait a second, go back to the if statement and check again if %CurLoc is still the same as %LOC. If it is, repeat the above forever until it isn’t. Now if it isn’t the same (else statement) it goes back to step one; setting the %CurLoc to %LOC, which will trigger the “%CurLoc variable has been set” profile, which will then trigger the camera shutter button.

What I did, but that’s completely optional for functionality, is set up another variable that is %MapillaryActive ~ true/false. I switch that variable manually and set it up as an additional if statement for all profiles; that allows me to easily switch all the profiles on or off from a home screen shortcut without going into Tasker and toggling them all three manually every time I want to take photos.

Now this probably sounds more complicated than it is, especially if you don’t have experience with Tasker. So here’s an imgur album with screenshots in case anyone wants to do it like this (I’ve changed Tasker to English for those):
I’ve added captions to the pictures to explain what the stuff is below the pictures, probably easier to understand than what I’ve wrote above.
The setup works fine!

Edit: I’m on the go at the moment but I’ll upload the tasks as xml files later so anyone can just import those if they wanna test it (you’ll then only have to edit device specific stuff like the shutter button name)

Edit: The xml files for import are, for profiles this, this and this and for tasks this and this.

I can see that I misunderstood the configurations. I read 1m, 2m 5m as meters while it actually means minutes.
If using the command line Python scripts from Mapillary , there is an option to remove duplicate images. I use that on images from action cameras and it works very well. But it would be better to not take those extra images.

I don’t have experience with the command line and python stuff, but I’ll try if I can do it. Thanks!

Back to the subject,
Can you share the EXIF information?
Is there enough info for Mapillary to get this right?
Have you tried to take a picture with and without the wide lens and uploaded it to see what happens?

Just a thought:
Maybe it’s possible to juggle around with there EXIF parameters:
ProjectionType=cylindrical / equirectangular

But I have no idea what the values would need to be to get this right…

Developers, any updates regarding wide-angle cameras support?

1 Like

We have support for it on iOS. We are currently working on implementing the new CameraX interface on Android and we have a phone with wide angle lens, so it’s in the works.


Any updates? It’s been 1 year now and no new feature. I bought this new S20 phone and here I come thinking the option is on android also.

Instead of giving ios the features first and throwing us android users under the bus, you should hold the feature development until both platforms are ready and have the same features.

1 Like

At this time the Android app seems like abandonware. Even bugs strongly affecting data quality are not fixed, there is no reaction, neither to forum post, nor to support emails.

Examples: Mapillary doesn't record compass direction, OpenCamera does - #10 by enteq
[bugreport] Some photos in a sequence get packed in the same place - #2 by Amiga4000
Problems with the android app - #2 by enteq

1 Like

If you’re not going to be paying attention to the people helping mapillary, then we unfortunately can’t help you have better coverage.

1 Like

Not being able to switch between camera modules is having a direct impact on the quality of the pictures that are uploaded to Mapillary in general.

The camera module that Mapillary selects by default is most of the times not the best lens that a phone has available. Please consider adding this functionality in Android. I am seeing that it is quite a long time it has been asked for, and I am pretty sure that it will be useful for everyone.


That a silly joke, no it’s sad to see that just being bought out by FB is making developers not care about it’s users. Shame. @Anders it’s been almost two years without ANY update…

Hey, I’ll forward this to the product owner.

We have wide-angle support on iOS, and it’s unfortunately not very useful, at least not when putting the phone inside a car as it captures a lot of the dash/ceiling and the car hood etc. For walking etc, it’s very useful though.


I personally have a 119° wide angle on my phone, and i record mainly by walking and cycling, if the Android app supported wide angle it would be awesome!

Then implement a digital zoom feature so we can adjust it while still having the wide angle.


if both cameras are used simultaneously, one could get 1. a wide angle photo, which could be cropped automatically at the top and bottom via Computer Vision, and 2. a normal photo, which contains much more details about the centre. You’d basically get something more close to human vision, with a fovea and some peripheral vision on the left and right.