yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] amn1987:
Post your system specs. I couldn't get the one based on kernel 4.19? to boot w/o disabling HW acceleration but 4.9 booted just fine. I am guessing yours is older system based on the presence of a DVD drive so slightly older kernel might work.
[BLISS ROMS Development] vagelisfil:
I have a Lenovo IdeaPad Y550 back from 2009. It's quite old system. I've tried all available options of booting but it stacked at the same point every time.

I've also tried all 11.x variants but still the same....
[BLISS ROMS Development] amn1987:
I still have an even older HP Pavillion dv5 with the same CPU. In it anything based on Linux kernel 4.x.x would run sluggishly even minimal distros like Puppy Linux. So even if you get one to boot it might not be an enjoyable experience. Nougat/Oreo based ones might be worth a try.
[BLISS ROMS Development] vagelisfil:
All other linux os i've ever used worked fine. I'll give a try to older bliss os distro.

Thx mate!
[BLISS ROMS Development] ElfinJNoty:
Share a log.txt file, or upload/copy&paste to somewhere like "Pastebin" and post link here

Make sure that your hotspot is broadcasting a 2.4 GHz signal. And make sure that your SP is showing a Mac address in wireless settings

No, have not seen any users report using Project xCloud.

Pretty sure that app is only supported to work on specific devices. May not include libraries for x86 compatibility, in which case, the native bridge for ARM apk compatibility would need to step in. That apk is going to presume you are running on a device with a typical Android you, not an integrated Intel graphics for example, or AMD/Nvidia GPU. So it just simply may not be compatible.
[BLISS ROMS Development] ritreg:
Install issue v 11.9

Hi,

Tried searching everywhere, not sure what I am doing wrong,

1st Install

Bliss-v11.9--OFFICIAL-20190525-2025_x86_64_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso

Everything works via USB boot , so installed it, installed grub, after successful install and reboot android does not boot loads other operating system (tried dual boot with both windows 10 and ubuntu after fresh installs ). Fresh install by formatting everything no bootable device found.

2nd Install

Bliss-v11.10--OFFICIAL-20191214-2253_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-undefined_gms.iso

Boots to android and everything works except Bluetooth. Bluetooth keeps stopping message appears continually if any service tries to access bluetooth rendering device unusable until reboot.

Am I missing anything, I wont to install v11.9 as this was working perfectly va USB. My device is Acer Iconia W700 i3-3217U
[BLISS ROMS Development] electrikjesus:
Please try booting using Old Modprobe mode or adding AUTO_LOAD=old to your Grub boot entry and see if that helps your Bluetooth
[BLISS ROMS Development] ritreg:
Booting using Old Modprobe mode did not work.
[BLISS ROMS Development] DoubleIk:
Hello,

Everything was working perfect since install (about 2 weeks ago) but yesterday i let my surface run out of battery..

Since then I'm stuck on the flower at startup.. Has someone experienced this ?

Édit : After all i dont think it is the battery that caused this.. I also updated su binary.. Is it crashed for good And i need New install or Can i do something to fix it...? I would prefer not going all over...

Thanks
[BLISS ROMS Development] ElfinJNoty:
Unfortunately, you will need to reinstall.

You could have avoided this by reading first.

In all of the "Release Update" posts, which we make with each version release and then have a link to all of them in the 3rd post of this thread.... For a few months now. All same the same thing. "Do Not Update SU Binary! Will result in a bootloop". Instructions are to simply ignore this notification and carry on.

No, there is not a "Can I do something to fix it" except installing over your existing install. Sort of a dirty flash. Depending on your install method, this would be a slightly different process. Can always move your data folder or r name it, then put it back in place after a fresh install.
[BLISS ROMS Development] DoubleIk:
Thanks for your answer.

I really took time to read but there was lot of informations And i guess i forgot that after 2 weeks. It's all good now i found out already there was nothing to do.

It's back on.

Thanks for the answer.
[BLISS ROMS Development] bittuvns:
I installed the latest touch supported version of pie in my touch enabled laptop & everything works perfectly. I just have one problem.. Play store & play services framework don't function properly.. Since play store is not installed, it gives problem in installing applications. Side loading of play store etc doesn't work. I tried uninstalling microG & then installed all the apps provided in archiieve.zip given on page 64 or 68(I don't remember exactly). So can I request that a nano or pico version of play store & services be integrated in the OS? It would prevent hassel of going through all the process of uninstalling & downloading various versions for play store... & a little bit easy guide for solving the current problem would be helpful
[BLISS ROMS Development] bfmetcalf:
I had this happen to me at one point. I actually was able to fix it by deleting the cache files from the Linux install I dual boot with. Can't remember where exactly they were stored, but it was somewhere in the data directory.
[BLISS ROMS Development] KKJdrunkenmonkey:
I spent a few weeks trying to remove microG and get GApps installed in the hopes of creating such a guide. Having minimal expertise in Android I did not have much luck; SystemUI continually crashed no matter what I tried. Eventually the Bliss folks released a version which had GApps preinstalled, it works much better.

In the past month I've had this happen twice. Fortunately I'm just using it for convenience, nothing important, and since I'm using DiskGenius to backup my Android partition I just restored it which eases the pain of reinstalling. But still, rough.
[BLISS ROMS Development] electrikjesus:
What CPU do you have again?
[BLISS ROMS Development] electrikjesus:
Why are you guys spending time doing that when we have Google Play included in our recent GMS builds?
[BLISS ROMS Development] bittuvns:
My CPU is N4100.. Thank you for this amazing ROM
[BLISS ROMS Development] electrikjesus:
I am working on adding fixes for bt on some Ryzen CPU's, but that wouldn't help your situation at all. It might be something else we added though. It would help the most if you could collect some logs for us to take a look at.

Thanks ;)
[BLISS ROMS Development] bittuvns:
Actually i have switched to OS 12 released by your team. Its fantastic build.Most of things work out of the box. Orientation is a headache sometimes

but i have learned to switch it accordingly. The only problem i am facing in that build is that most games dont work. But that might be an issue of Android Q.. Thanks guys for such amazing ROM..
[BLISS ROMS Development] michie:
Finally got this working on my dell venue pro 3845 after 5 days. Had to install X86 9.0 first without setup wizard, setup the system without wifi, then with wifi and then dirty flash Bliss in order to get the system to work in a extremely laggy state for 1 more hour.

After alot of patience and cursing during installation I got the system running somewhat fluent, added ro.config.low_ram=true to build.prop and installed pixel launcher Go edition for ram optimizations (Only 1Gb RAM available).

System needs to be booted holding the volume up button and choosing the HDD as boot device on every boot/reboot.

Not doing this will cause a black screen. (For some reason auto boot to HDD uses EFI64 instead of EFI32)

I'ts running fine now finally, thank you for your work!

Just curious, are there any plans for android GO X86 for low memory systems?
[BLISS ROMS Development] ElfinJNoty:
Please pay attention to the Update Release posts and the details of file names for our .iso's

The latest releases we made public come in two forms(as indicated by their file name!)

.....foss.... = MicroG

.....GMS....= GApps

Could have saved yourself a few weeks of effort ?

---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------

Every single one of our builds supports touch input. There is no unique touch supported build and a seperate non touch build.

You don't have a problem, you have an oversight or failure to read: GMS in the .iso filename = Google Play Services and Play Store are already built in. If the file does not contain "GMS" in it's name, and instead has "foss" then that build is lacking Google Play Services, and has a MicroG solution in its place.

Glad EVERYTHING will be working for you perfectly, now that we have eliminated your "issue" ? thanks for reading the "Update Release" posts found in this thread with each public release(as well as saved in a list in the 3rd post of this thread for easy reference).
[BLISS ROMS Development] bittuvns:
Thank you.. But I got it later.. I updated to Bliss 12 & it works very well.. So I don't plan to go back..
[BLISS ROMS Development] ritreg:
I have Intel core I5-3337U
[BLISS ROMS Development] electrikjesus:
No solidified plans for it yet. All the low-mem commits I have reserved for our 32bit builds once we get those going again.
[BLISS ROMS Development] michie:
Sounds good!

Pie and 10 performs good on this low ram device though untill I enable wifi. Wifi makes the device so laggy that it almost locks up. This behaviour is from bliss 8 and up.
[BLISS ROMS Development] dangouseboy:
Finally got both auto rotation and inverted touch screen work.

For inverted touch screen, I run some code in terminal before run the calibration app.

su

mkdir -p /data/misc/tscal

touch /data/misc/tscal/pointercal

