yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] stdiopt:
I guess I have something wrong then, some arm apps are closing, I will try to look further on this issue

06-21 22:20:16.776 5795 5795 E AndroidRuntime: Process: com.microsoft.rdc.android, PID: 5795
06-21 22:20:16.776 5795 5795 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/com.microsoft.rdc.android-v__ep2QpWt0mK-d4xnvAlw==/lib/arm/libRdpAndroidClientCore.so" has unexpected e_machine: 40 (EM_ARM)
06-21 22:20:16.776 5795 5795 E AndroidRuntime: at com.microsoft.rdc.android.RDP_AndroidApp.onMAMCreate(SourceFile:196)
06-21 22:20:16.776 5795 5795 E AndroidRuntime: at com.microsoft.intune.mam.client.app.MAMApplication$Impl.onCreate(SourceFile:93)
06-21 22:20:16.776 5795 5795 E AndroidRuntime: at com.microsoft.intune.mam.client.app.MAMApplication.onCreate(SourceFile:46)

I think processor supports it as I did run arm apps on older versions of android-x86 on same machine
[BLISS ROMS Development] ziggystardust:
Surface pro 2 cannot boot

Hi, imi have try bliss Os (bleeding edge, older version and latest version) using uefi windows installer on my Surface Pro 2 and bliss stop at "Starting Android" message, no splash screen and no activities. When using nomodeset it show bliss splash screen and seem to bootloop forever.

However, when using BlissOs stable v7.2 no problem occurred and can boot properly.

Any suggestions or troubleshoot?

Thanks
[BLISS ROMS Development] electrikjesus:
The kernels. Your device runs best with an older 4.4.x kernel
[BLISS ROMS Development] arifqur:
Thanks [MENTION=928479]electrikjesus[/MENTION]. You mean to use an older kernel extracted from anolder build of Bliss(That was Booting)?
[BLISS ROMS Development] ziggystardust:
Thanks [MENTION=928479]electrikjesus[/MENTION]

Can I use/ extract kernel from stable build and use it on the latest build?

thanks,
[BLISS ROMS Development] arifqur:
Okay! The new build only boots on the option "No Hardware Accelleration". Tried booting with the kernel extraxted from the 308 Nightly(Which is the latest rom that boots on my HP Specter x360 15T i7 8550U and GForceMX150) and the Boot logo was large like in nomodeset and after booting the system was not responding to either touch or keyboard

BTW: The new UI of the Boot Menu is Dope
[BLISS ROMS Development] arifqur:
Also for guys running Windows 10 with dual booting and boot menu not showing try this:

Open command prompt with administrator privileges and type;

bcdedit /set {bootmgr} displaybootmenu yes

And reboot.

Hopefully the grub menu will show up every time you boot

---------- Post added at 01:01 PM ---------- Previous post was at 12:50 PM ----------

@electrikjesus thanks for all the hard work.

Can you suggest what to do in my situation as the last nightly that boots on my system is the March 8 one and the last bleeding edge that boots is the February 2. All three newer ones boot on nomodeset.

Although I am happy with my March 8 build, the flashaholic in me wants the new builds badly.

Also I am still not able to mount my other HDD partitions with stickmount app.

Any suggestions?

My system is HP Specter x360 15T i7 8550U and GForceMX150)
[BLISS ROMS Development] electrikjesus:
I will likely need to release another build with an earlier kernel. I'll see if I can do some magic to the 4.15.x kernels and update it with all the latest patches
[BLISS ROMS Development] arifqur:
Many thanks for your reply and your hard work.
[BLISS ROMS Development] MagicAndre1981:
thanks for the new version. I tried it and I still have the boot issues (freeze at "starting android" in text mode) with normal boot and must use nomoderest, but performance is very bad. The Broadcom WLAN issue is still present.

