yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ajay131:
I will go home after 4/5 hrs and then will disable" legacy only", will boot and post ss.

Otherwise I will format my partitions C and F. Will install AndroidOS first. Try to boot it. And then will install Windiws on C drive.
[BLISS ROMS Development] ajay131:
I have disabled legacy
[BLISS ROMS Development] vittpda:
BLISS WEbSITE DOWNLOAD SECTION HAS NO ROMS ?

Went to the download section of bliss os downloads and there were no links? anybody having an issue today?
[BLISS ROMS Development] Guimenez:
No files today for me too
[BLISS ROMS Development] ajay131:
which link are u trying?

Try link from download section.

https://downloads.blissroms.com/BlissOS/
[BLISS ROMS Development] Guimenez:
Yes, all folders are empty
[BLISS ROMS Development] ElfinJNoty:
https://sourceforge.net/projects/blissos-x86/files/Official/

All builds of Bliss OS have been archived to the above link
[BLISS ROMS Development] Atlas974:
Sound Cherry Trail Tablet

Hi!

Would it work on any Cherry Trail based tablet?
[BLISS ROMS Development] fastguy:
Hi, thanks for this update. I will check tonight. Is there a git repository or similar to obtain your kernel sources, in case I'd like to build KVM support and maybe some updated wifi drivers?
[BLISS ROMS Development] electrikjesus:
The links to my kernel sources are in the OP, but here ya go anyways: https://github.com/BlissRoms-x86/kernel_common
[BLISS ROMS Development] FiendFyre:
I don't mean to be a bother but have the SP4 ipts patches been added to this build?
[BLISS ROMS Development] electrikjesus:
No. I opted to try a different route, and add them in firmware: https://github.com/BlissRoms-x86/de...mmit/6d97f04eee27bbfa2e9c3046887b04d68fc76ba8 as well as enabling them in the defconfig https://github.com/BlissRoms-x86/kernel_common/commit/71613e8308deaa339a89187a0271e48ba468a842
[BLISS ROMS Development] fastguy:
Thanks for your response on the kernel source. I'll look at it. Any chance you could enable kvm on a bleeding edge build? I can give necessary defconfig lines.

I tested latest build on my SP3. Kernel 4.11 is OK but Wifi is still not stable. (Marvell mwifiex)

There are some very recent patches (few days old) in wireless-driver-next.git and I will try to check if I could compile these on your kernel source, appreciate if you could have a look as well as I'm not very experienced in merging different trees.
[BLISS ROMS Development] electrikjesus:
PM me or find me on Hangouts/Tele and we can chat details from there
[BLISS ROMS Development] FiendFyre:
Huh ok, how would I go about setting up a build with that enabled?
[BLISS ROMS Development] electrikjesus:
That's the thing, this way allows me to use it in every kernel, so what was added is already included in all the releases. I'm missing a piece or pieces of the puzzle though (I'm still a noob), and it's not detecting the IPTS hardware on boot. But I have most of the puzzle put together for it ;)
[BLISS ROMS Development] FiendFyre:
Nice! Glad to hear progress is being made, thank you for hard work!
[BLISS ROMS Development] daleski75:
I get these errors when trying the installer

http://pastebin.com/QTeQJT8H
[BLISS ROMS Development] ElfinJNoty:
Have you used the installer before? You can open the installer and run the option "remove Android" or "cleanup Android"... I forget what it looks like and am not in front of my laptop. Do that first and it will remove the existing androidos EFI entry. Then install as normal.

Or if you have already run the installer, there is a method to extract the Bliss.xyz.iso and then extract syaytem.img from system.sfs. then delete .Sfs. and copy over the .Img's to your c:/AndroidOS/ directory, replacing what is already there. Only copy over the 4.img's which are already in the C:/AndroidOS directory. Overwrite them. You can leave your existing data.img in place. This is essentially the same as doing a dirty flash on a recovery install. In many testing sessions, this is the quickest way to do an update when a new bliss-x86 build is released.

All of this is referring to if you have already used the WinTool installer previously. But from the looks of your log and my previous experience, this appears to be why you are getting that error. Let us know if that is the case
[BLISS ROMS Development] daleski75:
Got it fixed something went a bit screwy with my bios so reset everything put it back into legacy/uefi mode and this time it worked.
[BLISS ROMS Development] ElfinJNoty:
Good, then we shall assume you have a good working multiboot with Bliss running a dream :good:

Let us know(hopefully with some logs) if you face any issues :)
[BLISS ROMS Development] daleski75:
Got it all setup and working great now, dual booting with windows 10 and runs great on my laptop.
[BLISS ROMS Development] SquaDrive:
I have an issue in Android x86. My speaker somehow is broken. It produce hissing and cracking sound. It's fine on headphones tho (It still cracking when not playing anything). Is this a kernel issue? Because my speaker and headphones working fine on Win 10. Btw everything is smooth except audio and buttons (like volume and power button).

I'm using Asus Transformer 3 Pro T303UA, i7 6500U device.

fyi my soundcard ven_10ec&dev_0295. Help me..><
[BLISS ROMS Development] ElfinJNoty:
Does the noise from speakers continue if you turn the volume down all the way(silent)?
[BLISS ROMS Development] SquaDrive:
Sorry for the late reply. Yeap still hearing it.. btw the speaker sound like this *attached videos*

https://drive.google.com/file/d/0B30A7CZWK8MZWGVrZ1U5ODBjZlk/view?usp=drivesdk
[BLISS ROMS Development] ElfinJNoty:
I think I can hear the hissing sound..... do you happen to have the Viper4Arise sound mod installed as described at the bottom of the second post in this thread?

If not, please make a backup of your system.img first, can simply copy and past to a safe location. and then attempt to do the steps as described to install the Viper4Arise mod, open V4A and install the Driver, and then after reboot, play some audio and see if the hissing sound persists.

For now, that is only one suggestion. It could be a device specific issue, in which case we will need to take a closer look. please provide some information regarding your laptop/tablet/pc like Make, Model #, audio card, intel chipset, etc. etc....... anything you feel might be relevant to your device. Also, logs of beginning audio playback could help.

You should be able to obtain most of this information about your device from within Windows10, by clicking "Start" and typing "system info" and screen shot the system information. Help us help you and we will do our best.

