yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
There's also Tincore Keymapper, it's a paid app, but if it doesn't work, Google Play is good at refunds within the first 24-48 hrs.
[BLISS ROMS Development] atg.303:
I installed it on my Asus x541L notebook. It is great.

Is there any way to remove root from iso before installing?

I need to use an app that requires unrooted device.

I disabled root access from superuser app still the app detects root and refuses to run.

I was not able to install Magisk and then use magisk hide.

Any help regarding unrooting or installing magisk is well appreciated.

P.S. The app doesn't use safetynet to detect because I was able to successfully run it on an emulator with failed safetynet.
[BLISS ROMS Development] appollokillers1:
well, octopus is crashing a lot, i get that message with info and close the app, i wander why is not working..., is working perfectly on Phoenix OS, no, not gonna pay for 100 apps that i need and find out that they don't work, someone from this project has to test this things and come with a solution...
[BLISS ROMS Development] GOOGLE_USER:
SMH

You need to utilize the THREAD SEARCH function, supplemented by a desire to read and learn instead of seeking the spoon.

Yeah, you pretty much said that already.

This is not that.

So, your point being... ?

Anyone that can read knows that it was explained to you; the subject of refunds via Google.

So you are just saying, "I'm not gonna ________." [INSERT WHATEVER YOU LIKE THERE, you're just not going to do it.]

Then you proceed, in the same breath, to tell the team what they have to do?

Wait right there for the spoon that never comes.

Suggested course of action: Positive adjustment of your approach or select an alternate source.
[BLISS ROMS Development] atg.303:
No sir its not like that, I have spent around 72 hours trying to run that app on pc. I have tried almost every android-x86 rom and emulator.

Actually the app is an educational app which has video content protected by Widevine DRM. I have subscription of the app and can watch videos on my phone perfectly.

The problem is every single pc rom I installed doesn't have Widevine CDM (according to DRMInfo) except this rom.

So if by any means I just make the app think that the device is not rooted then it would run successfully.

That's what I asked in the first place.

I have read all the previous posts in this thread and could not find my answer.
[BLISS ROMS Development] GOOGLE_USER:
PATHS

I think perhaps my tone came across too harsh in my response to you specifically when, in actuality, I intended to nudge you aside to engage the other member sucking the life of the thread.

My apologies for my brusqueness.

As well-formed as your communication is now I see potential, whereas before I was merely blinded by rage.

[Though again,

not

intended for you.]

I will now simply state, sans animus, that I feel my point remains valid as I present to you the following two keywords:

1) root - yielded this result CLICK HERE

2) Magisk - yielded this result CLICK HERE

These examples are afforded only a cursory glance by my eye.

I encourage you to study them and infer what you will as it applies to your desires.

Also, please consider the BETA status of development.

Root; no root; SuperUser vs. SuperSU vs. Magisk... paths must be chosen at some point to advance the development.

Unless you have enough DEVELOPERS to cover all paths.

A great deal is being covered here already.
[BLISS ROMS Development] atg.303:
Thank you sir for your reply.

I now see that it is not possible to discard root.

But is there a possibility that I could port Widevine CDM libraries from this project to other projects?

I know that these came pre-installed by Google, but I need to know the exact location of these libraries.

I couldn't find anything about it over internet.

Hope you understand.
[BLISS ROMS Development] GOOGLE_USER:
PIECEMEAL

You are welcome.

I would point out to you that customary convention indicates the preferred method of expressing one's appreciation is to click on the button labeled "Thanks!", or has a :good:, or possibly both depending upon the interface one is using to access XDA. You have expressed gratitude and it is accepted. I have not ever specifically requested a click for myself and I clamor for this not from you in the here and now, but for future considerations from

all members

who frequent this, and other, threads.

Diverging diatribe, not directed at you, [MENTION=7295614]atg.303[/MENTION].

Your Bliss Team Members are being woefully under served by this aspect along with some others. And from what I have ascertained, it is indicative of the caliber of the common XDA member posting here, NOT the quality of the offering or those providing.

GREAT SHAME upon any of you that fails to acknowledge a direct interaction or response from a Bliss Team Member by not, at the very least, clicking "Thanks!"

Elevate your interactions, people. Allow them to carry your appreciation with them.

If they have not earned it then why are you here?

Does a project of this scale simply fall into place without great effort, perseverance and, sadly, sacrifice?

To all that mistakenly believe the answer is yes; it does not.

Having read this, you now know and cannot claim ignorance.

I am calling you out for as long as I am here.

