yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ElfinJNoty:
Dude...

Our team is made up of devs around the planet who all have personal lives. We have been busy working on Android Pie and I'm sure you and other users would want to see BlissOS reach Android 9 ?

We could have replied immediately to your requests for support... And would have told you to help us locate working drivers for your device using a Linux distro. It is unfair to assume that we should go out and discover the solution for you specifically, and ignore our to-do list and other developmental efforts we are already engaged in. You were not ignored, just didn't have a solution to hand feed you quick enough for your liking.

While I am very glad you managed to figure out a way to make touchscreen work for your device.... I am almost glad now that nobody stopped what they were doing to provide you personalized assistance. It turns out it forced you to learn something, which benefited your experience and could also benefit others? Part of what the Android community is all about is testing things and sharing your results.

.

We find ourselves very busy trying to make Bliss OS the best Android experience possible. That involves achieving compatibility for 1000's of devices. On behalf of Team Bliss... We'd appreciate it if you shared your method to achieve better functionality and benefit other users
[BLISS ROMS Development] ElfinJNoty:
I'd also like to point out that XDA is wonderful enough to provide a "search thread" feature which can help users to find all sorts of useful information that has already been covered. This helps to locate useful info from our development team, as well as info provided by helpful users.

I quoted this post by [MENTION=928479]electrikjesus[/MENTION].... Just in case it proves the answer was here all along and could have been easily located without losing patience, insulting our team, and THEN refusing to reshare positive results
[BLISS ROMS Development] electrikjesus:
You could submit the fix on our github, or PM me about it on XDA, or Telegram [MENTION=928479]electrikjesus[/MENTION]
[BLISS ROMS Development] electrikjesus:
Surface - Switching Firmware

Further details were found easily using the Search function on this thread. If it takes me 5 min to find it, it shouldn't have been that hard. I just wish people would put more effort into things I guess. Maybe my expectations are skewed...

Maybe someone that is using a Surface device other than the Surface Book could make a guide with photos or a video walkthrough of doing this for all the Millennials out there ?

https://xdaforums.com/showpost.php?p=76896155&postcount=2107

https://xdaforums.com/showpost.php?p=77241202&postcount=2233

Just to consolidate
[BLISS ROMS Development] xhamadeex:
Thanks for the links. I'll try to do it but I don't think I will succeed as the method doesn't sound clear to me. Further instructions would be greatly appreciated, as I have no idea how to do it.

Cheers!
[BLISS ROMS Development] xhamadeex:
Does anyone know how I can change permissions to 644? The instructions in the second link says that and I tried to google it but I didn't find how. Thanks!
[BLISS ROMS Development] electrikjesus:
I'm a little behind, but I am uploading the last bleeding-edge build I promised (the one without the IPTS commits) All changes on that build are even with my last release post.
[BLISS ROMS Development] Adream09:
pls help me

================Installer Info================
Installer Directory:C:\Users\user\AppData\Local\Temp\RarSFX0
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: Dell Inc.
Model: Inspiron 5558
Product: 0WMF3P
BIOS info:
DELL - 1072009
A15
American Megatrends - 50009
Available GPU(s):
GPU: Intel(R) HD Graphics 5500
GPU: NVIDIA GeForce 920M
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
OSVer: Microsoft Windows NT 10.0.17134.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 8/12/2018 10:41:06 PM====
-ISO File: D:\araçlar\Bliss os\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified.iso
-TargetDrive: X
-UserData: 27262976
-Setup Directories...
-Folder Created: X:\AndroidOS
-Extracting ISO
#Launch:C:\Users\user\AppData\Local\Temp\RarSFX0\7z.exe x "D:\araçlar\Bliss os\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oX:\AndroidOS
#Launch:C:\Users\user\AppData\Local\Temp\RarSFX0\7z.exe e "D:\araçlar\Bliss os\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified.iso" "boot\grub\grub.cfg" -oX:\AndroidOS
-Creating Data.img
#Launch:C:\Users\user\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=X:\AndroidOS\data.img count=27262976
-Initialize Data.img
#Launch:C:\Users\user\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "X:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Directory is Already Exist
==============Revert Installation==============
-Cleaning up Bliss Directory ... X:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:

