yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] patriciogac:
I was able to download and run a HW info device. It shows :

Graphics: Intel Open Source Technology Center

GPU: Mesa DRI Intel HD Graphics (Cherrytrail)

OpenGL: OpenGL ES 3.1 Mesa 18.3.5 (git-eb334f34b7)

Vulkan support: Yes

Resolution 1280x800

Screen density 160ppi

Screen density (dpi): 160dpi (mdpi), 1280dpx800dp

Screen Size: 10.06in /256mm

Aspect Ratio: 16:10

Frame rate: 60Hz

Accelerometer and Gyroscope: Unsupported

Droid Info re3port:

DROID INFO REPORT

DEVICE

Model: FWIN232_PRO (android_x86_64)

Manufacturer: Fusion5

Baseband Version: Not Available

RIL Version: Not Available

Build Number: android_x86_64-userdebug 9 PQ2A.190405.003 eng.electr.20190525.202446 test-keys

Build Fingerprint: Android-x86/android_x86_64/x86_64:9/PQ2A.190405.003/electrikjesus05252024:userdebug/test-keys

Bootloader: unknown

Java VM: ART 2.1.0

OS Version: P (9)

SDK: 28

DISPLAY

Resolution: WXGA, 800x1280 pixels

Software Density: 160 dpi (mdpi)

Refresh Rate: 60 Hz

PROCESSOR

CPU Architecture: x86-64

Board: unknown

Chipset: ANDROID_X86_64

Cores: 4

Clock Speed: 480 MHz - 1920 MHz

Instruction Sets: x86_64

CPU Features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc aperfmperf nonstop_tsc_s3 pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb kaiser tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat

CPU Governor: powersave

Kernel Version: 4.9.153-blissified

Kernel Architecture: x86_64

GRAPHICS

Renderer: Mesa DRI Intel(R) HD Graphics (Cherrytrail)

Vendor: Intel Open Source Technology Center

OpenGL Version: OpenGL ES 3.0

RAM

Total: 3876 MB

Java Heap: 192 MB

STORAGE

Internal: 1.9 GB

External: 114.5 GB

FEATURES

Bluetooth: Yes

Bluetooth LE: Yes

GPS: Yes

NFC: No

USB Accessory: Yes

WiFi: Yes

WiFi Direct: No

BATTERY

Technology: Li-ion

Health: Good

SENSORS

Not Available

Created by Droid Info
[BLISS ROMS Development] electrikjesus:
These would be what you want to go to Google with. Search for those individually , adding Linux driver to the search
[BLISS ROMS Development] electrikjesus:
Can you please explain in a bit more detail what happened, what errors or shows in the terminal, etc.
[BLISS ROMS Development] patriciogac:
I downloaded the silead.ko file. But I dont know how to insmod it (Live USB version). Can you help me to load this module please?
[BLISS ROMS Development] wild_w1llie:
Build problems

Hello,

* I have followed the guide from github.

* My OS is Ubuntu 18.04 LTS

@ this step : bash build-x86.sh -r android_x86_64-userdebug

I first got this warning followed by a crash :

find: ‘vendor/bliss_priv/proprietary/houdini’: No such file or directory

WARNING: device/generic/x86_64/bliss.dependencies file not found

find: ‘vendor/bliss_priv/proprietary/houdini’: No such file or directory

I was able to bypass it by copying the houdini files from vendor/x86 to my vendor/bliss_private/propreitary folder.

Next error was:

Setting up Proprietary environment for: android_x86_64-userdebug

WARNING: device/generic/x86_64/bliss.dependencies file not found

followed by the error :

packages/apps/SettingsIntelligence/Android.bp:20:18: unrecognized property "platform_apis"

Which I could bypass by commenting out the line : //platform_apis: true, in the Android.mb file in SettingsIntelligence.

(I realize this is very bad practise)

After building for ~60minutes I got the following error:

(It installed all the necessery files and started lunch)

[ 75% 3/4] glob kernel/generic/x86_64/arch/x86_64/include/**/*

ninja: error: '/linux/build/bliss/out/soong/.intermediates/packages/apps/SettingsIntelligence/SettingsIntelligence/android_common/proguard_dictionary', needed by '/linux/build/bliss/out/target/common/obj/APPS/SettingsIntelligence_intermediates/proguard_dictionary', missing and no known rule to make it

15:06:42 ninja failed with: exit status 1

When I look in my out dirr I cannot find any proguard_dictionary folder, I have tried to search forums (including this one) but I cannot find any solution to this.

*Edit I also forced resync a few times just to make sure everything was downloaded correctly

If anyone have tips I would be very thankful :)

Best Regards
[BLISS ROMS Development] electrikjesus:
For starters, that was Android-x86's houdini that you grabbed there, and we don't use that. We use vendor/bliss_priv now to grab houdini and widevine from ChromeOS. You must have missed the step where you need to create the source & proprietary folders in bliss_priv for it to work

As for the issue with SettingsIntelligence, I thought I fixed that in the source, because it's building fine on my local machine. I will have to sync up on the Bliss build server to see if I'm missing anything there. I'd doublecheck that you have the right remote/branch checked out on your side in the meantime.

Thanks!!
[BLISS ROMS Development] electrikjesus:
That's not gonna work. We have to build it into the OS from source. So please share the source of your silead.ko file and the drivers.
[BLISS ROMS Development] DoughMucker:
I suspect he followed the steps. I'm trying to compile a Surface 2016 build and I know I created the directories and also get the same error:

find: ‘vendor/bliss_priv/proprietary/houdini’: No such file or directory
WARNING: device/generic/x86_64/bliss.dependencies file not found
find: ‘vendor/bliss_priv/proprietary/houdini’: No such file or directory

But I stopped at that point and came here to see if someone had a solution.

It appears the proprietary code was downloaded to vendor/bliss_priv/ but not extracted to source or proprietary directories. I did start to look through the bash script to see what is supposed to extract the code, but my coding skills are extremely basic and it's late so I'll try later. Sleepy.

Edit:

The proprietary code wasn't downloaded afterall...

vendor/bliss_priv/setup.sh was getting an error on line 46 (cd "$SOURCE_DIR") which turned out to be "cd /source" when I ran the script. Since "/source" doesn't exist, I changed line 46 to "cd source" and ran the script again....the proprietary code was downloaded. But the script failed at extracting the proprietary code at that point. I think the relative vs absolute paths are messed up in the script. I'm off to work and can't work on it now, but will look at it later.

As always, thanks for Bliss!
[BLISS ROMS Development] Swehub:
I have fixed Bliss OS with latest version of Magisk Version: v20.0 och Magisk Manager Version: v7.3.5. It is a great hobby for me, totally unnecessary and waste of time :) Bliss OS works well with IPTV.

https://www.youtube.com/watch?v=mCve0PE4Lg4

Regards,

Swehub
[BLISS ROMS Development] Apih95:
But how to install magisk?
[BLISS ROMS Development] wrwolf2:
Bliss OS 11.10 x86_64

hi there !

good to see you're making progress on this project, noticed you changed grub.cfg file. is there a wiki/doc that's also documenting changes for grub.cfg ?

take care,

marc
[BLISS ROMS Development] Mohamed Sallah:
Hey Devs , thanks for your great work

i've been a huge fan of this project since the beginning

just wanna ask if you are planning to update the android version to 10 anytime soon

thanks <3
[BLISS ROMS Development] DoughMucker:
Still new to compiling and trying to debug my issue....

When I

bash build-x86.sh -r android_x86_64-user

Then it seems this commit creates blissos/p9.0/source (and proprietary) instead of /blissos/p9.0/vendor/bliss_priv/source (and proprietary). It causes the script to fail at one point.

