yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] Spinoni31:
Hello, I've managed to do a repo init in the folder where i want to store my project and i did a repo sync during the night.

this morning when i tried to compile the os with the instructions from https://github.com/BlissRoms-x86/manifest I've got another error. This is the first lunch command I've done in the morning:

android @ android-build-environment: ~ / bliss-x86 $$ lunch bliss_android_x86-userdebug
ls: Unable To Access 'device / * / android_x86 / bliss.mk': File or Directory Not Existing
build / core / product_config.mk: 244: *** Can not locate config makefile for product "bliss_android_x86". Stop.
ls: Unable To Access 'device / * / android_x86 / bliss.mk': File or Directory Not Existing
build / core / product_config.mk: 244: *** Can not locate config makefile for product "bliss_android_x86". Stop.
your device can not be found in device sources ..
found the android_x86 device repo
wrote the new roomservice manifest
syncing the device config
Fetching project BlissRoms-Devices / android_device_generic_android_x86
% Total% Received% Xferd Average Speed ​​Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 -: -: - 0:00:01 -: -: - 0
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
remote: Counting objects: 123, done.
remote: Total 123 (delta 1), reused 1 (delta 1), pack-reused 121
Receiving Objects: 100% (123/123), 16.12 KiB | 8.00 KiB (s), done.
Delta resolution: 100% (72/72), done.
From https://github.com/BlissRoms-Devices/android_device_generic_android_x86
* [new branch] n7.1 -> github / n7.1
* [new tag] android-x86-6.0-r1 -> android-x86-6.0-r1
Fetching projects: 100% (1/1), done.

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

============================================
PLATFORM_VERSION_CODENAME REL =
PLATFORM_VERSION = 7.1.2
BLISS_VERSION = Bliss-v7.2-android_x86-UNOFFICIAL-20171031-0801
BLISS_BUILDTYPE = UNOFFICIAL
TARGET_PRODUCT = bliss_android_x86
TARGET_BUILD_VARIANT = userdebug
TARGET_BUILD_TYPE = release
TARGET_BUILD_APPS =
TARGET_ARCH = x86
TARGET_ARCH_VARIANT = x86
TARGET_CPU_VARIANT =
TARGET_2ND_ARCH =
TARGET_2ND_ARCH_VARIANT =
TARGET_2ND_CPU_VARIANT =
HOST_ARCH = x86_64
HOST_OS = linux
HOST_OS_EXTRA = Linux-4.10.0-37-generic-x86_64-with-Ubuntu-17.04-zesty
HOST_BUILD_TYPE = release
BUILD_ID = NZH54D
OUT_DIR = / home / android / bliss-x86 / out
============================================

Is there a problem with the repo or is it a problem of my pc. if it is my pc, what do i need to do to compile this correctly?

Thanks in advance for the reply, Spinoni31.

P.S: As I've said before in a previous post this error message was translated with google translate, as I'm Italian.
[BLISS ROMS Development] electrikjesus:
That doesn't look like an error from what I can see. It eventually downloaded the configs and started the process with it
[BLISS ROMS Development] Spinoni31:
I've tried to do another repo sync and re-did the . build/envsetup.sh and lunch bliss_android_x86-userdebug command, but this thime it shows this error when i do the lunch command:

android@android-build-environment:~/bliss-x86$ lunch bliss_android_x86-userdebug
WARNING: device/generic/android_x86/bliss.dependencies file not found

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.2
TARGET_PRODUCT=bliss_android_x86
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
TARGET_CPU_VARIANT=
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.10.0-37-generic-x86_64-with-Ubuntu-17.04-zesty
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NZH54D
OUT_DIR=/home/android/bliss-x86/out
============================================

I've notice that it said that there were "bliss.dependencies" missing from my system. how do i solve this?

EDIT:

By following android-x86 tutorial (http://www.android-x86.org/getsourcecode) by doing the commands in the "Bulding Directly" Section, everything started to work and now the system is being built. After everything is finished I'll add another edit to this post to show my success/failure in the build.

Anyway, thanks for the big help so far.

Thanks, Spinoni31.
[BLISS ROMS Development] electrikjesus:
That is just a warning for devices that need a bliss.dependencies file. This is not one of them, so it should build without it
[BLISS ROMS Development] ElfinJNoty:
It blows my mind.... The lack of donations to the team in the past year :( considering just how many devices Bliss-x86 works for, as well as all the other devices supported under Bliss OS development efforts.

Our team covers operating costs out of our own pockets, with Bliss-Managrment Team members making consistent & substantial donations to cover expenses. And we have received criticism for attempting to utilize fund raising campaigns..... And then we see the criticisers doing the same thing later on :confused:

Yet we see a lot of Bliss downloads per month. Which let's us know just how much the teams efforts are utilized.

We definitely appreciate our users and their efforts to contribute files and sources for continued development. We absolutely enjoy the fact that our sharred efforts are being used. This is our passion!

But [MENTION=928479]electrikjesus[/MENTION] is absolutely correct: it is very difficult to make everything work to everyone's satisfaction without test devices.

We don't ask for donations, but as a reminder, the teams PayPal account is available in the OP and on our website for anybody who is willing/wanting to contribute.

If a monetary contribution is not possible:

Please help promote the Bliss-x86 project to raise attention and pull in more users and/or devs in hopes that we can continue to make this project more compatible and lend assistance in development efforts.

Thanks
[BLISS ROMS Development] Tonio1987french:
Bliss-v7.2-android_x86_64-OFFICIAL-20171024-1354_k4.12_cb_ipts.iso

On Lenovo Miix 320

No rotation

No level batery

Screen is black when off but not shutdown

No webcam

No Sdcard

The rest works very well, THANK YOU
[BLISS ROMS Development] 2Pix:
Hi, just a small report:

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso

Tested on Lenovo x201T "outdoor" (no finger touch, only wacom pen), X201T & X220T "Multitouch" - no touch/pen support, no autorotate. On the other hand, the rest looks to be working OK.

If i can be of any help with some logs etc you might need...

BIG minus is that i could not figure out a way how to disable the annoying PC speaker bleep whenever i pushed some "enhanced" (volume up and down etc) key on the keyboard
[BLISS ROMS Development] z750leovince:
i need help for installing bliss in surface book...

for modified system.img for install ips driver, need install biss on my book? and when install i modified img with linux?
[BLISS ROMS Development] :
True, i understand that, but i mean if you can make a guide about how every x86 machine owner can add his own Driver, or my friend, if you can develop an app for Android that can install the Drivers through it, like Windows, ist just an idea
[BLISS ROMS Development] dedaol:
Test on Teclast X80h baytrail tablet

Hello,

I am doing a test on a Teclast X80h baytrail tablet. I copy the content of the ISO to a pendrive and UEFI boot it. That part works, I get the Bliss Grub menu.

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso : it detects the partition (/dev/sda1) just fine, then the built-in DSI screen goes blank when DRM kicks in. If I plug in the HDMI display, the DSI stays blank all the time, and I get a text shell prompt on it that I can play with.

It is expected by me, as mainline v4.4 never received the necessary patches to make that DSI screen work. The patches posted by Hans de Goede on 2017-02-28 and 2017-03-01 and most likely needed the patch by Ville Sirjala on 2017-06-06. All patches are here: https://git.kernel.org/pub/scm/linu...rs/gpu/drm/i915?h=next-20171018&qt=grep&q=DSI

The DSI screen finally works fine under linux with v4.14-rc5 (most likely any v4.14), but I know this kernel is not (yet) OK for Android. With v4.13 under linux the DSI screen freezes when I try to change mode (e.g. rotate, or switch between graphical and text console).

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso : The same DSI screen behavior as above. Again, it is expected, as this DSI screen got supported at around kernel v4.12. But dmesg looks better, it detected the built-in audio, axp288 based power chip for battery info (this is again the work of Hans de Goede, thanks to him).

Bliss-v7.2-android_x86_64-OFFICIAL-20171016-2034_k4.12-atsp.iso: This looks promising! The DSI screen survives the DRM switch, and even autorotates fine as I rotate the tablet. Wifi sees networks, but I couldn't connect to my home network (yet). After finally got the wifi connected, the screen went blank, most likely it froze. Further testing is needed.
[BLISS ROMS Development] Spinoni31:
Hello, It's me again.

After trying with the make command on the "building directly" section of android-x86 page the build process failed. Because i then got problems with the jdk i re-installed the system (this time leaving only the kde plasma D.E.) and re-downloaded everything like the way it was before and then I found out how to use the lunch command (Because i thought that after the lines describing the arch that he was going to use to build the project it was going to start building immediately) and then, following your manifest repo guide i did the mka iso_img command, but even this command failed.

Here are the last lines of script that i got:

[ 32% 12040/36682] build /home/android/bliss-x86/out/target/common/obj/JAVA_LIBRARIES/sdk_v16_intermediates/classes.jack
ninja: build stopped: subcommand failed.
build/core/ninja.mk:152: set instructions for "ninja_wrapper" failed
make: *** [ninja_wrapper] Error 1

While building until this point i noticed that there were a lot of warning messages, with some of them talking about some "deprecated API".. Is this normal?

Can someone help me through the build process?

Once again, i thank everyone in advance.

Thanks, Spinoni31.
[BLISS ROMS Development] magicfajita:
Hello, I am using the bleeding edge iso for surface pro, but I am not able to boot. Every time, the installation is successful, and I try to boot to Android OS and it gets stuck on "Detecting Android x86..." I saw a post for this earlier in the thread but no one supplied any fixes for it. Secure boot is disabled.
[BLISS ROMS Development] cai_miao:
Sorry man, that guy suggest to add my instruction didn't clarify that those steps are for Surface Books...

Firmware 0078 is symlink-ed by default so you should modify nothing and use it directly.

I think you should edit this again...
[BLISS ROMS Development] electrikjesus:
This is my issue, I do not know what your needs are for me to edit anything. I do not have any of these devices to work with. I'm coming really close to shutting down this project over all this. Just so you all are aware
[BLISS ROMS Development] ElfinJNoty:
:eek:

---------- Post added at 10:56 AM ---------- Previous post was at 10:52 AM ----------

All users:

We are unable to "fix" or include operation features for specific devices at this time. ESPECIALLY when we do not posess that device to use for testing and debugging.

Very few people are providing links to commits as they request things, and are even less often providing logs for us to see when and why something isn't working.

The current builds provided are as-is, and while we continuously attempt to improve on the project.... The point that we cannot fully support devices that have specific and unique drivers is appearently not being received correctly.

Please continue to report how your drvices are running with Bliss OS installed. However, do so without any expectations or entitlement to have further improvements to your specific device. [MENTION=273759]elect[/MENTION]ikjesus has been working very hard to include more drivers/fw's/patchsets to improve compatibility. But he is doing so without test devices and dedicating a lot of time towards bringing Bliss Oreo to x86 devices.....

Feel free to donate a device, provide documentation and links to a available sources, and provide logs. But please do so without improper expectations.

Thanks,

Team Bliss
[BLISS ROMS Development] cai_miao:
Sorry man, I'm just pinging you for clarifying :

the link you were asked to put previously, are only suit for Surface Book users, and should be clarified to prevent useless feedbacks like that ONE.

I'm really appreciate for your work,

but I can't really do anything since I'm in Asia and lacking of coding knowledge...

I really know how hard for a community contributor to maintaining such a big project,

it's really hard to fit everyone's need...

I'll try to get in touch with the Japanese man who modified the IPTS build, that's one of few things I can really do.

All the guys, please try first before you ask, provide technical details if you can,

and cherish every independent developer.
[BLISS ROMS Development] Mohamed Sallah:
Thanks !

Don't shut this project please !

see , me and i'm sure a lot of other people , appreciate your work much more than you think

and i'm sure a lot of people like me want to support you by providing resources and test devices or donate

but , even if i want to , i can't , i'm in far distant from you , i'm student so i don't have money , i don't have any kind of credit card to donate ,

so , the maximum support i can provide is clicking the thanks button or saying thank you in comment

i know that you tired from negative complains about compatible and you do all what you can to support much devices and you don't even have a test unit , but don't give up , and don't stop this project , there is a lot of people appreciate your work and love it more than you think

me and others are really appreciate your work , but we don't have any ability to support but saying thanks

so , Thanks !
[BLISS ROMS Development] electrikjesus:
No, I really don't want to shut this thing down. This project is not even close to what I envisioned for it a couple years ago. And yes, I do get stressed out though over it. And the past couple days for me have been spent chasing my tail, trying to get Oreo to boot. Every time I think I'm close, I realize just how far away I still am from it. It's a little depressing. Maybe more so than the IPTS woes we have.

I apologize to the community for bearing my heart about things. But on the bright side, this is also reassurance for you all that I'm not some kinda robot working in the Bliss Dungeon for nand chips ;)
[BLISS ROMS Development] EximusCode:
Hey, just had a bit of a problem when installing on the Lenovo Miix 510. I used the Easy method from the 2nd post but the InstallerV2.5. I have changed around the boot menu order, disabled the secure boot and everything. Everytime I get to the Grub, it asks for what OS to boot, I select Android-x86 and it gets stuck on Detecting Android-x86... and keeps loading dots ( . ). I let it run for 30 mins now and still nothing. Some help please?
[BLISS ROMS Development] electrikjesus:
Please show us your grub.cfg along with info of where you installed it and what build you tried to install.
[BLISS ROMS Development] ElfinJNoty:
We stopped feeding you nand chips a long time ago... It's a wonder you've survived :p

Keep up the good work [MENTION=928479]electrikjesus[/MENTION]

The Bliss Family and it's users for sure appreciate you and your continued efforts!
[BLISS ROMS Development] EximusCode:
GRUB: Is the grub.cfg in the AndroidOS folder? If so, there is no grub.cfg...

LOCATION: C:\AndroidOS *because I can't seem to shrink the volume of the c drive*

ROM: Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso
[BLISS ROMS Development] electrikjesus:
OK, try this. reboot, and when it gets to the boot menu with Bliss on it, hit "e", and add "nomodeset" to the grub command, right before the word "quiet".

Let us know if that boots for you. (P.S. This is the first step in troubleshooting. Also linked in the second post "Android-x86 project's installation guide.")
[BLISS ROMS Development] EximusCode:
Ok, I tried this twice (... nomodeset quiet) and (... nomodesetquiet) both give me the same detecting Android............ etc.
[BLISS ROMS Development] lfom:
You cannot move or rename the folder with the Bliss files on your C: drive, it must be in the root of your drive. This error means it cannot find one of the files to start booting.

To resize your drive, you must first defrag the free space using an utility. I also had to disable the virtual swap memory in Windows and delete the hibernation file to make it possible to resize the disk. Good luck.
[BLISS ROMS Development] IcedCube:
Firstly, a big thanks for showing the x86 platform some love in regards to Android. I have a MeeGoPad T09 which is an Atom-based PC and I have been able to boot Bliss-x86 on it using a USB key install. It's slow, but it works.

The only issue so far is there seems to be no support for the Intel Atom Braswell/CherryView SDIO bus. Would this be able to be added in the kernel? My device has a Broadcom WiFi adapter that sits on this bus. The eMMC was detected without problem (which uses the SDHCI bus IIRC). Also, is there a way to disable the auto-rotation to lock it into Landscape? Having apps randomly turn the screen because they feel like it is annoying when you're using a keyboard and mouse. Clicking Auto-rotate seems to change the setting from auto to portrait only.

EDIT: Latest build. Kernel 4.9 x64.
[BLISS ROMS Development] electrikjesus:
Then it might be that your device needs either a 32bit build or something else. Have you tried any of the 32bit builds yet?
[BLISS ROMS Development] electrikjesus:
I know the kernel support is mostly there for SDIO, but not sure if we're missing any patches for it or if Android-x86 even supports it. I know there is a ton of hardware that doesn't work right now because of this (my dell Venue pro 8 3845 for one), and would love to figure it out, but I'm not that knowledgeable in the areas needed to make that work right. I have learned a lot so far, but have not gotten there yet ;)

Rotation can be set to stick using an app from Play store normally. There have been many suggested in this thread in the past, but I tend to stick with Set Orientation, by Eyes-Free Project.
[BLISS ROMS Development] vanhels:
iso rom 32Bits Bliss

Hi, could you indicate the download link of the 32-bit iso for bliss,

Regards,
[BLISS ROMS Development] EximusCode:
Same here? I don't seem to be able to find the 32-bit download...
[BLISS ROMS Development] ElfinJNoty:
We will no longer be compiling 32 bit builds for the public. But our source is available if others wish to do so for their devices. And if someone does decide to compile 32 bit builds and share with the community, please feel free to contact us. However, we will not be officially supporting these efforts. More information about that can be found @ blissroms.com

As far as where to find 32 bit builds of Bliss-x86, if you click on the link in the OP under Downloads, archived files, there are several previous versions available to use for a testing purpose. If you want to try to use those files to verify weather or not a 32 bit build will work on your device, please report your findings.

From info gathered here in the forum: if a device will boot a 64 bit build of Bliss from a USB live boot, then it ought to boot from a local drive. There may also be other bugs or things causing your device not to boot Bliss due to the builds being out of date and not current with recent works of [MENTION=928479]electrikjesus[/MENTION]. Support should not be expected while running any archived builds. So this route of testing may not be beneficial, but is worth a shot to narrow down things if you choose.
[BLISS ROMS Development] EximusCode:
I don't get what I'm going wrong... I am able to run Bliss 64bit off my USB but the setup application keeps failing. And even trying to install it after trying to boot from usb, I can't see my partition I created. Is it because of the Linpus Bootmanager? When I look at tutorials on YouTube they seem to have a Windows 98 sortof UI with the Android-x86 in the lower right corner...

All I want to know is how to install to the Harddrive partition, I can only see my USB...
[BLISS ROMS Development] electrikjesus:
Like I stated in this post, it could be sdio or some other HDD controller related issue. Maybe even acpi

https://xdaforums.com/android/software/x86-bliss-x86-pc-s-t3534657/post74399788
[BLISS ROMS Development] maskes:
Hi,

I just installed Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9 to my Chuwi surbook and it runs great except from :

1. Touch screen. Chuwi Surbook has a Goodix TouchDriver

2. Bluetooth.

It work for about 30'' and then it turn off by itself and not turning on again unless I reboot it.

In these 30'' I manage to pair a couple of devices (speaker, headphones, mouse)

3. Rotation. which I don't mind

Is there anything a I can do to make it work.
[BLISS ROMS Development] EximusCode:
D e l e t e d
[BLISS ROMS Development] Leone/kyleproxx:
What is the difference with the Bliss-v7.2-android_x86_64-OFFICIAL-20171103-1727_k4.12_oto-installer.img file and Bliss-v7.2-android_x86_64-OFFICIAL-20171103-0937_k4.12_oto-installer.iso file

Why is there a img file now
[BLISS ROMS Development] jaffer707:
What about Sony Xperia D2502 dual???
[BLISS ROMS Development] THEHOLYG0D:
Lol?
[BLISS ROMS Development] electrikjesus:
I uploaded the .img file for those that need to make a DD image of the installer for their devices. The Udoo-x86 requires that as well
[BLISS ROMS Development] 4r44444:
Wooooot???!! Great Job Electric Jesus... Touch Screen working now in newest Bleeding Edge Build on Chuwi Hi12 Tablet.... Awesome!!!! The only thing that is missing now is the sound... Volume buttons work but no sound comes out of tablet! Edit.: Another Problem found: - When opening a Youtube Video it got messed up and buggy video, grey and white strings everywhere.
[BLISS ROMS Development] jaffer707:
My question is regarding the Rom compatibility for Xperia C3 D2502 Device
[BLISS ROMS Development] ElfinJNoty:
No....

Your Xperia device uses a snapdragon processor and is not an x86 architecture device(uses an arm 32bit SnapDragon 400)

Your device is not compatible with anything in this project.

If you'd like to try and build Bliss OS yourself for your own device, our source code is available on our website. If you have never done this process before, it will not be easy. But we have a Telegram chat for Build Support which may help you to accomplish this.

Just to reiterate: no, this will not work for your device. No, it will not be supported by us. Nobody on our team owns an Xperia device, and we do not support devices that we do not own amongst our team.
[BLISS ROMS Development] electrikjesus:
Was this one of the k4.12_oto-installer builds, or the one before it?
[BLISS ROMS Development] 4r44444:
Bliss-v7.2-android_x86_64-OFFICIAL-20171103-1727_k4.12_oto-installer.img
[BLISS ROMS Development] Lovelyven:
Does anyone know how to get this running on the mew surface pro. it installs fine but it gets stuck on detecting android when booting it up.
[BLISS ROMS Development] electrikjesus:
well...
[BLISS ROMS Development] ubuntuh:
can someone please upload the latest 32 bit version? i'm not so comfortable with github.thank you
[BLISS ROMS Development] Lovelyven:
sorry about that. i am using the new surface pro

intel i5

intel hd graphics 620

i disabled secure boot, used the installer provided. followed the easy installation mode. i tried both the regular build an the bleeding edge build and i still get detecting android. i also tried adding nomodeset also well to the grub at boot but still detecting android