Logan Magee

Christian and software developer focused on application and OS security. Creator of @accrescentapp. bsky: @lberrymage.dev | fedi: @[email protected]

[Logan Magee @lberrymage]

I'm reworking how Accrescent handles Android app versions, and it turns out that there's no consistent global ordering across all Android versions because of how Android composes longVersionCode and accepts negative versions 🫠.

I don't think we need versionCodeMajor.

[Logan Magee @lberrymage]

@ripsline @maxtannahill @BawdyAnarchist_ @accrescentapp No. I've been a volunteer community moderator for them and have made some minor contributions to their projects, but Accrescent is an independent project. Developers don't have to do anything themselves for Accrescent's signature verification.

[Logan Magee @lberrymage]

@ripsline @maxtannahill @BawdyAnarchist_ We're working on refining the requirements to open up submissions in a self-service way in the future. But the initial batch of developers who publish on Accrescent now were accepted selectively to help test the platform.

[Logan Magee @lberrymage]

@ripsline @maxtannahill @BawdyAnarchist_ Except for a couple of apps, developers proactively reached out and asked if they could publish their apps to Accrescent. If they met the documented requirements, they were usually accepted. This was to build a small testing userbase.

[Logan Magee @lberrymage]

@brutecat MinIO was discontinued a little bit ago without much warning, so I don't think it'll ever get patched as far as open source MinIO is concerned.

[Logan Magee @lberrymage]

@Technetium43_ Have you tried downloading it again? It seems to be working on my end.

Also let me know if you're using a VPN, Tor, or any traffic filtering or ad blocking app. We try to allow VPN/Tor traffic, but sometimes it gets blocked, and occasionally traffic filtering apps block our IPs.

[Logan Magee @lberrymage]

@Nasher6328 @fred6279 @Tricknologue @GrapheneOS @realmelontusks For banking apps, it depends on the app. The website has a section about them: https://t.co/K6fze5Xfu8.

There's a community list of banking apps compatible with GrapheneOS at https://t.co/ELipP98FrK.

Tap to pay depends on the app. It does not, notably, work with Google Pay.

[Logan Magee @lberrymage]

@Nasher6328 @fred6279 @Tricknologue @GrapheneOS @realmelontusks The camera quality is no different with the same app on GrapheneOS, and you can use both GrapheneOS' camera app or the Google Camera app if you prefer

[Logan Magee @lberrymage]

@Nasher6328 @fred6279 @Tricknologue @GrapheneOS @realmelontusks Yes to both. https://t.co/clbOkbEAN5 and https://t.co/kXK4kokVbr have more details

[GrapheneOS @GrapheneOS]

We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support.

https://t.co/8flkjD52Eg

[Logan Magee @lberrymage]

@MishaalRahman @Android Congratulations!

[Logan Magee @lberrymage]

@MishaalRahman Wow! Congratulations! It's sad to see you leaving the Android news scene - I've gotten a lot from your coverage that I can't find anywhere else - but I'm excited for what you have ahead. Wishing you the best!

[Logan Magee @lberrymage]

@rjc_uk @naomibrockwell @GrapheneOS Wildcards are also supported in some parts of the <queries> element, so apps don't even need to explicitly list individual apps they want to see.

I think QUERY_ALL_PACKAGES is slightly more powerful than <queries> wildcards, but I can't remember which APIs require it.

[Logan Magee @lberrymage]

@rjc_uk @naomibrockwell @GrapheneOS Apps don't need QUERY_ALL_PACKAGES to see other apps in the same profile: https://t.co/S2YHXMtgmZ

QUERY_ALL_PACKAGES also isn't a runtime permission, so it's granted automatically to apps which request it. Google Play does place some restrictions on its use though.

[Logan Magee @lberrymage]

@oxycblt Congratulations!

[Logan Magee @lberrymage]

@HSVSphere @GrapheneOS For more context: https://t.co/l7yeRgu41y

[GrapheneOS @GrapheneOS]

We're allowed to make a release with currently available revision of the December 2025 Android security patches right now but we wouldn't be allowed to publish sources. Therefore, we'd need to do this separately from regular GrapheneOS. We could special release channels for it with delayed tags...

It's trivial for someone to reverse the Java and Kotlin patches to source code within an hour of us releasing that. They could then submit security patches elsewhere including to GrapheneOS. This clearly isn't something Google's technical security people came up with as it's completety nonsensical.

[Logan Magee @lberrymage]

@HSVSphere @GrapheneOS I don't speak for the project, but they use the official signed security patch source code. They don't reverse engineer it. But you're correct that it doesn't make much sense to have long embargoes. GrapheneOS has criticized the move to longer embargoes partially because of that.

[Accrescent @accrescentapp]

If you've wondered how Android developer verification affects Accrescent, today we have a new blog post explaining briefly what it is, how it impacts us, and how we're responding.

https://t.co/FrFr5mJzu2

[Accrescent @accrescentapp]

It's time for an update! Check out our blog for a new update on:

- What we've accomplished in the last 3 months
- What's next for Accrescent

Thank you to our supporters for making this possible!

https://t.co/9vHexjZv1W

[Accrescent @accrescentapp]

Accrescent 0.28.0 is out, including:

- Download cancellation support
- Better update scheduling (especially on Android 14+)
- UI improvements and bug fixes

Full release notes below!
https://t.co/D4IWBuRAXo