yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ElfinJNoty:
Secure boot must be disabled, bitlocker must be disabled.

That error is reporting that the bootloader is trying to point to a disk location for the kernel to load, but the disk is not accessible.

Please verify the above

[MENTION=3837376]hawksneo[/MENTION] [MENTION=1961018]zummy[/MENTION]
[BLISS ROMS Development] MagicAndre1981:
thanks, this version now works faster and I can boot directly without selecting nomoderest, but I till can't connect to any wifi on my Toshiba Encore 8.
[BLISS ROMS Development] electrikjesus:
Can you please run a CPU-Z report and see if Bliss even detects your wireless adapter?
[BLISS ROMS Development] MagicAndre1981:
ifconfig shows the wlan0 device and driver brcmfmac is used. The issue with the Baytrail tablet is that it has x64 CPU, but 32bit firmware, so 64Bit Linux doesn't boot without hacks ( I currently have no Linux running to ,modify the ISO for Atom so I can't see if Ubuntu 18.04 detects Wifi).

For Windows 10 x86 I use this driver. Maybe the bin/txt files help you a bit.
[BLISS ROMS Development] Valeron2004:
Can I use dedicated graphics in bliss os v10.1?

My Laptop specs are:

Windows 10 (build 17134)

Intel Core i7-4700MQ processor

6GB DDR3 Ram

Intel HD 4600 graphics (Integrated)

AMD Radeon R7 M265 graphics (Dedicated)

I really want to play some games on high settings was thinking if I could use the AMD card. Pls help.
[BLISS ROMS Development] danishhot:
I've installed the stable version in my windows 10 PC. Like Remix os, there is no sound from the speakers or earphones. I have looked for a solution when I was using Remix os, however there was nothing I could found (May be I was not looking correctly). As Bliss support is active, that's the reason I came to this thread. Plz let me know if there is any fix for the no sound issue.
[BLISS ROMS Development] bfmetcalf:
Try one of the nightly builds. 7.1 is no longer active developed.
[BLISS ROMS Development] Anonturtle:
Wait I'm stupid I just read the tool page and it says choose a partition, but I'm not supposed to have to format any partitions? Do I create a partition on my Windows drive?

Keep getting this error when I try to install it to the same drive I have Windows installed on

-Boot Directory is Already Exist

==============Revert Installation==============

-Cleaning up Bliss Directory ... C:\AndroidOS

===Removing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S

Error output:

The directory is not empty.

-Remove Android UEFI Entry

-UEFI: -1

-Cleaning up Bliss Directory ... Z:\EFI\boot\

-UnMounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /D

==========================================

