yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] dapo4friends:
Thanks again for responding...

To save ur precious time and mine, I'd just skip all the parts i find unpleasant and unfair in ur response despite my attempts to be very clear by itemization...

I gain nothing by discrediting your team- on using the product of your hard work-free of charge,_what more cud I ask for, I mean!!!

Anyone who carefully compares the initial USB to MBR hard drive installation guide, with what you have written here can clearly see the omissions in the former-no mention of a need for a 2.5 gb of space for system to install, I assume you know you are writing for armateurs/enthusiasts!!!

Well, after formatting the entire 500 gb drive, here below is what I did and result i got;

I created a 90 gb windows partition and installed windows 8.1 into it...

I created an 12.00 gb ext4 partition for bliss x86

A 1.00 GB (to be safe) fat32 partition for grub to install to

The last partition (370gb) is for my personal files...

INSTALLATION...

My system is a 2012 Acer Intel atom 32bit 10.1 inch notebook

I used Rufus 2.9 to create a bootable USB containing bliss x86 installation files...

During installation, I was prompted to select the partition to install bliss into and i selected my 12.O GB Ext4 partition...all seemed well..

I was asked whether I'd like to install grub, BUT I WAS NOT GIVEN THE OPTION OF SELECTING A GRUB PARTITION...It went ahead, where it installed itself I do not know!!!!

I was also not given an option of selecting the data.IMG size I would want

Installer asked me if I wud like to add windows to boot menu bcos it found windows boot files in a partition, I agreed...

All finished and it asked to reboot or boot android x86...I agreed to boot android x86

After the ANDROID_# prompt, I'm still staring here at a blank screen with a prompt....

The suggested NOMODESET option didn't solve it also....all codes just running along and finally paused... At ANDROID_#

THE WORSE PART;

I Rebooted my PC, and Grub showed up, I selected WINDOWS,the result

Error 21: selected disk does not exist

Press any key to continue

Question:

What happened to windows again?

On attempting to resintall windows again using my windows bootable flash .

