yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] Ckani:
I finally got around to getting a dell venue 11 pro 7139. Mostly everything works except the touchscreen. Tried the latest nighty and bleeding edge. I have it set to legacy boot.

The Specs are

i5-4300Y

Intel hd 4200 1920x1080

8gb ram

Any suggestions I can try. I can get it to boot and install to a micro sd card or usb drive to test.
[BLISS ROMS Development] ElfinJNoty:
The latest nightlies should include updates to firmware files for the SP lineup. Give that a try.

Otherwise... Read.

Many users have been reporting which .iso's they are having success with
[BLISS ROMS Development] Themule08:
I can use this to put android on a surface pro right? From what I gather is once installed it is just a folder not a whole OS like linux...

Not bootable but more like a program
[BLISS ROMS Development] DoughMucker:
Kind of yes and kind of no...

It can be installed as a folder on an existing hard drive. A new drive or a new partition on a hard drive is not required.

But it is not a program; it is its own operating system. You won't be booting into Windows.
[BLISS ROMS Development] osbaldov:
I have a question based off of building from source code. I have an hour sleekbook laptop, with a dual core AMD A6-4455M CPU at 2.6ghz and 8gb of ram. Would this be suitable for building?
[BLISS ROMS Development] Blackdragonbird:
Hi, trying to use this rom in my system, but having issues. Using the live usb mode the system boots but keeps getting the message that app store/system/other app system has stopped. Got it to boot to the part where you select your launcher, after it computer got a black screen and rebooted. Tried it in my desktop and notebook, same results. Also tried to install it to an old ssd of mine, it copy the files on the ssd, but after first reboot the system can't find the system in it anymore, like the ssd is not bootable. Tried normal and fast install methods, same results.

My systems:

Desktop: i7 2700k, Asrock Z77 extreme 4, 24Gb Corsair 1600mhz, nvidia GTX 970 and GTX670(phys dedicated in windows), Samsung 850 EVO 250GB.

Notebook: HP Pavilion I3 2dn generation, Integrated Intel HD Graphics, Kingston SSD Now 128Gb, 8GB 1333mhz.
[BLISS ROMS Development] Guimenez:
I'm trying to download but link is down
[BLISS ROMS Development] jhetrosky:
is there a way to install bliss os using your Androidx86-Installv26.0003.exe on windows 7?

the easy installer requirement is windows 8.

when I try to run the easy Installer is says "not all requirement are met" and it opens but I can't click anything
[BLISS ROMS Development] jhetrosky:
stuck on detecting android
[BLISS ROMS Development] jhetrosky:
stuck on detecting android-x86.

using usb to boot
[BLISS ROMS Development] DoughMucker:
A better observation would have been to read the last post in this thread made by the developer (10 days ago). It's far more relevant than what you're referring to.

People have lives. It's August, the peak of summer vacation in many places. Give the guy a break!
[BLISS ROMS Development] ElfinJNoty:
Hello XDA Forum Members,

My name is Evan Galvin, I am on the Board of Directors for Team Bliss & Bliss Sudios, and the Team Product & Technology Strategist

On behalf of the team I'd like to report that Oreo development for BlissRoms and BlissOS for x86 has come to an end. Our team has been hard at work bringing up Bliss to Android 9. This work happens first on ROM side development for cell phone. We need to ensure the ROM side of things is buildable and stable before we can begin porting in features. Our lead developer for BlissOS has been aiding the rest of the team on that front, and little to no time has been allocated towards x86 development.

With the end of Oreo development and the transition to Android Pie, we ask for your patience as we stay away from reanswering questions and steering people towards solutions & information that already exists here in the threads as well as or Telegram Support thread. You may have noticed our absence in the thread, due to the reasons mentioned above. And you can expect this trend to continue until further notice.

If you have questions or need help, we ask that you help each other and utilize the information already available. Downloads remain available and self testing is required, we won't be providing support at this time until we have Android Pie ready for our users and tested to a point where we feel comfortable to share. Pie builds of Bliss OS have not yet started, so don't ask yet. We will announce if/when that changes.

