yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] WoltreX:
good work. :good: I have already mentioned that there is a working problem with the ntfs file system. I finally figured out what the problem. When the Bliss os is booting, writing Dalvik caches over ntfs disk. The android system can not read it naturally. Because the android systems are working with linux (ext3/4) and fat32 file systems.

-Solution Suggestion: If you can make dalvik cache files available into the data.img, the problem will be resolved.. :fingers-crossed:

NOTE: Those who implement this guide will not get any boot failure. >>

[GUIDE]How to setup Dual Boot on legacy PC? (BlissOS and Windows 7/8.1/10)

Main problem: Storage folder does not access disk parts. The root explorer does not see the disk partitions.
[BLISS ROMS Development] Eagle0110:
Tried "Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180602-1820_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_sp4.iso" on Surface Pro 4 i5, the touchscreen unreliability problem seems to have returned, touchscreen consistently dies only a couple minutes after boot.
[BLISS ROMS Development] electrikjesus:
Do you have any idea how to go about doing this?
[BLISS ROMS Development] WoltreX:
Yes, the problem corrected with a changed code. :good:

Users must use that grub code if they want to boot on ntfs disk.

title BlissOS

root (hd0,1)

find --set-root ls /BlissOS/system.sfs

kernel /BlissOS/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/BlissOS vga=788

initrd /BlissOS/initrd.img

boot

For single boot and ext4/fat32 disks:

title BlissOS

root (hd0,1)

find --set-root ls /BlissOS/system.sfs

kernel /BlissOS/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/BlissOS Data=/BlissOS vga=788

initrd /BlissOS/initrd.img

boot
[BLISS ROMS Development] yuzvir:
as for me, the touchscreen on sp4 doesn't work at all with this image in live cd
[BLISS ROMS Development] breaklaw93:
This rom got power button on screen,my power button laptop broken.
[BLISS ROMS Development] MagicAndre1981:
I can't boot this version on my Toshiba Encore 8. I see the consoleoutput but never get to the poind of the android boot logo. The last nightly works, but it looks like the changes of this version are not part of the nightly. (nightly is smaller).

I've just extracted the new files of the ISO and replaced the old ones on my drive in C:\AndroidOS. Do I have to do anything else to update from nightly to this version?
[BLISS ROMS Development] electrikjesus:
Nope, that's it.

I will see if I can get some time soon to build out an updated 4.16.14 kernel without all the IPTS and Atom/CoreM commits, and add that to the nightlies.
[BLISS ROMS Development] kypor:
I had the same issue on my Dell Venue 8 Pro, and Asus 102HA. Had to use nomodeset to get it to boot for both.

Sadly, audio doesn't work on both devices, and I tried the old modprobe method as well on both devices. :(

Used the Windows installer with the below ISO

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180608-1825_k4.16.13-ipts-blissified-ath-crt_18.1.0-devel_w14_dev-kernel.org
[BLISS ROMS Development] bart2465:
I can confirm this. Same problem on my Surface Pro 4 i5.

In the previous sp4 build this problem was not present.
[BLISS ROMS Development] MagicAndre1981:
ok, this worked, but Performance is terrible. GUI is really slow.

---------- Post added at 18:44 ---------- Previous post was at 18:41 ----------

for what does IPTS stand?

Btw, can you update the patchlevel to June? I'm not sure if the security issues from may/june are important to have.

---------- Post added at 18:50 ---------- Previous post was at 18:44 ----------

Also, the Wifi issue is still present.

using ifconfig wlan0 shows brcmfmac as used driver. Does this driver fully support the Broadcom BCM4324?
[BLISS ROMS Development] 4r44444:
ROM doesn't liveboot. some white boot commands appear on screen after clicking live boot, than tablet turns off.

Chuwi Hi12
[BLISS ROMS Development] kypor:
Update

Tried latest nightly (Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180612-0129_k4.16.5-blissified.iso) using Windows installer and was able to boot my ASUS 102HA without using "nomodeset" so graphics were better. However there was no automatic rotation, and audio still didn't work.

I'm not sure if audio hardware not working could be the issue, but I was unable to play any games I tested. I tried playing Marvel Strike Force, and Star Wars Galaxy of Heroes but both would not start.
[BLISS ROMS Development] tobad:
thx for reporting. didn't had time to try it by myself.
[BLISS ROMS Development] MagicAndre1981:
[MENTION=8756998]kypor[/MENTION]

the nightly version don't include the changes, so here are no issues...
[BLISS ROMS Development] corrifa:
I see in the bleeding edge section of the downloads that mostly all the newer surface devices have the newer kernel (4.16.8), however I don't see an updated version of the original Surface Book (1st gen).

