yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ElfinJNoty:
That is unfortunate.

However, as this is a development thread, and labeled as "beta preview" status... And as clearly stated in the OP and thought all the pages of user posts & comments....

We ask that when providing any and all feedback about user experience regarding using our project:

1.Device details(there are several variants of the OneMix I'm familiar with, different hardware combinations)

2.the exact file name of the .iso file used for installation(there is a section in the 2nd post called "the instructions" that goes into detail about what these file names detail about the build used. Important to know what you've installed in order to see patterns of behavior and weather or not an issue faced is device specific, kernel related, etc.)

3.LOGS! Cannot stress enough how useful these things are! Allows us to see the universal language of code taking place, and avoids trouble of needing the user to be extra knowledgeable, and/or bypass communication/language barriers. There are instructions for capturing a log in the OP, but here is a simple method to use:

Remember that you can use the terminal to grab logs:

$ su

$ logcat > sdcard/logcat.txt

Then repeat what caused your issue

Then grab the logcat.txt(or "whayevernameyougive".txt) and share it

Also, the best way to help us help you, would be to track down some info regarding a Linux distro that works on your device. If Linux plays well with your device, tracking down the right driver for your display panel will be easier ?
[BLISS ROMS Development] RASHIDDDDD:
Window 10+Phoenix OS + Bliss OS Possible?

i Have a question ask from alot but couldnt get answer that can i use as my THIRD OS. I have installed Win 10 and Pheonix OS so can it be possible? Will it have any conflicts with Phoenix OS?
[BLISS ROMS Development] electrikjesus:
Yes, it will conflict. You will want to use the "roll your own UEFI" section of the Instructions from post 2 of this thread ;)
[BLISS ROMS Development] electrikjesus:
Try to recreate your data.img for that install. The log you posted was only the install log, so that's not going to tell us anything about why apps crash
[BLISS ROMS Development] reardenlife:
Bliss v11.9 on KVM install?

I am having a difficulty with installation of Bliss-v11.9--OFFICIAL-20190801-1319_x86_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso

I am trying to install it on KVM VPS through VNC access. I am chosing ext4 FS, installing GRUB and making /system RW. However, after reboot the GRUB failed to find normal.mod:

/boot/grub2/i386-pc/normal.mod not found

I could not fix it through VNC, through the setting of a different 'prefix' environment variable, because of the parenthesis in the filenames of the hd0 (VNC server doesnt seem to accept them), so I decided to reinstall the OS w/o making /system RW. It seems to install grub correctly, but I could not load OS. It just getting stuck with 'Booting...' on the screen.

Any ideas how to fix it?

Interestingly I recently installed Android x86 8.1 RC2 on the similar setup and never had any such problems. It seems to me that something in the Bliss OS installer is messed up.

Edit:

Just tried Bliss-v11.9--OFFICIAL-20190526-1104_x86_64_k-k4.19.32-ax86-ga_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso.

Same thing.

[IMG="Bliss OS KVM install fail"]https://i.ibb.co/bFLkQN2/Screenshot-20190817-184458.jpg[/IMG]

EDIT2:

Apparently the problem is not within grub.

paste.ubuntu.com/p/6RTrpkfr4P/
[BLISS ROMS Development] jjm06:
That is what i See if bliss 32 bit run...

[IMG="bliss 32 bit [MENTION=242801]amd[/MENTION] Radeon hd 7470"]https://dl.xda-developers.com/4/8/0/7/3/4/5/IMG_20190818_084849.jpg?key=vdRCpqkmolGT-f5KKNodMQ&ts=1566111690[/IMG]
[BLISS ROMS Development] the patron:
thanks only intel dual core 32b
[BLISS ROMS Development] electrikjesus:
You might need to force HWACCELL=0 from grub to make Swiftshader kick in and render without a physical display
[BLISS ROMS Development] reardenlife:
In order to solve those 'stripes' like the guy above having? (Mine a little vertically stretched though)

I tried HWACCELL=0. Didn't help.

I am asking a hosting provider to change a video card from cirrus to std right now. Lets see what will happen.
[BLISS ROMS Development] DivideDroid:
ElfinJNoty, thank you for your help and patience.

The device is OneMix3, the white version with 8GB ram and 256GB internal storage. This model is pretty new and is released in June this year. Since it has an additional M.2 slot, it also has a 1TB SSB attached inside, where bliss is installed.

Package used is: Bliss-v11.9--OFFICIAL-20190526-1326_x86_64_k-k4.19.32-ax86-ga_m-19.0.0_ax86-p_f-dev-kernel.org.iso

And somehow I could not found a section for me to upload reports and logs, so I uploaded them to OneDrive:

Logcat output: https://astrnuts-my.sharepoint.com/:t:/p/chise/EZ-V9pJPR7RIoNr_GcMWWCIBGlu3T0Ueooxr0wjxS-uZ7A
AIDA64 report: https://astrnuts-my.sharepoint.com/:u:/p/chise/EU1C3-Lyod5LmEfG9E58Iw4B_bFX2SviGsyHICyyvPvKqg
[BLISS ROMS Development] MadMax0067:
Can you please refer me where i can learn how to recreate data.img for this install?
[BLISS ROMS Development] ElfinJNoty:
The USB installer, as well as the .exe UEFI only Windows installer:

Both will create your data.img for you according to specified size during the installation process
[BLISS ROMS Development] ElfinJNoty:
Also... I began to search for a useful link, and then realized I'm not sure why I am doing this. Something you perhaps should have done before asking?(searching the internet remains a very powerful tool to help one's self!)
[BLISS ROMS Development] ElfinJNoty:
Can also refer you to docs.blissroms.com. Very important to read in it's entirety. Including a "Installation Guide" section with an abundance of options and info. ?
[BLISS ROMS Development] sunny54_8:
I've failed to find the download link for bliss rom X86 since 5 hours, where do I stand ?
[BLISS ROMS Development] electrikjesus:
Stand back about ten steps and stop there....

