Repository navigation
Community Notices in Updater CE, Themes Gallery and Community Firmware Archive #6
ryan-specter
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In order to help protect device users from devices becoming non-functional after a firmware install, we are implementing a Notices feature across Updater CE, Themes Gallery, and Community Firmware archive that allows users of these tools to be displayed timely and proactive notices of issues resulting from installing stock and custom firmwares on devices. This will be alongside the release of Updater CE 2.5.2 in early November with Y2Reborn installs available.
This is inspired in part by scenarios that have already taken place such as Innioasis rendering Type B Y1 units (those that sold with firmware versions before 2.0), inoperable via software updates and did not communicate this to owners, and the recent hardware changes made to Y1 units sold after April 2026 that caused them to not boot with older versions of the stock firmware and a number of custom firmwares such as Rockbox-Y1 <0.4)
By being able to notify members of the community in this way we can ensure that these releases are blocked by the Updater app and that users are made aware of issues and remedies where these may arise
These notices will be hosted in English, but will be translated by the Updater CE desktop application where users have auto-translations enabled, and can of course will be available on innioasis.app and themes.innioasis.app in your language with browser translation.
If you wish to raise a community notice across these tools via the Notices feature, please raise it via this Discussions thread.
You can also submit requests for informational notices for things like major changes to a project, new projects and other non-priority messaging that can also be shown via this channel to users as non-invasive toasts. For example if you're releasing a new custom firmware on the Community Firmware archive , then you can let users know via this optional notification channel.
Another way to submit a notice for review is to create an XML element in notice.xml and submitting a Pull Request.
All reactions