yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] gilaxone:
Hello, what ROM version do you use on your Chuwi Hi 12?

I've try with the official version

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso

and the Bleeding-Edge versions

Bliss-v7.2-android_x86_64-OFFICIAL-20171024-1354_k4.12_cb_ipts.iso

Bliss-v7.2-android_x86_64-OFFICIAL-20171016-2034_k4.12-atsp.iso

with no luck about the touch screen :crying:
[BLISS ROMS Development] digital0:
Fedora 27 works when I copy mssl1680.fw to /lib/firmware/silead. But if I do the same with Bliss-v7.2-android_x86_64-OFFICIAL-20171103-1727_k4.12_oto-installer.img (unpack system.sfs, mount img, repack sfs), dmesg is still the same as above. Fedora dmesg:

[ 9.415332] silead_ts i2c-MSSL1680:00: Silead chip ID: 0x80360000

[ 11.013324] input: silead_ts as /devices/pci0000:00/808622C1:05/i2c-5/i2c-MSSL1680:00/input/input14

Is it because Fedora has a newer kernel (4.13.15)?

Similar problem with wifi. Fedora works if I have brcmfmac43430a0-sdio.bin and brcmfmac43430a0-sdio.txt in /lib/firmware/brcm. bin file is in the newest linux-firmware Fedora package, txt file I got from the Windows installation - Windows/System32/drivers/43430r0nvram.txt. Fedora dmesg (when I don't have the bin and txt files):

[ 9.775721] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.bin failed with error -2

Bliss dmesg when I do have the bin and txt files:

[ 12.593832] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2

It tries to load brcmfmac43430-sdio.bin instead of brcmfmac43430a0-sdio.bin, but if I copy brcmfmac43430a0-sdio.bin to brcmfmac43430-sdio.bin, it still gives the same error. I suspect it's because of a too old 4.12 kernel.
[BLISS ROMS Development] electrikjesus:
We might be moving to kernel 4.14.x to help with some of these issues. Early tests have booted and run fairly well on my Venue 8 Pro 3845
[BLISS ROMS Development] ilker4fun:
Will you add support for more devices in that kernel version? I really want to use your work on my Samsung galaxy book 10.6.
[BLISS ROMS Development] electrikjesus:
Ill eventually be merging in all the patches from GaliumOS's repo to help support those Chromebook devices
[BLISS ROMS Development] digital0:
Could I get an image with a newer kernel to test?
[BLISS ROMS Development] Guimenez:
Can you please try to add support for bailtrail with atom Z3735F?

Thank you
[BLISS ROMS Development] DrBeaker:
I tried this via taking the img file and writing to USB via RUFUS. I can get to boot from USB and get the menu (Live/Install/Debug/NoVesa/etc).. but I cannot find an option that will let me live-boot into Bliss OS, without the need to overwrite existing install.

Can we boot from USB in a live session? Any special requirements or settings?

---------- Post added at 02:39 PM ---------- Previous post was at 01:50 PM ----------

Attempted with the above mentioned file. can now get to boot to OS, but no touchscreen function at all. Had to navigate with USB keyboard.

anything else need to be loaded after initial boot?
[BLISS ROMS Development] 4r44444:
Sorry I don't know what you did wrong.

I just used this image and liveboot it, touchscreen worked... in build before it didn't work for me.

I have Chuwi HI12 Dualboot Version
[BLISS ROMS Development] WiseMMO:
I'm sorry if this was asked already, but I really do not know how to find what I'm looking for in 112 pages.

I'm coming onto an issue with an - acer one 10 n15p2 - on the live boot via USB I get full touchscreen functionality, but once installed the touchscreen doesn't work anymore, also I have issues with the screen, it's basically backwards, vertically or horizontally it's always upside down.

Can anyone tell me what I could do?

EDIT: And is there a way to remove the EFI Shell boot and just go into default boot everytime?
[BLISS ROMS Development] Inenting:
Hey,

Thank you for doing your best on this rom! I really would like to help getting this to work on my surface. What is the best thing I can do to help? Just provide logs and if yes what kind of logs? (sorry im new to this world)

I tried building android x86_64 based on android 8 myself but I couldn't even get the settings app to work so I gave up (for now).

This is my device:

Surface Pro 2017

Result of installing current images:

1. Device boots up

2. Type cover works

3. Wifi/bluetooth etc works

3. Touchscreen/power button/volume buttons don't work

4. Sleep doesn't work (it can't get out of sleep, have to reboot)

I found these kernels for the surface 4+ :

