TheBlissfulEntrepreneur · EJ's Wonder Emporium

Changing the landscape

Fri, 16 May 2025 13:11:00 +0500

How It Started

Back when I first started the BlissLabs nonprofit, I knew it had the potential to help transform the Android ROM scene at the time, so in my mind, it would be well worth the effort. What I didn’t know back then was exactly how it would do that.

At the time, I knew we needed to set up a way for the teams to collect funds, provide services like servers, design, and others, and make sure that it was not something only one person controlled. So setting up an org with a board and bank account was a must, but what kind of org was the question.

With my previous experience with my wife and her work with the Pediatric Hydrocephalus Foundation, I learned a lot about how that organization works, and how it relies on volunteers to advocate for Hydrocephalus, as well as what that advocacy looks like when it comes to lobbying. I could also see how an org for open-source Android projects could run on a similar structure. So I incorporated BlissLabs as a 501c(3) nonprofit organization, and all the leaders across the Bliss projects all voted on a board, which would have distributed control of the organization’s infrastructure.

The next steps were to get each project to assign a lead and form a way to not have just the board members calling all the shots, and let the board focus on stuff that the nonprofit would need to help the projects underneath it succeed. So we went into research mode and found a number of grants that helped supply emails, servers, documentation and planning services, and more, and distributed access to those across all the individual projects. This also included signing up for more notable donation collection methods as well, like OpenCollective, where we were in a unique position to sign on as a fiscal host, and let each project under BlissLabs set up an account and use BlissLabs as the host.

How It Changed

This is about the point where we decided to branch out, and promote what we did so other projects could benefit from it. This initially brought in community projects like Bliss-x86 (now Bliss OS), Boringdroid, SupremeGamers, and later led to Waydroid, SmartDock, XT-Mapper, IzzyOnDroid, Lindroid and others. With the majority of these projects utilizing BlissLabs as a fiscal host and a talent pool or think tank for ideas and innovation.

This eventually led to us also finding a way to tap that talent pool for others outside our org too. After being approached by a few companies wanting to have Android work done for them, we decided it was also time to start a separate for-profit company, Navotpala Tech (Bliss Co-Labs), that would be able to be insured, provide the means to manage incoming contracts, and empower the individuals that contributed to the many projects underneath the BlissLabs umbrella. Closing the loop for individuals looking to start off by learning through contributions towards our projects, and ending with paid opportunities for those individuals that showed a track record of dedication, innovation and lack of ego.

Where We Are Headed

This is where we are today. Two organizations, working together to cultivate innovation and bring to it products across the world. Working in a way that contributes heavily to the open-source ecosystem at the same time. And this is where I will set up the next stages of this vision too.

For the future of BlissLabs, we need to grow now. The nonprofit will need community organizers, content creators, grant writers, web designers, management, and a number of other positions added in order to facilitate the growth needed for the projects it has now, and the projects that will join in the future. And together we can all change the landscape to allow growth and monetization opportunities where there was never any clear cut way for all projects to grow, or these people to make a living doing what they love to do.

For the future of Navotpala Tech, in order to make sure that company stays true to its mission and vision, it is hard to find an exemplary solution when money is involved, and businesses often prioritize profits over ethics. Because of this, we have decided to continue on the slow growth road, letting small parts of each project help fund the businesses R&D budgets, and other initiatives that will expand the product line and fortify the company’s infrastructure. This will allow it to have the largest potential impact on the talent from BlissLabs projects, and give more than just a few core people a chance at contract development & design work. The business will still also continue to contribute directly to open-source development in order to help set an example for other businesses to know what a healthy CSR plan could look like.

Bass OS - when the bass drops, the music gets better

Wed, 13 Mar 2024 12:32:00 +0500

Project Background

About a year ago, I was contacted by a number of companies that wanted their own Android for PC OS that they could control the access and redistribution rights to. So I started on a journey putting together a new form of Bliss OS for the same kind of devices but done a little differently in order to target businesses, and product use, but was put together in a way that would allow me to retain rights to the parts that apply to all devices (the generic bits). When I first got started, the goal was to make one source have as many features as possible without the use of proprietary components like Google Play Store, Widevine, etc., and then just enable/disable various features and options for specific use cases. Around April of 2023, that goal was achieved and I had a solid starting point for the source that opened up many of the tiny little changes required for device and application specific use, and brought it all together with a single build toolkit. This at least set the stage for the bare minimum needs, and shed light on the future challenges for the project.

Challenges

The project updates would have to have the following goals, and those had a few challenges attached:

Make that system easy to expand:
I used a system that allows developers a simple method for expanding on the available build options and configuring the source all from the command line. Learning lessons from my previous projects like Android-Generic Project, I also wanted to include a way to make things easily upgradeable to new versions of Android. So this system had to include some of the advances to the patching system used in AG.
Make the system build process accessible for others:
I expanded the Bliss OS source and created new tools that greatly simplify the process and provide the majority of the configuration options through a single interface. This allows developers to easily setup, configure and deploy their generic Android .iso’s with little effort.
Reserve a place for private patches, addons, etc. for companies:
Some companies and developers aren’t able to share things as open source, so I need to take that into account and provide a way for them to naturally separate what should be a generic change and what should be a private change. So I added a few places for companies to add their changes and have them automatically apply when the source unfolds.
Reserve a place for the most valued assets to easily be integrated into the system:
I have many changes that don’t really fit in the “generic device” category, like password protected admin access, kernel level changes to guard against unwanted wireless devices being plugged in, etc., so I wanted to still offer these specialized changes to companies that had a need for them. The way I do this is through licensing addons (features). Each addon will come as its own separate project that gets linked inside the main bass-os project folder as an addon, patchset or manifest. This covers prebuilt pro versions of our apk’s, sources for API’s and packages, and individual changes to be placed on-top of the source.

Looking at what the community and industry have put together for Raspberry-Pi builds on Glodroid, Glodroid-Community and Tesla-Android, I was able to take inspiration from how they have things setup, and apply those concepts to Bass OS. This resulted in a single repo setup that developers and clients can easily manage, while retaining the ability to separate our private addons and features, and give developers a way to include their private changes as Ill. All while automating the process down to just a few keystrokes.

