[qubes-users] Re: Android-x86 on Qubes 4
On Wednesday, August 8, 2018 at 1:37:53 PM UTC, rex mat wrote:
> After the manual install, I can boot, but ethernet can only be configured
> from the terminal. That is still work in progress.
> You need to have an android-x86 build and check out the 7.1.2 version to
> build a cd. I found the instruction on the web on the android-x86.org web
> page. I recommend using the ubuntu 16.4 version mentioned as the preferred
> build machine in a hope you avoid the pain I went through to do a build on
> qubes.
>
>
>
> I did the following 2 changes:
>
>
>
> 1. Changed 1 line in "init" inside initrd
> from:
>
> for device in ${ROOT:-/dev/[hmnsv][dmrv][0-9a-z]*}; do
> to:
>
> for device in ${ROOT:-/dev/[hmnsvx][dmrv][0-9a-z]*}; do
> That allows the XEN hard drive to be used at initialization
>
>
>
> 2. I configured the kernel
> Below is the config (I hope, as I played afterwards to get a proper mouse,
> with no avail). This config disabled a lot of things that need blobs and the
> like to get it built:
>
> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86_64 4.9.109 Kernel Configuration
> #
> CONFIG_64BIT=y
> CONFIG_X86_64=y
> CONFIG_X86=y
> CONFIG_INSTRUCTION_DECODER=y
> CONFIG_OUTPUT_FORMAT="elf64-x86-64"
> CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_MMU=y
> CONFIG_ARCH_MMAP_RND_BITS_MIN=28
> CONFIG_ARCH_MMAP_RND_BITS_MAX=32
> CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
> CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
> CONFIG_NEED_DMA_MAP_STATE=y
> CONFIG_NEED_SG_DMA_LENGTH=y
> CONFIG_GENERIC_ISA_DMA=y
> CONFIG_GENERIC_BUG=y
> CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
> CONFIG_GENERIC_HWEIGHT=y
> CONFIG_ARCH_MAY_HAVE_PC_FDC=y
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_GENERIC_CALIBRATE_DELAY=y
> CONFIG_ARCH_HAS_CPU_RELAX=y
> CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
> CONFIG_HAVE_SETUP_PER_CPU_AREA=y
> CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
> CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
> CONFIG_ARCH_HIBERNATION_POSSIBLE=y
> CONFIG_ARCH_SUSPEND_POSSIBLE=y
> CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
> CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
> CONFIG_ZONE_DMA32=y
> CONFIG_AUDIT_ARCH=y
> CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
> CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
> CONFIG_X86_64_SMP=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
> CONFIG_FIX_EARLYCON_MEM=y
> CONFIG_DEBUG_RODATA=y
> CONFIG_PGTABLE_LEVELS=4
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
> CONFIG_IRQ_WORK=y
> CONFIG_BUILDTIME_EXTABLE_SORT=y
> CONFIG_THREAD_INFO_IN_TASK=y
>
> #
> # General setup
> #
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> # CONFIG_COMPILE_TEST is not set
> CONFIG_LOCALVERSION="-android-x86_64"
> CONFIG_LOCALVERSION_AUTO=y
> CONFIG_HAVE_KERNEL_GZIP=y
> CONFIG_HAVE_KERNEL_BZIP2=y
> CONFIG_HAVE_KERNEL_LZMA=y
> CONFIG_HAVE_KERNEL_XZ=y
> CONFIG_HAVE_KERNEL_LZO=y
> CONFIG_HAVE_KERNEL_LZ4=y
> CONFIG_KERNEL_GZIP=y
> # CONFIG_KERNEL_BZIP2 is not set
> # CONFIG_KERNEL_LZMA is not set
> # CONFIG_KERNEL_XZ is not set
> # CONFIG_KERNEL_LZO is not set
> # CONFIG_KERNEL_LZ4 is not set
> CONFIG_DEFAULT_HOSTNAME="android_x86_64"
> CONFIG_SWAP=y
> # CONFIG_SYSVIPC is not set
> # CONFIG_POSIX_MQUEUE is not set
> CONFIG_CROSS_MEMORY_ATTACH=y
> # CONFIG_FHANDLE is not set
> # CONFIG_USELIB is not set
> CONFIG_AUDIT=y
> CONFIG_HAVE_ARCH_AUDITSYSCALL=y
> CONFIG_AUDITSYSCALL=y
> CONFIG_AUDIT_WATCH=y
> CONFIG_AUDIT_TREE=y
>
> #
> # IRQ subsystem
> #
> CONFIG_GENERIC_IRQ_PROBE=y
> CONFIG_GENERIC_IRQ_SHOW=y
> CONFIG_GENERIC_PENDING_IRQ=y
> CONFIG_GENERIC_IRQ_CHIP=y
> CONFIG_IRQ_DOMAIN=y
> CONFIG_IRQ_DOMAIN_HIERARCHY=y
> CONFIG_GENERIC_MSI_IRQ=y
> CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
> # CONFIG_IRQ_DOMAIN_DEBUG is not set
> CONFIG_IRQ_FORCED_THREADING=y
> CONFIG_SPARSE_IRQ=y
> CONFIG_CLOCKSOURCE_WATCHDOG=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
> CONFIG_GENERIC_CMOS_UPDATE=y
>
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ_COMMON=y
> # CONFIG_HZ_PERIODIC is not set
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
>
> #
> # CPU/Task time and stats accounting
> #
> CONFIG_TICK_CPU_ACCOUNTING=y
> # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
> # CONFIG_IRQ_TIME_ACCOUNTING is not set
> # CONFIG_SCHED_WALT is not set
> CONFIG_BSD_PROCESS_ACCT=y
> # CONFIG_BSD_PROCESS_ACCT_V3 is not set
> CONFIG_TASKSTATS=y
> CONFIG_TASK_DELAY_ACCT=y
> CONFIG_TASK_XACCT=y
> CONFIG_TASK_IO_ACCOUNTING=y
>
> #
> # RCU Subsystem
> #
> CONFIG_PREEMPT_RCU=y
> # CONFIG_RCU_EXPERT is not set
> CONFIG_SRCU=y
> # CONFIG_TASKS_RCU is not set
> CONFIG_RCU_STALL_COMMON=y
> # CONFIG_TREE_RCU_TRACE is not set
> # CONFIG_RCU_EXPEDITE_BOOT is not set
> CONFIG_BUILD_BIN2C=y
> CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_LOG_BUF_SHIFT=17
>
[qubes-users] Re: Android-x86 on Qubes 4
On Wednesday, August 8, 2018 at 9:37:53 PM UTC+8, rex mat wrote:
> After the manual install, I can boot, but ethernet can only be configured
> from the terminal. That is still work in progress.
> You need to have an android-x86 build and check out the 7.1.2 version to
> build a cd. I found the instruction on the web on the android-x86.org web
> page. I recommend using the ubuntu 16.4 version mentioned as the preferred
> build machine in a hope you avoid the pain I went through to do a build on
> qubes.
>
>
>
> I did the following 2 changes:
>
>
>
> 1. Changed 1 line in "init" inside initrd
> from:
>
> for device in ${ROOT:-/dev/[hmnsv][dmrv][0-9a-z]*}; do
> to:
>
> for device in ${ROOT:-/dev/[hmnsvx][dmrv][0-9a-z]*}; do
> That allows the XEN hard drive to be used at initialization
>
>
>
> 2. I configured the kernel
> Below is the config (I hope, as I played afterwards to get a proper mouse,
> with no avail). This config disabled a lot of things that need blobs and the
> like to get it built:
>
> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86_64 4.9.109 Kernel Configuration
> #
> CONFIG_64BIT=y
> CONFIG_X86_64=y
> CONFIG_X86=y
> CONFIG_INSTRUCTION_DECODER=y
> CONFIG_OUTPUT_FORMAT="elf64-x86-64"
> CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_MMU=y
> CONFIG_ARCH_MMAP_RND_BITS_MIN=28
> CONFIG_ARCH_MMAP_RND_BITS_MAX=32
> CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
> CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
> CONFIG_NEED_DMA_MAP_STATE=y
> CONFIG_NEED_SG_DMA_LENGTH=y
> CONFIG_GENERIC_ISA_DMA=y
> CONFIG_GENERIC_BUG=y
> CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
> CONFIG_GENERIC_HWEIGHT=y
> CONFIG_ARCH_MAY_HAVE_PC_FDC=y
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_GENERIC_CALIBRATE_DELAY=y
> CONFIG_ARCH_HAS_CPU_RELAX=y
> CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
> CONFIG_HAVE_SETUP_PER_CPU_AREA=y
> CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
> CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
> CONFIG_ARCH_HIBERNATION_POSSIBLE=y
> CONFIG_ARCH_SUSPEND_POSSIBLE=y
> CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
> CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
> CONFIG_ZONE_DMA32=y
> CONFIG_AUDIT_ARCH=y
> CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
> CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
> CONFIG_X86_64_SMP=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
> CONFIG_FIX_EARLYCON_MEM=y
> CONFIG_DEBUG_RODATA=y
> CONFIG_PGTABLE_LEVELS=4
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
> CONFIG_IRQ_WORK=y
> CONFIG_BUILDTIME_EXTABLE_SORT=y
> CONFIG_THREAD_INFO_IN_TASK=y
>
> #
> # General setup
> #
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> # CONFIG_COMPILE_TEST is not set
> CONFIG_LOCALVERSION="-android-x86_64"
> CONFIG_LOCALVERSION_AUTO=y
> CONFIG_HAVE_KERNEL_GZIP=y
> CONFIG_HAVE_KERNEL_BZIP2=y
> CONFIG_HAVE_KERNEL_LZMA=y
> CONFIG_HAVE_KERNEL_XZ=y
> CONFIG_HAVE_KERNEL_LZO=y
> CONFIG_HAVE_KERNEL_LZ4=y
> CONFIG_KERNEL_GZIP=y
> # CONFIG_KERNEL_BZIP2 is not set
> # CONFIG_KERNEL_LZMA is not set
> # CONFIG_KERNEL_XZ is not set
> # CONFIG_KERNEL_LZO is not set
> # CONFIG_KERNEL_LZ4 is not set
> CONFIG_DEFAULT_HOSTNAME="android_x86_64"
> CONFIG_SWAP=y
> # CONFIG_SYSVIPC is not set
> # CONFIG_POSIX_MQUEUE is not set
> CONFIG_CROSS_MEMORY_ATTACH=y
> # CONFIG_FHANDLE is not set
> # CONFIG_USELIB is not set
> CONFIG_AUDIT=y
> CONFIG_HAVE_ARCH_AUDITSYSCALL=y
> CONFIG_AUDITSYSCALL=y
> CONFIG_AUDIT_WATCH=y
> CONFIG_AUDIT_TREE=y
>
> #
> # IRQ subsystem
> #
> CONFIG_GENERIC_IRQ_PROBE=y
> CONFIG_GENERIC_IRQ_SHOW=y
> CONFIG_GENERIC_PENDING_IRQ=y
> CONFIG_GENERIC_IRQ_CHIP=y
> CONFIG_IRQ_DOMAIN=y
> CONFIG_IRQ_DOMAIN_HIERARCHY=y
> CONFIG_GENERIC_MSI_IRQ=y
> CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
> # CONFIG_IRQ_DOMAIN_DEBUG is not set
> CONFIG_IRQ_FORCED_THREADING=y
> CONFIG_SPARSE_IRQ=y
> CONFIG_CLOCKSOURCE_WATCHDOG=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
> CONFIG_GENERIC_CMOS_UPDATE=y
>
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ_COMMON=y
> # CONFIG_HZ_PERIODIC is not set
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
>
> #
> # CPU/Task time and stats accounting
> #
> CONFIG_TICK_CPU_ACCOUNTING=y
> # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
> # CONFIG_IRQ_TIME_ACCOUNTING is not set
> # CONFIG_SCHED_WALT is not set
> CONFIG_BSD_PROCESS_ACCT=y
> # CONFIG_BSD_PROCESS_ACCT_V3 is not set
> CONFIG_TASKSTATS=y
> CONFIG_TASK_DELAY_ACCT=y
> CONFIG_TASK_XACCT=y
> CONFIG_TASK_IO_ACCOUNTING=y
>
> #
> # RCU Subsystem
> #
> CONFIG_PREEMPT_RCU=y
> # CONFIG_RCU_EXPERT is not set
> CONFIG_SRCU=y
> # CONFIG_TASKS_RCU is not set
> CONFIG_RCU_STALL_COMMON=y
> # CONFIG_TREE_RCU_TRACE is not set
> # CONFIG_RCU_EXPEDITE_BOOT is not set
> CONFIG_BUILD_BIN2C=y
> CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_LOG_BUF_SHIFT=17
>
Re: [qubes-users] Re: Android-x86 on Qubes
On 04/11/2017 12:17 PM, Desobediente wrote: I've tried every possibility to install or boot from live iso both cyanogen mod x86 and android-x86 and I've never had any luck. The HVM just sits there forever with "ANDROID" spinning. It goes on for days. Android 4.4 x86 work and install without any problems on HVM. Where do you have problem? Only 3 problems related to Android that I do not know how to solve: 1) How to emulate Fake Wifi connection (Android must think that he is connected to wifi network. 2) One installer messenger does not work. Say that "not connected". I think it request income/outcome open UDP port. Is it possible to somehow open them on VPN connection before android? 3) How to easy copy files from HVM without Qubes Copy I tried to attach Usb stick to Android, but it does not see it (or does not mount it automatically and I do not know how to mount usb stick) -- Regards -- 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/c309d056-9ed8-14c6-9c6a-d42fc49a5953%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Android-x86 on Qubes
I've tried every possibility to install or boot from live iso both cyanogen mod x86 and android-x86 and I've never had any luck. The HVM just sits there forever with "ANDROID" spinning. It goes on for days. -- 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/b250d018-2977-4cb7-b77e-ac4f70b7f00e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
Torsten Grote: > On 11/11/2016 06:01 PM, entr0py wrote: >> Thanks! With that, some progress... Deleting `> bus='xen'/>` from the config file results in usbtablet being >> replaced with ps/2 mouse device. > > I finally got around to try that and it works indeed! > >> Now, the pointer tracks mouse movements automatically instead of >> requiring manual dragging. However, the mouse acceleration doesn't >> match and the two pointers become de-synced. > > Yes that has other usability issues than the drag pointer. I wonder if > it is possible to change the mouse speed somehow. Maybe just temporarily > in dom0? > >> The mouse problem is not a Xen/Qubes issue. Android-x86-4.4-r5 >> (KitKat) works perfectly on Qubes. Input handling has changed somehow >> in Lollipop/Marshamallow. I would be perfectly content to use KitKat >> but (of course), that version doesn't emulate OpenGL (under Qubes) >> which breaks many Android apps > > For me the problem with Android 4.4 is that it doesn't support ADB over > IP, so there seems to be no way to connect with the debug bridge to it. > >> @Torsten: Did you see my last comment on the issue tracker? Other >> than that, make sure partition is bootable and use a compatible vga >> mode. > > Yes, I saw that, but I still can't boot the installed version. If I boot > into the system right after installation it works, but if I shut it down > and try to boot later, it just maxes out the load on one CPU and hangs > at "Booting from Hard Disk..." > > The partition is bootable and I installed GRUB and tried EFI GRUB 2 as > well. It doesn't even seem to reach GRUB, so maybe an incompatible vga > mode is not the problem. Do you use GPT? Which filesystem? > > When trying around I could even once get GRUB2 to start only to then > fail with an error 17. > > I have the same issue with Android 4 and 6. Do you remove the "CD" from > the VM config after the installation or do you always boot from the ISO? > > Kind Regards, > Torsten > GPT: no GRUB: yes EFI GRUB2: no Filesystem: whatever is the latest, EXT3/4 System: read/write (most likely irrelevant) I always `Reboot` after install. When the GRUB loader appears, I kill the VM and clone if necessary at that point. I vaguely recall having had problems by Launching right after install. It appears the video mode incompatibilities have been resolved since I last played with this. You should be able to proceed straight to the desktop. RemixOS is much more usable on the desktop and also has an option to disable screen timeout in Marshmallow. Damn mouse though... -- 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/3c88ddd2-cd09-ea1c-d9a5-0a6f1d7e3d4e%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
On 11/11/2016 06:01 PM, entr0py wrote: > Thanks! With that, some progress... Deleting ` bus='xen'/>` from the config file results in usbtablet being > replaced with ps/2 mouse device. I finally got around to try that and it works indeed! > Now, the pointer tracks mouse movements automatically instead of > requiring manual dragging. However, the mouse acceleration doesn't > match and the two pointers become de-synced. Yes that has other usability issues than the drag pointer. I wonder if it is possible to change the mouse speed somehow. Maybe just temporarily in dom0? > The mouse problem is not a Xen/Qubes issue. Android-x86-4.4-r5 > (KitKat) works perfectly on Qubes. Input handling has changed somehow > in Lollipop/Marshamallow. I would be perfectly content to use KitKat > but (of course), that version doesn't emulate OpenGL (under Qubes) > which breaks many Android apps For me the problem with Android 4.4 is that it doesn't support ADB over IP, so there seems to be no way to connect with the debug bridge to it. > @Torsten: Did you see my last comment on the issue tracker? Other > than that, make sure partition is bootable and use a compatible vga > mode. Yes, I saw that, but I still can't boot the installed version. If I boot into the system right after installation it works, but if I shut it down and try to boot later, it just maxes out the load on one CPU and hangs at "Booting from Hard Disk..." The partition is bootable and I installed GRUB and tried EFI GRUB 2 as well. It doesn't even seem to reach GRUB, so maybe an incompatible vga mode is not the problem. Do you use GPT? Which filesystem? When trying around I could even once get GRUB2 to start only to then fail with an error 17. I have the same issue with Android 4 and 6. Do you remove the "CD" from the VM config after the installation or do you always boot from the ISO? Kind Regards, Torsten -- 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/4f5d7f0d-1d04-aa76-f20b-01fa661b19c1%40grobox.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Nov 11, 2016 at 07:20:55PM -0200, Torsten Grote wrote: > On 11/11/2016 06:01 PM, entr0py wrote: > > Thanks! With that, some progress... Deleting ` > bus='xen'/>` from the config file results in usbtablet being replaced > > with ps/2 mouse device. > > Awesome, thanks Marek! > > Is there any way to make this permanent so we don't need to start the VM > with qvm-start each time? There is a hacky way to change "conf_file" entry in qubes.xml. It may have unknown side effects... > > Now, the pointer tracks mouse movements > > automatically instead of requiring manual dragging. However, the > > mouse acceleration doesn't match and the two pointers become > > de-synced. > > It was de-synced before already I think, but it would of course be nice > if that could be adjusted as well. AFAIR this was the main reason to use tablet device instead of mouse there. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYJlrbAAoJENuP0xzK19csFpwH/in3kCJGW7SEYyUH/fxgeTnM MwlgcTO66UxBO4rd+idSIyMLa6KiYsQLi7Z9yO90kEyNKCzD90pnTuTDMLXsH2A5 Ve2LliuXZED7I7AewOvtMC7EEXIVhFTJNK7YYeiO1ji4eTMxOcJ3s6yOMfMtI+q/ z1zBlgiwaMmqU7xX3veZMuAqPeCZep8v6aa9j/3Z/VZjQNPuJbW5Hqu0PIhBX3M5 Io3VPj+tp4+nK1jYUunRpZPlrn3T/XYqaaLg7H7WjcZIUQ8WDNTnW+idSQa46ovJ cWjhL5wHueG5oVVEvOmm3TcvrbT1szXjO1It/js/LhJ+LnfWAa1KBRGkcumLSPI= =pCqM -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/2016235717.GK7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
Marek Marczykowski-Górecki: > On Tue, Nov 08, 2016 at 11:09:37PM -0200, Torsten Grote wrote: >> On 11/07/2016 08:54 PM, 3n7r0...@gmail.com wrote: >>> AFAICT, it's an issue with how QEMU is implemented in Xen. The input >>> device in question is passed via `-usbdevice tablet` instead of being >>> left to the default PS/2 emulation. There doesn't seem to be any easy >>> way to disable that parameter from within Xen? > >> I would also be very interested in that! Marek, do you know? > > It is possible to modify config in /var/lib/qubes/appvms/, but for that > you need to copy it first, then pass its new location to qvm-start > --custom-config=... > Thanks! With that, some progress... Deleting `` from the config file results in usbtablet being replaced with ps/2 mouse device. Now, the pointer tracks mouse movements automatically instead of requiring manual dragging. However, the mouse acceleration doesn't match and the two pointers become de-synced. The mouse problem is not a Xen/Qubes issue. Android-x86-4.4-r5 (KitKat) works perfectly on Qubes. Input handling has changed somehow in Lollipop/Marshamallow. I would be perfectly content to use KitKat but (of course), that version doesn't emulate OpenGL (under Qubes) which breaks many Android apps - even non-3D things like Gallery, Maps, Chrome... @Torsten: Did you see my last comment on the issue tracker? Other than that, make sure partition is bootable and use a compatible vga mode. -- 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/99c29989-f671-2444-3bd2-87666dbafb94%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Nov 08, 2016 at 11:09:37PM -0200, Torsten Grote wrote: > On 11/07/2016 08:54 PM, 3n7r0...@gmail.com wrote: > > AFAICT, it's an issue with how QEMU is implemented in Xen. The input > > device in question is passed via `-usbdevice tablet` instead of being > > left to the default PS/2 emulation. There doesn't seem to be any easy > > way to disable that parameter from within Xen? > > I would also be very interested in that! Marek, do you know? It is possible to modify config in /var/lib/qubes/appvms/, but for that you need to copy it first, then pass its new location to qvm-start - --custom-config=... - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYJeKnAAoJENuP0xzK19csvpUH/iXmt08lhwbJZMdGGW649TGc cJXRE0m+yMqXBWsSL/vgW3vsMijmQiqqEa3IHBUPgAWIlz6KY0dgEG3RXf3XBRuz t1hrFUwcMYOp/qiDPC630O6Ipcp25c4KI0xYCopkQZo+4j5J3QFXZ8aAAyxBcM2S x3juYgY8JVMsTeRAm8shRm5m6jgD+yiLW33DrG7TyGesdoSHriuxwZs30pRg7L8S ewPFK03McKXS4JEQzlj0kYUzDAQ65H++K3VA4ULn3zdsRmTqea+sd2Q37e+s2Enc yCMwF7sNZb4LycdgP/Qhw7O3c4UD5yzY7OCyYOSOIcbRgLeeF8opSC6VDJcC1Jw= =x4/C -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/2016152425.GF7073%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
On 11/07/2016 08:54 PM, 3n7r0...@gmail.com wrote: > AFAICT, it's an issue with how QEMU is implemented in Xen. The input > device in question is passed via `-usbdevice tablet` instead of being > left to the default PS/2 emulation. There doesn't seem to be any easy > way to disable that parameter from within Xen? I would also be very interested in that! Marek, do you know? Kind Regards, Torsten -- 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/52ca9454-e84b-e8f5-d8fb-4b7721248d77%40grobox.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Android-x86 on Qubes
On 11/07/2016 04:02 PM, 3n7r0...@gmail.com wrote: On Monday, November 7, 2016 at 8:57:16 PM UTC, 3n7r...@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. Cool. You are doing this as a standalone HVM? Configuring /home can be as simple as that, esp. if you have the additional drive configured for that VM. Chris -- 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/dd3cf29f-125d-e2af-3b09-d68a2788048f%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Android-x86 on Qubes
On Monday, November 7, 2016 at 8:57:16 PM UTC, 3n7r...@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. Forgot to mention that networking works out-of-the-box. Also, it appears the mouse issue is solved here: https://groups.google.com/forum/#!searchin/android-x86/mouse$20issue|sort:date/android-x86/iFoKcvK2xNE/nYHoR6oSBgAJ Will report back once I've had a chance to investigate. -- 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/e944b7b0-8058-4386-8db3-d26286221cbb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
