yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] Ealge0110:
Although this only makes it stay on when external power is connected. Try "Auto Screen Saver" in Google Play, and it has an option to force screen saver on your device attempts to go to sleep, and thus keep it awake, although you might still lose touchscreen functionality if you're on one of the older builds...
[BLISS ROMS Development] youling257:
if you use the apk to sleep/wakeup，did you see suspend to idle(deep) and resume from dmesg ?

su

echo mem > /sys/power/state

what happen ?
[BLISS ROMS Development] Ealge0110:
Couldn't tell, that command just crashes my userspace every time I excute it lol
[BLISS ROMS Development] phnikola:
Pulling this little hair left from my head I just cant boot it from Surface Pro 4 (Core M)

Either of the two:

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180317-1639_k4.15-sb-ga-jwd_m18.1.0-devel_w09_surface-pro-4

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180602-1820_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_sp4

Installed with Androidx86-Installv26.0003 and all goes smooth.

Reboot to GRUB and selecting any of the entries just leads to stuck with white cursor screen.

Any simple solutions that work straightforward?

Thanks!
[BLISS ROMS Development] electrikjesus:
Both should work,my guess is secure boot or bitlocker is still enabled
[BLISS ROMS Development] LORD.ABUMOHAND:
Thanks for the hard work, but can you support Huawei matebook m5 version? I've tried so many version on this device everything works except the hardware buttons and proximity sensor. can you solve these problems? Thanks for the hard working again and keep going!
[BLISS ROMS Development] JG420:
I have 2 hard drives installed in a windows 10 PC. I would like to do a fresh install of win10 on the first hard drive, and install Bliss OS on the second hard drive... how would I even start?

I've tried booting Bliss from a live usb and I get errors. I try to install Bliss using the android -x86 install tool and get errors.

I have a legacy BIOS. And x64 not x86...

Can anyone spare some time and advice?
[BLISS ROMS Development] phnikola:
Nada...

Both of them are disabled...

Have any other idea?
[BLISS ROMS Development] weissgarnichts:
Hello. I successfully installed BlissOS (nightly) on a windows10-tablet (Intel Atom x5-Z8300 / 1.30 GHz (1.83 GHz Turbo) Processor, 2GB RAM, 32GB eMMC) with your installer.

Then i deleted it, because i wanted the bleedy edge (with microG) and installed it again with the installer. Installation was without errors but when i boot AndoidOS it seems to boot but before there comes the bootanimation the tablet switches off (same with "oldmodprobe").

may be a grub option can help but where is the grub.cfg?

This time i installed on D:\ but this can't be the problem, right?

Are the nightlies also with microG or only the bleeding edges?
[BLISS ROMS Development] kypor:
I would recommend reading this post below, however you don't need Notepad++ :)

https://xdaforums.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657/post76960360
[BLISS ROMS Development] phnikola:
Back to my original question...

Can someone post the structure of AndroidOS and EFI folder after successful installation?

Have a feeling that something is skipped in the copying/installation process on my Surface Pro 4. Installer reports success but I always end with Grub empty screen with blinking cursor. Cleaned up my EFI partition several times - but just cannot boot it.

Thanks!
[BLISS ROMS Development] electrikjesus:
Try reading this post, maybe follow to the previous posts it is talking about. I found this using the thread search for "surface pro 4"

https://xdaforums.com/bliss-roms/bl...s-x86-pc-s-t3534657/post76855394#post76855394
[BLISS ROMS Development] weissgarnichts:
Ok, thank you.

Reinstalled the nightly again on D:/ with the installer and it works again, so grub seems to be ok.

No microG but i will try it for a few weeks and wait for a new bleedy edge version that hopefully runs on the tablet.
[BLISS ROMS Development] dcduartee:
Anyone else has the "checking info" problem when adding a google account on the latest bleeding edge?
[BLISS ROMS Development] hecksagon:
Late to answer but this is caused by the TV applying overscan to the video signal. It is throwback from the old analog TV days, where the signal at the top and bottom of a frame was generally garbled. The TV would crop the image slightly to get rid of it. New digital signals don't have this issue, but this practice continues to persist. You can fix this on some TVs by hitting the aspect ratio button on the remote until its set to "just scan" or "original" or something to that effect. On some LG TVs you have to label that input as "PC" to get the overscan to turn off.
[BLISS ROMS Development] Atmans:
hi

I have checked all options and all HDMI inputs (Not working)

Version, Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9 works OK

Android x86 (in the Deprecated folder) works fine

I installed it on a different machine that does not have a screen and works normally when connected to HDMI

simply, the android system does not turn off the first screen when connected to hdmi and this is the problem
[BLISS ROMS Development] kypor:
Sorry if this is a dumb question, but is Houdini enabled by default, or is there a way to activate it? I cannot seem to get some apps working. I tried Androidx86, and the apps work using Native Bridge, but they do not work using Bliss.
[BLISS ROMS Development] youling257:
I used Side slip ，but default standard windows，many chinese app isn't material design ，always standard，even though use taskbar select phone size ，it still standard . what is freeform source code ? force default phone size .

remix os by chinese，its Windows mode，Optimization windows mode for chinese app ， Optimization windows mode for the Android app use iOS design .

google source freeform Windows，such as gmail app design，windows mode Optimization . in fact，many Android app UI use iOS design .

https://www.xda-developers.com/andr...what-it-is-and-how-developers-can-utilize-it/

https://github.com/farmerbb/Launcher3-Freeform
[BLISS ROMS Development] lollyjay:
[MENTION=5550662]youling257[/MENTION] sorry I can not help. I just activate native freeform windows by using terminal app and typing "settings put global enable_freeform_support 1"

By the way thanks for the link to the article. I had lost it:good:
[BLISS ROMS Development] strikegtx:
Just installed the latest (bliss-x86_64_n7.1.1r22_03.03.17_k4.10-blissified_01) on my Surface 3 (non-pro) aswell and also face the same issue, is a previous build more suited?

Also wireless seems to "connect" but claims no internet quite a bit, needs restarts to resolve.
[BLISS ROMS Development] electrikjesus:
The WiFi is a known issue on the later kernels. Toggling airplane mode for 10 sec. works for most cases.
[BLISS ROMS Development] electrikjesus:
Doing one last round of tests on a few new builds. Our rootless EDU versions are in the queue for this next release too! We're using the blissified kernel 4.4, and I will also be releasing a couple bleeding edge builds using the Ubuntu zesty kernel 4.10x as a base.
[BLISS ROMS Development] lollyjay:
Hey does anyone know how to get rid of the nav bar? I've tried a number of apps but they don't disable it.
[BLISS ROMS Development] L3RMiNi:
I use Expanded Desktop/Immersive Mode. Couldn't find a way to disable it either.
[BLISS ROMS Development] lollyjay:
I did a little research and found that on SOME 7.1.1 systems you can add the line

qemu.hw.mainkeys=1

to end of build.prop. I tried it and it works great. Now I am using Taskbar as home screen and Pie Control to provide the nav keys.
[BLISS ROMS Development] ElfinJNoty:
Thanks for sharing this.

We plan to include this along we many other features available with our Bliss CAF branch. Porting over features from CAF to AOSP has been slow but steady. Big things to come with Bliss-x86!!!

Stay tuned!
[BLISS ROMS Development] lollyjay:
Incidentally I noticed that apps opened from Pie Control also open as windowed apps. Cool...
[BLISS ROMS Development] electrikjesus:
Ok peeps! I'm finally uploading a few builds. Bliss-x86-EDU for 32 & 64 bit machines. Using our kernel 4.4 branch. Then a special 64 bit build is heading to the Bleeding Edge folder, with last week's changes to the Ubuntu Zesty kernel 4.10, but all blissified to work with Android-x86.

Common issues with these builds are still wifi issues, and other machine specific bugs due to poor driver or firmware support. So please keep that in mind when reporting bugs ;)

You will find a very new features in the Bleeding edge builds I'll be uploading this week. BlurUI, HeadsUp notifications, Blissify app reworked a bit, and a few other things I might have forgotten too. Big changes coming as well. Don't want to say too much yet though ;)

EDIT: Builds are all uploaded folks! Two rootless EDU builds and a bleeding edge build. More to come soon!
[BLISS ROMS Development] franzli:
On the latest bleeding edge build I'm getting massive force closes of com.android.phone (has stopped), which makes it impossible to get beyond the initial menu. I haven't tried installing to disk yet, so I don't know if this is just an issue with the live medium, but I didn't have this issue with the previous build.

If I'm doing anything wrong, I'll appreciate any help!

