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

I started the Bass toolkit and Bass OS (Bliss-Bass) project a while ago, and it's about time I post an update on how things have been going.

Check it out on my blog and see what all the commotion is about: https://electrikjesus.github.io/blog/Bass-OS-when-the-bass-drops-the-music-gets-better/

For the next major release of BlissOS, we've decided to open a Public Alpha. Not only this is the BlissOS version that is based on AOSP 14 (QPR1), but also We will try to go Vanilla-only

Yes, you heard that right, soon there will be no Gapps/FOSS builds and instead just pure Vanilla. Not only that there will be no native bridge integrated in the builds either. But don't panic, there will be way for you to install it. For the last few weeks, we've been actively working on bringing Android's Recovery Mode to BlissOS or Android-x86 in general and the result is Blissful :D. You will soon be able to flash Gapps or microG into the OS. Not only that, you will be able to flash OTA zips or native bridge too.

This will open a new chapter for us, and we hope you will support us in this journey.

Before proceeding, please remember that this is still in Alpha stage and it is for testing purpose.

https://paste.myself5.de/ofehizeref.sql

sorry I forgot to mention in the documentation above that after done flashing MindTheGapps or MinMicroG, please wipe your data

Clean up everything, start new. Treat it like you flash Gapps on a phone. Wipe the data

Bliss

New website updates have been pushed to the Bass site, including sources and documentation. And new Desktop Hybrid builds are available for Bass OS.

Features:
- Multiple boot entries for single-display, multi-display and multi-display IME
- Updates for MicroG included
- Fixes for freeform windows
- Fixes for sleep modes
- Added configs for CPU power management
- Check the changelog for more

Documentation:
- New docs site at: docs.blisscolabs.dev

You can find the download link on our website:
http://bliss-bass.blisscolabs.dev

- A vanilla hybrid desktop version can also be found on our souceforge (allowing you to flash gapps through KernelSU).

Just a small warning : In the future when we all move to Vanilla with Recovery Mode, we will only allow promoting packages that we've listed & recommend, we will not allow promoting other packages in the chat. This is due to 2 reasons:
- We don't have time to check for the legitimacy for all packages, they could make noscript that wipe everything on the device and this is happened before on phone side
- Some binaries might contain modified code, which is illegal. For example if you share a modified libhoudini in the chat Intel could sue not just you, but us (especially us since BlissLabs is an organization located in the US).
Take Yuzu Discord Server as a lesson for this. So if you want to share something, do it out of our scope. Do not share it inside the chat. If you do, we will handle it like we usually handle violated members (mute & ban)

We will warn again once the next BlissOS release come, and we will also add these to our rules

and yes this is also apply to Magisk/KernelSU modules

Check out our journey at #FOSSASIASummit2024

https://twitter.com/blissos_org/status/1778126146326110330

https://twitter.com/blissos_org/status/1778126146326110330

https://twitter.com/blissos_org/status/1778135279368544554

Do you have trouble setting up audio on your tablets/laptops that are using audio cards like bytcht* , bytcr* , cht-bsw* , chtmax*, chtrt* ? Reply now as we are trying to make these cards working once and for all !

We will say this once and we hope we can make this clear

When you come to us for support related to wifi, the most important information you should get for us is the wifi card name, not just the device you are using

And don't give us only the company who made the card, we don't take the My wifi is a TP-Link or The card is Intel as an answer. Actual, full name of the card, and if you know the actual chip name inside the card that would be extremely helpful

The upcoming version of the Linux kernel (6.10) will soon allow configuring touchscreen properties via cmdline. This commit will be particularly valuable for us in supporting devices equipped with silead touchscreens, as we’ve received numerous requests related to this hardware.

https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=review-hans&id=0b178b02673998f5acca5a0365a8858ca45beedb

We also backported it into our kernel source
https://github.com/android-generic/kernel_common/commit/9da3a2b1d3387c78b84a6b66432a7879df7ded3b

This change will soon be available to all of our upcoming builds, including Zenith which soon will use kernel 6.9
Updated tutorial on how to use this cmdline will also available soon on gsl-firmware repo:
https://github.com/onitake/gsl-firmware/pull/233

To help users following the tutorial closely, we will also bring "evtest" to all of our upcoming BlissOS builds.
https://github.com/android-generic/external_evtest
You can also use AOSP's getevent tool if you already get used to that

With the help of this change and the updated tutorial, we're happy to report our first successful case in supporting silead touchscreen.

Here's GlobalSpace SolT IVW 11.6" using a GSL168x touch controller.
We've made a patch to support it in BlissOS kernel. Not only that, we also submitted this patch into linux kernel upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=review-hans&id=7c8639aa41343fd7b3dbe09baf6b0791fcc407a1

BlissOS 14 (2020-2025),
a cherished member of the custom ROM community, is suffering in bed and it's currently on life support, and may not make past April 2025. After a valiant four-year battle against outdated security, BlissOS 14 succumbed to the cruel hand of time.
Though gone, BlissOS 14 is survived by its younger siblings, BlissOS 15, 16, and 17. The family encourages those who loved BlissOS 14 to carry on its legacy by upgrading to a newer version.
A brief period of mourning will be observed until April 2025. In lieu of flowers, donations to the open-source software community are appreciated.

Please see the full memorial post here: https://blog.blissos.org/bliss-1410-eol-plan

Hey look, new BlissOS releases 👀

https://blog.blissos.org/bliss-06-updates

We've noticed that there are some Japanese users trying BlissOS to be able to play Gakuen iDOLM@STER. However, some users with AMD GPUs are having issues on a live stage performance in which the big screen on the stage turn red when it supposed to play videos.

We acknowledged the issue, the thing is we can't be able to replicate this. To be able to replicate, we will have to spend time on the game to grind until we can get the SSR ticket and unlock the song. We can pay for gacha, but that's not worth just for recreating a bug.

Which is why we are looking for a volunteer that can help us instead. You'll either helping us getting logs and see what's wrong, or if possible, giving us the account to test. We're thinking that give us the account will be the last resort. If that happen, we on BlissOS and BlissLabs as a whole promises that your account will be safe as it only being used for testing, nothing else.