yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] Infinity123:
The latest build also doesn't have audio on Dell Latitude 13 (7350)

Wifi, B̶T̶, touch, camera is working. Basically everything works and is very smooth. I can pull some specific logs to help, just tell me.

edit: BT finds devices but can't connect. I tried to connect to my bluetooth speaker but it won't connect and says "bluetooth share has stopped".

edit2 Booted it up again and the audio started working somehow. When I went back to windows 10 the audio driver didn't start so I had to disable the realtek driver and re enable it again.
[BLISS ROMS Development] jrc2:
Is anyone else having issues with this freezing up?
[BLISS ROMS Development] jrc2:
Also, Amazon Kindle crashes.
[BLISS ROMS Development] electrikjesus:
That's fine. All the grub entries are the same. You will need to wipe the data.IMG somehow going back a version like that. The kernel might not take it too well. Use RMXtools v1.7 to format just the data.IMG. or a similar tool
[BLISS ROMS Development] Ranomez:
Not really needed, just had to clear data for a few apps (google play services and store and gmail) and everything else seems to work.

While Bluetooth works it seems it still can't see the 5Ghz Wi-Fi band, is that still broken on 7.0 cause I remember it was fixed on 6.0?

And sleep mode was never fixed for the Surface Pro 2 as it seems, right?
[BLISS ROMS Development] electrikjesus:
That is the same kernel Android-x86 project is using in their releases, so I would assume so. I will make a point to check for any patches on my end too.
[BLISS ROMS Development] Ranomez:
Ok, for now I will try to create a script to automatically install Viper4ARISE from the extracted zip for all those that want to use it cause IMO extracting a zip and a script into a folder then running the script in terminal with root is easier and faster.

On that note I remember at some point someone was trying to create some sort of custom recovery mode that could flash normal flashable zip files for Android-x86, guess that never got finished since I can't even find information about it on the internet anymore.
[BLISS ROMS Development] musicman5844:
Hope you get it cause you'll find that the zip is copyright. Already tried
[BLISS ROMS Development] Ranomez:
What does that have to do with anything?

I will just create a script that you put in the same folder you extract the zip to and then run it from terminal to copy the files to their right locations.

That's also the best way to make the script not bound to the current version of it, when it gets updated it should hopefully just be possible to extract the new zip to a folder, copy my script over and just run it (that is unless they add new files or rename some files).
[BLISS ROMS Development] electrikjesus:
UPDATE - 02.01.17

New unstable build is uploaded ( bliss-x86_64_n7.1.1r13_02.01.17_k4.10rc6-dev_02.iso ), using an early version of kernel 4.10rc6, with added patches and a few wifi fixes in there too. My Surface still suffers from the same wireless issues as rc5, but the hope is that others will work better. After all, this isn't just for me ;) Check GitHub for the changes to kernel. Branch is k4.10rc6-dev. This also has a couple test commits in it, one is screenrecord shortcut keys, which unfortunately makes x86 reboot right now, so steer clear of testing that. OpenGapps is still acting funky with Gmail on one test machine, but fine on another, so be aware of that too. Other than that though, all seems stable and error free.

ENJOY!!

