Android X86 Club

[lexluthermiester]

I have wait for 1-2 hours for first stage setup runtimes, before then it turned off by itself, when I turn it on, still the same process, before then it turned off again.

Which version are you using?

EDIT:
This is the one I've been playing around with and it seems the more stable version;

https://sourceforge.net/projects/blissos-dev/files/Android-Generic/PC/lineage/LineageOS_v17.1-android_x86_64-202008292133_k-k4.19.122-ax86-ga-rmi_m-lineage-17.1_dgc-q-x86-generic_ld-2.4.102-q-x86_dg-lineage-17.1_dh-lineage-17.1_mg-lineage-17.1_gms_cros-hd_cros-wv.iso/download

 

[bpm]

a bit oft to know my problem and what i tried before i found this board.

i want to run sky go (or sky x) on my chromebook (https://www.amazon.de/gp/product/B08DBDFL9V/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1)

this was working until december. but sky decided to prevent the app to run on chromeOS. since then i am struggling around.
with much searching i was able to get it running on my rooted phone again (even magisk hide was not enought. but with app manager it is possible)

on my chromebook (everything is tried with qemukvm) i tried this variants:
win 10 => not enought power. got it running but only for a few minutes until it stopped
win 7 => aureo theme needed => not possible to get it running within qemu
win 8.1 => got it running but just a few more minutes then with windows 10
===========================================================
here i changed the way to go, got it running on the rooted phone and thought this have to be possible with android x86 in qemu too.

but it is really hard to get startet.
tried bliss os with gearbox. but not able to install magisk. got "no internet connection" when i hit install magisk in gearbox (if bliss is booted the intrenet within is working fine)

tried a few other android x86 forks but always stuck on any other point.
in some it installes fine, but no input was recogniced on the gui.
other does not even install (error installing grub)

i dont really have linux know-how and so i have no experience with qemu too.
but i am a java developer since 20 years and so i thinik i have a basic it-knowhow ;-)

could anybody show me the right direction?
in best case an android-x86 (or fork) iso with magisk preinstalled.

not possible for me to find something like this by google.

 

[lexluthermiester]

could anybody show me the right direction?

I would try the following if you can get it to install;

Release CM-x86-14.1-r5 | Android-x86

www.android-x86.org

The is latest release of the AndroidX86 fork of LineageOS. It's my daily driver for a Dell E6230 and performs perfectly, so that HP you linked should run smoothly if it'll install.
(Sorry for the delayed response, I was never notified of your post or would have offered some help, maybe this will still be of assistance? )

@Everyone
AndroidX86 has two new versions currently

The above mentioned 14.1R5 release of LineageOS and 8.1R6.

Release 8.1-r6 | Android-x86

www.android-x86.org

I've tested both and the LineageOS release seems the more stable of the two across multiple platforms(laptop/desktop).

 

[abronola]

Hi,
I just joined hoping I could get some help here regarding my HP Pro Tablet 601 G1.
I'm trying to run android-x86 on it. I tried all the CM-x86 builds already and the regular Android-x86 builds upto the latest. The major issue I have is the slowness. All the CM builds and Android-x86 version 7 and up have the same slowness issue. The only version that works smoothly is the Android-x86-6.0-r3 (it runs so very snappy no lags at all). However, the power buttons, the brightness, the audio/volumes doesn't work and the Google play keep crashing. So, I wonder if the builds slowness issue on the recent builds is something todo with the GPU manipulation feature and if it is how do we disable it?

By the way, I have these in my grub.cfg. without nomodeset xforcevesa, it won't boot. (that's not needed though on Android 6).

linux /Android/kernel quiet root=/dev/ram0 androidboot.selinux=permissive nomodeset xforcevesa DATA=
initrd /Android/initrd.img

Thanks for the help in advance.

https://support.hp.com/us-en/document/c04718256​

 

[lexluthermiester]

Hi,
I just joined hoping I could get some help here regarding my HP Pro Tablet 601 G1.
I'm trying to run android-x86 on it. I tried all the CM-x86 builds already and the regular Android-x86 builds upto the latest. The major issue I have is the slowness. All the CM builds and Android-x86 version 7 and up have the same slowness issue. The only version that works smoothly is the Android-x86-6.0-r3 (it runs so very snappy no lags at all). However, the power buttons, the brightness, the audio/volumes doesn't work and the Google play keep crashing. So, I wonder if the builds slowness issue on the recent builds is something todo with the GPU manipulation feature and if it is how do we disable it?

By the way, I have these in my grub.cfg. without nomodeset xforcevesa, it won't boot. (that's not needed though on Android 6).

