yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] hamzio7:
Can i use RemixOs installer? And then only Replace the IMG files and the menu.lst?

And my other questions are...

Do i need to replace all the text in the menu.lst?

Do i need to change the name of RmixOs Folder to AndroidOs?

Edit:I added the text to menu.lst

And i renamed the folder too...

Now when i boot to android os it restarts on the booting screen... Where did i go wrong?
[BLISS ROMS Development] electrikjesus:
Don't rename the RemixOS folder for starts. Just replace the items in menu.lst. And make sure you update the AndroidOS folder in those items to be RemixOS, so:

menuentry 'Windows' --class windows {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

menuentry 'Bliss-x86' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 xforcevesa' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 nomodeset' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet i915.modeset=0 nomodeset DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 xforcevesa nomodeset' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa nomodeset i915.modeset=0 DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry 'Bliss-x86 DEBUG mode' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive DATA=/RemixOS DEBUG=2
initrd /RemixOS/initrd.img
}
[BLISS ROMS Development] hamzio7:
Do i need to replace all the text in menu.lst?

Remove the default and put this instead?
[BLISS ROMS Development] electrikjesus:
Not all the text I don't think. paste what you have there in here and I will update it for you real quick
[BLISS ROMS Development] hamzio7:
Still reboots on detecting Android X86
[BLISS ROMS Development] electrikjesus:
The only thing left is to replace the bootia32 & other grub files in the RemixOS folder with the ones from the Bliss iso. Or you are still missing some crutial info as to why it isn't finding it
[BLISS ROMS Development] hamzio7:
Can you please make me an edited menu.lst?

And for the bootia32 & other folders.. I will replace them and try my luck.
[BLISS ROMS Development] electrikjesus:
Please paste a link to t=your menu.lst then or a pastebin of its contents
[BLISS ROMS Development] hamzio7:
It's late here... I will try to send you my menu.lst tomorrow...and thanks again...
[BLISS ROMS Development] kypor:
Hats off to the team! The latest image of Bliss-v10.0-Beta-android_x86_64-OFFICIAL-20180304-1456_k4.16rc3-ga-jdw-2_m18.1.0-devel_w09_fw.iso works great with my Dell Venue 8 Pro 5830. The orientation works! Wish sound was working, but I'm going to see if there is something I can do to get it working. Otherwise, it seems to be working well. Thank you team!
[BLISS ROMS Development] xionbunny:
Oddly google's setup wizard can connect just fine in the last nightly if you run the build in live mode, but when installed it refuses to connect at all, Vmware 14 pro btw, cpu set for quad core, ram 2 gigs, gpu 2 gigs.
[BLISS ROMS Development] NaNo79:
wish to see full support for ipts (SP4) touch screen driver soon
[BLISS ROMS Development] xionbunny:
*delete this post, solved it on my own after days of searching*
[BLISS ROMS Development] electrikjesus:
please make sure your grub entry includes a SRC=...
[BLISS ROMS Development] electrikjesus:
Would you mind letting me know what you did to install it on this device? My test Dell Venue 8 Pro 5830 is not having the same success rate that our users are experiencing. So, I'm really curious now
[BLISS ROMS Development] kypor:
I haven't been doing anything special. Just using the "Windows Installer for Bliss" and installing the iso to the C:/AndroidOS/ folder. However doing it this way I cannot seem to write to system.sfs or root when venue is booted into Bliss Android. Otherwise main issues that I've noticed with the ROM so far are Bluetooth (not important to me at this point), and audio.
[BLISS ROMS Development] chandraprs:
I just installed Bliss Stable ROM and i think there is some incompatiblity with my device, Some android process frequently stopped and my main problem is SuperSU that keeps asking for binary update, when i update it, the update always unsuccessful, Any solution? Or it just due to compatiblity issues?

My System Specifications :

ASUS GL553VD Laptop

Intel® Core i7-7700HQ (2,80~3,80 GHz)

NVIDIA GeForce GTX 1050

8GB DDR4 2400MHz RAM

1TB Seagate HDD
[BLISS ROMS Development] bfmetcalf:
Instead of deleting the post, it would be most helpful if you provided your solution. Glad you got it working.
[BLISS ROMS Development] krono2:
Which versions are more stable "bleeding edge" or "nightly"?
[BLISS ROMS Development] avalanche99:
Hi.

