BlissOS Updates

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 [email protected] 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

ping us or send a message so we can send you to a private chat. We hope someone can be able to volunteer and we can solve this once and for all.

Example of the bug can be seen here:

https://x.com/k1y1L8ygYd1zmS1/status/1799801890693374350
https://x.com/o6Rr3jUfBa47782/status/1799790873674383360

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.

Hey look, new BlissOS releases 👀

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

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

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

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

https://fixupx.com/blissos_org/status/1791859895907782929

https://fxtwitter.com/blissos_org/status/1790493423021260933

https://fxtwitter.com/blissos_org/status/1789205368431927509