Re: [qubes-users] Re: Android Emulator

2016-08-21 Thread yonjah
On Sunday, August 21, 2016 at 11:02:48 PM UTC+8, johny...@sigaint.org wrote: > > On Friday, August 5, 2016 at 1:52:12 AM UTC+8, Torsten Grote wrote: > >> I tried it now and it works, but is barely usable, because it is > >> very(!!!) slow. On top of running ARM emulation in an AppVM, I needed to >

Re: [qubes-users] Re: Android Emulator

2016-08-21 Thread johnyjukya
> On Friday, August 5, 2016 at 1:52:12 AM UTC+8, Torsten Grote wrote: >> I tried it now and it works, but is barely usable, because it is >> very(!!!) slow. On top of running ARM emulation in an AppVM, I needed to >> turn on software graphic rendering, because hardware rendering didn't >> work. > >

Re: [qubes-users] Re: Android Emulator

2016-08-20 Thread yonjah
On Friday, August 5, 2016 at 1:52:12 AM UTC+8, Torsten Grote wrote: > I tried it now and it works, but is barely usable, because it is > very(!!!) slow. On top of running ARM emulation in an AppVM, I needed to > turn on software graphic rendering, because hardware rendering didn't work. Did any on

Re: [qubes-users] Re: Android Emulator

2016-08-05 Thread raahelps
On Thursday, August 4, 2016 at 1:52:12 PM UTC-4, Torsten Grote wrote: > On 08/03/2016 12:10 PM, Torsten Grote wrote: > > Oh thanks! I didn't try using an ARM image. If you ever find out how to > > run an x86 image with Qubes, please let me know. > > I tried it now and it works, but is barely usabl

Re: [qubes-users] Re: Android Emulator

2016-08-04 Thread Alex
On 08/04/2016 07:51 PM, Torsten Grote wrote: > I tried it now and it works, but is barely usable, because it is > very(!!!) slow. On top of running ARM emulation in an AppVM, I needed > to turn on software graphic rendering, because hardware rendering > didn't work. Yeah, it's quite slow, but depe

Re: [qubes-users] Re: Android Emulator

2016-08-04 Thread Torsten Grote
On 08/03/2016 12:10 PM, Torsten Grote wrote: > Oh thanks! I didn't try using an ARM image. If you ever find out how to > run an x86 image with Qubes, please let me know. I tried it now and it works, but is barely usable, because it is very(!!!) slow. On top of running ARM emulation in an AppVM, I

Re: [qubes-users] Re: Android Emulator

2016-08-03 Thread Torsten Grote
On 08/03/2016 11:37 AM, Alex wrote: > It says that to me too, but using an ARM image does work (this message > is just a warning) Oh thanks! I didn't try using an ARM image. If you ever find out how to run an x86 image with Qubes, please let me know. > once disconnected from usbVM and attached to

Re: [qubes-users] Re: Android Emulator

2016-08-03 Thread Alex
On 08/03/2016 03:35 PM, Torsten Grote wrote: > Hi Alex, > > On 08/03/2016 06:56 AM, Alex wrote: >> You appVMs may vary: in my work vm, where I use 2 IDEs (Android >> Studio and MonoDevelop) + android emulator + firefox + thunderbird, >> I capped at 10GB and it works ok. > > Do you mind explaining

[qubes-users] Re: Android Emulator (was: 3.2 RC - which VM settings?)

2016-08-03 Thread Torsten Grote
Hi Alex, On 08/03/2016 06:56 AM, Alex wrote: > You appVMs may vary: in my work vm, where I use 2 IDEs (Android Studio > and MonoDevelop) + android emulator + firefox + thunderbird, I capped at > 10GB and it works ok. Do you mind explaining how you got the Android Emulator working in an AppVM? If