MicroG services crashes every few minutes, when on the road with navigation, whether it’s a logbook. MagicEarth or CoMaps.
Android 13, iodé 4.28, S10e.
I’m having the same problem on iodé 4.28, S10e.
usually it crashes once or twice right after turning the phone on and than every once in a while
It hasn’t happened since today. I suspect MicroG could not reach an online service? Maybe Positon, BeacondB, or Nominatim? But I didn’t find anything about failures.
Actually, MicroG should catch such errors.
In addition, I cleared the cache from MicroG Services.
Let us know if it is still happening.
For me, it took a day longer to stop than for @volker01, but now its fine
I’m about to update to 4.29, lets hope it doesn’t come back
1 Like
I have a person asking for help over email with the same problem: under 4.29 they are facing continual microG crashes. So are @Privateer and @volker01 still facing issues or is all well for the two of you?
No, this problem no longer occurs.
What I did: cleared the cache partition (Samsung S10e). And in microG under location all switches once flipped.
(This also happened to a friend of mine and now no longer.)
I can’t say whether my activities solved it or whether it was a coincidence.
1 Like
Thanks for the update. I am directing another user (S10) to this thread.
Can you clarify how you did this? I see here that it may not be that easy / relevant?
Today a friend called me, the problem is back, when he is on the road with navigation (even the Cache partition was cleaned before). But for me it is not!
Looks like some MicroG Services not reachable, then the MicroG crashes?
1 Like
So you aren’t experiencing the issue again yourself, but it is on for the friend that called you (and they also have a 4.x device and did clear the cache from recovery)? Just trying to clarify if I understand correctly.
I may advise a user I am in email contact with to clear their cache from recovery, it can’t hurt and may possibly help (even if only temporarily), right? (well if they accidentally fully do a factory reset that could hurt quite badly 
)
Yes, correct.
Yes, normally I don’t recommended that to Non-Experience User. In my case I had a call with him … better to instruct him …
If the problem occurs, then of course it’s totally annoying, especially if you’re dependent on navigation.
Maybe it’s helpful if we compare our MicroG Settings?
2 Likes
between you and him or you and me?
Maybe between the users where it doesn’t work and where it works, for example to see where the differences lie.
Or are microg errors logged? Is there a log somewhere? 
1 Like
for me, the issue has come back too
For me, microG stops working always right after turning the phone on and infrequently during the day
I’ve just now cleared catch from recovery and turned the phone off and back on a couple times - so far no more errors! thanks @volker01 for the tip!
The user I am helping on email is having trouble getting Recovery to launch, I think they are not very technical so any specifics on that would be helpful.
They also report the crashes occur when using these apps: WAZE , IDF Mobilité , Fuel Flash. As they all request location, I did have them check they have Position.xyz as the location provider and that all microG location settings are enabled.
Can anyone that experiences the crashes comment on if they are opening an app that is requesting location when the crash occurs?
A new version of microG has been deployed through our f-droid repository. Please report back on this issue after updating it.
2 Likes
thanks!
I was about to report back that clearing cache didn’t last long and I’ve gotten crashes again
I’ve just updated microG - so far no crashes 
I’ll keep an eye on in and report back in a couple days
After a couple days I can report that I haven’t had any more crashes, so the update seems to work, thanks @vince31fr !
2 Likes