On another note [MENTION=928479]electrikjesus[/MENTION], I'm trying to use this on the Dell Venue 8 Pro 5855 (the newer 2016 model) and I'm very impressed to say that the previous build seemed to work very well (compared to my previous attempts of getting android variants to run on an Atom tablet)!

The buttons didn't seem to work, but I think I read that other people had that issue on other platforms, I didn't get to check sound. Bluetooth also didn't work, but here I was wondering if there'd be a way to borrow from the linuxium project - getting Linux to run on baytrail and cherrytrail platforms? Bluetooth is working on the latest build of that one, which is also on a 4.10 kernel.

On the other hand, if I remember correctly, backlight control seems to be working on your ROM on the DV8P 5855 and I'd love to find out why/how - that's the one thing (apart from sound) that's missing from the Linuxium Linux builds and it would be great if it would be possible to replicate your success with the backlight control there!

ps: just checked with older build 0303 and in fact Bluetooth is working, albeit a bit unstable (seems to switch off briefly every so often). That's really great!

Regarding the brightness settings, could it be that brightness is only regulated by color settings, rather than hardware-wise? There seems to be no effect on battery life from reducing or increasing brightness...
[BLISS ROMS Development] lollyjay:
Same here...
[BLISS ROMS Development] fastguy:
I had the "phone stopped" issue but guessed it was due to inaccessible Data location. This was a Hdd install, so I created /androidos/data folder and did not provide any SRC= or DATA= parameters in the kernel line in grub.

That worked.
[BLISS ROMS Development] electrikjesus:
There was a firmware repo structure change between the two releases, and with that, a ton of updates. But as my experience showed, not all these updates provided the same compatibility. There were machines that could run Bliss that somehow couldn't now. So, I reverted my changes back, minus a few updates for these next few builds I have heading your way. I will be testing them today and tomorrow, so hopefully by Wednesday you all will see them dropped in the AFH folder.

That bleeding edge build I uploaded over the weekend is not going to work on all machines that the other 4.10/4.11 kernels I've been using would. But, it allowed for other machines that haven't had any success, to boot into a somewhat Blissful experience. So that in my mind was worth the effort. Who knows, maybe one of these days someone who knows what their doing will see my efforts and offer a hand on Bliss-x86. It is a little lonely in this corner of the universe.
[BLISS ROMS Development] electrikjesus:
Yes, this will work now on many of these builds. But not all. There are still some filesystems it doesn't agree with. Android-x86 project did try to fix this, and it kinda worked, but there are many issues with how well it worked on my tests, so I reverted that change to save us all a headache.
[BLISS ROMS Development] fastguy:
I used it with an ext4 filesytem on which I also have my Arch.
[BLISS ROMS Development] franzli:
thanks for the feedback and update! I'm really glad I found out about your work here, good to see an android x86 version with a modern kernel. Eager to try this on my skylake tablet as well, which was never going idle on the 4.4 kernel that remix os ships with.

Regarding the backlight question, could you tell me how this is handled - by actual hardware dimming or through software? I'm just curious if this could help with Linux installations as well.

I'd love to be able to lend a hand, although I'm afraid at this point I won't be able to provide much expertise. Eager to learn though (time permitting)!
[BLISS ROMS Development] electrikjesus:
I would only be guessing myself if I were to try and explain. Possibly the people over at the Android-x86 projects Google group could help explain better. I'm still learning myself.
[BLISS ROMS Development] electrikjesus:
UPDATE - 03.21.17 - bliss-x86_64_n7.1.1r28_03.20.17_k4.11rc2_02.iso

Uploading a special Bleeding Edge build for you all this morning. Updates include Kernel 4.11rc2, firmware repo has been reworked to include support for more hardware (including devices that lost support on previous builds), advances in multitasking UI, system level freeform window support, Bradon Farmer's Taskbar Support Library ( https://github.com/farmerbb/Taskbar-Support-Library ) and it looks like local modules are building correctly as well. I will be building all these updates and more into a couple stable builds also over the next day or so. Keep your eyes peeled for those soon :)
[BLISS ROMS Development] electrikjesus:
We do use a different houdini that is not the same as the one included in Android-x86. Ours is enabled by default, but it doesn't like some of the Atom based processors sometimes. If things seems to work better with the bin that Android-x86 project is using, we could likely move back to their method fairly easily.
[BLISS ROMS Development] kypor:
Awesome thank you! Mine is an ATOM based device so I guess it probably won't work. This was my main issue as I was able to install Bliss, but I was unable to use the app I wanted. I tried Androidx86 and was able to install as well, and use the app wanted, but it lacks WiFi support for my device (Asus 102HA), despite everything else working smoothly. If Bliss was able to use Androidx86 Native Bridge solution then I could use Bliss. :)
[BLISS ROMS Development] bfmetcalf:
I have noticed a bunch of apps that I use not working as well. They worked on one of the builds back in Feb or March I think. Sonos is the main one that I used to use, but am no longer able to. May be worth a try to go back to the Android-X86 houdini to try it.
[BLISS ROMS Development] joq3:
I am thinking of buying a Microsoft Surface 2 (regular version). But I cant find any information on how well Bliss works on this. Are there any bugs at all? Hows the performance and battery life?

