Known limits

Huginn reads what your iPhone noticed, and your iPhone doesn’t notice everything. These are the gaps I know about, and how to fill them.

Short stops go missing

iOS drops stops of a few minutes, or folds them into the stay before. Huginn finds most of them from how you moved; for the rest, add the stop, or check in while you’re there.

Train or car

Your phone’s motion sensors report both as “in a vehicle”. Correct the trip once with How you travelled, and the same route reads right the next time.

Underground

On the U-Bahn or the Tube, your phone often loses its position and its motion reads as standing still, so a ride can show as a long stay at the first station. Correct it by hand for now. Recognising rides underground on its own is planned for 1.0.

Nothing before you installed it

Huginn starts the day you install it. Your iPhone’s motion history goes back about a week, but without places it can’t make a day, so Huginn doesn’t try.

A stop with no place

A stop Huginn found from motion alone has a time but no position. It gets one when iOS reports it, or you can name it yourself.

Suggested names are guesses

In a busy street, the business Apple names may be the one next door. That’s why suggestions show in lighter type until you name the place.

Always access

Without Always, Huginn can’t notice where you arrive. See Getting started.

Still stuck

Write to hello@mymuninn.app. I read every email myself.