yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] AL-GONE-KWIN:
Have run on amd a6-7400k radeon r5 kavari apu.

Only boots screen in no hw accel mode.

Noticed in kernel firmware amdgpu there are no kaveri_*.bin files.

Still no wifi, tried all PC android ROMs on my rtl8188su usb.

Got booted tho and the sparse settings of Pie greeted me.

Thanx.
[BLISS ROMS Development] ThamerX:
Overall satisfaction: happy

Hello

the latest is very nice accelerometer and rotation are working really well on my Surface pro 2017 but touch didn't work out of the box I had to flash 102v IPTS firmware to get touch and pen working. Although, there are few issues within the build

some games refuse to run and couldn't get PlayStore to work and the notification are suicide bombs

Overall the build seems to be very responsive but with few major issues

Bliss-v11.1-Beta--OFFICIAL-20181028-1108_x86_64_k-kernel-4.9-IPTS_m-m18.3.0-devel_w40_LLVM70_f-dev-kernel.org.iso
[BLISS ROMS Development] AllanJacques:
How did you flash the firmware? Can you teach me?
[BLISS ROMS Development] ThamerX:
simply download the firmware from jakeday/linux-surface on github

Mine for SP2017 was ipts_firmware_v102 then extract the files and paste to lib/firmware/intel/ipts

check this post xdaforums.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657/post76896155

you need to have R/W access

to get it you have to extract system.sfs then you'll get system.img

rename system.sfs.old

then boot to android and install es file explorer or any root explorer or use the terminal to copy the files
[BLISS ROMS Development] roberogi:
hello friends, after trying bliss pie in my mido, I tried to install it in a sony vaio, and I have graphics problems. On the other hand, the nougat starts without problems, I will try different boot combinations, the graph is ati radeon.

I will keep you informed, my idea is to make an installation as the only operating system (standalone), will it be possible?

your work is incredible, thank you
[BLISS ROMS Development] electrikjesus:
Yeah, I think we're missing a few things for Radeon support currently. Mauro Rossi has some new developments with that, but they are on newer kernels, and currently, I am unable to get any kernel past 4.9 to build correctly, so... baby steps. I think we've come a long way in a short time with the way we're doing things in Pie.

The next tasks I am personally trying to work on is drm_hwcomposer. Since we're using AOSP's version instead of Android-x86's (like we used in nougat & oreo), there are many advantages, and a few drawbacks too...

Once again, thank you all for being patient with me while things are all getting figured out.
[BLISS ROMS Development] roberogi:
ok, today I will try some things,¿Some magik booflag for ati?
[BLISS ROMS Development] roberogi:
with the automatic installation I have achieved a standalone installation with bliss oreo, for lack of some small adjustments, the operation is correct, some things do not work but I know that the sony vaio is difficult to tame, soon I will try with pie, I have already read something about of ati

after trying your rom for mido I'm excited, I tried your x86 for a long time, but my ascer aspire was very old
[BLISS ROMS Development] GOOGLE_USER:
Advancement

Quite right, on all points.

Self-dispatched and definitely on-the-ball, it was our fellow member [MENTION=7295614]atg.303[/MENTION] who located this gem, successfully applied the method, and was thoughtful enough to return here and share the find.

[MENTION=3044858]DrakenFX[/MENTION] - I thank you for placing me on the scene but I just happened to be engaged with the right people when something good occurred.

You, on the other hand, have contributed more than I have by testing, verifying, and reporting back here with your device details and files to share.

Your efforts are appreciated.

Same sentiment to you [MENTION=6901005]MoistPicklez[/MENTION] for reporting back on your success in applying.

[MENTION=928479]electrikjesus[/MENTION] could use more participants like this.

GO BLISS TEAM!​
[BLISS ROMS Development] MoistPicklez:
Hell, my Laptop is a junky Acer, and I am willing to test and poke or prod if needed. I'm not super proficient at providing logs but if any helps needed, I am in there like a pickle in a jar!
[BLISS ROMS Development] larrougos:
Hi guys! i really love this build and everything is working for me except the microphone. I have tried with the 3.5 jack as also bluetooth headphones. Nothing worked! Right now i have on my "init.sh"

alsa_amixer -c $c set Master on
alsa_amixer -c $c set Master 127 # Changed from 100 to 127
alsa_amixer -c $c set Headphone on
alsa_amixer -c $c set Headphone 100
alsa_amixer -c $c set Speaker 127 # Changed from 100 to 127
alsa_amixer -c $c set Capture 127 # Changed from 100 to 127 (Not meaning to, But didn't hurt nothing so left it)
alsa_amixer -c $c set Capture cap
alsa_amixer -c $c set PCM 100 unmute
alsa_amixer -c $c set 'Internal Mic Boost' 2 # Changed From 'Mic Boost' To 'Internal Mic Boost'

My laptop is a Lenovo Yoga 13.. If anybody has a solution for the mic i would greatly appreciate.
[BLISS ROMS Development] wrwolf2:
HI !

thanks' for your kind reply and please forgive US for missing comments and conversations over the last few weeks.

Bliss OS v.11.8 almost perfect

G services and play store work great however, i should point out G play protect wasn't activated nor device administrator was activated by default. it may be worth it a mention just in case fellow readers might experience difficulties.

we changed the HW and using HP laptop these days, to temporarily test BlissOS 11.8 :

- BT ( bluetooth ) works great

- chromecast casting: searches and finds android TV and devices ( awesome, we're impressed )

- power on/off button is a little temperamental ( when making attempts to switch the HW off while bringing up controls on a " toast " panel, that only works if done right after rebooting. when pressing power switch after a few hours usage, it very likely fails )

- google DUO ( crash , FC after setup is completed. may be related to camera or mic initialization ? )

- while adding mail clients from G Play, and upon setup only, screen turns portrait mode then mail client apps FC or crash without finishing account setup. that event occurs even when configuring display rotation locked to landscape.

please take care,

marc
[BLISS ROMS Development] GOOGLE_USER:
CHECKLIST

Let's see here

:

Junky ACER laptop, loaded up with BLISS OS.

Willingness to test, poke, or prod.

Lacks SUPER proficiency regarding logs. [refer back to willingness statement: still qualifies for participation]

CHECK, CHECK, and CHECK.

OK, then. Get on the bus!

Not sure about how the pickles in jars will be used yet, but I've prattled on about spoons, so... sure, why not? :D
[BLISS ROMS Development] electrikjesus:
In order to determine what audio adapter is being detected, can you please use the alt-f1 console and give me the results of:

$ lsmod > /sdcard/lsmod.txt

Thank you
[BLISS ROMS Development] larrougos:
Here you go sir!! :D
[BLISS ROMS Development] electrikjesus:
snd_hda_intel, so that tells me a little bit. I'm having an issue with another Intel audio chipset on the RCA Cambrio too. That one has no sound at all though.
[BLISS ROMS Development] larrougos:
Interesting! Mine has output but no input. I also tried with Bluetooth devices to record but without luck.
[BLISS ROMS Development] electrikjesus:
Found this on Android-x86 google groups, see if it helps in your case

https://groups.google.com/forum/#!s...ort:date/android-x86/aGLBaYUIw3Y/FZaBARjHBQAJ
[BLISS ROMS Development] :
Managed to triple boot bliss os pie with linux mint and windows 10 on my lenovo thinkpad 4gb ram Intel i5pro. I reslly like the os have wanted to boot an android for a while. Installed magisk as superuser by swapping initrd,ramdisk,kernels. Any way to flash a zip or install a recovery?
[BLISS ROMS Development] electrikjesus:
Nope. There is no recovery solution for Android-x86 just yet
[BLISS ROMS Development] :
Downloaded Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.9.153_m-19.0.0_ax86-p_f-dev-kernel.org.iso and and put it on an USB-pendrive where I booted computer from.

To test Bliss tried LIVE mode: completely distorted screen. My lappy's specs: Lenovo G505s with 64-bit AMD A10-5750M APU w/ AMD Radeon HD-Graphics .
[BLISS ROMS Development] mesheree:
Installed Bliss-v11.8--OFFICIAL-20190421-1341_x86_64_k-k4.19.32-ax86-ga_m-19.0.0_ax86-p_f-dev-kernel.org_gms.iso on an HP Stream 11 model AU58Y3K.

Wifi, camera, microphone, bluetooth, sleep, physical volume/seek/brightness/power buttons and Netflix are all working, but attempting to sign into the Jira website with Google credentials using Chrome or any Chromium-based browser (Kiwi, Opera, Edge) causes the browser to ... disappear. It doesn't quite crash, but it disappears off the screen. and if you pull the browser back up and try to refresh, the same thing happens. The Google Hangouts Meet app shows similar behavior. I'm guessing maybe the Google login stuff isn't fully-implemented yet?
[BLISS ROMS Development] electrikjesus:
I would suggest browsing back to the first few posts and read a bit. Making sure to read the instructions, command line instructions, the explanation of what the kernels do, and then the last few Update Posts. Those will arm you to the teeth with all the knowledge and power needed to run Bliss on amdgpu ;)

