yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] mike.danny:
Hey there,

I've been searching for some time for a replacement OS for Remix OS which I still use as a daily driver for playing Android games on laptop and I've given a shot to your latest build. When I've booted it live with wifi connection everything was ok. I was able to play my favorite games. Then out of curiosity I've tried to install it on an ext4 partition on my custom built desktop PC with only wired connection. The installation finished ok but It couldn't connect to google servers although the browsing was Ok.

Is there something I can do to get connection to google servers over wired internet?
[BLISS ROMS Development] electrikjesus:
Try it this way:

setparams 'BlissOS 10.1 Live' 'Live' 'quiet'

shift 2
savedefault
set root=$android
linux $kdir/kernel root=/dev/ram0 androidboot.selinux=permi\
ssive $src SETUPWIZARD=0 $@
initrd $kdir/initrd.img

And yes, just hitting "e" when grub shows will not save the changes, but if you setup a data.img on the USB drive you are booting live from, you should be able to only enter it once and be done with it. Otherwise, live boot is not persistent
[BLISS ROMS Development] electrikjesus:
Seems silly, but make sure your grub entry contains a SRC=

Hit me back and let me know...
[BLISS ROMS Development] Luelu:
What happened with the site?? :(
[BLISS ROMS Development] electrikjesus:
It's back up. just waiting on ssl for the https ;)

http://www.blissroms.com/

http://downloads.blissroms.com/Bliss/Official/x86/bleeding_edge/

and a mirror now too:

https://sourceforge.net/projects/blissos-x86/files/Official/Bleeding_edge/
[BLISS ROMS Development] 4r44444:
Ok... thanks... I edited the file on USB stick so it will save it permanently.

Still tablet is rebooting when hitting live boot :/
[BLISS ROMS Development] ghembuls:
Boss,

What this stand for? "k4.9.54-ga-px-ts-ax86"

4.9.54 is the kernel, but what about the other term?

Sorry, noob question.
[BLISS ROMS Development] electrikjesus:
The added commits on top of that base kernel branch. GA - Gallium patches, PX - Patches from Phoenix OS, TS - Some silead touchscreen commits - AX86 - Updates from Android-x86 kernel
[BLISS ROMS Development] electrikjesus:
There something got messed up somewhere. I suggest starting over and double checking each step of the way
[BLISS ROMS Development] ghembuls:
I tried the bleeding edge Bliss 8 with 4.9.54 kernel, but encounter 2 problems.

1. The display and font, even at maximum size, still looks too tiny. Bliss 7, has better size and easy on eyes.

2. Failure to add google account, both in setupwizard or normal adding. It stuck on collecting info, as if it waits for WiFi connection. Cause it cant be skipped as in Bliss 7, the login screen cant move forward.

Although for a brief moment of testing, it felt more responsive than Bliss 7. With the same setting, and default apps. The memory consumption in default apps, was bit better than Bliss 7.

Will be waiting for future release from your team.

Thanks.
[BLISS ROMS Development] HeHeStephen:
You can simply go to settings, display, and display size. This corrects text and screen size issues once you are booted in.
[BLISS ROMS Development] mike.danny:
Here is my Menu.lst file content:

default=0
timeout=6
splashimage=/grub/android-x86.xpm.gz
root (hd0,0)

title BlissOS 10.1
kernel /bliss-x86-10.1/kernel root=/dev/ram0 androidboot.selinux=permissive SRC=/bliss-x86-10.1 buildvariant=eng SETUPWIZARD=0 quiet DATA=
initrd /bliss-x86-10.1/initrd.img

title BlissOS 10.1 (Debug mode)
kernel /bliss-x86-10.1/kernel root=/dev/ram0 androidboot.selinux=permissive DEBUG=2 SRC=/bliss-x86-10.1
initrd /bliss-x86-10.1/initrd.img

title BlissOS 10.1 (Debug nomodeset)
kernel /bliss-x86-10.1/kernel nomodeset root=/dev/ram0 androidboot.selinux=permissive DEBUG=2 SRC=/bliss-x86-10.1
initrd /bliss-x86-10.1/initrd.img

title BlissOS 10.1 (Debug video=LVDS-1:d)
kernel /bliss-x86-10.1/kernel video=LVDS-1:d root=/dev/ram0 androidboot.selinux=permissive DEBUG=2 SRC=/bliss-x86-10.1
initrd /bliss-x86-10.1/initrd.img

I've edited the first entry that I use but still there is no connection to Google servers over wired internet, but browsing is fine.
[BLISS ROMS Development] electrikjesus:
As stated before, you are always able to define your DPI from grub also. Add this before quiet: DPI=xxx

Examples: DPI=160 , DPI=180 , DPI=220

Also found this for using the vga=xxx command, and we include vi editor in Bliss too: https://www.youtube.com/watch?v=SV8nVMNCw0k

[IMG="Veda mode resolutions"]https://i.imgur.com/uZwIZNb.png[/IMG]
[BLISS ROMS Development] ghembuls:
Uuughhh... yesshhh...!!! Will try this now.

Thanks boss... :good:
[BLISS ROMS Development] HF!!23:
Can't access download page any more
[BLISS ROMS Development] HeHeStephen:
That's weird. I have windows 10, Ubuntu and now this bliss ROM booting on my machine. But I don't load windows, can't see how that would be causing the audio issue. Would have to be Ubuntu. I found a workaround for now. If you boot android and have no sound, a regular reboot won't fix. But if you shutdown android completely and power android back up, it fixes the sound.

Everything is working perfect except there is a error system has stopped, but once you click close it dont. And if the ROM goes to sleep, you get a error that Bluetooth has stopped, even on or off. Click close and it don't reappear.

I noticed using YouTube, you can't drop the video to small version and multi task, not a huge deal though. Also if you try to use hiromacro from the play store, i can grant it superuser permission but it don't work. Also note even with root I can't change the build.prop, was going to add sf.hwrotation so I could get it to boot in my correct orientation.

Other then these noted exceptions, it a great ROM. Absolutely no lag on the games I play in android. Great job guys:
[BLISS ROMS Development] Guimenez:
i've tried the new "Bliss-v10.0-PC_Beta--OFFICIAL-20180202-2031_android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m17.3.3.iso" and now it doesn't stop on starting android, but it goes black.

I've tried all the options on the USB.

Is there anything i can do or log to anyone help me?

I've a "Toshiba ENCORE 2 WT8-B-102" with "Z3735G".

Thanks
[BLISS ROMS Development] greg_mp:
I keep on getting a "connection refused" on the blissrom website ...
[BLISS ROMS Development] electrikjesus:
there is no ssl yet, so use http instead of https ;)
[BLISS ROMS Development] electrikjesus:
Also... Thanks to [MENTION=5216756]jackeagle[/MENTION] , we now have Nightlies and Weeklies being built for x86!! For now, these will follow our manifest, so these are using Linux Kernel branch: k4.9.80-ax86-ipts-gal and Mesa branch: 17.3.3 (soon to be updated to 17.3.5)

http://downloads.blissroms.com/Bliss/Official/x86/nightly/
[BLISS ROMS Development] electrikjesus:
Out ftp is back to working order, so I'm uploading three builds now. The last two are with added commits for revenge pinning, and clear all button. and I'm trying to get the bootanimation to maintain its aspect ration while still being dynamically generated, but I'm considering giving up that fight, because I'm loosing... Anyhow, here are the build names:

Bliss-v10.0-Beta--OFFICIAL-20180225-1944android_x86_64_k4.9-ax86_m17.3.5.iso

Bliss-v10.0-Beta--OFFICIAL-20180225-2241android_x86_64_k4.9.83-ax86-ipts-gal_m17.3.5_rcnt_ba.iso

Bliss-v10.0-Beta--OFFICIAL-20180226-2112android_x86_64_k4.15.x-b-s-rt-jwd4-ys-ipts-2_m18.1.0_w07_ba2.iso (this one includes the ipts commits that one of our awesome users passed a link along for jack-daily's github. THANKS, hope it works. no conflicts with other i915 devices in my testing)
[BLISS ROMS Development] jthomas1987:
Cool, thank you for the updates. Downloading the newest nightly now.
[BLISS ROMS Development] bloodsand:
Help :) SP3

I am having trouble booting the new nightly "Bliss-v10.0-Beta--OFFICIAL-20180226-2112android_x86_64_k4.15.x-b-s-rt-jwd4-ys-ipts-2_m18.1.0_w07_ba2.iso" When I boot up and select android x86 it looks like it is going to boot, but just comes up with a command line. "detecting Android-x86... found at dev/sda4.

Surface pro 3 i7

I was running the Bliss-v10.0-PC_Beta--OFFICIAL-20180201-2214_android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m18.1.0-dev_w05

with no prob other than wifi timeout and no sleep.

Thanks
[BLISS ROMS Development] ilker4fun:
I tried all of last three builds on my galaxy book 10.6. But again no wifi and still inverted touchscreen and no sound. But I would like to thank you again and again for introducing new ideas. I like the new touchscreen calibration app which cames default. I hope someday,it will fix the inverted touchscreen problem.
[BLISS ROMS Development] trycatch:
Hello there, at least I think there should be an option to disable autorotation? (grub parameter, grub entry etc?)
[BLISS ROMS Development] ghembuls:
Bliss 10.1 On VMWare

VMWare setting same as Bliss 7.2

Iso

Bliss-v10.0-Beta-android_x86_64-NIGHTLY-20180301-0138.iso

System Addons

SuperSU binnary updated Hehe.. :D Yes, dont update it. Loosing root after shutdown. Sorry

LSpeed

Busybox 1.28.1

Failure

Apps which require actual WiFi connection, cause it cant be skipped (as Bliss 7.2 did) on virtual environment.

Viper4Android (Driver is installed but keep on asking for driver update & Permission is given)

Pros

Onscreen interaction is better, less lag and stutter.

Included rotation setting (orientation manager)

Display adjustment (Font & Screen size)

Responsiveness seems increased (Comparing with default Bliss 7 installation)

I will keep this version instead of Bliss 7, while waiting for improvements. Congrats to all involved developers.

Thanks @electrikjesus

Screen Capture Attached
[BLISS ROMS Development] dirtyreturn:
Does this mean 32bit builds too?
[BLISS ROMS Development] ghembuls:
There is an orientation manager included within the OS, you can locate it on home (included in latest nightly).

---------- Post added at 19:21 ---------- Previous post was at 19:19 ----------

From what I have installed, I dont think there is any 32bit version available. Maybe there is a setting to make the OS be read as 32bit, but so far, it is 64bit as it is.
[BLISS ROMS Development] electrikjesus:
I'll be building with the other kernel as well
[BLISS ROMS Development] electrikjesus:
Please see our website for details
[BLISS ROMS Development] bloodsand:
Nice, thanks :good:
[BLISS ROMS Development] xionbunny:
Hope the issue with wifi gets fixed soon otherwise, these builds are fairly awesome.
[BLISS ROMS Development] electrikjesus:
It would be helpful if you go a little more in depth on to what issue that is again, especially your specific device
[BLISS ROMS Development] xionbunny:
its the same issue that someone else had a few posts back, in VMware you cant complete the setup because of it, and apps that require wifi won't function, other apps that don't require it do work as normal, provided you manage to get past the initial setup that is. Though even then the apps that require wireless access to connect still won't its as if they don't see the internet at all.
[BLISS ROMS Development] grayhaze:
Using Bliss-v10.0-Beta--OFFICIAL-20180226-2112android_x86_64_k4.15.x-b-s-rt-jwd4-ys-ipts-2_m18.1.0_w07_ba2.iso the touchscreen still doesn't work on the SP4 unfortunately, but it feels like progress is being made. I've verified that all the driver files that need to be there are, but I'm wondering if the presence of the drivers for all MS IPTS devices at the same time is causing a conflict somewhere. One bonus of this build is that wifi now appears to be very stable, albeit lacking 5G for some reason. The screen orientation sensor also appear to work... but in reverse! Easily remedied using the orientation setting app though. Hopefully we can find the last missing piece of the puzzle with a bit more fiddling. Thanks for taking the suggestions on board [MENTION=928479]electrikjesus[/MENTION]!
[BLISS ROMS Development] electrikjesus:
I doubt that is the issue. I'm willing to bet it's a modprobe issue on init. Have you tried booting and adding AUTO_LOAD=old ?
[BLISS ROMS Development] naffis:
Can someone give me external download link for x86 (pc platforms)?

I try to download from the official website I got

"Network error"
[BLISS ROMS Development] ghembuls:
Official Site (All 64 bit version)

http://downloads.blissroms.com/Bliss/Official/x86/

AFH (32 & 64 bit version)

https://androidfilehost.com/?w=files&flid=136638
[BLISS ROMS Development] naffis:
Thank man! ??

I have been looking for days to download it
[BLISS ROMS Development] Aminux32:
Keep getting a splash screen with bluetooth error, i dont even use a wireless card on my desktop.

Also, since i´m using 1920x1080p the screen rotates to the left side and stays that way, can´t seem to find the option to rotate manually.
[BLISS ROMS Development] grayhaze:
Yes, and no difference unfortunately. It seems like the first touch on the screen triggers the orientation sensor, which causes the display to flip upside down. But no touches register on screen.
[BLISS ROMS Development] kypor:
How do edit init.sh or gain root?

Sorry if this has been mentioned but I could not locate any information. In short: How do edit init.sh or gain root?

I'm using the latest bleeding edge build of Bliss-v10.0-Beta--OFFICIAL-20180226-2112android_x86_64_k4.15.x-b-s-rt-jwd4-ys-ipts-2_m18.1.0_w07_ba2.iso which works the best with my Dell Venue 8 Pro 5830. However I would like to edit the init.sh file to see if I can hopefully get a few things working properly (rotation and sound). However using vi I cannot write any edits to init.sh as it is Read only. Is there a way to edit this file? Sorry I should mention that I did use vi as su, but still is Read Only by filesystem.

Thank you so much for the great work and support! And again sorry if this has been answered already.
[BLISS ROMS Development] electrikjesus:
Reformat data and run through setup wizard again, but do not choose to restore from a device
[BLISS ROMS Development] electrikjesus:
Use the terminal editor app, and type $ su before you edit. SuperSU should be able to mount as r/w
[BLISS ROMS Development] Aminux32:
I was using live mode usb, the only options are to introduce my gmail account and that´s basically the setup, after a few seconds i´m in the desktop screen with the issues i described.

Maybe i should try another version.
[BLISS ROMS Development] kypor:
Thank you for responding electrikjesus! I did use su and it still shows as read only. :(
[BLISS ROMS Development] electrikjesus:
I've had some issues with this. And on those installs, the best way around it is to extract the system.sfs to a /system folder and point grob to look there for system
[BLISS ROMS Development] pippideniro:
support for Chuwi Hi12 tablet?
[BLISS ROMS Development] electrikjesus:
Just about everything but the touchscreen works. I still have no IPTS devices to help in getting that working right
[BLISS ROMS Development] dark4m:
[MENTION=928479]electrikjesus[/MENTION],

Thanks for the great job with the rom appreciated bigtime.

I've tryed the android installer 1.2

to install Bliss-v10.0-Beta-android_x86_64-NIGHTLY-20180303-0110.iso

on my Lenovo win10 64bit-i5 intel hd graphics, legassy bios mode

it did the seccessfuly half way and stopped responding for more than 2 hours 2 times.

the android entry appeard in the boot menu, but when I select it it gowes to some message that says "no file found" or something like it.

so please if their any other installer tool that works with the new rom I'd appreciate it.

BTW I've installed PhoenixOS on the same laptop and it works just fine. but they have that anoying "beta relece for avaluation use only" message keeps coming out with my talkback screenreader and because of that its almost useless for a blind user like me.
[BLISS ROMS Development] electrikjesus:
Why would android_installer 1.2 work?? Can't you just use the installer we include?
[BLISS ROMS Development] dark4m:
I'm sorry if I only found the iso images, didn't find any included installer. If someone kindly post a link for that because I went through the main post and the only installer I've found talks about lecassy bios was the 1.2.

or my screen reader skiped it somehow

Thanks in advance
[BLISS ROMS Development] DigitalMD:
The installer is included in the ISO file. You can run it when you boot the ISO
[BLISS ROMS Development] 4r44444:
Maybe you can look what Android X86 Project did to get Touch working, their Oreo got Touchscreen working on Chuwi Hi 12.
[BLISS ROMS Development] electrikjesus:
We are all caught up to their changes, so it might be just a matter of time before the builds trickle down to you all.
[BLISS ROMS Development] kypor:
Thanks electrikjesus! However I looked around online and I cannot seem to figure out how to have grub look at the system folder. Everything I've tried doesn't work
[BLISS ROMS Development] DiogoSilva48:
Can someone help me please. This happens on all Android x86 that I try on my PC, including this one, I just don't know why. Only when I'm using UEFI, if I use legacy is fine.
[BLISS ROMS Development] dark4m:
I've used the easy installer it installed ok, on a UEFI booted laptop,

the problem this time is the grub boot menu to show android does not show on not even after I've installed the rom via bootable usb stick, I made sure to confirm the grub2 installation just to be 100% sure.

any advice on force pc not to bipass the OS sellection boot menu?

Thanks in advance.
[BLISS ROMS Development] chandraprs:
This OS looks interesting, but what about keyboard mapping? Is the Keyboard Mapping feature included in this OS? If no, then how can i play games with this?
[BLISS ROMS Development] lp894:
Can tell you this, I tried the most recent 8.0 nightly on a Lenovo X1 Tablet 2nd Gen (i5-7y57, 8gb DDR4 ram, 256gb SSD, Intel 8265 Wireless Adapter) doesn't even boot. Gets just past loading the Bluetooth drivers and looks like its going to start android then chops me. Going to verify I don't have any BIOS/Firmware updates or anything then try again

---------- Post added at 10:58 AM ---------- Previous post was at 10:14 AM ----------

Specifically fails on the x1 tablet after applying Intel dcc parameters completed
[BLISS ROMS Development] danishkhanjatoi:
keymapper implementing

openthos os x86 is pure open source and ongoing development it has

keymapper i am wondering is it possible to add this keymapper to bliss os x86 link rrmove space>> github com

/ openthos / oto _ packages _ apps _ OtoKeyboardMap
[BLISS ROMS Development] pastordeecat:
Dual boot on Ubuntu PC

I could really use some help please! Need simple instructions for a noob trying to dual boot both Bliss OS and Ubuntu (Linux Mint 18.2).

I have Bliss OS on a DVD and USB. Can't find anything and I don't know which set to choose on this site. Please help!!! Thanks
[BLISS ROMS Development] bfmetcalf:
If you used dd to write the iso onto the usb drive. Try to boot off of it and see if it boots. It should run live just like a linux distro would.
[BLISS ROMS Development] xionbunny:
Google play services do not see any internet connection in VMware, even after skipping the setup wizard with the SETUPWIZARD=0 command, as such any app that requires them to function will not connect to the internet either or function as they should, since you are unable to setup and update googles services. This still happens in the latest nightly build.
[BLISS ROMS Development] pastordeecat:
Live is not the problem

Thanks but running it live is not the problem. I'd like to actually install it on my hard-drive and then dual boot with Ubuntu on one partition and Bliss OS on another.

The problem with running Bliss OS live is (as stated above) it only saves your changes temporarily. And I don't know how to "create a data.img" using Linux. Otherwise that would be an option. If someone has suggestions on how to do that, I'd be grateful as well. Bliss looks great! I tried it out running as a live usb, but I'd like to install it permanent if possible.
[BLISS ROMS Development] electrikjesus:
Ok, it states from here: https://xdaforums.com/showthread.php?t=1974014

Step 2 – Creation of the actual EXT4.img

dd if=/dev/zero of=system_new.img bs=4k count=60000

Translation of the terms,

bs =blocksize, 4k= the size of the block`s which in this
[BLISS ROMS Development] kypor:
Sorry electricjesus but I still can't figure out how to boot the system folder. I tried converting the system.sys file into system.img but still cannot modify any files in system root.
[BLISS ROMS Development] bfmetcalf:
T create a data.img on Linux use the commands below

<code>

truncate --size= 3G data.img

mkfs.ext4 -m0 data.img

</code>

You can change the size to what you want to.

Can you post your grub.cfg?
[BLISS ROMS Development] electrikjesus:
Max file size on fat32 is small for a data.IMG. I use NTFS
[BLISS ROMS Development] hamzio7:
Hey guys...

I did everything as mentioned in the OP but i don't get to choose which OS to start...after reboot it boots the Windows... What should i do?

I tried with different ROMs too like CM13 and RemixOs but nothing changes.
[BLISS ROMS Development] lollyjay:
Assuming you have uefi then you need to install easyuefi (as in OP) and move AndroidOS to first position in boot sequence
[BLISS ROMS Development] hamzio7:
My BIOS mode is legacy...does this changes anything?
[BLISS ROMS Development] lollyjay:
Sorry I can't help. I always use UEFI. Maybe someone else can help.
[BLISS ROMS Development] hamzio7:
Ok thanks.

I hope someone can help me
[BLISS ROMS Development] lollyjay:
Just checking... did you create the 300mb partition for grub?
[BLISS ROMS Development] hamzio7:
Yes i did...and i did all the other steps...step by step...i even tried grub and grub2...
[BLISS ROMS Development] electrikjesus:
Are you able to install RemixOS or Android-x86 on your device?
[BLISS ROMS Development] hamzio7:
Yes i can install it and I already did...but i want this ROM...or any other AOSP but i can't run any one of them...i have bliss 7.1.1 and CM13

I can run them in LIVE MODE...BUT i can't boot to them when i install them on HDD

CM13 booting stops at Rooting Android X86

Bliss doesn't boot... It's reboot on first boot steps
[BLISS ROMS Development] electrikjesus:
You could try to replace the menu.lst in RemixOS dir with the grub entry for Bliss :

menuentry 'Windows' --class windows {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

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

menuentry '[GPU]Bliss-x86 xforcevesa' --class bliss {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa DATA=/AndroidOS
initrd /AndroidOS/initrd.img
}

menuentry '[GPU]Bliss-x86 nomodeset' --class bliss {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet i915.modeset=0 nomodeset DATA=/AndroidOS
initrd /AndroidOS/initrd.img
}

menuentry '[GPU]Bliss-x86 xforcevesa nomodeset' --class bliss {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa nomodeset i915.modeset=0 DATA=/AndroidOS
initrd /AndroidOS/initrd.img
}

menuentry 'Bliss-x86 DEBUG mode' --class bliss {
search --file --no-floppy --set=root /AndroidOS/system.img
linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive DATA=/AndroidOS DEBUG=2
initrd /AndroidOS/initrd.img
}

and then replace all the .img files in RemixOS folder with the ones from the Bliss iso. Make sure you also extract the system.img thats inside the system.sfs file and delete the system.sfs file if you want root ;)

I had to do that on one of my Lenovo machines that wouldn't take Android-x86 Grub for some reason.