Get on those THANKS buttons!

Get in that THREAD SEARCH box!

Get in that FORUM SEARCH box!

Get on that GOOGLE SEARCH box!

Get

yourself

some of this BLISS!

And back, full circle, to you for the anti-climactic close.

I must defer to the team for their response as to whether piecemeal offerings are considered or even possible.

Good luck to you.
[BLISS ROMS Development] electrikjesus:
if I'm able to get one or two more people on the team to help cover my bases I am planning on updating our Android-PC project with widevine and chrome OS Houdini libraries.
[BLISS ROMS Development] SantiOriginal:
Dear Bliss Team,

I Love Bliss OS!

Only thing not working is Bluetooth (it won't turn on/ shuts itself down automatically).

I have a Generic bluetooth 2.0 + EDR adapter - firmwareversion HCI 3. 16384 / LMP 3. 17166 ,

processor Intel(r) Celeron(R) CPU B830 @ 1.80GHz 1.80 GHz,

on a Packard Bell Easy Note TE.

Drivername: nth.inf Class Guid {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}

driverdate: 06/21/2006

Driver provider: Microsoft,

Driver Section: BthUsbGeneric.NT, Driver Rank: 0xFF2000

Matching device: Id: USB\Class_E0&SubClass_01&Prot_01

Device updated: False

Parent Device: USB\VID_8087&PID_0024\5&381eb8db&0&1

:fingers-crossed:

Is there any way that i can make my bluetooth usb adapter from Trust back in the day work? Thank you so much from a fan!
[BLISS ROMS Development] MonsterMunchOri:
I dont know how to upload firmware

I am using surface pro 2017 i5

I installed bliss os in my surface (Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.9.153-ipts_m-19.0.0_ax86-p_f-dev-kernel.org.iso)

But I cant use touch screen,power button,volume key, etc... (only surface keyboard is available)

I think that I have to upload firmware v102,

so I downloaded it, and moved into right folder using zipper app

but I cant moved it because it occur error

If solution is uploading firmware, could you explain how to upload firmware simply or clearly?

or could you propose right solution?

sorry for bad english,

I think there might be someone who is good at Korean.

so I write down same content in korean

서피스 프로 2017을 사용중입니다.

윈도우와의 듀얼부팅을 위해 파티션을 나누어서 bliss os를 설치하였는데요.

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

서피스 키보드 이외의 모든 물리적 버튼이 사용 불가능하였습니다.

서피스 프로 전용 펌웨어를 올리지 않아서 생긴 문제인 것 같았습니다.

그래서 펌웨어를 다운로드 한 후 지퍼라는 파일 관리자 어플를 사용해서 맞는 위치에 옮겨놓을려고 했습니다.

그런데 엑세스가 거부되었다고 뜨면서 안되더라구요.

루트 익스플로거가 필요하다 싶어 구글링해서 설치하였는데 계속 팅겨서 옮길 수 없었습니다.

제가 하는 방법은 제가 생각해봐도 정상적인 것 같지 않았습니다... 살짝 야매로 하는 느낌? 이였죠

혹시 이 문제의 해결책이 펌웨어를 올리는 것이라면,

펌웨어 올리는 법을 자세히 알려주실 수 있을까요?

혹시 이 문제의 해결책이 이게 아니라면

물리적 버튼과 터치스크린을 고칠 수 있는 방법을 제시해주세요...

I

I

I ( translator version)

V

Surface Pro 2017 is in use.

I installed a Bliss os by partitioning for dual booting with Windows.

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

All physical buttons other than the Surface Keyboard were disabled.

It seemed like the problem was caused by the failure to post firmware specifically for the Surface Pro.

So after I downloaded the firmware, I tried to put it in the right place using a file manager named Zipper.

But I couldn't do it when it said that access was rejected.

I went to Google and installed the root explorer because I needed it, but I couldn't move it because it kept stopped.

The way I did it, it didn't seem normal to me... It's like a little bit of a trick.

If the solution to this problem is to raise the firmware,

Can you tell me how to upload the firmware in detail?

If this isn't the solution to this problem,

Please show me how to fix physical buttons and touch screens...
[BLISS ROMS Development] electrikjesus:
I am not going to repeat myself any more than I have to, this is why I added the "Specific Surface model instructions" section to the second post of this thread.

Can't get much easier that that.
[BLISS ROMS Development] Kevin_XU:
Dear Bliss Team,

Thank you for your hard work on this project and sharing. I love this system!

I just installed 11.8 on my Surface Go and it works well. The WIFI works fine, touchscreen and keyboard look fine. The only problem is the power button, it doesn't work and I cannot lock the screen. It's wired as the volume buttons work well. Is there any method that I can use to solve this problem?

(P.S. I tried your surface instructions on the first page, but it's for wifi issues and my wifi works fine, and the response on terminal is sudo: not found)

Thanks anyway
[BLISS ROMS Development] electrikjesus:
Just use the root terminal (alt-f1), shouldn't need the 'su' command this route
[BLISS ROMS Development] Kevin_XU:
Thanks for your patience.

So I need to use the root terminal to try "For Surface Go users, you will have to remove some files and replace with the Jakeday's firmware. Please see this thread on Reddit: " ? This one for Surface Go? It says it's for WIFI function, will it be workable for my power button problem?

P.S. I just tried the root terminal to replace the firmware, but it says "mv: bad 'sdcard/surface/*‘: No such file or directore". I think I might make some mistakes on the codes and don't know how to get the correct path of the ath10k document?
[BLISS ROMS Development] atg.303:
For all of those who want to install Magisk in this or any other android-x86 based rom, please

consider and study

the method shown in THIS VIDEO by Infernal.

It worked for me on my

Asus X540LJ

notebook.
[BLISS ROMS Development] electrikjesus:
Sdcard is a representative of where you want to extract things first.
[BLISS ROMS Development] ElfinJNoty:
https://review.blissroms.com/

Bliss OS is compiled from the same source as our ROM, with additional patches for x86.

If you need help with compiling.... All relevant info, including our Telegram support chats(we have one specific for build help) are linked via BlissROMs.com, as well as all source links ?

I don't recall how big our source files are, but should be fine with that amount of storage
[BLISS ROMS Development] electrikjesus:
If you actually read the opening of the OP in this thread, all related instructions are spelled out for you.
[BLISS ROMS Development] jotade:
Hello everyone. I have a Dell and i have installed a lot of android x86 roms. And in no one i can get directv to work. Does anyone knows how to fix that or which version is working of the buildings? Thanks
[BLISS ROMS Development] MoistPicklez:
[MENTION=928479]electrikjesus[/MENTION] Just wanted to ask if there might be a way to remove Superuser and the corresponding folders in /system using the terminal by chance?

I tried a few different methods I searched for online, but nothing so far has worked with Bliss. Root or not, you guys put a ton of time and effort into this amazing project, many many thanks for everything.
[BLISS ROMS Development] electrikjesus:
It's built into the distro from source, so removing it without doing so on the source level is likely not possible.

If you represent a business or corporate venture, and are looking to remove su for your project, this is one of the reasons why we offer our paid development services.
[BLISS ROMS Development] appollokillers1:
oh well, no idea what's with you and the spoon... your jub here is to give answers and solutions for the ppl, all coming here for that, is no reason to get grumpy for anyone, just be open minded and listen what others say or ask, is not for nothing, many projects started for pc and all were abandoned,so... good luck with the project, gd jub til now
[BLISS ROMS Development] MoistPicklez:
While I appreciate the info I could not afford something like that. I am just a humble Bliss user, however I will donate when I can to support the project without a doubt. It's for a worthy cause!
[BLISS ROMS Development] electrikjesus:
I am still considering the prospect of an unrooted EDU build on down the road, but there's a lot of work that needs to be done before I could even consider such a release variant.
[BLISS ROMS Development] electrikjesus:
What are you replying to here?
[BLISS ROMS Development] GOOGLE_USER:
Despite the lack of quoting or tagging, I recognize this as being addressed to me, [MENTION=928479]electrikjesus[/MENTION].

The following response is inspired, though not necessarily or specifically endorsed, by the Bliss Team.

I speak neither explicitly nor implicitly as a member of this team; rather, I speak as an XDA member.

I hope this rectifies your apparent misconception regarding my status here.

What is with me and the spoon?

I was alluding to the following term, defined as:

spoon-feed

-- to present (information) so completely as to preclude independent thought

This is what you, along with far too many other members, seem to

expect

.

This forum is not a customer service hotline and you are not a customer in the generally accepted definition.

You have purchased nothing and that is what is owed to you; nothing.

What is offered is generous and useful. It is not, as you say, a job.

To wit:

This is your misconception.

This is your corrective measure necessary; follow your own words and you will have provided, and adhered to, your own advice.
[BLISS ROMS Development] GOOGLE_USER:
On the other paw...

That's what I'm talking about! Go get it!

Clicking thumbs-up buttons, requesting permission over there on YouTube to post link in here, and giving credit...

You deserve some credit yourself.

Do exercise a degree of caution when recommending someone else's works. Let that individual be the one to make broad claims regarding the efficacy of the work. It may be true that it is functioning, as stated, in numerous scenarios. But how many of those can you vouch for?

Yours, and yours alone.

Don't set yourself up for some knucklehead to come back trying to cause you grief because it didn't work for their device.

Something like this

:

For all of those who want to install Magisk in this or any other android-x86 based rom, please

consider and study

the method shown in THIS VIDEO by Infernal.

It worked for me on my

XXXXXX

device.

I hope it has allowed you access to your application. And excellent find, my friend.

In the next few days I'm going to PM you with instructions on how to insert a link as I did in the example above.
[BLISS ROMS Development] atg.303:
Yes, after installing magisk the application worked.
[BLISS ROMS Development] electrikjesus:
If you guys are working on the latest build, could you pass the patched ramdisk.img link to me in a PM please? I've been looking for a way to automate this process through the OS, or in the least, at build time, but I haven't figured out what he's patching in the ramdisk. I can make that change in the source and run off a build with it integrated if I knew what he was patching and how.

[EDIT] This might also be just one of those things I need spelled out for me to even understand.
[BLISS ROMS Development] GOOGLE_USER:
Ramdisk.img

Gladly!

Unfortunately, I have yet to incorporate this since I have been allowing my system to remain "as delivered" for testing purposes.

Given that the weekend may afford me a little time, I would implement this procedure if [MENTION=7295614]atg.303[/MENTION] does not respond before tomorrow -- when I return to my machine's location.

This was [MENTION=7295614]atg.303[/MENTION]'s find and if possible I would avoid stealing any thunder. A decision made easy due to proximity issues. :laugh:

However, I'll not leave you chomping at the bit once I have access, should you not have received the ramdisk img yet.

Also, if you like, perhaps Infernal may be receptive to opening a line of discourse and I am willing to try that route if the ramdisk.img deciphering proves problematic for some reason. I say this to avoid stretching you thin if you are otherwise engaged. But, again, trying to show some restraint because this wasn't my baby.

I would point out that Infernal is a YouTube moniker, and though an XDA member exists it is presently unknown to me if they are one in the same.

I will abide by your preference in whatever manner I possibly can. You need only state it, if you are still empty handed in 24 hours.
[BLISS ROMS Development] IcedCube:
Hey electrikjesus,

This might seem off the topic of Bliss OS and I don't want to derail the topic, but if you could hear me out that'll be great.

I've noticed some Android emulators, like Nox, Andy OS and friends use some sort of emulation layer like QEMU or something else (VMWare Player in the case of AndyOS) to provide their "Android on Windows" experience. However, something is a little strange with them: Even though the disk images they use are x86 (which makes sense, since they can utilize the native CPU virtualization capabilities), they come up as an ARMv7 or AArch64 device to Android. For example, Andy runs x86 applications as evidenced by the ".x86" suffix on Google Play apps, but for example inside my Unity GPU testing application, it was reporting "ARMv7 NEON rev 4 CPU".

So I assume those emulators are using some sort of "information faking" facility to fool applications they are actually running on a phone/tablet. Running "cat /proc/cpuinfo" in those emulators reveal the true identity of the CPU, which in my case, was my Ryzen 5 2600 with 4 virtual CPU cores.

I'm not saying that Bliss OS should copy this behaviour, but from your point of view, is it possible to "fake" CPU's information to the Android applications? If so, does it just apply a shim to the application so if it does try to poll for the CPU information, it gets dummy data? Does Android x86 do this automatically for compatibility reasons? I assume that an APK that contained a runtime that was not x86 (armv7/aarch64) would fail to launch on Bliss OS since there's no binary translation layer.

Also, I haven't checked out Bliss OS (yet) on my Intel NUC. Really been meaning to... just been busy with other stuff. What is the status of hardware accelerated 3D graphics and such in general for Bliss OS?

Cheers,

IcedCube
[BLISS ROMS Development] abhinavsri01:
No Display at boot !!!

Hi

As soon as I select Bliss OS Live..I receive a message "Detecting Android x86.... Found at dev/" but soon after that my Display goes off.

I waited for a long time but to no use.

I tried running the No Hardware acceleration mode - but I dont get a proper display just some vertical lines.

Can anybody help me please?

I'm using Dell 3162 Laptop

Celeron N3060

2GB RAM

Intel HD 400

32 GB eMMC
[BLISS ROMS Development] electrikjesus:
It's the CPU. for that processor, you're going to want to try thr 4.9 kernel releases. If that doesn't work, then you'll likely need an earlier kernel, like 4.4
[BLISS ROMS Development] MoistPicklez:
Well I followed the instructions to get Magisk installed which worked fine but I could not run my application is still detected root, probably from Superuser which wasn't able to be fully removed however it's a good start and it worked with Bliss without issues. Gonna keep tinkering to see what I can accomplish.
[BLISS ROMS Development] DrakenFX:
I manage to switch from "Superuser" to "Magisk" here are the files if needed for further development , thanks [MENTION=7576522]GOOGLE_USER[/MENTION] for the video and big thanks to [MENTION=928479]electrikjesus[/MENTION] for BlissOS_x86

Device in use :

-------------------

* Dell Venue 8 Pro (5855)

* intel X5-Z8500

* 4GB Ram

* 64GB Storage (using Android_x86 Installer)

BlissOS Release:

* Bliss-v11.8--OFFICIAL-20190420-2101_x86_64_k-k4.9.153_m-19.0.0_ax86-p_f-dev-kernel.org_gms

initrfd , ramdisk , kernel files in the following link

https://androidfilehost.com/?fid=1395089523397964075

Edit:

Only issue with this build and any other build in that matter is

* Bluetooth crashing or not working at all.

* No sleep / suspend.

I'll post a logs with the current BT issue, later today or tomorrow.
[BLISS ROMS Development] ElfinJNoty:
Thanks for sharing your files ?

Is Bliss OS..... Not "BlissOS_x86"

And for what it's worth, it was not Mr. Google_User who shared the Magisk installation video. And he points that out himself.

There have been several attempts today to include Magisk at build time. [MENTION=928479]electrikjesus[/MENTION] is working hard this weekend. As always, gratitude is most deserved for his efforts.

Stay tuned for further updates
[BLISS ROMS Development] Grumpy Cat:
Any chance of increasing the server bandwidth for downloads or using file hosting sites? It took 5 hours to download the last build.
[BLISS ROMS Development] Grumpy Cat:
Can't boot via live, can't even use it in a virtual environment.

Thoughts?
[BLISS ROMS Development] electrikjesus:
Sounds like you got a bad connection or mirror server there. Which led to a bad Iso.

We pay our server costs out of our own pockets. So if the public feels it's not enough, then the public can pull their resources together to fix it.
[BLISS ROMS Development] Grumpy Cat:
Works in Virtualbox. Maybe it's my CPU, it's a first gen i7.
[BLISS ROMS Development] electrikjesus:
It could be many things. Can you provide a list of devices your PC has?
[BLISS ROMS Development] AndroTech:
Tried on a samsung N140 netbook (2010 model), stuck in boot menu.

Any help!!!
[BLISS ROMS Development] electrikjesus:
Nope. All the steps needed to troubleshoot have been provided in the second post. Unless you can detail what steps you've taken from there, we are unable to help you
[BLISS ROMS Development] DoughMucker:
Tried the IPTS version of the beta preview with my Surface 2017. Here are my initial comments and observations.

After changing the firmware I was able to use touch.

I kept experiencing some type of app or system issue...the app I was trying would quit and the system seemed to restart at the lockscreen.

I see an issue with Bliss that existed with Android-x86... root permissions don't seem to persist through a reboot.

I initially tried to simply overwrite the existing .img files of my Oreo installation. That resulted in the system getting stuck with an animated, yellow Bliss logo. After looking at the grub files on the working USB stick, I see that adding "androidboot.hardware=android_x86_64" was needed as a grub option.

Thanks for the build! I'll get some proper logs for any issues I have when I get time to give it a better trial.
[BLISS ROMS Development] pankspoo:
How to install apps after usb side loading?
[BLISS ROMS Development] ElfinJNoty:
Download .apk

Click .APK

Chose install

When prompted to allow installation, say yes.

Use a file manager of your choice to locate and select .apk

However... If this is a troublesome task(installing an application?!?) You should not be using Bliss OS at this time.
[BLISS ROMS Development] pankspoo:
Its just saying cant install the app i think rom Don't have apk Installer. If its not installing any app then how to Install other file manager
[BLISS ROMS Development] ydd0ras:
U have F-Droid pre-installed. Download and install the Amaze file manager or I.e. the MiXplorer from XDA.