ProfileManager: Native and Real profiles. Need an explanation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Hi.
Could someone please explain the purpose and difference between the Native and Real profiles in Google device registration ?
I've never used this feature, but I would like to correctly translate it into my native languages.
There are even more profiles in the code for the internal needs of the microG, so I'm even more confused now.
https://github.com/microg/GmsCore/blob/master/play-services-base/core/src/main/kotlin/org/microg/gms/profile/ProfileManager.kt
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 with play-services-base/core/src/main/kotlin/org/microg/gms/profile/ProfileManager.kt and trace the Native and Real profiles used during Google device registration. Document their purpose and differences, including the other profiles mentioned in the issue, so translators can distinguish user-facing behavior from internal microG profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100