For those that are curious, I detail a little about the toolkit on our Website for Bass OS (https://bliss-bass.blisscolabs.dev), along with a glimpse of the many use-cases and applications for using an OS put together like this.

Licensing

The largest challenge I had for this project was related to ego. How do I create a product that is as easy to adopt and maintain as an Open-Source project, while still retaining the ability to generate income from it? This is where the licensing system comes into play. For many of the parts of this system, there are addons and features available. For the build system, we include the base “generic” options and scripts as part of the open-source project, while we reserve the “value added” bits for licensed use. And any parts of those two sides that cross over, should have a warning or error attached when they are used without licensing access to the change first.

Taking this approach will still allow us to provide companies, hobbyists, and individuals a free to use set of features, apps, and configurations, while attempting to force licensing onto those that would want to change the source and rebrand without properly licensing. Because innovation through open-source is only viable when we all play by the rules.

Sources & Documentation

Now we can get to the exciting part of this post, the source code. You can find the source at the following link: https://github.com/Bliss-Bass/bass-os but please pay close attention to the readme for that repo, as it contains all the required information to get things up and rolling. Including dependencies, hardware requirements, resource links and more.

I plan on creating addon guides & templates, contributing guides, and linking the various feature guides we have on Bliss OS docs that they have adopted for some of their builds. This should allow the community everything they need to build off our open-source offerings and set their own terms for licensing their creations if they choose to do so.

Gratitude

I do want to say Thank You to all the members of the business and user community that have helped the growth of this project. And I am looking forward to 2024 being a great year for Android on x86 based hardware.

Android, AOSP, and what Open-Source Licensing means for you or your company

Fri, 13 Oct 2023 12:32:00 +0500

Android is one of the most popular operating systems in the world, powering billions of devices. It is based on the Android Open Source Project (AOSP), which is a free and open-source software platform. AOSP is important because it allows anyone to modify and redistribute the software, which has led to a wide variety of Android devices and applications.

One of the key features of AOSP is that it is using open-source software (OSS) components licensed under the GNU General Public License (GPL), LGPL, MIT, BSD or Apache License. Some of these licenses require that the source code for any software that is based on AOSP must also be released under the same license. This ensures that users can inspect the source code for security vulnerabilities and make changes to the software to meet their specific needs.

In this post, we will discuss the importance of following through with the GPL source requirements for AOSP. We will also provide some tips on how to evaluate the security of software that is based on AOSP.

The Importance of Releasing Changes to the Source for AOSP

There are several reasons why it is important to follow through with the GPL source requirements for AOSP.

First, it ensures that you are complying with the licenses of all of the open source software that you use in your product. When others can trust that you are releasing any updates made, your product image is improved and you build further confidence with your user base.

Second, it helps to ensure the security of the software. When the source code is available, anyone can inspect it for potential security vulnerabilities. This can help to prevent malicious actors from exploiting these vulnerabilities to attack users.

Third, releasing the source code can help to improve the quality of the software. When users are able to contribute to the development of the software, they can identify and fix bugs that the original developers may have missed. This can lead to a more stable and reliable software.

Fourth, releasing the source code in its entirety can help to promote innovation. When developers are able to build on the work of others, they can create new and innovative software applications. This can lead to a more vibrant and dynamic software ecosystem.

What You Should Look For When Projects Do Not Produce Source That You Can Inspect

When an AOSP based project does not produce source code that anyone but them can look through, it is important to be wary. There are several reasons why a company might choose to do this, and we will touch upon the nefarious reasons first.

They may be hiding something malicious. If a company is not willing to release the source code for their software, it is possible that they are hiding something malicious. This could include malware, backdoors, or other security vulnerabilities.
They may be trying to lock you in. If a company does not release the source code, they can control how you use their software. This could mean that you are not able to make changes to the software, or that you are required to use their proprietary services.
They may be trying to make a quick buck. Some companies will release closed-source software that is simply a repackaging of open-source software. This allows them to charge a premium for software that is actually free or was not properly licensed for commercial use.

If you are considering using an AOSP based OS solution from a company that does not release the source code, it is important to do your research. Make sure to read reviews and security reports before making a decision. You should also be prepared to pay a premium for the software, as there is no guarantee that it is safe or secure.

If you are looking for an Android project that you can be confident in, it is important to choose a project that publishes its source code. This will help to ensure that the project is secure and that it is committed to quality.

What Can Make This Easier?

The importance of releasing source code based on AOSP cannot be overstated. AOSP is a cornerstone of the Android ecosystem, and it allows anyone to create and distribute their own version of Android. This freedom has led to a wide range of innovation, from custom ROMs to new devices and operating systems.

However, with this freedom comes responsibility. When you release a product based on AOSP, you are legally obligated to comply with the licenses of all of the open source software that you use. This can be a complex and challenging task, especially if you are not familiar with open source licensing.

Releasing source code based on AOSP is important for a number of reasons:

Compliance: It ensures that you are complying with the licenses of all of the open source software that you use in your product.
Transparency: It allows the community to see how you have used AOSP and other open source software, which can help to build trust and encourage collaboration.
Security: It can help to improve the security of your product by allowing others to review your code and identify and fix vulnerabilities more quickly.
Innovation: It can foster innovation by making it easy for others to build on your work and create new and innovative products and services.

Android-Generic Project Manager’s Auto OSS License Documentation tool can help you to comply with the licenses of all of the open source software that you use in your AOSP-based product. This tool can automatically scan your repo based code for OSS licenses and generate a manifest that documents the licenses and any required actions. This tool can be a valuable asset for any company that is releasing AOSP-based products.

In short, releasing source code based on AOSP is a good thing for everyone involved. It helps to ensure compliance, transparency, security, and innovation.

Conclusion

In this post, we have discussed the importance of following GPL source requirements for AOSP. We have also provided some tips on how to evaluate the security of software that is based on AOSP as well as provided a solution to assist in properly maintaining projects based on open-source code..

When choosing an Android project, it is important to take a hard look at the project’s security practices. One of the most important things to consider is whether or not the project publishes its source code.

If you are considering using an Android project that does not publish its source code, it is important to be aware of the risks. There is no way to know for sure whether or not the project is secure if the source code is not available. It is also important to be aware that the project may not be committed to security if they are not willing to publish the source code.

Here are some additional tips to help you evaluate the security of an Android project:

Make sure the project is licensed under the GPL, LGPL, BSD, MIT or Apache. This will ensure that the source code is available for inspection.
Read reviews and security reports. This can help you to assess the quality and security of the software.
Be skeptical of claims of security without proof. If a company claims that their software is secure, but they do not provide any proof, it is important to be skeptical.
Ask for a security assessment from a third-party security firm. This can help you to get an independent opinion on the security of the software.

By following these tips, you can help to ensure that you are using safe and secure Android software.

Building your own business through task automation

Sun, 07 May 2023 12:32:00 +0500

The importance of Task Automation

Task automation is the process of using software to automate simple tasks or a series of more complex tasks. This reduces the need for manual handling of such tasks, therefore improving accuracy and efficiency. Once configured, tasks are completed automatically, allowing more time for employees to focus on creativity and strategic workflows.

How to Automate Tasks

There are many different ways to automate tasks. Some common methods include:

Using software robots (bots) to perform repetitive tasks
Creating macros to automate tasks in a spreadsheet or other software program
Using workflow automation tools to automate processes that involve multiple steps

The Benefits of Task Automation

The many benefits of task automation include:

Increased productivity: Task automation can free up time for employees to focus on more creative and strategic work.
Improved accuracy: Task automation can help to improve accuracy by reducing the risk of human error.
Enhanced efficiency: Task automation can help to improve efficiency by streamlining processes and eliminating unnecessary steps.
Reduced costs: Task automation can help to reduce costs by eliminating the need for manual labor.

How to Get Started with Task Automation

If you are interested in automating tasks in your business, there are a few things you need to do to get started:

Identify the tasks that are most suitable for automation.
Choose the right automation tools.
Develop a plan for implementing automation.
Train your employees on how to use the new automation tools.
Monitor the results of your automation efforts and make adjustments as needed.

How I Automate Tasks in my Development Environment

Throughout my professional career, the companies I have founded have all stemmed from observing an existing need, and recognizing my ability to fill that need. Be it web design, application development, or software automation, my companies were also all established as partnerships. This collaboration allowed me to provide value to the client while collectively sharing responsibilities.

As time goes on, responsibilities can shift and the levels of efficiency and productivity can change. As usual, I answer the phone calls, I respond to the emails, I lead the efforts in sharing what the business is all about. In addition, for my current company I am also the primary developer which my clients are seeking to have working on their projects. The successes and experience gained through my previous companies have helped to establish myself as one of the top engineers in the field, intimately familiar with the software and hardware stacks being used.

This is where I start to let my creative juices flow a bit. The more effort spent on tasks “X”, “Y” or “Z”, the more I am able to identify the portions of those tasks which are repetitive. At this point I am able to mitigate this repetitiveness by utilizing existing automation tools or by creating new tools from scratch for these specific tasks. This results in a very lean infrastructure for a business. This form of task automation allows me to be more creative and focus on exemplary solutions for my clients and the community, instead of solutions that can bring a quick buck.

Task Automation in Development

When it comes to task automation in development, normally the mindset required does not come naturally. Meaning not everyone can easily recognise that they have performed the same steps in a process 3 times in a row. Their focus is on the task itself, not the process in which to complete it. To find this process, you must also record or note each step taken to complete the task/s.

For example, when working with Linux and AOSP development, 90% of the steps one takes are already recorded by default in a hidden file in the user’s “/home” directory. Check for a “~/.bash_history’’ file and it will contain all the commands entered into the terminal for that user’s bash sessions. Scrolling through the lines of commands recorded, we can begin to spot the repetitive commands which keep repeating. Those lines can be copied out into a separate notepad/.txt file for now, including a comment about the task it relates to.

After scrubbing through the history looking for patterns, there will be an arsenal of repeated steps, start looking at each task and establish variables from the parts that change. This allows us to start building small functions that can handle these variables (Example: do_taskname $1, $2, $3, $4, etc.). Building out functions to take specific inputs can also help take the work out of a lot of things that just take time away from creativity. Especially when we start to tie those functions together into something usable.

In AOSP, we still use a “vendorsetup.sh”. This allows us to build a “vendor profile” or use one that already exists in the project, and add the common functions there. Or if you are like me, you tie those functions together with a menu or a UI, and lock the user into the process they should follow.

An alternative route one could take when looking for ways to automate things in software and engineering, is to also look for others that thought of it first. This is where tools like the “Android-Generic Project” come into play.

Very often, when you see a need for a solution somewhere within your workflow, someone else also saw that need and already started working on a solution. My recommendation for places to look for such solutions include: Bitbucket, GitHub, and GitLab. There are of course other options though, you just have to keep your eyes peeled.

For your company, you have the unique knowledge and details of what you or your team’s workflow consists of.You have now equipped yourself with the knowledge of what to look for in order to make things easier, accurate, and efficient!. Get out there and start automating your work tasks. You can thank me later ;)

Conclusion

Task automation is a powerful tool that can help businesses to improve productivity, accuracy, efficiency, and cost-effectiveness. If you’re not already automating tasks in your business, then what better time than today to consider the benefits and get started?

Here are some important tips to help automating tasks in your business:

Start small. Don’t try to automate everything all at once. Start by automating a few simple tasks and then gradually add more complex tasks as you become more comfortable with automation.
Be patient. Automation can take some time to implement and get up and running. Don’t get discouraged if you don’t see results immediately. Just keep in mind that the efforts going in will lead to the improvements to the business in the end..
Be flexible. As your business grows and changes, you may need to adjust your automation strategies accordingly. Be prepared to make changes as needed.
Get help if you need it. There are many resources available to help you automate tasks in your business. If you get stuck, don’t hesitate to ask for help from a consultant or other expert.

If you would like to check out some of the task automation I have been using in my profession, feel free to head over to Android-Generic Project (https://android-generic.github.io). If you feel your AOSP based project could use an automation mindset to help make things easier on your engineering department, please checkout the Bliss Co-Labs (https://blisscolabs.dev), as that is kind of what we’re here for.

I hope you found this blog post helpful. If you have any questions, please feel free to leave a comment below. And if you know someone else who might find this information helpful, please share it with them.