If [MENTION=928479]electrikjesus[/MENTION] is gracious enough to bless you all with his presence, that means he is taking time away from development to do so. Which further means longer before BlissOS is ready for Pie. Also, please do not personal message or use official team emails asking for help or support. They will be ignored, as your idea of an "urgent matter" is no greater priority than any of our other users who use the appropiate avenues to seek help and support.

Again, thank you for your understanding and patience during this transition to Android 9. We will update you all as things progress. #stayblissful

Evan Galvin

Team Bliss
[BLISS ROMS Development] REV3NT3CH:
To add to this. I'm a new team member to the Bliss OS project and will mostly be doing kernel development on this side of the field starting with the Pie bringup. For those of you who remember me and have used my work on Android phone devices, happy to see you here.
[BLISS ROMS Development] REV3NT3CH:
To answer you. Have you at all tried any of the newer builds via live booting them? iirc surface book 2 uses ipts (could be wrong) but wouldnt hurt to try and see if one of the ipts builds work for you. Bliss x86 isn't really meant for just 1 device and is still in early growth stages...which heavily relies on feedback, logs etc. However as stated by Evan and myself above we've been working on Android 9 and have ceased development of Oreo. We also do have jobs outside of this currently as well as family. Keep in mind that op has also been a majority of being the only one doing this project...think of that for a moment. 1 person with all of you on different devices... Can be a heavy load.
[BLISS ROMS Development] VTArxelus:
Bliss working on Acer Switch One SW1-011, but...

Hi there! Reporting that Bliss 10.1-PC_rc1 is running on Acer Switch One model SW1-011, however bluetooth, WiFi, and sound are non-existant. I can tether via USB to my phone for internet, but that defeats the portion of the efforts. The specifc problem I see is that Bliss doesn't seem to be detecting the MAC addresses, and perhaps falling back on some sort of default with zero functionality. As for the sound, I'm not sure what the problem is there. If you have any advice, i'm open to trying whatever to get it working.
[BLISS ROMS Development] electrikjesus:
Sb2 build unless you want root. Then follow instructions to update firmware manually from the latest Bleeding edge build
[BLISS ROMS Development] Amfakh:
I'm on GL503VM right now try to running v7.2 with kernel 4.9, installation is successful but the display is messed up like this

edit: tried latest 10.1, it booted successfully but keyboard not working and force shut down after 20 sec or so,

xforcevesa not booting and nomodeset results to same problem as the picture below
[BLISS ROMS Development] vittpda:
Dual boot works, Wifi issues after usage, restart option doesnt restart

Ive got BlissOS 10.1 dual boot on Surface pro 4, everything seems to work but I ve noticed wifi drops while downloading or video usage. Also hangs on Bliss Logo on device bootup periodically. If i hit restart device shuts down but no restart. Need to hold power for 10 seconds then retry powering up. But great work otherwise!
[BLISS ROMS Development] DoughMucker:
Possibly. I guess I've seen too many posts in xda from impatient users requesting "urgent" help and then making negative comments about response times.

You're confused here. Your post for help was not 10 days ago. I referred you to a post 10 days earlier. But you shouldn't have any expectations on time for a reply. Regardless, I see two devs have responded to your first question since then.

My post was specifically about your inaccurate "observation" about the thread being "unattended to". electrikjesus's post which I referred to said, and I'm paraphrasing, "I'm making another build for the surface users. I'm making some instructions. I want to make it easier. I just don't have the time I used to." It is entirely relevant to your inaccurate observation and the other posts.

I'd rather give some positive feedback and say thanks for whatever amount of their valuable time they do give to develop or provide support. :good::good:
[BLISS ROMS Development] marcos8202:
What is mean by "secondary modprobe option"?One of the know issues on page 1 is sound not working which is what I'm experiencing. Everything else seems pretty good. I get a random restart sometime. I never thought of running Android on my old Toshiba Encore 2 tablet. So overall this is pretty cool. So I'm googling and trying to research myself as I'm not a Dev or have coding skills. But I can follow instructions.
[BLISS ROMS Development] REV3NT3CH:
To be honest it all boils down to your hardware. A better question to ask is does any particular form of Linux work for you? If so which one and what version of the kernel is it running? Even my dev tablet doesn't have everything working 100% on it. Getting the compatibility down 100% is not an easy task. Help lighten the load. Instead of being so negative about it. Will not get anyone anywhere
[BLISS ROMS Development] electrikjesus:
If there is a previous version, use that. It is likely the kernel change that hangs the device.
[BLISS ROMS Development] ElfinJNoty:
Without knowing what .iso you've flashed, this post = only "it not work" ?

