yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
Every time I have tried to include OpenGapps or GMS, I am unable to use the device due to constant crashes, so this is an area that could use a little help.
[BLISS ROMS Development] ydd0ras:
microG is here! one lucky guy about this fact! [emoji4]. using microG on all devices!
[BLISS ROMS Development] mahir555:
so there are 2 builds uploaded .. can i use any one on my dell 13 pc?
[BLISS ROMS Development] Phantasy0742:
in my latitude 5290, using 20181018 ver is working good.

but bluetooth is not working, and when pressed the power button it working camera app but crashed app.

in 20181028 ver, when pressed the power button, not working sleep mode.

still bluetooth not working. screenshot not working.

when pressed physical home button, it working voice assistant.
[BLISS ROMS Development] DoughMucker:
Yes. See the "Specific Surface model instructions" section of post 2. You'll use v102 touch screen firmware.

Edit: In order to copy the files, you'll have to extract system.img from system.sfs (and delete or rename system.sfs to system.sfs.old).
[BLISS ROMS Development] y2kbugleung:
I am now handling the multi-boot on Surface Pro 6.

Windows 10 is pre-installed. I don't want to remove it, so I can make the machine look like new when I sell it in the future.

I have Ubuntu 18.04 installed, and dual-booted.

I have just installed Bliss.

Following this guide, I am editing /etc/grub.d/40_custom

https://askubuntu.com/questions/1014944/adding-android-x86-to-grub2

with these lines posted on #2

Reboot, and select Bliss on grub:

I am not familiar with UFEI. Should the disk number and partition number be set on anywhere?

I have Bliss installed on nvme0n1p7

Thanks.

---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------

So, is the kernel version only the difference between these two files?

Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.19.24-ax86-cali_m-19.0.0_ax86-p_f-dev-kernel.org.iso

Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.9.153-ipts_m-19.0.0_ax86-p_f-dev-kernel.org.iso

And how "IPTS Builds - !! Only for Surface & Lenovo X1 devices !!" different with others, if no special driver (touch screen drivers, etc) is built-in?

I am new here, please forgive me for these questions.

---------- Post added at 01:57 PM ---------- Previous post was at 01:06 PM ----------

rebooting the machine, pressing "C" in grub, and run "ls (hd0,gpt7)/", I see directories "lost+found" and "bliss-x86-11.4".

There is no "Android OS".

Did I miss anything during installation?

---------- Post added at 02:07 PM ---------- Previous post was at 01:57 PM ----------

I have followed the step to copy the files into /system/lib/firmware but it says system is mounted as read only.

I have installed Bliss as R/W. Should I manually mount system as R/W?

You said extracting system.img from system.sfs. May you please give some more detail?

Should it be done before installing Bliss, or after installing?

Thanks.
[BLISS ROMS Development] y2kbugleung:
I have extracted everything from the iso, extracted system.img from system.sfs, replaced the files, repacked system.img and then system.sfs.

However, when I repack eveything to a single iso, I am warned this iso is not bootable...

Please help... I am lost...
[BLISS ROMS Development] ElfinJNoty:
You appear to be reading SOME of the instructions in the OP + 2nd & 3re post. Then you are asking if you should follow the instructions that have been provided.

I'm confused why you are confused

---------- Post added at 01:09 PM ---------- Previous post was at 01:04 PM ----------

If you have Win10 preinstalled, did you install Bliss to it's default directory on your C: drive?

If so, I'm not sure what all you are trying to repack.... But you should just be able to access your installation directory at C:/AndroidOS/

Locate the system.sfs, extract it's contents to that same directory, then you'll now have a system.sfs and a system.img. no need to repack anything. Just remove the system.sfs from that directory. Reboot the device with only the system.img in that directory. You will need to adjust your grub boot menu entry to reflect the change(pointing to system.img rather than .sfs)

Now you will boot with r/w access from now on ?
[BLISS ROMS Development] MagicAndre1981:
yesterday evening wifi worked again for some short time, but today it no longer works. But I "solved" this issue in a different way.

Because Ethernet adapter works fine and installing apks works again I install this app:

https://play.google.com/store/apps/details?id=mattiesworld.gotdns.org.adboverethernet&hl=en_US

Started it and now I can run adb connect IPofTablet:5555 on my development VM and when I start Visual Studio I can deploy/debug the android part of my Xamarin.Forms app.