Kernel 4.9 with experimental IPTS

Kernel 4.11 that works for sp 4 and higher users

Thank you for your time.
[BLISS ROMS Development] electrikjesus:
For those of you using a BayTrail device and have never had any luck with it running at normal speeds, my Venue 8 Pro 3845 has had that issue or the longest time. What the issue has been was that Android was using the default clock source for it. And on some BayTrail devices, the clock source should be set to tsc. So, if you are having this same "slow-motion" issue on your device, try adding the following to your grub command after the word "quiet":

quiet rw clocksource=tsc hpet=off

Hope this helps a few of you ;)
[BLISS ROMS Development] ingermy:
with this the tochscreen works perfectly!!!! Surface Pro 2017 android x86 7.1.2 kernel 4.9

https://drive.google.com/drive/folders/0B3Ttv3AmOdafQUNhdjE5MWRGVkU

electrikjesus you can do something? thanks
[BLISS ROMS Development] Inenting:
Yes thank you! Touchscreen works! But sadly the buttons still don't work and those are important as well. And for some reason I can't install it on the nvme drive, I can only use the live mode.
[BLISS ROMS Development] ingermy:
Even on mine it does not install. I had to install it manually in resident mode.
[BLISS ROMS Development] electrikjesus:
Yes, I can close this thread since it's no longer needed any more. You all enjoy your Android-x86 builds.
[BLISS ROMS Development] ilker4fun:
[MENTION=928479]electrikjesus[/MENTION] , don't stop your work for this OS,please. I have some news about my galaxy book. I have been testing other android-x86 builds and I have found a one without touch inverting.

cm-x86_64-13.0-r1

https://www.fosshub.com/Android-x86.html/cm-x86_64-13.0-r1.iso

I hope you can implement this in this awesome OS. Thanks
[BLISS ROMS Development] electrikjesus:
Oh, that's nice. Now you guys have one more option to use instead of Bliss. Enjoy!
[BLISS ROMS Development] ilker4fun:
I didn't write cm-x86_64-13.0-r1 as a option because it has lots of bugs. It just didn't invert touchscreen. I would be awesome you make a final build for those who really want to use Bliss-x86 with these changes. I hope you change your mind about not continuing the develeopment. Even you don't, I must say, you guys did great things in this OS, thank you for all of this.Best of luck.
[BLISS ROMS Development] ingermy:
Sorry! I have always followed your project with interest. It would seem to me, if you have the time and desire, to insert ipts touch drivers into your kernel. Thanks for all the time you dedicate!
[BLISS ROMS Development] Inenting:
What is up with this OP? Does he have a stick up his ass? We are just trying to make the rom better by researching roms and giving hints to include in next build so that more people can enjoy this rom. You can go ahead and close this thread, we don't need an OP with multiple sticks up his ass.
[BLISS ROMS Development] electrikjesus:
I am sorry for my responses yesterday. This project has taken more time and resources than I am capable of providing. So much that my work and family life has started to suffer. Because of this, I have no choice but to lay off on development.

I wish you all knew what I was going through right now, it might help you empathize a little instead of saying I have a stick up my ass.
[BLISS ROMS Development] ufocus:
Please take care
[BLISS ROMS Development] Lovelyven:
Hello, can you please explain to me how do you install this
[BLISS ROMS Development] ilker4fun:
Don't listen other people, mate. I wish you best of luck. Again thank you for everything.
[BLISS ROMS Development] electrikjesus:
I have Bliss-x86 8.0 alpha about ready for you all, but need to find the time to put together all the changes and instructions. I might just make a video of it and do it that way... Provided I find the time.
[BLISS ROMS Development] ilker4fun:
It would be awesome. I look forward to it.
[BLISS ROMS Development] ingermy:
Guide attached. Good luck!!!
[BLISS ROMS Development] laomms:
the ipts firmware for surface

https://github.com/jakeday/linux-surface/tree/master/firmware
[BLISS ROMS Development] z750leovince:
how proceed for install this firmware?
[BLISS ROMS Development] dracinn:
Can anyone provide a mirror link to the UEFI installer?
[BLISS ROMS Development] electrikjesus:
Needs to be pulled into our source and compiled from device/generic/firmware
[BLISS ROMS Development] electrikjesus:
About the installers, I should be more transparent about those here with you all, there was an issue with something that kept happening every time I uploaded an .exe file to AFH, so I had no choice but to pull them. But when I got no response from AFH over WHY I pulled them, I felt it was best I posted about it here: https://plus.google.com/+JonWest/posts/fptG9QBFjLJ