1. I noticed that the grub partition was empty (means grub wasn't installed there!!) Windows still had its files inside

2. If system files are about 2.5_and data files_are about 8gb in size, that's a total of 10.5. + or -, how come the entire partition was filled with 0 mb space left...

3. Windows 8.1 uses roughly about 10 GB of space when freshly installed, but here I can read that 20gb has been occupied on my windows partition

I used the latest version of the Bliss x86_x64 (2017-07-03) stable branch for this installation.....

So??
[BLISS ROMS Development] dapo4friends:
Thanks thanks again for responding...

To save ur very precious time and mine, I'd just skip the parts i find unpleasant and unfair in ur response despite my attempts to be very clear by itemization...

I gain nothing by discrediting your team- I'm using the product of your hard work-free of charge,_what more cud I ask for, I mean!!!

Anyone who carefully compares the initial USB to MBR hard drive installation guide, with what you have written here can clearly see the omissions in the former-no mention of a need for a 2.5 gb of space for system to install, I assume you know you are writing for armateurs/enthusiasts!!!

Well, after formatting the entire 500 gb drive, here below is what I did and result i got;

I created a 90 gb windows partition and installed windows 8.1 into it...

I created an 12.00 gb ext4 partition for bliss x86

A 1.00 GB (to be safe) fat32 partition for grub to install to

The last partition (370gb) is for my personal files...

INSTALLATION...

My system is a 2012 Acer Intel atom 32bit 10.1 inch notebook

I used Rufus 2.9 to create a bootable USB containing bliss x86 installation files...

During installation, I was prompted to select the partition to install bliss into and i selected my 12.O GB Ext4 partition...all seemed well..

I was asked whether I'd like to install grub, BUT I WAS NOT GIVEN THE OPTION OF SELECTING A GRUB PARTITION...It went ahead, where it installed itself I do not know!!!!

I was also not given an option of selecting the data.IMG size I would want

Installer asked me if I wud like to add windows to boot menu bcos it found windows boot files in a partition, I agreed...

All finished and it asked to reboot or boot android x86...I agreed to boot android x86

After the ANDROID_# prompt, I'm still staring here at a blank screen with a prompt....

The suggested NOMODESET option didn't solve it also....all codes just running along and finally paused... At ANDROID_#

THE WORSE PART;

I Rebooted my PC, and Grub showed up, I selected WINDOWS,the result

Error 21: selected disk does not exist

Press any key to continue

Question:

What happened to windows again?

On attempting to resintall windows again using my windows bootable flash .

1. I noticed that the grub partition was empty (means grub wasn't installed there!!) Windows still had its files inside

2. If system files are about 2.5_and data files_are about 8gb in size, that's a total of 10.5. + or -, how come the entire partition was filled with 0 mb space left...

3. Windows 8.1 uses roughly about 10 GB of space when freshly installed, but here I can read that 20gb has been occupied on my windows partition

I used the latest version of the Bliss x86_x64 (2017-07-03) stable branch for this installation.....

So??
[BLISS ROMS Development] daspex:
Hi,

i've tested serveral builts and the 1555 k4.9 b m17.1 pw rc 01 iso works fine but the touchscreen reacts just for gestures and not for fingertips or swipes.I would love to use this rom as my standard driver if the touchscreen would work normal.Maybe the touchscreen has to be adjusted?I would be greatfull for help with this issue becouse this is the only x86 that ever runs on my device.Thank's in advance.
[BLISS ROMS Development] hgblob:
Sensors for Surface 3 Pro

Hi Again,

Thank you for your very hard work, my Surface 3 PRO is almost perfect. One thing that was missing was the correct sensor hub. I made a patch to your ax86 kernel https://github.com/vamanea/kernel_common/commit/9b220fc796920311db7be132a42f7b8f51b447e5 which enables the orientation and ALS sensors on Surface Pro 3. After this patch orientation works perfectly, ALS I'm not so sure, but the problem might be in the HSB libsensors.
[BLISS ROMS Development] OMERZEN:
How can I use my external monitor (with VGA cable) and my HDTV (with HDMI cable) ?
[BLISS ROMS Development] daspex:
I wonder if it may be usefull to change the I2C Touch device address from RVP/iCDK(0x4B) to FFRD(0x4A) or Auto.Could that change something?
[BLISS ROMS Development] animesh1558:
i successfully installed it but doesn,t shows up to choose when i restart.
[BLISS ROMS Development] ElfinJNoty:
If the grub doesn't show up as an option on bootup.... Verify you do not have windows "fast startup" enabled. Also, go into your bios and verify you have the boot entry available. Switch your boot priority so that grub is #1 ahead of the windows boot manager. You can reverse this easily if this doesn't work
[BLISS ROMS Development] electrikjesus:
You will need to boot into your UEFI settings and choose the Android OS entry. The other option that was mentioned in the 2nd post is using EasyUEFI to select it as default.
[BLISS ROMS Development] daspex:
Why you don't respond to my posts?
[BLISS ROMS Development] electrikjesus:
I'm sorry, but it seems like you expect immediate answers for a device I know little to nothing about, other than it might have an i2c touch adapter, and one of the recent builds I assume works for your device where none other have...

If this isn't what it seems, then please fill in the blanks I missed. Otherwise, I would love to have a lot more info and possibly some logs to help me understand what's going on in that device of yours.
[BLISS ROMS Development] electrikjesus:
Could you give us some info on what type of device/PC you have, along with it's graphics chipset or setup?
[BLISS ROMS Development] daspex:
Ok. I would like to give the needed informations you miss but what are you mean with blanks?Sorry but english is not my nature language should i post the install log or what kind of infornation do you need?

---------- Post added at 03:19 ---------- Previous post was at 03:02 ----------

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

Installer Directory:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0

Installer Version:2.4.5800.0

Secure Boot ... Disabled

Manufacturer: MPMAN

Model: MPW815

Product: MPW815

BIOS info:

INSYDE - 3

MPMAN.F.W86C.JLBNRBA02

INSYDE Corp. - 54470054

Available GPU(s):

GPU: Intel(R) HD Graphics

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

Administrator privilege ... ok

OS Type: 32-bit!

CPU Architecture: 9

CPU Name: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz

OSVer: Microsoft Windows NT 10.0.14393.0

OperatingSystem Version ... ok

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

System Firmware: UEFI

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

====Install Started on 26.07.2017 06:29:50====

-ISO File: C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170626-1555_k4.9-b_m17.1_pw_rc_01.iso

-TargetDrive: C

-UserData: 17762877

-Setup Directories...

-Folder Created: C:\AndroidOS

-Extract ISO

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe x "C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170626-1555_k4.9-b_m17.1_pw_rc_01.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS

-Extract SFS

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe e "C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170626-1555_k4.9-b_m17.1_pw_rc_01.iso" "boot\grub\grub.cfg" -oC:\AndroidOS

-Create Data.img

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=C:\AndroidOS\data.img count=17762877

-Initialize Data.img

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

===Installing Boot Objects===

-Mounting EFI Partition...

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

-Setup Boot Directory...

-Boot Folder Created: Z:\EFI\boot\

-Copy Boot files

-Add UEFI Entry

-UnMounting EFI Partition...

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

==========================================
[BLISS ROMS Development] ElfinJNoty:
What type of device are you using? Name/model number at least. If you already know the type of CPU and graphics, that would be helpful information.

All you have shared so far is a desire to output to an external display. We need more information about your device otherwise we are unable to help you.

Nevermind, your log will be sufficient

Please look up the term "fill in the blanks" in a Google search. ?
[BLISS ROMS Development] daspex:
Ok. Posted last install log and google for blanks...

---------- Post added at 03:45 ---------- Previous post was at 03:29 ----------

Ok. I posted the last install log for my device but if you need more information please let me know,sorry for missunderstood something but english is not my nature language and i've had a horribly buissy day today,sorry for that.
[BLISS ROMS Development] electrikjesus:
Lol, I think he was replying to the other user. For you, could you also supply the device name, model, manufacturer. And also specifically what Intel HD gfx chipset and ports it has
[BLISS ROMS Development] daspex:
Yeah,it has been late today.

CPU:INTEL ATOM Z3735 1.33 GHz

Graphics: INTEL HD GRAPHICS IGP MICRO HDMI

DISPLAY: 8" 1280X800 MULTI TOUCH IPS

DEVICE NAME: MP MAN 815(MPW815)

MPMAN.F.W86C.JLBNRBA02

BIOS:INSYDE - 3

INSYDE Corp. - 54470054

ports i have to figure out...

But as i read ips i remember that google has removed the support for it from the kernel since 4.3 version if i remember right but as i posted before some gestures are working but no fingertips or swipe movements are recognized by the system.
[BLISS ROMS Development] electrikjesus:
I have a IPTS test build that I will try and remember to upload tomorrow. It won't work for everyone, like the newer SP4 screens, but it might for the older
[BLISS ROMS Development] daspex:
Thank you very much for being so kind and support my old device and for helping with that issue,can't wait for downloading it tomorrow.:good:

Bonam noctem and thank's again:victory:
[BLISS ROMS Development] wheeqo:
I'm sorry if it's not related to the topic.

I have tablet only with out keyboard (Acer Iconia W700, i5-3337U, HD 4000, SSD 64GB) and successfully installed the ROM with dual boot.

Is there anyway to choose option from Grub menu without keyboard? The power and windows button did not work, and the volume up & down only choose the option up & down, the enter function is not present. Any solution?

I heard there is solution to edit the grub config file and change the keyboard assignment code.
[BLISS ROMS Development] PLAY911:
Hi! please I would like to know if theres any build specially recommended for nuc7i3bnh

Also I would like to know if the resolution and hertz can be changed?

ie 4k 50 or Fhd 60......I have tried many roms before but no one covered this staff

Many thanks in advance.

Regards
[BLISS ROMS Development] kanttii:
On Surface Pro 3 Grub goes into touch mode for me without changing anything. All I need to do is

1. disconnect keyboard and reboot

2. Then a touch keyboard button appears on top right

3. Press that button and use its arrows to navigate and press enter

But if you see none of that, maybe the grub version doesn't support your touch processor/controller. Strange.

Now I assume you have a USB keyboard available.

Would you like to try booting Ubuntu 17.04 from a USB drive and testing if the grub it has supports touch?

If not, do you have space in your hard drive or SSD to install Ubuntu on for a test? If you have 8-12GB

1. please back up your data

2. install Ubuntu on a 8-12GB partition

Open the update tool and install all available updates, OR

3. Open terminal and run "sudo apt update"

4. Again in terminal, run "sudo apt dist-upgrade"

5. After you've installed updates, reboot and check whether grub supports touch yet

6. If not, try the Udoo build of Bliss. It has a different bootloader, rEFInd instead of grub, and that could work.. it's a maybe too, there are tons of different devices and not all are yet properly supported in Linux.

Here's how it looks for me:

https://i.imgur.com/xmHSscJ.jpg

---------- Post added at 13:37 ---------- Previous post was at 13:01 ----------

Try with this bleeding edge build if others don't work: https://downloads.blissroms.com/Bli...FICIAL-20170712-1941_k4.12-SP3_m17.2.0_01.iso

Changing refresh rate is not possible in Android as far as I know. It'll use the highest the screen supports. I just tried it with a few kernel command line options and they weren't respected in Android, it just stayed at 60hz. So if you have a TV that's 50hz, this will run at 50hz, and a 60hz tv Will run at 60hz. I tried this on 90, 100 and 144hz monitors too and it used the maximum available refresh rate the monitor has.
[BLISS ROMS Development] franzli:
Wow, that's interesting, I didn't know that some devices do have touch support on grub! I'd guess that must be some feature of the firmware of the particular device (apparently the surface tablets) to offer a keyboard even on the bootloader level. The closest I ever got are the two Dell Venue 8 Pro models I have which support touch in the BIOS/UEFI, but don't on grub. At last this allows changing the boot order between the android install, Linux and windows on the UEFI level, even though it's a but cumbersome.

On other devices I've tried, eg the Cube i7 Book, there no touch support in the BIOS at all, so in order to get there you always need a keyboard attached. I get around that by booting into Linux by default and I've got some shortcuts on the desktop for switching into win or android (using efibootmgr).
[BLISS ROMS Development] daspex:
Hi,

You can try the Refind bootloader wich is configurable easy with config file it is possible to enable touchscreen functionality...ask the google

Edit:it has a nice user interface with high customizable functions.
[BLISS ROMS Development] ubuntuh:
Hi everybody i have installed the latest build to my Asus Eebook x205ta and everything runs fine and smooth except 3 Bugs:

- Sound is'nt working (neather through headphones)

- Bluetooth is'nt working too

- the system reboots instantly after been woken up from sleep

anyone who is facing the same problems?

Processor:

Intel® Bay Trail-T Quad Core Z3735 1.33 GHz Processeur
[BLISS ROMS Development] electrikjesus:
If I remember correctly, the w700 uses the same MBR bootloader as the w500 I use to test on. If so, you can use the EasyBCD to enable "Metro" style boot, and then make sure the Grub config has Android as the default choice. Done & Done
[BLISS ROMS Development] electrikjesus:
I have started working on a minimal theme for rEFInd, you can find that work in progress here: https://github.com/BlissRoms-x86/bootable_newinstaller/tree/nougat-x86-oto/install/refind
[BLISS ROMS Development] NoyTheBiche:
Hi! Thank you for this great androidx86 rom ! ;)

Just one question, i want to download the latest .iso (with the 4.13 kernel) but i just want to update my pc.

Can i update my pc without formating my pc and lost my apps? just install androidx86 without formating my partition?
[BLISS ROMS Development] electrikjesus:
UPDATE - 07/28/2017 - New Bleeding-Edge Releases!!

I am uploading last weeks test builds for the bleeding edge builds, 32bit & 64bit .ISO's, kernel 4.13rc2, with all the usual patches. These builds also have updates for the USB installer so it will correctly write EFI boot entries. These also have the added grub options to try the different sleep & power button configs. (Add SLEEP=1 & DC2P=1 as grub options) BUT... you're gonnal have to use a build.prop editor to un-try them for now ;)

There's also bluetooth fixes in the kernels too - Bliss-v7.2-android_x86_64-OFFICIAL-20170719-1347_android-7.1.2_r27_k4.13rc1-bt_m17.1.5_pwb_01.iso & Bliss-v7.2-android_x86-OFFICIAL-20170719-1347_android-7.1.2_r27_k4.13rc1-bt_m17.1.5_pwb_01.iso

The other build being uploaded there is a kernel-4.9 test build for devices using an IPTS screen. Some of the newer SP4 screens have testes as not working, but others have reported it to be partially working with different IPTS screens (maybe older devices??) Just be warned, it may not work as you are hoping it will, so don't complain if it's not. - Bliss-v7.2-android_x86_64-OFFICIAL-20170721-1419_k4.9-ipts_m17.1.5_bt_01

Updates

Kernel-4.13rc2

Mesa 17.1.5

Bluetooth Fixes

Installer Updates

and as usual, there's is more, but I forgot...

Known Bugs:

- SetupWizard will crash if your device doesn't have working wifi. If you have this issue, please add "SETUPWIZARD=0" to your grub command in order to skip it.

- Changelog from AboutBliss won't work (I've given up)

- Bluetooth power cycling on some devices, or not working on some kernels.

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] electrikjesus:
I'm gonna inform you on a secret. In this very thread, lies all the lost knowledge of the ancients who worked on Android-x86 project before we came along. It is cleverly hidden though on the first page of this thread, and ONLY REVEALED once a user completes the quest of truly understanding all that is within the second post, their thirst for knowledge will be quenched.
[BLISS ROMS Development] daspex:
Hi,