So my main purpose is now working, get a working Android on my Tablet to test Android part of Xamarin.Forms apps :good:

2 other things that I saw:

I have to grant SU/root several times even when I click "remember choise"

1 Play Store related app update can't be installed (likely Yalp related issue)
[BLISS ROMS Development] electrikjesus:
For the Surface machines, I recommend using Rufus to burn a bootable USB, then use that to install to your Windows NTFS drive without formatting.

This will also prompt you to add the needed Grub 2 entries, so that all you will have to do afterwards is reboot from windows and hold the VolDown button while booting to boot to the secondary UEFI entry.
[BLISS ROMS Development] enboig:
Trying to install, I got black screen just after boot. I thought it was frozen, but after pressing random keys, bliss grub was installed, so screen is dark but everything else is ok. Running it live is ok, everything works (screen, wifi, ...). I think I may have so use special parameters at grub, but after trying nomodeset, vulkan, .... I am out of options. Could anybody help me? I am trying to install on a Intel NUC8 I5BEH.

Thanks

PS: I have been searching some days in different forums, and used to use gentoo, so I have played quite a little before asking.
[BLISS ROMS Development] ExsertWizard:
Is there a proper way to remount system as RW when I’m booting bliss is live from my usb with data.img?
[BLISS ROMS Development] electrikjesus:
Try a different kernel. Some machines may have a screen blanking issue on the installer with some of the newer kernels.
[BLISS ROMS Development] electrikjesus:
Not really. Since the typical fat32 formatted USB only supports images up to 4gb, we don't recommend extracting the system.img from the system.sfs and creating a 4gb data.img on the root directory of the USB, then removing the system.sfs file afterwards
[BLISS ROMS Development] ExsertWizard:
I am aware of the FAT32 filesystem limits, i didnt create a data.img larger than 4GB and i was able to place system.img in the USB flash drive. I just want to test my Surface Pro 6 firmware files with Bliss OS but since the system is read-only it won't let me copy the files unless system.img is extracted from system.sfs. I'm having problems in booting the OS and i'm not sure if its booting system.img properly as I get stuck in the bootlogo. I haven't used GRUB before, so what do I have to do to point out system.img instead of system.sfs?
[BLISS ROMS Development] electrikjesus:
Yes. If that doesn't help, post your grub entry in here
[BLISS ROMS Development] ExsertWizard:
Here. I've included all of the .cfg files. I appreciate the help!
[BLISS ROMS Development] electrikjesus:
Everything is there as it should be... As long as you removed the system.sfs file after extracting the system.img that's inside, it should work
[BLISS ROMS Development] meghgoswami:
Hello there, I tried to boot this wonderful OS on my Lenovo Ideapad 330, but it always gets stuck both at the Live Disk and even after being installed on "Detecting android... found at sda*" (something like this). I left it for two hours, still nothing happened. I have tried the Easy Installer, Rufus and syslinux method, but nothing works... Can someone help me? Here's the log file:-

https://xdaforums.com/attachment.php?attachmentid=4733040&stc=1&d=1553855464
[BLISS ROMS Development] ElfinJNoty:
Just a quick look at your log, easily reveals that the installer is detecting something already written to your EFI, and aborting so that it doesn't mess anything up. This behavior is intended. The log states the the install directory(for the EFI entry) is "not empty".

Did you try to use the "Cleanup Android" button prior to trying to run the installer? This should remove any previous Android-x86 based install. Bliss or other. Then perform the installation again.
[BLISS ROMS Development] meghgoswami:
I am getting another error now :crying:
[BLISS ROMS Development] meghgoswami:
It got installed alright, but it is still stuck at the "detecting android... Found at sda*" message ??
[BLISS ROMS Development] wrwolf2:
cfg file for your ISO

Android.cfg file for /EFI/boot/ ( correct entries descriptions for the installation iso image only )

please note :

this simple editing won't fix entries descriptions on post-install " Bliss_OS " grub2 boot screen.

take care

marc
[BLISS ROMS Development] electrikjesus:
You are using a lot of "we"'s in your updates. Who is We? And were you thinking of submitting any pull requests for what your changed to get things working?
[BLISS ROMS Development] avalanche99:
Hi.

I hope I can get help.

I got Bliss Oreo installed on a seperate partition beside Windows 10 and it works fine on my Surface Pro 4.

