yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
When you say that it hangs on the boot logo, can you describe it a little more? Another thing you might try is going through the Android-x86 guide linked at the top of the second post. Might be helpful
[BLISS ROMS Development] FriendlyNeighborhoodShane:
Thanks man. Gonna try more. Think RMX is my pc specific problem.
[BLISS ROMS Development] FriendlyNeighborhoodShane:
Hey, [MENTION=928479]electrikjesus[/MENTION], I'm having problems with root. I extracted system.sfs but still supersu shows "supersu can't root, did you upgrade...."
[BLISS ROMS Development] electrikjesus:
is the system.sfs & system.img sitting in the same folder? If so, delete the system.sfs ;)
[BLISS ROMS Development] FriendlyNeighborhoodShane:
Done that. No luck. It's on usb, does that matter?
[BLISS ROMS Development] electrikjesus:
It shouldn't, but I have not tested that exact scenario. Maybe try and format the USB as ntfs first, then install and create the data.img. But that's stretching it...
[BLISS ROMS Development] FriendlyNeighborhoodShane:
will do, sir:svetius:
[BLISS ROMS Development] franzli:
Thanks for your reply! It just sits there without any other output - I disabled the quiet boot flag, but output stops once the boot logo starts. Oops, I guess the debug mode would give me more helpful output? Didn't think of that, next time! In the meanwhile it seems that the problem was installing on the c: drive. I made a small extra partition on the emmc and installing there leads to a successful boot.

Ultimately, I'd like to have most Android on the SD card, but installing there directly didn't work (apparently grub couldn't find it for booting).

I was thinking about creating an ext4 partition on the SD card, installing on the internal emmc as I just did but supplying the ext4 partition on the SD card to the DATA= boot flag somehow. Could anyone tell me if that's feasible or if there are any helpful hints? Otherwise I'll report back how that goes one I find the time to try.

---------- Post added at 09:44 PM ---------- Previous post was at 08:48 PM ----------

I've tried booting the latest bleeding edge 4.11 kernel on a baytrail device (the older Dell Venue 8 Pro 5830) and it seems to hang after loading the ath6k1 firmware, last two lines of output say mention it but no error message (last line says ath6k1: firmware supports: 64bit-rates...)

On the 4.9 kernel it has one additional line pertaining to ath6k1: Firmware lacks RSM-CAP-OVERRIDE, so HT (802.11n) is disabled.

Regarding the cherry trail Venue 8 Pro, there the version with 4.11 kernel boots until "Bluetooth: hci0: Applying Intel DDC parameters completed"and seems to hang there
[BLISS ROMS Development] FriendlyNeighborhoodShane:
[MENTION=928479]electrikjesus[/MENTION], I did this and made a new data.img, nothing happened. but when i again made a new data.img, it worked! (seems to have been a problem with the data.img) Thanks!:highfive:
[BLISS ROMS Development] jrk190:
Think there's a way to remap keys? Kinda curious to use on my Chromebook but my media keys are only usable as f1-0
[BLISS ROMS Development] SquaDrive:
hi, i've tried using ur latest bleeding edge build. My speaker, volume button, auto rotation and power button still didn't work properly. Do you include latest alsa driver in this build?

btw i'm using asus transformer 3 pro. skylake processor.
[BLISS ROMS Development] electrikjesus:
The different bleeding edge versions I have up all have different kernels, so thumb through them and see if there's possibly a better result from one of the others.
[BLISS ROMS Development] Miustone:
[MENTION=928479]electrikjesus[/MENTION] really excited to see Bliss x86 ! I loved the ROM in the early Days and it looks like it is even better now. I'm about to download and install that on My Laptop. I was thinking about how to get ZIPs flashed on the x86 Builds, and maybe i'd have an Idea...

Root is available? How does the Partition scheme looks like? Do We have a usual Android like scheme (Boot, System, Cache, Data)?

And what about the Main Filesystem? Could it be possible to use F2FS instead of EXT4? Asking just out of interest...

BR and Thanks for all the Work on Bliss!

EDIT: Got the Root Info from the First Page!
[BLISS ROMS Development] F4uzan:
The partition scheme is fairly different from normal Android device. You'll find /data and /system, I'm unsure about how /cache is set up though. As for boot, it doesn't need a separate partition since it's available in / as "vmlinuz" and "initrd.img".

Filesystem? Unless your bootloader supports booting to F2FS out of the box, it's pretty much useless to switch to F2FS. You /can/ dump the whole installation to an F2FS partition, but I doubt it'll boot. Best to stick with EXT4.

And ps: You aren't limited to simply EXT4 and F2FS (F2FS being limited for flash-storage like NAND chips), there's plenty more on a full-fledged computer installation.

For remapping, you can try "External Keyboard Helper Pro" or "Miltilanguage Keys Remapper", they're both in Play Store, one is paid and the other is free though lacks some feature. I haven't personally tried it on my Chromebook, though.
[BLISS ROMS Development] Stickypinkyfinger:
Thanks for the great rom. I just installed it on my pc. I am having 1 issue though. Bliss is saying its using 118gb out of 119gb plus will only let me install 3 apk files before it says its full. Is there any fix as the install is sitting inside a 50gb partition?

---------- Post added at 07:10 AM ---------- Previous post was at 06:35 AM ----------

Figured it out. Instead of installing Bliss inside an ext4 format, i installed in NTFS and set data folder to 45gb.

Plenty of space now for everything to sit in.
[BLISS ROMS Development] barneycat74:
Hello I have a problem with x86 builds when installing to hard disk using ext4 file system. Everything works on my lenovo x230 thinkpad, but the harddisk is constantly caching, even when idle the hard disk activity never stops. The only way I have been able to stop this is to format the hard disk to ext2, but using ext2 isn't recommended for newer android x86 builds. Does anyone have any idea as to why this might be happening? Thanks.
[BLISS ROMS Development] shanx_verma:
Which dell venue and variant do you have? xD
[BLISS ROMS Development] electrikjesus:
I have seen this issue on some hardware, but not all. Best way to solve it I have found is to format as NTFS. I am still hunting down why this and other ext4 issues are happening though.
[BLISS ROMS Development] barneycat74:
Ok thanks will give this a try. When formatting to NTFS the installer wants to know how much space to allocate to the data file, it defaults to 512mb. Do I need to change this? (hard drive size is 500GB)

I thought perhaps the issue with ext4 maybe due to journalling which is turned on by default. I tried to disable this using the terminal in gparted but although it worked it didn't seem to make much difference to the CPU activity. I didn't get this problem with ext2 though, which as I understand has no journalling feature, so I thought that might be the issue with ext4.
[BLISS ROMS Development] franzli:
I haven't been able to find a version that boots on the Del Venue 8 Pro 5830 yet. I don't have a lot of time to look into this at the moment, so maybe there's an easy fix? If/when I'll find more time, I'll see if I can do some troubleshooting - any hints very welcome, of course. You need to give the nomodeset kernel parameter for it to boot at least into the boot animation, but it hangs there somewhere, I gave some reports earlier in this thread.

As mentioned in an earlier post, the newer DV8P 5855 boots on the 4.9 kernel. I haven't gotten to properly test my installation yet, but had the impression that it rebooted on its own occasionally.
[BLISS ROMS Development] electrikjesus:
It could also be that as well. I do remember trying to fix a few issues with journaling entries earlier on in the project. It might be time to revisit that.
[BLISS ROMS Development] electrikjesus:
Update - 04.18.17 - new bleeding edge updates, and download server!

I am uploading a couple new bleeding edge builds to our download server right now. From this point forward, we will be using the Bliss server to host only the CURRENT release for that branch, all other builds will still be archived on AFH, but the Bliss server will get the new builds first.

Updates to these builds include Kernel-4.11rc6 (KMS Enabled, other patches too), A.R.I.S.E. Sound Systems in now included! (Thanks to Arise team for permissions), Taskbar v3.3, Theme "Safe Mode" (hold VolUp while boot for theme recovery - http://review.blissroms.com:8081/#/c/1618/ ), updates to mesa, and a bunch more I likely forgot about by now.

Downloads for Bliss-x86 - Bleeding Edge: https://downloads.blissroms.com/Bliss/Alpha/x86/bleeding_edge/
[BLISS ROMS Development] electrikjesus:
It looks like you are trying to install over without hitting the clean up button
[BLISS ROMS Development] rajnallan:
Hey,

No I did clean up. I also formatted the partition, rebooted and tried again. This did not happen before. I had installed the earlier versionbs many times the same way and I had no issues.

Raj
[BLISS ROMS Development] electrikjesus:
It looks like it errored on creating the uefi entry. I'd suggest you remove that too
[BLISS ROMS Development] rajnallan:
Hey Thanks. I using Explorer++ i made sure there no entries in the boot that was created by android installer. Can you help me with the process in removing the entries and errors.
[BLISS ROMS Development] electrikjesus:
Find me on Hangouts or Telegram, and I will see what I can do
[BLISS ROMS Development] rajnallan:
Thanks. What is your hangouts ID? ZE=1]---------- Post added at 06:58 PM ---------- Previous post was at 06:50 PM ----------[/SIZE]

[/COLOR]

I have sent you an invite on hangouts. I found out your id from Google+ and sent you an invite through hangouts
[BLISS ROMS Development] unterwelt:
Hello on my teclast x98 pro the Display is upside Down... I don't Know What i should so (Touchscreen is normal so its Hard to Use...)
[BLISS ROMS Development] electrikjesus:
I think I remember some others having this issue on the Android-x86 Google Groups... Here, see what you find: https://groups.google.com/forum/#!searchin/android-x86/Invert$20touchscreen|sort:relevance Or search for your model in there too.
[BLISS ROMS Development] Miustone:
Anyone tried FlashFire from chainfire? It should be able to flash ZIPs from within the System if Root is available. How about that?
[BLISS ROMS Development] ElfinJNoty:
I tested it months ago and was unsuccessful. Tried with Xposed and some TBO apps.

Didn't work
[BLISS ROMS Development] Miustone:
But it should... As long as we have no Custom Recovery for x86 We just have FlashFire. There can be many Reasons for it to not Work Correctly. But We should find out why, otherwise is there no way to flash ANYTHING. Which will be the main Reason for a lot of People to use it not... (Including Me).

What about real Recoveries ? Are there none from the Zenfones as example? They are also running x86 so it could be basically possible to Port a Recovery from them to our PCs right? I'm really looking forward to Android/Bliss on x86 but there are some small things left like it seems...

I really would like to help somehow! Let's see...
[BLISS ROMS Development] electrikjesus:
See, that's the issue, many flash able zips use commands from recovery partition to flash, but the partitions are different with Android-x86 variants. Any of the recoveries I have found for x86 devices are all still for EMMC and not UEFI or legacy boot schemes. The kinda recovery included with Bliss-x86 at the moment, only drops to system shell, and accepts a couple base commands, but nothing cool enough to use ATM.
[BLISS ROMS Development] hgblob:
Audio and Alarm on Surface 3

Hi,

First of all thanks for all your hard work, my Surface 3 PRO is running almost perfect. However I have 2 annoying issues:

Running the latest stable build:

Audio recording doesn't work at all: using the google voice search or even the audio recorder gets the device audio in a blocked state. After trying to record audio, neither input nor audio output work on the device at all until I reboot.

Setting any kind of alarm in application alarm will not wakeup the device. The alarm will sound when I manually wake up the device.

Any help would be appreciated.

Blob
[BLISS ROMS Development] Miustone:
Thanks for the explanation!

Someone should really work on that, i would do it but i've no Plan how to create a Recovery, or even how to include it into the x86 Project.

That's why i was putting My Hopes into FlashFire. Since it's a Apk which does Emulate a Recovery it should just run fine for us. The Partitions could be a Problem but there is some kind of detecting within the App. Maybe can [MENTION=631273]Chainfire[/MENTION] patch the App for Us to work...? Would be a Big Thing at all...

:fingers-crossed:
[BLISS ROMS Development] electrikjesus:
The mic issues on the SP3 is a known issue. I don't know how to fix it yet. The sleep issue is also something you'll find common across all Android-x86 variants, as PC's use a hybernate/sleep method that is a bit different than Androids sleep method
[BLISS ROMS Development] t3chg33k:
I used the vanilla x86 builds on my Dell Venue 11 Pro 7140 (Core M) for a long time and always had the issue of sound not working out of the box. However, unmuting SP0 would get the sound working immediately. Presently, I am using the latest stable build of Bliss since the bleeding edge is nigh unusable on my device.

I have been trying out a few things on account of which I have reinstalled the same stable build multiple times. The odd thing is that while the sound works out of the box on one installation, it doesn't on the next. Even unmuting nearly all the alsa mixer controls has no impact and I have no sound at all. Odder still, with the same installation, while I had sound with the Android Installer UEFI, pointing Grub2Win to the same installation with the same configuration resulted in no sound at all.

I am simply out of ideas now in terms of getting the sound working.
[BLISS ROMS Development] electrikjesus:
Maybe you are seeing a pattern where there is none, or the other way around... Have you tried to boot Bliss from a powered off State each time? Or have you rebooted? Cause it almost looks like the sound controller isn't being shutdown properly
[BLISS ROMS Development] t3chg33k:
Hey, thanks. You seem to be right on the sound controller not shutting down properly. I just did a complete Power Off and then booted to the Android installation and got the sound back. However, prior to it, I had done 3 fresh installations without any success. So perhaps it is also a case of the controller not initiating properly as well?

Anyway glad to have the sound working for now. However since the audio doesn't switch on plugging in headphones, I was hoping to connect bluetooth headphones for private listening. Unfortunately, bluetooth crashes on initiation as well. I guess I can't ask for everything.
[BLISS ROMS Development] electrikjesus:
Update - 04-25-17 - Bleeding Edge

New builds for Bliss-x86 32bit & 64bit!! Changes include kernel-4.11rc7, auto mounting external drives and CD drives, changes to how f2fs is auto-mounted too. Arise included, update to Taskbar 3.3.1, and more, but I'm ADHD-AF

https://downloads.blissroms.com/Bliss/Official/x86/

I have also moved all obsolete builds into the archived folders on AFH. Check the OP for those links.
[BLISS ROMS Development] guyz_ahead:
In the latest build i am getting insufficient storage error and wifi not detecting. Its not turning on. Just could boot into bliss rom successfully. Anyfix for wifi? I followed all steps carefully. EDIT- Storage is fine now. WIFI still not detected. Using usb wifi receiver. help asap
[BLISS ROMS Development] pitt93:
On asus t100ha audio, rotation, and sd card slot are not working....Bt and camera not tested, other thing works great...very good job!
[BLISS ROMS Development] electrikjesus:
I would love a little more info about this "USB WiFi receiver"

I have had to state this many times already, so I'm likely going to end up putting it in the OP... Before saying sound is not working, please make sure you test from a completely powered off state. 99% of the time, it is not working due to Windows or another OS not shutting down the hardware properly.
[BLISS ROMS Development] pitt93:
i've tried againg, i've tested as the istruction but isn't working both with built in speaker and external speaker (3,5mm jack)

Maybe a cherry trail issue
[BLISS ROMS Development] electrikjesus:
That could be. I will be working on a few updates to the kernels and firmware today, so I might be able to figure out the issue... hopefully
[BLISS ROMS Development] guyz_ahead:
Its lexus usb wifi receiver for pc. Not supported?
[BLISS ROMS Development] electrikjesus:
I can't even find it using Google... So, my question is, how does it work in Linux? Do you have to compile your own drivers for it?
[BLISS ROMS Development] electrikjesus:
Hello Blissers!! I'm uploading a couple new bleeding edge builds to the Bliss downloads server. Updates include:

Additional CD-ROM support

Added qemu-android script for Android-x86 project for RPM installs (https://groups.google.com/forum/m/#!topic/android-x86/NuXzAp5DBZU)

Updated firmware with new linux firmware sources (there will be releases using this, ubuntu's firmware and the stock Android-x86 firmware archive eventually)

WiFi issues fixed for many devices

probably more, but I forgot...

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] lollyjay:
Can we upgrade?
[BLISS ROMS Development] electrikjesus:
I was able to on half my test machines. Just replaced the system.img, kernel, ramdisk, initrd, and it updated just fine. On a couple of the machines though, I had some gapps issues, so I had to wipe data.img and start fresh with those.
[BLISS ROMS Development] lollyjay:
Thanks I did upgrade but still no working wifi. It works for me on the Stable build but not on any of the Bleeding Edge builds
[BLISS ROMS Development] electrikjesus:
I'm working on pushing out a few stable & EDU builds using kernel-4.4 right now. SHould be tested and uploaded by the end of the weekend.
[BLISS ROMS Development] blubba83:
Hi ... Can someone help please ... In 64 bit CPU all android x86 32 bit versions run fine but 64 bit says opcode error. I made a screenshot Form CPU info and boot error. System will loop before bootlogo.
[BLISS ROMS Development] electrikjesus:
It looks like it is seeing your Pentium dual-core cpu as a 32bit cpu. These CPU's came in a few flavors, 32bit & 64bit. I don't think it supports the 64bit architecture we use with today's processors though, which might be what's causing your issues. Stick with the 32bit builds I say ;)

https://en.m.wikipedia.org/wiki/Pentium_Dual-Core
[BLISS ROMS Development] blubba83:
But Win 7 64 and win 10 64 run fine. So it is a real 64 bit CPU. How to get a more Detail error log at boot, i want to know which opcode ist wrong ? Can it be that Android x86 64 kernel identifys this CPU wrong ?

I have read a while and found out that it seems to be a Compiler Problem when it uses sse4 or sse5, is it possible to say the Compiler to dont use these.

Found this: it Seen to be possible to emulate sse4 on Intel

https://sourceforge.net/p/android-x86/misc/3/
[BLISS ROMS Development] electrikjesus:
Feel free to PM me if there is anything in the source that might need to change.
[BLISS ROMS Development] Mazen Yasser:
Is There a Build for 64x Based Pc's ?

and , can it be used along other OS's ..

im using Windows 10 Pro alongside Ubuntu 14.04 .. Can i install it with them as the 3rd OS running with them .. or i have to remove one ?

Thanks in advance for your Efforts :)
[BLISS ROMS Development] franzli:
Short answer, yes, there is an x64 variant and you should be able to multiboot using grub. Have a look at OP for details.
[BLISS ROMS Development] franzli:
Booting of the latest x64 bleeding edge hangs on Dell Venue 8 Pro (5830, baytrail), apparently while/after trying to initialise the WiFi module?

The last two lines when booting in debug mode concern ath6kl.

I'm using the nomodeset boot parameter otherwise there's no graphics output at all, is there anything else one could try?

Ps: oops, sorry wing report, it seems I got confused by previous attempts. If I bit without debug mode, it eventually gets to the start screen, just takes quite a while! Great, I'm curious to see how it performs on baytrail!
[BLISS ROMS Development] wizmart:
WiFi not working for me, only Ethernet on a HP elitebook 8470p, nice rom otherwise, root and Google apps. Latest bleeding edge

Oops, k didn't see the one from 27, I gonna try
[BLISS ROMS Development] pipyakas:
Got the rom running on my asus k451ln, only issues are bluetooth not working and I cant shutdown/restart the laptop from within android.

Everything else work fine atm, I can even change the screen's brightness which I could never do in linux without the "acpi_osi=" flag
[BLISS ROMS Development] rajnallan:
Good morning. How are you? The latest Bleeding edge is running extremely well except for the well know issue of wifi. I am waiting for the newer build to upgrade to get rid of the wifi issue. Otherwise the build is very good and running extremely well. I may have some video issues stuttering sometimes...not related to internt which is very good, stable and fast. Thanks and appreciate the great efforts.

With my surface pro 3 i have the issue with the installer and I still have to use the remix Installer and then place the Bliss files in the partition folder. I hope you had some time to look at the installer as we discussed. Thanks
[BLISS ROMS Development] hgblob:
I took matter in my own hands and fixed the Mic issue. I posted the patch on android-x86 but my membership wasn't approved yet.