Toshiba Encore 8 WT8-A-102 (Atom Z3740).
[BLISS ROMS Development] arifqur:
Surprisingly on nomodeset I still get great performance. Probabaly because the i7 quad-core is a very fast chip
[BLISS ROMS Development] MagicAndre1981:
you can't compare an i7 to a slow Intel Atom cpu
[BLISS ROMS Development] DoughMucker:
Thanks for the updates!

I've been using the previous bleeding edge builds on my Surface 2017 with fairly good results. Unfortunately, I lose all touch capability with this one. My original install was the Easy Install method but for this (and previous updates), I extracted and replaced all the files in Android-OS. Updating this way worked previously, but would it stop working now for some reason? Would providing a syslog or other log help figure out what happened?
[BLISS ROMS Development] electrikjesus:
I am facing the some touch issues also on my Surface Book. Already reported though ( https://github.com/jakeday/linux-surface/issues/203 ) For the Surface 2017, Now that the latest build has working system R/W, you will need to replace the firmware found in system/lib/firmware (i think) with the correct firmware for your device.

Surface Series Devices:

Series 5 devices: Surface Book 2, Surface Pro 2017

Series 4 devices: Surface Book, Surface Pro 4, Surface Laptop

Series 3 devices: Surface Pro 3

For the ipts_firmware files (series 4/5 devices only), please select the version for your device.

v76 for the Surface Book

v78 for the Surface Pro 4

v79 for the Surface Laptop

v101 for Surface Book 2 15"

v102 for the Surface Pro 2017

v137 for the Surface Book 2 13"

For the i915_firmware files (series 3/4/5 devices), please select the version for your device.

kbl for series 5 devices

skl for series 4 devices

bxt for series 3 devices

Firmware files can be found here:

https://github.com/jakeday/linux-surface/tree/master/firmware

I guess that was one thing I forgot to mention in the update post. The Bleeding-Edge build will work with touch out of the box for Surface Book only, all other Surface devices will need to update firmware manually.
[BLISS ROMS Development] astroganger:
anyone can help me to know where is the instruction to install for surface pro 2017 ???
[BLISS ROMS Development] mrdannyaitch:
I was ready to bin my Minix Z64 (Intel Z3735F) as it was stuck on 4.4.4 but this has given it a new life, especially as I now have a work phone that I can't root and play with! Just wanted to firstly say thanks, but also to ask if anyone can point me to a likely location in order to fix the lack of audio over HDMI on this setup? I can follow instructions pretty well but I'm no coding expert...

I tried installing the latest bleeding edge using the easy tool from the first post, couldn't see what the error was on screen but it basically got stuck at the stage where it was installed but not booting. So I'm back to 7.2 (if anyone finds this in the future, use the k4.9 .iso, had lots of issues on the other build.
[BLISS ROMS Development] TONYTONYAU:
Pardon me sir.

In the download section, which one is the correct ISO for surfacebook?

I don't see a new version ISO with surfacebook names on it. (1st gen SB, not 2nd gen)

Or will this one work on surfacebook?

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180603-1422_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_ipts_v103.iso

Thanks.
[BLISS ROMS Development] farivar:
I miss the opengapps or gms version.

Is there any way to install it manually?
[BLISS ROMS Development] electrikjesus:
Any build ending in dev-kernel.org, and using a kernel with -ipts- in the name is tuned to work on the SurfaceBook
[BLISS ROMS Development] TONYTONYAU:
I used the one I mention above. But touchscreen were not working.

I try surface2 13 one, only liveCD work. For some reason it wont create a grub option while booting :(
[BLISS ROMS Development] electrikjesus:
Use the latest release, it will not be marked as a "surface" build
[BLISS ROMS Development] avalanche99:
I tried this onmy SP4.

Copied the i915 firmware in system/lib/firmware/i915 folder and the ipts firmware to system/lib/firmware/intel/ipts.

Touch works again after a restart but stops working after a couple of minutes.

Any idea where the problem comes from?

Kind regards

avalanche99
[BLISS ROMS Development] DoughMucker:
I'm having trouble mounting system as rw. Searching through the forums I see a possible cause of being on an NTFS partition. But that's okay for the time being, I'll go back to the previous version for now.
[BLISS ROMS Development] arifqur:
Try to extract the system.img from system.sfs and replace it in the AndroidOS folder. Remember to delete the syatem.sys file from the same folder.
[BLISS ROMS Development] DoughMucker:
Thanks. I'll give it a try in a couple weeks when I'm available again. :(
[BLISS ROMS Development] mrdannyaitch:
Wonder if someone can help me please.

I'm trying to run Kodi but I cannot get it to run at all -

https://pastebin.com/artwLqQ0

It tries to run once, tried again and then stops. I also seem to have a high number of audio errors showing - is this the system trying to output via HDMI which I'm also trying to resolve.

Help greatly appreciated.
[BLISS ROMS Development] arifqur:
Try disabling the Google app in settings>apps and then force stopping it. I had some audio codec and media server errors when i used Google assisstant.
[BLISS ROMS Development] mrdannyaitch:
Thanks I'll give that a go. There's no onboard mic as far as I'm aware, no port for it anyway. But is that likely to stop Kodi even starting? I've not had it working yet.
[BLISS ROMS Development] mrdannyaitch:
I don't have the Google app Installed
[BLISS ROMS Development] arifqur:
Okay. Type the following in Terminal app after su:

/system/bin/dumpsys cpuinfo

The resulting output would let you know of the cpu usage per app. Maybe that will narrow it down
[BLISS ROMS Development] arifqur:
Yeah tried the version for x86. It opens but a toast appears sying that native libraries were not found etc and then if you click addons it fcs
[BLISS ROMS Development] ElfinJNoty:
If you download/install Kodi from the playstore, it should automatically detect and pull the x86 variant and it's lib's.

I have had Kodi installed and running on every release(and many test versions behind the scenes) for about a year now.... Have never had an issue.

Kodi versions do not change often... So compatibility should be pretty consistent.

And please tell me you are using stable Kodi version and not an alpha 18 ?
[BLISS ROMS Development] arifqur:
Installed Kodi via playstore and its version number is 17.6.

It fcs right after opening. Can't even see it load.

Second version I downloaded via a link from the web and it opens butdisplays a toast saying that libraries are missing.
[BLISS ROMS Development] electrikjesus:
Can you please send me a screenshot of the bottom "OpenGL" section in Settings>About Phone?
[BLISS ROMS Development] mrdannyaitch:
Here's mine - as it was me that raised this initially - sorry it's rotated
[BLISS ROMS Development] mrdannyaitch:
su

x86_64:/data/data/com.termux/files/home # /system/bin/dumpsys cpuinfo

Load: 1.89 / 0.49 / 0.16

CPU usage from 486471ms to 467846ms ago (2018-06-28 20:16:17.223 to 2018-06-28 20:16:35.848):

36% 1635/system_server: 27% user + 8.9% kernel / faults: 14065 minor 1381 major

23% 1141/mount.ntfs-3g: 6.6% user + 16% kernel / faults: 13500 minor

18% 1479/bootanimation: 11% user + 6.8% kernel / faults: 149698 minor 2 major

8.5% 1151/loop1: 0% user + 8.5% kernel

8.5% 1169/loop2: 0% user + 8.5% kernel

7% 744/kswapd0: 0% user + 7% kernel

5.1% 1075/mmcqd/1: 0% user + 5.1% kernel

4.2% 1300/surfaceflinger: 2.5% user + 1.7% kernel / faults: 13 minor

1.9% 1311/installd: 0.7% user + 1.1% kernel / faults: 65 minor

0.8% 1148/loop0: 0% user + 0.8% kernel

0.6% 1156/kworker/2:1H: 0% user + 0.6% kernel

0.3% 6/kworker/u8:0: 0% user + 0.3% kernel

0.3% 1228/logd: 0.2% user + 0.1% kernel / faults: 60 minor

0.3% 7/rcu_preempt: 0% user + 0.3% kernel

0.3% 1299/servicemanager: 0.1% user + 0.2% kernel / faults: 2 minor

0.2% 1600/kworker/1:2: 0% user + 0.2% kernel

0.1% 1308/audioserver: 0% user + 0% kernel / faults: 20 minor 1 major

0% 1//init: 0% user + 0% kernel / faults: 78 minor

0% 22/migration/2: 0% user + 0% kernel

0% 1100/kworker/3:1H: 0% user + 0% kernel

0% 1205/ueventd: 0% user + 0% kernel / faults: 107 minor

0% 1307/zygote: 0% user + 0% kernel / faults: 1 minor

0% 1312/keystore: 0% user + 0% kernel / faults: 12 minor

0% 1317/netd: 0% user + 0% kernel / faults: 9 minor 1 major

69% TOTAL: 14% user + 17% kernel + 37% iowait + 0% softirq

no idea what I'm looking at here!
[BLISS ROMS Development] electrikjesus:
Ahh, it defaulted to the Mesa DRI renderer... Do things work different when you add HWACCEL=0 to the default entry in grub?
[BLISS ROMS Development] mrdannyaitch:
I'm sorry but at best I'm an intermediate instructions follower! Have been trying to work this out for myself but the Google groups for x86 was essentially a foreign language. Happy to mess around if there are clear instructions, have edited build props / can follow terminal steps but that's about it. Sorry.

Got myself into the grub entry for Android X86 (first grub entry) and opened a command line to see if it may be something obvious to try, but no.

Appreciate the help in advance
[BLISS ROMS Development] arifqur:
Here it is:

Edit: Tried it with HWACCEL=0 and boy the system gets reall y stuttery and choppy and laggy.

Going back in 3,2,1
[BLISS ROMS Development] amitkma:
I am building bliss rom for my pc and following the instruction I am able to generate the iso image. I am trying to build ota for the image I have generated. There is bliss_ota (which is basically built for bliss-roms) in manifest of x86. I am just wondering if it would work with Bliss-x86. I have gone through the code and found that ota.xml should be there on server but surprisingly there is no ota.xml in Bliss-OS directory and they are there in BlissRoms. Kindly provide valuable suggestions.
[BLISS ROMS Development] pankspoo:
Can we able to play games?
[BLISS ROMS Development] dy4pev:
Change boot order

How do i change the grub boot order? Dual boot with windows 10
[BLISS ROMS Development] arifqur:
Try using the EasyUEFI windows tool
[BLISS ROMS Development] dy4pev:
How?

---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------

i tried using easyuefi but it can only change the order of bootloaders(windows and grub) not the bootorder in grub2 booterder
[BLISS ROMS Development] arifqur:
Install Notepad++ .Open an elevated command prompt i.e. Run as administrator and type the following:

mountvol X: /s

X:

EFI\Boot\grub.cfg

Now the grub.cfg will open in the Notepad++ . You can move the entry you want to boot first and cut and paste and save and reboot.
[BLISS ROMS Development] Heelixx:
Great job to the dev. I am currently using the stable version of this rom but everytime that I try to use any versions of the nightly or bleeding edge, I always seem to get stuck at the point where it says something like detecting synaptic mouse. This has happened in all of the bleeding edge and nightly versions. Is this a kernel issue? Can it be fixed?
[BLISS ROMS Development] ElfinJNoty:
Here is a video demonstration of using the Easy UEFI installer via Windows10 using the latest nightly(at time of screen capture)

https://youtu.be/0UkPyYfj0xA
[BLISS ROMS Development] Atmans:
Installer Version:2.6.0.0

Secure Boot ... Not Supported

Manufacturer: Acer

Model: Aspire E1-571

Product: EA50_HC_CR

BIOS info:

ACRSYS - 1

InsydeH2O Version 03.72.23V2.21

InsydeH2O Version 03.72.23V2.21

InsydeH2O Version 03.72.23V2.21

Available GPU(s):

GPU: Intel(R) HD Graphics 4000

=============[REQUIREMENTS CHECK]============

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz

OSVer: Microsoft Windows NT 10.0.16299.0

OperatingSystem Version ... ok

Windows Security: Access NVRAM Privilege ... Not All Set

Not possible to install on this laptop
[BLISS ROMS Development] electrikjesus:
I was never able to get Bliss' ota to work with x86. There is also no real recovery for x86 yet, so we won't likely have a working ota in the traditional sense.

I am currently working out a method to treat x86 like Treble builds though, and possibly build out an ota solution for that eventually, or find one we can adapt for x86... Who knows
[BLISS ROMS Development] electrikjesus:
[IMG="*Shall we play a game"]https://i.imgur.com/EjrMrfP.gif[/IMG]
[BLISS ROMS Development] electrikjesus:
I use notepad ++, but you have to mount your UEFI partition to find it
[BLISS ROMS Development] electrikjesus:
Are you asking or stating that it didn't work... :confused:
[BLISS ROMS Development] donthateme702:
I heard the funniest thing, guy tells me that he could only unlock his phone half way to use this,haha. How do you spend 3 hours unlocking phone and its halfway.
[BLISS ROMS Development] Atmans:
[MENTION=928479]electrikjesus[/MENTION]

yes that was the question,sorry missing (?)

I can not install this on a laptop, but I installed on Intel Cherry Trail Z8350 Quad Core 1.84GHz on PiPO X9S

I have a problem with the resolution on Pipo and I have a different one on the tv

but it works correctly on Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4

TV BOX

TV After HDMI CONNECT
[BLISS ROMS Development] electrikjesus:
Try to install SecondScreen from play store, that can help with the HDMI resolution issue you have
[BLISS ROMS Development] arifqur:
My GeekBench Scores on Bliss
[BLISS ROMS Development] Atmans:
[MENTION=928479]electrikjesus[/MENTION]

Thank you I will check it today

Edit:

The application did not help, it is similar to typing in the console wm size, wm density

this version work great Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4 many android 6.0, rooted remix OS 6.0 but not latest Bliss OS ,why is this happening?

Could it be if the android turns off the screen when connecting to tv some like this option "video = LVDS-1: d" maybe it would help
[BLISS ROMS Development] electrikjesus:
How does it stack up against the competition?
[BLISS ROMS Development] Ealge0110:
Didn't try GeekScore but with 3DMark my SP4 i5 8G with Bliss beta 10.0 out scored 98% of Android devices, and in particular out scored 80% of Google Pixel 2 devices xD
[BLISS ROMS Development] electrikjesus:
I'd like to see a comparison between Pixel C or something with similar specs
[BLISS ROMS Development] arifqur:
Sorry but only checked the benchmark with Bliss.

The reason being that my setup is blistering fast even on win 10 but the sheer raw power that it seems to generate on Bliss is absolutely mind boggling.

The largest of apks install in split seconds and everything launches immediately.

I always wanted to try out Android on an Iphone Bionic chipset and see if it was the Android OS lagging or on inferior hardware.

This is the closest that I can come to mimicking that scenario.

Great job [MENTION=928479]electrikjesus[/MENTION]. There is nothing out there that can even come close to this setup.

That means a lot really since on a 2018 hardware built for windows 10, I am using Bliss as my daily driver. Have not booted into Windows for quite some days now.
[BLISS ROMS Development] arifqur:
Also thanks for including Wireguard support in the kernel. Do not remember reading anywhere that it was included. A nice surprise
[BLISS ROMS Development] electrikjesus:
I don't usually mention upstream additions to the kernels. Those should all be available at https://www.kernel.org
[BLISS ROMS Development] electrikjesus:
OK people, I would like to speak to you all frankly for a moment. We get a bunch of emails, PMs, IMs, DMs, etc. per week asking us to add support for this device or that device, and some of them are actually helpful, but the majority are not. They either request support for such'n'such a device, with no information as to where we can find Linux or android kernel sources, and on the few occasions we do get linked the sources, they are just a dump, with no commit history, no commit attribution, no info as to what kernel subversion, etc. 99% of the time.

Now let me explain why this isn't helpful. As open-source community developers ourselves, we do what we can to make sure the 1000's of developers who put their work into every possible corner of our source code is given the credit they deserve for it. By doing so, we also make things quite a bit easier for the rest of the community to see the specific changes that were made for whatever it is you might be looking for. I'm going to pick on a few oem's on this one too... Take ASUS as an example. They package up their kernel source, and remove the .git folder... Now, we know they removed it, because they left the .gitignore & .mailmap files in their source dump. By them removing this, we can no longer see what changes were made to fix specific issues, or what drivers might have been changed, and why. It makes just about every OEM source "dump" I come across seem like they all have something to hide. Or they used someones work, and didn't want to pay them for it. It could be just about anything, but most of them are nefarious.

Yes, I know I can do a diff on the source filed to find out what has changed, but that's almost pointless, because of the lack of commit documentation and history. I refuse to work with anything that could be seen as stolen code as long as I can help it. And what I suggest is that we start contacting our OEM's as asking for a bit more transparency in their sources. I feel that it's not asking too much, especially if they have nothing to hide.
[BLISS ROMS Development] arifqur:
Seems to be the right way to go

---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------

Bump, Wink! Wink!
[BLISS ROMS Development] Manut38:
Hey,

I can't boot 10.1 rc1 aka 20180619 build on my Lenovo Yoga 3 Pro.

The boot process gets stuck after I select Android in grub and the boot text flashes. No bootanimation, straight into a black screen, no flashing cursor in the top left.

It works with nomodeset but it's waay to slow to be usable that way.

I had that issue before on a nightly build about a month ago, back then I just skipped that one and the next nightly was working again... But now I don't really know what to try.

Sorry if the solution is already here in this thread somewhere, I couldn't find anything.

Thanks for your ideas!
[BLISS ROMS Development] arifqur:
Try using an older build that is smaller in size maybe.
[BLISS ROMS Development] Manut38:
Will try that later today, but I'm curious, why would that help? Was there a recent big change to graphic drivers or something?
[BLISS ROMS Development] arifqur:
Yeah it ususally happens as its a work in progress
[BLISS ROMS Development] ohcurly:
Encryption and Root disable

Has anyone been successful in enabling encryption? When I enable it, the device just reboots (as it is supposed to do) but it doesn't encrypt. My Company Portal policies from my work need this in order to access company resources like OneDrive and email. This OS is the closest to what I need that I have found for my Surface Pro 4. I searched but couldn't find anything on this subject. I also need to disable root, and it seems to get reenabled on every boot.
[BLISS ROMS Development] electrikjesus:
Encryption from Android requires a working recovery that is capable of it... That we do not have just yet
[BLISS ROMS Development] youling257:
you need to know initrd.img，mount /dev/block/sdaX /mnt，mount /mnt/$SRC/system.img /android/system，mount /mnt/$SRC/data.img /android/data.

so you need encrypt /dev/block/sdaX，this is a linux partition encrypt problem，but how to make initrd.img auto mount this encrypted partition ?
[BLISS ROMS Development] astroganger:
Anyone can tell me how to turn on the surface pro 2017 when the screen got sleep, the power button does not work? I used the last iso.

Any help

Thanks
[BLISS ROMS Development] Rawwrius01:
Hey,

I have a question, is it possible to use the interface/launcher on a Android tablet?

Would love to use this on my Galaxy Tab.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[BLISS ROMS Development] arifqur:
Keep the power button pressed for ten seconds or more and the Surface would reboot.

For the next time go into Developer Options and tick "Stay On"