-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProfileManager: Native and Real profiles. Need an explanation #2360
Comments
Native is to register a device of the same type with same software version as the actual device, but randomized hardware id, real is the same with real hardware id |
@mar-v-in thanks for your answer. Since an extended explanation in this strings is not possible ,is it worth changing the default strings to something like this? Your device (Randomized H/W ID) GmsCore/play-services-core/src/main/res/values/strings.xml Lines 215 to 216 in 720823e
|
To keep current names (but explaining them) I propose this:
|
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
The text was updated successfully, but these errors were encountered: