Database Info

VirtualBox Android Emulator with Marketplace

Does anyone know of any VirtualBox Android Emulator that has Marketplace?
Thanks!
Oh, I forgot to add "that's free" and not the $50 that some cheeky bastards are trying to charge for a thing called AndroidVM!

iridium21 said:
Does anyone know of any VirtualBox Android Emulator that has Marketplace?
Thanks!
Oh, I forgot to add "that's free" and not the $50 that some cheeky bastards are trying to charge for a thing called AndroidVM!
Click to expand...
Click to collapse
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.

attn1 said:
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.
Click to expand...
Click to collapse
I'm already running Android under Virtualbox - I just wondered if there's a version for VB that has Marketplace.

attn1 said:
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.
Click to expand...
Click to collapse
Wow. So much complete and utter wrong in one post... I've been running Android under a virtual machine for quite a while...

There is an x86 version of Android available at androidx86.org
It will definitely run under Virtual Box or any other virtualization software package. It's Android 1.6 by the way, and you will have to perform some geek-like activities to simulate an SD-card to install appz.
Big question is whether an ARM-device version of Android would work in a normal VM emulator (not talking about Bochs and stuff).

FloatingFatMan said:
Wow. So much complete and utter wrong in one post... I've been running Android under a virtual machine for quite a while...
Click to expand...
Click to collapse
Well, since I hadn't heard of a port to x86, I was certainly wrong about that, which makes the rest of the post moot, but not wrong. In any event, I stand corrected.

sorry to add a flame of any kind but this
"Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already."
is totally wrong.
Virtual machines virtualise the hardware of your machine (bad explanation I KNOW). if you have a PowerPC you can only emulate PowerPC (Mac for those that dont know) and intel/amd chips are things like x86 then theres smaller devices like ARM. my point is that if you have a Intel/amd box you can only emulate x86 O/S. however if you have a netbook with a version of linux or windows built on arm arch then u could prob get away with the original android if you are running normal x86 then u require android that has been built from source on x86.
this made me laugh
"Since Android is built on a Linux kernel, it's not impossible"
all i can say is what??
anyway back to the point... to run android on a x86 box u need x86 android

The problem with getting the Market to work is simply that the GApps are currently only available in a compiled for ARM version. period. that's the answer you wanted to hear i guess.
@others: stop OTing please...

hvc123 said:
sorry to add a flame of any kind but this
"Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already."
is totally wrong.
Virtual machines virtualise the hardware of your machine (bad explanation I KNOW). if you have a PowerPC you can only emulate PowerPC (Mac for those that dont know) and intel/amd chips are things like x86 then theres smaller devices like ARM. my point is that if you have a Intel/amd box you can only emulate x86 O/S. however if you have a netbook with a version of linux or windows built on arm arch then u could prob get away with the original android if you are running normal x86 then u require android that has been built from source on x86.
this made me laugh
"Since Android is built on a Linux kernel, it's not impossible"
all i can say is what??
anyway back to the point... to run android on a x86 box u need x86 android
Click to expand...
Click to collapse
VMware and Virtualbox emulate PC hardware. Since Android runs on a Linux kernel, and Linux was originally developed for an x86 PC, it follows that a port of Android could be done for a PC. Since this was not a generic discussion about virtual machines but a specific discussion about PC emulation, I don't see where the argument is.
PC = x86 and it's successors. You said I was totally wrong and then pretty much made my case. The only point I missed is that the work had already been done. To run Android in a x86 (PC) VM, you'll need an X86 (PC) compatible version of Android - right - what I said.

Right... Ok, now does anyone know the answer to the original question?

the_fish said:
The problem with getting the Market to work is simply that the GApps are currently only available in a compiled for ARM version. period. that's the answer you wanted to hear i guess.
@others: stop OTing please...
Click to expand...
Click to collapse
OP should read your thread.

arctu said:
OP should read your thread.
Click to expand...
Click to collapse
I have
Supposedly, these guys have Android with Marketplace for VirtualBox:
http://www.androidvm.com/home
So it must be able to be done - the only problem is that it's $49.95!

deleted

zgornz said:
They state they are running Ubuntu in a VM, then installed the Android emulator in Ubuntu, then the android emulator is setup to have the Marketplace. The android emulator is doing the ARM emulation.
I think using qemu User Mode emulation it might be possible to actually launch the Marketplace and apps via android-x86 without using a phone emulator. Not sure it would be that valuable, but it would allow lots more apps on a netbook running Android.
Click to expand...
Click to collapse
I imagine it would be a mess to get a touch screen working in android running on an emulator.

I read reviews on androidx86 booted (not emulated) on a few netbooks that ran great and very responsive..I also read one on a touch screen comp that worked fine..they claim all apps work-minus gapps obviously.
I plan on trying this on my Toshiba nb205 netbook today and can post a review if anyone is interested..
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

A review would sure be appreciated. More knowledge is always better.

Just a quick follow up, I tried out the Androidx86 on my netbook this weekend, both booted off the usb and installed on the hd..it runs..nothing spectacular and slightly dissappointing. You still only have a 4x4 screen and the Marketplace is entirely different, very small selection of "blah" apps..none of my favorite android apps anyways-facebook,twitter,gmail..not really any widgets either. Lastly, you need to use an external mouse..the touchpad just moves the background but gives you no pointer (could be a hardware compatability issue tho)..
On the positive side, the internet was very fast and resume time was almost instantanious..not really any major bugs, just nothing too special..

This method works with 1.6 as originally described here:
link-> forum.xda-developers.com/showthread.php?t=529170
I got it to run with the signed-dream_devphone_userdebug-img-14721.zip image from HTC for the developer phone.
link-> developer.htc.com/adp.html
I replaced the android-sdk-windows\add-ons\google_apis-4_r02\images\system.img with the one from the signed-dream_devphone_userdebug-img-14721.zip
(you should backup the original system.ini)
I then used the Android SDK GUI interface to create a Google API Level 4 machine.
I did not need to install the marketenabler.apk, as described in the original thread.
It boots up like a new Dev Phone, it behaves like there is a valid SIM and working data connection.
CTRL-F11 rotates the screen (slide out keyboard).
I have only installed a few free apps (K9 mail) but they seem to work fine.
I can't post links so copy, and paste them.
It would be trivial to create an Ubuntu virtual machine and then install the Android SDK inside of it and modify the system.img. Installing the SDK on your own machine probably takes less space and resources then running it inside another VM.

attn1 said:
Well, since I hadn't heard of a port to x86, I was certainly wrong about that, which makes the rest of the post moot, but not wrong. In any event, I stand corrected.
Click to expand...
Click to collapse
Updated, not corrected.
Yes, you were absolutely correct except for being out of date, because that process you described has already taken place as others have now pointed out.
To the person who said he was wrong, actually, no.
Android as it stands on the phone, is an ARM system compiled in ARM machine code. Android apps are hardware/platform agnostic but the operating system is not, it does have to be ported and recompiled for any different hardware system. That being said, it seems that most of that work is finished, ala androidx86.org
Cheers,
Rob

x86 Android Market
I have been reading a bit. It seems that it is possible to have Gapps installed for x86.
Froyo, people have been using Cyanogen 6 Gapps for Tegra.
Android x86 launched their Gingerbread version not long ago. It would not surprise me if Cyanogen 7 Gapps worked with it. Different devices used different versions and now there is just one version for all. It should be possible to run VM from the desktop.
NDK dependent Apps: in theory, it may be possible taking the apk using android apk tool, x86 NDK from the x86 build and rebuild it for x86 code.
I will be playing with an old EEE900 and see how this goes sooon.

[GUIDE]Definitive guide to Windows 8 on ARM

Collating known facts and informed opinion
There is no public pre-release of Win8 on ARM yet (and it might only ever be OEM only)
Should be a Windows 8 beta in February 2012? , but still might not be a public ARM beta
Win8 on ARM will need to be customised extensively by the OEM for their particular hardware
as it is NOT a general purpose system covering all standard components like Windows or Linux on x86 PC’s is
Needs ARM v7 cpu (but all modern tablets have a their cpu / SOC based on ARM v7)
Needs a UEFI firmware/‘bios’
and no existing Android/Thinkpad systems out there have this
http://news.softpedia.com/news/Wind...m-the-Maker-of-Instant-Boot-BIOS-205487.shtml
Will have a secure bootloader on ARM (but not on x86/x64)
http://arstechnica.com/microsoft/ne...ing-or-the-end-of-the-world-as-we-know-it.ars
Win8 tablet spec
http://www.tomshardware.com/news/Windows-8-Microsoft-Tablet-x86-ARM,14504.html
?MB RAM, 10GB storage, 1366x768 screen
Some ARM related information mentioned on http://en.wikipedia.org/wiki/Windows_8
There will be an Embedded Windows version of Win8 on ARM
http://www.windowsfordevices.com/c/a/News/Microsoft-promises-embedded-versions-of-Windows-8/
Running x86 apps on Windows ARM – not possible or v unlikely. Microsoft have not definitely confirmed that there wont be any x86 emulator, but unlikely in the limited space available
Maybe we will see a 3rd party Virtual Box or Boschs or similar to emulate x86 and some intercept dll’s to thunk the api calls to the relevant native ARM windows dll’s))
Will it run WP7 apps ? (Silverlight / processor neutral apps) – unknown, but should be easy to port
http://news.softpedia.com/news/Port-Windows-Phone-Apps-to-Windows-8-232615.shtml
There is a rumour of some internal HP testing of Win8 on Thinkpad
http://www.foxnews.com/scitech/2011/10/24/hp-testing-windows-8-on-touchpads/

The only (prototype) Windows 8 ARM tablet device seen to date, is the Qualcom one
http://www.qualcomm.com/media/relea...on-windows-8-based-prototype-pcs-previewed-mi
http://www.pcmag.com/article2/0,2817,2392930,00.asp
http://www.youtube.com/watch?v=BblNpUEp6N8
[This info copied from tbaker077's post in the HP Touchpad section, as it saved me having to look it up]
And Nvidia Tegra 3, TI OMAP4430 one
http://www.netbooknews.com/27326/nv...gon-powered-tablets-laptop-running-windows-8/
http://www.youtube.com/watch?v=kElw2byX9EE&feature=relmfu
Both video clips from the recent Microsoft Windows 8 Build conference

Next version of Windows Phone (WP8) to be based on Windows 8
(presumably Windows8 onARM)
http://arstechnica.com/microsoft/ne...s-8-kernel-and-integration-multiple-cores.ars

Windows 8 on ARM should go to [OEM] developers in February
http://news.cnet.com/8301-13924_3-5...to-developers-soon-say-sources/?tag=txt;title

Here's the latest definitive info from Microsoft
Its a very long and detailed Building Windows 8 blog posting
http://blogs.msdn.com/b/b8/archive/...ndows-for-the-arm-processor-architecture.aspx

A good write up of the latest news
http://www.zdnet.com/blog/hardware/...-on-arm-and-why-apple-should-be-worried/18071

Widows 8 Consumer Preview available today (Client and Server versions)
But Intel only
No ARM version other than via OEM's / 'testers'
Latest news on http://www.zdnet.com/blog/microsoft/its-windows-8-download-day-heres-what-we-know/12058
And no Domain or Enterprise management features on Windows on ARM !
http://arstechnica.com/microsoft/ne...-will-lack-enterprise-management-features.ars

xsoliman3 said:
And no Domain or Enterprise management features on Windows on ARM !
http://arstechnica.com/microsoft/ne...-will-lack-enterprise-management-features.ars
Click to expand...
Click to collapse
I see why MS would have decided to do this, ie split home and business tablets in to ARM and x86, and to be honest i think for the most part it would go that way anyway, but actively NOT putting one of the best features in windows on to a device is only going to reduce your customer base an i gt the feeling they are going to need all the support they can get on this one
The concept of what they are doing here is great but the implementation of it is quite frankly, terrible! but we shall just have to wait and see, nothing is set in stone yet

Microsoft Confirms Lockdown of ARM Devices Running Windows 8
http://www.xda-developers.com/feature/microsoft-confirms-lockdown-of-arm-devices-running-windows-8/

Windows RT
The official name of Windows on ARM is now announced as Windows RT
http://windowsteamblog.com/windows/.../04/16/announcing-the-windows-8-editions.aspx
Lots of disussion there about the naming

RT is OEM only, confirmed

More on managing WOA (Windows RT) in a corporate environment, even though it can't be domain joined
http://blogs.msdn.com/b/b8/archive/...quot-pcs-in-the-enterprise-including-woa.aspx

xsoliman3 said:
More on managing WOA (Windows RT) in a corporate environment, even though it can't be domain joined
http://blogs.msdn.com/b/b8/archive/...quot-pcs-in-the-enterprise-including-woa.aspx
Click to expand...
Click to collapse
I have to say im starting to understand the ARM development a bit more after reading that.
I still think x86 is the way to go for a fully functional tablet (at least for me) but if the price is right on these arm units then I think there will be some serious thought going in to buying them

dazza9075 said:
I have to say im starting to understand the ARM development a bit more after reading that.
I still think x86 is the way to go for a fully functional tablet (at least for me) but if the price is right on these arm units then I think there will be some serious thought going in to buying them
Click to expand...
Click to collapse
x86 models would def go for a higher price because you would be able to run all Windows 8 Desktop software unlike on WinRT.
The main difference will be battery life and processing juice.
Anyways, I think Microsoft should give less options for the Windows 8 tablets and provide more support for the hardware.

xsoliman3 said:
Running x86 apps on Windows ARM – not possible or v unlikely. Microsoft have not definitely confirmed that there wont be any x86 emulator, but unlikely in the limited space available
Maybe we will see a 3rd party Virtual Box or Boschs or similar to emulate x86 and some intercept dll’s to thunk the api calls to the relevant native ARM windows dll’s))
Click to expand...
Click to collapse
Not gonna happen. x86 is complex instruction set, ARM is reduced instruction set. Emulating ARM on x86 can be done with somewhat reasonable speed if you have a fast processor, but x86 on ARM is probably going to be ridiculously slow. ARM is more efficient, so clock for clock you get better speed with lower power requirements, but emulating CISC from RISC is ****ty.
As far as WINE style API hook intercepting, that is a real crapshoot because many apps do have some bits of assembly in there.
xsoliman3 said:
Will it run WP7 apps ? (Silverlight / processor neutral apps) – unknown, but should be easy to port
http://news.softpedia.com/news/Port-Windows-Phone-Apps-to-Windows-8-232615.shtml
Click to expand...
Click to collapse
Anything that runs on the .Net platform should work in win8 ARM assuming that windows 8 includes the .net framework.
dazza9075 said:
I have to say im starting to understand the ARM development a bit more after reading that.
I still think x86 is the way to go for a fully functional tablet (at least for me) but if the price is right on these arm units then I think there will be some serious thought going in to buying them
Click to expand...
Click to collapse
I disagree, ARM is far more practical for mobile applications due to it's massive energy efficiency advantage over x86.
Besides, as of yet there are no x86 based SoC's, it's all separate IC's, which reduces the energy efficiency even further. Intel has Medfield coming up, but I wouldn't count on that including a decent GPU.

Rakeesh_j said:
Anything that runs on the .Net platform should work in win8 ARM assuming that windows 8 includes the .net framework.
Click to expand...
Click to collapse
Windows Phone uses the .Net Compact Framework, special version of the Silverlight, XNA and some phone-specific assemblies. It won't start on the desktop .Net, because it uses a different set of the assemblies, not saying that it uses a different CLR (especially the garbage collector).
But microsoft can write a special "layer" which will allow to run WP7 apps, but why is it needed? There is lots of crap in the marketplace.

Rakeesh_j said:
Anything that runs on the .Net platform should work in win8 ARM assuming that windows 8 includes the .net framework.
Click to expand...
Click to collapse
You can write applications in .NET for WinRT, but they don't actually run in the CLR as we think of it today.
Best way to explain is to look at the linked image.
http://i.zdnet.com/blogs/davidburela.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Think of the Green as what works on WinRT that you can purchase and install. (Things in blue on WinRT, cannot be sideloaded since you can only install from the store which sells Metro apps).
What is happening is the application you write in .NET, instead of going to IL to be run in a .NET CLR, is being sent to WinRT for execution.
Better explanation here:
http://csharperimage.jeremylikness.com/2012/03/net-and-metro-windows-runtime-and-clr.html
Would it be possible for a light CLR to be written in ARM for .NET apps to execute against, probably. But at this time, your .NET appears to be executed by WinRT. This means you get a subset of .NET that can execute on Windows 8 ARM as a METRO app being interpreted by WINRT.

No sideloading of arm desktop apps
Just to re-iterate a point from the above post
As per the recent complaints by firefox etc, even if you build a standard aka desktop app and compile for ARM, you will not be able to deploy it as not signed
(and no side loading of desktop apps)
Might? be able to pursuade the Microsoft store to host it, as they will host deskop apps for Windows8, but not sure if they will allow desktop apps for WIndows 8 on ARM (Windows RT)
ALso unclear if ENterprise customers can have their own private app store for their corporate apps
Side loading of Metro apps on Windows RT is also unclear
Can get them from the store (signed) but again doesnt seem to be able to side load them ?
to be confirmed

Windows 8 diet exposes Microsoft's weak ARM
Windows 8 diet exposes Microsoft's weak ARM
http://www.theregister.co.uk/2012/04/17/windows_8_package_confusion/
Good article comparing WIndows8 on x86/x64 to Windows RT on ARM
and the enevitable confusion

xsoliman3 said:
Just to re-iterate a point from the above post
Also unclear if ENterprise customers can have their own private app store for their corporate apps
Side loading of Metro apps on Windows RT is also unclear
Can get them from the store (signed) but again doesnt seem to be able to side load them ?
to be confirmed
Click to expand...
Click to collapse
These questions are answered here:
http://blogs.msdn.com/b/windowsstor...deploying-metro-style-apps-to-businesses.aspx
To Sideload:
You need to sign an application with a cert the machine trusts. (Can be your own cert, if you add it to cert store.)
Set 'Allow all trusted apps to install' in group policy or registry
Then either use a machine that is domain joined, or activate a special product key by using a script on the target machine to enable sideloading.
This will allow you to install via a variety of methods listed in the article.
While no 'private app store' has been listed, creating your own, would just be a quick website, that drops install requests in a queue, that are then executed by sccm or another deployment agent. On x86, you could create a background process to do it if you don't have a domain and a deployment agent.

[Q] Android x86 efi boot

So I tried out Android x86 for my PC. It works beautifully. I cannot boot it on my Surface Pro though... It seems like the Surface Pro was designed to only boot EFI boot loaders. Not BIOS boot loaders... I was wondering if somebody could lend a hand at helping me get past this issue. I really think Android x86 would be great for the Surface Pro, there are so many things I miss from my Nexus 7 but I don't want an Android device, if I could just dual boot it every now and then, I would be happy. Can someone please get the Android 4.2 x86 ISOs to boot via EFI? That would be appreciated.

sionicion said:
So I tried out Android x86 for my PC. It works beautifully. I cannot boot it on my Surface Pro though... It seems like the Surface Pro was designed to only boot EFI boot loaders. Not BIOS boot loaders... I was wondering if somebody could lend a hand at helping me get past this issue. I really think Android x86 would be great for the Surface Pro, there are so many things I miss from my Nexus 7 but I don't want an Android device, if I could just dual boot it every now and then, I would be happy. Can someone please get the Android 4.2 x86 ISOs to boot via EFI? That would be appreciated.
Click to expand...
Click to collapse
hmmm ... interesting you tried ...
and came out with a finding ...
following this thread on the possible development on this front ...
I've always dreamt of a Surface Pro on Android always ...
a reboot to Win7 for Work ... and back to Android !!!
going to be really very interesting ...
Hope the Android X86 team is peaking at this thread ...
Cheers!

Did you bother disabling secure boot?
Otherwise you can try "jar of beans" or "bluestacks" to run android applications for windows. There is a version of bluestacks which claims to be optimised for the surface pro, in reality its just bluestacks with proper windows 8 touch support.

SixSixSevenSeven said:
Did you bother disabling secure boot?
Otherwise you can try "jar of beans" or "bluestacks" to run android applications for windows. There is a version of bluestacks which claims to be optimised for the surface pro, in reality its just bluestacks with proper windows 8 touch support.
Click to expand...
Click to collapse
Of course I did, the problem is the Surface Pro's UEFI chip does not actually support booting BIOS-based bootloaders. It only boots EFI-based bootloaders like the Windows Boot Manager or Grub EFI, etc. Unless one was to emulate BIOS to boot Android, it needs a EFI bootloader to even boot it on the Surface Pro. Ubuntu boots fine on the Surface Pro, but it is booting from Grub EFI. I copied the Grub EFI file to my other flash drive, and Grub indeed boots. It is the trouble of getting Android x86 to boot because it isn't using a EFI-based bootloader.
Also, that wasn't the point. I want to run pure Android just for the experience of having Android right on my Surface so I don't miss having a Nexus 7. I tried it on my desktop PC and it runs beautifully, if only I could get it on my Surface...

Surface Pro comes with Windows 8 Pro and a CPU capable of second-level address translation. It is therefore capable of running Client Hyper-V, which is a hypervisor-based virtualization (rather than hosted VM) technology that allows you to run another OS in parallel with Windows. I believe it includes support for BIOS-based OSes. Perhaps you should try that?

GoodDayToDie said:
Surface Pro comes with Windows 8 Pro and a CPU capable of second-level address translation. It is therefore capable of running Client Hyper-V, which is a hypervisor-based virtualization (rather than hosted VM) technology that allows you to run another OS in parallel with Windows. I believe it includes support for BIOS-based OSes. Perhaps you should try that?
Click to expand...
Click to collapse
But what's the point in that? I don't want to virtualize. I want to run it natively... That's like saying hey use Bluestacks. I want Android running native on my Surface.
Anyway, guys I got it. Here it is.

First of all, running on a hypervisor is nothing like using Bluestacks. Android would then be running as "natively" as Windows at that point (Windows itself would also be running on the hypervisor), except that Windows would have first access to the display (Android would be able to use the graphics hardware nonetheless). When the virtual display was set to the Android machine, Android would be interacting with the input devices. As a plus side, you could switch back and forth rapidly...
That said, if you managed to get it working on bare metal, that's cool. Did you mean to include a link in your "Here it is "?

GoodDayToDie said:
First of all, running on a hypervisor is nothing like using Bluestacks. Android would then be running as "natively" as Windows at that point (Windows itself would also be running on the hypervisor), except that Windows would have first access to the display (Android would be able to use the graphics hardware nonetheless). When the virtual display was set to the Android machine, Android would be interacting with the input devices. As a plus side, you could switch back and forth rapidly...
That said, if you managed to get it working on bare metal, that's cool. Did you mean to include a link in your "Here it is "?
Click to expand...
Click to collapse
The tutorial is on the YouTube page. But the problem with the Hyper-V hypervisor is it uses that remote console. I only found it decent for running Windows with the guest drivers installed. Unless I'm just not executing it very well, Hyper-V isn't a good solution. Since VirtualBox is used much more in the Linux world, I would use that before using Hyper-V.
I'll investigate the virtual solutions though and let you know.

more recent linux kernel versions do support hyper-v, partly provided by microsoft believe it or not
I would assume that hyper-v support would carry over into android. Just a case of setting it up.

Worth trying. However, Android runs a somewhat customized kernel build that probably doesn't include a lot of the optional stuff such as the Hyper-V helpers. Of course, you could install the required kernel module for them...

SixSixSevenSeven said:
I would assume that hyper-v support would carry over into android. Just a case of setting it up.
Click to expand...
Click to collapse
I somewhat doubt the android platform itself has support for hyper-v.
Further, if you're looking to boot android directly would an android kernel and platform support booting via UEFI at all yet?
What partition would android be installed to? it likely wouldn't like being stuffed into an NTFS partition so you'd have to repartition the SSD and take some of the space from Windows, or boot android from an SDcard or USB memory stick.
EDIT: I see you did infact get it running, nice job, did you just use GRUB for a bootloader? did you have android run from the SSD or from elsewhere?
tbh if I had a surface pro I don't think i'd be installing android on it, slightly a waste.
by the way, a faster way of doing advanced reboot so you get the boot options is to hold shift and select the reboot option from the power menu.

So, after a short little flip around the web, I came across this
https://01.org/android-ia/downloads/2013/android-4.2.2r1-ia0
somehow.
I would love to have my Surface Pro dual-bootable between Android and Win8, but your tutorial has sort of overwhelmed me.
Are you using this code? Would it be better to?
Just wasn't sure where this development was going....

Purrsia said:
So, after a short little flip around the web, I came across this
https://01.org/android-ia/downloads/2013/android-4.2.2r1-ia0
somehow.
I would love to have my Surface Pro dual-bootable between Android and Win8, but your tutorial has sort of overwhelmed me.
Are you using this code? Would it be better to?
Just wasn't sure where this development was going....
Click to expand...
Click to collapse
You can try my guide in windows 8 development forums
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
feherneoh said:
Can't you add the lines which boot android-x86 into Ubuntu's GRUB? If it can be loaded, it could be used to load Android's kernel
Click to expand...
Click to collapse
Microsoft locked it, you can only use the stock bootloader for now
Sent from my HTC One X+ using xda app-developers app

rEFIit
Have you tried a rEFIit or rEFIitd? As the name subtly suggests, its a bootloader for EFI machines. I suggest having a look. I'm going to try this myself on a couple of machines tomorrow once I get to work. Good luck! Let me know how it turns out or if I lead someone down the right track!
rEFInd - An EFI boot manager utility: http://goo.gl/KRwzk
rEFIt: http://refit.sourceforge.net/
Agreed, Android on a Surface would be kick ass. Windows for work, Android for real life!

Hi Folks.....
Feeling a little nervous here seems I must have took a wrong turn somewhere to end up in the Microsoft Surface forum LOL.
Is anyone still wondering about this? I noticed the other day that the linux kernel 3.10 which is currently used by the android-x86 project has android efi drivers/patches which maybe what you require. I'd also have a poke around the Android-IA sources which is the official intel android open source project from what I recall there's more efiboot goodies in there.
As an extra bonus the 3.10 kernel also includes a patch for Binder which allows a 32bit userspace to function correctly with a 64bit PAE kernel which means "BIG RAM" so if you have more than 4 gig and a 64 bit processor you can get access to the full ram allocation, not quite the pure 64bit Android that I want but it'll do for now while I figure out the finer points of x86_64 assembly language.
If Anyone wants/needs a kernel rattling off with these options enabled just let me know and i'll well rattle one off!
Thanks

trevd said:
Hi Folks.....
...I noticed the other day that the linux kernel 3.10 which is currently used by the android-x86 project has android efi drivers/patches which maybe what you require. I'd also have a poke around the Android-IA sources which is the official intel android open source project from what I recall there's more efiboot goodies in there.
As an extra bonus the 3.10 kernel also includes a patch for Binder which allows a 32bit userspace to function correctly with a 64bit PAE kernel which means "BIG RAM" so if you have more than 4 gig and a 64 bit processor you can get access to the full ram allocation, not quite the pure 64bit Android that I want but it'll do for now while I figure out the finer points of x86_64 assembly language.
If Anyone wants/needs a kernel rattling off with these options enabled just let me know and i'll well rattle one off!
Thanks
Click to expand...
Click to collapse
If the offer still stands, I would be interested in this (..or even just a how-to).
I have a multiboot system with PCLinuxOS, Ubuntu, and Win8.1 running right now, and I can get the recent 4.4rc1 release from android x86 to boot if I switch to legacy bios and use legacy grub from PCLinuxOS or the android_x86 thumbdrive, but I cannot get it to boot from Ubuntu's EFI capable Grub2 (..d/t kernel panic). On my Acer m5-583p it works great in legacy mode (wifi, touchscreen, keyboard, etc), but I would like to be able to use an EFI bootloader so that I don't have to change to/from legacy/efi before selecting the OS at boot.
Thanks! :good:

Windows RT 8.1 anti-jailbreak differences

It looks like they locked out the jailbreak from 8.1 by invalidating all old signatures. Windows RT 8.1's ci.dll does not trust the "1.3.6.1.4.1.311.10.3.6" OID in certificates anymore, only a new "1.3.6.1.4.1.311.10.3.21" OID. Both are required now. How it works is, if a certain configuration bit is not set in the call to CipMinCryptToSigningLevel, attempting to load an executable with a *10.3.6 OID on the certificate but not a *10.3.21, CipMinCryptToSigningLevel will explicitly fail with STATUS_INVALID_IMAGE_HASH--it won't even bother to consider it a 0 signing level.
I bet that this time, they will not give device manufacturers anything but executables that require booting Windows in test mode, something only Microsoft and device manufacturers can accomplish due to Secure Boot.
Microsoft Office's executables are signed with both the 2010 and 2011 keys, presumably so that it can run on both 8.0 and 8.1.
Visual Studio 2012's remote debugger doesn't work anymore, either. I bet that they're working on further locking down the remote debugger to avoid letting us use it to jailbreak.
The only good news I see is that NtUserSetInformationThread sub 7--the kernel exploit--has not been fixed.

Myriachan said:
It looks like they locked out the jailbreak from 8.1 by invalidating all old signatures. Windows RT 8.1's ci.dll does not trust the "1.3.6.1.4.1.311.10.3.6" OID in certificates anymore, only a new "1.3.6.1.4.1.311.10.3.21" OID. Both are required now. How it works is, if a certain configuration bit is not set in the call to CipMinCryptToSigningLevel, attempting to load an executable with a *10.3.6 OID on the certificate but not a *10.3.21, CipMinCryptToSigningLevel will explicitly fail with STATUS_INVALID_IMAGE_HASH--it won't even bother to consider it a 0 signing level.
I bet that this time, they will not give device manufacturers anything but executables that require booting Windows in test mode, something only Microsoft and device manufacturers can accomplish due to Secure Boot.
Microsoft Office's executables are signed with both the 2010 and 2011 keys, presumably so that it can run on both 8.0 and 8.1.
Visual Studio 2012's remote debugger doesn't work anymore, either. I bet that they're working on further locking down the remote debugger to avoid letting us use it to jailbreak.
The only good news I see is that NtUserSetInformationThread sub 7--the kernel exploit--has not been fixed.
Click to expand...
Click to collapse
Do you know if they blocked downgrading (through updating the EFI certs), or if we can just throw the old CI.dll in there or not?
Edit: Nevermind, they state that a recovery drive can return to RT.

netham45 said:
Do you know if they blocked downgrading (through updating the EFI certs), or if we can just throw the old CI.dll in there or not?
Click to expand...
Click to collapse
I can boot the 8.0 recovery image from USB just fine. In fact, if I choose Command Prompt, I can then go run WinDbg if it's on the hard drive. =)
Windows 8.1 knows the name of the new OIDs. The previous OID 1.3.6.1.4.1.311.10.3.6 is "Windows System Component Verification"; the new OID 1.3.6.1.4.1.311.10.3.21 is specifically named "Windows RT Verification".
Replacing ci.dll with the old version causes it to fail to boot. Looking into this more.

Myriachan said:
It looks like they locked out the jailbreak from 8.1 by invalidating all old signatures. Windows RT 8.1's ci.dll does not trust the "1.3.6.1.4.1.311.10.3.6" OID in certificates anymore, only a new "1.3.6.1.4.1.311.10.3.21" OID. Both are required now. How it works is, if a certain configuration bit is not set in the call to CipMinCryptToSigningLevel, attempting to load an executable with a *10.3.6 OID on the certificate but not a *10.3.21, CipMinCryptToSigningLevel will explicitly fail with STATUS_INVALID_IMAGE_HASH--it won't even bother to consider it a 0 signing level.
I bet that this time, they will not give device manufacturers anything but executables that require booting Windows in test mode, something only Microsoft and device manufacturers can accomplish due to Secure Boot.
Microsoft Office's executables are signed with both the 2010 and 2011 keys, presumably so that it can run on both 8.0 and 8.1.
Visual Studio 2012's remote debugger doesn't work anymore, either. I bet that they're working on further locking down the remote debugger to avoid letting us use it to jailbreak.
The only good news I see is that NtUserSetInformationThread sub 7--the kernel exploit--has not been fixed.
Click to expand...
Click to collapse
I run office from windows.old but it doesnt work at all.

windowsrtc said:
I run office from windows.old but it doesnt work at all.
Click to expand...
Click to collapse
Windows RT 8.1 installs a new set of Office executables that are signed with the new signature. The old Office executables won't work, just like everything else won't work.

Trying to use the old ci.dll fails, but using the old boot loader does not. In fact, the old 8.0 boot loader can actually boot the 8.1 kernel just fine, not even noticing a difference.
The 8.1 bootmgr.efi is signed with the *10.3.21 OID. This means that they could reflash the firmware to only accept *10.3.21 signatures during the final build 8.1 upgrade process if they wanted to be mean to people in the way that Apple is. In other words, I fully expect that Microsoft will do this. Even worse, they could force the 8.1 install on most people via Windows Update if it's free to RT users.
We need another way in. >.<

I dunno, I think this should reinvigorate those with the know-how to figure out how to get Linux on the thing so we could keep control of our own devices. It's come up a couple times in a couple threads, and I'm sure a kernel driver is the easiest way to go about it for now.

The Linux boot ideas have all been about cross-booting from RT into Linux. If 8.1 locks out our ability to run unsigned code (including kernel drivers), then it would no longer be possible to load Linux either. New devices, or older ones that got the upgrade, would be stranded.
Don't get me wrong, I thing that getting Linux working is an admirable goal. Just don't expect it will fix the 8.1 "now with moar lockdown!" problem.

Myriachan said:
Visual Studio 2012's remote debugger doesn't work anymore, either.
Click to expand...
Click to collapse
What about VS2013 - the preview version has just been released... ?

GoodDayToDie said:
The Linux boot ideas have all been about cross-booting from RT into Linux. If 8.1 locks out our ability to run unsigned code (including kernel drivers), then it would no longer be possible to load Linux either. New devices, or older ones that got the upgrade, would be stranded.
Don't get me wrong, I thing that getting Linux working is an admirable goal. Just don't expect it will fix the 8.1 "now with moar lockdown!" problem.
Click to expand...
Click to collapse
Well, I meant, get out ahead of it and don't ever bother upgrading to 8.1. Leave it jailbroken at 8.0 and give up on Microsoft thereafter.

GoodDayToDie said:
The Linux boot ideas have all been about cross-booting from RT into Linux. If 8.1 locks out our ability to run unsigned code (including kernel drivers), then it would no longer be possible to load Linux either. New devices, or older ones that got the upgrade, would be stranded.
Don't get me wrong, I thing that getting Linux working is an admirable goal. Just don't expect it will fix the 8.1 "now with moar lockdown!" problem.
Click to expand...
Click to collapse
It all depends on whether upon 8.1's final release Microsoft will do a firmware update that disallows bootarm.efi files that were signed with the original keys.

"The following error occurred: The Remote Debugger cannot be started as an Administrator on Microsoft Windows RT. Restart the remote debugger with normal user permissions."
I'm rather disappointed in MS for /still/ not unlocking RT.
Edit:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like they locked down the debugger decently.

I think the best way is to find a way to flash uefi by uart.so we can hack uefi directly.
BTW,windows 8.1 WDK contains arm files and may be they can be used on vs2012.

I came up with a copy of windbg/cdb that works, but it looks like they blocked attaching to csrss by marking it as a protected image.

netham45 said:
I came up with a copy of windbg/cdb that works, but it looks like they blocked attaching to csrss by marking it as a protected image.
Click to expand...
Click to collapse
This may make things harder, but you can try to run WinDBG as a service and run your script. Start from here: http://support.microsoft.com/kb/824344

netham45 said:
I came up with a copy of windbg/cdb that works, but it looks like they blocked attaching to csrss by marking it as a protected image.
Click to expand...
Click to collapse
I PM'd you about discussing ways into 8.1. I sent a PM because I would rather not discuss certain things visibly prior to 8.1 release when Microsoft still has an easy chance to defeat what we come up with before launch.

Myriachan said:
... Windows 8.1 knows the name of the new OIDs. The previous OID 1.3.6.1.4.1.311.10.3.6 is "Windows System Component Verification"; the new OID 1.3.6.1.4.1.311.10.3.21 is specifically named "Windows RT Verification".
Replacing ci.dll with the old version causes it to fail to boot. Looking into this more.
Click to expand...
Click to collapse
Since your exploit still works, can you locate ci.dll and patch it in-memory? Or is Microsoft performing runtime integrity checks?
As far as I {knew|know}, Microsoft was only doing on-disk checks before mapping the image into memory. See Alan Meese's Windows Phone: Security Deep Dive, http://channel9.msdn.com/Events/TechEd/Europe/2012/WPH304. (I know its a different platform, but I would expect it to be very similar).
Jeff

noloader said:
Since your exploit still works, can you locate ci.dll and patch it in-memory? Or is Microsoft performing runtime integrity checks?
Click to expand...
Click to collapse
Yes, which is what the 8.0 exploit does. Finding ci.dll is simple: EnumDeviceDrivers or whatever the NT API equivalent is. The hard part is writing to kernel memory.
Two exploits are required in order to jailbreak. The first is to execute arbitrary assembly code at user level. The second is to attack kernel mode with an exploit. Both of these are difficult problems to solve. In 8.0, the code execution exploit was to use a Microsoft-signed debugger executable to modify an existing program's code. The kernel exploit was the kernel not properly validating parameters from csrss.exe, a trusted process.
Microsoft didn't release a security fix for the csrss.exe exploit probably under the idea of being on the other side of the airtight hatchway, using Raymond Chen terminology: attacking csrss.exe requires Administrator access, so from a security perspective, an attacker would already have won. The only time that that philosophy doesn't apply is with DRM protections--and guess what, the 8.1 fix is to mark csrss.exe as a DRM process, which it clearly is not.
The other big thing Microsoft did in 8.1 was to invalidate all the signed debugger executables from 8.0, and make the new 8.1 debuggers require a special secure boot mode that only device manufacturers and Microsoft can enable.

Myriachan said:
It looks like they locked out the jailbreak from 8.1 by invalidating all old signatures. Windows RT 8.1's ci.dll does not trust the "1.3.6.1.4.1.311.10.3.6" OID in certificates anymore, only a new "1.3.6.1.4.1.311.10.3.21" OID. Both are required now. How it works is, if a certain configuration bit is not set in the call to CipMinCryptToSigningLevel, attempting to load an executable with a *10.3.6 OID on the certificate but not a *10.3.21, CipMinCryptToSigningLevel will explicitly fail with STATUS_INVALID_IMAGE_HASH--it won't even bother to consider it a 0 signing level.
I bet that this time, they will not give device manufacturers anything but executables that require booting Windows in test mode, something only Microsoft and device manufacturers can accomplish due to Secure Boot.
Microsoft Office's executables are signed with both the 2010 and 2011 keys, presumably so that it can run on both 8.0 and 8.1.
Visual Studio 2012's remote debugger doesn't work anymore, either. I bet that they're working on further locking down the remote debugger to avoid letting us use it to jailbreak.
The only good news I see is that NtUserSetInformationThread sub 7--the kernel exploit--has not been fixed.
Click to expand...
Click to collapse
Myriachan - do you have a reference for those changes? A friend is writing a paper and would like to verify the source and cite you. Google is turning up lots of spurious noise.

noloader said:
Myriachan - do you have a reference for those changes? A friend is writing a paper and would like to verify the source and cite you. Google is turning up lots of spurious noise.
Click to expand...
Click to collapse
I believe everything in this thread is our own research.

BlissOS on VirtualBox - Not working...

I've watched a tons of install videos on youtube and while the outdated buggy blissos11 running anroid9 works on virtualbox i can't get the latest one running.
Now i'm asking if the problem is on my end or blissos.
So, i got blissos15-android12l SUCCESSFULY INSTALLED but when i boot the os, nothing happens. What's going on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's stuck FOREVER.

It works in VMware for me, but fails in Vbox.

I toght virtualbox is better because it's minimalistic and has decent privacy standards over vmware, also vmware seems to be somewhat deeply integrated to the host OS, not the case with virtualbox, it's super light - only two services in taskmanager.
Seriously i saw someone on youtube getting blissOS 14/15 running in virtualbox but when i follow the same steps and it even says successfuly installed, it doesn't load the OS after booting, i'm clueless.

Both VMWare and VirtualBox is not officially supported by Bliss OS.
Why run Bliss OS in an 3rd-party emulator where Windows since some time offers Windows Subsystem for Android, what actually is Android 13 based?

Privacydroid said:
I toght virtualbox is better because it's minimalistic and has decent privacy standards over vmware, also vmware seems to be somewhat deeply integrated to the host OS, not the case with virtualbox, it's super leight - only two services in taskmanager.
Seriously i saw someone on youtube getting blissOS 14/15 running in virtualbox but when i follow the same steps and it even says successfuly installed, it doesn't load the OS after booting, i'm clueless.
Click to expand...
Click to collapse
VMware doesn‘t have privacy issues, and Virtualbox is by no means light. 2 processes in task manager means nothing (how much ram/cpu those processes use matters more).
I’m doing some testing with Blis in VBox and will get back to you.
For general use, as @jwoegerbauer said, WSA would be better (if you run windows 11 )
- Tejas

Windows 11? You must be joking, before touching that cancerous malware i'll switch to linux.
11 is utter garbage spyware, sure 10 is the same but 11 is even worse.
Has Windows become Spyware?
Has Windows become Spyware? Windows 11 vs XP Network Analysis on Wireshark. What websites does your new laptop secretly connect to? Get Crowdsec (free): https://www.crowdsec.net/?mtm_campaign=PCSecMag-May22 (sponsor) Buy the best antivirus: https://thepcsecuritychannel.com/best-antivirus Join...
yewtu.be

Privacydroid said:
Windows 11? You must be joking, before touching that cancerous malware i'll switch to linux.
11 is utter garbage spyware, sure 10 is the same but 11 is even worse.
Click to expand...
Click to collapse
AFAIK Malware, short for malicious software, refers to any intrusive software developed by cybercriminals (often called hackers) to damage or destroy computers and computer systems. Don't think Microsoft is doing so.
AFAIK Spyware collects personal and sensitive information that it sends to advertisers, data collection firms, or malicious actors for a profit. Attackers use it to track, steal, and sell user data, such as internet usage, credit card, and bank account details, or steal user credentials to spoof their identities. Don't think Microsoft is stealing an user's private data.
BTW:
Serious Windows users make use of O&O Shutup tool to configure behaviour of Windows OS with regards to unwanted actions.

jwoegerbauer said:
AFAIK Malware, short for malicious software, refers to any intrusive software developed by cybercriminals (often called hackers) to damage or destroy computers and computer systems. Don't think Microsoft is doing so.
AFAIK Spyware collects personal and sensitive information that it sends to advertisers, data collection firms, or malicious actors for a profit. Attackers use it to track, steal, and sell user data, such as internet usage, credit card, and bank account details, or steal user credentials to spoof their identities. Don't think Microsoft is stealing an user's private data.
BTW:
Serious Windows users make use of O&O Shutup tool to configure behaviour of Windows OS with regards to unwanted actions.
Click to expand...
Click to collapse
Honestly no offense but the reply you wrote is nothing but extremely dumb, dumb in these sense of seriously trashworthy.
Does microsoft meet the definition of malware? No. Did i mean that they are malware? No.
Is microsoft a disgusting company that should be ashamed of themselfes? Absolutely.
Is microsoft windows spyware and does it steal personal information? You don't think so? We are done here, no words. Stop replying let this thread die without saying anything more that hurts my brain.

@Privacydroid I know... I personally use Linux and Win11 in dualboot and still end up using Linux 90% of the time.
Microsoft is becoming more and more like an ad company, and I have to admit that (sadly). Not that win10 is any better than 11 (older versions of windows 10 were better though). The PC Security Channel compared XP to 11, cut comparing 10 to 11 shows that they collect approximately the same amount of data.
However, this thread has nothing to do with Windows. It's about Bliss OS. For me, VMware works. I'm trying to get it working with Virtualbox, and I'll tell you if I do. What version of windows (your screenshots imply windows) and Virtualbox are you using? Bliss 12.1 (12L) is considered experimental right now (keep that in mind too).

It will run (and freeze up at setup) in virtualbox if you go to without hardware acceleration (at bottom of list). (don't do this)

In VMWare, you need to enable EFI (go to the .vmx file and add the line
Code:
firmware = "efi"
before booting. Install it (make sure to set the CD and HD to SATA in the settings) and remember to disable HW acceleration (Advanced Options -> No Hardware Acceleration). It works (doesn't freeze like Vbox does).

traman124 said:
In VMWare, you need to enable EFI (go to the .vmx file and add the line
Code:
firmware = "efi"
before booting. Install it (make sure to set the CD and HD to SATA in the settings) and remember to disable HW acceleration (Advanced Options -> No Hardware Acceleration). It works (doesn't freeze like Vbox does).
Click to expand...
Click to collapse
I'd say microsoft windows isn't becomming an ad company, it already is.
It's the same trash like google android, facebook preinstalled - cannot be deleted but only deactivated which is not the same, i don't use facebook but these mentally drowned companys force it on anybodys phone without their consent.
And this is exactly what happens on windows aswell, when i tried windows 11 in virtualbox for the first time it had not only facebook preinstalled but also a whole lot's of other degenerated trash like tiktok. It's insane just how many connection windows makes directly after booting up the os, lucky privacy has evolved to such a degree where you can even use windows without any concerns over privacy, i've literally entirely blocked all microsoft connection to my personal computer.
Safing Portmaster - Easy Privacy
Portmaster is a free and open-source application that puts you back in charge over all your computer's network connections. Increase your privacy and security. Get peace of mind.
safing.io
I've tried using blissOS in virtualbox with hardware acceleration both on/off but it doesn't work either way.
I might check out vmware again, thanks for the info. Had my hopes up to get it running in vbox.
Edit: Windows 10 21H2, tried both blissOS 14 and 15, both fail.

ummm I just tested it, it works. You need to use the entry for no acceleration in the grub to boot. I'll send you a video soon. Also it didn't install for me when I used bios. (works with EFI)

traman124 said:
ummm I just tested it, it works. You need to use the entry for no acceleration in the grub to boot. I'll send you a video soon. Also it didn't install for me when I used bios. (works with EFI)
Click to expand...
Click to collapse
And how would you configure grub to not use acceleration? Guess i'll just wait for that video.
Oh and regarding windows, this is also great https://privacy.sexy

here's that video:
blissos.mp4
MP4 File
1drv.ms
be prepared for mediocre performance though
You can then add those parameters to the regular grub so you don't have to do that every time

Wondering why not
Dual Boot Bliss OS and Windows, Android 11 with Google Play Store​for example this one
Bliss OS 14.3 - Generic x86_64 - kernel-5.10.42 - 06.26.21

Works.. I just selected the vbox/vmware option...

@CXZa where did 6ou download that Bliss image?

@jwoegerbauer he's trying to run it on a VM, not dual boot.

traman124 said:
@CXZa where did 6ou download that Bliss image?
Click to expand...
Click to collapse
Bliss OS For PC
Open Source OS for PC's, based on AOSP
blissos.org