Sorry again for the delay, but I was hoping they would have a resolution by now...
[BLISS ROMS Development] electrikjesus:
As for the Bliss-x86 oreo alphas, the only thing holding me back from letting them loose to you all is the lack of Houdini compatibility libs. If this is something you all feel you can live without while it is in Alpha stage still, Just let me know somehow. The larger the disturbance, the more it catches my attention.

So... Let me know
[BLISS ROMS Development] digital0:
Could you please update silead firmware as in https://github.com/BlissRoms-x86/de...mmit/58b1df66e7619445c3b6fb34865187cae7d077f0 ? I've added onda obook 20 plus support, and it was just merged to https://github.com/onitake/gsl-firmware

Edit: I posted a patch to kernel too - https://patchwork.kernel.org/patch/10104041/ . It would be nice if it was added to Bliss source, or I can create a pull request.
[BLISS ROMS Development] electrikjesus:
Yes, please feel free to submit a pull request. We would be happy to help test things with you.

EDIT: I pulled them in anyways. Should be included in the Alpha release soon ;)
[BLISS ROMS Development] hgblob:
updated mwifiex for SP3

Hi electrikjesus,

For many years the mwifiex WiFi drivers for Surface Pro 3 have been junk, crashing the kernel or failing to resume the firmware if the power saver has been enabled.

In recent kernels(4.14) these issues appear to be fixed however the kernel itself does not work on Surface Pro3(fails to resume from sleep). I have run the wireless backports scripts and added the 4.14 wifi drivers and stack to your 4.12 android x86 My commit is my in github repo: https://github.com/vamanea/kernel_common/commit/ffe8e63972d00d68fc5f25cafa269acd5bafd8a9 I don't know if it helps or breaks wifi for other devices but wifi is finally working on my SP3 and wanted to share.

PS: the defconfig needs changes to enable other wlan device support, all the kernel configs are named BACKPORT...
[BLISS ROMS Development] electrikjesus:
!!New Bliss-x86 v8.0 Alpha Release!! - 12/12/2017

We're doing it!! I't getting pushed out the door. Bliss-x86 v8.0 Alpha is mostly ready, so in my eyes, it's good enough to release to you all as an alpha release. Some things have changed in the boot process, so the Windows Installers will not work as expected. On the old boot process, you used

DATA=AndroidOS/

but in this one, you will need to keep it shortened to

DATA=

Also, grub2 is not getting written correctly still on a couple different test devices, so I will likely be working on updating the oto-installer to work for Oreo soon.

With this though, I don't want to see anyone in here posting silly things like "it doesn't work" or "I installed and it shows a black screen" If you plan on using this build, I would appreciate a little on your part to also provide the info we need to help you, like install type, conditions, hardware, PC type, processor type, drive type, filesystem type, what steps you took so far, etc. Please and Thank You.

Updates / Additions:

Kernel 4.14.4 - Tested and boots on ARM/ARM64/ROCK64/AMD/Intel/Nvidia processors, also supporting Nvidia/AMD/Radeon/Intel GFX chipsets

Added drivers and firmware for many devices, including all the silead TS firmware

New boot animation

Rooted with SuperSU (Do not update binary, it might break things)

Substratum works in rooted mode for now

Bluetooth is not working right just yet on all machines. (The bane of my existence)

Much more (check out github)

Bugs / Issues:

Bluetooth issues still exist on many devices

Frik if I know, it's an Alpha release, WTF do you expect here?

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] L3RMiNi:
Awesome!

Thanks again for your hard work and dedication.

Rock on!
[BLISS ROMS Development] electrikjesus:
Would you like to make it a pull request to our 4.14.4 branch? I could easily run off a test build this week with it.
[BLISS ROMS Development] hgblob:
The backports patch only builds on kernel 4.12, others will probably fail. The scripts do a customized version between donor kernel and destination kernel :) For me kernel 4.14 never worked.

PS: We had the discussion about the sensors on SP3 some time ago. With my previous patch and the Intel IIO sensors lib from https://github.com/01org/android-iio-sensors-hal I got the SP3 sensors to work again. I'm not quite sure why but the standard iio sensors lib from Android-X86(hsb?) never worked.
[BLISS ROMS Development] electrikjesus:
Well, tell me where to include it or should I just merge changes somewhere?
[BLISS ROMS Development] hgblob:
I was thinking your k4.12-atsp kernel branch
[BLISS ROMS Development] electrikjesus:
Maybe I'm not following you right. What am I supposed to do with it? Where or what did you replace?
[BLISS ROMS Development] avalanche99:
Hi.

