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

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

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