However I was able to install it to a usb flash drive but it just hangs at the text android logo and then reboots without ever actually getting into android, I have secure boot disabled and bitlocker isn't currently enabled on any drives that I have plugged in rn, so I'm at a loss as to what the problem is
[BLISS ROMS Development] kypor:
I also get this error on my Asus 102HA. Not sure what is causing this. :(
[BLISS ROMS Development] ElfinJNoty:
The output from the installer is telling you that there is already an EFI entry for AndroidOS. You should have no problem installing to the same drive as your Windows installation. As a matter of fact, we suggest to do that.

"Error output:

The directory is not empty"

Should be resolved by using the "Cleanup Android" button in the installer. Do that first, then select your .iso, your C: drive, data.img size(12gb is always what I use for testing), then click install.

You should NOT be using the Windows installer to install onto a USB as the target location. That defeats the purpose of the Windows installer. Use a local drive as target(again, suggest C: or whatever your Windows installation disk is named)

You do not need to create partitions when using Windows installer.

Just make sure that there is enough free space on your installation location(C: or whatever) to accommodate for 4gb of space for the OS + whatever size data.img you have selected

---------- Post added at 11:31 PM ---------- Previous post was at 11:29 PM ----------

Here is a video walk through of the entire process, start to finish:

https://youtu.be/0UkPyYfj0xA
[BLISS ROMS Development] Anonturtle:
Edit: So I did what you said and the install worked but it never boots into a gui it gets to the command line and then either freezes or is really slow and reboots on its own

Ohhh, okay thank you so much for the quick reply! I will try these steps and see if it works
[BLISS ROMS Development] Ealge0110:
Mind to clearfy which IPTS frameware version is the default one that comes already with the ROM after install?

Wondering if I till need to replace the frameware files on SP4.
[BLISS ROMS Development] Eagle0110:
Nevermind, touch screen does not work without manually exchange frameware files.

However, before that is even a problem, I can confirm, that as mentioned above, it gets stuck at "booting Android" while booting with system.img instead of system.sfs. Tried both using the tool box to unpack and repack system.sfs to system.img (with and without adding SP4 IPTS frameware), and to manually create system.img and copy into it on Linux, neither worked, and both got stuck at the same point.
[BLISS ROMS Development] electrikjesus:
Here is the post that details the process. And it has been proven to work https://xdaforums.com/showpost.php?p=76896155&postcount=2107
[BLISS ROMS Development] Ealge0110:
Of course that is exactly the process I followed.

But the biggest problem with this build is not the touch screen, rather it is that it doesn't boot up with a system.img repackaged from system.sfs, with or without IPTS frameware added, done manually or using the Android toolbox.

It always stuck at "starting up Androud" with system.img.
[BLISS ROMS Development] electrikjesus:
For goodness sakes, why are you repacking?

Just extract the system.img from the system.sfs, and use a root explorer from within Bliss OS
[BLISS ROMS Development] peterandrewd:
Touchscreen not working on Surface Pro 4 on latest 10.1 beta build.

But it works with a previous build 20180317-1639_k4.15-sb-ga-jwd_m18.1.0-devel_w09_surface-pro-4.iso

Everything else works fine except that.

Thoughts?
[BLISS ROMS Development] Ealge0110:
By repacking I meant to repack with the Android toolbox, I of course tried to just extract the system.img from system.sfs manually in Linux like exactly what I did to get R/W working in the Beta 10.0 build, and no it does not give any different result.

For goodness sakes, why are you assuming your fan and your supporters and your volunteer beta testers are all idiots? You know, maybe they are actually trying to help? Like, maybe they are?
[BLISS ROMS Development] peterandrewd:
Also want to say a massive thank you to the devs for this ROM.

Im going to stay on the 20180317-1639_k4.15-sb-ga-jwd_m18.1.0-devel_w09_surface-pro-4.iso build seeing as the touchscreen works on the Surface Pro 4 with that build.

But I look forward to newer builds where hopefully the touchscreen works again.
[BLISS ROMS Development] DoughMucker:
Thanks for the instructions. Just to clarify some things that may help others as I also had some trouble initially:

-Use 7-zip to first extract the Bliss.iso and then a second time to extract system.img from the resulting system.sfs. Then delete system.sfs from the AndroidOS folder and replace it with system.img. Then boot into BlissOS for the rest.

(My original instructions were to use the BlissOS/Android PC Toolbox to extract the system.img file. The author has since removed the tool. I'm leaving the following only for reference... (Extract the system.img file from system.sfs in Windows using BlissOS/Android PC Toolbox (option 1). I don't think it's linked in the OP yet, so search this thread for the link. The Toolbox creates the system.img file in the "in" folder where you placed the system.sfs file. Ignore the system folder created in the "extract" folder.)

-The correct location to put the Surface drivers is:

/system/lib/firmware/intel/ipts

-Change the permissions of the files to 644.

-I used Total Commander to copy the files in android. I initially had trouble copying the files from my SD card; it turns out I had to move them to my internal storage (such as Downloads) first and then copy them to /system/lib/firmware/intel/ipts.

Bliss is working quite well. I'm looking forward to Jake Day and others updating the Surface drivers so this device works even better.
[BLISS ROMS Development] Ealge0110:
When you were extracting the system.img file from system.sfs, which option did you choose in the BlissOS/Android PC Toolbox? Did you chose "unpack system.sfs" and then "repack system.img"? Or did you choose another option to extract the system.img?

Also, which version of the BlissOS/Android PC Toolbox did you use? Did you use 1.1 or 1.0?

I think I took the same procedure you described, but after I replaced system.sfs with system.img it gets stuck at "starting Android..." during boot on my SP4...
[BLISS ROMS Development] DoughMucker:
Option 1 and nothing more. You don't need to repack system.img. the tool created and extracted system folder, but it also creates the system.img directly. I'm not at my PC now, but if I recall correctly, it'll be in the same folder that you placed system.sfs.

Version 1.1
[BLISS ROMS Development] electrikjesus:
I don't think I assumed any such thing, just making sure we all are on the same page
[BLISS ROMS Development] astroganger:
I think you cannt delete. Sys with. Img... This which cause the android to stuck
[BLISS ROMS Development] mikekoz:
I am not sure where to post this, so I will do it here. I picked up a used Surface Pro 3 a few month back. One of the reasons I picked it up was to install Bliss Os x86, or some other Android based rom, and dual boot it with Windows 10. I bought the Surface thinking it would have a lot of developer support. Is there a specific rom here I should use on the 3? I have tried several of the Android 6, 7, and 8 roms, and they all have problems. Some of the the Oreo ones do not boot, all I get is a black screen. I tried one of the newest Oreo ones and it booted, but had issues with the touch screen. The 7.1 roms will boot up, but the screen also has issues. The auto rotate does not work with any of them, but I can live with that. When the tablet display goes to sleep, the device locks. On the Android 7 roms, the screen will stop functioning all together after 5-10 minutes. Do you see a pattern here? ;p). I also tried the rom that was made for the Surface Pro 4. Guess what did not work!!?? What is it about the Surface Pro 3 that makes these Android roms misbehave? Is there something unusual about the displays that makes the Android drivers just not like them?
[BLISS ROMS Development] VMolina141:
[MENTION=928479]electrikjesus[/MENTION] Hey! I don't know if i can ask this here, but i'll try! From all the Adroid-based OS's out there i LOVED bliss the most, but for some reason i can't open "Arena Of Valor" :c (This game is the only reason why i am looking for a OS like this) it just keep's crashing, doesn't even try to launch, why? Is Bliss not for gaming? AoV isn't supported? It's a setting? I did something wrong? but most important, can you help me? i'm using Bliss v7.2 (Nougat 7.1), thank you
[BLISS ROMS Development] Lostwon:
Booted on Chromebook via USB wifi connection resets computer

Hello, I made a fat32 usb drive and coppied initrd.img ramdisk.img kernel, and system.img (which I extracted from system.fsf with unsquashfs) to /android/ I then created a data.img in /android as well. This is what my grub menu entry looks like

insmod part_gpt

search --no-floppy --fs-uuid --set=root F89A-A2E8

echo	'Loading BlissOS ...'

linux /android/kernel root=/dev/ram0 SRC=/android androidboot.selinux=permissive quiet DATA=

initrd /android/initrd.img.

It boots, but says something like "Your internal device is damaged" I can get that to go away. When I try and connect to wifi, I hit connect and the computer restarts.

While I can move the cursor around the screen, I cant click anything. I can navigate with <tab> and <space>.

Any ideas as to the problem?

My Hardware:

Samsung Chromebook 3 (Celes) there are two different Samsung 3's.

I am dual booting chromeOS and Gallium.

I put the grub menu entries in the grub loader for Gallium.

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org.iso

Can i insmod the drivers from galliumos into my Bliss kernel?

I can boot Bliss and access tty1 and do it if its possible.
[BLISS ROMS Development] electrikjesus:
For the Chromebook support, you will want to use one of our builds that have the Gallium OS commits added (look for "ga" in the filename)
[BLISS ROMS Development] deshwasi:
anyone tried this on a xps18 running windows 10? obviously i would want the giant touchscreen to be working in Android
[BLISS ROMS Development] Lostwon:
Ohh thank you I loved the look of what I could see, can't wait to get it running.
[BLISS ROMS Development] electrikjesus:
This one includes the Chromebook commits ;)