[MENTION=928479]electrikjesus[/MENTION] is busy right now and we'd like to respectfully avoid interrupting him and his family as they deal with some personal matters throughout the weekend. Let us all wish him and his family well as they work through a difficult and stressful time.
[BLISS ROMS Development] SquaDrive:
Okay, i'll try to install V4A 1st.. i'll back again later to report it..
[BLISS ROMS Development] Ludespeed:
I installed this on a dell latitude 7350 tablet; haven't done much testing but I can confirm that the touch screen works; wifi works; battery indicator is accurate. Biggest and maybe only issue is there is no sound.
[BLISS ROMS Development] tobad:
can’t tell you. i never tried to build it with that patch... but as the autor said, it should work. read further maybe he used the original androidx86 sources.
[BLISS ROMS Development] muralirj:
Works on amd processor?
[BLISS ROMS Development] ElfinJNoty:
We've seen mixed results. Couldn't tell ya(especially with the lack of information being limited to AMD processor, I wonder how many different CPU's AMD has manufactured since their company was founded?)

Install and test. Please report your findings back here
[BLISS ROMS Development] wenna.speedy:
I am trying in the meantime, but with no success yet. :/ . if anyone do it, it will be helpfull for many people.
[BLISS ROMS Development] xhamadeex:
Has anyone tried the following commands to see if touch functionality is restored on the surface pro 4?

rmmod intel_ipts

and

modprobe intel_ipts

Please let us know

Cheers!
[BLISS ROMS Development] scarmau:
it could be a solution, but I couldn't execute those commands on terminal.
[BLISS ROMS Development] Ealge0110:
Well, what happens when you attempt to excite those commands on terminal?
[BLISS ROMS Development] xhamadeex:
Thanks for trying?

Do you mind asking you why you couldn't?

Cheers!
[BLISS ROMS Development] muralirj:
I tried andriod x86 original projects and that works perfectly without any issues.. And I am looking for only x86 builds because x86 64bit builds are always stuck on the boot screen with "Android #.."
[BLISS ROMS Development] ElfinJNoty:
well since we don't actively compile or support 32 bit builds, and your device, as you say, won't boot 64bit builds. Then I think that should be pretty clear.... use Android-x86 and their 32bit builds on your device.

We have some 32 bit builds available in our archived builds folder. However, these builds are old, do not include any of the recent additions, and these builds are unsupported by our team.

you can distinguish between 32 bit builds(_x86) and 64 bit builds(default, _x86_64) in the file names.
[BLISS ROMS Development] muralirj:
K thanks.bud nd can u point out the file name of 32bit builds its Confusing to find out
[BLISS ROMS Development] ElfinJNoty:
x86_64 = 64bit

x86 = 32bit

Any and all 32bit builds will be at the Android File Host link
[BLISS ROMS Development] XRed_CubeX:
Stuck on x86_64

Hello everyone, today I tried to install bliss os and when the boot remains on the x86-64 writing: and I can not do anything.

And long ago I tried to install Android x86 and gave me the same problem some time ago.

How can I solve this problem?

Pc:Compaq presario cq57-441SL

CPU:Amd E-series E-300 notebook

GPU:AMD Radeon HD 6310

Installation method:Iso image on USB with rufus
[BLISS ROMS Development] GADGETNiK:
Hello! Will bliss work and what build? on amd athlon 64x2 4200+
[BLISS ROMS Development] Fernix_:
Hi, i was gonna install this rom on my laptop but the downloads site is completely empty. Did anything happen to this project?
[BLISS ROMS Development] XRed_CubeX:
Pls why i cant use bliss os?
[BLISS ROMS Development] MartiniGM:
Surface 2017 support

The 20180312 Surface BlissOS has touch support on my Surface 2017. But the system.img is not extractable using Bliss/Android-tool, instead it unpacks the single files. And it won't repack an .img file. So I can't get supersu to work.

When I use Bliss/Android-tool on the newer 20180803 BlissOS it extracts the system.img, but in that release touch support has been lost.

Any tips to get both supersu and touch support for Surface 2017?
[BLISS ROMS Development] xhamadeex:
Unfortunately touch does not fully work on the surface pro as it stops working after a while and you have to restart to get touch to work again. :(
[BLISS ROMS Development] ElfinJNoty:
Reposting for those who don't read more than a page or two before posting

---------- Post added at 02:17 AM ---------- Previous post was at 02:13 AM ----------

And the link for all builds, archived....

https://sourceforge.net/projects/blissos-x86/files/Official/
[BLISS ROMS Development] XRed_CubeX:
Eh però a me servirebbe un po di aiuto
[BLISS ROMS Development] ElfinJNoty:
Ti suggerirei di utilizzare google translate per aiutarti a leggere "OP" e utilizzare la funzione "filo di ricerca" nella parte superiore della pagina. Non ci hai fornito alcuna informazione per aiutarci ad aiutarti.

And next time, English only :good:
[BLISS ROMS Development] XRed_CubeX:
This is my post.
[BLISS ROMS Development] doomanix:
I was hoping to try my hand at developing this rom for the Lenovo Tablet 2 Pro (non lte) 1380f. Lenovo released the source code for the rom based off of Lollipop ages ago but it seems everyone has erased any development progress made for this Tablet over at the Lenovo Thinkpad General forums. Could anyone point me in the right direction? I'll need to find the files used to unlock the bootloader that were deleted but I wanted to know if with the source code it would even be possible.

Source code link : https://pcsupport.lenovo.com/ca/en/products/tablets/yoga-series/yoga-tablet-2-pro-1380/downloads
[BLISS ROMS Development] MartiniGM:
What build are you using?
[BLISS ROMS Development] xhamadeex:
I used the surface pro 4 build and the latest build. Non worked.
[BLISS ROMS Development] MartiniGM:
Have you tried this one? Touch works pretty good on my Surface 2017 https://sourceforge.net/projects/bl...-sb-ga-jwd_m17.3.6_surface-pro-4.iso/download
[BLISS ROMS Development] Noob4Eterenity:
Failed installation.

Hello, my name is Wasi. When I open the installer, winrar opens and this message appears:

Extracting files to temporary folder

Extracting from Androidx86-Installv26.0003.exe

Cannot create MaterialDesignColors.dll

Cannot create MaterialDesignThemes.Wpf.dll

Cannot create Android_UEFIInstaller.exe

And when i try to install on my partition F: , which I made and formatted seperately for bliss os itself, install failed appears and tells to check log as a file which i cant find at the place it showed(C:\), but that isn't a big deal as there was one at the top right. Here is what the log says:

================Installer Info================

Installer Directory:C:\Users\Kamrul\AppData\Local\Temp\RarSFX1

Installer Version:2.6.0.0

Secure Boot ... Disabled

Manufacturer: LENOVO

Model: 80E5

Product: Lenovo G50-80

BIOS info:

LENOVO - 1

B0CN40WW

INSYDE Corp. - 54200029

Available GPU(s):

GPU: Intel(R) HD Graphics 5500

=============[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 9/15/2018 10:20:40 PM====

-ISO File: C:\Users\Kamrul\Desktop\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso

-TargetDrive: F

-UserData: 71387054

-Setup Directories...

-Folder Created: F:\AndroidOS

-Extracting ISO

#Launch:C:\Users\Kamrul\AppData\Local\Temp\RarSFX1\7z.exe x "C:\Users\Kamrul\Desktop\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oF:\AndroidOS

Error Executing C:\Users\Kamrul\AppData\Local\Temp\RarSFX1\7z.exe with Args: x "C:\Users\Kamrul\Desktop\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oF:\AndroidOS

Error output:

7-Zip 9.28 alpha Copyright (c) 1999-2012 Igor Pavlov 2012-06-20

Processing archive: C:\Users\Kamrul\Desktop\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso

Error: Can not open file as archive

==============Revert Installation==============

-Cleaning up Bliss Directory ... F:\AndroidOS

===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

==========================================

And yeah, I had installed remix os , phoenix os and also bliss os several times before:p. Your help would be most appreciated;);):):)
[BLISS ROMS Development] ElfinJNoty:
:)