I tested the new alpha version on my Asus T102HA with Intel Atom X5-8350 CPU an everything works fine besides the screen rotation.

It's stuck at one position and the screen doesn't rotate at all.

Tried to test the Sensors but the App I used said "unsupported".

I really want to get dual boot on my Asus T102HA with Android an Windows 10.

Can somebody help me to fix this?

Kind regards

avalanche99
[BLISS ROMS Development] fastguy:
Hi electrikjesus, would you mind pasting a typical grub2 entry for Oreo on an ext4 partition for manual installers like me? (I shared my Bliss install with my Arch partition)

Also, is houdini working now on Oreo Alpha?
[BLISS ROMS Development] KevMetal:
I wouldn't mind a look at the grub entry either
[BLISS ROMS Development] franzli:
Sensors are not working on many devices, particularly the cherry trail atoms, and for screen rotation the workaround is as easy as installing some app for rotating the screen manually. So if everything else works fine, I think you're in a great position for a dual boot!
[BLISS ROMS Development] avalanche99:
But how can I do this to rotate the screen? It is stuck in portait mode but I use the tablet the most of the time in landscape mode like a normal laptop.

I aleady tried several screen rotation apps but the screen orientation stays in portrait mode and the image is then getting smaller and is shown in landscape mode.

If I could rotate the screen manually would be ok for me. But how?

Kind regards

avalanche99
[BLISS ROMS Development] franzli:
Oh, I see! That sounds more problematic indeed, I used to be able to normally rotate, although it's been a while, so maybe there was a regression. This sounds more like a problem with the graphics config than a sensor problem to me though. Which release is this happening on?

I'm not sure if a logcat could reveal anything of interest if you take it right after booting? Maybe get one and post it here for [MENTION=7622168]elektric[/MENTION]jesus (maybe he'll have a chance to comment himself on whether that could be helpful in this case, but I suspect it might).
[BLISS ROMS Development] youling257:
that because https://osdn.net/projects/android-x...mits/305531834fe0ee345e46b5cef8e2c528c03eaf71
[BLISS ROMS Development] digital0:
Unfortunately 8.0 alpha reboots instantly on my Onda obook 20 tablet. Nothing is printed in the console (after removing 'quiet'), just reboots after about a second. If I put kernel and initrd.img from Bliss-v7.2-android_x86_64-OFFICIAL-20171103-0937_k4.12_oto-installer.iso to usb key, the tablet boots. Don't know how to debug it, anyone has any idea?
[BLISS ROMS Development] ingermy:
surface 2017

good job!

wifi, bluetooth, audio, work

unfortunately the touch does not work

thank you
[BLISS ROMS Development] ubuntuh:
[MENTION=5398565]electricjesus[/MENTION] i would be very very greatful if you could compile one last 32-bit version of the oreo rom. I would really appreciate.
[BLISS ROMS Development] Truely Simple:
Want to know if my notebook PC is supported or not.

I have a HP Compaq 6530b with updated BIOS. With windows 7 installed. I tried to install Bliss OS {Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso using USB mode}. I selected 'ISO Image mode' (recommended) rejecting 'DD Image mode'.

After selecting Live CD, I waited for less than 1 minute then a screen came and installation didn't moved further.

On the screen, in top right quarter in white background it was written (not exact): Android x86... found at : dev/sdb1

And below after some space in black background there was written (not exact): Android x86_64 :/ #

After that nothing happened for long time, then I tried typing 'sbd' pressed enter, it showed (not exact): <some path> not found.

Then I tried sbd1, and same thing happened.

After that I was forced to force shutdown the PC.

Is this sequence the sign of my PC is not supported?:confused:
[BLISS ROMS Development] fastguy:
Hi Oreo installers, does the dual screen setup work? If if you plug an external monitor, can you use it separately?
[BLISS ROMS Development] electrikjesus:
I have updated the second post adding a few details for installing next to Windows:

Custom Install For Bliss-x86 8.x UEFI/ESP (64bit)
[BLISS ROMS Development] electrikjesus:
We have stopped supporting 32-bit devices. Please read the following disclaimer from our website: http://blissroms.com

"Bliss OS x86 will no longer provide a 32-bit ISO image download for the community. If you have a project that needs 32-bit support, please contact us to let us know about it, or if you are looking to hire us for commercial development on a project, reach us at blissfamilyroms@gmail.com . Otherwise, feel free to use our XDA Thread for continued free support on all previous releases"