The directory is not empty.

-Remove Android UEFI Entry
-UEFI: -1
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
====Uninstall Started on 8/12/2018 10:44:17 PM====
Android Installation Not Found
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Remove Android UEFI Entry
-UEFI: -1
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================

I could not operate the operating system. The mistakes I have made are as above.
[BLISS ROMS Development] peterandrewd:
Yes it made me learn something, but regardless, not everyone is a dev on here, and could've at least replied to point me in the right direction.

This forum is designed for support and helping others...as you said...but no one replied to me or helped me (even though this forum is designed for supporting others, etc), so if people don't reply to or help me, I don't help them or others. Simple.

I do understand you are busy though, and I do appreciate and respect that, and thank you for your assertive non aggressive answer.

Look, the only way I'll share my solution is if I have a guarantee of sorts that next time I'll be answered.

Despite what the answer to my questions were (to locate the linux distro for my device)...it still would've been nice to get ANY answer rather than leave people hanging.
[BLISS ROMS Development] xhamadeex:
The latest bleeding edge rom is only 469.8MB. Is this correct?
[BLISS ROMS Development] electrikjesus:
No, it failed uploading so I'll have to fix it when I get home
[BLISS ROMS Development] xhamadeex:
Thanks! Do we still need to update the frameware files to get touch to work on SP4? I appreciate your help!
[BLISS ROMS Development] electrikjesus:
Likely, yes.
[BLISS ROMS Development] DoughMucker:
You need root (included in BlissOS) and to grant superuser permission for Total Commander or whatever file manager app (with root capabilities!) you are using. After that it's just a matter of selecting the files, right clicking and choosing properties and changing the permissions.
[BLISS ROMS Development] xhamadeex:
I changed the permissions into

rw r r

And it worked.

However the touch screen stopped working after few minutes. The problem is still there. Did I set the right permissions?
[BLISS ROMS Development] DoughMucker:
You impatiently made several posts within a day at the start of a weekend and expected an immediate response. You said you were patient. That's not patience.

Now you state you'll only post your supposed solution with some type of guarantee to be helped quickly? I hope you can see the hypocrisy in that, but based on what you have written above, I'm thinking no.

Initially I had troubles updating my drivers and had to figure some of this stuff out myself. I posted what I learned to help others. You should too.

---------- Post added at 08:03 PM ---------- Previous post was at 07:51 PM ----------

You probably did everything correctly. There is a known problem with the driver. Sometimes mine works for a long time. Sometimes not.
[BLISS ROMS Development] xhamadeex:
This really sucks! I guess I'm not gonna be to use it until a fix is found!:(
[BLISS ROMS Development] peterandrewd:
Of course...on a weekend is usually when people aren't at work, etc...therefore you'd think they would have more time to respond.

Also in my country, it wasn't the start of the weekend, it was the middle-end of the weekend.

Based on your response, having a dig at me, now I definitely don't want to post the solution.

If we could work something out, where I get responses, and I stop being "impatient"...then I'm happy to call a truce and start helping others and actually contributing.
[BLISS ROMS Development] Ealge0110:
Tried 10.1 Beta released on 8/12. Just like version 10.1 Beta build released in July, the legacy way for app to recognize SD card path does not work, apps that do not support document provider, such as Neutron Music Player, basically have no ways to access the SD card. This was not a problem in previous 10.0 Beta builds.
[BLISS ROMS Development] KevMetal:
Jaja ... I think you don't have any solution ... you just thought you would somehow "spite" the people you believe are somehow obligated to help you like you paid for a service or something ...you are waaay toooo entitled ..why still hang around here if you have your device working and aren't interested in helping people ? the answer is clear in your "truce" that you still think you are going to extort the information you seek by offering a bluff as recompense ...you helped yourself so just say thanks to the thread for motivating you to learn sonething and then go ..:fingers-crossed:;)
[BLISS ROMS Development] peterandrewd:
???