Now please tell us the steps you've taken to produce your results.
[BLISS ROMS Development] Supersonic27543:
Installed 11.9 with kernel 4.19 and no bugs so far! But I noticed that sometimes the first UI element is highlighted in gray. Looks like it's for keyboard navigation, but is it possible to turn it off? Is it an Android-x86 thing and not present in other kernel types? (My other device with Android-x86 also has the same behaviour)

Also Bliss OS is great and thank you for everyone who helped this grow! :)
[BLISS ROMS Development] ElfinJNoty:
All of our public releases are available via SourceForge. And there is a link in the OP.

You can also visit blissroms.com and click the download button on top right of page(in the menu) or just scroll down to the downloads section.

5 hours is an embarrassingly long amount of time to have still not found a way to our download links. I would advise you be very careful and thoroughly read the first 3 posts in this thread, and visit docs.blissroms.com for all needed infos about this project. And I wish you good luck moving forward.
[BLISS ROMS Development] electrikjesus:
If they're looking for a 32bit build, that's only shared in the update post for that release. Since it's experimental, I didn't want to add it all over
[BLISS ROMS Development] r0ckster05:
Surface 3 Non Pro Working Kernel =

Hey there.

First i want to thank you for all the efford and work you put into the Bliss Roms!!

I think i tried every Bliss OS version on my surface 3 (non pro), and non of it really worked.

most of them didn't even start in live mode or didn't detect my hard disk's when i tried to install it.

the others mostly didn't had working sound. 2 of them had working sound but no working battery icon (always 0%) and all was slow and it crashed.

i know it's now officially supported, but i hope that maybe there are some other with a surface 3 who could tell me if there is any version or way to get

bliss os or any other android port to surface 3??
[BLISS ROMS Development] atlantisq:
Thinkpad X1 Tablet 3rd gen?

Hi,

I have an Thinkpad X1 Tablet (3rd gen) from Lenovo. I've tried multiple Android builds on it but the farthest I've got is with the 11.4 Surface IPTS builds with kernel 4.19. Iit seems to load the kernel and get stuck at console:/ #. The console works and I can tell it to list the directories and reboot and stuff, but GUI never shows up. If I try nomodeset and/or xforcevesa it boots into a black screen with a non-flashing cursor and nothing moves from there. Bliss OS 7.2 and Android x86 8.1 gets to finding android... found at dev/nvme0nip4 and reboots. Btw I installed all these with the windows installer as with all the liveUSBs the computer shows up the Grub menu and whatever I select it goes into a black screen.