linux /Android/kernel quiet root=/dev/ram0 androidboot.selinux=permissive nomodeset xforcevesa DATA=
initrd /Android/initrd.img

Thanks for the help in advance.

https://support.hp.com/us-en/document/c04718256​

Have you tried 4.4R5? It is possible that the tablet in question is just to slow to run the latest versions of AndroidX86 well.

BTW, welcome to TPU!

 

[lexluthermiester]

See updates in the OP! AndroidX86 is on the move!!

 

[iameatingjam]

Very interesting. I did not know this existed. And I'm amazed by such high compatibility. I mean I knew you could emulate android pretty competently. But to have it run native like that I imagine would be a world's difference in performance.... it must be if you guys are running it on such old hardware.

So is there an element of emulation still there for apps assuming that they are running on arm or how does that work?

 

[lexluthermiester]

But to have it run native like that I imagine would be a world's difference in performance.... it must be if you guys are running it on such old hardware.

The performance is great! Runs everything I care about very well. Granted, some games & apps from the store don't run, but that is a minor quibble given that most do. On more modern hardware, the performance is better than ANYTHING ARM has to offer.

For example, on an i9-9800X with a GTX 1070ti and 32GB of RAM, if an app/game will run, it'll run freaky fast.

So is there an element of emulation still there for apps assuming that they are running on arm or how does that work?

Nope, no emulation. Remember, Android is Linux with a custom shell. Google creates the code to be compiled and plugging an X86/X64 kernel into it is not so difficult. The difficulty comes with making sure the software can seamlessly interact with the hardware presented, and it's getting better all the time..

 

[lexluthermiester]

Update, a new version of BlissOS 14 is out!
14.10.3
Link as always to the OpenGApps version;

BlissOS-x86 - Browse /Official/BlissOS14/OpenGApps/Generic at SourceForge.net

An Open Source OS, based on Android for PC's & Tablets

sourceforge.net

This ISO can be used for either a fresh install or to upgrade a standing install. To upgrade choose not to format the drive and the installer will detect the current install and ask if you want to upgrade.
Works like a charm, fixes a few bugs and one glitch that cause a soft-restart.

 

[HMTheBoy154]