I tried a lot of builds of bliss an now I want to give you feedback.

I don`t know if this is enough information for you so if not let me please know to help get bliss better.

I tried all these builds on an Asus T102Ha 2 in 1 Tablet with the following Hardware:

Intel Atom X5-Z8350 CPU @ 1,44Ghz

4 Gb Ram DDR3 [MENTION=1796504]1600[/MENTION]Mhz

64Gb eMMc Storage

Intel SST Audio Device (WDM)

Realtek I2S Audio Codec

Intel SD Host Controller

I always installed the roms with the UEFI-Installer v26.0003. After testing I also removed Android with this tool.

In no rom my sd card worked, sound on speakers only worked on 1 build.

The latest builds didn´t even start, so I tried to start in nomodset and there I had luck ans screen rotation warked, but still no sound.

If you could get sound work and the sd card slot, then I could use it all day, but without sound I will have to wait until it gets fixed.

I also got a Chuwi Hi10, and if I get some time I can also try some builds on this device, but there will try in live mode, I don´t want do get anything damaged on this dual boot device.

Hope this resume can help the bliss team.

Kind regards

avalanche99
[BLISS ROMS Development] electrikjesus:
Likely the bleeding-edge builds, because those have at least been run through with testers
[BLISS ROMS Development] stonedogSC:
Is there a specific version that has working Wi-Fi? I've tried several variants from stable to nightly to bleeding edge and none seem to have Wi-Fi. otherwise they seem pretty solid (outside of the setup wizard). Happy to try experimental builds if this device isn't one you've run into. Thanks for the cool work!

Samsung Galaxy Tab Pro S
[BLISS ROMS Development] electrikjesus:
As far as I know, your devices chipset just isn't supported in our kernels just yet.
[BLISS ROMS Development] maheshkondraju:
i just checked PhoenixOSInstaller_v2.5.9.375_x86_x64.iso where Surface Pro 4 touch screen works perfectly, may be this bit of information can help building a new bleeding edge build :)

cheers
[BLISS ROMS Development] pinkfloyd3:
there is any way to install v10 on legacy bios ?

sorry for my bad english
[BLISS ROMS Development] Camlin3:
Yeah ,try to burn iso with rufus or try grub2win for windows (high success) ,or syslinux or even grub any bootloader installation first ,after that ,you can add entries for bliss os .
[BLISS ROMS Development] electrikjesus:
I have actually just finished revising the OP's on this thread to help make sense of things a bit better. Hope you're able to find that part of the instructions fine ;)
[BLISS ROMS Development] electrikjesus:
Could you please pass me along any of the firmware files they may have in system/lib/intel/ipts ?
[BLISS ROMS Development] Ealge0110:
Are you sure it works perfectly? Doesn't it stop working after a random period of time?

I though it use the same old IPTS drivers as earlier Bliss builds with Nougat, and many people mentioned it suffer the same problem due to driver's problems on the Chinese forum...

I'd love to be proven wrong, though.
[BLISS ROMS Development] electrikjesus:
So, I finally have a couple builds that have working IPTS, but only for the Surface Book so far. In order to get it working for the other Surface variants, right now, you need to manually mount the system.sfs from Linux, and replace a few firmware files in system/lib/firmware/Intel/ipts/ for your specific device. The firmware files can be found on jakeday's GitHub. I will post these builds once I work out a better way to get things working across multiple devices instead of just the Surface Book.
[BLISS ROMS Development] Ealge0110:
Wow what an exciting news!!! Keep up the good works! Will give a try once it comes out! :)
[BLISS ROMS Development] electrikjesus:
This is the same issue my IPTS builds are facing too. It'll go anywhere from 10-30 min just fine, then all of a sudden, touch stops responding. This is why I am hesitant to release them.
[BLISS ROMS Development] Eagle0110:
Well, there was an earlier post by someone you probably missed (and I couldn't find it with search), but the surface Linux community seem to have managed to get it perfectly working with a custom kernel: https://github.com/jakeday/linux-surface

or this: https://github.com/parryjacob/linux-sp4

Here are more discussions: https://www.reddit.com/r/SurfaceLinux/comments/6eau79/current_state_of_surfaces/

This seems to be an entirely different solution than the iTouch driver thing, I haven't tried this myself and I'm honestly a total noob with Linux, but hope this could help with some inspiration on how to make your amazing ROM to make a big step towards perfection!
[BLISS ROMS Development] electrikjesus:
The route I took this round was using the solution Jakeday took. https://github.com/jakeday/linux-surface
[BLISS ROMS Development] Ealge0110:
Wow!

So using Jakeday's kernel still gives the 10-30 minutes randomly stop working problem?
[BLISS ROMS Development] electrikjesus:
Yeah :'(
[BLISS ROMS Development] Ealge0110:
Oh...

:'(

Perhaps give a try to the other one if you can?

https://github.com/parryjacob/linux-sp4

On the discussion for "what works" post on Reddit, someone mentioned this kernel works with the 2017 Surface Pro.
[BLISS ROMS Development] electrikjesus:
I'm trying that one now
[BLISS ROMS Development] Geometry:
Galaxy Tab Pro S - Wifi solved

Good news for you:

The Wifi for Samsung Galaxy Tab Pro S works fine, at least since linux kernel 4.9 (I have not carefully tested earlier kernel version), but you have to replace one firmware file, see here:

http://www.linlap.com/samsung_galaxy_tabpro_s

This works equally well in linux as in Android.

More specifically you have to replace in "system" the file

lib/firmware/ath10k/QCA6174/hw3.0/board.bin

with the version here:

https://github.com/infernix/samsung_tabpro_s/tree/master/ath10k/QCA6174/hw3.0

You can ignore all other file replacement instructions.

To do this replacement, extract system.sfs in your Android installation into a directory at the same location named "system". Without changing the boot options, Android should automatically read this "system" directory instead of the "system.sfs" file. So there you can make the change.

The Tab Pro S has another problem: Audio does not work properly. The good news is that this has been partially fixed, with the fix included in the linux kernel since 4.12. So if you use linux or Android with kernel version at least 4.12 audio will work over headphone jack and over HDMI. Speaker does not work unfortunately. But with earlier kernels there are additional audio problems.

What does not work for me are the cameras, orientation sensor, GPS and I have also not been able to make them work under linux. If anybody has had some success with these (either under linux or Android), let me know. For almost everything else works both in Ubuntu Linux and in the recent Bliss builds with kernel at least 4.12.

Anyway, glad somebody else is working with the same device.

I would also be happy to test anything on this device that the Bliss builders might propose to solve remaining problems.
[BLISS ROMS Development] pinkfloyd3:
thanks mate

yep i find it thanks u guys

u guys are awesome

sorry for my bad english
[BLISS ROMS Development] lp894:
So....odd scenario. I found that when I try to boot Bliss x86 from a live USB, it doesn't work. But when I install it to the HDD, it DOES work.

2nd Question, any way around the situation of Games not working from the Play Store?

---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------

That being said.....literally everything works except sleep and the camera. When I close the keyboard cover, the screen just flickers randomly and the came says it may be in use by another application.

Gyro, Accelerometer, Touch Screen, Pen input(including pressure sensitivity), palm rejection, speakers get fairly loud (maybe even louder than Windows it seems lol), auto-rotate works correctly......idk what else to report on. If only I could make the fingerprint scanner on my device function as the home button lol
[BLISS ROMS Development] grayhaze:
[MENTION=928479]electrikjesus[/MENTION]: Apparently the issue with the IPTS touchscreen driver failing after a period of time was due to a priority issue. See https://github.com/jakeday/linux-surface/issues/31 for more info. I thought Jake had fixed it, but perhaps not. Sounds like you're making good progress though! If I happen to win the lottery, I promise I'll buy you the devices you need for testing. ;)

I've also seen mention of rotating the screen temporarily solving the issue, but not sure how true that is.
[BLISS ROMS Development] electrikjesus:
Screen rotation is working fine, but has no effect on touch coming back from my tests so far
[BLISS ROMS Development] Ealge0110:
On that issues link there is a post in the discussion mentioning a patch that "bypasses a priority mechanism which seems not supported on Skylake guc and increases the ipts guc priority."

That seems to be what fixed the issue completely and here is the link: https://gist.github.com/sebanc/6be29c1dfbba564a9a15c7b5fcbe96fc

Maybe this could give some idea on how the problem can be solved.
[BLISS ROMS Development] kypor:
I don't understand how you got this to work by extracting system.sfs into the root folder. I have tried to extract system.sfs into the AndroidOS folder (C:\AndroidOS\system) and it does not boot. I haven't changed any boot options in grub either as you mention. Are you sure there is nothing else you did to get this to work? I'm trying to figure out what's missing. Unless you installed this on a partition, and not a folder in Windows?

If I could write into the system folder I could try some great info including sound at the following URL. Great Linux tips for Dell Venue 8 Pro

www.studioteabag.com/science/dell-venue-pro-linux/#ALSA
[BLISS ROMS Development] digital0:
You should use ext4 partition, not ntfs, as it does not support posix permissions.
[BLISS ROMS Development] kypor:
Thanks! So it was a partition that this is installed into. Good to know! :)
[BLISS ROMS Development] electrikjesus:
I'm running a build with this patch to see if it fixes things on Surface Book. If it does, I will try and push that build out and one for the Sp4 too. https://gist.github.com/sebanc/6be29c1dfbba564a9a15c7b5fcbe96fc

EDIT: That seems to have fixed things. Now to figure out why we still loose touch/mouse interaction when a freeform window FC's...
[BLISS ROMS Development] elcidroyale:
I'm coming from Phoenix. In general I loved the idea of booting into Android for more simple computing needs (Windows is bloated and over built for my needs but I LOVE my hardware). The reason why I left that in the dust was because I could not get Google Play services working. I searched the web high and low, tried a bunch of versions and still didn't work.

Now that wasn't the deal breaker. It was:"

I could not control brightness and volume with my hotkeys (oddly the hotkey for keyboard backlight worked). Nor could I find any app or hack to enable this functionality (I found widgets but no thanks).

Does Bliss OS recognize hotkeys for volume, brightness, keyboard backlight, etc? Or is there a app/ hack to program any of the hotkeys on my keyboard?
[BLISS ROMS Development] grayhaze:
Awesome! Thanks for investigating this [MENTION=928479]electrikjesus[/MENTION]. I look forward to testing a build when it's ready.
[BLISS ROMS Development] electrikjesus:
Uploading two IPTS builds now. One for Surface Book (firmware v76), and one for Surface Pro 4 variants (v78)

Other updates include:

Updates for Android 8.1r18 (build/make version is not reflecting this yet)

Updates to other firmware, pulled from Google's Linux/firmware repo

Bug squashes and fixes for various things.

And likely more that I forgot.

Check the Bliss downloads server in the bleeding_edge folder for the downloads
[BLISS ROMS Development] grayhaze:
So far testing the new build on a SP4, everything seems to work great. The touchscreen works flawlessly, screen orientation sensor works, wifi is stable and everything is super fast and smooth. I'm going to try installing to the device, rather than just using live mode from a USB stick, and I'll report back if I find any issues. Thank you so much for working on this for the Surface dwellers. I'll be sending another donation your way soon. :)
[BLISS ROMS Development] 10basetom:
The Live install works fine, but after I copy a 512MB data.img file to the USB flash drive, it hangs on the Bliss OS splash screen. Anybody experience this and know how to resolve this? I'm using a Sony Vaio laptop with UEFI.
[BLISS ROMS Development] Ealge0110:
Wow! You made it!

Installed on to SP4 with the installer, hours have past and the touchscreen is still working perfectly!

I think you have accomplished something some consider impossible.

Wi-Fi is also working and stable, rotation worked perfectly.

The system appears to be incredibly more power effencient than Windows 10 xD

Other bugs encountered so far, in case feedback is helpful:

- Pen not detected (nothing happens when putting the pen onto the screen).

- Any USB storage devices (via the USB port) and SD cards (via the SD card reader) is recognized as "corrupted" even if they are not. I remember read somewhere before that Surface UEFI recognize the SD card reader as USB device so these two could be actually one single problem.

- Bluetooth can add devices but fails to send or receive files.

- Power button seems to turn off the display but not sure if it actually goes to sleep, but it can be "waken up" by pressing the power button again.

- Camera Hardware doesn't seem to work, every app that calls for camera either crash or return error message.

Will report back if more comes up.
[BLISS ROMS Development] Eagle0110:
Okay, almost 5 hours later, the touch screen on my SP4 with the new build stopped working

I got it recovered with a reboot.

Personally, I can live with a touch screen that only probably stops working once in 5 hours...
[BLISS ROMS Development] WoltreX:
A suggestion: It can be a better operating system if the ability to boot on the NTFS file system can be provided (Error: File manager cant see any disk if you re using BlissOS with dual boot windows. So you cant boot Bliss os on NTFS disk.)

You must create fat32 disk for boot Bliss OS. This means that the data file can not go above 4GB. A situation that restricts users.
[BLISS ROMS Development] electrikjesus:
This one may also be that you ran into the free form window bug we have. Sometimes when you resize a freeform window or the app force closes, you lose touch, stylus and mouse input. but you can alt-tab to the app that closed, then hover over the edge of the window, and try to resize again, then you will regain interaction after a successful attempt. (a real b... glitch)

some of those may be false positives too:

- Pen not detected (nothing happens when putting the pen onto the screen).

Pen works perfect on my Surface Book. No cursor like Windows or the mouse. I prefer it that way anyways.

- Power button seems to turn off the display but not sure if it actually goes to sleep, but it can be "waken up" by pressing the power button again.

I haven't tried these yet in my testing, but the usual fixes can be found by adding either poweroff.doubleclick=1 or sleep.earlysuspend=2 to your grub command and see if things act better/different
[BLISS ROMS Development] Ealge0110:
It probably was the free form window bug, there was an app crashing at the time indeed (though due to known incompatibility with Android O I believe. Will give a try to the recover method next time, although I have a feeling I won't run into this again anytime soon lol

For the pen it definitely doesn't work, it is not able to interact with any element on the screen, it doesn't do anything to buttons in the manual, or any other interactive elements whatsoever.

This is strange indeed, it is the same hardware handling touch and pen.

Not very familiar with modifying grub at the moment but will give a try later.

Additionally, the root doesn't seem to work correctly, as no app seems to be able to modify anything in the system partition (and thus makes it impossible to update busy box even manually, for example). But is this actually a bug with SU or is this actually a new security feature of Android O?

Substratum also doesn't seem to work. I installed it from Google Play, it seems able to generate and "enable" theme but nothing happens, and no item show up in "enabled" list. Confined with themes stated to support Android O and dynamic overlay.
[BLISS ROMS Development] Ealge0110:
Actually I just ran into the free form window bug now. I noticed that when this bug occurs I also lose my cursor (it stops being able to interact with anything) . If that is always the case, the touchscreen failure I encountered yesterday would have a different cause, since my mouse cursor was still functional. It could still be the old reliability problem with IPTS.

But honestly, you did make a huge improvement with IPTS reliability.

---------- Post added at 07:09 PM ---------- Previous post was at 06:54 PM ----------

Also, figured the SD card "corrupt" was indeed a false positive.

So apparently our Bliss Rom doesn't currently support exFAT file system, and on SP4 it only reads SD cards with FAT or FAT32 file system xD

(would be good to note to others who wish to try the Rom)

The USB device "corrupt" was probably the same cause, but I don't currently have a spare flash drive to format to FAT32 and try.
[BLISS ROMS Development] grayhaze:
That's really strange, as I've installed it on my SP4 using the Bliss installer (installing to C:\AndroidOS) and my pen works perfectly. It even supports pressure sensitivity in apps like Squid, which I didn't expect to be the case.
[BLISS ROMS Development] electrikjesus:
The root issue is a known issue. As well as Substratum being broken as of 8.1.0r18, so I am on the lookout for a fix for that from the Substratum team.
[BLISS ROMS Development] grayhaze:
After installing to my SP4 today so I could have a proper play, everything's working pretty well. I had fun playing Asphalt at ultra high resolution with the keyboard using Octopus on-screen touch mappings and tested a few more games, mostly of the board game variety. I had hoped to be able to use the Kindle app to read books, but unfortunately all text is invisible. Possibly an incompatibility with the app on x86 architecture, so it's back to the slightly rubbish Windows Kindle app for now. All in all though it's opened up a whole bunch of app options for me, with even lighter games running considerably faster and without frame drops compared to using something like Memu on Windows. I'm sure things will only improve from here, but I'm really happy with what we have now. :)
[BLISS ROMS Development] electrikjesus:
Good find. I will get that added to the release notes next round.