I'm supposing its the 3000*2000 screen that is confusing the system? But if it works on the hi-res screen of the surface...

Anythng else I can try?

Oh btw mine is with a 8550U cpu w the UHD 620 graphics
[BLISS ROMS Development] ElfinJNoty:
Q

On the grub bootloader screen where you'd select a boot menu option, press "e" for edit and verify that you have "androidboot.hardware=android_x86_64" without quotation marks. If it's not there, add it. Should fix. You can search for "androidboot.hardware" in this thread to see several other mentions of this and how users were instructed to add that command to the grub.cfg for permanent fix

---------- Post added at 05:43 PM ---------- Previous post was at 05:33 PM ----------

We won't discuss "any other Android port" here as this is the official support thread for Bliss OS. If you seek help with an alternative/competitor? Please go-to their offered support venues and ask them about their offerings. We will not provide assistance, and do not want other users offering such info, about another development team or company's work. There are other places for those subjects. Thank you for understanding :angel:

For all users, this applies:

You should also only be installing the most current releases (as of this post = 11.9)as previous versions lack recent changes and improvements, and we only support the latest public releases. If your device has an ipts display, then you'd need an ipts build, which we will try to get an updated ipts build out soon. Always use the .iso file with the most recent Bliss version available(in the file name).

If you do not have an ipts display panel(so far only the Pro 3 model in the Surface line), or you are not sure? you should test with the generic builds in a Live boot from our USB installer.

The Surface 3 has been reported working well by several users. Can check the Update Posts for details on each release announcement.

Also, check my previous reply to other user, where I make reference to ensuring you have: androidboot.hardware=android_x86_64

You may also benefit from the "old modprobe" boot menu entry option in the grub bootloader.

Remember to press "e" and add the above command to the boot menu entry to test
[BLISS ROMS Development] electrikjesus:
Try the Cali build from the IPTS download folder. That has a few x1 specific kernel commits added
[BLISS ROMS Development] electrikjesus:
You want the latest kernel-4.18+ IPTS build for the Surface 3. Make sure you follow the surface specific instructions in our docs for that device to work mostly right (battery level issues still)
[BLISS ROMS Development] sunny54_8:
I've found other android roms easily and downloaded. But on blissroms website they ask for email to send download link, after clicking download link in mail it again takes me back to the same website asking for and again asking for Email to send download link.
[BLISS ROMS Development] ElfinJNoty:
:confused:

Doesn't happen at all like that here :eek:
[BLISS ROMS Development] atlantisq:
Thanks for the advice, got a little further still. After finding android, console cursor flash, the screen goes blank with a dead cursor on the upper left corner and the backlight turns on, looking like the color of the logo screen. Interesting find is long press the power button causes the screen to go dim, as if there is a power menu showing up somewhere. Same thing with all the surface and generic 11.9 builds, with or without the androidboot.hardware argument.

X1 tablet gen 3 with 8550U and QHD screen.
[BLISS ROMS Development] electrikjesus:
Can you see if you can find me some Linux kernel drivers or modules for that device?
[BLISS ROMS Development] electrikjesus:
I would love to know exactly what steps you took to try to download. We do everything we can to spell things out and make it as easy as possible to download without even donating. And we never request anybody's email for download links. that might be a sign of a redirect in your browser locally
[BLISS ROMS Development] SparkyKitty:
I do have a Samsung np740u3l, and tried Bliss v11.9, and it does work very well only with one problem, when on battery and letting stay idle for 10 minutes, the System UI keeps stopping like it's trying to lock the device but can't. It is only that one problem I have with it. I cant get the latest experimental builds to work unfortunately.
[BLISS ROMS Development] ElfinJNoty:
Latest experimental builds are intended for machines that can only run a 32bit operating system due to CPU limitations...

If you can boot a regular x86_64 build, there is no reason for you to be trying those builds.

It has been mentioned already: disable your lockscreen or enable "do not sleep while charging" to avoid the system ui crash by preventing the device from trying to sleep.

This has been a known issue with sleep states and has been cited in Release Update Posts.

