Re: [qubes-users] Android-x86 on Qubes 4

2018-08-08 Thread trueriver 
Rex, you have got further than me with this!

I strongly endorse Olivie's request quoted below.

I am one of the many persons he mentions.

Warmly
R~~

On Wednesday, 8 August 2018 09:41:46 UTC+1, Olivie Médoc  wrote:
> ... 
> Is it possible that you sent brief notes about how you modified the
> android cd in order to make it installable ?
> 
> 
> 
> A lot of persons are apparently digging through this problem and it
> would help a lot.
>...

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/11471ce7-5c1e-4899-8967-c6893f5bd189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Android-x86 on Qubes 4

2018-08-08 Thread 'Olivie Médoc' via qubes-users 
On 08/02/18 15:32, Mat Rex wrote:
> I was able to install android-x86 7.1.2 on Qubes 4.0.
>  
> I created an android-x86 CD with a custom kernel and a change to the
> android init script.

Is it possible that you sent brief notes about how you modified the
android cd in order to make it installable ?

A lot of persons are apparently digging through this problem and it
would help a lot.

There is also a qubes issue related to that:
https://github.com/QubesOS/qubes-issues/issues/2233

This would be greatly appreciated.


>  
> I created a standalone HVM, booted linux from a CD to create ext2
> filesystem and installed legacy grub. [if you have a hard disk drive,
> YMMV. I think old grub and SSD do not like each other via all these VM
> layers, but this is untested - for now I just stick to ext2]
>  
> Booting the android-x86 CD I could install android. I refused to
> convert the filesystem to ext3 or to ext4 when the installer gave the
> option and skipped installing grub from android-x86.
>  
> Booting linux from CD again I updated the grub configuration
> (menu.lst) to boot android-x86.
>  
> After this the android installation can be booted. It has the known
> tablet-mouse issue. I can configure networking from the terminal -
> sometimes. Other times it takes me a lot of repeated entering of
> commands I saw on various forums. I am looking into the best way to
> automate this, will probably need to create a new cd. [this is an AOS
> CD, no google play, no proprietary drivers.]
>  
> However: You cannot attach a microphone or camera to this VM (except
> if you assign the hardware controller to it), so its use is limited.
> The VM does not even shut down, it needs a kill.
>  
> If there is any interest at this early stage, I can provide the CD as
> is or the pointers/patches/configurations how to create it. I hope to
> automate networking configuration in some form in a week or two.

Networking works out of the box in my case. I use an HVM with Android
x86_64 7.1.2 and booting on the live version.

>  
> I am not planing to further deal with the tablet-mouse issue. Using
> the keyboard more and the "mouse" less, you can get by. That should
> not be hard to fix on the qubes side, IMHO. It is not clear yet how
> usb devices can be attached to this VM, but that is something I would
> like solve, but given that on the windows side it has a separate
> maintainer, it might take a while.
> -- 
> You received this message because you are subscribed to the Google
> Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to qubes-users+unsubscr...@googlegroups.com
> .
> To post to this group, send email to qubes-users@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/5742571533216758%40sas1-38f90f4f25ea.qloud-c.yandex.net
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c1ccd8fd-7dc0-1b51-cabb-1e5d667530e1%40yahoo.fr.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Android-x86 on Qubes 4

2018-08-02 Thread Mat Rex 
I was able to install android-x86 7.1.2 on Qubes 4.0. I created an android-x86 CD with a custom kernel and a change to the android init script. I created a standalone HVM, booted linux from a CD to create ext2 filesystem and installed legacy grub. [if you have a hard disk drive, YMMV. I think old grub and SSD do not like each other via all these VM layers, but this is untested - for now I just stick to ext2] Booting the android-x86 CD I could install android. I refused to convert the filesystem to ext3 or to ext4 when the installer gave the option and skipped installing grub from android-x86. Booting linux from CD again I updated the grub configuration (menu.lst) to boot android-x86. After this the android installation can be booted. It has the known tablet-mouse issue. I can configure networking from the terminal - sometimes. Other times it takes me a lot of repeated entering of commands I saw on various forums. I am looking into the best way to automate this, will probably need to create a new cd. [this is an AOS CD, no google play, no proprietary drivers.] However: You cannot attach a microphone or camera to this VM (except if you assign the hardware controller to it), so its use is limited. The VM does not even shut down, it needs a kill. If there is any interest at this early stage, I can provide the CD as is or the pointers/patches/configurations how to create it. I hope to automate networking configuration in some form in a week or two. I am not planing to further deal with the tablet-mouse issue. Using the keyboard more and the "mouse" less, you can get by. That should not be hard to fix on the qubes side, IMHO. It is not clear yet how usb devices can be attached to this VM, but that is something I would like solve, but given that on the windows side it has a separate maintainer, it might take a while.



