Rebranding to AeolusUX

[Dia2809]

Hey Dev/s,

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

[AeolusUX]

Hey Dev/s,

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?

[Dia2809]

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?

I totally understand that you want to keep things simple, especially since you maintain it in your free time. My intention of a Rebrand was to keep the Fork more visible, especially because it supports the R36s which is one of the most used Handhelds. You are putting so much effort into this Project so why dont make it more visible that you are doing work on those too and not only the ArkOS team, allot of people assume this project is maintained by them while they are just doing the base updates for their devices and you (hopefully) test and see if it works on a r36s. Its like KNULLI and Batocera, they could have called them Batocera-35XX while they took the whole rebranding flair. I would say it could also help Devs from ArkOS, PortMaster, RetroHandhelds and such because sometimes they arent aware that this a seperate project.

Also another question why isnt it completly open source?

Thanks again!

[AeolusUX]

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?

I totally understand that you want to keep things simple, especially since you maintain it in your free time. My intention of a Rebrand was to keep the Fork more visible, especially because it supports the R36s which is one of the most used Handhelds. You are putting so much effort into this Project so why dont make it more visible that you are doing work on those too and not only the ArkOS team, allot of people assume this project is maintained by them while they are just doing the base updates for their devices and you (hopefully) test and see if it works on a r36s. Its like KNULLI and Batocera, they could have called them Batocera-35XX while they took the whole rebranding flair. I would say it could also help Devs from ArkOS, PortMaster, RetroHandhelds and such because sometimes they arent aware that this a seperate project.

Also another question why isnt it completly open source?

Thanks again!

I definitely see your point, and it’s something I’ll think about more seriously. Personally, I don’t really see my work as a full standalone fork — it’s more of a tailored version, similar to what Wummle did with his "Wummle Fork." That’s why I just called mine the "R3XS Fork" — to reflect that it’s focused on that specific device, without trying to present it as a completely separate project.

As for why it’s not completely open source: a lot of the scripts I use are community-made — some are shared on Discord, others hosted in personal repos — and much of the core comes directly from the official ArkOS sources. Most of the update-related scripts are already available in their public update repo. That said, I’m working on adding a dedicated scripts section to my own updater repo in the future, to make things more transparent and accessible where possible.

Since I’m building on top of a lot of existing work, I try to be careful about what I re-publish — especially when the original authors haven’t open-sourced it themselves.

[fyrus7]

I agree with the suggestion, because this fork is mostly different on how the system works, I get confuse the first time reading ArkOS wiki and find so many change in r36s then the original ArkOS. AeolusUX or AeoOS or ArkAeoOS should be nice