Now for testing purpose I installed Pie on a seperate 5Gb partition. On installation I skipped to install Grub2, because it was already installed with the Oreo build but now I miss a Grub entry for the Pie build..

I can't figure out what the grub.cfg and android.cfg files have to look like. Can someone give me some help?

Oreo is installed in a folder called bliss-x86-10.1 and pie into a folder called bliss-x86-11.4.

grub.cfg and android.cfg are attached in text form.

Oreo build : Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org

Pie build : Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.9.153-ipts_m-19.0.0_ax86-p_f-dev-kernel.org

Kind regards

avalanche99
[BLISS ROMS Development] wrwolf2:
<DRAFT>

HI and thanks' for your awesome reply message. Could you please define " submitting any pull requests for what we changed to get things working " ?

we are not going to upload any .iso with changes we made ( if that's your concern ) we may in fact write a short note to let everyone else know where we got suggestions and hints on how to add: google play services and services framework and sync adapters, on smartphones/tablets that ship without play store. info and data that are easy to find when searching the net anyway.

some smartphones/devices shipping with firmware customized for PRC market but also delivered to EU ( xiaomi smart devices for instance ) have dedicated forums and blogs with tutorials on how to add play store. Although those tutorials were limited to Android 8.1 ( Oreo ) and Android MM ( marshmallow ) then no guarantee that's gonna work on Android Pie. in fact, we haven't yet been adding google play store 'cause that is the step " that starts getting things messy " or " when System UI F.C and we're back on lockscreen ( something that kicks off sync and then crashing the system ?? ) We also noticed that unlike MM or Oreo we have to manually activate Device Administrator within " Settings/Security & location " and the fairly new security system such as " google play protect " may trigger system crash if not properly configured.

we are not going to release any such .ISO ( installation disk/image ) which include google software and eventually because your colleague mentioned... in US you may face legal issues when adding google software to Bliss OS for x86 / x86-64 ( BTW: we also noticed there are several variants for google play services and among which: Arch. X86 ; Arch. x86 and x86-64 however , upon lab tests we managed to use better a play services variant for android-TV arch: x86. we can't remember the minimum version of android and target version must be oreo or pie. we assume you're all aware about that , though. )

NOTE: for some reason when using YALP store to convert google software and apps to system apps ( Services framework, Account manager, Sync adapter , Play services ) file system turns a Read-Only file system ( /system/priv-app/ ), reboot is necessary in order to optionally change files permissions on those app/folders ( with chmod .) That may explain why you're experiencing storage " permissions / authorizations " issues when trying to add google play store to your Bliss OS on android pie. </DRAFT>
[BLISS ROMS Development] electrikjesus:
Would you mind sharing more details about this? What you had to do, what was changed, and what permissions needed to be added? I could likely add some of this to init, but others might require patching in PackageManager or PackageInstaller
[BLISS ROMS Development] wrwolf2:
<DRAFT>

well... allow US to learn and understand whether we can replicate that also, we mentioned we weren't adding " google play store " as yet because it's getting things messy.

changing file permissions ( chmod for owner/group/others ) may as well be optional and still might need to be done when google software ( GMS, GFS, GFS login etc etc ) still run as user apps rather than system apps ( i.e: changing permissions using chmod and before converting google apps/software using yalp store feature, while G software still bringing up those error messages " play services stop working. App Info; Close app. ).

As soon as you convert those G apps to system apps, error messages stop annoying. we read on the net also clearing cache and storage data for play services ( gms ) and services framework ( gsf ) may as well get rid of error messages but then we need switching all android authorizations back on , for play services and services framework .

rest assured we also managed to get "Google" option appear in "Settings" and we had chances to activate and deactivate device administrator within " Settings/Security & location " ( both " Find my device " and " G pay " device administrator. ) we applied configuration for google account ( adding google account within Settings/Accounts ) then connecting to google servers to authenticate credentials , configured those switches for " google play protect " feature as well.

NOTE: we don't believe you want to patch Package Manager or PackageInstaller, that may trigger installing all apps as system apps. We were following up those messages of your team partner , mentioning you couldn't get play services and play store to work because you're facing issues with storage permissions ( or maybe file/folder R-W-X permissions for USER, Group, Others ) </DRAFT>
[BLISS ROMS Development] mGforCe:
BlissOS boots only in Hardware accleration disable mode

HI,

I have acer aspire sw3-016, with Atomx5-z8300 CPU. I tried booting latest ROM "Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k5.0.4-ma_m-19.0.0_ax86-p_f-dev" on it.

Below are my observations:

1. It doesn't boot in any mode apart from Hardware acceleration disabled. In live debug mode, it stops after detecting android x86...found at /dev/sda1. In other modes like Vulkan/no setup wizard, I see the below screen shot, post which it restarts & stays at blank screen.

2. in hardware acceleration disable mode, after booting, touch screen works, physical keyboard also works, but screen brightness & Wifi doesn't work. Is there any solution to that? Also lack of hardware acceleration makes device very slow in response.

If you need any further information on hardware, let me know.

I feel community can help me in having a stable dual boot ROM on my tablet. Thanks.
[BLISS ROMS Development] electrikjesus:
Please try a different build using an lower kernel version, like the 4.19.31 or the 4.9.1xx, and let me know the results
[BLISS ROMS Development] ilker4fun:
What do you mean when you say "we"? You and your coding teammates? And I wonder why you say we fixed that, we added this bla bla when you are not willing to share it. Keep it to yourself, sir
[BLISS ROMS Development] Synthetisoft:
Does Bliss support Linux Nvidia GPU drivers?
[BLISS ROMS Development] Ahmed elrased:
If I broke some rule I'm sorry, but english is not my native language and I'm a newbie.

I installed successfully Bliss OS on an SD card using a Lenovo yoga710. Installation went smoothly, the sytem is fast and again very smooth but I can neither download nor install apps. I tried searching on google but nothing came out, I tinkered with the settings and Developer mode but I couldn't find anything that helped solve the issue

Touching on screen does not work. Can you please help me? Thanks in advance.
[BLISS ROMS Development] electrikjesus:
Yes, but not all Nvidia hardware is supported out of the box
[BLISS ROMS Development] Ahmed elrased:
I can not mount ntfs why not be automatic
[BLISS ROMS Development] electrikjesus:
The way I figure, if you give people the ability to mess things up out of the box, they eventually will, but if you force them to learn how to do something before they try it, you'll find that things don't end up so bad.

This applies to giving you native ability to mount the drive your computer depends on for most tasks. You can do it, but I'm going to make you search the Android-x86 Google Groups on how ;)

Hope you understand
[BLISS ROMS Development] ElfinJNoty:
Deleted
[BLISS ROMS Development] electrikjesus:
Bliss OS 11.7 Updates - 2019-04-03

!! Please remember to not quote these update posts, or any of the OP's !!

We're back with some more Bliss goodness for you all. This time around we have a ton of fixes for installing apps, notifications, notification actions, and much, much more. There's also some updates for audio and PCI/PCI-E thanks to Spurv project. And to tie it all off, a new test version of Taskbar included (still trying to nail down the remaining issues), Thanks again to [MENTION=4289533]farmerbb[/MENTION] for all the work he's poured into Taskbar.

(Enabling Taskbar as your navbar)

If you would like to use Taskbar as your default launcher, you will need to first go into Settings > Blissify > Gestures, and enable something like Carbon Gestures (I setup three-finger swipes, Right for Back, Down for Home, & Up for Recents), then you can go to Blissify > Buttons, and first, switch the navigation mode to SmartBar, then go back and disable the Navbar from there by switching off Allow Navigation Bar on the top. At this point, you need to switch to your homescreen, so swipe up with your gesture, or tap the Win key. Or Win+esc. Then launch Taskbar, enable it, set to launch on Boot, and I disable hiding, and enable a few other settings in Freeform and Advanced screens. Setting it up this way will prevent any crashing from happening on initial launch. And it allows you to also use Quickstep launcher as the main background. Again, here's a video showing how I use it currently https://youtu.be/htFC8poBEPY

Builds being uploaded:

Bleeding-Edge Builds - !! for all other devices !!

Bliss-v11.7--OFFICIAL-20190403-2153_x86_64_k-k4.9.153_m-p9.0_f-dev-kernel.org.iso !! Most Stable Bliss OS Experience !!

Bliss-v11.7--OFFICIAL-20190403-2316_x86_64_k-k4.19.32-ax86-ga_m-p9.0_f-dev-kernel.org.iso

Bliss-v11.7--OFFICIAL-20190404-1301_x86_64_k-k5.0.5-ma_m-p9.0_f-dev-kernel.org.iso ** pending testing

Bleeding-Edge IPTS Builds - !! for Surface * X1 devices !!

Bliss-v11.7--OFFICIAL-20190404-1444_x86_64_k-k4.19.24-ax86-ipts2_m-p9.0_f-dev-kernel.org.iso ** pending testing

General Updates List:

Notifications working now

Notification actions are stable

Bluetooth updates & fixes

Taskbar freeform launcher updates.

ALSA & PulseAudio updates for more sound support options

Added more native support for PCI/PCI-E

Power buttons working on many more devices (still no sleep state)

Some upstream updates from Android-x86 project

and much much more, check the changelog.

Known new issues:

AOSP Gesture navbar crashes often. Use Smart Bar for now from Blissify's Navbar settings. Taskbar app also affecting navbar crashes.

Sleep states aren't working right on many machines. Some can cause SystemUI to restart

Power buttons may still not work on a few machines.

Changelog:

Changelog too large for posting here. Links:

https://sourceforge.net/projects/blissos-x86/files/Official/bleeding_edge/Generic%20builds%20-%20Pie/Changelog-Bliss-v11.7--OFFICIAL-20190403.txt/download

Thanks, and have a Blissfull time!!
[BLISS ROMS Development] Ahmed elrased:
I have tried but root does not work and I can transfer the file to the system if possible.

---------- Post added at 02:35 PM ---------- Previous post was at 01:45 PM ----------

Is it possible to add ntfs. Automatic recognition I have tried to add this command
[BLISS ROMS Development] electrikjesus:
Please try not to prove my point any further
[BLISS ROMS Development] MagicAndre1981:
Thanks for the update. With Bliss-v11.7--OFFICIAL-20190403-2153_x86_64_k-k4.9.153_m-p9.0_f-dev-kernel.org.iso I now have broken notification. I can't swipe down to open notifications at all. It simply doesn't expand.

2 navigation buttons are broken at all. So clicking an home, switch window does nothing (only back works). I changed to smart bar, but here the same happens.

Tommorow I'll try Bliss-v11.7--OFFICIAL-20190403-2316_x86_64_k-k4.19.32-ax86-ga_m-p9.0_f-dev-kernel.org.iso and see if this version works better on the 8" tablet.
[BLISS ROMS Development] ExsertWizard:
Does anyone here have a Surface device (ideally a Surface Pro 6)? If you do, does the volume rocker and battery percentage work?
[BLISS ROMS Development] electrikjesus:
Might want to try wiping data first.
[BLISS ROMS Development] wrwolf2:
that was weird !

in fact we had to " wipe " USB flash drive and erasing it ( quick format didn't do the job ) , while running Rufus to get USB storage ready for " installation " of bliss OS ( it may be worth mentioning, while installing bliss OS onto a disk partition of a windows system, we also erase that partition applying ext4 format then setting system directory as R/W directory. )

<DRAFT>

first impressions of 11.7:

- very much an improvement while NC ( or notification panel ) won't crash the system UI , also the display isn't freezing that often ( in fact we've only come across unstable system once , maybe twice after we set-up Carbon Gestures and while swiping down with three fingers, to bring up the power menu and to restart/shutdown the system. other carbon gestures actions other than the ones related to controls to restart or shutdown , won't make the system crash. on/off hardware switch is now also working )

- HW keyboard Fn keys ( such as those keys to adjust brightness and volume ) are also working. ESC key doesn't work as BACK button ; BACKSPACE doesn't either ; HOME key doesn't work as a HOME button however: left " WIN " key works as HOME button; right " MENU " key works as a menu tap ( . . . )

- adding android apps ( installing apk ) brings up no errors nor unstable system events occur ( exceptions when making an attempt to update android apps " within /system/priv-app " . that is also predictable. )

- while adding google software:

we see fewer error messages ( " play services keeps stopping. App info; Close App" ) relating to google services framework ( gsf ) google play services ( gms ) and play store ( com.android.vending ); system UI won't become unstable upon restart, also WI-FI card is connected to the network and unlikely disconnects while making attempts to adding a google account the form to enter credentials and authenticate with google servers won't show up in addition, we can't retrieve gsf.id to register android device and to link with google account ( gsf.id isn't in the local database as if play services is no longer generating one )</DRAFT>
[BLISS ROMS Development] electrikjesus:
Could ypu please grab some logs of the missing gfs.id stuff?