The network location has stopped working.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
**Describe the bug**
The network location has stopped working.
**To Reproduce**
The NLP TEST application is used for testing.
**System**
Android Version: [15]
ROM: [Samsung]
**microG**
microG Core version: [0.3.13.250932]
microG Self-Check results: [All ticked]
**Additional context**
I must say right away that I have partially identified where the problem lies. This problem has already occurred on two other devices, and now on my Samsung SM-A356E. First, I installed MicroG on my new phone using the Magisk MicroGPlus module, and this problem appeared after a few days, then I integrated MicroG directly into the firmware, and everything worked well for about a month, and today the location stopped being determined again. Clearing the cache and rebooting does not work, however, if you reset all the MicroG data, the location is detected normally again, but resetting is not the best option, since then you would have to reconnect all applications to cloud messages. Using the "poke" method, I determined that if I delete the geocache.db file in the databases folder and restart MicroG, then the location is determined again.
I copied the wrong geocache.db before deletion. If I return it to the databases folder with a replacement, the location will not be determined again. I have attached this file for your consideration.
[geocache-bag.zip](https://github.com/user-attachments/files/27103095/geocache-bag.zip)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with the NLP TEST application on Android 15 and examining the attached geocache.db. Compare behavior before and after deleting geocache.db; done means network location works again without clearing all microG data or reconnecting applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100