Is Bliss rom rooted as standard? Can I install SuperSU and use Tasker to the full externt?
[BLISS ROMS Development] astroganger:
Buy android device instade
[BLISS ROMS Development] Blubster:
Don't! It's an arm device, with a tegra 4 inside, Not an x86 processor. There is no android for it as far as I know. A surface pro 2 could work (I have not tried bliss on it but android-x86 works wonderfully on it) and can be found cheaply nowadays.
[BLISS ROMS Development] joq3:
I dont know how I missed that detail! Thanks! Yes the Surface Pro 2 is impressive, I really like the build quality and the stand. How well does android-x86 work on it? Is it as good as a ”real” android tablet? Any bugs or issues with battery time or performance? Is it Oreo or Nougat?
[BLISS ROMS Development] Blubster:
It works quite good, it is a little off topic though, as I did not try bliss with it yet. I tried Android-x86 nougat r1. I don't remember if sleep was working, I think not.

Performance was stellar, MUCH better than any android device I have ever owned. Smooth as silk.

I experienced one bug, the trackpad stopped working after a few minutes, touchscreen was fine and keyboard too.

Sound works, wifi works. Pretty much everything works actually, except the (crappy) trackpad. No widevine so Netflix is out of the question, or maybe it works in SD, I did not try it anyway.

I played some swgoh on it and it was perfect. Battery life should be comparable to windows I guess, nothing to write home about, maybe 2 to 3 hours of screen on time, definitely not as good as a standard android tablet. But my testing was short and I don't remember if sleep worked. I did not do a proper test of the battery life.

I'm out of town until the end of next week so can't try bliss until then, I'll try it as soon as possible on the surface pro 2.

Don't hesitate to pm me if you don't hear from me in the next few weeks!
[BLISS ROMS Development] ElfinJNoty:
You did try to boot to bios/UEFI and select something besides "Windows Boot Manager" as the primary boot option.... Correct?
[BLISS ROMS Development] Dr4g0n:
Hello,

thank you for this awesome work.

I curently use the Version "Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180619-2059_k4.16.14-bliss-ipts-ga_18.1.0-devel_w14_dev-kernel.org.iso" on my surface book 2 13".

The touch screen works perfectly. Unfortunately I miss the Google Apps, is there an instruction how I can install them later?
[BLISS ROMS Development] egandt:
Figure it out needed gru2win and had to disable everything but grub in the UEFI boot menu.

ERIC
[BLISS ROMS Development] Yong73:
My sp3 works perfectly with Remix os, it’s old os, but stable is more important for me. Everything are working on my sp3

从我的 iPhone 发送，使用 Tapatalk Pro
[BLISS ROMS Development] fastguy:
Which version of Remix? As far as i know SP2 like SP3 only supports connected standby and not normal standby, so it would not sleep normally (only software suspend) and thus battery life would not be so good.

How's your experience in this?
[BLISS ROMS Development] Blubster:
Just a little remark, actually surface pro 2 do not support connected standby, even if they have the same processors as the surface pro 3. No legitimate reason for that...
[BLISS ROMS Development] VMolina141:
Question on game helper

hey, does this OS have a game helper to map keyboard keys to play games? like Remix and Phoenix OS have? if not, will you add it? (theres like 220 replies pages, cant read them all) i've been thinking to change from phoenix to another android based OS because of poor problem fixing there, thx
[BLISS ROMS Development] digital0:
Yes.
[BLISS ROMS Development] fastguy:
Really this is very good then. It makes a good 2nd hand guy. I'll check it out!
[BLISS ROMS Development] egandt:
I'm on Beta1 for the Surface 2017 it works, but I can not figure out root

"Rooted with Superuser. Access Superuser settings from Settings>Users"

