About dArkOSen
I'm Dave, the developer behind dArkOSen. I started developing in April 2026, around the same time I discovered what Bash is. Up until then I referred to it simply as 'linux', not even fully understanding what a shell script was. I've come a long way in a short few months lol. dArkOSen grew out of a lot of experimentation, problem-solving, and a willingness to figure things out as I went.
dArkOSen originally started as the R36H ProMax Compatibility Project. The goal was simple: bring dArkOS to the ProMax with a boot sector that could correctly load the larger boot logo required by the device.
The eventual solution was something of a Frankenstein build, combining pieces from several developers and builds, including ArkOS4Clone. As the project gained attention, I kept adding fixes and improvements to the setup tool. Eventually, people started asking for the same treatment for the R36S.
That project became just as popular, so I consolidated the two into a single master build and called it dArkOSen - dArkOS, enhanced.
The idea became simple: one build to rule them all.
Today, dArkOSen is a unified build designed to install across genuine supported devices, bringing together the fixes, improvements, and collection of tools I've developed throughout the project.
Interestingly, dArkOSen has already reached the point where it would have been considered finished if this were still only my personal project.
The original goals have been met: custom hotkeys, faster boot times, countless system stability repairs, and -perhaps most importantly- the feeling that the system is polished and that things should simply work the way you expect them to on the R36S.
At this point, continued development isn't really about solving problems that I personally need solved. It's about making the experience better for everyone using dArkOSen.
The current goals are therefore focused on refining the user experience, improving the bundled tools, and continuing to add useful features.
That's ultimately up to the community.
I enjoy building things, solving problems, and learning along the way. But development takes time, and dArkOSen has grown considerably beyond the project I originally started for myself.
If the project continues to be useful to people, I'd like to keep improving it. Support is one way of making that worthwhile.
Buying me a coffee isn't going to fund a development team, but that's not really the point. Financial support is a tangible way of saying “this was worth my time” - and that carries considerably more weight than words alone.
If dArkOSen has made your device better, solved a problem for you, or simply saved you some time, and you'd like to help keep development going, consider buying me a coffee.
It helps keep me motivated to see what I can break-and then figure out how to fix it.
I use AI extensively while developing dArkOSen. It has been an incredibly useful learning and development tool, particularly while I was learning Bash, Linux, and the many other things I needed to understand along the way.
That doesn't mean I ask an AI to write something, paste the answer into dArkOSen, and call it finished. I use it more like a combination of research assistant, teacher, debugger, and second set of eyes. I still have to understand what I'm changing, test it on real hardware, figure out when something doesn't work, and ultimately take responsibility for the result.
When I started out, I was writing pseudo-code that was maybe 20% actual code and 80% English, then using Claude to translate my intentions into proper syntax. Now the ratio is closer to 90/10, with many of my projects now written entirely by me and AI primarily used for debugging or particularly complex problems. It literally saved me months of work on the Battery Calibration Tool.
I simply wouldn't be able to maintain my current output and level of quality without the assistance of AI tools.
I can be pretty vocal about my dislike of vibe coding, so I think it's worth explaining the distinction as I see it.
Nobody would judge a framer or carpenter for using a hammer. More importantly, no decent framer would hand the hammer a blueprint and let it decide how to build the house. Not even if it was the smartest hammer.
That's how I see AI. It's my hammer. And just a hammer. I'm still the builder.
I use it to help me learn, investigate problems, write and review code, and get through the tedious parts of development faster. But I decide what gets built, I need to understand what I'm changing, and I test the results on actual hardware. When something breaks, it's still my problem to understand and fix.
The difference is that my hammer lets me put down a lot more nails than I could manage on my own.
Four months ago I barely knew what Bash was. Today I'm maintaining an operating-system project and an ecosystem of scripts used by thousands of people. AI has been a big part of how I got here, but I still had to learn how the machine works for myself.
dArkOSen is a passion project born out of love for the R36S. If you appreciate what I do and want to support the project you can show that support by buying me a coffee. Proceeds help fund the cost of SD cards and other expenses involved with development.