Edit: there might be a sound issue on some machines. Forgot to merge that branch of fixes in. Sorry peeps
[BLISS ROMS Development] apophis9283:
Good job man, Love seeing your work :)
[BLISS ROMS Development] grayhaze:
Am I missing something or do these builds still not enable touch screen functionality on the Surface Pro 4? I saw that you mentioned that touch support should be working for all MS products up to the Surface Book. I've tried both the stable and unstable 7.1.1 builds and neither work. Keyboard and trackpad work fine though. Apologies if this has already been covered somewhere in the thread, but I couldn't find any mention of it when searching for "surface pro 4", "touch" or "touchscreen".
[BLISS ROMS Development] electrikjesus:
I may have missed something for the SurfaceBook. I only have a SP3 to test the builds with, and had to change a few things on top of what Android-x86 project had already to get the patches to take
[BLISS ROMS Development] grayhaze:
I believe there are some extra steps involved in getting the IPTS drivers working correctly with the Linux kernel, which are required for touch screen and pen functionality on the SP4 (see https://github.com/ipts-linux-org/ipts-linux-new). There are instructions floating around for getting this working on a basic Linux install, but nothing conclusive for Android-x86. If you were able to work this out and get it integrated into Bliss that would be amazing.

Otherwise from my short time playing with the ROM, I can see you've done some really cool work here. Keep it up! :)
[BLISS ROMS Development] rajnallan:
In both Stable as well as Unstable versions I get Google Play Services error while using Google Play Music, Movies etc. I am on surface pro 3. The latest unstable version does not complete set up. At the last step it force closes
[BLISS ROMS Development] electrikjesus:
I wish I could avoid these issues, but this happens the OpenGapps push something for their x86 branch that doesn't agree with Bliss somehow. And because we pull directly from OpenGapps at build time, it's hard to avoid new bugs. Try a reboot, or clearing play data. I have no issues on my end 90% of the time.

At the last step? If this is the restore apps step, the solution is to start a new device, and then after it has a chance to sync the new device data to your Google account, you should be able to restore apps fine.
[BLISS ROMS Development] electrikjesus:
I will check it out. (EDIT: I did check it out. He's got just a handful of commits for the patches on top of kernel-4.9. I will try to pull them in and make a test build this weekend with them and test to make sure it doesn't mess anything up for other devices.) The current sources for my Surface patches were mainly geared towards the SP3, So it's likely that they did miss things for newer models, but upon reviewing the code for the patches, it had all the touchscreen and multitouch additions for all surface devices. The IPTS driver info is new to me, so I will have a look into it.

I did merge in all the sound fixes today, so I now have sound again on my machine :) Here's the list of device fixes I was able to merge into the kernel: https://github.com/BlissRoms-x86/kernel_common/commits/k4.10rc6-dev

I will likely be uploading this build tomorrow if I don't find any glaring issues with it.

Thanks again peeps for digging what we have going two far!!
[BLISS ROMS Development] Ranomez:
[MENTION=928479]electrikjesus[/MENTION] after digging around on the internet for things related to the Surface Pro 2 and Android x86 I found out that sleep mode was last working in 4.4 and seems like CPU scaling never worked on any Surface device on Android x86 (so always staying at maximum frequency eating the battery pretty fast and also keeping the fan on) although it does seem like on some other devices (perhaps with a different CPU) it does scale properly.
[BLISS ROMS Development] rajnallan:
Thanks. You were right ..I set it up as a New Device and after sometime the Google play music is now working. No errors. However, When I try t play a movie from my library on Play Movies, I get a meesage that this Device Isn't supported for playback. Any solutions. I am on the stable build on one partition and on the Unstable on another which forse closes often.
[BLISS ROMS Development] electrikjesus:
I can't think of anything further we can do to help Play recognize the device. Maybe google how to change device I'd to a chrome pixel
[BLISS ROMS Development] rajnallan:
i changed the system files to RW but still it does allow me to edit build.prop. if i have to change the device i have to edit build.prop. Any help please? Thanks.
[BLISS ROMS Development] electrikjesus:
If you used the UEFI installer, then you likely missed a simple step. (a lot of users have,so don't feel too special)

Hope that helps
[BLISS ROMS Development] azwina:
if you don mind , can you explain with detail how to do this ??

thanks
[BLISS ROMS Development] logant:
mobile legend in game controller not working

hi, thx for the great x86 os. everything works great.

But when i tried to play mobile legend & last day on earth, i couldnt move around, i can klik the skill using the mouse but not the movement. is theres some setting that i missed?

When i tried remix n other os before i install bliss, i can move in games by using keyboard (WSAD).

Thx, oh, i use the v7.2_x86_64 Official.
[BLISS ROMS Development] THEHOLYG0D:
First you install it normally, like you would without the touch screen and complete the installation by keyboard and mouse, then goto the link from the above quote and select proper device, download it and copy it somewhere so that you can copy it in the Android.

Once you have restarted or downloaded directly to the Android which you installed, keep it in the donwload folder.

Now when you boot you press alt+f1 or alt+f3, that brings you to the main console, then issue the above commands and you'd be done.

Make sure you issue the commands properly, because Linux is case sensitive..

If you are still stuck, PM, I'll get back to you

Let's keep the thread clean ;)
[BLISS ROMS Development] marcel201:
I want to install this on my old laptop and hook him up to my smart tv with hdmi, will it be able to display it on my tv`s resolution?not a poor cloned display at my laptop`s resolution.
[BLISS ROMS Development] electrikjesus:
It's been covered before in this thread, but yes. Using this app, you can get a better native resolution for HDMI and wireless displays: https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free&hl=en
[BLISS ROMS Development] Zemnexx:
Any build of Bliss-x86 that is 32 bit? My laptop seems to only want to boot Androidx86 whenever it is 32bit, the 64bit builds never boot properly despite my processor being 64 bit compatible, and hangs at the console during boot, but 32bit works without issues. This happens no matter what I use, Bliss/Remix/Phoenix.
[BLISS ROMS Development] blubba83:
Same hier ,it is sse4, some old 64bit pcs dont have this. A few months ago i tried to build without sse4 but my knolage is to small .
[BLISS ROMS Development] marcel201:
I'm running this right now through a live USB and I see it has installed in settings SuperSU but doesn't have root, it's somewhere in the settings to activate it?
[BLISS ROMS Development] electrikjesus:
You guys are funny sometimes :) When you use the Live USB mode, it doesn't save any data, and system is not R/W. so you will not be able to save your changes or use root. This is all in the second post on the thread.
[BLISS ROMS Development] electrikjesus:
I do have a 32bit build I made last week, but Play services, along with a whole host of other gapps keep closing on my tests, so... I didn't release it, because it does not work right with gapps anymore. Until I have time to track down the issue, it will have to wait.
[BLISS ROMS Development] DiamondJohn:
On a bit of a stretch, but that sounds like a very similar issue to what I am having with a build of crDroid 7.1.2 for an unofficial device. Are you getting "class not found" in your logcats? I found that manually building the ODEX file appears to fix it; at least for some time. But anything that was ODEX'd during the build, is rock solid. If it is similar, then I will be interested to hear what/how you solved it.
[BLISS ROMS Development] Ashwin Prabhunerurkar:
thank you

works perfectly for surface pro 4

can you find a more recent build

also in other flavors of android

this is a 7.1.2 aosp build from june

[MENTION=928479]electrikjesus[/MENTION]

can you please check if you can add this ipts driver to your ipts source
[BLISS ROMS Development] electrikjesus:
Again, there is no attribution for any of the commits, so no. Normally, I have no issues with pull requests, github sources, .patch files where I can add attribution myself, etc. After two years, you'd think people would start sending pull requests or something for the work they want done.

Not really feeling the level of appreciation I prefer for an open-source project this size...

Just saying
[BLISS ROMS Development] ElfinJNoty:
After reading through the last few pages of comments, I am noticing that folks are neglecting to include what device/CPU/installation method/bliss-build-version they are attempting to install....

Help us help you by providing as much info about your target device as possible. Bliss is capable of running on thousands of HW configurations, but we'd like to know which one YOU are using when having issues.
[BLISS ROMS Development] janneriiki:
Does anyone have suggestions on how to install xposed framework v.88.1 on latest bleeding edge update of Bliss OS x86_64 (17.10.2017) ?

Regards
[BLISS ROMS Development] fredg1664:
please help

Hi, i tried to install "android-x86_7.1.2@K4.9.img" on my sp4 and the boot stay on the android logo, from usb it starts right but not from a partition on internal HDD, can you quickly explain how to install it please,
[BLISS ROMS Development] azwina:
i using easy method to install but fail to start :-

error message is look like "missing a file , file:\Android\boot\grldr.mbr"

how to do ?

i try 2 time install also fail using easy method, but when i boot in selection boot got 2 android logo how to delete this android logo ??
[BLISS ROMS Development] electrikjesus:
New Bleeding-Edge Bliss-x86 build is available!! - 10/27/2017

A new Bliss-x86 bleeding edge build is ready, including the IPTS drivers and firmware for Surface machines, and added drivers and firmware for many chromebook touchscreens and touchpads. I will also be running off an .RPM installer of Bliss-x86 soon also. So keep your eyes peeled for that too.

Updates / Additions:

Added IPTS drivers and firmware for SP4 users(But they are not detected correctly on boot) Refer to this post for more on that: https://xdaforums.com/showpost.php?p=74171272&postcount=937

Added drivers and firmware for many Chromebooks (Thanks to GalliumOS project)

Kernel 4.12

Much more (check out github)

Bugs / Issues:

Bluetooth issues still exist on many devices

GPS issues on many devices also

lockscreen might not respond to some trackpad/mouse input (I suggest you disable lockscreen, or if you need it, make it not Swipe.)

There's more I'm sure. The noobs will point it out at least a dozen times ;)

As always, check the Bliss download site for the newest builds. The rest are all on AFH as a backup archive. Hope you all enjoy this one :D

https://downloads.blissroms.com/Bliss/Official/x86/bleeding_edge/
[BLISS ROMS Development] Mohamed Sallah:
can you please make detailed instruction for Noobs this part

" Added IPTS drivers and firmware (But they are not detected correctly on boot) Refer to this post for more on that: https://xdaforums.com/sho...&postcount=937"
[BLISS ROMS Development] z750leovince:
for me...I would like android x86 for y surface book...and would like detailled for this method how entered lign command
[BLISS ROMS Development] Spinoni31:
Hello, I'm having a problem building the system from my ubuntu 17.04 VM.

whenever I try to use the lunch command with the command given in the makefile page of the project i get the following error:

lunch bliss_android_x86-userdebug
ls: Unable To Access 'device / * / android_x86 / bliss.mk': File or Directory Not Existing
build / core / product_config.mk: 244: *** Can not locate config makefile for product "bliss_android_x86". Stop.
ls: Unable To Access 'device / * / android_x86 / bliss.mk': File or Directory Not Existing
build / core / product_config.mk: 244: *** Can not locate config makefile for product "bliss_android_x86". Stop.
Traceback (last call last):
"Build / tools / roomservice.py" file, line 302, in <module>
os.mkdir (local_manifest_dir)
OSError: [Errno 13] Permission denied: '.repo / local_manifests'
ls: Unable To Access 'device / * / android_x86 / bliss.mk': File or Directory Not Existing
build / core / product_config.mk: 244: *** Can not locate config makefile for product "bliss_android_x86". Stop.

** Do not have a product spec for: 'bliss_android_x86'
** Do you have the right repo manifest?

the specs of the VM are as follows:

2 Hard drives (one for storing system and build environment with 170GB of size and the other with 20GB for storing the builds)

CPU: Intel core 4200u @ 1.6GHz

RAM: 4GB DDR3L @ 1600 MHz

OS: Ubuntu 17.04 with KDE Plasma and LXDE

can someone point me in the right direction for solving this problem? I am a complete newbie in terms of building from source the android os.

thanks in advance, Spinoni31

P.S.: If I have posted in the wrong thread feel free to move it in the right place

P.S. 2: sorry if the error message isn't written correctly in English, as i needed to translate this from Italian since English isn't my main language.
[BLISS ROMS Development] electrikjesus:
You will need to provide a bit more information as to what you did to setup your build environment, what you typed prior to the lunch command, what branch you are trying to init, etc.
[BLISS ROMS Development] danerrickcuba@gmail.com:
hello i need help...i tried searching this thread for keywords "partitions" "mount" "ntfs/fat32/exfat" to find out if previuosly discussed on possibility of mounting partitions on android, i have a partition with data as with many users do, but i cant ACCESS it...any tips? ideas?
[BLISS ROMS Development] electrikjesus:
Look here: https://github.com/BlissRoms-x86/bootable_newinstaller/blob/nougat-x86/initrd/scripts/2-mount#L12
[BLISS ROMS Development] darkgoat:
I was trying to run this release on my SP4. Here is what I did:

1.) Got the system.sfs from the iso

2.) Extracted system.img from system.sfs

3.) Unpacked system.img

4.) Executed the commands according to https://xdaforums.com/showpost.php?p=74171272&postcount=937

5.) Repacked system.img with make_ext4fs

6.) Converted it to system.sfs with mksquashfs

7.) Copied system.sfs back to usb-stick/iso

Android boots from the USB but touch is not working on the SP4.

Did i do something wrong?

Thanks ;):good:
[BLISS ROMS Development] 4r44444:
Chuwi Hi12 newest Bleeding Edge Build:

- No Touch ( Display = Last Surface 3 Display --> Samsung PLS SEC3542 -->Touch Screen: Multitouch 10 points ) (12,0 Zoll, 2160 x 1440 Pixel, IPS-Panel)

- No Sound ( Audiocard = ES8316AudCodec Device , Intel SST Audio Device (WDM) )

CPU = Intel Atom x5-z8300
[BLISS ROMS Development] THEHOLYG0D:
First thing Android 7.0+ plus needs at least 8gb otherwise later you'll get all sorts of error while compilation.

Second from the very small snippet it seems you have not even init the repo and directly trying to build without a repo sync.

Tips : try increasing the 170gb to minimum of 250gb because when the compilation starts lots of, i mean lots of space is used if you aren't using ccache compress

If you can possibly try dual booting to give all available resources to build..

I'm also a newbie and just gotten into this business all of the above is best to my knowledge as I experienced.

Good luck with your builds.,

---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------

You know, scroll a few posts back and find my post where I've mentioned a workaround to get touch working especially on Chuwi devices, by replacing the silead_ts.fw file, sound wait for it, someone might find hax eventually ;)
[BLISS ROMS Development] Spinoni31:
Thanks for replying. because i'm working on a laptop and because 8 Gb of RAM is the maximum that my motherboard can accept, Ihave decided to try to do a build envirnment on my main hard drive, in a 320GB Partition that I'll use to build the bliss-x86 rom from there. Also, is it possible to just copy the folder of the repo in this hard drive (by still doing the repo init command and the repo syncing the folder that has been copied)? I'm asking this because my internet connection is really slow (About 520 Kb/s) and i don't want to download about 60 Gb of data if it's possible.

Thanks again for the reply, Spinoni31.
[BLISS ROMS Development] THEHOLYG0D:
You know regarding that copy thing I'll tell you a funny part..

I did recent HDD changes, I had 4 build environments. And let me tell you if you have successfully completed the repo sync command you'll have millions of file in Kb sizes, and they take time like hell to copy, but check to see if you still have those xxxxxxxxhugehexadecimalxxxxxx.pack things, if you have it, you can do it by repo init and you are saved, if you don't; you better turn the display to lowest and leave your laptop ON overnight :p

Bliss downloads 32.2 GB exactly That I can accurately say because I had kept my PC for a night duty xD
[BLISS ROMS Development] :
YOGA BOOK

HI

I installed Bliss x86 on my Yoga Book but i faced some Issues:

1) No Sound

2) No Bluetooth

3) 90 Grad Screen Rotation ( i fixed it by install third app Party ) but i would like to see it in Bliss Rom

4) No Halo Keyboard:(

All the Drivers are ready to download at this site

https://pcsupport.lenovo.com/uu/en/products/tablets/yoga-series/yoga-book/downloads

But i dont know how to install :mad:
[BLISS ROMS Development] electrikjesus:
The issues you are having are common issues for most devices. So I doubt it's driver based. I think we might need to figure out the driver issues... eventually.

The problem most of our community here isn't getting is this: I am only one person, and I am trying to work on a project much bigger than myself. I am trying to make the one kernel work for all devices possible, but doing this is increasingly difficult with the severe lack of development resources I have. I want to make sure that changes for one type of device don't interfere with other devices using shared components, and I cannot do this without testing these on my own.

You all are greatly appreciated for for your continued use and posting the occasional sources or commits. But the bigger picture needs to be seen here for everyone involved. I am in no place financially to be able to purchase any test devices for Bliss-x86, nor has Bliss or Bliss-x86 ever received any donations to help provide said devices, yet my development on said project is requiring many devices in order to make sure it is the exemplary solution for all devices involved. I hope you all get my point here.