Please let us know which build(.iso) you were able to successfully install.

No promise to help correct at this time, that said, we appreciate the feedback and need more details to make sure your efforts are useful.

Thanks again for the feedback

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

Thank you for following up and sharing your success?

---------- Post added at 02:09 AM ---------- Previous post was at 02:02 AM ----------

1. Do not quote the OP

2. That is unfortunate

3. ...........

Sorry, couldn't think anything else helpful to tell you. We can only be of help to users who provide us relavant information towards your installation method, which build you used (.iso), and perhaps even a weeeee bit of info about which of the million and 1 x86 architecture devices you own that have been manufactured in the past, um, 40 years?

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

1. Thanks for not not quoting the OP

2. Ahhhh. Trouble doing a live boot from USB? Your machine may not even meet the minimum requirements to run Bliss OS. See if you can live boot any Linux distros using same (unknown machine?) And the same USB. If you can, come back. If not, see #3

3..........

Still thinking
[BLISS ROMS Development] minilandl:
How did you get rooted apps working are you using magisk can you pass safetynet with systemless root provided by bliss x86
[BLISS ROMS Development] wenna.speedy:
ASUS T101HA (Z8350)

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9 & k4.4 - no sound, no rotate, no brightness

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org - doesnt boot(black screen)

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180619-2059_k4.16.14-bliss-ipts-ga_18.1.0-devel_w14_dev-kernel.org - no sound, wifi problem - reboot after connect

but...

Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified.iso

GPU - ok (GARENA FREE FIRE)

Wifi -ok, stable

Rotate - ok

brightness - ok

