I only get cell poll timeout in recents tabs, and in Llamalog.txt, when it should do something, I’m getting a
I have the impression the medthod should be there…
I just tried Tasker. Does not work also… There’s also a comment on play store, that Tasker on FP2 does not work.
So, I guess there’s a problem with Fairphones OS that does not allow location based automation tools to work…
That’s interesting, Tasker works for me 
I use two profiles defining “work” and “home” by using Google Maps coordinates + radius. The system setting for “location” is set to “energy saving” meaning it does not use GPS. This works for me - which leads to the conclusion that location based stuff generally works on the FP2 but it does not correctly communicate with the Llama-App.
I didn’t use taker before, so I can’t get over the start screen with its explanation. Location works, e.g. for navigation, yes
Maybe only the location detected by the cell towers doesn’t work. The location detected by the phones location-service based on A-GPS/Wi-Fi-database is working fine because it’s used by all the apps with location based functions?!
1 Like
You’re right, I forgot about this one… And indeed, Tasker does start…
Thanks for the reminder!
Location detection works fine in energy saving mode. At least with Google maps, camera, here maps, … 
hooray, I think I found it 
I digged a little bit around in my Llama settings. I found “Android Postitionsbestimmung” under “Versuchslabor” and activated it - it seems to work. At least Llama instantly finds new cells and updates its area information. Let’s see if this solves the problem. If so I guess the Llama location service uses a depricated API.
I don’t know the english terms for these menu items, most probably “Experimental” and “Use Android location service”? Here are some screenshots to make thins clear:
1 Like
Can you add the position to a region? I only get a white screen
Edit: I see, there’s a plugin necessary. Now I can select the location, but it doesn’t save it…
Judging from your previous description of how Llama is supposed to work and the description of this setting, I’d say that there are still no cell towers found.
Do I understand correctly? The normal way for Llama to get a position is by circumventing the built in (to Android) position service (offered by Google) and decide whether you are in your home region by comparing IDs of cell towers in range.
The “experimental” positioning is different: It clearly says that it now does use the position service built in to Android. That means it doesn’t look for cell tower IDs anymore but relies on the position given by Google (based on stuff like WiFi networks, cell towers, GPS, … whatever is available to Android).
Your solution solves the problem from a usage perspective but does not seem to fix the underlying problem that Llama is not able to see cell tower IDs on your phone.
Yes, this is a work around. Llama can’t get information from cell towers. If you activate debug, you’ll see “cell poll proximity timeout”. Every five minutes or so
Indeed, I was too optimistic. Llama just detected a different cell ID then before but still it does not find the right IDs. The IDs provided by Llama can not be found in the openCellID-database - so obviously something’s messed up here. Still trying to find out if this is a general Android issue or a FP2 issue.
Regarding the “Android location service” under Llama:
Thanks to lklaus I found the plugin needed and it worked for me as soon as I deleted all cell IDs for my areas and chose two points for “work” and two points for “home”. “It worked for me” in this case means that the location was saved and it shows up under the area tab saying “two points defined on map”.
Let’s see if I’m still happy tomorrow
Yes, that’s it. From kebabapps
I saw your response while trying to find the solution to cell id issues. Would the workaround you mentioned not consume more battery, since it’s location and not cell ID based? I had a Nexus 5X and the Cell ID detection was working on that. Not been able to figure out how to fix this on Moto G with Lollipop.
With the recent updates it should be a non issue. In fact, I’m using Tasker with cell ids for a long time now
Sorry for gravedigging into an old topic, but which update are you referring to? My Fairphone 2 should have the latest updates (I bought it at the start of this year), I’m running FP Open 16.12.0 and I still have the same problem described in this topic…
This was long before 16.12. Did you already try some app and fail? Or it out just a question for being prepared?