Hi, thanks for the shout out, glad that you like what we're doing here . However, there are some edit I'd like the OP to have:
- Instead of listing SourceForge link of each version, please give the link to the project site. The website explains what's inside of each builds (14/15/16/Zenith & Generic/Go/Surface) which can avoid confusion for the newcomers.
- Zenith different from 16 is that Zenith will use latest stable Linux kernel instead of LTS kernel like the other builds. Also it will be based on the latest BlissOS version too so if we release BlissOS 17 based on Android 14, it will be on 17.
- Our group (or more like an organization) is called BlissLabs
- For CPU, it's not that generally any Intel CPU is supported and only ZEN based AMD CPUs are supported. BlissOS require CPUs that are on x86_64-v2 Microarchitecture level. For more info, you can check out the Documentation
- For GPU, we do support AMD integrated graphics.... and that thing is better than Nvidia right now imo. Nvidia GPUs got the poorest support as it's currently using the nouveau driver. Things might get better in the future with the Turing and newer series, but currently I'd recommend using Intel or AMD graphics right now (except Intel dGPU, we haven't tested that yet).

 

[lexluthermiester]

Hi, thanks for the shout out, glad that you like what we're doing here .

Cool. Welcome to TPU and this club!

However, there are some edit I'd like the OP to have:

Not a great way to start out though.. I'll try not to take it personally. You'll notice that the name of this thread is called the "Android X86 Club", not the BlissOS Club. You folks were not the first to do Android on X86/X64 hardware and will not be the last. The OP will continue to be formatted as I see fit. You folks are welcome to participate and contribute. You are not welcome to dictate terms.

- Instead of listing SourceForge link of each version, please give the link to the project site. The website explains what's inside of each builds (14/15/16/Zenith & Generic/Go/Surface) which can avoid confusion for the newcomers.

Going to continue linking directly to the images I personally test as I don't want to send visitors of this thread off looking for something that I didn't recommend/test myself. It's just how it's going to go. That said, won't be discouraging anyone from visiting that page either. I do like how clean the new page format is, very different from the way it was last time I visited. Much improved!

- Zenith different from 16 is that Zenith will use latest stable Linux kernel instead of LTS kernel like the other builds. Also it will be based on the latest BlissOS version too so if we release BlissOS 17 based on Android 14, it will be on 17.

That is surprisingly good info to know. I figured it was something to do with the kernel, but wasn't sure and didn't want to comment information that might be incorrect.

- Our group (or more like an organization) is called BlissLabs

Also good to know.

- For CPU, it's not that generally any Intel CPU is supported and only ZEN based AMD CPUs are supported. BlissOS require CPUs that are on x86_64-v2 Microarchitecture level.

And again, good info to know!

For more info, you can check out the Documentation

Nice, very handy. Had no idea it was even there. As mentioned above, it's been a while since I've been to the main Bliss website. It used to be a very disjointed mess. For that reason, I'd been avoiding it for a few years in favor of the SourceForge site and the AndroidFileHost.com pages. Much better now!

- For GPU, we do support AMD integrated graphics.... and that thing is better than Nvidia right now imo. Nvidia GPUs got the poorest support as it's currently using the nouveau driver. Things might get better in the future with the Turing and newer series, but currently I'd recommend using Intel or AMD graphics right now (except Intel dGPU, we haven't tested that yet).

My experience has been different. I've have not issues with Intel and NVidia and headaches with Radeon. Might still be some work to do.

The Nouveau drivers have been trouble free and have worked on nearly everything I've thrown at them. Quadro's are hit & miss, but the main Geforce lineup from the 400's on up have been perfect, the only exception being Vulkan support, but that's a known issue.

The MESA drivers have likewise been trouble free. Not one Intel model has failed to provide good performance. Like the Geforce mentioned above, Vulkan support is not there, but that is also not unexpected.

The few Radeon GPU's I have don't seem to work to well or very stable, so I generally avoid them for AndroidX86 testing. Will have to try again soon as your statement has intrigued me.

 

[HMTheBoy154]

Not a great way to start out though.. I'll try not to take it personally. You'll notice that the name of this thread is called the "Android X86 Club", not the BlissOS Club. You folks were not the first to do Android on X86/X64 hardware and will not be the last. The OP will continue to be formatted as I see fit. You folks are welcome to participate and contribute. You are not welcome to dictate terms.

Sorry what I mean is that I would like to edit the part that is related to BlissOS only, not the whole OP. I don't have the intention of dictating any terms, if my English is hard to understand then I'd like to apology that too.

My experience has been different. I've have not issues with Intel and NVidia and headaches with Radeon. Might still be some work to do.

The Nouveau drivers have been trouble free and have worked on nearly everything I've thrown at them. Quadro's are hit & miss, but the main Geforce lineup from the 400's on up have been perfect, the only exception being Vulkan support, but that's a known issue.

The MESA drivers have likewise been trouble free. Not one Intel model has failed to provide good performance. Like the Geforce mentioned above, Vulkan support is not there, but that is also not unexpected.

The few Radeon GPU's I have don't seem to work to well or very stable, so I generally avoid them for AndroidX86 testing. Will have to try again soon as your statement has intrigued me.

May I ask what the list of GPUs you've tested ? You mentioned Gerforce 400+ which mean you have a card in Fermi family ? I don't have an Nvidia card that was that old though, I only have an GTX 1660S to test the GSP Firmware so hearing this is interersting.

As for the Radeon, I would like to hear about those too. It's pretty surprising that they are not as reliable as running on an Nvidia GPU with nouveau.

 

[lexluthermiester]

By way of an edit The newest version of BlissOS 14(14.10.3 - 2024-9-16) is up and fixes a problem with the KernelSU app and settings, link follows;

https://sourceforge.net/projects/blissos-x86/files/Official/BlissOS14/OpenGApps/Generic/Bliss-v14.10.3-x86_64-OFFICIAL-opengapps-20240916.iso/download

Sorry what I mean is that I would like to edit the part that is related to BlissOS only, not the whole OP. I don't have the intention of dictating any terms, if my English is hard to understand then I'd like to apology that too.

Fair enough. I'll put it in the OP for reference.

I'll respond to your other comments later as you caught me on a busy day.

 

[lexluthermiester]

You mentioned Gerforce 400+ which mean you have a card in Fermi family ? I don't have an Nvidia card that was that old though, I only have an GTX 1660S to test

I have both a GTX460-1GB and a GTX560-2GB and both worked well with both AndroidX86 CM14.1R5 and BlissOS 11.14 a few years ago. The Nouveau drivers haven't changed a lot since then(that I know of, feel to correct). I most recently tested a GTX960, GTX980, GTX1060 and GTX1070ti. I have RTX 2000 and RTX 3000 cards to test with but haven't yet. Wouldn't expect any issues as long as the newest versions of the drivers are used. For mobile, I currently have two laptops, one with a GT525 and the other with a GTX1050, no issues.

As for the Radeon, I would like to hear about those too.

As far as Radeons, I have a limited number of cards to test with. Currently on hand I have an R5-240, R7-250x, R7-450 and an RX-560. Only the 240 gave any issues, would not run anything 3D at all. It work perfectly in both Windows XP and 7. For mobile I only have a Dell laptop with an HD7650M and no version of Androidx86(32 or 64 bit) or BlissOS(again 32 & 64 bit) will work. Just basic drivers and no 3D support.

 

[lexluthermiester]

By way of an update, Bliss14(20241012) and Bliss16(20241011) were updated mid-month a few weeks ago. Sorry for not posting sooner. From what I've read, there are some fixes, nothing major but handy and also a few security patches.
You can get each from the BlissLabs website or the SourceForge links below;

BlissLabs

A non-profit org that develops open source software for the community

blisslabs.org

BlissOS-x86 - Browse /Official/BlissOS16/Gapps/Generic at SourceForge.net

An Open Source OS, based on Android for PC's & Tablets

sourceforge.net

BlissOS-x86 - Browse /Official/BlissOS14/OpenGApps/Generic at SourceForge.net

An Open Source OS, based on Android for PC's & Tablets

sourceforge.net

Bliss15 was also updated(20241012) for those using it;

BlissOS-x86 - Browse /Official/BlissOS15/Gapps/Generic at SourceForge.net

An Open Source OS, based on Android for PC's & Tablets

sourceforge.net

Remember folks, these ISO's can update an existing install. During setup when asked if you want to format the drive, say no and the installer will see and ask if you want to update it, then say yes.
This applies only to those who did not setup up OTA updates during the first install. If you did, look for updates in the normal way through the settings app.

 

[RyzenMaster.sys]

Hello. I finally got fed up with OpenElec+Kodi not working as I wanted on my HTPC, so I installed Android X86. I use my HTPC to watch youtube, play music in tidal, play discs, and to play music from my collection of ripped CDs stored on my NAS... Some of that stuff a standard smart tv is usually too limited to support. I remembered this project from experiments with it in years prior and installed it here to see if it suits my needs

My HTPC is a slim tower I got for free, essentially out of a recycling pile, with a couple parts out of my own junk pile to spruce it up a bit. i3 4170, Intel GFX, 4GB, 128 SSD, some cheap Realtek wifi dongle. The PC is operating smoothly in Android X86, and the UI is perfect for a HTPC, super easy to use. It is doing everything I want, with a major exception. I can't get the optical drive to work.

I notice in the initial post in this thread that optical drives can be utilized using mounting commands in the terminal. Any more details on what commands I need to use to accomplish this? Fdisk does not show any disks for some reason. Android sees the device and says "This device doesn't support the HL-DT-ST CD/DVD Drive" and tells me I need to set it up. But when I click set up, settings stops and crashes... This is a standard internal sata drive, but I also tried connecting it via a SATA to USB adapter so it would show up as an OTG device, but that yields the same results.

I have probably a dozen other SATA optical drives I could try if this specific one is a problem. Even some blue ray ones... does Android X86 do blue rays?

I guess after reading i should probably install bliss OS. I know the standard Android x86 is basically EOL, and android 9 is old, but figured id give it a go anyhow.

 

[lexluthermiester]

I notice in the initial post in this thread that optical drives can be utilized using mounting commands in the terminal. Any more details on what commands I need to use to accomplish this? Fdisk does not show any disks for some reason. Android sees the device and says "This device doesn't support the HL-DT-ST CD/DVD Drive" and tells me I need to set it up. But when I click set up, settings stops and crashes... This is a standard internal sata drive, but I also tried connecting it via a SATA to USB adapter so it would show up as an OTG device, but that yields the same results.

Mounting an optical drive in Android work the same way as mounting in Linux(because Android is Linux).

How to mount cdrom in Linux

These days, CDs and DVDs are becoming less popular, in favor of flash drives and other convenient, portable media. However, you still may come across them every once in a while, and if your computer…

linuxconfig.org

You need a terminal emulator with SU(root) and a video player that can mount the DVDs you want to play.

does Android X86 do blue rays?

Not that I know of.

 

[RyzenMaster.sys]

Mounting an optical drive in Android work the same way as mounting in Linux(because Android is Linux).

How to mount cdrom in Linux

These days, CDs and DVDs are becoming less popular, in favor of flash drives and other convenient, portable media. However, you still may come across them every once in a while, and if your computer…

linuxconfig.org

You need a terminal emulator with SU(root) and a video player that can mount the DVDs you want to play.


Not that I know of.

Just using VLC for playback. Any clue how I can get a terminal emu with root permissions?

I'm working in blissos 15.9 now. I used KernalSU to grant termux root access but when I try and use SU it just says "no su program is installed on this device" implying it's not rooted. Kernal su also says there's a new version available but refuses to actually do anything but open and instantly close a browser when I click that.

I got kernal su updated by just clicking download before the browser closed and running the apk. But still termux says it has no su permission

 

[lexluthermiester]

Any clue how I can get a terminal emu with root permissions?

Google Play store, Termux is the one BlissOS16 comes with not sure about BlissOS15. Then grant it SU in the KernelSU app.

I'm working in blissos 15.9 now. I used KernalSU to grant termux root access but when I try and use SU it just says "no su program is installed on this device" implying it's not rooted. Kernal su also says there's a new version available but refuses to actually do anything but open and instantly close a browser when I click that.

I got kernal su updated by just clicking download before the browser closed and running the apk. But still termux says it has no su permission

Thant should work. Can't imagine what the problem is..

 

[RyzenMaster.sys]

KSU bug in granting root for apps on BlissOS · Issue #2113 · tiann/KernelSU

Please check before submitting an issue I have searched the issues and haven't found anything relevant I will upload bugreport file in KernelSU Manager - Settings - Report log I know how to reprodu...

github.com

Must be a known issue. I was able to workaround it using the fix there in grub, but now that I have superuser it's not seeing the optical.

This is so weird. The android gui sees it here

But terminal doesn't... I may grab a different optical drive.

 

[lexluthermiester]

KSU bug in granting root for apps on BlissOS · Issue #2113 · tiann/KernelSU

Please check before submitting an issue I have searched the issues and haven't found anything relevant I will upload bugreport file in KernelSU Manager - Settings - Report log I know how to reprodu...

github.com

Must be a known issue. I was able to workaround it using the fix there in grub, but now that I have superuser it's not seeing the optical. View attachment 377528
This is so weird. The android gui sees it here View attachment 377529
But terminal doesn't... I may grab a different optical drive.

Have you tried BlissOS16?

 

[RyzenMaster.sys]

Interesting. I can see and mount a data CD. In this case a need for speed game. See it in files just as you'd expect.

But it just doesn't know how to handle audio or blank discs. Errors when I try and mount them. I may try a DVD too.

Have you tried BlissOS16?

I may. So you have CDs/DVDs working in BlissOS16? I just picked 15 because it should be stabler.

 

[lexluthermiester]

Interesting. I can see and mount a data CD. In this case a need for speed game. See it in files just as you'd expect.

But it just doesn't know how to handle audio or blank discs. I may try a DVD too.


I may. So you have CDs/DVDs working in BlissOS16? I just picked 15 because it should be stabler.

To be honest, I haven't tried it yet. I should do that since it's sitting right here..

EDIT:
Just tried. I'm getting a "No Superuser binary detected." error. Let me do some digging and I'll chime in shortly.

 

[RyzenMaster.sys]

To be honest, I haven't tried it yet. I should do that since it's sitting right here..

EDIT:
Just tried. I'm getting a "No Superuser binary detected." error. Let me do some digging and I'll chime in shortly.

Same issue I had where I couldn't SU.

I had to boot into grub, hit e, then add "syscall_hardening=off" to the end of the line beginning with "Linux", then hit f10 to boot. I have no clue what this does tbh, but it what this article said to do I

KSU bug in granting root for apps on BlissOS · Issue #2113 · tiann/KernelSU

Please check before submitting an issue I have searched the issues and haven't found anything relevant I will upload bugreport file in KernelSU Manager - Settings - Report log I know how to reprodu...

github.com

I think the BlissOS or KernalSU update must have broken something with root access at some point but it seems like a simple fix.

 

[lexluthermiester]

Same issue I had where I couldn't SU.View attachment 377534
I had to boot into grub, hit e, then add "syscall_hardening=off" to the end of the line beginning with "Linux", then hit f10 to boot. I have no clue what this does tbh, but it what this article said to do I

KSU bug in granting root for apps on BlissOS · Issue #2113 · tiann/KernelSU

Please check before submitting an issue I have searched the issues and haven't found anything relevant I will upload bugreport file in KernelSU Manager - Settings - Report log I know how to reprodu...

github.com

I think the BlissOS or KernalSU update must have broken something with root access at some point but it seems like a simple fix.

KernelSU is supposed to be a SU binary substitute but doesn't seem to be working that way. AndroidX86 4.4.4-R5 and CM14.1R5 had proper optical drive support, but BlissOS seems to have changed things up. This has me intrigued, we'll figure it out.