sound - doesnt work... :(

I am very sad, the last one works really good, but the sound... Has anyone solution or working version with cherrytrail tablets?
[BLISS ROMS Development] ElfinJNoty:
This answer can be found in the OP and following posts

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------

We do not use magisk.

Root info is in the OP and following posts
[BLISS ROMS Development] SERGE4NT:
Why can i not install some apps, like Fouad-Whatsapp v7.60?
[BLISS ROMS Development] tobad:
currently not working.

you can try: https://xdaforums.com/showpost.php?p=76740960&postcount=2031
[BLISS ROMS Development] jhetrosky:
Wanted to use the easyUEIFI but I cant. after I clicked on it, it says not all requirements are met.

================Installer Info================

Installer Directory:C:\Users\Peñanueva\AppData\Local\Temp\RarSFX2

Installer Version:2.6.0.0

Secure Boot ... Not Supported

Manufacturer: Gigabyte Technology Co., Ltd.

Model: To be filled by O.E.M.

Product: H61M-DS2

BIOS info:

DELL - 1072009

BIOS Date: 04/17/13 12:03:18 Ver: 04.06.05

BIOS Date: 04/17/13 12:03:18 Ver: 04.06.05

Available GPU(s):

GPU: NVIDIA GeForce GT 730

=============[REQUIREMENTS CHECK]============

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: Intel(R) Pentium(R) CPU G620 @ 2.60GHz

OSVer: Microsoft Windows NT 6.1.7601 Service Pack 1

Windows Security: Access NVRAM Privilege ... Not All Set

System Firmware: Other

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

booting the iso on usb with rufus wont work. Do you know why I cant use the easyUEIFI installer?

I installed remixOS years ago and it works fine, just wanted to use this because remix has been suspended.
[BLISS ROMS Development] xhamadeex:
Hello developers

Do you guys think we will ever see the surface pro 4 run android or Linux without the touch screen issues? I just want to know if it's fixable or not.

I noticed that with Linux, you can run scripts to restart the IPTS firmware and get touch to work again, there was a guy who made the scripts run by pressing the volume up and down buttons using acpid (link: https://github.com/jakeday/linux-surface/issues/186 ). Can we do the same on android using Tasker maybe?

Thanks for your help!

Cheers!

---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------

By the way, the commands are:

rmmod intel_ipts

and

modprobe intel_ipts

which I got from the following link

https://github.com/jakeday/linux-surface/issues/55

Can anyone confirm that these commands do restore touch functionality, as I don't have the rom installed.

Thanks!
[BLISS ROMS Development] wenna.speedy:
I am not able to build Vannila 7 with this kernel on my machine :/. Could you send me your builded iso?
[BLISS ROMS Development] scarmau:
Restore android boot

Hi everybody!

I have reset the efi partition of my sp4 for some problem and as a result the android boot has disappeared.

I'd like to know if is possible restore the android boot (grub) without reinstalling Android from scratch.

Thanks in advance :D
[BLISS ROMS Development] ElfinJNoty:
"Secure Boot ... Not Supported"

Disable secure boot. Disable Bitlocker. Turn off "Fast Startup" in Windows.

Again, this answer and many others can be found in the OP and following posts

---------- Post added at 12:02 PM ---------- Previous post was at 11:51 AM ----------

The short answer is yes, I do think we will see the Surface 4 run without touchscreen issues.

That said, Oreo development is dead. BlissOS is not the reason for these touchscreen issues, as you mentioned, Linux distros overall see the same results. We will do our best to include a patchset in the future to help resolve. Thank you for sharing the script and the commands. Would be even more helpful if someone would like to test on a Surface 4 device and verify weather or not it works. We do not own a Surface 4 on the team. We don't own a device, we cannot test on it.

This will not be resolved at this time as we are busy working on Bliss bringup to Android Pie and are not currently building for x86. Again, thank you for the share

---------- Post added at 12:13 PM ---------- Previous post was at 12:02 PM ----------

We don't know what your "some problem" is and cannot/will not advise what to do when you are started with something broken.

There is not a simple method, but by reading the OP and following posts, there are instructions on how to roll you own manual UEFI installation. Including installing grub to EFI. Please do not reply asking for assistance to do what you are asking.... The answer to your question can be found in the OP and following posts.

Advise that you fix your "some problem" first, then do a fresh install from scratch
[BLISS ROMS Development] scarmau:
Thanks for the answer.

The "problem" was external to android and I solved.

However now I will follow your advice to restore the grub.
[BLISS ROMS Development] vampire_dnd:
ROG Keyboard Issue

Any solution for ROG keyboard? not work :(
[BLISS ROMS Development] ajay131:
I tried to install it E DRIVE.

Please suggest solution. I despirately want to install.

log-------------------

#Launch:C:\Users\Ajay\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "E:\AndroidOS\data.img"

===Installing Boot Objects===

-Mounting EFI Partition...

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

-Setup Boot Directory...

-Boot Directory is Already Exist

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

-Cleaning up Bliss Directory ... E:\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

==========================================
[BLISS ROMS Development] ElfinJNoty:
There is a button on the installer.... "Remove Android"

https://youtu.be/0UkPyYfj0xA

^~follow steps in this video if there is any confusion about what tha very obvious button might do to help ya ?
[BLISS ROMS Development] ajay131:
Thanks for the reply.

I did exactly as per video. I choose E drive & It's installed correctly. But not showed in my boot menu(i checked in EasyBcd). Then I restarted pc, no option in boot menu (showed "repairing c drive").

Should I choose C DRIVE?
[BLISS ROMS Development] ElfinJNoty:
Have you gone into bios and selected the proper order of boot priority? Windows Boot Manager should not be the 1st option for boot order. Select "grub" or "androidOS"

As far as I know, easyBCD has been reported to have mixed results and can interfere.

I would recommend just installing to your C: drive. The installer cannot damage any portion of your Windows installation

Using the installer in windows, you will have to "remove Android" before each new installation, otherwise you will face the same error as first reported.

Installing to a drive besides C: shouldn't matter. The installer will write the boot entry in grub and set up the EFI according to your settings. I think easyBCD is the culprit here. But who knows ?!?

When provided proven method of installation, like in the video, best to follow those instructions exactly before attempting to vary off the proven path.
[BLISS ROMS Development] ElfinJNoty:
If you are willing to contribute to development, we could always use extra help. We were planning to release source for Oreo, once we have finalized preparations for Pie.

Thanks for sharing the patch with the us. That includes users and Team Bliss. Feel free to contact myself or [MENTION=928479]electrikjesus[/MENTION] if you care to be a little less "inactive" :svetius::cool:

Thanks again for sharing

---------- Post added at 02:24 AM ---------- Previous post was at 02:17 AM ----------

Find us it's driver. We are always willing to include additional driver/Firmware/patchset that people share for their particular devices to improve compatibility. However we don't go chasing down the needed parts to resolve compatibility issues for specific devices/accessories. We ask our users to help us help you.

If you can boot a Linux distro which works out of the box, or have a driver file for us to use.... Sharing that would be a start. If you find it, we will do our best to include in future builds. ?
[BLISS ROMS Development] ajay131:
Installed it on C drive, still not showing it in boot menu.

Yes I went to BIOS but there is no Grub/AndroidOS in Boot Order to give priority. attaching log file.

Please see it.
[BLISS ROMS Development] ElfinJNoty:
How much free space is remaining on the drive you are installing to?

As I said previously, do not use EasyBCD in between installing and rebooting. Forget EasyBCD exists. If it has some method of turning off and removing itself. Do it. Avoid easyBCD altogether. Completely power off your machine. Remember that SecureBoot should be off(your log shows that it is), bitlocker should be off, and fast startup(setting from power options within windows) should be disabled.

Power on and hit whatever key you need to use to enter either boot menu or bios, and then locate boot options. You said previously you did not know how to find Windows Boot Manager? Then you have not located where you need to be in your bios to set your order of boot options. Each bios is different. So I can't tell you exactly where it is. But it's there somewhere. And there should be other options. USB, Floppy, CD-Rom, etc. Windows Boot MGR should be an available option. So should Android OS. If you find that area of bios and are not sure... Take a picture and share it. But Windows Boot MGR should NOT be #1 if you can also see the Bliss install.

I can't help you any further. You are missing something. The log shows nothing out of the ordinary. Or your machine has some type of weird protection method, and that's why it is attempting to "repair C: drive" upon reboot. Even when you didn't install to the C: drive? Again, don't mean to be rude, but there is some type of user error taking place here
[BLISS ROMS Development] ajay131:
Yes I know there is problem with my system only. But I dont know what it is. I thought log will give some idea but i didnt figured out. I have also uninstalled easyBcd. Repair c drive only displayed once.

I have now enabled legacy options also but still no change.

Sending u pics, please tell what is wrong.

One more thing to tell, hard drive was previously Dynamic MBR. I converted it to BASIC GPT and then flashed Win10 in efi mode.

Will that ve a problem???
[BLISS ROMS Development] ElfinJNoty:
Annoucement: The Downloads server is currently undergoing maintenance.

During this process, all Bliss OS .iso files will be unavailable.

An update will be posted when this process is completed.

Thank you for your patience during this important process!

As always, #stayblissful

---------- Post added at 08:38 PM ---------- Previous post was at 08:19 PM ----------

You should not have legacy only enabled, considering your Windows install and the BlissOS install are both UEFI based

No this will not be a problem, considering the Windows Installer ONLY supports UEFI and is not compatible with any type of legacy installations of the Windows10(you should be booted to when using the installer)

When you posted your log file, it passed the check for UEFI being present... But were you booting with legacy only mode enabled in bios?

Boot to windows, click start, type "disk management" and open it then screenshot & share please

Either grub is not being written to EFI correctly, or something else weird and unknown is taking place. Potentially both, because the installer in not reporting an error, therefore I am running out of ideas for you. If you followed the video, and got no error during installation, you need to determine where things are going wrong. There is no reason grub should not be installed unless the fat32 partition EFI is located is out of space.

Waiting on you screenshot of disk manager
[BLISS ROMS Development] Legitsu:
Last time i tried this I could't get multimon support working

anybody know how to fix it or at least get bliss to default to the correct monitor