P.S. You all should really apologize to [MENTION=5398565]electricjesus[/MENTION] for always mentioning him by accident...
[BLISS ROMS Development] electrikjesus:
Yes, at least not with the newer builds. Try to find some builds using kernel 4.4.40 or older
[BLISS ROMS Development] electrikjesus:
Also, I was nice and left my archived builds on AFH for a week past what I said I would. I will continue to leave them there for now, but I will no longer be adding new archived builds to their service due to the lack of response from them over what happens to my executables.
[BLISS ROMS Development] Lovelyven:
Can someone please explain how to do the custom install, I can't for the life of me get it installed on nougat or Oreo beta. I am constantly getting stuck at the grub part i just do not know what to do. I followed the instructions on the page but i do not understand it very well. I'm trying to run it on surface pro 2017. Any help would be appreciated
[BLISS ROMS Development] Lovelyven:
Thanks, tried it today but i'm stuck at the grub part not sure what to do
[BLISS ROMS Development] Boscep:
hi [MENTION=928479]electrikjesus[/MENTION]

I have downloaded 8.0 alpha ISO for about 7 hours from official site.

I would glad to see faster server for future builds.

thank you.
[BLISS ROMS Development] fastguy:
Hi [MENTION=928479]electrikjesus[/MENTION], I downloaded and installed Oreo on Surface Pro 3, it went well. (manual install to ext4 Linux partition with the GRUB info in 2nd post).

But I thought Oreo had better two monitor support. It's just a mirror still and I didn't see any options to have extended desktop.

I'll investigate more.
[BLISS ROMS Development] electrikjesus:
Our server speed is directly influenced by the amount of donations we receive. So far, that number is still zero, so I will do my best to not take that as an insult
[BLISS ROMS Development] digital0:
Just donated $10, thank you for your support!
[BLISS ROMS Development] tobad:
does this mean we can not manual rotate the screen??

i have a asus t101ha. it boots in portrait mode and stays regardless of tablet orientation and position....

it would be ok for me with with forcing it to landscape mode, is there any possibility? like a boot parameter in grub???
[BLISS ROMS Development] youling257:
so you just need edit init.sh，#has_sensors=false，OK ?

---------- Post added at 11:17 PM ---------- Previous post was at 11:12 PM ----------

https://groups.google.com/d/msg/android-x86/efgnq9xA5aQ/f0swkZulBAAJ

*HPPAVILION*)

hal_sensors=true

;;

---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------

such as *HPPAVILION*，what is yours ? please you cat /sys/class/dmi/id/uevent

---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------

like a boot parameter in grub，it is impossible !
[BLISS ROMS Development] KevMetal:
my .iso came down within an hour maybe i got lucky

* i would / will donate if i can make a dual install stick on my xububtu/acer netbook but no amount of 20 millon different grub entries can make it boot ( the paths are wrong and the kernel never loads)

live cd can boot -- trying a manual install -- i will try again later :good: if i ever succeed you will see a donation cos its worth it bro
[BLISS ROMS Development] tobad:
The Installation Guide here has some errors in path description.

Here is mine with Windows 10 & EFI & GPT

1. extract iso

* to c:\BlissOS

2. extract system.sfs with 7zip (only if there is a system.img inside - with 8.0-alpha stick with the sfs)

* save it to c:\BlissOS

3. create data.img (>=4GB with RMXtools v1.7 FIX)

* save it to c:\BlissOS

4. access EFI Partition

mountvol X: /s

5. install grub

5.1 extract Custom+UEFI+BOOT.zip to X:

6. configure X:\BOOT\grub\grub.cfg and add

cd /d X:
BOOT\grub\grub.cfg

with 7.x

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

with 8.0-alpha

menuentry 'Bliss-x86 8.0-Alpha' --class android {
search --file --no-floppy --set=root /BlissOS/system.sfs
linux /BlissOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA= SRC=/BlissOS
initrd /BlissOS/initrd.img
}

7. unmount EFI Partition

mountvol X: /d

8. install EasyUEFI_Setup_2.5.exe

and create bootentry to BOOT/grub/grubx64.efi (X:\)

set it to the first entry

9. restart and have fun
[BLISS ROMS Development] tobad:
[MENTION=928479]electrikjesus[/MENTION]

I have a DELL venue 11 running your 7.x fine. With 8.0 Alpha i cant do the setup wizard after booting because some processes continuesly Stop

Com.Android.phone hast stopped

Just to give you some Feedback. Thanks for this great peace of Software!