[Fused Location] microG current only implemented 1/4 methods to getCurrentLocation/getLastLocation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
As far as I can tell, microg does not support the recommended way to get the current location getCurrentLocation.
And only implement 1/4 ways.
And getLocationAvailability also is not implemented.
Originally posted by @Cod3dDOT in https://github.com/breezy-weather/breezy-weather/issues/901#issuecomment-2046310614
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in play-services-location/src/main/java/org/microg/gms/location/FusedLocationProviderClientImpl.java, especially the linked method ranges. Compare the implemented getLastLocation overloads and the missing getCurrentLocation and getLocationAvailability behavior with the linked Google Play Services API documentation. Done means the reported location methods and availability check are implemented compatibly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- api, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100