-- 
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5742571533216758%40sas1-38f90f4f25ea.qloud-c.yandex.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Android-x86 on Qubes

2016-11-08 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-11-07 12:57, 3n7r0...@gmail.com wrote:
> Using stock android-x86_64-6.0-r1.iso from android-x86.org (cm not tested)
> 
> Issues:
> 1. no boot
> 2. mouse support
> 3. wake from sleep
> 4. private storage
> 5. secure clipboard
> 
> 1. If HVM hangs priors to splash screen, try adding `vga=ask` to boot kernel 
> parameters. (1024x768x16 works for me)
> 
> 2. Mouse cursor needs to be dragged around inside vm. 
> Not aware of any workaround. 
> Previously reported: 
> https://groups.google.com/d/msg/qubes-users/2GAfjsltkmk/QY9fVetKKAAJ
> 
> 3. Can't figure out how to wake hvm from sleep. 
> Untested workaround: Disable sleep completely by adding: 
> "setprop sleep.state disabled" to /data/local.prop
> or "sleep.state=disabled" to /system/build.prop 
> (https://groups.google.com/d/msg/android-x86/8iSh5pVqv4U/Fz8Nh11UDwAJ)
> 
> 4. Is moving /home/ as simple as copying and editing fstab or are there 
> qubes-specific steps that need to be taken? If yes, would appreciate it if 
> someone could point me to qubes package that handles this.
> 
> 5. No clue. I hope someone is willing to work on this.
> 

Cross-linking open GitHub issue:

https://github.com/QubesOS/qubes-issues/issues/2233

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYIZZUAAoJENtN07w5UDAwSdYP/i2G79s4oJvY8wIhD6O5hytU
11d9vGcPjowofIjdleE5KdnAgy0FB/ny68BGC3upc0nB7TIHobdOP+2h74qzXeEa
kDryIVIDmPiL4hQNGqGPILP64LsUNvvYNhME4LTKb6Nhyb4X3IAIWv2DiLp72CP9
tpj6Mok9ybbmyuXuOgE1sddTz6Tjcbak4oxRqOCtY+uBURZe7ZqnqWtSuKrUJVCZ
5oMFwcrPliVewHEDaxv7z3uMUWS/cwfICZ2CxWVpNAqF/6vUvMwWeEn1i27wXzvH
fFapTksovg9LhG32JYGELe87zbPmz4rfzL0KNbDDdH6dTVO9dCygk42YGbt23fNU
KsaHf3a/fvVzk/GkWxDpCo4LiOgQo3Ih+dp+3HwFPs5TwZOzKp24rJEKERAtz520
6fQ2PQ/zb/khlgz+IeymKJQ5MOU6t8IUwKP88YpCTbIaX0GFhgmEuXv+zpWHihgL
NBggiHOYVCn7W89M4GtM1Uv7nD1h4Qkb5VzgffZa8OtNctRa68hoGSGkqaymb2mo
52aH91/qvYd+vbszgp2dzNSjAaUv0X2plU45zBUOtT/A9VLl/FhR2NqfM+dhsRrd
20FWVx6Wsu0i/9dScOn/16LfZ9MA771mTfzpWXE5R2Gvhf91N8piFHtqx93JKkqP
QwZ2rnu39VLaLGteznre
=nZh+
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9e18c507-2ffc-cb72-0858-a07bf72b2177%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Android-x86 on Qubes

2016-11-07 Thread 3n7r0py1 
Using stock android-x86_64-6.0-r1.iso from android-x86.org (cm not tested)

Issues:
1. no boot
2. mouse support
3. wake from sleep
4. private storage
5. secure clipboard

1. If HVM hangs priors to splash screen, try adding `vga=ask` to boot kernel 
parameters. (1024x768x16 works for me)

2. Mouse cursor needs to be dragged around inside vm. 
Not aware of any workaround. 
Previously reported: 
https://groups.google.com/d/msg/qubes-users/2GAfjsltkmk/QY9fVetKKAAJ

3. Can't figure out how to wake hvm from sleep. 
Untested workaround: Disable sleep completely by adding: 
"setprop sleep.state disabled" to /data/local.prop
or "sleep.state=disabled" to /system/build.prop 
(https://groups.google.com/d/msg/android-x86/8iSh5pVqv4U/Fz8Nh11UDwAJ)

4. Is moving /home/ as simple as copying and editing fstab or are there 
qubes-specific steps that need to be taken? If yes, would appreciate it if 
someone could point me to qubes package that handles this.

5. No clue. I hope someone is willing to work on this.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8a849a2b-92e3-4be7-a54e-00290af811a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.