https://downloads.blissroms.com/Bli...s-ipts-ga_18.1.0-devel_w14_dev-kernel.org.iso
[BLISS ROMS Development] xhamadeex:
Thank you for this amazing rom

I am currently running it on my surface pro 4 and it works great!

However, It seems that Netflix and prime video have a maximum resolution of 480p. Is there a way to change that?

Furthermore, it seems that touch screen stops working after some time. Is there a way to fix that?

Thanks!
[BLISS ROMS Development] xhamadeex:
Thanks for the instructions.

Is there much of a difference between the latest build and the SP4 build? Should I delete my SP4 build and install the latest build? Thanks!
[BLISS ROMS Development] uright:
I'm having the same issue with my Surface Book Gen 1. Touch screen works for a couple minutes and stopped registering after awhile. I'm not sure how to export any logs to troubleshoot.

Also, I just received the Surface Go today. Will try to install Bliss OS to test out the compatibility. Thanks for this awesome rom!
[BLISS ROMS Development] DoughMucker:
I don't know what the SP4 build is, so can't say. But I never delete my old install until testing the new one out for a while. I duplicate the entire AndroidOS folder to AndroidOS-LastWorking and then replace the system files in AndroidOS with the new ones. Only after testing for a while do I delete the backup folder. It makes it easy to go back to the previous install.
[BLISS ROMS Development] electrikjesus:
We got a review by DistroTube, and not too shabby (although he mentioned he wanted a more PC like experience, and it was a tap away the entire time!!)