I'm on 6-02 for the Surface 2017 it works, but I can not figure out root, the above statement does not help, I've extracted the system to a system.img and it is R/W, but I can not figure out any way to manage root and any root app simply says it is not rooted. I have a need for root, as otherwise this is working reasonable well on the surface, but no single post explains what needs to be done beyond extract system.img and then go to Settings->User (there is nothing root related there!).

Note: Root checker states "Not Rooted".

How do I enable root now that I'm R/W?

ERIC
[BLISS ROMS Development] simonmcmullon:
no touchscreen support, just tried this in a new corebook
[BLISS ROMS Development] farivar:
edit build.prop in the system folder

add sleep=1 sleep.earlysuspend=1

also edit your grub.cfg and add "sleep=1 sleep.earlysuspend=1"

my cube mix plus hibernate properly
[BLISS ROMS Development] AndrewH1993:
I'm unable to get this to work on my Macbook Pro early 2011 model A1278 as well as my Surface Pro 4. I've tried the Udoo imgs, the 4.4 and 4.9 stable ISOs and the bleeding edge Surface Pro 4 img as well. No luck. Only once was I able to get my Mac to boot on the 4.9 Stable ISO flashed by RUFUS both ISO and The Udoo (flashing IMG option) No luck since. Only formatted to Fat 32. What am I doing wrong?
[BLISS ROMS Development] electrikjesus:
!!New Bliss-x86 v10.1 PC Beta - 07/16/2018

We have a somewhat transitional update for you all today. I rebased BlissOS off our GSI project (Bliss-Bass), and the outcome is actually pretty stable. Some old issues have returned, and some have been resolved. Most of the details can be found below in the Updates/Additions or the Changelog. Build might take a while to upload, so keep checking back.

Have FUN!!

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180716-1838_k4.15.18-ipts_18.1.0-devel_w14_dev-kernel.org.iso - This contains firmware for all current devices included in kernel.org. - THIS BUILD INCLUDES OpenGapps

Updates / Additions:

Kernel 4.15.18 - reworked for all devices, and added IPTS commits *Surface devices will require manual firmware update*

Moved to old way of packaging the system image. (for root to work, you must extract the system.img file from within the system.sfs, then delete the system.sfs file)

Rooted with Superuser. Access Superuser settings from Settings>Users (R/W works if you extract system.img, read above)

Substratum Service mode enabled (now fully working, but reboot required after you build/enable a theme. select from Settings>Display>Advanced>Themes)

A few fixes and updates for Bluetooth

Fixes for some devices that didn't boot right

Using Android-x86's newest updates to bootable/newinstaller (this comes with a new UEFI grub menu)

Maybe more... I've been busy

Bugs / Issues:

Android Service Has Stopped dialog is back. It does not harm anything though.

Bluetooth issues still exist on some devices

you will get Play Store and process crashes until WiFi is connected. Just dismiss these for now. Once connected to WiFi, things should work properly. **ONLY ON OPENGAPPS BUILDS**

Sound or keyboard might not work, try to boot using the secondary modprobe option

Expect more. It's only a beta release. Report your issues, but make sure you SEARCH the thread first to make sure it hasn't been answered. And post logs too (I know, WTF are logs anyways??)

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/BlissOS/bleeding_edge/
[BLISS ROMS Development] minilandl:
Okay you have to use a specific bliss os tool https://xdaforums.com/bliss-roms/bl...ease-blissos-android-pc-toolbox-v1-0-t3806721 I will hopefully be writing a more detailed guide on how to get root and magisk working soon considering many people are stuck and i dont blame you its kinda cryptic. Basically copy the system .sfs file into the in folder then extract it with the exe and repack it as a system.img file then remove the system.sfs from the live usb or hdd and replace it with the system.img that was created.
[BLISS ROMS Development] farivar:
this release give me

"android System

There is an internal problem with your device. contact your manufacturer for details"

when i connect to wifi the device reboots. im using cube mix plus Core M7y30
[BLISS ROMS Development] arifqur:
Hi [MENTION=928479]electrikjesus[/MENTION]. Thanks for all the hard work. I tried the latest build but sadly it still does not boot on my HP Specter x360 15T.

The last build that boots is the March 8 Nightly.

I remember you said something about updating the old kernel with new commits /etc

Take care buddy
[BLISS ROMS Development] Zummmy:
Hello,

I have the same problème than you. Did you find a solution?