If I comment out that line (I've created the directories) and try again... when vendor/bliss_priv/setup.sh is called in android.mk, the wrong variable is being passed:

++ echo 'Downloading files...'
Downloading files...
(Debugging info for downloading is commented out as I've downloaded it and commented out the downloading command)
++ cd android_x86_64-user/source
vendor/bliss_priv/setup.sh: line 46: cd: android_x86_64-user/source: No such file or directory

It seems as though the buildvariant is being used instead of the directory. I can't figure this one out yet.

I'm guessing somebody made some changes to the code that now cause it to fail for new compilers (no houdini), but it works for you guys as you already have it downloaded.
[BLISS ROMS Development] wild_w1llie:
Hello eJesus,

Maybe I missunderstod the instructions, I created those two folders and expected houdini to be installed when i ran the -r flag?

Since they were never installed i manually moved them.

I'm away on a trip this week but I'll check when i get back :)

Thanks for the help!
[BLISS ROMS Development] eatzum:
Hi I apologize if this is the wrong place to ask this, but I've tried searching and have no luck. when i try to install bliss os on an old HP pc. i get a message that says no IRQ vectors for handling and nothing else happens after that. the mobo only supports legacy bios not sure if that is the issue i've tried both 32 bit and 64 bit and both have same issue. i tried running on a newer laptop and it worked perfectly. not sure what the issue is. any help is appreciated.

thank you
[BLISS ROMS Development] ElfinJNoty:
Please post written steps you took in order to achieve this.

We know it is possible, but nobody has been willing to write the process out for other to reproduce.

We would potentially add this to our docs.blissroms.com and give credits for tutorial/instructions.

Our userbase, and the Android-x86 community as a while would benefit greatly from this ?

---------- Post added at 01:43 AM ---------- Previous post was at 01:35 AM ----------

We began this project on Nougat as a base

We have bumped to latest available Android version with each of it's releases since

It is safe to assume what our plans will be for Android 10

It is not appropriate to ask for an ETA for development

We make official announcements for each public release

Stay tuned

---------- Post added at 01:45 AM ---------- Previous post was at 01:43 AM ----------

docs.blissroms.com

>Troubleshooting section has example grub boot entry options
[BLISS ROMS Development] Apih95:
Is there any systemd-boot configuration available ? I would like to try on my archlinux desktop :)
[BLISS ROMS Development] bfmetcalf:
I have my Arch Linux boot go to grub and grub go to Bliss. Works well and was easy to setup. Don't have my laptop here or I would give you my config I used.
[BLISS ROMS Development] Apih95:
Ahh your Arch use grub . I never use grub on my Arch box coz it is always failed for me hahahaha. So i rather use systemd-boot instead. If you know what parameter need to be adjust on systemd config for BlissOS do share and let me know :highfive:
[BLISS ROMS Development] bfmetcalf:
No, my Arch uses systemd-boot ( I think, may be syslinux also, been a while since I messed with the boot part). So I basically have a bliss entry in systemd-boot that boots grub which then boots Bliss.
[BLISS ROMS Development] Apih95:
Nice ! Would you share later ? :fingers-crossed:
[BLISS ROMS Development] bfmetcalf:
I'll try to remember to check it tonight. I know that I found how to do it on google somewhere.

you could try doing this config and see if it loads grub for you. Look in the /EFI folder to make sure that grub.efi is correct. Should be all that is needed to get it to chainload I do believe.

esp/loader/entries/Bliss.conf

title Bliss
efi /EFI/grub.efi
[BLISS ROMS Development] Apih95:
Wow..I never done this before..chainload into another bootloader like grub or etc. Thanks for this ! :good:
[BLISS ROMS Development] electrikjesus:
We adopted that change directly from upstream Android-x86 projects bootable/newinstaller repo. Check there for any additional documentation on the change.
[BLISS ROMS Development] electrikjesus:
Would you be able to create a pull request for that change in https://github.com/BlissRoms-x86/vendor_bliss_priv ?

That second error has a fix that was pushed this morning. Please resync that repo and try again.

Thank you
[BLISS ROMS Development] electrikjesus:
Currently, no. I am looking for further information on how to add systemd support though if you happen to know of any good sources of info.
[BLISS ROMS Development] wrwolf2:
HI !

thanks' a lot for your kind reply , please allow me to add we simply intend to swap the first menu entry with the second one , and on the main screen for grub 2.

We noticed Wi-Fi and other features aren't working when selecting first menu entry and then booting up with it, though we also seem unable to use internet connection while testing " vulkan option " [ advanced menu. ]