[YOUTUBE]https://youtu.be/v2QSgY5vva4[/YOUTUBE]
[BLISS ROMS Development] xhamadeex:
Thanks for the reply!

Does your touch screen stop working after a while, and does Netflix or prime video stream at 480p max?

Cheers!:cowboy:
[BLISS ROMS Development] coolmaster121:
So I got a few HP Stream 7 tablets with Win10 on them. Was wondering if its possible to run BlissOS on them.
[BLISS ROMS Development] Blubster:
I don't know about the touchscreen issue, but regarding 480p in Netflix, I think it is unavoidable, we can't get widevine lv1 drm with this rom (or any x86 custom rom actually) because each device has to have drm keys installed by the manufacturer, which we cannot do obviously...

And we can't fake drm keys unfortunately.

I think the situation is pretty much the same for any x86 roms, I tried android-x86, bliss, remixos and Phoenix os, widevine is missing every time and I remembered the oneplus 5 "issue" with widevine, devices had to be sent back to oneplus to get widevine installed or get it upgraded. It was not a simple process of just installing an update anyone could do...

So I don't think you should expect any miracle on this front. ?
[BLISS ROMS Development] peterandrewd:
Don't mean to butt in but have to say, personally I can watch and stream Netflix on all my other devices so the Netflix 480p issue personally doesn't bother me, as long as the touchscreen issue is fixed using the above driver, etc, then I'm 1 happy man.

Please keep us updated on the touchscreen though, if it stops working or not :)
[BLISS ROMS Development] electrikjesus:
What are you even talking about? We use Intel's widevine DRM libs so all devices that have hardware support can enjoy DRM material. Netflix works great on my ThinkPad, SurfaceBook, Desktop, etc...
[BLISS ROMS Development] DiogoSilva48:
You get L1 or L3?
[BLISS ROMS Development] imran.zee:
Surface Go

has anyone managed to get this installed and working on a Surface GO? I could boot into android however could not clear the initial setup phase since it kept crashing no matter what option I select from the menu. (Options were Setup as a new device or Backup from Old Devices, Use Google Account etc). The touch screen was working though.

I also tried installing the Vanilla x86 version from Android x86 Open project however there are no wifi drivers for the Surface Go on it.

Any assistance to get this going on my Surface go is much appreciated.
[BLISS ROMS Development] osbaldov:
I'm using a Asus t100a and having trouble with sound. I get audio but when connected to headphones it plays through both headphones and speakers.
[BLISS ROMS Development] electrikjesus:
Not sure, I would have to check the source for that
[BLISS ROMS Development] DiogoSilva48:
You can use the DRM info app like on the screenshot I'm attaching.
[BLISS ROMS Development] electrikjesus:
Could you also please send a screenshot of the OpenGL section in Settings>About Phone?
[BLISS ROMS Development] DiogoSilva48:
The other screenshot was on my phone.
[BLISS ROMS Development] xhamadeex:
Thank you for responding.

I tried prime video and Netflix and they both output a maximum resolution of 480p.

I attached the required screenshots.

Let me know if you need anything more I am happy to support this amazing project.

Cheers!:)
[BLISS ROMS Development] electrikjesus:
OK, the one thing we should note here is what Mesa version we're also using. 17.3.3 in this case. I'll see if I can post something using mesa 18.1.0 later to see what differs
[BLISS ROMS Development] xhamadeex:
Thanks for your help! Let me know if you need me to test anything. By the way I don't know if this makes a difference but I am running the OS using an external hard drive.

Cheers!
[BLISS ROMS Development] peterandrewd:
Used the Android PC Toolbox to install latest 10.1 build. Boots up fine qnd everything else OTHER than the WiFi work fine.

The WiFi just won't work. Keeps automatically shutting off (the on/off toggle button).

Won't search for networks and just doesn't recognise the WiFi.

Surface Pro 4 with the 'ipts_firmware_v78' firmware files installed into the lib/intel/ipts directory.

Even the touchscreen now works on that build with the ipts_firmware_v78 files.

Now its just the WiFi not working.

Prior to this, the WiFi worked on another build I had installed. WiFi works in Windows so its not my connection...