This patch for hardware/libaudio:

diff --git a/audio_hw.c b/audio_hw.c
index 7c2406f..b7f8887 100644
--- a/audio_hw.c
+++ b/audio_hw.c
@@ -183,6 +183,7 @@ struct snd_pcm_info *select_card(unsigned int device, unsigned int flags)
static struct snd_pcm_info *cached_info[4];
struct snd_pcm_info *info;
int d = !!(flags & PCM_IN);
+ char e = d ? 'c' : 'p';
if (!cached_info[d] && !cached_info[d + 2]) {
struct dirent **namelist;
char path[PATH_MAX] = "/dev/snd/";
@@ -191,7 +192,7 @@ struct snd_pcm_info *select_card(unsigned int device, unsigned int flags)
int i, fd;
for (i = 0; i < n; i++) {
struct dirent *de = namelist[i];
- if (!strncmp(de->d_name, "pcmC", 4)) {
+ if (!strncmp(de->d_name, "pcmC", 4) && de->d_name[strlen(de->d_name) - 1] == e) {
strcpy(path + 9, de->d_name);
if ((fd = open(path, O_RDWR)) >= 0) {
info = malloc(sizeof(*info));
--
[BLISS ROMS Development] electrikjesus:
If you want to submit that patch to blissroms-x86/hardware-libaudio via GitHub, I can apply that to this next test build.
[BLISS ROMS Development] hgblob:
done. I only did superficial testing but I guess there is not that much to break :)
[BLISS ROMS Development] electrikjesus:
I started on it based on what Jide has for their installer source, but life came between me and my work, then after a few squirrels, I completely forgot.
[BLISS ROMS Development] rajnallan:
Thanks for the update. It will a lot easier for everyone if the installer issue is sorted out. I have tried Remix OS on Desktop. laptop and tablet. No issues at all. However , I am able to install Bliss using remix installer at the moment. Whenever, you upload a new build I install it as a new set up. But now I intend to update the files.

Also, the WiFi goes off if I keep the system idle for sometime. If I am continuously using the system then WiFi is stable.

Thanks
[BLISS ROMS Development] electrikjesus:
Looks like everything tests out OK, so I merged your changes. Thank you :) Now if we can figure out whats going on with ambient noise on these mics, we'll be all good!