You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Open GMSCore" doesn't support or open any of the forked GMSCore. It only support official from revanced. As we know that revanced GMSCore doesn't support hiding from launcher. Due to which many people like me use the rufusin GMSCore as he only added support for hide from launcher.
So, the option should open forked GMSCore(s) from ReX and rufusin too.
Error logs
No response
Solution
No response
Additional context
No response
Device Environment
No response
Acknowledgements
This issue does not reproduce on unpatched YouTube or YT Music.
This issue is not a duplicate of an existing bug report.
I have chosen an appropriate title.
All requested information has been provided properly.
I have written the title and contents in English.
The text was updated successfully, but these errors were encountered:
I tested it a while ago, and it doesn't seem to be an issue with RVX
While implementing the feature to remove icons from the launcher, it appears that a certain class org.microg.gms.ui.SettingsActivity has been removed
(Validated in rufusin/GmsCore, It seems that the fork does not reflect the latest GmsCore changes)
I built the GmsCore fork locally, which does not have the feature to remove the icon from the launcher, and it worked normally
Type
Other
Tools used
rvx-builder
Application
GMSCore forks
Bug description
"Open GMSCore" doesn't support or open any of the forked GMSCore. It only support official from revanced. As we know that revanced GMSCore doesn't support hiding from launcher. Due to which many people like me use the rufusin GMSCore as he only added support for hide from launcher.
So, the option should open forked GMSCore(s) from ReX and rufusin too.
Error logs
No response
Solution
No response
Additional context
No response
Device Environment
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: