BlissOS Updates

As we bid farewell to the year 2024, We want to take a moment to express our deepest gratitude to every single one of you in this community. Your unwavering support, contributions to development, dedication to maintaining devices, and efforts in various capacities have been the backbone of the BlissRoms and BlissOS project. Most importantly, thank you for being an integral part of the Bliss Family, trusting in our vision, and helping us spread bliss to countless users around the world. This year has been an incredible rollercoaster ride for Bliss development, filled with challenges, achievements, and growth. Let’s raise a toast to the amazing memories, happy moments, and laughs we’ve shared along the way. Here’s to continuing this beautiful journey together, making BlissRoms and BlissOS even more extraordinary in the year to come. Thank you all for being with us, and cheers to a bright and blissful future ahead! 🌟🎉 #StayBlissful #FeelTheWind #Voyager

Team Bliss wishes you a Merry Christmas! 🎅🏻🎄🎁 #StayBlissful

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.

**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.

We have also provided support for another tablet featuring a Silead touchscreen. Here's the SARY Tab 3. The kernel patch and firmware are currently awaiting integration: https://github.com/onitake/gsl-firmware/pull/242 https://lore.kernel.org/platform-driver-x86/20241202221802.9711-1-buingoc67@gmail.com/

Suprisingly, vmwgfx is now working on BlissOS. And it's all thanks to a project that we did not expect https://fixupx.com/blissos_org/status/1860618609120407787

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 <samsung_options> 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.

Wishing everyone a joyful, vibrant, and prosperous Diwali, celebrating the triumph of good over evil and light over darkness. ✨🪔✨ Stay blessed and enjoy the festivities! #StayBlissful

Wait this is not Android 🤔

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

Ok maybe one more update, then we will stop for transitional phase The new builds addressed 2 bugs: - For esdfs bind mounting, we added SDCARDFS_DISABLE=1 to allow disable it. And on Live boot, by default esdfs bind mounting will be disabled. - For KernelSU, we've found out why it broken on recent kernel version on both stable & LTS. On recent kernel, they've implemented a syscall hardening solution that prevented others from hooking up syscall, thus blocking KernelSU from being able to hookup syscall like faccessat(). https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.11.3&id=1e3ad78334a69b36e107232e337f9d693dcc9df2 We can revert this and can continue to be able to use KSU without any issue, however we don't know how risky it is to revert in term of security (we literally revert a hardening solution). So instead we decided to add a cmdline to the kernel. Users can set syscall_hardening=off to the kernel to be able to continue using KernelSU, but please be aware of that you are stripping away a security measure ! For discussion about this bug & future solution, you can check out this Github Issue on KernelSU repo: https://github.com/tiann/KernelSU/issues/2113

Are you a Vietnamese and have a Facebook account ? We've opened a Facebook page that post in Vietnamese ! https://www.facebook.com/blissosvn

Also also, while we made a video a couple of days ago saying that we will remove ARM translators & Widevine DRM, we actually not remove them in these new builds..... yet. Not only that, these Official Stable builds will be the actual last builds that include them. Which lead us to the big news we would like to announce: We are officially in a transitional phase. During this time, BlissOS will stop releasing new builds to focus on development & prepare new documentation. Support in chat is still available but mostly will be handled by mods. If any volunteers would like to help us during this phase, here's what you can do: Package ARM translators & Widevine DRM into flashable zips. Magisk/KernelSU modules can also do the job but you have to disable unmounting modules feature on apps. Make sure it have init.d scripts to survive OTA updates. We will choose the good ones and put them in our new Documentation. There will be no ETA when we will coming back, but we hope that we can finish that as soon as possible. Thank you for your continued support. We truly appreciate your patience and contributions. #StayBlissful

We've updated all stable builds with August 2024 ASB. Kernel is also being updated with latest KernelSU version. And there is one new feature in all of these builds: You can now be able to activate keymappers such as Panda Keymapper (and other keymappers with ARM-only libraries)...... with some little extra work. Usually to activate keymappers they will create some "injection" scripts which is just trying to run an app_process command. What you need to do is to edit the script to add this to the app_process command

app_process -Xforce-nb-testing <the_rest_of_the_command>

Then you run the script and it will be activated. All the work to make this force native bridge option working is already done by us and Undefined (https://github.com/qwerty12356-wart). If you have any issue, you can report to us. Also due to some issue with the build server over the last week we have to constantly rebuild to fix the KernelSU versioning issue. If your KernelSU report that the version is old, tell us immediately which version so we can rebuild them.

We would like to welcome IzzyOnDroid@floss.social to our BlissLabs family of Android & Linux projects on OpenCollective! You can find their collective page here: https://opencollective.com/izzyondroid

Quick PSA

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

Eid Mubarak to everyone celebrating! 🌙 ✨ Also on Twitter | Insta