Funny guy. I do actually have a possible fix but believe what you want
[BLISS ROMS Development] peterandrewd:
When will the new bleeding edge build be uploaded?
[BLISS ROMS Development] mikekoz:
I just tried this on my Surface Pro 3 and it did not work. It installs with no errors, but gets stuck at a black screen when the tablet reboots. The black screen does not show any errors, just shows drivers being loaded. I have actually tried several of the Oreo Bliss roms with the same result. My Surface Pro has been a bit of a disappointment in this regard. It is just not very receptive to 3rd party roms! :(:crying: I am not going to give up, however!
[BLISS ROMS Development] DoughMucker:
It's no dig at you. It's the definition of hypocrisy to believe one thing (insisting that you should be helped) and to behave the other way (like you won't help others). And it's bad form at xda to not share. Good luck getting help with anything else with that attitude.
[BLISS ROMS Development] electrikjesus:
Lesson for the day:

[YOUTUBE]https://www.youtube.com/watch?v=arJLy3hX1E8[/YOUTUBE]

Point being, we can offer them all the help in the world, but in the long run, the help they really need can't be found here on XDA.
[BLISS ROMS Development] peterandrewd:
If the previous post wasn't a dig at me, then this one definitely is with the last sentence.

I behaved that way because I treat people how I've been treated, weather that's hypocritical or not, I don't care.

Also just for the record, if people are nice to me, make the effort to answer me, use manners, and just generally show niceness to me regardless of what I post, then I do help them. And will help them. I've had a couple PM's I've replied to and helped them...soooo, people should help because privately I have been helping others...
[BLISS ROMS Development] ElfinJNoty:
I'm just gonna come out and say it....

Weather or not you are a "nice guy" on a regular basis, is irrelevant at this point. All you've done thus far in this forum thread is demonstrate impatience, act entitled, be rude, and try to impress some type of obligation on others to cater to your needs.

Your time frame is now not something anybody cares to consider. Your entitlement is unwelcome. Your rudeness has been obvious and disrespectful to Team Bliss as well as your fellow XDA members, and you should expect little to no assistance in answering any potential question you might have about Bliss OS moving forward.

We we're unable to meet your unlofty expectations. And your attitude since has steered me towards completely ignoring you in the future versus lending any of my time and effort to resolve anything for someone so undeserving. Bliss OS, Team Bliss, our developers/graphic designers/testers/users are all being asked as of this moment, NOT TO ASSIST THIS MAN and DO NOT REPLY in this forum to anymore of his messages. If he continues to post, I will grab the attention of one of our XDA Admins to clean up the thread and remove him from our presence.

In the meantime, let this serve as a clear example of how NOT to interact with a development team and it's userbase. We don't care if you use BlissOS. We will not cater to your blatent disrespect and demands.

Can't make everyone happy. Hope everyone else had a productive Monday and a great start to their week...

#StayBlissful
[BLISS ROMS Development] suzook:
Anyone install this on a NUC??? I have one laying around. It has Windows 8 on it, but bored, thinking Of using Android.
[BLISS ROMS Development] emyers6:
Sorry if someone has already touched on this topic but I feel like I've scrolled through all 200 some pages and I've seen nothing on the subject. My sole purpose for installing Android onto my surface pro 2017 i7 model was to be able to play mobile Android games from a legit Android platform. I did not want to have to spend a decent chunk of change on a worthy tablet just for that. I've tried BlueStacks etc they run like crap on the sp4 because of all the thermal issues it has and I've tried every remedy still doesn't work right. Anyways to my point, can anyone shed light on the reason as to why in PUBG mobile for example it will not let me turn my graphics up and sets all my settings at low and says due to the specs of my device... I have the 7th gen i7 so 2017... My Google pixel 2 xl can run PUBG beautifully on the highest settings and framerate available but my i7 surface pro can't? Is it because Android runs crappy on a 64bit processor vs an ARM processor? I'm completely baffled. Anyone?
[BLISS ROMS Development] ElfinJNoty:
....both your i7 and your Pixel 2 XL's CPU are 64bit

I think you mean x86 versus Arm64

The reason is that your games were intended to run on ARM architecture. You'd have to install a vanilla Android-x86 build and attempt to run the same game/s in order to verify that this isn't simply an issue with the game not being optimized for x86 hardware(CPU anddddd GPU)

We have no control over app developers desire to provide support for x86 hardware.

Probably not the answer you were looking for, but truth non the less
[BLISS ROMS Development] electrikjesus:
On our tests, mostly everything worked
[BLISS ROMS Development] ElfinJNoty:
The installer is attempting to mount the EFI but the location is already occupied by your previous install.

Please open the installer, first click on "uninstall Android", then resume your regular install steps.

Video link for reference:

https://youtu.be/0UkPyYfj0xA
[BLISS ROMS Development] zeldatsuki:
Nvm i give up on this till the touchscreen works properly on surface, i got it installed by reinstalling windows, anyways as per usual the touch screen only works a few minutes then dies.

---------- Post added at 03:16 AM ---------- Previous post was at 03:04 AM ----------

Thanks for the reply, but that wasn't working, tried it several times before, only thing that fixed it was reinstalling windows. Hope to see updates in the future for surface pro 4 that has proper working touch firmware, thanks for your effort :) This is a really awesome project with a lot of potential!
[BLISS ROMS Development] tobad:
[MENTION=2543135]osbaldov[/MENTION] [MENTION=8756998]kypor[/MENTION] [MENTION=798224]drellisdee[/MENTION] [MENTION=4726518]avalanche99[/MENTION]

any news for ASUS T 101HA / 102HA users?

is sound working for you?

which builds are you guys using currently?

did you try the build (https://downloads.blissroms.com/Bli...d-ath-crt_18.1.0-devel_w14_dev-kernel.org.iso) with drellisdee patch to enable intel ish, cherry trail features, and the rt5645 for sound?

thanks in advance for sharing your bliss experience

just, tobad
[BLISS ROMS Development] mikekoz:
I thought I would share this with anybody out there that owns a Surface Pro 3. It looks like I finally found a Bliss ROM that likes my tablet! This past weekend I installed one of the Bleeding Edge ROM's that was made for the SP4 on my device. There are two available, and I think I used the more recent one. I am at work right now, so I cannot verify! Anyhow, the other Oreo ROM's I have tried would not even load. This one got off to a slow start as the Surface's keyboard initially did not work during setup. I used the virtual to finish, disconnected and reattached the keyboard, and it has been working ever since! The only problem I am having is when it firsts boots into Android, I get a few Google Play Service and process errors. Wifi works, but is a tad bit slow. Bluetooth turns on, but I have not tested it. The touch screen works great, and even auto-rotates. The camera is even working, although I will never use it. My Surface was one of the high end models with an I7, 512 GB SSD, 8 GB ram, etc, and everything so far is running smooth as a baby's bottom!! I will post updates if I run into any issues later on. Right now getting this to work has justified my investment in this tablet! Thanks to all of the Bliss team for creating these ROM's and making them available!! ;p)
[BLISS ROMS Development] ElfinJNoty:
Do us a favor and verify the name of the .iso you used for your successful experience on your SP3.

Planning to make some edits to the OP with updated suggestions or perhaps a FAQ soon...

Will likely add your findings. Thanks for the contribution ?

#stayblissful
[BLISS ROMS Development] kypor:
Hi tobad. I have tried that ISO mentioned however it only boots to a black screen. If I have to use nomodeset to get it working then it's not worth it, because the graphics are slow. So in short, I don't know if the drellisdee patch made a difference.

Also, for older ISO's that have worked, I was unable to install the games/apps I would like, however they did work on Androidx86. Different Houdini libs I suppose.

So in short, I haven't been able to use Bliss yet :(
[BLISS ROMS Development] mikekoz:
Will do! I can take care of that this eve. You are welcome!!
[BLISS ROMS Development] tobad:
thanks for feedback!

so which Androidx86 build do u use and does sound work with it?
[BLISS ROMS Development] mikekoz:
Oddly enough, it looks like there are three ROM's for the SP4 in the Bleeding Edge folder, and I used the oldest one! The file date on the download page is 3-13-2018. The filename has a date in it of 20180312, followed by -2126_k4.15-sb-ga-jwd_m17.3.6_surface-pro-4. This now leaves me with a conundrum! Do I stick with this one, or install the one dated 20180602? I am guessing there is no way to just upgrade to the later one? My gut instinct tells me that if it is not broken, do not try to fix it, but my curiosity may get the best of me!! :laugh:
[BLISS ROMS Development] ElfinJNoty:
If you used the UEFI Windows installer... Go-to your install directory and examine the contents.

If you want.... You can rename or move out of that directory. Then extract another .iso, and replace the content you originally find in the install directory(by default is C:/AndroidOS/)

Kernel, ramdisk, data, system can be extract from .iso and moved into that location. Is how we usually test on the fly. This is basically a dirty flash comparable though, because you are leaving the data.img intact. There are tools to manipulate the data partition. And most of the time switching between build of the same version(10.1 to 10.1 for example) it is okay to use the same data.

Like I said. Dirty method. But works without issue most of the time for quick nightly build bumps.

We try to announce when a completely fresh install would be neccessary
[BLISS ROMS Development] kypor:
I don't use Bliss or Androidx86 at the moment, as neither works. So far, I hate to say, but Andoidx86 works smoothest, only issue is no WiFi. Bliss there were older builds that worked, not sure which anymore, but then I couldn't use the apps/games I wanted. In short, I don't use anything but I keep testing new builds to see if something magical happens
[BLISS ROMS Development] mikekoz:
Thank you! I may try it this evening. It looks simple enough, and I have enough space to backup the folder in case it no workee!!
[BLISS ROMS Development] mkam89:
Has somebody experience with compiling the selinux enforcing mode at android x86?
[BLISS ROMS Development] mikekoz:
Tried this on the Latest ROM for the SP4 and it did what all the other Oreo ROM's did on this tablet.....stalled at a black screen. Tried the other ROM, dated 3-17, and it booted, but had no root access. I just copied back my backed up files and put it the way it was. It is back up and running again. Thank you for your suggestion though. I may try this again if I see another ROM pop up I want to try!
[BLISS ROMS Development] electrikjesus:
It looks like your devices favor either the kernel branch: k4.15-sb-ga-jwd Or mesa branch: m17.3.6. I'm leaning a little towards the combo of both

So when I can get a chance, I will run off a newer build with that combo for all the Surface users again. I can't promise I'll have the time to run off a build for each specific Surface flavor like before through. We will try and get some more detailed instructions together for the Surface devices and updating the firmware on those though. I really do want to make it easier on everyone. I just don't have the time I used to.
[BLISS ROMS Development] mikekoz:
That sounds great!! I will keep my eye open for them!! Thank you!!!
[BLISS ROMS Development] Rakivic:
Bliss-x86 crashes when android set up device screen appers

While I can get Bliss to boot on my PC with out issue. Every time the, android set up new device screen appears. Bliss completely locks up, and then my PC restarts. I followed the guide to get Bliss to boot and run from my USB. Using RMXtools to create the data.img. Does anyone know why this is happening or how I can fix it? I made the disk over 2X and the same thing keeps happening.

I am trying to use Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org.iso

Thanks

Edit: I also completely shut down my Antivirus when making the disk

My system specs are:

i7-8700k

Asus Maximums X HERO w/bios v 1602

Secure boot is disabled
[BLISS ROMS Development] ElfinJNoty:
You can add a command to grub boot menu entry:

SETUPWIZARD=0 (only needs to be booted once with this command, try hitting "E" to edit in grub screen)

Try this since you say that is what is crashing and rebooting.

You will likely receive FC's for system process and Google services.... Until you have an active internet connection. Just dismiss the FC's if any and go-to settings upon boot and establish internet. Verify you can boot into homescreen with this ? then we can further troubleshoot
[BLISS ROMS Development] dcooper:
What is the latest working iso for surface pro 2017

I was looking through the bleeding edge downloads, but I am unclear as to what iso is the latest for the surface pro 2017. The image I downloaded was Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180316-2333_k4.15-sb-ga-jwd_m18.1.0-devel_w09_surface-2017.iso Is this indeed the latest working iso, or can I pick from one of the newer images?

Thanks.