Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cdylibcore and JNI bridge for per-app foreground interval aggregation.arm64-v8aandarmeabi-v7aas part of the database flavor build.Scope
This is the first measured migration slice, not a claim that the whole application has already been rewritten. Android APIs, UI, Room/database schema, permissions and lifecycle remain Kotlin. Further pure business-logic modules can move incrementally after parity tests.
Validation
CI runs
cargo test, both flavor unit-test suites, and both debug APK builds. The signed Release workflow continues to use the existingKEYSTORE_BASE64,KEYSTORE_PASSWORD,KEY_ALIAS, andKEY_PASSWORDsecrets and must verify the same signing certificate before publishing.Compatibility
No application ID, database schema, versioning format or signing configuration is changed.