we made attempts to read and learn about grub.cfg and when we discovered there were substantial changes in the code / script ( grub2 is one of those " things " we never managed to study and understand fully , we feel it is one of those " ESSENTIALS " and ever so easy to understand for everyone else , though making grub2 a obstacle for US as well as an option we'll never find our own way around folders , and " bootloaders " within EFI partition. ]

take care,

marc
[BLISS ROMS Development] g2mantap:
just to update BLiss OS 11.10 on my Asus T100TA as my main OS

upgrade from bliss 11.06....last time time, everything is ok except file manager and firefox browser but after upgrade to 11.10...touchscreen no longer working, had to use touchpad.....menu got flickering and wifi cannot be detected

hope can repair these problem

---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
[BLISS ROMS Development] Mishal Mohamed:
Just tried the latest build and HOLY SH*T its the fastest Android-x86 OS iv'e ever experienced!

Games like PUBG ran in full 60FPS at 1080p which blew my mind, because PrimeOS and PhoenixOS never ever reached this level of performance (atleast for me though), they barely reach 40FPS in 720p resolutions.

Expecting a keymapper in the future updates, or is there a keymapper already compatible with Bliss?
[BLISS ROMS Development] DoughMucker:
Just created a pull request. My first! So, I hope it's okay. (Well, it's my 2nd, but I'm not going to count some minor XML changes for Kodi).

Thanks for the fix to the second error. I'm building again now and it hasn't made it this far before (6% done). I'll join you in Telegram if I have any other problems while trying make an IPTS build.
[BLISS ROMS Development] electrikjesus:
I saw your pull request and I will likely test it out this week sometime. If there's anything else needed, I'll just amend your patch with them ;)

Thanks again, and if you find me on Telegram, there's a few others working together on the IPTS builds as well as others. I could connect you with them if interested.
[BLISS ROMS Development] DoughMucker:
I had let my build run over the night and woke up to the same error you had.
[BLISS ROMS Development] push911:
what android / bliss os would you recommend on HP 10-P018WM Detachable Laptop, 10.1 IPS Touch Display, Windows 10 Home, Intel Atom X5-Z8350 Processor, 4GB Memory, 64GB eMMC?
[BLISS ROMS Development] electrikjesus:
I will look into this new build issue then. Likely something that needs updating in Blissify app still
[BLISS ROMS Development] bloadstar:
Tried doing a search through the thread and it didn't work out so I'm going to ask the question and see if someone can either help or point in the right direction.

Installed bliss os x86 (version 11 I believe). It's on an asus t200ta transformer book.

WiFi randomly shuts off and won't turn back on. Also it will randomly freeze at any given time. Weather it's at initial start-up once the lockscreen has loaded or if the device was in use or even a minute or two after rotation. It'll just randomly freeze.

Using the taskbar homescreen thing for the launcher glitches out and causes the screen to flicker, being black for 2-10 seconds each flicker. Ended up using the stock launcher because it doesn't glitch the screen.

Update: been using "old mod prop" mode for literally 20 minutes and no issues with WiFi or freezing. So I'm leaving this post up in case anyone knows whether this is the confirmed fix or if there's something else I should try.

Update #2: no chances with "old prop mode". Screen flickers. WiFi not turning on.
[BLISS ROMS Development] Younes_vd:
Hello there. I had a question if u don't mind.

How do you play pubg on bliss os without key mapping and mouse support.??

I mean it doesn't have key mapping tools so how do you use keyboard and mouse???
[BLISS ROMS Development] bloadstar:
[youtube]OAxFmLyQuXo[/youtube]

Took a video of the issues I'm having on an asus t200ta.

If anyone could help it would be greatly appreciated.

This happens on both modes for the bliss os
[BLISS ROMS Development] Younes_vd:
hello guys I just tried to install bliss os using androidx86 installer an it came up with this erro

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

Installer Directory:C:\Users\YOUNES\Desktop\Androidx86-Installv26.0003

Installer Version:2.6.0.0

Secure Boot ... Disabled

Manufacturer: LENOVO

Model: 81BF

Product: LNVNB161216

BIOS info:

LENOVO - 1

6JCN31WW

INSYDE Corp. - 56511031

Available GPU(s):

GPU: Intel(R) UHD Graphics 620

GPU: NVIDIA GeForce MX150

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

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

OSVer: Microsoft Windows NT 10.0.18362.0

OperatingSystem Version ... ok

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

System Firmware: UEFI

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

====Install Started on 10/25/2019 12:33:23 PM====

-ISO File: C:\Users\YOUNES\Downloads\Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso

-TargetDrive: I

-UserData: 33512489

-Setup Directories...

-Folder Created: I:\AndroidOS

-Extracting ISO

#Launch:C:\Users\YOUNES\Desktop\Androidx86-Installv26.0003\7z.exe x "C:\Users\YOUNES\Downloads\Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oI:\AndroidOS