I'd need to know a little bit more about what GPU is running, and also how these apps were running. Was it in Freeform mode, or were the apps in fullscreen mode? Any themes and Blissify settings applied will also be relevant. Thanks :P
[BLISS ROMS Development] mesheree:
It's a netbook with sucky integrated graphics on a Celeron N3060 (I can't link), but I'd be really surprised if this had anything to do with graphics. This is new behavior since the Play Store was added.

This happened right after BlissOS install, in Fullscreen mode, and the only changes I made were:

Choose a launcher (QuickStep)

Connect to Wifi

Sign into Google

Download Chrome or a Chromium-based browser from the Play Store

Type <ourdomain>.atlassian.net into the address bar

Browser shows me the list of signed-in Google accounts

Wait a second or two, and... Poof. Browser disappears, appears to still be running in the background, but if I switch back to it enough times, I get the "<App> keeps stopping" dialog.

I re-installed BlissOS several times, varying in the following ways, none of which made the slightest amount of difference:

Signing into Google via the Settings App or the Play Store

Signing into a single Google account or multiple Google accounts

Specifying the Desktop or Mobile versions of the Jira website

Trying a different Chromium-based browser (Opera, Edge, Kiwi)

I didn't try using the other launcher, since QuickStep seemed like a better lowest-common-denominator for testing purposes.
[BLISS ROMS Development] electrikjesus:
Just a hunch here... Check in Settings > Apps > Permissions to make sure Chrome and the other Play Store apps have the permissions needed. And also check to make sure they're also granted permission to display over other apps.
[BLISS ROMS Development] mesheree:
Just tried the whole 'Install BlissOS from scratch again' with Chrome as the browser. In the app's own permissions section, it already has all the permissions I'm able to give it, and in the Special App Access section, Chrome doesn't show up in the list for me to grant the 'Display over other apps' permission.
[BLISS ROMS Development] :
Thanks for your reply: is not really helpful, just general blahblah . Giving up ...
[BLISS ROMS Development] electrikjesus:
I always love finding out that my time was wasted when adding all the info I could to this thread...
[BLISS ROMS Development] ElfinJNoty:
He explained where you should read to educate yourself on the process you are attempting. Suggested where to find a compatible build(which has been reported to be working well with AMD hardware) and again pointed to where to read about the specifics of each build.

What you seeked is there, in the open, waiting for you or anyone else to utilize. READING instead of expecting someone to feed you the info or steps necessary, will make you much more capable of......

Oh nevermind, you gav up. We'll save our blah blah general stuff for someone else, who is less entitled and perhaps grateful for the work and efforts involved in providing Bliss OS to the public

C Ya!
[BLISS ROMS Development] Mohamed Anwar:
Why

Come on man, You know that the one that doesn't read the info have many problems.

I was have a lot of errors and problems but after I readed it, It solved many problems.

Thanks you electrikjesus and The Whole Bliss Team.
[BLISS ROMS Development] :
Running Bliss OS Pie on AMD machines basically works

Downloaded the build - the one claimed to be ready for AMD equipped machines -

and permanently installed it on a USB-pendrive - for testing Bliss in Resident Mode.

Can report it's basically working, but not as expected: mouse randomly freezes/stucks, Wi-Fi connection isn't detected by all apps , e.g. YALP, though properly set up - BTW could sign in to Google Play, FDroid app constantly crashes, File Manager isn't working, downloading an apk through FireFox doesn't work, installing an app via Gogle Play Store doesn't work - stucks, etc.pp. ...

Waiting for a bugfree release.

Have a nice day.
[BLISS ROMS Development] ChildXde:
Kernel not found

i have installed the newest Blissos from Official Website (Version: Bliss-v11.8--OFFICIAL-20190421-1341_x86_64_k-k4.19.32-ax86-ga_m-19.0.0_ax86-p_f-dev-kernel.org_gms.iso) on my Lenovo Laptop: T440s with Ubuntu 19.04 installed.

i added into the file:

/etc/grub.d/40_custom

menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.sfs
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive androidboot.hardware=android_x86_64 quiet DATA=
initrd /AndroidOS/initrd.img
}

on the android device disk i have the folder bliss-x86-11.7 and subfolders and files data kernel ...

if i boot the Bliss version comes an error kernel not found.

Update:

i have fix it with this update code:

menuentry 'Android 9' --class android {
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos3'

search --file --no-floppy --set=root /bliss-x86-11.7/system.sfs
linux /bliss-x86-11.7/kernel root=/dev/sda3 SRC=/bliss-x86-11.7 androidboot.selinux=permissive androidboot.hardware=android_x86_64 quiet DATA=
initrd /bliss-x86-11.7/initrd.img
}

set root fix the problem and the AndroidOS i have changed with the bliss folder only the system.sfs is lost and in the booting he shoes it.

Next Problem:

i have tested it in live cd and there was an error like in the installed version. if i open the taskbar and open the menu and click something what opens in window modus all flickers black and the normal tasbar trys to open. can i fix it?
[BLISS ROMS Development] ElfinJNoty:
If you extract the contents of the .sfs, you will be left with a system.img, which will have full read/write privileges. Then adjust your boot menu entry to point to the .img instead of the .sfs
[BLISS ROMS Development] ChildXde:
this fix the grub problem thanks.

if i now start the screen stays black and i only see the browser and if i but the power button i got a reboot menu and cannot use Blissos longer.

some more bugs i have found before:

1. sometimes the Wifi/Wlan dont works and cannot connect and also find no networks

2. the taskbar trys to open and everythink flickrs black like an mask that is over the normal launcher

3. after booting screen stays black only with coursor

can someone maybe helps me?

Edit:

because of black screen i have readed to change the kernel can i change it with the kernel file in the blissos folder? and what kernel i need for an Intel I7vPro System (LenovoT440s)
[BLISS ROMS Development] electrikjesus:
Try adding this to your grub command line:

acpi_backlight=video
[BLISS ROMS Development] dakocha:
Can I post some bug reports here?? I'm using the latest Pie build. Every time a full screen app is running, I can't access the notification bar OR the nav bar!! Also, the bundled SuperSU app has some weird bug that makes it ask for permissions on apps that I've selected "remember this choice forever" weird??
[BLISS ROMS Development] electrikjesus:
I'm aware of the superuser bug, but for the other, yes. Please post any logs you can grab if the event happening. Also let me know what device you are running it on, touchscreen, launcher, if is navbar hidden, etc.
[BLISS ROMS Development] xwndle:
I have been trying to dual boot Windows 10 and an Android OS for like a week now. tried the exe installers PrimeOS and PhoenixOS, the install went smoothly but everytime I reboot it just says "Selected boot device is disabled in BIOS setup" now tried BlissOS using a bootable USB which the closest I got since the live/debug works.

I'm sorry if this question is out of place or something but I really need help I have tried to install too many times and even accidentally forced to change the bootmgr in bcdedit which resulted to Windows 10 not booting anymore and I needed to undo it in the command prompt using a bootable windows recovery DVD.

I got it to install BlissOS without a hitch. But grub2 doesn't show up, it just directly boots to windows. I have tried fiddling with the BIOS but I can't find any option or entry that would enable grub or boot directly to BlissOS. I already have set a supervisor password but I cant see any option to trust EFI in the BIOS. I even tried EasyUEFI (made a mess with the EFI and had to clean up the entries and bcdboot windows10 again) and Grub2Win (test boot and set grub2win as default) tried enabling grub and android but they're still hidden and the changes i made revert after the next boot then the same error message pops up again "Selected boot device is disabled in BIOS setup"

I wanted to try changing the boot mode to legacy but i read that it doesn't work for blissos. sorry for the trouble. I believe im out of ideas and the bios thing doesn't help even after I updated it (or maybe i just dont know what I need to find there)

[IMG="System Information"]https://ibb.co/m5gbTpS[/IMG]

[IMG="EasyUEFI snip"]https://ibb.co/pncqwFL[/IMG]
[BLISS ROMS Development] :
May be OFF-TOPIC

I'm using Etcher instead of Rufus or other tools to push an Android image onto a bootable USB-pendrive: it always worked at 100%

Then to get a resident Android I'm installing it via the GRUB menu on another USB-pendrive ( >= 64 GB, USB 3.0 recommended ): requires 2 USB slots on computer, of course. This also every time was working at 100% for me.

BTW: How to remove GRUB boot-loader from the system, is shown here:

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

HTH
[BLISS ROMS Development] xwndle:
:( I have already tried Etcher after rufus. Same thing happened, the flashing worked, installed bliss smoothly, grub2 as well, after rebooting, no grub
[BLISS ROMS Development] beacool:
I have Teclast X5 Pro tablet and i install this rom but my touchscreen is not working right. Is there anything i can do? Please help...
[BLISS ROMS Development] PremiumMediocre:
Try:

Bliss-v11.4-Stable--OFFICIAL-20181228-0938_x86_64_k-k4.20-gal_m-18.3.1_pie-x86_f-dev-kernel.org.iso

...with modprobe. This is the only one that I could get the goodix touchscreen to work with. I think your tablet uses goodix as well.
[BLISS ROMS Development] :
If you are working on an UEFI computer then you've to put the x64 ready boot-loader ( bootx64.efi ) onto USB-stick -> subfolder \efi\boot, too, if missing, AFAIK. Also in order for the system to recognize the USB-stick as bootable in UEFI mode, it must be formatted with FAT or FAT32.
[BLISS ROMS Development] speechless:
i wanna test bliss os for the first time so is better to wait for next build? or im gd to go with v11?
[BLISS ROMS Development] mitzra3l:
Hello guys

I tried a clean install on a PC, previously had win10, but decided to clean all up and start fresh. Sadly it didn't work, when I boot the PC I get a message "no os detected"

Please help

Enviado do meu Aquaris X através do Tapatalk
[BLISS ROMS Development] :
Watch this video: https://www.youtube.com/watch?v=mw_EuTYAGLI
[BLISS ROMS Development] mitzra3l:
Thank you for your reply, but my idea is to install a Bliss OS, not windows
[BLISS ROMS Development] shookica:
I am running 11.9 - Bliss-2019-05-07-arm64-ab-gapps on a Umidigi S3 Pro.

Installed it by unlocking bootloader, flashing TWRP, wipe all (dalvik,system,cache,data), install Bliss, install Magisk, install disable_dm-verity_forceencrypt, reboot.

Bluetooth does not work.
[BLISS ROMS Development] electrikjesus:
Wrong thread. You're going to want to search for the GSI/Treble builds thread for Bliss
[BLISS ROMS Development] peter19ji:
Both IPTS 11.6 builds for Surface as well as latest Oreo build doesn't work for Surface pro 6. Jakeday has recently updated his linux-surface project for touchscreen support on SP6, so please update.
[BLISS ROMS Development] electrikjesus:
I have not been able to get the Surface Book I had to test these builds to turn on at all in order to test the IPTS builds, so that is why development on those have slowed.

There are two possible solutions here,

A) Someone with a Surface device and some Linux & Android kernel know-how could take some time to help make these builds.

B) The community starts to work together with a common interest in mind, and figure out a way to get another Surface device in my hands, and I can continue working on the Surface devices myself.

I'm wide open to any other options the community can come up with as well, so please feel free to chime in ;)
[BLISS ROMS Development] Kevin_XU:
Thanks for your update, the power button finally works. But I find another problem for getting access to local document. When I open the Files, it just says "can't load content at the moment", just want to know if there is any solution to it.

P.S. when I choose to update Super SU and reboot, it just stuck at the loading page and loop the logo for ... 7 mins now

P.S. I tried another firmware of 11.9, this time the access to local content works well, but power button doesn't work....interesting, I'll try other two
[BLISS ROMS Development] Grumpy Cat:
Been awhile since I've tried Bliss. Much progress with legacy AMD hardware, namely the 4xxx GPU's?
[BLISS ROMS Development] GOOGLE_USER:
So... don't.
[BLISS ROMS Development] beacool:
Thanks for your advice but unfortunately it has the same problem. Touchscreen not working properly. A little side of screen has touchable. Big part of not. I thing it has silead touchscreen

https://github.com/onitake/gsl-firmware/tree/master/firmware/teclast/x5_pro
[BLISS ROMS Development] peter19ji:
I wonder if a KVM over IP remote control solution would help, which even works with a computer w/o an OS. Sunlogin kongkong A2(向日葵控控A2) from Oray costs RMB￥688 (about USD$99, international shipping fee not included) with config-free basic tier remote control service costing nothing but someone who reads Chinese to set up an account. I'm a newcomer at XDA and I don't think I can post a link yet, so maybe contact Oray at 800@oray.com.
[BLISS ROMS Development] electrikjesus:
I'll upload the latest .rpm build for kvm/qemu tonight and let you guys test then.
[BLISS ROMS Development] electrikjesus:
Those should just be permissive warnings, although. I'm not sure how to hide those from the logs. Google might be your friend here
[BLISS ROMS Development] SirDigitalKnight:
Anyone try this on a Lenovo ThinkPad? I have a T520 and was looking at this as a dual boot option? Does this run well in a dual boot config along side Windows?
[BLISS ROMS Development] Mohamed Anwar:
Problem

Hello World,Hello Bliss Team.

I've Noticed that the issuse with Messenger haven't been fixed yet.

Just making sure that you are noticing the issuse.