Glad everything else is working well ?
[BLISS ROMS Development] sunny54_8:
THANKS Sir,I was not just clicking try to download anyway, but also its not highlighted darker so it was not much visible on screen.
[BLISS ROMS Development] atlantisq:
Not very experienced with Linux but here's what I've found so far:

wiki.debian.org/InstallingDebianOn/Thinkpad/X1%20Tablet%20Gen%203 this link reports Debian to work with Debian's 4.17.0-1 kernel and using Xfce as the window manager

Also here is a device-specific patch: github.com/da-cali/linux-x1-tablet which is based on jakeday's linux-surface: github.com/jakeday/linux-surface
[BLISS ROMS Development] electrikjesus:
Yeah, that's where I got those patches for the cali build. I'll try and see if they have any updated patches next time I'm working on the IPTS kernels

There's a good chance all I'm missing is a few options in the defconfig
[BLISS ROMS Development] atlantisq:
Thank you. Will keep an eye out.
[BLISS ROMS Development] wizmart:
On an Acer aspire one 255D 2011 with a Atom processor 4 cores 2g ram I can boot only with no hardware acceleration which limit performance, i run without problems android 8.1 x86, Primeos on the same device. Do I need to change something on the boot menu? I did try all versions of bliss64 but without success....Not sure i have a 32 or 64b proc. right now running from manjaro 64 kernel but with some distros i can boot only 32b....

Any advice welcome, thank you
[BLISS ROMS Development] bullet25:
Does anybody have instruction on adding the surface firmwares if you can't boot into the system in the first place? The installation guide implies you can boot into Android.
[BLISS ROMS Development] electrikjesus:
We currently don't produce any Atom specific builds. We are considering it though, but it would need a different device tree and kernel combination than the generic builds we aim for currently. Maybe with a little guidance, that might be an avenue where a few of our community members could step up to. I would he happy to help things along, just cant dedicate the time when it's just me working on things.

There's likely something else going on then here. You're the first Surface user to report things NOT booting, so that is a sign that there might still be an issue with how you have your bios setup with encryption enables, or secure mode enabled.

Search the thread for "yourSurfaceModel bios boot" and see what you find ;)
[BLISS ROMS Development] sivagurunarayanasami:
App crash (32 bit)

Apps crash(like amazon kindle, chrome) or not opening on latest 32 bit.(Experimental - 32 bit (x86) builds - Pie).

is any way to fix the bug ?

i hope fix upcoming build

thanks you sir.:good::good:
[BLISS ROMS Development] bullet25:
I have a Surface 3, there isn't much in the bios at all. There are no encryption options, and secure boot is off.

I can boot to the USB or installer.

On the Expermental or ISPT builds, for both live and if install it gets stuck at the Detecting Android part.

On the Generic build it boot to the live disk fine, but if installed it just stays on the boot logo animation.
[BLISS ROMS Development] reardenlife:
Alright. So I loaded Live Ubuntu and mounted the partition where Bliss OS is installed. Any ideas how to fix grub from that point?

[IMG="grub files"]https://i.ibb.co/m8wTMvv/Screenshot-20190824-230436.jpg[/IMG]
[BLISS ROMS Development] ElfinJNoty:
https://opensource.com/article/17/3/introduction-grub2-configuration-linux

---------- Post added at 11:57 AM ---------- Previous post was at 11:53 AM ----------

Make sure(by moving your selector over the boot menu choice in grub boot menu options, then press "e" to edit) that you have: "androidboot.hardware=android_x86_64".

If it isn't there, add it, and boot. It will be a one time modification to the boot menu entry, and adding that(if not present) should get you to booting. If that works, refer to my previous reply about intro to grub config ?
[BLISS ROMS Development] reardenlife:
I cannot see how it is related to my question. I will tell it again: there is no /boot/grub2/grub.cfg. I have only stage2 file, which I apparently need to reconfigure. The question is about how to do that.

The real problem is that there is no information within grub documentation about 'normal.mod'.
[BLISS ROMS Development] ElfinJNoty:
Grub should be installed to your EFI partition on a standard install. And you asked how to fix grub. Therefore, that guide was meant for you knowing how to find and access your grub.cfg, and what you might use to supposedly fix.