#Launch:C:\Users\YOUNES\Desktop\Androidx86-Installv26.0003\7z.exe e "C:\Users\YOUNES\Downloads\Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso" "boot\grub\grub.cfg" -oI:\AndroidOS

-Creating Data.img

#Launch:C:\Users\YOUNES\Desktop\Androidx86-Installv26.0003\dd.exeif=/dev/zero of=I:\AndroidOS\data.img count=33512489

-Initialize Data.img

#Launch:C:\Users\YOUNES\Desktop\Androidx86-Installv26.0003\mke2fs.exe-F -t ext4 "I:\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 ... I:\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

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

what is the problem ? how can I solve this?

I did it for second time and here is the log (attached file). this time installation got finish but when boot it up it doesn't work.:crying:

oh and also if I install it through usb drive when it asks to format the drive which of them should I chose ext4 or ntfs? which is better?
[BLISS ROMS Development] bloadstar:
QUOTE=Younes_vd;80664359]oh and also if I install it through usb drive when it asks to format the drive which of them should I chose ext4 or ntfs? which is better?[/QUOTE]

I can't say anything about all the other stuff. My assumption would be that it isn't a free partition you're trying to install to if it's saying drive path occupied.

If you're installing through the USB id say to format the specific partition to ext4. I tried under ntfs and fat32 and I had a storage issue where I only had like 1gb free for some reason. After research I found out it has to be ext4 because that's what Linux uses and android is based off Linux. So try ext4 so you hopefully won't have a storage issue.
[BLISS ROMS Development] IamTheBRAVE:
For lockscreen, try using spacebar to unlock or disable it entirely.

For wifi, verify that your wifi on\off button on the keyboard is turned on and tick the option "turn on wifi automatically" in advanced menu.

I had the same gliches, that's how i fixed them on mine. Hope it helps
[BLISS ROMS Development] bloadstar:
Alright I'll try after work and requote you if anything. Thanks for your help.
[BLISS ROMS Development] IamTheBRAVE:
You are right. The install tried to create a boot directory but found one already exists (another OS using the partition). [MENTION=7567843]Younes_vd[/MENTION] :

Here is what you need to do:

-create a separate partition ( don't have to format it right away)

- turn off the computer and boot from usb, start the install.

- when asked format to ext4 and install.

It should work.
[BLISS ROMS Development] electrikjesus:
Please read the last few update posts again, slowly. They're linked from the third post on this thread
[BLISS ROMS Development] electrikjesus:
Please click the Clean Up button before trying to install again.
[BLISS ROMS Development] electrikjesus:
Announcement - Community Builds

First, the bad news...

Since my free time has been shorter and shorter these past months, I haven't had the time to devote what is needed for this project to keep up, so I am looking for help from the community in order to spread some of this FOSS love ;)

If you are building Bliss OS, for whatever reason, personal, hobby, work, tinkerer, etc. I urge you to join our Bliss OS telegram threads, and work along side a few other community members and myself in order to help this project grow and become a truly Blissful experience. We have a number of people already who are building for the various Surface devices, and I am helping as many as possible learn the ropes. All we ask for is a will to learn, and the drive to keep at it.

And now for the good news ;)

On the Bliss OS side of things, we are also moving forward with a new website ( https://blissroms-x86.github.io ) and we are starting work on Q-x86 along side the Android-x86 team. I figured this round we could work a bit harder at combining our efforts ;)

Manifest for the bringup for Bliss OS Q builds are up and can be found here: https://github.com/BlissRoms-x86/manifest/tree/q , and yes. it's booting ;)

And the manifest for Android-PC - Q-x86 (AOSP + Android-x86 patches) is also up and ready for builds: https://github.com/Android-PC/platform_manifest/tree/q-x86

Thanks again XDA peeps, you all ROCK!!

https://t.me/blissx86
[BLISS ROMS Development] Younes_vd:
Hello again thank u all for your helps.

I cleared the android as you said and installed it again but its not working when I press bliss os to boot it says(detecting bliss os found at sda5) and stuck in here. Thats all. By the way I also tryed to test the live mode but even in live mode it has the same problem and stucks at the same place(detecting bliss os found at sda5). I'm really disappointed with my laptop I don't know whats wrong i payed so much money to buy it for but nothing is compatible with it. Ive been trying different OS like prime os and this one. None of them work. Only phoenix os installer works for me which is very slow and not smooth. :crying::crying::crying: