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
{{ message }}
This repository was archived by the owner on Jun 9, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 9, 2026. It is now read-only.
I have a little question, is it possible to rebrand this project to just AeolusUX or something else, i mean its something bigger now than just a fork of ArkOS and people assume its just ArkOS with support added for R36s clones, while this Project is so much more and could be allot bigger.
It also gives you the opportunity to get free from the chains of ArkOS and then you all would be able to support more and better
I have a little question, is it possible to rebrand this project to just AeolusUX or something else, i mean its something bigger now than just a fork of ArkOS and people assume its just ArkOS with support added for R36s clones, while this Project is so much more and could be allot bigger.
It also gives you the opportunity to get free from the chains of ArkOS and then you all would be able to support more and better
Thanks Damian
Hi Damian,
Thanks for suggesting a rebrand like AeolusUX to highlight the project’s growth. The Community Image, ArkOS-R3XS, is just a custom ArkOS image tailored to how I want my R36S, built with community scripts. As this is a pet project I work on in my free time and share with the community, keeping the ArkOS name simplifies updates and avoids rebranding hassle. I’d consider rebranding the ArkOS-K36 fork for clones, but with others now supporting those clones, I’m likely dropping it altogether.
What benefits do you see in rebranding ArkOS-R3XS?
Repository owner locked and limited conversation to collaborators on Jun 4, 2025
Activity
AeolusUX commentedon Jun 4, 2025
Hi Damian,
Thanks for suggesting a rebrand like AeolusUX to highlight the project’s growth. The Community Image, ArkOS-R3XS, is just a custom ArkOS image tailored to how I want my R36S, built with community scripts. As this is a pet project I work on in my free time and share with the community, keeping the ArkOS name simplifies updates and avoids rebranding hassle. I’d consider rebranding the ArkOS-K36 fork for clones, but with others now supporting those clones, I’m likely dropping it altogether.
What benefits do you see in rebranding ArkOS-R3XS?