---------- Post added at 09:16 PM ---------- Previous post was at 08:59 PM ----------

Please try the suggested .iso and report back so that we can take notes of compatibility. Thanks go to [MENTION=239006]MartiniGM[/MENTION] for helping a fellow user out:good:

Sometimes different kernel versions play differently on the same device. Upstream Android-x86 code or our edits and modifications. The Linux kernel itself adding/dropping support for different hardware that ends up causing various issues across the thousands of devices BlissOS is capable of running on.

We suggest to run our latest nightly releases first, and from a USB live boot <~~~That is the best method to quickly determine if your device will be compatible with the latest and greatest version of #Bliss. If that is not successful, try a bleeding-edge build. If still you are unsuccessful, we recommend trying older version of Bliss. All build .Iso files are designated by their VersionNumber/BuildDate/KernelVersion and other naming which is described in the OP and it's following posts.

We need user experience and feedback in order to investigate potential fixes or patches for particular hw & chipsets. We prefer to hear that things worked beautifully throughout your installation and you are currently living in #Bliss.:cool: However, when that is not achieved... we hope that you will provide any and all information about your installation and usage. Details of your device: make, model, cpu, gpu, etc.(you CANNOT go into too much detail!):cowboy:
[BLISS ROMS Development] xhamadeex:
I tried it and touch stops working after a while.

Maybe because I have the non 2017 model.

Thanks for the suggestion.

---------- Post added at 02:21 AM ---------- Previous post was at 02:09 AM ----------

Thanks for supporting surface devices.

I installed it in an external hard drive and unfortunately touch stops working after a while.

Device: Surface pro 4 (not the 2017 model).

Processor: Intel(R) Core(TM) i5-6300 CPU @ 2.40GHz 2.50GHz. x64 bit processor.

RAM: 8GB

Graphics: Intel(R) HD Graphics 520.

Please let me know if you need anything else, I will do what ever I can to support this ROM.

Cheers!
[BLISS ROMS Development] ak1998:
hello guys i am new here. first of all i am very thankful to the developer for this awesome work. i installed this rom on my laptop yesterday and everything working fine except ethernet. So can someone help me fix the problem.
[BLISS ROMS Development] ElfinJNoty:
Please read a few posts before yours, where we point out how to properly make a post when reporting "no work" in order to help us help you:good:
[BLISS ROMS Development] Zaturah:
Hey is there a rootless version of this, i tried to us the edu or a edu version i found but there was a problem for some reason it didn't recognized the memory so the disk assigned to this was less than 2gb or something like that
[BLISS ROMS Development] xhamadeex:
Will do.

Cheers!
[BLISS ROMS Development] ElfinJNoty:
The latest nightlies and bleeding g edge builds do not have R/W access out of the box, because the system.img is compressed by squashfs(which denerates the system.sfs file). .sfs files are read only. So try any of the builds from the past 4+ months and there will not be root access without taking additional steps.

EDU builds are old anyways. Don't even think we made any through Oreo Development? Which, btw, is now over. We are in the process of preparing BlissOS for it's Android 9 Pie flavor... Follow us on social medias to stay current with the latest and greatest news and announcements from Team Bliss ?

#StayBlissful
[BLISS ROMS Development] xhamadeex:
I am trying to install the surface pro 4 IPTS files into the latest bleeding edge build, to do that we need the BlissOS-Android PC toolbox, however it is deleted.

https://xdaforums.com/bliss-roms/bl...ease-blissos-android-pc-toolbox-v1-0-t3806721

What can I do? And can someone point me to the IPTS files of the surface pro 4 non 2017 model?

Thanks!
[BLISS ROMS Development] ElfinJNoty:
Team Bliss did not create/provide the toolbox. We have no control over it. Was the choice of it's creator and he has not replied to our questions regarding his decision.

I don't own a Surface device and have not myself done any of the manual driver/FW insertion. You can read through the last 10-20 pages of discussion or use the threads "Search" function that XDA kindly provides for users to locate things in the current thread you are viewing. If you need a pointer for how to use a search engine, I'd suggest "surface+ipts+manual" and see what that pulls up for ya ?

Or perhaps another user can help you out?
[BLISS ROMS Development] ak1998:
oh sorry . Here I took some logs using catlog app after connecting my lan cable.

edit:- got the problem it is wrong ip address,gateway,subnetmask and dns anyway to manually configure them like in remix os
[BLISS ROMS Development] ElfinJNoty:
Not at this time, will talk it over amongst the team if it might be possible to allow those setting to be manually configured from within the OS. Might be able to add in some custom settings strings. Not sure though, so no promises and no eta's as usual
[BLISS ROMS Development] attachsnow:
hello can you send me the file?

a0910115172@gmail.com

big thanks to you.
[BLISS ROMS Development] Grrrmachine:
problem with USB touchscreen

I'm trying to install BlissOS on an HTPC (gigabyte brix), and it all works fine except for the USB touchscreen (device 0eef:0001). It looks like it's being detected as a mouse, so its stuck in portrait mode even when the screen its attached to is landscape. This means down is left, right is down etc etc (both axis are inverted).

Is there any way to get the EETI eGalax drivers into a nightly build for me? Or is there some other way I can modify the build to correctly detect the touchscreen as a multitouch device?
[BLISS ROMS Development] ElfinJNoty:
Send you "the file?" :confused:

---------- Post added at 07:23 PM ---------- Previous post was at 07:21 PM ----------

Provide us a link to the drivers and we can take a look at potentially including in future builds
[BLISS ROMS Development] Grrrmachine:
Thanks. The manufacturer's site is here: www.eeti.com.tw/drivers_android.html
[BLISS ROMS Development] scarmau:
do you want the files in the C:\Windows\INF\PreciseTouch\Intel?
[BLISS ROMS Development] scarmau:
Hi, i have Surface Pro 4 i5 8gb 256gb.

do you want the files in the C:\Windows\INF\PreciseTouch\Intel?
[BLISS ROMS Development] gsmsource:
Hi, which rom is suitable for the 2018 surface pro lte edition? I know lte probably wont work but which file should i use to install?

Thanks
[BLISS ROMS Development] razorrzr1:
I can only see empty Folder in BlissOs,incl. Nightlies etc.

Pls Help
[BLISS ROMS Development] quarku:
Same here, all empty.
[BLISS ROMS Development] xhamadeex:
rmmod intel_ipts

modprobe intel_ipts

Great news!

I just used those commands after touch functionality stopped working and it restored it. No need to reboot. Now, can we use these commands to solve the surface pro 4 (non 2017) touch functionality? Maybe through tasker?

Cheers!
[BLISS ROMS Development] xhamadeex:
Can we make a script that will execute the following commands when the volume button is long pressed?

su

rmmod intel_ipts

modprobe intel_ipts

This way touch functionality will be restored everytime we long press the volume button.

---------- Post added at 09:46 PM ---------- Previous post was at 08:55 PM ----------

a developer asked for a logcat to see what is causing the touch functionality problems on the SP4 2015. I attached the logcat file.

https://drive.google.com/file/d/1sRvbhNq9eoJ4S-AQy0FpY1tkHynqphXj/view?usp=sharing

Please let me know if you need anything else.

Cheers!
[BLISS ROMS Development] ElfinJNoty:
It is a shame that people do not read before posting.

This has been covered. Posted numerous times here in the thread, cross posted to our official social media channels.

You make things worse by confirming that people are not reading.

Guys, normally I'd just link ya directly and call it a day.

But I will not give a handout here and become more frustrated when you return with further questions that can be answered by reading the OP and following pages.

Rather a hand up....

The downloads can still be found in the OP.

Please read the last 10 or so pages to familiarize yourself with the current status of the project and to figure out why you two are failing together