Is this something in the works? Or will another version work for the original Surface Book? I am currently using the version from March, with only minor issues, just curious why it seems to be the only one not in the new set. Thanks! Really appreciate the work put into this.
[BLISS ROMS Development] arifqur:
I have a HP Specter x360 15T model and the last nightly that I am able to boot is the one dated March 8, 2018. The last Bleeding edge that boots is dated Feb 28, 2018.

I have downloaded nearly 30 builds other than these and they don't boot and keep stuck after finding the x86 and the cursor keeps blinking and that's it.

The March 8 nightly is installed via the Windows tool and everything works including sound, touchscreen, Bluetooth audio, etc.

It is ridiculously fast and the fastest android experience that I've ever had.

Great job.

Only problem that I have is that I am not able to delete any system app like youtube in order to install Vanced version of YouTube. Also since the system is not read write I cannot install Arise or Xposed. Although root works fine I still cannot rename anything in the /system folder. Used Root Explorer, Solid Explorer, ES file manager but nothing doing.

Any workarounds to this?

Thanks for a great experience.

Edit: Started reading the thread from the beginning and have found that in Nougat Builds a workaround for system r/w was to delete the system.sfs file but in the Oreo Builds there is no syatem.img in the Android folder and also if you try to extract the sfs file there is no system.img file inside

Edit2: Read the thread up to around post #1400 and also tried booting the last bleeding edge and it does boot on the Nomodeset option. Everything seems to be working like touch screen, audio, etc. I don't know where to go from here
[BLISS ROMS Development] Ealge0110:
It's unfortunately an known issue thatt the current root solution doesn't allow R/W to anything in the "system" partition, and he seems to be working on it...

For YouTube I'm using OGYouTube
[BLISS ROMS Development] arifqur:
Tried using the USB installer made via Rufus and installed Bliss on an ext4 partition and booted straight into Bliss but Google sign-in could not be completed. Booted back into Windows and was surprised to see that the System partition was extracted into a folder.

However, I could not boot back into Bliss. After mounting the X: drive via command prompt I found out that there was no grub installed.

Oh well still love how this Android performs. Gonna keep it.
[BLISS ROMS Development] stdiopt:
Here's my solution for that:

In a linux system:

I create a image system.img

e.g:

* truncate --size=2500M system.img

* mkfs.ext4 system.img

* mount system.img somefolder

I mount system.sfs

* mount system.sfs someotherfolder

finally copy files maintaining permissions etc:

cp -arp someotherfolder/* somefolder

and leave the system.img instead of system.sfs where it was installed..

---------

Has anyone managed houdini/compatible arm layer to work? i tried to run enable_nativebridge from /system/bin but i think the houdini.sfs for 8.1 doesn't exists
[BLISS ROMS Development] tvcat-xda:
Hi, how is the gaming performance if it run in virtualbox?

Thanks.
[BLISS ROMS Development] Eagle0110:
However, after doing so, during booting up it will stuck at "Detecting Android-x86... found at /dev/nume0n1p3" and not progress any further.

Do I need to modify anything in grub for this to work?
[BLISS ROMS Development] stdiopt:
Mine worked with no issues and writable system.img

My grub entry:

menuentry 'Bliss' {
search --file --no-floppy --set=root /OS/Bliss/kernel
linux /OS/Bliss/kernel root=/dev/ram0 androidboot.selinux=permissive quiet
initrd /OS/Bliss/initrd.img
}

My files:

/mnt/main/OS/Bliss$ ls -l
-rwxrwxrwx 1 root root 68719476736 Jun 17 12:13 data.img
-rwxrwxrwx 1 root root 1358870 Jun 11 00:13 initrd.img
-rwxrwxrwx 1 root root 7671488 Jun 11 00:13 kernel
-rwxrwxrwx 1 root root 1443139 Jun 11 00:13 ramdisk.img
-rwxrwxrwx 1 root root 2726297600 Jun 17 10:16 system.img

I have Bliss in C:\OS\Bliss hence the grub trying to find /OS/Bliss/kernel
[BLISS ROMS Development] Eagle0110:
Thank you so much for trying to help but unfortunately with your grup entries it still doesn't work on my SP4.

I have it installed in C:\AndroidOS so currently I have:

menuentry 'Bliss' {
search --file --no-floppy --set=root /AndroidOS/kernel
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet
initrd /AndroidOS/initrd.img
}

Originally I had (before creating system.img and exchanging it with system.sys):

menuentry 'Android-x86' --class android-x86 {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive sleep.earlysuspend=0 quiet DATA=
initrd /AndroidOS/initrd.img
}

I have all your files but also "android.boot", removing this additional file did not make it work.

Also, I installed with the automatic installer, would it have to do with that?
[BLISS ROMS Development] youling257:
mount your system.img ，ls -alZ bin/*，make sure these，

-rwxr-xr-x 1 root shell u:object_r:vdc_exec:s0 18852 2018-05-27 22:22 vdc
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 vmstat -> toybox
-rwxr-xr-x 1 root shell u:object_r:vold_exec:s0 770760 2018-05-27 22:22 vold
-rwxr-xr-x 1 root shell u:object_r:system_file:s0 152 2018-05-27 21:56 vr
-rwxr-xr-x 1 root shell u:object_r:system_file:s0 28584 2018-05-27 22:22 wacom-input
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 wc -> toybox
-rwxr-x--- 1 root root u:object_r:webview_zygote_exec:s0 14984 2018-05-27 22:22 webview_zygote32
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 which -> toybox
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 whoami -> toybox
-rwxr-xr-x 1 root shell u:object_r:wificond_exec:s0 347048 2018-05-27 22:22 wificond
-rwxr-xr-x 1 root shell u:object_r:system_file:s0 190 2018-05-27 21:56 wm
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 xargs -> toybox
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 xxd -> toybox
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 yes -> toybox
lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 zcat -> toybox

when you mount system.sfs，copy files to mounted system.img，do you use -arp or -afZ ?

I test copy file use -arp and -afZ，then ls -alZ file，-arp and -afZ no difference.

selinux context is important for oreo.

if you install oreo to ext4 partition，you can make system folder，mount system.sfs ，cp -afZ files to system folder，

keep selinux context !
[BLISS ROMS Development] Ealge0110:
Ah I used -arp...

What are the difference? Do I just need to create system.img again with -crz instead?

Thank you for explaining!
[BLISS ROMS Development] losl1946:
I want to test this rom and installed "android_x86_64-OFFICIAL-20171014-1217_k4.9.iso" on VirtualBox. It failed to boot and stuck on the boot image for several minutes and did nothing, help needed. Thank you !

SLo
[BLISS ROMS Development] losl1946:
It finally booted up to Android but when setting up the Android machine "setup wizard has stopped" popped up continuously and setup could not be carried on. Please help, thank you.

SLo
[BLISS ROMS Development] stdiopt:
this might help: http://man7.org/linux/man-pages/man1/cp.1.html

cp -ar would work

the goal is to clone the files/devices/fifos maintaining permissions, selinux context from system.sfs into the system.img, I believe rsync does that too (I wasn't aware of selinux context but i guess -a flag maintains that)

I'm using this iso (this is not a surface): Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180603-1620_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_sl.iso

My system.img content (odd that ? appears instead of context I guess my archlinux doesn't use selinux):

$ ls -alZ
total 220
drwxr-xr-x 17 root root ? 4096 Jun 11 00:17 .
drwxrwxrwx 1 root root ? 4096 Jun 18 17:27 ..
drwxr-xr-x 53 root root ? 4096 Jun 3 19:00 app
drwxr-xr-x 3 root 2000 ? 12288 Jun 11 03:17 bin
-rw------- 1 root root ? 3191 Jun 3 18:48 build.prop
-rw-r--r-- 1 root root ? 74747 Jun 3 17:49 compatibility_matrix.xml
drwxr-xr-x 13 root 2000 ? 4096 Jun 17 20:12 etc
drwxr-xr-x 2 root root ? 4096 Jun 3 18:33 fake-libs
drwxr-xr-x 2 root root ? 4096 Jun 3 18:33 fake-libs64
drwxr-xr-x 2 root root ? 12288 Jun 3 17:25 fonts
drwxr-xr-x 3 root root ? 4096 Jun 17 20:12 framework
drwxr-xr-x 7 root root ? 20480 Jun 3 18:50 lib
drwxr-xr-x 4 root root ? 20480 Jun 11 03:09 lib64
drwx------ 2 root root ? 16384 Jun 11 00:14 lost+found
-rw-r--r-- 1 root root ? 2946 Jun 3 17:49 manifest.xml
drwxr-xr-x 3 root root ? 4096 Jun 3 17:32 media
drwxr-xr-x 56 root root ? 4096 Jun 3 19:01 priv-app
drwxr-xr-x 8 root root ? 4096 Jun 3 17:32 usr
drwxr-xr-x 8 root 2000 ? 4096 Jun 3 18:56 vendor
drwxr-xr-x 2 root 2000 ? 12288 Jun 3 18:48 xbin
[BLISS ROMS Development] Ealge0110:
Wow that totally worked!!!

I have successfully booted into the system and R/W to system partition is now totally working!!!

Thank you!

By the way you made me getting my first taste of using Linux terminal, for that I am grateful!!! :D

---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------

Thanks! That made sense! Got it working with just -ap

Thanks! That made sense! Got it working with just -ap on Linux Mint :D
[BLISS ROMS Development] arifqur:
Guys I have no experience with Linux. After seeing the posts by [MENTION=3763572]stdiopt[/MENTION] on how to create the system.img from system.sfs, I installed PeppermintOS on a virtualbox and from there I tried to follow the istructions. I managed to make a 2500MB system.img and mount it but mounting the system.sfs was a pain. Once I managed to mount both these in different folders the copy command drove me nuts. However, I did manage to get the copy command working but then it said permission denied.

Man sorry to bother you but is there a detailed tutorial for idiots like me that I can follow?

Thanks

Edit: Just now used sudo su before the copy command and it seems to have worked. Not totally sure(BTW used cp -arp)

Edit2: Replaced the Grub entry from/android.boot to /kernel and replaced the system.img and deleted system.sfs and voila it booted.

Whew! That took some serious head banging to get it to work.

Thank all of you guys. Finally have system as r/w in Bliss
[BLISS ROMS Development] Developer Anindya:
Hello everyone, I have a question regarding installation. Please read and I wold like to declare that I have experience with dual Booting on PC. My questions follow:

1) Using Easy BCD and a plane archive manager I was able to get Kali Linux installed into a new partition in my pre-existing hard drive. So will it work here too. The steps which I experimented upon are very simple--> Grab the ISO, Make a Partition of around 2-10GB, Paste the ISO there, Also extract it with any archive manager, Fire up EASY BCD, add a parameter for dual booting in the ISO section, Apply Changes, reboot.............. So my question is will this method work for bliss too>>>?

2) I have 3GB RAM and dual core 2.5 GHz proc. Is it sufficient>??
[BLISS ROMS Development] arifqur:
Anybody here knows of a Xposed installation guide for Oreo?

The guide in the OP does not work on the new Bliss 10.0
[BLISS ROMS Development] stdiopt:
Just a quick note having android.boot or kernel doesn't really affect much, is just a way that grub uses to search the proper filesystem, meaning:

search ... --set=root /AndroidOS/android.boot it will look for a partition that contains /AndroidOS in its root and a file android.boot, i just used kernel because it was a file that was there, it could be anything in that folder
[BLISS ROMS Development] electrikjesus:
The next releases of Bliss OS will include fixes for system r/w, su, and a few more things. We decided to go back to the old method of packaging the system.img inside the system.sfs (as did Android-x86 project)

Also, anyone asking about Google Play services crashing should know better now that I have that info posted on every update post for the last few months, as well as the downloads post on the OP. This means that I give you all permission to troll anyone still asking that question.
[BLISS ROMS Development] avalanche99:
Hi.

I can't find an answer in the whole thread, so I ask. If this question was already answered I apoligize right now.

How can I update bliss rom?

I've got an SP4 with this built installed:

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180317-1639_k4.15-sb-ga-jwd_m18.1.0-devel_w09_surface-pro-4.iso

And now I would like to try this new built without installing bliss again with the installer.

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180602-1820_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_sp4.iso

How can I do this?

And a second question, do the nighly builts include all the drivers needed for the SP4?

Kind regards

avalanche99
[BLISS ROMS Development] WoltreX:
I shared a toolbox for BlissOS. It can help you for edit BlissOS. In order to solve various problems, i will also add some solutions to the next versions.

BlissOS/Android PC Toolbox

-The most important issue with BlissOS is that disk access is not possible. With this tool users can solve the problem in part because they can create data.img with personal data. :fingers-crossed:
[BLISS ROMS Development] arifqur:
Network speed meter apps are not working on the March 8 Nightly that I am using. They are all stuck at 0.

Sometimes they start working after a reboot untill the next time that the PC is restarted. Can't find any rhyme or reason.

Any ideas guys?
[BLISS ROMS Development] stdiopt:
Any word on native_bridge? (running arm apps in x86) tried to setup manually but might depend on android-x86
[BLISS ROMS Development] arifqur:
Great. Just when I learned my first Linux commands and other stuff to make an img file from sfs, you decide to make it r/w.

Just kidding.

Thanks for all the hard work
[BLISS ROMS Development] Ealge0110:
What is your device model? I have the same problem on my SP4, I blamed the supposedly inferior Marvel Wi-Fi card but maybe it's a software issue after all...
[BLISS ROMS Development] electrikjesus:
Nice!! Would you mind if I mention and link to this tool in the second post?
[BLISS ROMS Development] electrikjesus:
We don't include Android-x86's native-bridge, we added Intel's Houdini, enabled by default for all compatible devices. It does require a compatible processor though... Most Intel's work, most AMD's work. Haven't tried any ARM apps on Snapdragon or Atom though
[BLISS ROMS Development] arifqur:
I have a HP Specter 360 15T i7 Quad core 8550U.

Yeah it does work like very rarely after a reboot.

Tried so many Internet Speed Meter Apps.

Funny thing is that I was downloading a torrent using the FLUD App and in its UI it shows the current Download speeds.

Hope somebody figures this one out. Very troubling for my OCD
[BLISS ROMS Development] arifqur:
I failed to mention in my previous posts that after converting system.sfs to img format I was successfully able to update the su binary
[BLISS ROMS Development] Ealge0110:
I can confirm this too, updating SU binary worked prefectly after converting system.sfs to img format.
[BLISS ROMS Development] arifqur:
wow! Dude you are a genius. Managed to install Arise on my Bliss x86 and get it working simply by copying and pasting the extracted contents from the arise folder to /system.

BTW any such solution for Xposed?

Have not tried the Toolbox as yet.
[BLISS ROMS Development] WoltreX:
There is no xposed framework for x86-64 Oreo systems. If someone can build it, i can add a option in toolbox for install to system.
[BLISS ROMS Development] arifqur:
Yeah I know. Was googling for it like forever.

Well we can still hope and keep our fingers crossed.
[BLISS ROMS Development] electrikjesus:
!!New Bliss-x86 v10.1 PC Beta - rc1 Release!! - 06/21/2018

It's that time again folks. And with this build, comes a bunch of updates and fixes. And with those, we are getting closer to a build I would call stable. Most of the details can be found below in the Updates/Additions or the Changelog.

Have FUN!!

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180619-2059_k4.16.14-bliss-ipts-ga_18.1.0-devel_w14_dev-kernel.org.iso - This contains firmware for all current devices included in kernel.org, and DOES NOT INCLUDE GMS OR OPENGAPPS - THIS BUILD INCLUDES FDROID/MICROG

Changelog-Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180619-2059.txt - This is the recent changes since last build

Updates / Additions:

Kernel 4.16.14 - reworked for all devices

Moved to old way of packaging the system image. (for root to work, you must extract the system.img file from within the system.sfs, then delete the system.sfs file)

Rooted with Superuser. Access Superuser settings from Settings>Users (R/W works if you extract system.img, read above)

Substratum Service mode enabled (now fully working, but reboot required after you build/enable a theme. select from Settings>Display>Advanced>Themes)

Latest build doesn't include OpenGapps or Google's GMS. It includes Fdroid/microG (no chromecast support or support for apps that require Google Services)

A few fixes and updates for Bluetooth

Fixes for some devices that didn't boot right

Using Android-x86's newest updates to bootable/newinstaller (this comes with a new UEFI grub menu)

Maybe more... I've been busy

Bugs / Issues:

Bluetooth issues still exist on some devices

you will get Play Store and process crashes until WiFi is connected. Just dismiss these for now. Once connected to WiFi, things should work properly. **ONLY ON OPENGAPPS BUILDS**

Sound or keyboard might not work, try to boot using the secondary modprobe option

Expect more. It's only a beta release. Report your issues, but make sure you SEARCH the thread first to make sure it hasn't been answered. And post logs too (I know, WTF are logs anyways??)

As always, check the Bliss download site for the newest builds. The rest are all on AFH as a backup archive. Hope you all enjoy this one :D

https://downloads.blissroms.com/BlissOS/bleeding_edge/
[BLISS ROMS Development] jcrompton:
Thank you for pursuing this area

My main hope is to be able to use a PC (my main larger screen device vs my wife's large ipad) for watching videos / TV / movies specifically using Terrarium TV

Has anyone had any luck doing this? I have been getting black screens with playing video on generic Builds

Thanks!!!

---------- Post added at 09:26 PM ---------- Previous post was at 08:51 PM ----------

I tried to boot this latest version on my

Dell Latitude E6410

and the Live Boot only cause the PC to reboot almost immediately

How to troubleshoot ?