Any ideas please?
[BLISS ROMS Development] peterandrewd:
Kinda annoying to say the least.
[BLISS ROMS Development] vaynefox:
Can I install this on virtualbox? I kinda like to try it and at the same time I would also like to use it to test some of my apps....
[BLISS ROMS Development] peterandrewd:
Can someone please help me with my WiFi issue!? Geez.

Im frustrated asf. Been trying things ALL DAY to get it to work
[BLISS ROMS Development] peterandrewd:
I tried being patient, but find it awfully hard to believe that no one can even point me in the right direction with the WiFi connectivity issues I'm having on the latest build (see previous posts).

Here's a more detailed explanation of the issue.

Using the Android BlissOS Toolbox, I unpacked the system.img, added the v78 touchscreen firmware drivers into /intel/ipts directory then repacked the system.img and kept both the system.sfs and system.img in the AndroidOS directory, otherwise it doesn't boot into BlissOS.

So the touchscreen works...but there is no wifi connectivity at all. Turning it on doesn't do anything, it just toggles back to off automatically.

Doing the same process without adding the v78 touchscreen drivers, the wifi works but the touchscreen doesn't...

So can someone PLEASE help me to any degree!?
[BLISS ROMS Development] lastnikita:
Hi there, I would love to get support for galaxy book, especially the wifi issue.

I'm no linux guru but I can help by providing remote access or logs, or whatever is best suited.

If any good soul would like to chime in, please do =)
[BLISS ROMS Development] uright:
I'm experiencing the same issue. I loaded all of the surface rom (pro-4, pro 2017). The touch screen works along with keyboard and trackpad. The wifi doesn't work though.

I think Surface Go is using Qualcomm Atheros QCA61x4A. Does anyone know if there's a driver for this wireless adaptor?
[BLISS ROMS Development] imran.zee:
Yeah, I tired both the nightly builds for the surface pro 4 and the stable builds too of bliss OS. While the stable build refused to go past the setup stage due to the crashes, I got the nightly rom to get past the initial screen although it reported a bunch of errors. The surface keyboard, track pad, Bluetooth, touchscreen and even the USB C port worked. Heck the power on/off and volume buttons were functional too......just not the wifi. I am no expert in android, but turns out that "ath10k" drivers have to be added to the kernal for the wifi to work, unfortunately I dont have any expertise in this area to get this done. Hopefully the devs can help here.

This is a solid device to have android on, seems like a perfect pixel c replacement and cheaper too.
[BLISS ROMS Development] peterandrewd:
I have the Surface Pro Marvall wireless linux drivers...just need them compiled into the rom
[BLISS ROMS Development] peterandrewd:
Don't hold your breathe. Support seems virtually nonexistent.

Devs tell you to do a search... and then when you do, half the time you don't find your exact answer, and when you do, something else doesn't work. THEN when you ask dor support or post for advice... you don't get replied to.

Best off trying PhoenixOS mate. Updated more regularly.
[BLISS ROMS Development] MagicAndre1981:
ok, I hacked the Ubuntu 18.04.1 ISO with the script to get it bootable on the tablet.

It uses brcmfmac in driver version 6.10.197.71.

Under lib/firmware/brmc I see a lot of bin/txt files. Try to get them from the Ubuntu ISO and put them into your Bliss ISO and I'll test it again.
[BLISS ROMS Development] imran.zee:
WiFi fixed on Surface Go

I found a solution to the WiFi problems on Surface Go but the solution requires a file "board.bin" to be downloaded. XDA wont let me link to the site nor does it allow me to upload the file (just 8KB), how do I post the solution?
[BLISS ROMS Development] peterandrewd:
FINALLY figured out how to keep the touchscreen working on Surface Pro 4 build!

Typing this right now through the OS using the touchscreen. 15 minutes in and still responding.

---------- Post added at 03:22 AM ---------- Previous post was at 02:42 AM ----------

Almost an hour in and touchscreen still working properly.

If anyone needs a how-to, let me know.?
[BLISS ROMS Development] xhamadeex:
Great!

Please let us know how you did it!
[BLISS ROMS Development] peterandrewd:
Nah, I change my mind ?

I figured it out for myself, and took the time to do so...so I'm sure others could devote time to figure it out too.

No one wanted to help me or answer my posts when I had queries and issues, so people get what they give (or don't give).

People should answer next time ?
[BLISS ROMS Development] xhamadeex:
LOL.. I believed you for a while.
[BLISS ROMS Development] electrikjesus:
For a thread I respond to daily just about, I find your statement quite rude.