Thank you very much for that great rEFInd config file.Will your version of rEFInd and the conf file also work with 32bit bliss and win10 ?

Edit:downloaded your last 32 bit bliss from today is it the version you mentioned last night?

Edit:Sorry i overread your update information posting.Will download and test at once..:))

And again thank's very much for uploading the ips version

Best regards
[BLISS ROMS Development] electrikjesus:
The IPTS build I mentioned last night is only x86_64, but it does support 32bit bootloader and userspace
[BLISS ROMS Development] dapo4friends:
It would seem that my last logged entry on page 68 has been forgotten about.. Anyways no problem, I'll stick with my windows and remix Os....

Thanks for the response so far
[BLISS ROMS Development] youling257:
4.13 kernel，please you enable es8316

-# CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH is not set

-# CONFIG_SND_SOC_INTEL_BXT_RT298_MACH is not set

-# CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH is not set

+CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH=m

+CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=m

+CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m

CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m

CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m

-# CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH is not set

+CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m

CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m

CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m

CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m

@@ -5143,12 +5152,12 @@

-# CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH is not set

-# CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH is not set

-# CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH is not set

-# CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH is not set

-# CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH is not set

+CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH=m

+CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m

+CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=m

+CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m

+CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m

CONFIG_SND_SOC_INTEL_SKYLAKE=m

CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m

-# CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH is not set

-# CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH is not set

+CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH=m

+CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=m

+CONFIG_SND_SOC_DA7213=m

+CONFIG_SND_SOC_DA7219=m

+CONFIG_SND_SOC_ES7134=m

+CONFIG_SND_SOC_ES8316=m

+CONFIG_SND_SOC_ES8328=m

+CONFIG_SND_SOC_ES8328_I2C=m

+CONFIG_SND_SOC_ES8328_SPI=m

-# CONFIG_SND_SOC_MAX98504 is not set

-# CONFIG_SND_SOC_MAX98927 is not set

-# CONFIG_SND_SOC_MAX9860 is not set

+CONFIG_SND_SOC_MAX98357A=m

+CONFIG_SND_SOC_MAX98504=m

+CONFIG_SND_SOC_MAX98927=m

+CONFIG_SND_SOC_MAX9860=m
[BLISS ROMS Development] electrikjesus:
BTW. If anyone has an extra Surface Pro 3 lying around, hit me up. I'm in desperate need of a good tablet for x86 testing ;)
[BLISS ROMS Development] electrikjesus:
Dude. to be open with you, I'd have to admit that out of the thousands of users, you were the only person with such issues, and that tends to mean that it was not intentional, but still a mistake. Please consider maximizing your information retention rate by taking the time to read through everything involved with the process. If you still don't understand some things, read through it again, and maybe follow a couple of the links to the Android-x86 project docs, or other community resources.

Good luck on your adventures :)
[BLISS ROMS Development] electrikjesus:
I will see what we can do
[BLISS ROMS Development] daspex:
Ok. Downloaded and installed it and this version is recocnizing much more to swipes and gestures as the bliss version i tried before.

In tthe system setting area i could pick functions but in the function menu i could not.At the homescreen if i swipe up the app screen apears and by swiping down the app menu closes but i cant start apps...so far the best result i ever had on this device.i'll try to change some different settings in the uefi....
[BLISS ROMS Development] electrikjesus:
It almost sounds as if it's recognizing your touchscreen as a trackpad..

Also, could you please remove the .zip file you attached for no reason?