Introducing GMS Flags 2.0: Now Available for Public Beta Testing

Introducing GMS Flags 2.0 - Public Beta v1

Two months ago, the decision was made to archive the original GMS Flags project. Initially, the team did not anticipate the emergence of a version 2.0, but an innovative idea struck unexpectedly, paving the way for a complete overhaul. With great enthusiasm, we are proud to announce that GMS Flags is back, entirely rebuilt from the ground up.

This new iteration boasts a fresh design and employs a different strategic approach under the hood, ensuring it is faster, more stable, and far more reliable than its predecessor.

How GMS Flags 2.0 Works

GMS Flags 2.0 operates as an LSPosed module, diverging from traditional methods by interacting with each application independently. Instead of modifying Google Mobile Services (GMS) or Phenotype, it alters flag values within apps at runtime. This innovative method effectively addresses previous challenges:

• Flags no longer reset every 24 hours.
• The latest GMS restrictions have no impact on performance.
• Long-standing issues with Google Wallet, wallpapers, and others are now resolved.

Understanding the Tradeoff

While this per-app approach provides increased flexibility, it also comes with a limitation. Users are currently unable to modify every package as before. Instead, GMS Flags 2.0 works with a predefined list of applications, which we plan to expand over time.

Server-Driven Architecture

In addition, GMS Flags 2.0 is closely integrated with our server infrastructure. This connection allows for real-time updates across various aspects including:

• Recommendations
• Flag lists
• Micro-hooks

These features can be refreshed without necessitating a complete app redeployment, significantly improving the user experience.

Reversible Modifications

One of the standout features of GMS Flags 2.0 is the reversibility of changes. Any adjustments made—whether they are flag modifications or recommendations—can be reverted at any time. Users retain complete control over their settings, ensuring that nothing is permanent.

Beyond Basic Flag Adjustments

Recognizing that certain features require more than simple flag changes, GMS Flags also incorporates micro-hooks. These are small runtime patches specifically crafted for individual apps, which are only activated if GMS Flags is used in its official, unaltered form. This is a self-imposed safeguard aimed at maintaining the integrity of the application, separate from Google's Play Integrity requirements. Modified or repackaged versions will not be eligible for these micro-hooks.

Enhanced Analytics for User Insight

We have invested significant effort in developing analytics capabilities that help us better understand user needs and preferences. This information is critical in guiding our focus toward features that matter most to our community.

The current version includes 14 unique recommendations, with plans for further additions in the pipeline.

System Requirements

To utilize GMS Flags 2.0, the following requirements must be met:

• Root access
• LSPosed framework

Beta Testing and User Feedback

It is important to note that this marks the first public beta of GMS Flags 2.0. Users should be prepared for potential instability; some flags may not function on every version of the app, and certain features may not yet be fully refined. We welcome bug reports as they are invaluable for improvement, and we encourage your feedback and suggestions as we move forward.

As we embark on this journey with GMS Flags 2.0, we remain cautiously optimistic about its longevity in the face of potential challenges.

Conclusion

In summary, GMS Flags 2.0 represents a significant step forward in app modification technology, offering users enhanced performance, flexibility, and control. As the development team continues to innovate and respond to user needs, we look forward to building a robust tool that not only meets but exceeds expectations.

Summary Table

Feature	Description
Architecture	LSPosed module that modifies apps individually.
Flag Resetting	No longer resets every 24 hours.
Compatibility	Works with a predefined list of apps, expandability planned.
Reversibility	All changes can be undone at any time.
Micro-Hooks	Runtime patches tailored per app, requiring unaltered builds.
Analytics	Enhanced insights into user preferences for focus on relevant features.
Recommendations	Currently includes 14, with more planned.
Requirements	Root and LSPosed are necessary for operation.

For those interested in exploring GMS Flags 2.0, we invite you to participate in this first public beta phase and look forward to your valuable contributions.

GMS Flags 2.0 - Public Beta v1 Two months ago I archived GMS Flags. Honestly none of us really expected a 2.0 to happen - the idea just hit out of nowhere one day, we gave it a shot, and here we are GMS Flags is back, rebuilt from scratch with a new design and a completely different approach under the hood. It's faster, more stable and far more reliable than the original How it works GMS Flags 2.0 is an LSPosed module. Instead of touching GMS or Phenotype, it hooks each app individually and changes flag values inside the app at runtime, no matter what's stored in GMS or Phenotype. That fixes the old pain points: • flags no longer reset every 24 hours • the new GMS restrictions don't affect it • old issues with Google Wallet, wallpapers etc are gone One tradeoff Because of this per-app approach, you can't tweak literally every package like before. For now it works with a predefined list of apps, and we'll keep expanding it over time Server-driven The app is tightly integrated with our own server, so a lot of things (recommendations, flag lists, micro-hooks and more) can be updated on the fly without shipping a new build Everything is reversible Nothing is permanent, any flag or recommendation can be turned off and all overrides can be cleared at any time Beyond flags Some features need more than a flag, so the app also supports micro-hooks, small runtime patches curated per app. These are signed by us and only run if GMS Flags is the untouched official build (our own safeguard, nothing to do with Google's Play Integrity). Modified or repackaged copies won't apply them We've also put a lot of work into analytics, which helps us understand priorities and see what people are actually interested in, so we can focus on what matters most The collection currently has 14 recommendations, with more on the way Requirements: root + LSPosed Heads up: this is the very first public beta, so things will break, some flags may not apply on every app version and a few features are still rough. That's expected, bug reports genuinely help and are very welcome. We'd love to hear your feedback and suggestions And well, let's see how long GMS Flags 2.0 lasts before Google decides to kill this one too :) DOWNLOAD: @gmsflags2_releases GMS Flags 2.0 - Public Beta v1 Two months ago I archived GMS Flags. Honestly none of us really expected a 2.0 to happen - the idea just hit out of nowhere one day, we gave it a shot, and here we are GMS Flags is back, rebuilt from scratch with a new design and a completely different approach under the hood. It's faster, more stable and far more reliable than the original How it works GMS Flags 2.0 is an LSPosed module. Instead of touching GMS or Phenotype, it hooks each app individually and changes flag values inside the app at runtime, no matter what's stored in GMS or Phenotype. That fixes the old pain points: • flags no longer reset every 24 hours • the new GMS restrictions don't affect it • old issues with Google Wallet, wallpapers etc are gone One tradeoff Because of this per-app approach, you can't tweak literally every package like before. For now it works with a predefined list of apps, and we'll keep expanding it over time Server-driven The app is tightly integrated with our own server, so a lot of things (recommendations, flag lists, micro-hooks and more) can be updated on the fly without shipping a new build Everything is reversible Nothing is permanent, any flag or recommendation can be turned off and all overrides can be cleared at any time Beyond flags Some features need more than a flag, so the app also supports micro-hooks, small runtime patches curated per app. These are signed by us and only run if GMS Flags is the untouched official build (our own safeguard, nothing to do with Google's Play Integrity). Modified or repackaged copies won't apply them We've also put a lot of work into analytics, which helps us understand priorities and see what people are actually interested in, so we can focus on what matters most The collection currently has 14 recommendations, with more on the way Requirements: root + LSPosed Heads up: this is the very first public beta, so things will break, some flags may not apply on every app version and a few features are still rough. That's expected, bug reports genuinely help and are very welcome. We'd love to hear your feedback and suggestions And well, let's see how long GMS Flags 2.0 lasts before Google decides to kill this one too :) DOWNLOAD: @gmsflags2_releases