Just saw this on our SourceForge, and we forgot to put on a warning

Please do not sharing our SourceForge link, like.... just don't. Share our website instead. We've seen some people shared our SF on many different forums and ended up causing some confusion to newcomers:
- They download OTA zips instead of iso images (like this guy) .
- They don't know which Android version they are downloading.
- They don't know which variant (Gapps/FOSS) means.
- The green Download button & Project Activity made people mistakenly thought that the builds that we uploaded are latest which is an issue because for example if we build BlissOS 14 last, people will think that it's the only latest version we are providing right now.

Our website not only direct to the correct place to download the iso, but also have explanation for version number & variants. So please, share our website, not our SourceForge !

Call for Contributors: Help Shape BlissOS Vanilla Builds!

As BlissOS transitions toward Vanilla builds, we’re seeking skilled contributors experienced in bash scripting and/or creating flashable zips for custom recoveries or KernelSU (KSU) / Magisk modules.

If you got the skill and is interested in making one for the upcoming BlissOS updates, we’d love your help in developing modular or flashable zips for proprietary components like GApps, DRM libraries, ARM translators, or other enhancements you believe would benefit the community.

What we offer:
- Access to our current development resources for testing your work.
- Collaboration to verify and officially recommend your contributions in our documentation. (If requested)
- Visibility as a trusted resource for BlissOS users. (If requested)

Interested? Reach out to @hmtheboy154 to discuss your ideas and get started!
Note: We are NOT currently accepting requests solely for testing BlissOS builds.

Important Announcement: BlissOS Source Lockdown

Effective immediately, all BlissOS source code will be in lockdown. Ongoing internal changes are being made, and these updates have not yet been pushed to the repository. We strongly advise anyone currently syncing or planning to sync to halt the process immediately.

Please note that we will not be able to provide assistance to anyone attempting to build BlissOS during this period. We apologize for any inconvenience this may cause and appreciate your understanding.

You have a Samsung Galaxy Book but audio is not working ? Here's what you can do to make sure it will have a chance to work in the next Zenith build and maybe future BlissOS builds.

First, install a linux distro with Kernel 6.11.3+. Recent rolling distro like Fedora or Arch Linux are already shipped with newer 6.11 kernel so you can use them.

Next, prepare a file in /etc/modprobe.d, something like /etc/modprobe.d/samsung\-audio.conf. In that file, add this code

options snd\-hda\-intel model=<samsung\_options>

Replace with one of these
alc298-samsung-amp
alc298-samsung-amp-v2-2-amps
alc298-samsung-amp-v2-4-amps

Save and reboot to test. If one of the three options works, that mean audio will work on the next build of BlissOS too. In the future, you still have to create the same config file. However, you can help us bringing your model to patch_realtek.c by giving some info about the laptop & the option that made your audio work.

To users who are using Surface builds and trying to calibrate iptsd, we realized a mistake in our Documentation: the location to store configuration files should be /data/vendor/iptsd.d instead of /data/vendor/ipts.
We've fixed it in our Documentation
https://docs.blissos.org/configuration/calibrate-and-configure-iptsd/

Please update the directory name based on the new edit.

FYI Android emulators & containers solution out there, this also affect your projects :(

We forgot to post anything about the suspend issue

Currently we only support S3 suspend (aka Suspend\-to\-RAM). Meanwhile the old Intel Atom tablets or most recent devices are only support s2idle (aka Suspend\-to\-Idle). Either linux handling s2idle really buggy on the device, or our Suspend HAL handle it really buggy. Whatever the case is, you should not using it on BlissOS for now

To know if your device support s2idle and disable suspend if true:
- On a terminal app like Termux open /sys/power/state

$ cat /sys/power/state freeze mem disk

If it have both mem & freeze then might support both S3 and s2idle. If it only have freeze then you might only support s2idle.

Next, to further check. You can read /sys/power/mem_sleep

$ cat /sys/power/mem\_sleep s2idle [deep]

If you have deep and it's in the square brackets, then yes you support S3. If the brackets pointed to s2idle then you can use echo deep > /sys/power/mem_sleep or switch it on BIOS Settings. There is a Sleep State option, usually it will say Linux or Windows in which Linux is actually S3.

- If you have mem, chances are S3 is already the default sleep state. If it doesn't , edit grub and boot with

SLEEP\_STATE=mem

- If you only have freeze or you don't want to use suspend, boot with

SLEEP\_STATE=none

The device will immediately wake up instead of suspend

More info about sleep state on Linux you can read here
https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html

New weekly Zenith builds released with kernel 6.9.5.

Also after some testing, we've realized that currently KernelSU on Zenith builds are working, but it's broken a bit
- You can grant files explorer like MiXplorer or Amaze root permission
- You can grant tweaking tool like SmartPack Kernel Manager
- On Termux you can't type su, but you can type /system/bin/su
- XtMapper still can't be able to activate, we might have to go with manual activation using Termux method