chown 1000.1000 /data/misc/tscal /data/misc/tscal/*

chmod 775 /data/misc/tscal

chmod 664 /data/misc/tscal/pointercal

Then run calibration app, touch the five points and restart.

for auto rotation, edit /etc/init.sh

try going into init.sh and scroll down to init_hal_sensors function and after the last "fi" statement insert the following:

has_sensors=true

hal_sensors=iio

set_property ro.iio.accel.quirks no-trig

set_property ro.iio.accel.order 102 #insert this line if screen is 90 degree rotation instead of 180, it exchanges Y and X axis

set_property ro.iio.accel.x.opt_scale -1 #Use one or more of them, depends on which axes are inverted.

set_property ro.iio.accel.y.opt_scale -1

set_property ro.iio.accel.z.opt_scale -1

I tried install the android x86 original version. It seems my battery reading works fine in android x86 8.1 and 7.1, but it doesn't work in BlissOs 7.2 or 10.1. Haven't find anyway to fix it.
[BLISS ROMS Development] KKJdrunkenmonkey:
No actually, I couldn't, and I mildly resent the implication that I didn't do my research. Unless your naming scheme has changed over the years you didn't have a GMS build with IPTS support for Surfaces, which left me in a spot where I had to try to figure it out myself. I certainly appreciate that your team has one now though and am happily using it.
[BLISS ROMS Development] edisonzhong0623:
Hey man, same machine and problems as you!

Have u got these things fix?

that will be nice!

Thinkpad X1 tablet gen3
[BLISS ROMS Development] brightjh01:
anyboby use this on EOL chromebook without tough screen , (Asus C200MA) and is so how do you like it. useing linux at this time.
[BLISS ROMS Development] svanden:
I have been on enough forums to know that the first thing I should do when I have a problem is use the handy dandy little search box provided. In this case I have searched every way I know to describe my situation and either 1) dont even know how to describe it in "searchable" terms or 2) I have missed something super simple and deserve a headslap (just as likely as #1). I am new to bliss and dual booting, but I am not new to isolating variables. My issue is that I can get the touch function working on my Surface Pro 6, but, as soon as I decide to boot back into windows and then subsequently boot to bliss touch ceases to work.

Setup:

Surface pro 6 i7

Windows 10

Bliss-v11.10--OFFICIAL-20191215-1101_x86_64_k-k4.19.24-ax86-ipts2_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-undefined_gms

I have peripherals and other things, so here is what I have tried:

1. Install surface firmware -> reboot to bliss -> touch works -> reboot to bliss again -> touch works

2. (a)* -> Install surface firmware -> reboot to bliss -> touch works -> reboot to windows (a) (b) -> reboot to bliss -> touch fails

I have tried these same steps and altered (a)* by removing my sd card for the entire process and (b) by connecting my surface dock upon booting windows and then removing it after shutting down from windows, then trying to boot bliss. To be clear on my methods I have tried (a), (b), (a) and (b). I hope someone can troll the bejesus out of me and point me to a previous post, or kindly help me because my issue is actually weird. Thanks for taking the time to read my post.
[BLISS ROMS Development] KKJdrunkenmonkey:
One of the most important things to understand about dual booting is that the operating systems will generally know nothing about each other (exceptions exist, of course, such as using EXT2FS in Windows to attach your Bliss ext4 partition as a readable drive). In particular, Windows doesn't know the ext4 file system and won't touch Bliss unless you go to some lengths to do so. So, whatever is being done to your machine is likely temporary, in memory only so-to-speak. I remember coming across a thread where someone was talking about Windows setting up a device to work a certain way with it, causing it to be incompatible with Linux. I'm fairly new to Linux, but this seems a plausible explanation, investigation is needed to determine if it is correct.

Your test case said "reboot" to Bliss. Try powering down completely from Windows and see if booting into Bliss behaves as expected. A reboot may leave some of the hardware hot resulting in an incompatible state. I'd view this as a Linux/Android/Bliss driver bug, as it is not properly initializing some of the things it needs, but again I'm new to Linux so who knows. Anyway, you mentioned only two test cases, rigorously testing combinations of cold boot vs. reboot might help. Lastly, if you get stuck, make sure to post logs - use Alt-left arrow to get a command prompt, then "logcat -d|logcat.txt" and post your resulting logcat.txt file where someone (better than me) can review it.
[BLISS ROMS Development] soumakischris:
help !!! i am trying to install bliss os on Parallels Desctop and i cant get it to work ! Can some one help me
[BLISS ROMS Development] dangouseboy:
I tried Android x86 9.0 rc1 recently, the battery indicator also works fine. Is there any way I can fix the battery indicator in Bliss OS? Like replacing some files with those in Android x86 9.0 rc1?
[BLISS ROMS Development] openschools:
HP Streambook Touch: power state, SD cards, GMS feature flags

First up thank you so much for this ROM which has far exceeded every other I've tried! It is working well so far on an HP Streambook G5 with touch screen.

I am dual booting with Linux by installing into the same filesystem or a dedicated partition and using custom grub entry

I have a few things I cant resolve and a general question re GMS please:

Sleep state:

VULKAN is enabled which sorted out restart UI issues after sleep mode

Sleep state works fine when using the power button and selecting sleep

But closing the lid does not invoke sleep mode which I would like - it just turns the screen off (wifi is still active)

Can i change this setting by editing any acpi configs or...?

SD CARD

I have 3 partitions on the sd card (internal mmc) which are used by my Linux install. They get auto mounted by android on boot and then it offers to format them

(Notifications: Issue with SD card - Tap to fix)

I dont want these partitions to be visible - can i hide or block them?

I tried to pass SDCARD=/dev/mmcblk0p2 where android is installed (via grub) but that did not stop it mounting the others

I read up on vold but on the edge of my knowledge...

GMS feature flags

I am planning to manage these devices using mobile device management (android enterprise) and meraki

The requirements include GMS and specifically feature flags

device_admin

managed_users

Are these install able or only available with a GMS license?

It may still work without them but without the full feature set - I can work around

Thanks again :)

Background:

This is for a school. I have 60 netbooks running linux and now 30 new streambooks with touch screen running linux. I am adding android as a dual boot option and aim to manage them with mobile device management as much as possible

Keep up the amazing work!

Lloyd
[BLISS ROMS Development] electrikjesus:
Lid close actions are supported, but your hardware might need something more than what we provide in the kernel so far.

Adding device_admin and managed_users is not something we have added in our public builds, but if you are interested in building from the source, I could walk you through where to add those.

For blocking partitions, rules would have to be added to source to target those specifically.
[BLISS ROMS Development] electrikjesus:
As the other user stated, you should try and shutdown completely from Windows as sometimes it does not release devices properly because it holds their state in a paging file or ramdisk. I would also suggest using the old modprobe boot method along with vulkan. You might have more consistent results with those steps.
[BLISS ROMS Development] rebel1699:
This exactly what my dell would do (when I first started using android for pc) on a reboot from windows to android. A full shutdown from windows and boot back up to android will release all devices and function normally, indeed. Worked every time.
[BLISS ROMS Development] Younes_vd:
hello my device specification is this

lenovo ideapad 520 cori7 8550u ram8g intel uhd620 and nvidia GeForce mx150 4g

which build is compatible with it? so I can install

Alright I just flashed the latest update v11. 10 to the USB and the I select live mode but it's stucked here ?

"Detecting Android-x86... Found at /dev/sdb1"

What is wrong? What should I do now?
[BLISS ROMS Development] openschools:
Thanks for the speedy reply!

Am i reading right that blocking partitions will require building from source as well as the features?

Is it possible to add file system support for exfat and ntfs to android in a similar way to Linux? I could work with that if it auto mounted but did not offer to format and respected permissions

What do i need to look for in my hardware re lid close actions - for future reference please?

I will test with the public build first but yes would be willing to build from source, thanks for the help!
[BLISS ROMS Development] electrikjesus:
System support for ntfs is added, but it doesn't auto mount any ntfs partitions except for the one it's on. That can be added to init.sh. Exfat support is still in the works
[BLISS ROMS Development] ingermy:
Congratulations on your work. On my surface pro 2017 (sp5) everything works fine except the battery level. Has anyone solved in the surfaces?
[BLISS ROMS Development] KKJdrunkenmonkey:
I haven't, no. When you say everything works fine, can you comment on the hardware keys (e.g. power button), infrared lid close detection, and sleep mode? None of those things work for me on my SP2017, the sleep thing is particularly nasty as the system locks up hard and tends to corrupt files.
[BLISS ROMS Development] openschools:
Encrypting

Is it possible to encrypt with any of the Bliss OS for PC please?

Attempting with 11.11 but it stops almost immediately and restarts the UI

Thanks!
[BLISS ROMS Development] ingermy:
I meant that the most annoying bug for me is the battery.

Even on my buttons and sleep mode do not work.

Sorry for my bad English.
[BLISS ROMS Development] valtchov:
Thanks for the great work. I am running the official 11.10 (generic build) on an 8" atom based tablet (NuVision TM800W610L Signature) with Vulkan enabled. Everything works great except sleep. When the tablet goes to sleep or after I press the power button, I am not able to wake it up. The screen stays dark and I have to reboot it by long pressing the power button. Any tips to explore to get this fixed? Working great and smooth UI apart from this. Thx

V
[BLISS ROMS Development] electrikjesus:
Encryption on these generic builds will not work. That will require a specialized device repo
[BLISS ROMS Development] electrikjesus:
People with sleep issues still,

Please check the troubleshooting section of our docs.blissroms.com site for the various sleep options that can be testes through Grub command line. Not all machines are created equal, so some may require a bit of tweaking.
[BLISS ROMS Development] Yo_MaMa:
If anyone's looking for sleep mode on a surface pro 4, boot up with vulkan support.

edit: with vulkan=1 the sp4 now wakes up from lock but not if it goes in deep sleep. I have tried 'sleep=1' and 'acpi_sleep=s3_bios,s3_mode' but regretfully, neither is working.
[BLISS ROMS Development] cjeu100:
wifi not working

no android os has support for rtl8821ce wifi driver

plz add it or is there a kernel version that has it?
[BLISS ROMS Development] ak1998:
Hi, I installed the rom today. Everything working great, but for some reason I am not able to take screenshot. Trying to take screenshot is giving me "Taking screenshots isn't allowed by the app or your organisation" on every screen. I am attaching the logs. Can someone please help me solve this issue. Thanks in advance.
[BLISS ROMS Development] cjeu100:
when booting without vulkan screen recording works but not screenshots

when booting with vulkan screenshots work but screen recording not working for me
[BLISS ROMS Development] izwb003:
Speakers not working

speakers not working:

Hello and just now I installed the OS on my Surface 3(not Pro) , everything works well but the speaker is not working and I can't hear any sound... I considered it as a firmware problem and I followed the instructions on the official Docs site as Surface Pro 3, but it's still not working... Now I wonder what should I do to fix this issue. I am a newcomer to Android and this forum and I don't know if I need to attach the log or not... Can someone help me about it? Thanks a lot.
[BLISS ROMS Development] tanmay99:
Specs to be considered:

UEFI BIOS with GPT disk

Ryzen 5 2400G with Radeon Vega 11 Graphics

So the question is, whether the latest Vulkan build, which apparently works on kernel 4.19.something, supports AMD iGPU (Radeon Vega 11) or not. if not, which is the latest build I can get running on this apu. Cuz in one of the first posts state that Vega graphics are supported from Kernel 4.20+ but I cannot find a recent build with that kernel on github. The last such build (I can see) is of March 2019.

+ Data is limited here. I cannot go ahead and download 10 builds and wait for rufus to do things for me and run LiveCD everytime to see what works. Hence the question.
[BLISS ROMS Development] chandra49:
key mapper

can i using key mapping like octopus in this os?
[BLISS ROMS Development] valtchov:
Same for me, tried these settings but still unable to wake up NuVision tablet from deep sleep.
[BLISS ROMS Development] philip00026:
Hi! Any chance we could get a surface pro 7 build soon? I love the ROM but am stuck at the windows logo :(
[BLISS ROMS Development] tanmay99:
Thanks for the info. I already tried the top 4.19.50 download from sourceforge, no luck. It is stuck at detecting Androidx86... Found at /dev/sdb1 (or sdb if I formatted the flashdrive as mbr disc). An underscore comes below this blinks for a while and is dead. Most likely the GPU is not supported as was my experience with some other x86 forks. But as you said 4.20 was not working well, so I will go ahead and download the March k-5.0 build (latest for that kernel I guess), and report whether it works or not.

P.S. My meaning in downloading 10 builds was to download many builds one by one, and also everytime run rufus and wait for it to do things on my humble 2.0 (hence slow) pendrive. (Takes 5 long minutes for both isohybrid and ddimage). And then run LiveCD each time to see which one works.