We do not officially support virtualization.

Sorry you are having difficulties.

Suggest you install with the documented methods we provide.

Beyond that, not sure why you keep seeking support for something we do not officially support. I wish you success, but think you have exausted my efforts to assist you.
[BLISS ROMS Development] reardenlife:
Then you have to update your documentation. On your official website (https://blissroms.com/ , Download section) it is written that:

And that is exactly what I was using.

Beyond that, your actions on the Telegram channel (banning me for simply asking a question) are totally inadequate and you probably know about that. ;)
[BLISS ROMS Development] harris123424:
I have problem with Taskbar ( bliss os x86 pie 64bit ). flickering monitor. But quickstep launcher works fine
[BLISS ROMS Development] ElfinJNoty:
You are using a VPS which is not the same as native virtualization.

Either way, you are free to use our OS or do not. We happily assist as many users as we can on a daily basis. It is a difficult task enough when users follow instructions and attempt to use our BETA PREVIEW releases. Testing on any one of the 1000's of potential hardware configurations possible. YOU are chosing to do something that is untested. We make the builds for that purpose. But let me be clear one final time: We do not officially support virtualization.

Many changes to the website are in the works.

As far as you getting removed from a TG group... Our rules are posted, and our team administrates those groups at our discretion. Again, if not to your liking.... Feel free not to use our OS or our support forum or our TG chats.

Nobody has ever been banned for simply asking a question.

Unless that person asked the same question repeatedly in all of our chats and then acted rude when we asked them not to. No rudeness is tolerated. And no entitlement will be met with an eagerness to help.

This is a development thread, so please keep on topic. Otherwise we can seek a moderator's help to remove you from here as well?
[BLISS ROMS Development] reardenlife:
So you require hardware assisted virtualization?

I am doing my best. :)

Bugreporting is not rudeness. As well as clarification of the qustion being asked.

I have a problem of installation of Bliss OS on VPS. And this problem can be solved, because I have Andoid x86 8.1 RC2 working on my KVM VPS. And it seems like a fun thing for me to solve. *( Again, I am not attacking you or your work by submitting a bugreport or insistently asking how my problem can be solved. )

And I thought that is what opensource projects suppose to be - a fun thing, not an ordeal you describing. Am I wrong?
[BLISS ROMS Development] electrikjesus:
I apologize for all the miscommunication in this matter. We will try and tone things down moving forward.

Our current form of KVM/QEMU support is the one detailed here for Android-x86 Project: https://www.android-x86.org/documentation/qemu.html

That is the one method I have used to test with in the past, and was the only way I knew to boot using QEMU or KVM until recently when you and one other user mentioned using a different method.

So, the method you are using doesn't have all the details worked out just yet, but with a little help, I feel we can get the docs updated with the required info in order to help things out a bit.

Thank you for your patience in things and I appreciate all the feedback you and others have given as of recently.
[BLISS ROMS Development] michaje:
supersu occupied

hello there,

am getting error supersu occupied i can't use supersu what should I do?
[BLISS ROMS Development] r0ckster05:
May I ask, how you added the firmware files directly to the live cd?
[BLISS ROMS Development] bullet25:
I just did what the instructions said from the live mode, then installed it with that.

So I booted to the Live mode, copied the firmware files to the sdcard, used the terminal to move them to /system/lib/firmware, shutdown, rebooted to the install and installed.
[BLISS ROMS Development] the patron:
Help App Summoners War.

please help the summoners war game application since update app sw5.0.7 when starting it when loading the data to enter the game ... this pop-up warning appears on the front when you click ok close the SW application.

Currently the application is in update sw5.0.8 and the pop-up warning continues since that day I cannot use the SW game.

Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01

https://xdaforums.com/sho...postcount=1039

Bliss-v11.9--OFFICIAL-20190801-1319_x86_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso

I have used these versions of android and I have the same error

Lineage OS 14.0 CM-x86-14.1-r2.iso 32bits

Android-x86 Oreo 8.1-r2.iso 32bits

Primeos_Classic_0.4.5.iso 32bits

I use this method of installation ext4

https://youtu.be/471z1kpUZvo